
From nobody Wed Apr  1 00:25:01 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B0F1ACE63; Tue, 31 Mar 2015 13:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udWx84H-UVyf; Tue, 31 Mar 2015 13:07:08 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 16DD81ACE8B; Tue, 31 Mar 2015 13:07:07 -0700 (PDT)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2VK70Ff012765 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2015 16:07:00 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com t2VK70Ff012765
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427832421; bh=TqNZlG5anUMdPif06+kNOxHHVjM=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=Y8IBFPbViamALDZMhJCmdOvIVNq2vjSfay8ckjt2+XlA4oSX0J+OYpNmHhSb124Fu P6Z7GmYooHJKVHDxSxbfSeu25D3cukmWApCDGL3j8h8dAL9IG5oGybdnFAdDIPS0S0 Y8kerlLDblNJh8Ll/E9QYhAh2aj/Be2mHfd7mnDk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com t2VK70Ff012765
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd01.lss.emc.com (RSA Interceptor); Tue, 31 Mar 2015 16:06:38 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2VK6o00004409 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 16:06:50 -0400
Received: from MXHUB105.corp.emc.com (10.253.50.22) by mxhub33.corp.emc.com (10.254.93.81) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 31 Mar 2015 16:06:49 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB105.corp.emc.com ([10.253.50.22]) with mapi id 14.03.0224.002; Tue, 31 Mar 2015 16:06:50 -0400
From: "Black, David" <david.black@emc.com>
To: Lucy yong <lucy.yong@huawei.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAy+K+AAApXc7AAEy4w8AAl8toQ
Date: Tue, 31 Mar 2015 20:06:49 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936430EE6@MX104CL02.corp.emc.com>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <78DCD4FF-4030-4386-A0CA-7AA5FF1C2E4A@cisco.com> <2691CE0099834E4A9C5044EEC662BB9D571555B8@dfweml701-chm>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D571555B8@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D24327794936430EE6MX104CL02corpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qy-C6hVPyRSfoawDFVm3gOaEavo>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>, "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 20:07:12 -0000

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

SGkgQ2FybG9zLA0KDQo+IE9uZSBhcHByb2FjaCBpcyB0byBhZGQgYSAzLmMpIHRvIHRoZSBsaXN0
IHRoYXQgUm9uIHNoYXJlZC4gSSB0aGluayB0aGVyZSBpcyBhbm90aGVyIHBvdGVudGlhbCBhcHBy
b2FjaCB0byB5b3VyIGluaXRpYWwgY29tbWVudDoNCj4gd2UgY291bGQgbm90ZSB0aGF0IGZvciBh
IHR1bm5lbGluZyBwcm90b2NvbCAoR1JFKSwgdGhpcyBpcyBlcXVpdmFsZW50IHRvIHRoZSByZWxh
eGF0aW9uIG9mIHRoZSBVRFAgY2hlY2tzdW0gaW4gUkZDIDY5MzUsIGFuZCBrZWVwIHRoZSBleGlz
dGluZyB0ZXh0Lg0KDQpJdOKAmXMgbm90IHRoYXQgc2ltcGxlIChJIHdpc2ggaXQgd2FzKS4gICBU
aGUgc2hvcnQgc3VtbWFyeSBpcyBSRkMgNjkzNSBkb2VzIG5vdCBzZXQgYSBwcmVjZWRlbnQgdGhh
dCBjYW4ganVzdCBiZSBjaXRlZCAtIGluIHBhcnRpY3VsYXIgYSBzaW5nbGUgc2VudGVuY2UgcG9p
bnRpbmcgdG8gUkZDIDY5MzUgdG8gc2F5IOKAnHRoZXJlZm9yZSB0aGlzIGlzIG9r4oCdIGlzIGxp
a2VseSB0byBnYXJuZXIgbXVsdGlwbGUgSUVTRyBEaXNjdXNzIHBvc2l0aW9ucyBmb3Igbm90IGV4
cGxhaW5pbmcgd2h5LCBzb3JyeSAoTHVjeSBhbmQgSSBhcmUgaW4gdGhlIG1pZHN0IG9mIHdvcmtp
bmcgdGhyb3VnaCB0aGlzIGZvciBHUkUtaW4tVURQKS4NCg0KRm9yIHRoZSBsb25nIHZlcnNpb24s
IHBsZWFzZSBzdGFydCB3aXRoIFNlY3Rpb24gMy4xIG9mIHRoZSBNUExTLWluLVVEUCBkcmFmdCAo
aW4gQVVUSDQ4IGF0IHRoZSBSRkMgRWRpdG9yKToNCg0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0xMSNzZWN0aW9uLTMuMQ0KDQpTZWN0aW9uIDMuMiBp
cyBhbHNvIGFwcGxpY2FibGUsIGJ1dCBtdWNoIHNob3J0ZXIgYW5kIHJlYXNvbmFibHkgc3RyYWln
aHRmb3J3YXJkIGJ5IGNvbXBhcmlzb24uDQoNClRoYW5rcywNCi0tRGF2aWQNCg0KRnJvbTogTHVj
eSB5b25nIFttYWlsdG86bHVjeS55b25nQGh1YXdlaS5jb21dDQpTZW50OiBUdWVzZGF5LCBNYXJj
aCAzMSwgMjAxNSAzOjQ4IFBNDQpUbzogTHVjeSB5b25nOyBDYXJsb3MgUGlnbmF0YXJvIChjcGln
bmF0YSk7IEJsYWNrLCBEYXZpZA0KQ2M6IFJvbmFsZCBQLiBCb25pY2E7IGludC1hcmVhQGlldGYu
b3JnOyBpcHY2QGlldGYub3JnOyBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0
Zi5vcmc7IGludGFyZWEtY2hhaXJzQGlldGYub3JnDQpTdWJqZWN0OiBSRTogW0ludC1hcmVhXSBT
dGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KDQpIaSBDYXJs
b3MsDQoNCkkgYW0gbm90IGNsZWFyIHdoYXQgeW91IHByb3Bvc2UgaGVyZS4gVURQIGNoZWNrc3Vt
IGluY2x1ZGVzIElQIGhlYWRlciwgR1JFIGNoZWNrc3VtIGRvZXMgbm90Lg0KDQpSZWdhcmRzLA0K
THVjeQ0KDQpGcm9tOiBDYXJsb3MgUGlnbmF0YXJvIChjcGlnbmF0YSkgW21haWx0bzpjcGlnbmF0
YUBjaXNjby5jb21dDQpTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSAyOjAxIFBNDQpUbzog
QmxhY2ssIERhdmlkOyBMdWN5IHlvbmcNCkNjOiBSb25hbGQgUC4gQm9uaWNhOyBpbnQtYXJlYUBp
ZXRmLm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnPG1haWx0bzpp
cHY2QGlldGYub3JnPjsgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3Jn
PG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc+OyBpbnRh
cmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBSZTogW0ludC1hcmVhXSBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEt
Z3JlLWlwdjYNCg0KSGksIEx1Y3ksDQoNCk9uZSBhcHByb2FjaCBpcyB0byBhZGQgYSAzLmMpIHRv
IHRoZSBsaXN0IHRoYXQgUm9uIHNoYXJlZC4gSSB0aGluayB0aGVyZSBpcyBhbm90aGVyIHBvdGVu
dGlhbCBhcHByb2FjaCB0byB5b3VyIGluaXRpYWwgY29tbWVudDogd2UgY291bGQgbm90ZSB0aGF0
IGZvciBhIHR1bm5lbGluZyBwcm90b2NvbCAoR1JFKSwgdGhpcyBpcyBlcXVpdmFsZW50IHRvIHRo
ZSByZWxheGF0aW9uIG9mIHRoZSBVRFAgY2hlY2tzdW0gaW4gUkZDIDY5MzUsIGFuZCBrZWVwIHRo
ZSBleGlzdGluZyB0ZXh0Lg0KDQpGcmVkLCBSRkMgMjQ3MyBkb2VzIG5vdCBtZW50aW9uIGNoZWNr
c3Vtcy4NCg0KVGhhbmtzLA0KDQpDYXJsb3MuDQoNCg0K

--_000_CE03DB3D7B45C245BCA0D24327794936430EE6MX104CL02corpemcc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0
YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiO30NCnNwYW4uQmFsbG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29u
IFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJC
YWxsb29uIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFu
LmFwcGxlLWNvbnZlcnRlZC1zcGFjZQ0KCXttc28tc3R5bGUtbmFtZTphcHBsZS1jb252ZXJ0ZWQt
c3BhY2U7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNw
YW4uRW1haWxTdHlsZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5
bGUyMg0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ291
cmllciBOZXciOw0KCWNvbG9yOmJsYWNrOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0
eWxlOm5vcm1hbDsNCgl0ZXh0LWRlY29yYXRpb246bm9uZSBub25lO30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBh
Z2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6
ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0t
LT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxl
Ij4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+SGkgQ2FybG9zLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jmd0
Ow0KPC9zcGFuPk9uZSBhcHByb2FjaCBpcyB0byBhZGQgYSAzLmMpIHRvIHRoZSBsaXN0IHRoYXQg
Um9uIHNoYXJlZC4gSSB0aGluayB0aGVyZSBpcyBhbm90aGVyIHBvdGVudGlhbCBhcHByb2FjaCB0
byB5b3VyIGluaXRpYWwgY29tbWVudDo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPiZndDsgd2UgY291bGQgbm90ZSB0aGF0IGZvciBhIHR1bm5lbGluZyBwcm90b2NvbCAoR1JF
KSwgdGhpcyBpcyBlcXVpdmFsZW50IHRvIHRoZSByZWxheGF0aW9uIG9mIHRoZSBVRFAgY2hlY2tz
dW0gaW4gUkZDJm5ic3A7NjkzNSwgYW5kIGtlZXAgdGhlIGV4aXN0aW5nIHRleHQuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPkl04oCZcyBub3QgdGhhdCBzaW1wbGUgKEkgd2lzaCBpdCB3YXMpLiZuYnNwOyZu
YnNwOyBUaGUgc2hvcnQgc3VtbWFyeSBpcyBSRkMgNjkzNSBkb2VzIG5vdCBzZXQgYSBwcmVjZWRl
bnQgdGhhdCBjYW4ganVzdCBiZSBjaXRlZCAtIGluIHBhcnRpY3VsYXIgYSBzaW5nbGUgc2VudGVu
Y2UgcG9pbnRpbmcgdG8gUkZDDQogNjkzNSB0byBzYXkg4oCcdGhlcmVmb3JlIHRoaXMgaXMgb2vi
gJ0gaXMgbGlrZWx5IHRvIGdhcm5lciBtdWx0aXBsZSBJRVNHIERpc2N1c3MgcG9zaXRpb25zIGZv
ciBub3QgZXhwbGFpbmluZyB3aHksIHNvcnJ5IChMdWN5IGFuZCBJIGFyZSBpbiB0aGUgbWlkc3Qg
b2Ygd29ya2luZyB0aHJvdWdoIHRoaXMgZm9yIEdSRS1pbi1VRFApLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+Rm9yIHRoZSBsb25nIHZlcnNpb24sIHBsZWFzZSBzdGFydCB3aXRoIFNlY3Rpb24g
My4xIG9mIHRoZSBNUExTLWluLVVEUCBkcmFmdCAoaW4gQVVUSDQ4IGF0IHRoZSBSRkMgRWRpdG9y
KTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9InRleHQtaW5kZW50Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48YSBo
cmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW1wbHMtaW4tdWRwLTEx
I3NlY3Rpb24tMy4xIj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW1wbHMt
aW4tdWRwLTExI3NlY3Rpb24tMy4xPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+U2VjdGlv
biAzLjIgaXMgYWxzbyBhcHBsaWNhYmxlLCBidXQgbXVjaCBzaG9ydGVyIGFuZCByZWFzb25hYmx5
IHN0cmFpZ2h0Zm9yd2FyZCBieSBjb21wYXJpc29uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOmJsYWNrIj5UaGFua3MsPGJyPg0KLS1EYXZpZDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0
O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4g
MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBMdWN5IHlvbmcg
W21haWx0bzpsdWN5LnlvbmdAaHVhd2VpLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5
LCBNYXJjaCAzMSwgMjAxNSAzOjQ4IFBNPGJyPg0KPGI+VG86PC9iPiBMdWN5IHlvbmc7IENhcmxv
cyBQaWduYXRhcm8gKGNwaWduYXRhKTsgQmxhY2ssIERhdmlkPGJyPg0KPGI+Q2M6PC9iPiBSb25h
bGQgUC4gQm9uaWNhOyBpbnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzsgZHJhZnQtaWV0
Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9y
Zzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSRTogW0ludC1hcmVhXSBTdGFydCBvZiBXR0xDIGZvciBk
cmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBDYXJsb3Ms
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj5JIGFtIG5vdCBjbGVhciB3aGF0IHlvdSBwcm9wb3NlPGI+PGk+DQo8L2k+PC9i
PmhlcmUuIFVEUCBjaGVja3N1bSBpbmNsdWRlcyBJUCBoZWFkZXIsIEdSRSBjaGVja3N1bSBkb2Vz
IG5vdC4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5M
dWN5PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNC
NUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gQ2FybG9zIFBpZ25hdGFybyAoY3BpZ25hdGEpIFs8YSBo
cmVmPSJtYWlsdG86Y3BpZ25hdGFAY2lzY28uY29tIj5tYWlsdG86Y3BpZ25hdGFAY2lzY28uY29t
PC9hPl0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSAyOjAxIFBN
PGJyPg0KPGI+VG86PC9iPiBCbGFjaywgRGF2aWQ7IEx1Y3kgeW9uZzxicj4NCjxiPkNjOjwvYj4g
Um9uYWxkIFAuIEJvbmljYTsgPGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj5pbnQt
YXJlYUBpZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBp
ZXRmLm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZA
dG9vbHMuaWV0Zi5vcmciPg0KZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYu
b3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnIj4NCmludGFy
ZWEtY2hhaXJzQGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0ludC1hcmVh
XSBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSwgTHVjeSw8bzpwPjwvbzpw
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uZSBhcHByb2FjaCBpcyB0byBh
ZGQgYSAzLmMpIHRvIHRoZSBsaXN0IHRoYXQgUm9uIHNoYXJlZC4gSSB0aGluayB0aGVyZSBpcyBh
bm90aGVyIHBvdGVudGlhbCBhcHByb2FjaCB0byB5b3VyIGluaXRpYWwgY29tbWVudDogd2UgY291
bGQgbm90ZSB0aGF0IGZvciBhIHR1bm5lbGluZyBwcm90b2NvbCAoR1JFKSwgdGhpcyBpcyBlcXVp
dmFsZW50IHRvIHRoZSByZWxheGF0aW9uIG9mIHRoZSBVRFAgY2hlY2tzdW0NCiBpbiBSRkMmbmJz
cDs2OTM1LCBhbmQga2VlcCB0aGUgZXhpc3RpbmcgdGV4dC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RnJlZCwgUkZDIDI0NzMgZG9lcyBub3Qg
bWVudGlvbiBjaGVja3N1bXMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2FybG9zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CE03DB3D7B45C245BCA0D24327794936430EE6MX104CL02corpemcc_--


From nobody Wed Apr  1 00:25:02 2015
Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65C581ACCE4 for <ipv6@ietfa.amsl.com>; Tue, 31 Mar 2015 14:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tT3UDBOBEULC for <ipv6@ietfa.amsl.com>; Tue, 31 Mar 2015 14:07:39 -0700 (PDT)
Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com [209.85.213.180]) (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 57BC91A86F0 for <ipv6@ietf.org>; Tue, 31 Mar 2015 14:07:39 -0700 (PDT)
Received: by igbud6 with SMTP id ud6so30434080igb.1 for <ipv6@ietf.org>; Tue, 31 Mar 2015 14:07:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cc8WkFJxBRYq5LhIoUGvJmSCBc7spskmwfd/M5xxQws=; b=Ulo7VrhAUvPCHjy4Hzbj7ei7Pr1NTyuQx7py2egh4e7LXqjClIfTC2zRDtFzSmbLp1 BbZbwPBx7LlEj2gc/C274QNIaGkin0Zzy2Ha52mrdIbSiB0MhNrbQE3za4biyC3RB5ke hiJ8i6SCvuByAAVzjtnFDGI79onXVVV+ZxTyYW41aWCTU/pLLdbef3sSgQvw9Y9wwi8Z W5kL+hK/nHBtm0VY9qPteUXdbEtlOXQWp9rdx91We2+tbJHP5UG+HioFdiejq60Nqeil MgzePk9ZP3wbKRWJ0OVyJz8wG+WkqA9tTmBDwhjjW8KQ4nBnlHz8nYWubzs12QoLmII6 ZH0w==
X-Gm-Message-State: ALoCoQlJH7R3GyAj4HDbxcYttYQLrgdCwdokpMLQIDXWsCuH1WRj7X+XfMAtD/GmN6GmRUhw3Aqi
MIME-Version: 1.0
X-Received: by 10.107.128.213 with SMTP id k82mr12290461ioi.7.1427836058770; Tue, 31 Mar 2015 14:07:38 -0700 (PDT)
Received: by 10.107.149.15 with HTTP; Tue, 31 Mar 2015 14:07:38 -0700 (PDT)
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D57155648@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm> <2691CE0099834E4A9C5044EEC662BB9D57155648@dfweml701-chm>
Date: Tue, 31 Mar 2015 14:07:38 -0700
Message-ID: <CALx6S378jMsRDuor==X8GytrQvujW_UE1gGAMLXV6+YgCSDxJw@mail.gmail.com>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
From: Tom Herbert <tom@herbertland.com>
To: Lucy yong <lucy.yong@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fTM5tzSUZPZkiPi7kPUP8QXMCOY>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>, "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 21:07:41 -0000

On Tue, Mar 31, 2015 at 1:45 PM, Lucy yong <lucy.yong@huawei.com> wrote:
> Minor tweak. J
>
>
>
> From: Lucy yong
> Sent: Tuesday, March 31, 2015 3:42 PM
> To: Lucy yong; Ronald Bonica; Black, David; int-area@ietf.org; ipv6@ietf.=
org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> Hi Ron and Carlos,
>
>
>
> Here is the proposed text for the second paragraph in Section 4.1
>
>
>
> Because the IPv6 delivery header does not include a checksum of its own, =
it
> is subject to corruption.  Thus the use of gre in IPv6 must be in the cas=
e
> where an IPv6 delivery network can ensure packet corruption extremely
> unlikely and/or the case where GRE payload is able to tolerate the packet
> corruption.
>
Suggest to be "tolerate packet corruption or mis-delivery to the wrong addr=
ess."

Thanks,
Tom


>
>
> Thanks,
>
> Lucy
>
>
>
>
>
> From: Lucy yong
> Sent: Tuesday, March 31, 2015 2:23 PM
> To: 'Ronald Bonica'; Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> Hi Ron,
>
>
>
> 3c) may happen for a VPN or non-VPN case. The payload can be in non-IPv6
> space.  Is =E2=80=9COutcome 3c) is not acceptable, but it extremely unlik=
ely.=E2=80=9D for
> particular network/usage in your mind?
>
>
>
> Is the goal here to prove such corruption is acceptable or extreme unlike=
ly?
>
>
>
> Regards,
>
> Lucy
>
>
>
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald Bon=
ica
> Sent: Tuesday, March 31, 2015 1:43 PM
> To: Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> Resend=E2=80=A6
>
>
>
> From: Ronald Bonica
> Sent: Tuesday, March 31, 2015 2:23 PM
> To: 'Black, David'; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> David, Lucy,
>
>
>
> You are correct.  Maybe the following text will address the issue:
>
>
>
> OLD>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own, it is subject to corruption.  However, even if the delivery
>
>    header is corrupted, to likelihood of that corruption resulting in
>
>    misdelivery of the payload is extremely low.
>
> <OLD
>
>
>
> NEW>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own,  the destination address in the delivery header is subject to
>
>    corruption. If the destination address in the deliver header is
> corrupted,
>
>    the following outcomes are possible:
>
>
>
> 1)      The delivery packet is dropped because the new destination addres=
s
> is unreachable
>
> 2)      The delivery packet is dropped because the new destination addres=
s
> is reachable, but that node is not configured to process GRE delivery
> packets from the ingress
>
> 3)      The delivery packet is processed by a GRE egress other than that
> which was originally specified by the GRE ingress. Processing options are=
:
>
> a.       The payload packet is dropped because the payload destination is
> unreachable from the node that processed the delivery packet
>
> b.      The payload packet is delivered to its intended destination
>
> c.       The payload packet is erroneously delivered to a node other than
> its intended destination. The intended destination and the node to which =
the
> payload is actually delivered are numbered identically, but reside in
> different VPNs.
>
>
>
> Outcomes 1), 2), 3a) and 3b) are acceptable. Outcome 3c) is not acceptabl=
e,
> but it extremely unlikely. Because IPv6 address space is so large and so
> sparsely populated, outcome 1) is by far the most probable. Therefore, th=
e
> combined likelihood of all acceptable outcomes by far exceeds the likelih=
ood
> of the one unacceptable outcome.
>
>
>
> Furthermore, even if the payload is erroneously delivered to a node other
> than its intended destination, that node will discard the packet if the
> payload is also corrupted or if there are no applications waiting to cons=
ume
> the packet.
>
>
>
> <NEW
>
>
>
>                                    Ron
>
>
>
>
>
> From: Black, David [mailto:david.black@emc.com]
> Sent: Monday, March 30, 2015 7:48 PM
> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org;
> Black, David
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
>> Also, why would you object to 3b? The packet ends up at the right node,
>> just via an unexpected route.
>
>
>
> That assertion is based on the assumption that the payload destination
> address is worldwide unique.
>
>
>
> There are lots of counterexamples that void the assumption, e.g.,
> 10.0.0.0/8.
>
>
>
> Thanks,
> --David
>
>
>
>
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>


From nobody Wed Apr  1 00:25:04 2015
Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C46DF1B2AE0 for <ipv6@ietfa.amsl.com>; Tue, 31 Mar 2015 15:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4xwewlFOOpx for <ipv6@ietfa.amsl.com>; Tue, 31 Mar 2015 15:56:34 -0700 (PDT)
Received: from mail-ig0-f172.google.com (mail-ig0-f172.google.com [209.85.213.172]) (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 8A2821B2A2F for <ipv6@ietf.org>; Tue, 31 Mar 2015 15:56:34 -0700 (PDT)
Received: by igbud6 with SMTP id ud6so32893490igb.1 for <ipv6@ietf.org>; Tue, 31 Mar 2015 15:56:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4ZaA2E+hAr/iTTzSXbxiLNtF+oYNVNd09ZW01TaJJzU=; b=PONoJ8rShOFrGUdGy5LLeGann/T5ehuWp/1YtDRGwo2lZoz30JlhAErxC86bO3V7wu W6XfVfX6NCDgXMq/rI4Fi7ygsPKNeYVS+kOTNo0TEctswAt4d7yfSfGpbcYUwtvKs2qZ pnp7AkyDn1f7K5GO0FaneO+WW+QVcbkYsZixiz++7Ao1RtDu/zKV2jfF8Eb7/5hSPyKU 6nQBCiiGuaS2ft00wdfrHj15yzjvu02xRfNdhP9N1GVT7uyKyJrQMyn+MSVesm4vW5HC kU4Ov8o0HK8E2JEbMVEdsOsTl5LbKvzGmRHYKa7flk0yWb5u6GJChqyLLXWBsYjvZ/Q7 M5CQ==
X-Gm-Message-State: ALoCoQmF7Z7bw5RGLRLfhLNfqF2A/b+ud3WU6AEOpvFkuxXrxtq5x9YhPaJ1wbd0OU/SfGQ2ZvQr
MIME-Version: 1.0
X-Received: by 10.50.97.41 with SMTP id dx9mr7886578igb.1.1427842593868; Tue, 31 Mar 2015 15:56:33 -0700 (PDT)
Received: by 10.107.149.15 with HTTP; Tue, 31 Mar 2015 15:56:33 -0700 (PDT)
In-Reply-To: <BLUPR05MB433CBF724C50E3B6F631F8BAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715558D@dfweml701-chm> <BLUPR05MB433CBF724C50E3B6F631F8BAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
Date: Tue, 31 Mar 2015 15:56:33 -0700
Message-ID: <CALx6S35uMSTEAjkFZGKnzxN-n3avzwttVwJwGe0HfRC5k0n=zg@mail.gmail.com>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
From: Tom Herbert <tom@herbertland.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wOJEVNk-HxNwRLG4zvIbxKS-JE0>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "Black, David" <david.black@emc.com>, Lucy yong <lucy.yong@huawei.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 22:56:41 -0000

On Tue, Mar 31, 2015 at 3:04 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> Lucy, David,
>
>
>
> The proposed text says that outcome 3c) is unacceptable but highly unlike=
ly.
> For example, assume the following:
>
>
>
> -          That an IPv6 address is assigned to every milligram of matter =
on
> earth, including every drop of water. (2**95 IPv6 addresses are assigned)
>
> -          That every minute, the destination address on a delivery packe=
t
> is corrupted
>
> -          The pattern of corruption is random
>
>
>
> Every time a destination address is corrupted, the odds are 1 /
> 8,589,934,592 that the result will be an assigned address. This should
> happen one ever 16, 331 years.
>
>
>
> Now, assume that only 1% of those of those 2**95 IPv6 addresses are
> configured on devices that de-encapsulate GRE. In this case, outcomes 3a)=
,
> 3b) and 3c) will occur only once every 1,633,100 years!
>
>
>
> So, practically speaking, we don=E2=80=99t have much to worry about. But =
for the
> purposes of the pedantry, we may need to say that GRE over IPv6 is only
> practical when operators can deal with that risk.
>

You are assuming that failures will nicely follow a random
distribution, this is not always the case. For instance, we have had
issues in the past where a packet was queued to NIC on the host, but
then addresses we're overwritten due to loss of synchronization
between host and device as to rather packet was completed, so the
result would be mis-delivery if there is not checksum to catch that.

It is necessary prudence to assume that the risk of mis-delivery is
non-zero and that risk is probably greater in IPv6 than IPv4. An
operator should be aware of these risks and be able to evaluate the
ramifications of mis-delivery. Probably, in most cases the risk is in
fact inconsequential, but that really needs to be determined by the
operator-- of course if the operator's network is carrying nuclear
launch codes I would hope they worry about mis-delivery a little more
:-)

Tom


>
>
> David, what is the minimum text that we can import to satisfy the
> requirement.
>
>
>
>                                                              Ron
>
>
>
>
>
>
>
> From: Lucy yong [mailto:lucy.yong@huawei.com]
> Sent: Tuesday, March 31, 2015 3:21 PM
> To: Ronald Bonica; Black, David; int-area@ietf.org; ipv6@ietf.org
>
>
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> Hi Ron,
>
>
>
> 3c) may happen for a VPN or non-VPN case. The payload can be in non-IPv6
> space.  Is =E2=80=9COutcome 3c) is not acceptable, but it extremely unlik=
ely.=E2=80=9D for
> particular network/usage in your mind?
>
>
>
> Is the goal here to prove such corruption is acceptable or extreme unlike=
ly?
>
>
>
> Regards,
>
> Lucy
>
>
>
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald Bon=
ica
> Sent: Tuesday, March 31, 2015 1:43 PM
> To: Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> Resend=E2=80=A6
>
>
>
> From: Ronald Bonica
> Sent: Tuesday, March 31, 2015 2:23 PM
> To: 'Black, David'; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
> David, Lucy,
>
>
>
> You are correct.  Maybe the following text will address the issue:
>
>
>
> OLD>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own, it is subject to corruption.  However, even if the delivery
>
>    header is corrupted, to likelihood of that corruption resulting in
>
>    misdelivery of the payload is extremely low.
>
> <OLD
>
>
>
> NEW>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own,  the destination address in the delivery header is subject to
>
>    corruption. If the destination address in the deliver header is
> corrupted,
>
>    the following outcomes are possible:
>
>
>
> 1)      The delivery packet is dropped because the new destination addres=
s
> is unreachable
>
> 2)      The delivery packet is dropped because the new destination addres=
s
> is reachable, but that node is not configured to process GRE delivery
> packets from the ingress
>
> 3)      The delivery packet is processed by a GRE egress other than that
> which was originally specified by the GRE ingress. Processing options are=
:
>
> a.       The payload packet is dropped because the payload destination is
> unreachable from the node that processed the delivery packet
>
> b.      The payload packet is delivered to its intended destination
>
> c.       The payload packet is erroneously delivered to a node other than
> its intended destination. The intended destination and the node to which =
the
> payload is actually delivered are numbered identically, but reside in
> different VPNs.
>
>
>
> Outcomes 1), 2), 3a) and 3b) are acceptable. Outcome 3c) is not acceptabl=
e,
> but it extremely unlikely. Because IPv6 address space is so large and so
> sparsely populated, outcome 1) is by far the most probable. Therefore, th=
e
> combined likelihood of all acceptable outcomes by far exceeds the likelih=
ood
> of the one unacceptable outcome.
>
>
>
> Furthermore, even if the payload is erroneously delivered to a node other
> than its intended destination, that node will discard the packet if the
> payload is also corrupted or if there are no applications waiting to cons=
ume
> the packet.
>
>
>
> <NEW
>
>
>
>                                    Ron
>
>
>
>
>
> From: Black, David [mailto:david.black@emc.com]
> Sent: Monday, March 30, 2015 7:48 PM
> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org;
> Black, David
> Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
>
>
>> Also, why would you object to 3b? The packet ends up at the right node,
>> just via an unexpected route.
>
>
>
> That assertion is based on the assumption that the payload destination
> address is worldwide unique.
>
>
>
> There are lots of counterexamples that void the assumption, e.g.,
> 10.0.0.0/8.
>
>
>
> Thanks,
> --David
>
>
>
>
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>


From nobody Wed Apr  1 00:25:09 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461181A1BF6; Tue, 31 Mar 2015 16:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzOhcoyyIvND; Tue, 31 Mar 2015 16:23:22 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (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 27A871A1BBC; Tue, 31 Mar 2015 16:23:21 -0700 (PDT)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2VNNGHd009490 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2015 19:23:18 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t2VNNGHd009490
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427844198; bh=5szwayUwGaHGOGCS0AHCycBw/A8=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=U1zxquQqRELDdh98hwRmdgY4DUtOqEsFehaE1LTJcWimbWonn/rr9ApOp0A6f6l6n IeJ/Rzr2W3xHZct6OwyT33Pkq+0tGIXPrNmB2miojONY+9HU9X5tFiLCa9kEzeA4JG BN9ei0Q32G5HoX/gglDO1elvKLXOMhfHlW39826s=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t2VNNGHd009490
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 31 Mar 2015 19:21:13 -0400
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2VNMtXW026467 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 19:22:57 -0400
Received: from MXHUB201.corp.emc.com (10.253.68.27) by mxhub31.corp.emc.com (128.222.70.171) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 31 Mar 2015 19:22:55 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB201.corp.emc.com ([10.253.68.27]) with mapi id 14.03.0224.002; Tue, 31 Mar 2015 19:22:55 -0400
From: "Black, David" <david.black@emc.com>
To: Ronald Bonica <rbonica@juniper.net>
Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYAACwrJwAA2QUoAACDTX0A==
Date: Tue, 31 Mar 2015 23:22:54 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949364312AD@MX104CL02.corp.emc.com>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715558D@dfweml701-chm> <BLUPR05MB433CBF724C50E3B6F631F8BAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <CALx6S35uMSTEAjkFZGKnzxN-n3avzwttVwJwGe0HfRC5k0n=zg@mail.gmail.com>
In-Reply-To: <CALx6S35uMSTEAjkFZGKnzxN-n3avzwttVwJwGe0HfRC5k0n=zg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4gLCsg1lx2D-2WGz3Foe1l_fmuI>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 23:23:25 -0000

Um9uLA0KDQpUb20gY29tbWVudHM6DQo+IFlvdSBhcmUgYXNzdW1pbmcgdGhhdCBmYWlsdXJlcyB3
aWxsIG5pY2VseSBmb2xsb3cgYSByYW5kb20NCj4gZGlzdHJpYnV0aW9uLCB0aGlzIGlzIG5vdCBh
bHdheXMgdGhlIGNhc2UNCg0KKzEsIGFuZCBsaWtld2lzZSwgSVB2NiBhZGRyZXNzZXMgYXJlIGFs
c28gbm90IHVuaWZvcm1seSByYW5kb21seQ0KZGlzdHJpYnV0ZWQgaW4gcHJhY3RpY2UgOy0pLiAg
TmljZSB0cnksIHRob3VnaCAuLi4NCg0KWW91IGFza2VkOg0KPiA+IERhdmlkLCB3aGF0IGlzIHRo
ZSBtaW5pbXVtIHRleHQgdGhhdCB3ZSBjYW4gaW1wb3J0IHRvIHNhdGlzZnkgdGhlDQo+ID4gcmVx
dWlyZW1lbnQuDQoNCkknbSBub3Qgc3VyZSBJIGNhbiBkaWN0YXRlIHRoZSB0ZXh0LCBidXQgbGV0
IG1lIHN1Z2dlc3Qgd2hlcmUgdG8gImRpZy4iDQoNCkEgbW90aXZhdGluZyBvYnNlcnZhdGlvbiBp
cyB0aGF0IGlmIHRoZSBsaWtlbGlob29kIG9mIGRlc3RpbmF0aW9uDQpJUHY2IGFkZHJlc3MgY29y
cnVwdGlvbiBjYXVzaW5nIG1pc2RlbGl2ZXJ5IGlzIHZlcnkgc21hbGwsIHRoZW4gdGhlDQpsaWtl
bGlob29kIG9mIHRoYXQgY29ycnVwdGlvbiBpbiBjb21iaW5hdGlvbiB3aXRoIGFuIG9mZnNldHRp
bmcNCmNvcnJ1cHRpb24gaW4gdGhlIHNvdXJjZSBJUHY2IGFkZHJlc3MgaXMgc29tZXRoaW5nIGxp
a2UgKHZlcnkgc21hbGwpKioyLA0KaS5lLiwgdHJ1bHkgbWluaXNjdWxlLiAgSGVuY2UsIGlmIG9u
ZSBjYW4gcGFpciBvZmYgdHVubmVsIHNvdXJjZSBhbmQNCmRlc3RpbmF0aW9uIElQdjYgYWRkcmVz
c2VzIHNvIHRoYXQgYm90aCBoYXZlIHRvIGJlIGNvcnJ1cHRlZCBmb3INCm1pc2RlbGl2ZXJ5IHRv
IG9jY3VyLCB0aGVuIG1pc2RlbGl2ZXJ5IHNob3VsZCBiZSBzdWZmaWNpZW50bHkgdW5saWtlbHku
DQooTkI6IGEgbnVtYmVyIG9mIHdvcmRzIGluIHRoaXMgcGFyYWdyYXBoIGFyZSAiaGFuZCB3YXZl
cyIgLSB0aGF0J3MNCmRlbGliZXJhdGUpLg0KDQpTbywgd2hhdCBpcyBpdCBzYWZlIHRvIHNheSAo
d2l0aG91dCBicmVha2luZyBydW5uaW5nIGNvZGUpIG9uIHRoZQ0Kc3ViamVjdHMgb2Y6DQoJLSBH
UkUgZW5jYXBzdWxhdG9yIHVzZSBvZiBzZXBhcmF0ZSBJUHY2IHNvdXJjZSBhZGRyZXNzZXMgZm9y
DQoJCXNlcGFyYXRlIHR1bm5lbHM/IChOQjogInR1bm5lbHMiIG5vdCAiZGVzdGluYXRpb25zIiB0
bw0KCQlhbGxvdyBmb3IgbXVsdGljYXN0KS4NCgktIEdSRSBkZWNhcHN1bGF0b3IgY2hlY2sgb2Yg
SVB2NiBzb3VyY2UgYWRkcmVzcz8NCg0KRm9yIE1QTFMvVURQLCB0aGUgYW5zd2VycyB3ZXJlIHZl
cnNpb25zIG9mIFNIT1VMRCBhbmQgTVVTVCBpbiB0aGF0DQpvcmRlciAoc2VlIGl0ZW1zIGMgYW5k
IGQgaW4gU2VjdGlvbiAzLjEgb2YgZHJhZnQtaWV0Zi1tcGxzLWluLXVkcCkuDQoNCk9UT0gsIEdS
RSAicnVubmluZyBjb2RlIiBpcyBhIGNydWNpYWwgY29uc2lkZXJhdGlvbiBoZXJlIGFuZCB0aGUN
CmNvbW1lbnQgdGhhdCAiR1JFIG92ZXIgSVB2NiBpcyBvbmx5IHByYWN0aWNhbCB3aGVuIG9wZXJh
dG9ycyBjYW4NCmRlYWwgd2l0aCB0aGF0IHJpc2siIGlzIGFsc28gdXNlZnVsLCBJTUhPLg0KDQpU
aGFua3MsDQotLURhdmlkDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9t
OiBUb20gSGVyYmVydCBbbWFpbHRvOnRvbUBoZXJiZXJ0bGFuZC5jb21dDQo+IFNlbnQ6IFR1ZXNk
YXksIE1hcmNoIDMxLCAyMDE1IDY6NTcgUE0NCj4gVG86IFJvbmFsZCBCb25pY2ENCj4gQ2M6IEx1
Y3kgeW9uZzsgQmxhY2ssIERhdmlkOyBpbnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzsg
ZHJhZnQtaWV0Zi0NCj4gaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzsgaW50YXJlYS1j
aGFpcnNAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtJbnQtYXJlYV0gU3RhcnQgb2YgV0dMQyBm
b3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQo+IA0KPiBPbiBUdWUsIE1hciAzMSwgMjAx
NSBhdCAzOjA0IFBNLCBSb25hbGQgQm9uaWNhIDxyYm9uaWNhQGp1bmlwZXIubmV0PiB3cm90ZToN
Cj4gPiBMdWN5LCBEYXZpZCwNCj4gPg0KPiA+DQo+ID4NCj4gPiBUaGUgcHJvcG9zZWQgdGV4dCBz
YXlzIHRoYXQgb3V0Y29tZSAzYykgaXMgdW5hY2NlcHRhYmxlIGJ1dCBoaWdobHkgdW5saWtlbHku
DQo+ID4gRm9yIGV4YW1wbGUsIGFzc3VtZSB0aGUgZm9sbG93aW5nOg0KPiA+DQo+ID4NCj4gPg0K
PiA+IC0gICAgICAgICAgVGhhdCBhbiBJUHY2IGFkZHJlc3MgaXMgYXNzaWduZWQgdG8gZXZlcnkg
bWlsbGlncmFtIG9mIG1hdHRlciBvbg0KPiA+IGVhcnRoLCBpbmNsdWRpbmcgZXZlcnkgZHJvcCBv
ZiB3YXRlci4gKDIqKjk1IElQdjYgYWRkcmVzc2VzIGFyZSBhc3NpZ25lZCkNCj4gPg0KPiA+IC0g
ICAgICAgICAgVGhhdCBldmVyeSBtaW51dGUsIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIG9uIGEg
ZGVsaXZlcnkgcGFja2V0DQo+ID4gaXMgY29ycnVwdGVkDQo+ID4NCj4gPiAtICAgICAgICAgIFRo
ZSBwYXR0ZXJuIG9mIGNvcnJ1cHRpb24gaXMgcmFuZG9tDQo+ID4NCj4gPg0KPiA+DQo+ID4gRXZl
cnkgdGltZSBhIGRlc3RpbmF0aW9uIGFkZHJlc3MgaXMgY29ycnVwdGVkLCB0aGUgb2RkcyBhcmUg
MSAvDQo+ID4gOCw1ODksOTM0LDU5MiB0aGF0IHRoZSByZXN1bHQgd2lsbCBiZSBhbiBhc3NpZ25l
ZCBhZGRyZXNzLiBUaGlzIHNob3VsZA0KPiA+IGhhcHBlbiBvbmUgZXZlciAxNiwgMzMxIHllYXJz
Lg0KPiA+DQo+ID4NCj4gPg0KPiA+IE5vdywgYXNzdW1lIHRoYXQgb25seSAxJSBvZiB0aG9zZSBv
ZiB0aG9zZSAyKio5NSBJUHY2IGFkZHJlc3NlcyBhcmUNCj4gPiBjb25maWd1cmVkIG9uIGRldmlj
ZXMgdGhhdCBkZS1lbmNhcHN1bGF0ZSBHUkUuIEluIHRoaXMgY2FzZSwgb3V0Y29tZXMgM2EpLA0K
PiA+IDNiKSBhbmQgM2MpIHdpbGwgb2NjdXIgb25seSBvbmNlIGV2ZXJ5IDEsNjMzLDEwMCB5ZWFy
cyENCj4gPg0KPiA+DQo+ID4NCj4gPiBTbywgcHJhY3RpY2FsbHkgc3BlYWtpbmcsIHdlIGRvbuKA
mXQgaGF2ZSBtdWNoIHRvIHdvcnJ5IGFib3V0LiBCdXQgZm9yIHRoZQ0KPiA+IHB1cnBvc2VzIG9m
IHRoZSBwZWRhbnRyeSwgd2UgbWF5IG5lZWQgdG8gc2F5IHRoYXQgR1JFIG92ZXIgSVB2NiBpcyBv
bmx5DQo+ID4gcHJhY3RpY2FsIHdoZW4gb3BlcmF0b3JzIGNhbiBkZWFsIHdpdGggdGhhdCByaXNr
Lg0KPiA+DQo+IA0KPiBZb3UgYXJlIGFzc3VtaW5nIHRoYXQgZmFpbHVyZXMgd2lsbCBuaWNlbHkg
Zm9sbG93IGEgcmFuZG9tDQo+IGRpc3RyaWJ1dGlvbiwgdGhpcyBpcyBub3QgYWx3YXlzIHRoZSBj
YXNlLiBGb3IgaW5zdGFuY2UsIHdlIGhhdmUgaGFkDQo+IGlzc3VlcyBpbiB0aGUgcGFzdCB3aGVy
ZSBhIHBhY2tldCB3YXMgcXVldWVkIHRvIE5JQyBvbiB0aGUgaG9zdCwgYnV0DQo+IHRoZW4gYWRk
cmVzc2VzIHdlJ3JlIG92ZXJ3cml0dGVuIGR1ZSB0byBsb3NzIG9mIHN5bmNocm9uaXphdGlvbg0K
PiBiZXR3ZWVuIGhvc3QgYW5kIGRldmljZSBhcyB0byByYXRoZXIgcGFja2V0IHdhcyBjb21wbGV0
ZWQsIHNvIHRoZQ0KPiByZXN1bHQgd291bGQgYmUgbWlzLWRlbGl2ZXJ5IGlmIHRoZXJlIGlzIG5v
dCBjaGVja3N1bSB0byBjYXRjaCB0aGF0Lg0KPiANCj4gSXQgaXMgbmVjZXNzYXJ5IHBydWRlbmNl
IHRvIGFzc3VtZSB0aGF0IHRoZSByaXNrIG9mIG1pcy1kZWxpdmVyeSBpcw0KPiBub24temVybyBh
bmQgdGhhdCByaXNrIGlzIHByb2JhYmx5IGdyZWF0ZXIgaW4gSVB2NiB0aGFuIElQdjQuIEFuDQo+
IG9wZXJhdG9yIHNob3VsZCBiZSBhd2FyZSBvZiB0aGVzZSByaXNrcyBhbmQgYmUgYWJsZSB0byBl
dmFsdWF0ZSB0aGUNCj4gcmFtaWZpY2F0aW9ucyBvZiBtaXMtZGVsaXZlcnkuIFByb2JhYmx5LCBp
biBtb3N0IGNhc2VzIHRoZSByaXNrIGlzIGluDQo+IGZhY3QgaW5jb25zZXF1ZW50aWFsLCBidXQg
dGhhdCByZWFsbHkgbmVlZHMgdG8gYmUgZGV0ZXJtaW5lZCBieSB0aGUNCj4gb3BlcmF0b3ItLSBv
ZiBjb3Vyc2UgaWYgdGhlIG9wZXJhdG9yJ3MgbmV0d29yayBpcyBjYXJyeWluZyBudWNsZWFyDQo+
IGxhdW5jaCBjb2RlcyBJIHdvdWxkIGhvcGUgdGhleSB3b3JyeSBhYm91dCBtaXMtZGVsaXZlcnkg
YSBsaXR0bGUgbW9yZQ0KPiA6LSkNCj4gDQo+IFRvbQ0KPiANCj4gDQo+ID4NCj4gPg0KPiA+IERh
dmlkLCB3aGF0IGlzIHRoZSBtaW5pbXVtIHRleHQgdGhhdCB3ZSBjYW4gaW1wb3J0IHRvIHNhdGlz
ZnkgdGhlDQo+ID4gcmVxdWlyZW1lbnQuDQo+ID4NCj4gPg0KPiA+DQo+ID4gICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFJvbg0KPiA+
DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4gRnJvbTogTHVjeSB5b25nIFttYWls
dG86bHVjeS55b25nQGh1YXdlaS5jb21dDQo+ID4gU2VudDogVHVlc2RheSwgTWFyY2ggMzEsIDIw
MTUgMzoyMSBQTQ0KPiA+IFRvOiBSb25hbGQgQm9uaWNhOyBCbGFjaywgRGF2aWQ7IGludC1hcmVh
QGlldGYub3JnOyBpcHY2QGlldGYub3JnDQo+ID4NCj4gPg0KPiA+IENjOiBkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc7IGludGFyZWEtY2hhaXJzQGlldGYub3JnDQo+
ID4gU3ViamVjdDogUkU6IFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2Ng0KPiA+DQo+ID4NCj4gPg0KPiA+IEhpIFJvbiwNCj4gPg0KPiA+DQo+ID4NCj4gPiAzYykg
bWF5IGhhcHBlbiBmb3IgYSBWUE4gb3Igbm9uLVZQTiBjYXNlLiBUaGUgcGF5bG9hZCBjYW4gYmUg
aW4gbm9uLUlQdjYNCj4gPiBzcGFjZS4gIElzIOKAnE91dGNvbWUgM2MpIGlzIG5vdCBhY2NlcHRh
YmxlLCBidXQgaXQgZXh0cmVtZWx5IHVubGlrZWx5LuKAnSBmb3INCj4gPiBwYXJ0aWN1bGFyIG5l
dHdvcmsvdXNhZ2UgaW4geW91ciBtaW5kPw0KPiA+DQo+ID4NCj4gPg0KPiA+IElzIHRoZSBnb2Fs
IGhlcmUgdG8gcHJvdmUgc3VjaCBjb3JydXB0aW9uIGlzIGFjY2VwdGFibGUgb3IgZXh0cmVtZSB1
bmxpa2VseT8NCj4gPg0KPiA+DQo+ID4NCj4gPiBSZWdhcmRzLA0KPiA+DQo+ID4gTHVjeQ0KPiA+
DQo+ID4NCj4gPg0KPiA+IEZyb206IEludC1hcmVhIFttYWlsdG86aW50LWFyZWEtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mIFJvbmFsZCBCb25pY2ENCj4gPiBTZW50OiBUdWVzZGF5LCBN
YXJjaCAzMSwgMjAxNSAxOjQzIFBNDQo+ID4gVG86IEJsYWNrLCBEYXZpZDsgaW50LWFyZWFAaWV0
Zi5vcmc7IGlwdjZAaWV0Zi5vcmcNCj4gPiBDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2
QHRvb2xzLmlldGYub3JnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFJl
OiBbSW50LWFyZWFdIFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2
Ng0KPiA+DQo+ID4NCj4gPg0KPiA+IFJlc2VuZOKApg0KPiA+DQo+ID4NCj4gPg0KPiA+IEZyb206
IFJvbmFsZCBCb25pY2ENCj4gPiBTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSAyOjIzIFBN
DQo+ID4gVG86ICdCbGFjaywgRGF2aWQnOyBpbnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9y
Zw0KPiA+IENjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc7IGlu
dGFyZWEtY2hhaXJzQGlldGYub3JnDQo+ID4gU3ViamVjdDogUkU6IFN0YXJ0IG9mIFdHTEMgZm9y
IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KPiA+DQo+ID4NCj4gPg0KPiA+IERhdmlkLCBM
dWN5LA0KPiA+DQo+ID4NCj4gPg0KPiA+IFlvdSBhcmUgY29ycmVjdC4gIE1heWJlIHRoZSBmb2xs
b3dpbmcgdGV4dCB3aWxsIGFkZHJlc3MgdGhlIGlzc3VlOg0KPiA+DQo+ID4NCj4gPg0KPiA+IE9M
RD4NCj4gPg0KPiA+ICAgIEJlY2F1c2UgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90
IGluY2x1ZGUgYSBjaGVja3N1bSBvZiBpdHMNCj4gPg0KPiA+ICAgIG93biwgaXQgaXMgc3ViamVj
dCB0byBjb3JydXB0aW9uLiAgSG93ZXZlciwgZXZlbiBpZiB0aGUgZGVsaXZlcnkNCj4gPg0KPiA+
ICAgIGhlYWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2VsaWhvb2Qgb2YgdGhhdCBjb3JydXB0aW9u
IHJlc3VsdGluZyBpbg0KPiA+DQo+ID4gICAgbWlzZGVsaXZlcnkgb2YgdGhlIHBheWxvYWQgaXMg
ZXh0cmVtZWx5IGxvdy4NCj4gPg0KPiA+IDxPTEQNCj4gPg0KPiA+DQo+ID4NCj4gPiBORVc+DQo+
ID4NCj4gPiAgICBCZWNhdXNlIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNs
dWRlIGEgY2hlY2tzdW0gb2YgaXRzDQo+ID4NCj4gPiAgICBvd24sICB0aGUgZGVzdGluYXRpb24g
YWRkcmVzcyBpbiB0aGUgZGVsaXZlcnkgaGVhZGVyIGlzIHN1YmplY3QgdG8NCj4gPg0KPiA+ICAg
IGNvcnJ1cHRpb24uIElmIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBkZWxpdmVyIGhl
YWRlciBpcw0KPiA+IGNvcnJ1cHRlZCwNCj4gPg0KPiA+ICAgIHRoZSBmb2xsb3dpbmcgb3V0Y29t
ZXMgYXJlIHBvc3NpYmxlOg0KPiA+DQo+ID4NCj4gPg0KPiA+IDEpICAgICAgVGhlIGRlbGl2ZXJ5
IHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5hdGlvbiBhZGRyZXNzDQo+
ID4gaXMgdW5yZWFjaGFibGUNCj4gPg0KPiA+IDIpICAgICAgVGhlIGRlbGl2ZXJ5IHBhY2tldCBp
cyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5hdGlvbiBhZGRyZXNzDQo+ID4gaXMgcmVh
Y2hhYmxlLCBidXQgdGhhdCBub2RlIGlzIG5vdCBjb25maWd1cmVkIHRvIHByb2Nlc3MgR1JFIGRl
bGl2ZXJ5DQo+ID4gcGFja2V0cyBmcm9tIHRoZSBpbmdyZXNzDQo+ID4NCj4gPiAzKSAgICAgIFRo
ZSBkZWxpdmVyeSBwYWNrZXQgaXMgcHJvY2Vzc2VkIGJ5IGEgR1JFIGVncmVzcyBvdGhlciB0aGFu
IHRoYXQNCj4gPiB3aGljaCB3YXMgb3JpZ2luYWxseSBzcGVjaWZpZWQgYnkgdGhlIEdSRSBpbmdy
ZXNzLiBQcm9jZXNzaW5nIG9wdGlvbnMgYXJlOg0KPiA+DQo+ID4gYS4gICAgICAgVGhlIHBheWxv
YWQgcGFja2V0IGlzIGRyb3BwZWQgYmVjYXVzZSB0aGUgcGF5bG9hZCBkZXN0aW5hdGlvbiBpcw0K
PiA+IHVucmVhY2hhYmxlIGZyb20gdGhlIG5vZGUgdGhhdCBwcm9jZXNzZWQgdGhlIGRlbGl2ZXJ5
IHBhY2tldA0KPiA+DQo+ID4gYi4gICAgICBUaGUgcGF5bG9hZCBwYWNrZXQgaXMgZGVsaXZlcmVk
IHRvIGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbg0KPiA+DQo+ID4gYy4gICAgICAgVGhlIHBheWxv
YWQgcGFja2V0IGlzIGVycm9uZW91c2x5IGRlbGl2ZXJlZCB0byBhIG5vZGUgb3RoZXIgdGhhbg0K
PiA+IGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbi4gVGhlIGludGVuZGVkIGRlc3RpbmF0aW9uIGFu
ZCB0aGUgbm9kZSB0byB3aGljaCB0aGUNCj4gPiBwYXlsb2FkIGlzIGFjdHVhbGx5IGRlbGl2ZXJl
ZCBhcmUgbnVtYmVyZWQgaWRlbnRpY2FsbHksIGJ1dCByZXNpZGUgaW4NCj4gPiBkaWZmZXJlbnQg
VlBOcy4NCj4gPg0KPiA+DQo+ID4NCj4gPiBPdXRjb21lcyAxKSwgMiksIDNhKSBhbmQgM2IpIGFy
ZSBhY2NlcHRhYmxlLiBPdXRjb21lIDNjKSBpcyBub3QgYWNjZXB0YWJsZSwNCj4gPiBidXQgaXQg
ZXh0cmVtZWx5IHVubGlrZWx5LiBCZWNhdXNlIElQdjYgYWRkcmVzcyBzcGFjZSBpcyBzbyBsYXJn
ZSBhbmQgc28NCj4gPiBzcGFyc2VseSBwb3B1bGF0ZWQsIG91dGNvbWUgMSkgaXMgYnkgZmFyIHRo
ZSBtb3N0IHByb2JhYmxlLiBUaGVyZWZvcmUsIHRoZQ0KPiA+IGNvbWJpbmVkIGxpa2VsaWhvb2Qg
b2YgYWxsIGFjY2VwdGFibGUgb3V0Y29tZXMgYnkgZmFyIGV4Y2VlZHMgdGhlIGxpa2VsaWhvb2QN
Cj4gPiBvZiB0aGUgb25lIHVuYWNjZXB0YWJsZSBvdXRjb21lLg0KPiA+DQo+ID4NCj4gPg0KPiA+
IEZ1cnRoZXJtb3JlLCBldmVuIGlmIHRoZSBwYXlsb2FkIGlzIGVycm9uZW91c2x5IGRlbGl2ZXJl
ZCB0byBhIG5vZGUgb3RoZXINCj4gPiB0aGFuIGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbiwgdGhh
dCBub2RlIHdpbGwgZGlzY2FyZCB0aGUgcGFja2V0IGlmIHRoZQ0KPiA+IHBheWxvYWQgaXMgYWxz
byBjb3JydXB0ZWQgb3IgaWYgdGhlcmUgYXJlIG5vIGFwcGxpY2F0aW9ucyB3YWl0aW5nIHRvIGNv
bnN1bWUNCj4gPiB0aGUgcGFja2V0Lg0KPiA+DQo+ID4NCj4gPg0KPiA+IDxORVcNCj4gPg0KPiA+
DQo+ID4NCj4gPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFJvbg0KPiA+DQo+
ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiBGcm9tOiBCbGFjaywgRGF2aWQgW21haWx0bzpkYXZpZC5i
bGFja0BlbWMuY29tXQ0KPiA+IFNlbnQ6IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNzo0OCBQTQ0K
PiA+IFRvOiBSb25hbGQgQm9uaWNhOyBpbnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZw0K
PiA+IENjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc7IGludGFy
ZWEtY2hhaXJzQGlldGYub3JnOw0KPiA+IEJsYWNrLCBEYXZpZA0KPiA+IFN1YmplY3Q6IFJFOiBT
dGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCj4gPg0KPiA+DQo+
ID4NCj4gPj4gQWxzbywgd2h5IHdvdWxkIHlvdSBvYmplY3QgdG8gM2I/IFRoZSBwYWNrZXQgZW5k
cyB1cCBhdCB0aGUgcmlnaHQgbm9kZSwNCj4gPj4ganVzdCB2aWEgYW4gdW5leHBlY3RlZCByb3V0
ZS4NCj4gPg0KPiA+DQo+ID4NCj4gPiBUaGF0IGFzc2VydGlvbiBpcyBiYXNlZCBvbiB0aGUgYXNz
dW1wdGlvbiB0aGF0IHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uDQo+ID4gYWRkcmVzcyBpcyB3b3Js
ZHdpZGUgdW5pcXVlLg0KPiA+DQo+ID4NCj4gPg0KPiA+IFRoZXJlIGFyZSBsb3RzIG9mIGNvdW50
ZXJleGFtcGxlcyB0aGF0IHZvaWQgdGhlIGFzc3VtcHRpb24sIGUuZy4sDQo+ID4gMTAuMC4wLjAv
OC4NCj4gPg0KPiA+DQo+ID4NCj4gPiBUaGFua3MsDQo+ID4gLS1EYXZpZA0KPiA+DQo+ID4NCj4g
Pg0KPiA+DQo+ID4NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+ID4gSW50LWFyZWEgbWFpbGluZyBsaXN0DQo+ID4gSW50LWFyZWFAaWV0
Zi5vcmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ludC1hcmVh
DQo+ID4NCg==


From nobody Wed Apr  1 00:25:46 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529241A906E; Tue, 31 Mar 2015 12:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KC6XMoJ4aUYN; Tue, 31 Mar 2015 12:07:36 -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 8A5E31A01F6; Tue, 31 Mar 2015 12:07:33 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQX48045; Tue, 31 Mar 2015 19:07:32 +0000 (GMT)
Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 31 Mar 2015 20:07:31 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml706-chm ([10.193.5.225]) with mapi id 14.03.0158.001; Tue, 31 Mar 2015 12:07:18 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "Black, David" <david.black@emc.com>
Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAy+K+AAApXc7A=
Date: Tue, 31 Mar 2015 19:07:18 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57155576@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <78DCD4FF-4030-4386-A0CA-7AA5FF1C2E4A@cisco.com>
In-Reply-To: <78DCD4FF-4030-4386-A0CA-7AA5FF1C2E4A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.181]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57155576dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/RRa7F4U3WSXivZz96MA5rrWecr4>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 19:07:39 -0000

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

SGkgQ2FybG9zLA0KDQpJIGFtIG5vdCBjbGVhciB3aGF0IHlvdSBwcm9wb3NlLiBVRFAgY2hlY2tz
dW0gaW5jbHVkZXMgSVAgaGVhZGVyLiBHUkUgZG9lcyBub3QuDQoNCkx1Y3kNCg0KRnJvbTogQ2Fy
bG9zIFBpZ25hdGFybyAoY3BpZ25hdGEpIFttYWlsdG86Y3BpZ25hdGFAY2lzY28uY29tXQ0KU2Vu
dDogVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgMjowMSBQTQ0KVG86IEJsYWNrLCBEYXZpZDsgTHVj
eSB5b25nDQpDYzogUm9uYWxkIFAuIEJvbmljYTsgaW50LWFyZWFAaWV0Zi5vcmc7IGlwdjZAaWV0
Zi5vcmc7IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzsgaW50YXJl
YS1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbSW50LWFyZWFdIFN0YXJ0IG9mIFdHTEMg
Zm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KDQpIaSwgTHVjeSwNCg0KT25lIGFwcHJv
YWNoIGlzIHRvIGFkZCBhIDMuYykgdG8gdGhlIGxpc3QgdGhhdCBSb24gc2hhcmVkLiBJIHRoaW5r
IHRoZXJlIGlzIGFub3RoZXIgcG90ZW50aWFsIGFwcHJvYWNoIHRvIHlvdXIgaW5pdGlhbCBjb21t
ZW50OiB3ZSBjb3VsZCBub3RlIHRoYXQgZm9yIGEgdHVubmVsaW5nIHByb3RvY29sIChHUkUpLCB0
aGlzIGlzIGVxdWl2YWxlbnQgdG8gdGhlIHJlbGF4YXRpb24gb2YgdGhlIFVEUCBjaGVja3N1bSBp
biBSRkMgNjkzNSwgYW5kIGtlZXAgdGhlIGV4aXN0aW5nIHRleHQuDQoNCkZyZWQsIFJGQyAyNDcz
IGRvZXMgbm90IG1lbnRpb24gY2hlY2tzdW1zLg0KDQpUaGFua3MsDQoNCkNhcmxvcy4NCg0KT24g
TWFyIDMwLCAyMDE1LCBhdCA3OjQ3IFBNLCBCbGFjaywgRGF2aWQgPGRhdmlkLmJsYWNrQGVtYy5j
b208bWFpbHRvOmRhdmlkLmJsYWNrQGVtYy5jb20+PiB3cm90ZToNCg0KPiBBbHNvLCB3aHkgd291
bGQgeW91IG9iamVjdCB0byAzYj8gVGhlIHBhY2tldCBlbmRzIHVwIGF0IHRoZSByaWdodCBub2Rl
LCBqdXN0IHZpYSBhbiB1bmV4cGVjdGVkIHJvdXRlLg0KDQpUaGF0IGFzc2VydGlvbiBpcyBiYXNl
ZCBvbiB0aGUgYXNzdW1wdGlvbiB0aGF0IHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uIGFkZHJlc3Mg
aXMgd29ybGR3aWRlIHVuaXF1ZS4NCg0KVGhlcmUgYXJlIGxvdHMgb2YgY291bnRlcmV4YW1wbGVz
IHRoYXQgdm9pZCB0aGUgYXNzdW1wdGlvbiwgZS5nLiwgMTAuMC4wLjAvOC4NCg0KVGhhbmtzLA0K
LS1EYXZpZA0KDQpGcm9tOiBMdWN5IHlvbmcgW21haWx0bzpsdWN5LnlvbmdAaHVhd2VpLmNvbV0N
ClNlbnQ6IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNjozMSBQTQ0KVG86IFJvbmFsZCBCb25pY2E7
IFp1bmlnYSwgSnVhbiBDYXJsb3M7IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBp
ZXRmLm9yZz47IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+OyBCbGFjaywgRGF2
aWQNCkNjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFpbHRv
OmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEtY2hh
aXJzQGlldGYub3JnPG1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJF
OiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KSGkgUm9u
LA0KDQozYikgaXMgdGhlIGNvbmNlcm4uIEdSRSBwYXlsb2FkIG1heSBiZSBub24tSVAgdHlwZS4g
SWYgYSBncmUtaW4taXB2NiB0dW5uZWwgaXMgdXNlZCBmb3IgbXV4IG9mIGRpZmZlcmVudCBwYXls
b2FkIHR5cGVzLCB0aGUgb3V0Y29tZSBtYXkgYmUgdW5rbm93biBhbmQgY2FuIGJlIHVuYWNjZXB0
YWJsZSB1cG9uIElQIGFkZHJlc3MgYW5kL29yIEdSRSBoZWFkZXIgYXJlIGNvcnJ1cHRlZC4NCg0K
THVjeQ0KDQoNCg0KRnJvbTogUm9uYWxkIEJvbmljYSBbbWFpbHRvOnJib25pY2FAanVuaXBlci5u
ZXRdDQpTZW50OiBNb25kYXksIE1hcmNoIDMwLCAyMDE1IDU6MTQgUE0NClRvOiBMdWN5IHlvbmc7
IFp1bmlnYSwgSnVhbiBDYXJsb3M7IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBp
ZXRmLm9yZz47IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+OyBCbGFjaywgRGF2
aWQNCkNjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFpbHRv
OmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEtY2hh
aXJzQGlldGYub3JnPG1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJF
OiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KTHVjeSwN
Cg0KV2h5IHdvdWxkIHlvdSBvYmplY3QgdG8gM2E/IERyb3BwaW5nIHRoZSBwYWNrZXQgaXMgdGhl
IHByZWZlcnJlZCBiZWhhdmlvcj8NCg0KQWxzbywgd2h5IHdvdWxkIHlvdSBvYmplY3QgdG8gM2I/
IFRoZSBwYWNrZXQgZW5kcyB1cCBhdCB0aGUgcmlnaHQgbm9kZSwganVzdCB2aWEgYW4gdW5leHBl
Y3RlZCByb3V0ZS4gUmVjYWxsIHRoYXQgdGhlIGRlc3RpbmF0aW9uIGFkZHJlc3MgaW4gdGhlIHBh
eWxvYWQgaGVhZGVyIGlzIHByb3RlY3RlZCBieSB0aGUgVURQL1RDUCBjaGVja3N1bS4NCg0KQXJl
IHlvdSB0aGlua2luZyB0aGF0IHRoZXJlIG1pZ2h0IGJlIGEgM2MpPw0KDQogICAgICAgICAgICAg
ICAgICAgICAgUm9uDQoNCg0KRnJvbTogTHVjeSB5b25nIFttYWlsdG86bHVjeS55b25nQGh1YXdl
aS5jb21dDQpTZW50OiBNb25kYXksIE1hcmNoIDMwLCAyMDE1IDY6MDUgUE0NClRvOiBSb25hbGQg
Qm9uaWNhOyBadW5pZ2EsIEp1YW4gQ2FybG9zOyBpbnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50
LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnPG1haWx0bzppcHY2QGlldGYub3JnPjsgQmxh
Y2ssIERhdmlkDQpDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3Jn
PG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc+OyBpbnRh
cmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBSRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQoN
CkhpIFJvbiwNCg0KMSkgICAgICBhbmQgMiApIGFyZSBmaW5lLiBJTU86IDMpIHdvcmtzIHVuZGVy
IGNlcnRhaW4gY29uZGl0aW9ucyBidXQgbm90IGFsbC4NCg0KSSBhZGQgRGF2aWQgQmxhY2sgKFRT
VldHIGNoYWlyKSB0byB0aGUgdGhyZWFkLiBIZSBjYW4gcHJvdmlkZSB0aGUgdGhvcm91Z2ggY2hl
Y2suDQoNClJlZ2FyZHMsDQpMdWN5DQoNCkZyb206IFJvbmFsZCBCb25pY2EgW21haWx0bzpyYm9u
aWNhQGp1bmlwZXIubmV0XQ0KU2VudDogTW9uZGF5LCBNYXJjaCAzMCwgMjAxNSA0OjQ5IFBNDQpU
bzogTHVjeSB5b25nOyBadW5pZ2EsIEp1YW4gQ2FybG9zOyBpbnQtYXJlYUBpZXRmLm9yZzxtYWls
dG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnPG1haWx0bzppcHY2QGlldGYub3Jn
Pg0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzxtYWlsdG86
ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPjsgaW50YXJlYS1jaGFp
cnNAaWV0Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnPg0KU3ViamVjdDogUkU6
IFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KDQpMdWN5LA0K
DQpXb3VsZCB0aGUgZm9sbG93aW5nIHRleHQgd29yaz8NCg0KT0xEPg0KICAgQmVjYXVzZSB0aGUg
SVB2NiBkZWxpdmVyeSBoZWFkZXIgZG9lcyBub3QgaW5jbHVkZSBhIGNoZWNrc3VtIG9mIGl0cw0K
ICAgb3duLCBpdCBpcyBzdWJqZWN0IHRvIGNvcnJ1cHRpb24uICBIb3dldmVyLCBldmVuIGlmIHRo
ZSBkZWxpdmVyeQ0KICAgaGVhZGVyIGlzIGNvcnJ1cHRlZCwgdG8gbGlrZWxpaG9vZCBvZiB0aGF0
IGNvcnJ1cHRpb24gcmVzdWx0aW5nIGluDQogICBtaXNkZWxpdmVyeSBvZiB0aGUgcGF5bG9hZCBp
cyBleHRyZW1lbHkgbG93Lg0KPE9MRA0KDQpORVc+DQogICBCZWNhdXNlIHRoZSBJUHY2IGRlbGl2
ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzDQogICBvd24sICB0
aGUgZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlcnkgaGVhZGVyIGlzIHN1YmplY3Qg
dG8NCiAgIGNvcnJ1cHRpb24uIElmIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBkZWxp
dmVyIGhlYWRlciBpcyBjb3JydXB0ZWQsDQogICB0aGUgZm9sbG93aW5nIG91dGNvbWVzIGFyZSBw
b3NzaWJsZToNCg0KMSkgICAgICBUaGUgZGVsaXZlcnkgcGFja2V0IGlzIGRyb3BwZWQgYmVjYXVz
ZSB0aGUgbmV3IGRlc3RpbmF0aW9uIGFkZHJlc3MgaXMgdW5yZWFjaGFibGUNCjIpICAgICAgVGhl
IGRlbGl2ZXJ5IHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5hdGlvbiBh
ZGRyZXNzIGlzIHJlYWNoYWJsZSwgYnV0IHRoYXQgbm9kZSBpcyBub3QgY29uZmlndXJlZCB0byBw
cm9jZXNzIEdSRSBkZWxpdmVyeSBwYWNrZXRzIGZyb20gdGhlIGluZ3Jlc3MNCjMpICAgICAgVGhl
IGRlbGl2ZXJ5IHBhY2tldCBpcyBwcm9jZXNzZWQgYnkgYSBHUkUgZWdyZXNzIG90aGVyIHRoYW4g
dGhhdCB3aGljaCB3YXMgb3JpZ2luYWxseSBzcGVjaWZpZWQgYnkgdGhlIEdSRSBpbmdyZXNzLiBQ
cm9jZXNzaW5nIG9wdGlvbnMgYXJlOg0KYS4gICAgICAgVGhlIHBheWxvYWQgcGFja2V0IGlzIGRy
b3BwZWQgYmVjYXVzZSB0aGUgcGF5bG9hZCBkZXN0aW5hdGlvbiBpcyB1bnJlYWNoYWJsZSBmcm9t
IHRoZSBub2RlIHRoYXQgcHJvY2Vzc2VkIHRoZSBkZWxpdmVyeSBwYWNrZXQNCmIuICAgICAgVGhl
IHBheWxvYWQgcGFja2V0IGlzIGRlbGl2ZXJlZCB0byBpdHMgaW50ZW5kZWQgZGVzdGluYXRpb24g
YmVjYXVzZSB0aGUgcGF5bG9hZCBkZXN0aW5hdGlvbiBpcyByZWFjaGFibGUgZnJvbSB0aGUgbm9k
ZSB0aGF0IHByb2Nlc3NlZCB0aGUgZGVsaXZlcnkgcGFja2V0DQoNCkFsbCBvZiB0aGVzZSBvdXRj
b21lcyBhcmUgYWNjZXB0YWJsZS4NCg0KPE5FVw0KDQogICAgICAgICAgICAgICAgICAgICAgICAg
IFJvbg0KDQpGcm9tOiBMdWN5IHlvbmcgW21haWx0bzpsdWN5LnlvbmdAaHVhd2VpLmNvbV0NClNl
bnQ6IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDo1MCBQTQ0KVG86IFp1bmlnYSwgSnVhbiBDYXJs
b3M7IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBpZXRmLm9yZz47IGlwdjZAaWV0
Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+DQpDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1p
cHY2QHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9v
bHMuaWV0Zi5vcmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFp
cnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1p
bnRhcmVhLWdyZS1pcHY2DQoNClRoYW5rcyBhdXRob3JzIHRvIGFkZCBzZWN0aW9uIDQuMS4NCg0K
SSBhbSBub3Qgc3VyZSBpZiB0aGUgc3RhdGVtZW50IG9mIOKAnEhvd2V2ZXIsIGV2ZW4gaWYgdGhl
IGRlbGl2ZXJ5IGhlYWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2VsaWhvb2Qgb2YgdGhhdCBjb3Jy
dXB0aW9uIHJlc3VsdGluZyBpbiBtaXNkZWxpdmVyeSBvZiB0aGUgcGF5bG9hZCBpcyBleHRyZW1l
bHkgbG93LuKAnSBpcyBwcm9wZXIuIElQdjYgcmVxdWlyZXMgdGhlIGVuZCBwb2ludC91cHBlciBs
YXllciB0byBkZWFsIHdpdGggdGhlIGhlYWRlciBjb3JydXB0aW9uLiBDb3VsZCB3ZSBzdGF0ZSB0
aGF0IHRoaXMgaXMgdGhlIGRpZmZlcmVuY2UgZnJvbSBncmUtaW4taXB2NCBpbnN0ZWFkPw0KDQpM
dWN5DQoNCg0KRnJvbTogSW50LWFyZWEgW21haWx0bzppbnQtYXJlYS1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgT2YgWnVuaWdhLCBKdWFuIENhcmxvcw0KU2VudDogTW9uZGF5LCBNYXJjaCAz
MCwgMjAxNSAzOjI3IFBNDQpUbzogaW50LWFyZWFAaWV0Zi5vcmc8bWFpbHRvOmludC1hcmVhQGll
dGYub3JnPjsgaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4NCkNjOiBkcmFmdC1p
ZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtaW50
YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEtY2hhaXJzQGlldGYub3JnPG1h
aWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFtJbnQtYXJlYV0gU3RhcnQg
b2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQoNCkRlYXIgSW50LUFyZWEg
YW5kIDZtYW4gV0dzLA0KDQpBdCB0aGUgSW50LUFyZWEgV0cgbWVldGluZyBpbiBEYWxsYXMgdGhl
cmUgd2VyZSBzb21lIGNvbW1lbnRzIG9uIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni4gSXQg
d2FzIGRlY2lkZWQgdG8gc3VibWl0IHRoZSBkb2N1bWVudCBmb3IgV0cgTGFzdCBDYWxsIHRvIHRo
ZSBJbnQtQXJlYSAmIDZtYW4gV0dzIGFzIHNvb24gYXMgdGhlIGFncmVlZCBjaGFuZ2VzIHdlcmUg
bWFkZS4NCg0KVGhlIGRvY3VtZW50IGhhcyBub3cgYmVlbiB1cGRhdGVkIGFjY29yZGluZ2x5LCBz
byB0aGlzIGVtYWlsIHN0YXJ0cyBhbiBJbnQtQXJlYS82bWFuIFdHcyBMYXN0IENhbGwgb246DQoN
Cmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni0w
NA0KDQpQbGVhc2UgcmVzcG9uZCB0byB0aGlzIGVtYWlsIHRvIHN1cHBvcnQgdGhlIGRvY3VtZW50
IGFuZC9vciBzZW5kIGNvbW1lbnRzIGJ5IDIwMTUtMDQtMDYuDQoNCkluIGFkZGl0aW9uLCB0byBz
YXRpc2Z5IFJGQyA2NzAyICJQcm9tb3RpbmcgQ29tcGxpYW5jZSB3aXRoIEludGVsbGVjdHVhbCBQ
cm9wZXJ0eSBSaWdodHMgKElQUikiOg0KQXJlIHlvdSBwZXJzb25hbGx5IGF3YXJlIG9mIGFueSBJ
UFIgdGhhdCBhcHBsaWVzIHRvIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Nj8NCklmIHNvLCBo
YXMgdGhpcyBJUFIgYmVlbiBkaXNjbG9zZWQgaW4gY29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1
bGVzPw0KKFNlZSBSRkNzIDM5NzksIDQ4NzksIDM2NjksIGFuZCA1Mzc4IGZvciBtb3JlIGRldGFp
bHMuKQ0KDQpCZXN0LA0KDQpKdWFuIENhcmxvcyBadW5pZ2ENCihhcyBJbnQtQXJlYSBXRyBjby1j
aGFpcikNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CkludC1hcmVhIG1haWxpbmcgbGlzdA0KSW50LWFyZWFAaWV0Zi5vcmc8bWFpbHRvOkludC1hcmVh
QGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnQtYXJl
YQ0KDQo=

--_000_2691CE0099834E4A9C5044EEC662BB9D57155576dfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQg
NSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw
YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9
DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2
Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0K
YTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29s
b3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5N
c29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVy
cGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29B
Y2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0
eWxlLWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNh
bnMtc2VyaWYiO30NCnNwYW4uYXBwbGUtY29udmVydGVkLXNwYWNlDQoJe21zby1zdHlsZS1uYW1l
OmFwcGxlLWNvbnZlcnRlZC1zcGFjZTt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5
bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCglt
c28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fu
cy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwt
cmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0
OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGlu
Ow0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJ
e3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+
PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4
dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxh
eW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5r
PSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+SGkgQ2FybG9zLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SSBhbSBub3QgY2xlYXIgd2hhdCB5b3UgcHJvcG9zZS4g
VURQIGNoZWNrc3VtIGluY2x1ZGVzIElQIGhlYWRlci4gR1JFIGRvZXMgbm90Lg0KPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij5MdWN5PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk
ICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gQ2FybG9zIFBpZ25hdGFybyAoY3BpZ25hdGEpIFtt
YWlsdG86Y3BpZ25hdGFAY2lzY28uY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1h
cmNoIDMxLCAyMDE1IDI6MDEgUE08YnI+DQo8Yj5Ubzo8L2I+IEJsYWNrLCBEYXZpZDsgTHVjeSB5
b25nPGJyPg0KPGI+Q2M6PC9iPiBSb25hbGQgUC4gQm9uaWNhOyBpbnQtYXJlYUBpZXRmLm9yZzsg
aXB2NkBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3Jn
OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0ludC1h
cmVhXSBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSwgTHVjeSw8bzpwPjwv
bzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uZSBhcHByb2FjaCBpcyB0
byBhZGQgYSAzLmMpIHRvIHRoZSBsaXN0IHRoYXQgUm9uIHNoYXJlZC4gSSB0aGluayB0aGVyZSBp
cyBhbm90aGVyIHBvdGVudGlhbCBhcHByb2FjaCB0byB5b3VyIGluaXRpYWwgY29tbWVudDogd2Ug
Y291bGQgbm90ZSB0aGF0IGZvciBhIHR1bm5lbGluZyBwcm90b2NvbCAoR1JFKSwgdGhpcyBpcyBl
cXVpdmFsZW50IHRvIHRoZSByZWxheGF0aW9uIG9mIHRoZSBVRFAgY2hlY2tzdW0NCiBpbiBSRkMm
bmJzcDs2OTM1LCBhbmQga2VlcCB0aGUgZXhpc3RpbmcgdGV4dC48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RnJlZCwgUkZDIDI0NzMgZG9lcyBu
b3QgbWVudGlvbiBjaGVja3N1bXMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2FybG9zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gTWFyIDMwLCAyMDE1LCBhdCA3OjQ3IFBN
LCBCbGFjaywgRGF2aWQgJmx0OzxhIGhyZWY9Im1haWx0bzpkYXZpZC5ibGFja0BlbWMuY29tIj5k
YXZpZC5ibGFja0BlbWMuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jmd0OzxzcGFuIGNsYXNzPSJhcHBsZS1j
b252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkFsc28sIHdoeSB3b3VsZCB5b3Ugb2JqZWN0IHRvIDNiPyBU
aGUgcGFja2V0IGVuZHMNCiB1cCBhdCB0aGUgcmlnaHQgbm9kZSwganVzdCB2aWEgYW4gdW5leHBl
Y3RlZCByb3V0ZS48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
OyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsi
PlRoYXQgYXNzZXJ0aW9uIGlzIGJhc2VkIG9uIHRoZSBhc3N1bXB0aW9uIHRoYXQgdGhlIHBheWxv
YWQgZGVzdGluYXRpb24gYWRkcmVzcyBpcyB3b3JsZHdpZGUgdW5pcXVlLjwvc3Bhbj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+VGhlcmUgYXJlIGxvdHMgb2YgY291bnRl
cmV4YW1wbGVzIHRoYXQgdm9pZCB0aGUgYXNzdW1wdGlvbiwgZS5nLiwgMTAuMC4wLjAvOC48L3Nw
YW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7PC9zcGFu
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+
VGhhbmtzLDxicj4NCi0tRGF2aWQ8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4g
MGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNv
bGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+Jm5ic3A7PC9zcGFuPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+THVjeQ0KIHlvbmcgWzxhIGhyZWY9Im1haWx0bzpsdWN5LnlvbmdAaHVhd2VpLmNvbSI+
PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRGNzIiPm1haWx0bzpsdWN5LnlvbmdAaHVhd2VpLmNvbTwv
c3Bhbj48L2E+XTxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bh
bj48YnI+DQo8Yj5TZW50OjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4m
bmJzcDs8L3NwYW4+TW9uZGF5LCBNYXJjaCAzMCwgMjAxNSA2OjMxIFBNPGJyPg0KPGI+VG86PC9i
PjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5Sb25hbGQg
Qm9uaWNhOyBadW5pZ2EsIEp1YW4gQ2FybG9zOzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQt
c3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmciPjxz
cGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5pbnQtYXJlYUBpZXRmLm9yZzwvc3Bhbj48L2E+Ozxz
cGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJt
YWlsdG86aXB2NkBpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRGNzIiPmlwdjZAaWV0
Zi5vcmc8L3NwYW4+PC9hPjsNCiBCbGFjaywgRGF2aWQ8YnI+DQo8Yj5DYzo8L2I+PHNwYW4gY2xh
c3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpk
cmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJj
b2xvcjojOTU0RjcyIj5kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8
L3NwYW4+PC9hPjs8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3Nw
YW4+PGEgaHJlZj0ibWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnIj48c3BhbiBzdHlsZT0i
Y29sb3I6Izk1NEY3MiI+aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8L3NwYW4+PC9hPjxicj4NCjxi
PlN1YmplY3Q6PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwv
c3Bhbj5SRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PC9z
cGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpIFJvbiw8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjNiKSBpcyB0aGUgY29uY2Vybi4gR1JFIHBheWxvYWQg
bWF5IGJlIG5vbi1JUCB0eXBlLiBJZiBhIGdyZS1pbi1pcHY2IHR1bm5lbCBpcyB1c2VkIGZvciBt
dXggb2YgZGlmZmVyZW50IHBheWxvYWQgdHlwZXMsIHRoZSBvdXRjb21lIG1heSBiZSB1bmtub3du
IGFuZCBjYW4gYmUNCiB1bmFjY2VwdGFibGUgdXBvbiBJUCBhZGRyZXNzIGFuZC9vciBHUkUgaGVh
ZGVyIGFyZSBjb3JydXB0ZWQuPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5MdWN5PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xp
ZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPiZuYnNwOzwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPlJvbmFsZA0KIEJvbmljYSBbPGEgaHJlZj0ibWFpbHRvOnJib25pY2FAanVuaXBlci5uZXQi
PjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5tYWlsdG86cmJvbmljYUBqdW5pcGVyLm5ldDwv
c3Bhbj48L2E+XTxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bh
bj48YnI+DQo8Yj5TZW50OjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4m
bmJzcDs8L3NwYW4+TW9uZGF5LCBNYXJjaCAzMCwgMjAxNSA1OjE0IFBNPGJyPg0KPGI+VG86PC9i
PjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5MdWN5IHlv
bmc7IFp1bmlnYSwgSnVhbiBDYXJsb3M7PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFj
ZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzppbnQtYXJlYUBpZXRmLm9yZyI+PHNwYW4g
c3R5bGU9ImNvbG9yOiM5NTRGNzIiPmludC1hcmVhQGlldGYub3JnPC9zcGFuPjwvYT47PHNwYW4g
Y2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0
bzppcHY2QGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6Izk1NEY3MiI+aXB2NkBpZXRmLm9y
Zzwvc3Bhbj48L2E+Ow0KIEJsYWNrLCBEYXZpZDxicj4NCjxiPkNjOjwvYj48c3BhbiBjbGFzcz0i
YXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmRyYWZ0
LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9y
OiM5NTRGNzIiPmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzwvc3Bh
bj48L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48
YSBocmVmPSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xv
cjojOTU0RjcyIj5pbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzwvc3Bhbj48L2E+PGJyPg0KPGI+U3Vi
amVjdDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFu
PlJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+THVjeSw8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFu
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPldoeSB3b3VsZCB5b3Ugb2JqZWN0IHRvIDNhPyBEcm9wcGluZyB0
aGUgcGFja2V0IGlzIHRoZSBwcmVmZXJyZWQgYmVoYXZpb3I/PC9zcGFuPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5BbHNvLCB3aHkgd291bGQgeW91IG9i
amVjdCB0byAzYj8gVGhlIHBhY2tldCBlbmRzIHVwIGF0IHRoZSByaWdodCBub2RlLCBqdXN0IHZp
YSBhbiB1bmV4cGVjdGVkIHJvdXRlLiBSZWNhbGwgdGhhdCB0aGUgZGVzdGluYXRpb24gYWRkcmVz
cyBpbiB0aGUgcGF5bG9hZCBoZWFkZXINCiBpcyBwcm90ZWN0ZWQgYnkgdGhlIFVEUC9UQ1AgY2hl
Y2tzdW0uPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5BcmUgeW91IHRoaW5raW5nIHRoYXQgdGhlcmUgbWlnaHQgYmUgYSAzYyk/PC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgUm9uPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGNsYXNzPSJh
cHBsZS1jb252ZXJ0ZWQtc3BhY2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7
PC9zcGFuPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkx1Y3kNCiB5b25nIFs8
YSBocmVmPSJtYWlsdG86bHVjeS55b25nQGh1YXdlaS5jb20iPjxzcGFuIHN0eWxlPSJjb2xvcjoj
OTU0RjcyIj5tYWlsdG86bHVjeS55b25nQGh1YXdlaS5jb208L3NwYW4+PC9hPl08c3BhbiBjbGFz
cz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGJyPg0KPGI+U2VudDo8L2I+
PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPk1vbmRheSwg
TWFyY2ggMzAsIDIwMTUgNjowNSBQTTxicj4NCjxiPlRvOjwvYj48c3BhbiBjbGFzcz0iYXBwbGUt
Y29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+Um9uYWxkIEJvbmljYTsgWnVuaWdhLCBKdWFu
IENhcmxvczs8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+
PGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6Izk1
NEY3MiI+aW50LWFyZWFAaWV0Zi5vcmc8L3NwYW4+PC9hPjs8c3BhbiBjbGFzcz0iYXBwbGUtY29u
dmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmci
PjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5pcHY2QGlldGYub3JnPC9zcGFuPjwvYT47DQog
QmxhY2ssIERhdmlkPGJyPg0KPGI+Q2M6PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQt
c3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdy
ZS1pcHY2QHRvb2xzLmlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6Izk1NEY3MiI+ZHJhZnQt
aWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPC9zcGFuPjwvYT47PHNwYW4gY2xh
c3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpp
bnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRGNzIiPmludGFy
ZWEtY2hhaXJzQGlldGYub3JnPC9zcGFuPjwvYT48YnI+DQo8Yj5TdWJqZWN0OjwvYj48c3BhbiBj
bGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+UkU6IFN0YXJ0IG9mIFdH
TEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5IaSBSb24sPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNw
Ozwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+MSk8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo3LjBw
dDtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs8c3BhbiBjbGFz
cz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5hbmQNCiAyICkgYXJlIGZpbmUuIElNTzog
Mykgd29ya3MgdW5kZXIgY2VydGFpbiBjb25kaXRpb25zIGJ1dCBub3QgYWxsLjwvc3Bhbj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2IHN0eWxlPSJtYXJnaW4tbGVmdDouMjVpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SSBhZGQgRGF2aWQgQmxhY2sg
KFRTVldHIGNoYWlyKSB0byB0aGUgdGhyZWFkLiBIZSBjYW4gcHJvdmlkZSB0aGUgdGhvcm91Z2gg
Y2hlY2suPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5SZWdhcmRzLDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5MdWN5PC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGlu
Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2Ui
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5Sb25hbGQNCiBCb25pY2EgWzxhIGhyZWY9Im1haWx0bzpyYm9u
aWNhQGp1bmlwZXIubmV0Ij48c3BhbiBzdHlsZT0iY29sb3I6Izk1NEY3MiI+bWFpbHRvOnJib25p
Y2FAanVuaXBlci5uZXQ8L3NwYW4+PC9hPl08c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNw
YWNlIj4mbmJzcDs8L3NwYW4+PGJyPg0KPGI+U2VudDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNv
bnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPk1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDo0OSBQ
TTxicj4NCjxiPlRvOjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJz
cDs8L3NwYW4+THVjeSB5b25nOyBadW5pZ2EsIEp1YW4gQ2FybG9zOzxzcGFuIGNsYXNzPSJhcHBs
ZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86aW50LWFyZWFA
aWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5pbnQtYXJlYUBpZXRmLm9yZzwv
c3Bhbj48L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bh
bj48YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRG
NzIiPmlwdjZAaWV0Zi5vcmc8L3NwYW4+PC9hPjxicj4NCjxiPkNjOjwvYj48c3BhbiBjbGFzcz0i
YXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmRyYWZ0
LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9y
OiM5NTRGNzIiPmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzwvc3Bh
bj48L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48
YSBocmVmPSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xv
cjojOTU0RjcyIj5pbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzwvc3Bhbj48L2E+PGJyPg0KPGI+U3Vi
amVjdDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFu
PlJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+THVjeSw8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFu
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPldvdWxkIHRoZSBmb2xsb3dpbmcgdGV4dCB3b3JrPzwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+T0xEJmd0Ozwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgQmVjYXVzZSB0aGUgSVB2NiBkZWxp
dmVyeSBoZWFkZXIgZG9lcyBub3QgaW5jbHVkZSBhIGNoZWNrc3VtIG9mIGl0czwvc3Bhbj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgb3duLCBpdCBpcyBzdWJqZWN0IHRvIGNvcnJ1cHRp
b24uJm5ic3A7IEhvd2V2ZXIsIGV2ZW4gaWYgdGhlIGRlbGl2ZXJ5PC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPiZuYnNwOyZuYnNwOyBoZWFkZXIgaXMgY29ycnVwdGVkLCB0byBsaWtlbGlob29kIG9m
IHRoYXQgY29ycnVwdGlvbiByZXN1bHRpbmcgaW48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5i
c3A7Jm5ic3A7IG1pc2RlbGl2ZXJ5IG9mIHRoZSBwYXlsb2FkIGlzIGV4dHJlbWVseSBsb3cuPC9z
cGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZsdDtPTEQ8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5i
c3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPk5FVyZndDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+Jm5ic3A7Jm5ic3A7IEJlY2F1c2UgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90
IGluY2x1ZGUgYSBjaGVja3N1bSBvZiBpdHM8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7
Jm5ic3A7IG93biwgJm5ic3A7dGhlIGRlc3RpbmF0aW9uIGFkZHJlc3MgaW4gdGhlIGRlbGl2ZXJ5
IGhlYWRlciBpcyBzdWJqZWN0IHRvPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNw
OyZuYnNwO2NvcnJ1cHRpb24uIElmIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBkZWxp
dmVyIGhlYWRlciBpcyBjb3JydXB0ZWQsPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZu
YnNwOyB0aGUgZm9sbG93aW5nIG91dGNvbWVzIGFyZSBwb3NzaWJsZTo8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW4tbGVmdDouNzVpbiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6LS4yNWluIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+MSk8L3NwYW4+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZTo3LjBwdDtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDs8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PC9z
cGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGUNCiBkZWxp
dmVyeSBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBuZXcgZGVzdGluYXRpb24gYWRkcmVz
cyBpcyB1bnJlYWNoYWJsZTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW4i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjIpPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6Ny4wcHQ7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhlDQogZGVs
aXZlcnkgcGFja2V0IGlzIGRyb3BwZWQgYmVjYXVzZSB0aGUgbmV3IGRlc3RpbmF0aW9uIGFkZHJl
c3MgaXMgcmVhY2hhYmxlLCBidXQgdGhhdCBub2RlIGlzIG5vdCBjb25maWd1cmVkIHRvIHByb2Nl
c3MgR1JFIGRlbGl2ZXJ5IHBhY2tldHMgZnJvbSB0aGUgaW5ncmVzczwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBz
dHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRl
eHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPjMpPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7Y29sb3I6IzFGNDk3RCI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+VGhlDQogZGVsaXZlcnkgcGFja2V0IGlzIHByb2Nlc3NlZCBieSBhIEdS
RSBlZ3Jlc3Mgb3RoZXIgdGhhbiB0aGF0IHdoaWNoIHdhcyBvcmlnaW5hbGx5IHNwZWNpZmllZCBi
eSB0aGUgR1JFIGluZ3Jlc3MuIFByb2Nlc3Npbmcgb3B0aW9ucyBhcmU6PC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
IHN0eWxlPSJtYXJnaW4tbGVmdDoxLjI1aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
InRleHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPmEuPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7Y29sb3I6IzFGNDk3
RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PHNwYW4gY2xhc3M9ImFwcGxl
LWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhlDQogcGF5bG9hZCBwYWNrZXQgaXMgZHJvcHBlZCBi
ZWNhdXNlIHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uIGlzIHVucmVhY2hhYmxlIGZyb20gdGhlIG5v
ZGUgdGhhdCBwcm9jZXNzZWQgdGhlIGRlbGl2ZXJ5IHBhY2tldDwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MS4yNWluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0
LWluZGVudDotLjI1aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij5iLjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2NvbG9yOiMxRjQ5N0QiPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQt
c3BhY2UiPiZuYnNwOzwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPlRoZQ0KIHBheWxvYWQgcGFja2V0IGlzIGRlbGl2ZXJlZCB0byBpdHMgaW50
ZW5kZWQgZGVzdGluYXRpb24gYmVjYXVzZSB0aGUgcGF5bG9hZCBkZXN0aW5hdGlvbiBpcyByZWFj
aGFibGUgZnJvbSB0aGUgbm9kZSB0aGF0IHByb2Nlc3NlZCB0aGUgZGVsaXZlcnkgcGFja2V0PC9z
cGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5BbGwg
b2YgdGhlc2Ugb3V0Y29tZXMgYXJlIGFjY2VwdGFibGUuPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbHQ7TkVXPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgUm9uPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVw
dDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGlu
IDBpbiI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1z
cGFjZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+THVjeQ0KIHlvbmcgWzxhIGhyZWY9Im1haWx0bzps
dWN5LnlvbmdAaHVhd2VpLmNvbSI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRGNzIiPm1haWx0bzps
dWN5LnlvbmdAaHVhd2VpLmNvbTwvc3Bhbj48L2E+XTxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0
ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YnI+DQo8Yj5TZW50OjwvYj48c3BhbiBjbGFzcz0iYXBw
bGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+TW9uZGF5LCBNYXJjaCAzMCwgMjAxNSA0
OjUwIFBNPGJyPg0KPGI+VG86PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2Ui
PiZuYnNwOzwvc3Bhbj5adW5pZ2EsIEp1YW4gQ2FybG9zOzxzcGFuIGNsYXNzPSJhcHBsZS1jb252
ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWlsdG86aW50LWFyZWFAaWV0Zi5v
cmciPjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5pbnQtYXJlYUBpZXRmLm9yZzwvc3Bhbj48
L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBo
cmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRGNzIiPmlw
djZAaWV0Zi5vcmc8L3NwYW4+PC9hPjxicj4NCjxiPkNjOjwvYj48c3BhbiBjbGFzcz0iYXBwbGUt
Y29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYt
aW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5NTRG
NzIiPmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzwvc3Bhbj48L2E+
OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVm
PSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0
RjcyIj5pbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzwvc3Bhbj48L2E+PGJyPg0KPGI+U3ViamVjdDo8
L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPlJFOiBT
dGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhhbmtzIGF1dGhvcnMgdG8gYWRkIHNlY3Rp
b24gNC4xLjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+SSBhbSBub3Qgc3VyZSBpZiB0aGUgc3RhdGVtZW50IG9mIOKAnDwvc3Bhbj48c3BhbiBs
YW5nPSJFTiIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhvd2V2ZXIsIGV2
ZW4gaWYgdGhlIGRlbGl2ZXJ5DQogaGVhZGVyIGlzIGNvcnJ1cHRlZCwgdG8gbGlrZWxpaG9vZCBv
ZiB0aGF0IGNvcnJ1cHRpb24gcmVzdWx0aW5nIGluIG1pc2RlbGl2ZXJ5IG9mIHRoZSBwYXlsb2Fk
IGlzIGV4dHJlbWVseSBsb3cu4oCdIGlzIHByb3Blci4gSVB2NiByZXF1aXJlcyB0aGUgZW5kIHBv
aW50L3VwcGVyIGxheWVyIHRvIGRlYWwgd2l0aCB0aGUgaGVhZGVyIGNvcnJ1cHRpb24uIENvdWxk
IHdlIHN0YXRlIHRoYXQgdGhpcyBpcyB0aGUgZGlmZmVyZW5jZSBmcm9tIGdyZS1pbi1pcHY0DQog
aW5zdGVhZD88L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTiIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+THVjeTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4m
bmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gY2xhc3M9ImFw
cGxlLWNvbnZlcnRlZC1zcGFjZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzwv
c3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkludC1hcmVhDQogWzxhIGhy
ZWY9Im1haWx0bzppbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6
Izk1NEY3MiI+bWFpbHRvOmludC1hcmVhLWJvdW5jZXNAaWV0Zi5vcmc8L3NwYW4+PC9hPl08c3Bh
biBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGI+T24gQmVoYWxm
IE9mPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvYj5a
dW5pZ2EsIEp1YW4gQ2FybG9zPGJyPg0KPGI+U2VudDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNv
bnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPk1vbmRheSwgTWFyY2ggMzAsIDIwMTUgMzoyNyBQ
TTxicj4NCjxiPlRvOjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJz
cDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj48c3BhbiBzdHlsZT0i
Y29sb3I6Izk1NEY3MiI+aW50LWFyZWFAaWV0Zi5vcmc8L3NwYW4+PC9hPjs8c3BhbiBjbGFzcz0i
YXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmlwdjZA
aWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5pcHY2QGlldGYub3JnPC9zcGFu
PjwvYT48YnI+DQo8Yj5DYzo8L2I+PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+
Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZA
dG9vbHMuaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjojOTU0RjcyIj5kcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8L3NwYW4+PC9hPjs8c3BhbiBjbGFzcz0iYXBw
bGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmludGFyZWEt
Y2hhaXJzQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6Izk1NEY3MiI+aW50YXJlYS1jaGFp
cnNAaWV0Zi5vcmc8L3NwYW4+PC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPjxzcGFuIGNsYXNzPSJh
cHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5bSW50LWFyZWFdIFN0YXJ0IG9mIFdH
TEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Njwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RGVhciBJbnQtQXJlYSBh
bmQgNm1hbiBXR3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkF0IHRoZSBJbnQtQXJlYSBXRyBtZWV0aW5nIGluIERh
bGxhcyB0aGVyZSB3ZXJlIHNvbWUgY29tbWVudHMgb24gZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1p
cHY2LiBJdCB3YXMgZGVjaWRlZCB0byBzdWJtaXQgdGhlIGRvY3VtZW50IGZvciBXRyBMYXN0IENh
bGwgdG8gdGhlIEludC1BcmVhICZhbXA7IDZtYW4NCiBXR3MgYXMgc29vbiBhcyB0aGUgYWdyZWVk
IGNoYW5nZXMgd2VyZSBtYWRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UaGUgZG9jdW1lbnQgaGFzIG5vdyBiZWVu
IHVwZGF0ZWQgYWNjb3JkaW5nbHksIHNvIHRoaXMgZW1haWwgc3RhcnRzIGFuIEludC1BcmVhLzZt
YW4gV0dzIExhc3QgQ2FsbCBvbjo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNw
OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LTA0Ij48c3BhbiBzdHlsZT0i
Y29sb3I6Izk1NEY3MiI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pbnRh
cmVhLWdyZS1pcHY2LTA0PC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+UGxlYXNlIHJlc3BvbmQgdG8g
dGhpcyBlbWFpbCB0byBzdXBwb3J0IHRoZSBkb2N1bWVudCBhbmQvb3Igc2VuZCBjb21tZW50cyBi
eSAyMDE1LTA0LTA2LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Jm5ic3A7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5JbiBhZGRpdGlvbiwgdG8gc2F0aXNmeSBSRkMgNjcw
MiAmcXVvdDtQcm9tb3RpbmcgQ29tcGxpYW5jZSB3aXRoIEludGVsbGVjdHVhbCBQcm9wZXJ0eSBS
aWdodHMgKElQUikmcXVvdDs6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5BcmUgeW91
IHBlcnNvbmFsbHkgYXdhcmUgb2YgYW55IElQUiB0aGF0IGFwcGxpZXMgdG8gZHJhZnQtaWV0Zi1p
bnRhcmVhLWdyZS1pcHY2PyZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SWYg
c28sIGhhcyB0aGlzIElQUiBiZWVuIGRpc2Nsb3NlZCBpbiBjb21wbGlhbmNlIHdpdGggSUVURiBJ
UFIgcnVsZXM/PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4oU2VlIFJGQ3MgMzk3OSwg
NDg3OSwgMzY2OSwgYW5kIDUzNzggZm9yIG1vcmUgZGV0YWlscy4pPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkJlc3Qs
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPkp1YW4gQ2FybG9zIFp1bmlnYTxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0
ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPihh
cyBJbnQtQXJlYSBXRyBjby1jaGFpcik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+X19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpJbnQtYXJl
YSBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86SW50LWFyZWFAaWV0Zi5vcmciPklu
dC1hcmVhQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaW50LWFyZWEiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaW50LWFyZWE8L2E+PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_2691CE0099834E4A9C5044EEC662BB9D57155576dfweml701chm_--


From nobody Wed Apr  1 00:25:47 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9B71ACE6A; Tue, 31 Mar 2015 12:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukpMNbfVN58V; Tue, 31 Mar 2015 12:21:31 -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 C391E1AC39F; Tue, 31 Mar 2015 12:21:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUI83621; Tue, 31 Mar 2015 19:21:25 +0000 (GMT)
Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 31 Mar 2015 20:21:24 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Tue, 31 Mar 2015 12:21:15 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, "Black, David" <david.black@emc.com>,  "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYA==
Date: Tue, 31 Mar 2015 19:21:15 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D5715558D@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.181]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D5715558Ddfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/snavMwU6QxMYnInjhA3Scsotu2k>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 19:21:34 -0000

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

SGkgUm9uLA0KDQozYykgbWF5IGhhcHBlbiBmb3IgYSBWUE4gb3Igbm9uLVZQTiBjYXNlLiBUaGUg
cGF5bG9hZCBjYW4gYmUgaW4gbm9uLUlQdjYgc3BhY2UuICBJcyDigJxPdXRjb21lIDNjKSBpcyBu
b3QgYWNjZXB0YWJsZSwgYnV0IGl0IGV4dHJlbWVseSB1bmxpa2VseS7igJ0gZm9yIHBhcnRpY3Vs
YXIgbmV0d29yay91c2FnZSBpbiB5b3VyIG1pbmQ/DQoNCklzIHRoZSBnb2FsIGhlcmUgdG8gcHJv
dmUgc3VjaCBjb3JydXB0aW9uIGlzIGFjY2VwdGFibGUgb3IgZXh0cmVtZSB1bmxpa2VseT8NCg0K
UmVnYXJkcywNCkx1Y3kNCg0KRnJvbTogSW50LWFyZWEgW21haWx0bzppbnQtYXJlYS1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgUm9uYWxkIEJvbmljYQ0KU2VudDogVHVlc2RheSwgTWFy
Y2ggMzEsIDIwMTUgMTo0MyBQTQ0KVG86IEJsYWNrLCBEYXZpZDsgaW50LWFyZWFAaWV0Zi5vcmc7
IGlwdjZAaWV0Zi5vcmcNCkNjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0
Zi5vcmc7IGludGFyZWEtY2hhaXJzQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0ludC1hcmVhXSBT
dGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KUmVzZW5k4oCm
DQoNCkZyb206IFJvbmFsZCBCb25pY2ENClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDI6
MjMgUE0NClRvOiAnQmxhY2ssIERhdmlkJzsgaW50LWFyZWFAaWV0Zi5vcmc8bWFpbHRvOmludC1h
cmVhQGlldGYub3JnPjsgaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4NCkNjOiBk
cmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWll
dGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEtY2hhaXJzQGlldGYu
b3JnPG1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBTdGFydCBv
ZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KRGF2aWQsIEx1Y3ksDQoN
CllvdSBhcmUgY29ycmVjdC4gIE1heWJlIHRoZSBmb2xsb3dpbmcgdGV4dCB3aWxsIGFkZHJlc3Mg
dGhlIGlzc3VlOg0KDQpPTEQ+DQogICBCZWNhdXNlIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBk
b2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzDQogICBvd24sIGl0IGlzIHN1YmplY3Qg
dG8gY29ycnVwdGlvbi4gIEhvd2V2ZXIsIGV2ZW4gaWYgdGhlIGRlbGl2ZXJ5DQogICBoZWFkZXIg
aXMgY29ycnVwdGVkLCB0byBsaWtlbGlob29kIG9mIHRoYXQgY29ycnVwdGlvbiByZXN1bHRpbmcg
aW4NCiAgIG1pc2RlbGl2ZXJ5IG9mIHRoZSBwYXlsb2FkIGlzIGV4dHJlbWVseSBsb3cuDQo8T0xE
DQoNCk5FVz4NCiAgIEJlY2F1c2UgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90IGlu
Y2x1ZGUgYSBjaGVja3N1bSBvZiBpdHMNCiAgIG93biwgIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNz
IGluIHRoZSBkZWxpdmVyeSBoZWFkZXIgaXMgc3ViamVjdCB0bw0KICAgY29ycnVwdGlvbi4gSWYg
dGhlIGRlc3RpbmF0aW9uIGFkZHJlc3MgaW4gdGhlIGRlbGl2ZXIgaGVhZGVyIGlzIGNvcnJ1cHRl
ZCwNCiAgIHRoZSBmb2xsb3dpbmcgb3V0Y29tZXMgYXJlIHBvc3NpYmxlOg0KDQoNCjEpICAgICAg
VGhlIGRlbGl2ZXJ5IHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5hdGlv
biBhZGRyZXNzIGlzIHVucmVhY2hhYmxlDQoNCjIpICAgICAgVGhlIGRlbGl2ZXJ5IHBhY2tldCBp
cyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5hdGlvbiBhZGRyZXNzIGlzIHJlYWNoYWJs
ZSwgYnV0IHRoYXQgbm9kZSBpcyBub3QgY29uZmlndXJlZCB0byBwcm9jZXNzIEdSRSBkZWxpdmVy
eSBwYWNrZXRzIGZyb20gdGhlIGluZ3Jlc3MNCg0KMykgICAgICBUaGUgZGVsaXZlcnkgcGFja2V0
IGlzIHByb2Nlc3NlZCBieSBhIEdSRSBlZ3Jlc3Mgb3RoZXIgdGhhbiB0aGF0IHdoaWNoIHdhcyBv
cmlnaW5hbGx5IHNwZWNpZmllZCBieSB0aGUgR1JFIGluZ3Jlc3MuIFByb2Nlc3Npbmcgb3B0aW9u
cyBhcmU6DQoNCmEuICAgICAgIFRoZSBwYXlsb2FkIHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2Ug
dGhlIHBheWxvYWQgZGVzdGluYXRpb24gaXMgdW5yZWFjaGFibGUgZnJvbSB0aGUgbm9kZSB0aGF0
IHByb2Nlc3NlZCB0aGUgZGVsaXZlcnkgcGFja2V0DQoNCmIuICAgICAgVGhlIHBheWxvYWQgcGFj
a2V0IGlzIGRlbGl2ZXJlZCB0byBpdHMgaW50ZW5kZWQgZGVzdGluYXRpb24NCg0KYy4gICAgICAg
VGhlIHBheWxvYWQgcGFja2V0IGlzIGVycm9uZW91c2x5IGRlbGl2ZXJlZCB0byBhIG5vZGUgb3Ro
ZXIgdGhhbiBpdHMgaW50ZW5kZWQgZGVzdGluYXRpb24uIFRoZSBpbnRlbmRlZCBkZXN0aW5hdGlv
biBhbmQgdGhlIG5vZGUgdG8gd2hpY2ggdGhlIHBheWxvYWQgaXMgYWN0dWFsbHkgZGVsaXZlcmVk
IGFyZSBudW1iZXJlZCBpZGVudGljYWxseSwgYnV0IHJlc2lkZSBpbiBkaWZmZXJlbnQgVlBOcy4N
Cg0KT3V0Y29tZXMgMSksIDIpLCAzYSkgYW5kIDNiKSBhcmUgYWNjZXB0YWJsZS4gT3V0Y29tZSAz
YykgaXMgbm90IGFjY2VwdGFibGUsIGJ1dCBpdCBleHRyZW1lbHkgdW5saWtlbHkuIEJlY2F1c2Ug
SVB2NiBhZGRyZXNzIHNwYWNlIGlzIHNvIGxhcmdlIGFuZCBzbyBzcGFyc2VseSBwb3B1bGF0ZWQs
IG91dGNvbWUgMSkgaXMgYnkgZmFyIHRoZSBtb3N0IHByb2JhYmxlLiBUaGVyZWZvcmUsIHRoZSBj
b21iaW5lZCBsaWtlbGlob29kIG9mIGFsbCBhY2NlcHRhYmxlIG91dGNvbWVzIGJ5IGZhciBleGNl
ZWRzIHRoZSBsaWtlbGlob29kIG9mIHRoZSBvbmUgdW5hY2NlcHRhYmxlIG91dGNvbWUuDQoNCkZ1
cnRoZXJtb3JlLCBldmVuIGlmIHRoZSBwYXlsb2FkIGlzIGVycm9uZW91c2x5IGRlbGl2ZXJlZCB0
byBhIG5vZGUgb3RoZXIgdGhhbiBpdHMgaW50ZW5kZWQgZGVzdGluYXRpb24sIHRoYXQgbm9kZSB3
aWxsIGRpc2NhcmQgdGhlIHBhY2tldCBpZiB0aGUgcGF5bG9hZCBpcyBhbHNvIGNvcnJ1cHRlZCBv
ciBpZiB0aGVyZSBhcmUgbm8gYXBwbGljYXRpb25zIHdhaXRpbmcgdG8gY29uc3VtZSB0aGUgcGFj
a2V0Lg0KDQo8TkVXDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoN
Cg0KRnJvbTogQmxhY2ssIERhdmlkIFttYWlsdG86ZGF2aWQuYmxhY2tAZW1jLmNvbV0NClNlbnQ6
IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNzo0OCBQTQ0KVG86IFJvbmFsZCBCb25pY2E7IGludC1h
cmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBpZXRmLm9yZz47IGlwdjZAaWV0Zi5vcmc8bWFp
bHRvOmlwdjZAaWV0Zi5vcmc+DQpDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xz
LmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5v
cmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5v
cmc+OyBCbGFjaywgRGF2aWQNClN1YmplY3Q6IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1p
ZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KPiBBbHNvLCB3aHkgd291bGQgeW91IG9iamVjdCB0byAz
Yj8gVGhlIHBhY2tldCBlbmRzIHVwIGF0IHRoZSByaWdodCBub2RlLCBqdXN0IHZpYSBhbiB1bmV4
cGVjdGVkIHJvdXRlLg0KDQpUaGF0IGFzc2VydGlvbiBpcyBiYXNlZCBvbiB0aGUgYXNzdW1wdGlv
biB0aGF0IHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uIGFkZHJlc3MgaXMgd29ybGR3aWRlIHVuaXF1
ZS4NCg0KVGhlcmUgYXJlIGxvdHMgb2YgY291bnRlcmV4YW1wbGVzIHRoYXQgdm9pZCB0aGUgYXNz
dW1wdGlvbiwgZS5nLiwgMTAuMC4wLjAvOC4NCg0KVGhhbmtzLA0KLS1EYXZpZA0KDQoNCg==

--_000_2691CE0099834E4A9C5044EEC662BB9D5715558Ddfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNv
bnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IlxAU2ltU3VuIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30N
Ci8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYu
TXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
MDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojOTU0
RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1z
b1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
bXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiO30NCnANCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJn
aW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1m
YW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZv
bnQtZmFtaWx5OkNvbnNvbGFzO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1z
b0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxs
b29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpw
Lk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdy
YXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4t
cmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1z
dHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpD
b25zb2xhczt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRl
eHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFp
biBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uQmFs
bG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZv
bnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpwLmltcHJpbnR1bmlxdWVpZCwgbGku
aW1wcmludHVuaXF1ZWlkLCBkaXYuaW1wcmludHVuaXF1ZWlkDQoJe21zby1zdHlsZS1uYW1lOmlt
cHJpbnR1bmlxdWVpZDsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbWFyZ2luOjBpbjsNCglt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToi
VGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTI2DQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUyNw0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMx
RjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNw
YW4uRW1haWxTdHlsZTI5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5
bGUzMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzENCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
IjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTMyDQoJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJ
Zm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlv
bjpub25lIG5vbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzMNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdE
O30NCnNwYW4uRW1haWxTdHlsZTM0DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVt
YWlsU3R5bGUzNQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1
bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu
MGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIj
OTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SGkgUm9uLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+M2MpIG1heSBoYXBwZW4gZm9yIGEgVlBOIG9yIG5vbi1WUE4gY2Fz
ZS4gVGhlIHBheWxvYWQgY2FuIGJlIGluIG5vbi1JUHY2IHNwYWNlLiAmbmJzcDtJcyDigJw8L3Nw
YW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPk91dGNvbWUgM2MpIGlzIG5vdCBhY2NlcHRh
YmxlLCBidXQgaXQgZXh0cmVtZWx5IHVubGlrZWx5LuKAnSBmb3IgcGFydGljdWxhciBuZXR3b3Jr
L3VzYWdlDQogaW4geW91ciBtaW5kPyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPklzIHRoZSBnb2FsIGhlcmUgdG8gcHJvdmUgc3VjaCBjb3JydXB0aW9uIGlzIGFjY2VwdGFi
bGUgb3IgZXh0cmVtZSB1bmxpa2VseT8mbmJzcDsgJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5MdWN5PC9zcGFuPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBJbnQtYXJlYSBbbWFpbHRvOmludC1hcmVhLWJv
dW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlJvbmFsZCBCb25pY2E8YnI+DQo8
Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgMTo0MyBQTTxicj4NCjxiPlRvOjwv
Yj4gQmxhY2ssIERhdmlkOyBpbnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzxicj4NCjxi
PkNjOjwvYj4gZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnOyBpbnRh
cmVhLWNoYWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0ludC1hcmVhXSBT
dGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+UmVzZW5k4oCmPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7
cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFJvbmFsZCBCb25pY2EgPGJy
Pg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDI6MjMgUE08YnI+DQo8Yj5U
bzo8L2I+ICdCbGFjaywgRGF2aWQnOyA8YSBocmVmPSJtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmci
PmludC1hcmVhQGlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5p
cHY2QGlldGYub3JnPC9hPjxicj4NCjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWll
dGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZyI+ZHJhZnQtaWV0Zi1pbnRhcmVhLWdy
ZS1pcHY2QHRvb2xzLmlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzppbnRhcmVhLWNoYWly
c0BpZXRmLm9yZyI+aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8
L2I+IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjoj
MUY0OTdEIj5EYXZpZCwgTHVjeSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PllvdSBhcmUgY29ycmVjdC4gJm5ic3A7TWF5YmUgdGhlIGZvbGxvd2luZyB0ZXh0IHdpbGwgYWRk
cmVzcyB0aGUgaXNzdWU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5PTEQm
Z3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBCZWNhdXNlIHRoZSBJUHY2IGRlbGl2ZXJ5
IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PiZuYnNwOyZuYnNwOyBvd24sIGl0IGlzIHN1YmplY3QgdG8gY29ycnVwdGlvbi4mbmJzcDsgSG93
ZXZlciwgZXZlbiBpZiB0aGUgZGVsaXZlcnk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IGhl
YWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2VsaWhvb2Qgb2YgdGhhdCBjb3JydXB0aW9uIHJlc3Vs
dGluZyBpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgbWlzZGVsaXZlcnkgb2YgdGhlIHBh
eWxvYWQgaXMgZXh0cmVtZWx5IGxvdy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmx0O09MRDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+TkVXJmd0OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsm
bmJzcDsgQmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIgZG9lcyBub3QgaW5jbHVkZSBh
IGNoZWNrc3VtIG9mIGl0czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgb3duLCAmbmJzcDt0
aGUgZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlcnkgaGVhZGVyIGlzIHN1YmplY3Qg
dG8NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDtjb3JydXB0aW9uLiBJZiB0aGUg
ZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlciBoZWFkZXIgaXMgY29ycnVwdGVkLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgdGhlIGZvbGxvd2luZyBvdXRjb21lcyBhcmUgcG9z
c2libGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRl
bnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+MSk8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBkZWxpdmVy
eSBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBuZXcgZGVzdGluYXRpb24gYWRkcmVzcyBp
cyB1bnJlYWNoYWJsZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFy
YWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRlbnQ6LS4yNWluIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Mik8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo3
LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3Nw
YW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBkZWxpdmVyeSBwYWNrZXQgaXMgZHJv
cHBlZCBiZWNhdXNlIHRoZSBuZXcgZGVzdGluYXRpb24gYWRkcmVzcyBpcyByZWFjaGFibGUsIGJ1
dCB0aGF0IG5vZGUgaXMgbm90IGNvbmZpZ3VyZWQgdG8gcHJvY2VzcyBHUkUgZGVsaXZlcnkgcGFj
a2V0cyBmcm9tIHRoZSBpbmdyZXNzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDouNzVpbjt0ZXh0LWluZGVudDotLjI1
aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4zKTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OywmcXVv
dDtzZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+VGhlIGRlbGl2ZXJ5IHBhY2tl
dCBpcyBwcm9jZXNzZWQgYnkgYSBHUkUgZWdyZXNzIG90aGVyIHRoYW4gdGhhdCB3aGljaCB3YXMg
b3JpZ2luYWxseSBzcGVjaWZpZWQgYnkgdGhlIEdSRSBpbmdyZXNzLiBQcm9jZXNzaW5nIG9wdGlv
bnMgYXJlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4yNWluO3RleHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPmEuPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9z
cGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGUgcGF5bG9hZCBwYWNrZXQgaXMgZHJv
cHBlZCBiZWNhdXNlIHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uIGlzIHVucmVhY2hhYmxlIGZyb20g
dGhlIG5vZGUgdGhhdCBwcm9jZXNzZWQgdGhlIGRlbGl2ZXJ5IHBhY2tldDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MS4yNWluO3RleHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPmIu
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5UaGUgcGF5bG9hZCBwYWNrZXQgaXMgZGVsaXZlcmVkIHRvIGl0cyBpbnRlbmRlZCBkZXN0
aW5hdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4yNWluO3RleHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPmMuPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9z
cGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGUgcGF5bG9hZCBwYWNrZXQgaXMgZXJy
b25lb3VzbHkgZGVsaXZlcmVkIHRvIGEgbm9kZSBvdGhlciB0aGFuIGl0cyBpbnRlbmRlZCBkZXN0
aW5hdGlvbi4gVGhlIGludGVuZGVkIGRlc3RpbmF0aW9uIGFuZCB0aGUgbm9kZSB0byB3aGljaCB0
aGUgcGF5bG9hZCBpcyBhY3R1YWxseSBkZWxpdmVyZWQgYXJlIG51bWJlcmVkIGlkZW50aWNhbGx5
LCBidXQgcmVzaWRlIGluIGRpZmZlcmVudA0KIFZQTnMuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj5PdXRjb21lcyAxKSwgMiksIDNhKSBhbmQgM2IpIGFyZSBhY2NlcHRhYmxl
LiBPdXRjb21lIDNjKSBpcyBub3QgYWNjZXB0YWJsZSwgYnV0IGl0IGV4dHJlbWVseSB1bmxpa2Vs
eS4gQmVjYXVzZSBJUHY2IGFkZHJlc3Mgc3BhY2UgaXMgc28gbGFyZ2UgYW5kIHNvIHNwYXJzZWx5
IHBvcHVsYXRlZCwgb3V0Y29tZSAxKSBpcyBieSBmYXIgdGhlIG1vc3QgcHJvYmFibGUuDQogVGhl
cmVmb3JlLCB0aGUgY29tYmluZWQgbGlrZWxpaG9vZCBvZiBhbGwgYWNjZXB0YWJsZSBvdXRjb21l
cyBieSBmYXIgZXhjZWVkcyB0aGUgbGlrZWxpaG9vZCBvZiB0aGUgb25lIHVuYWNjZXB0YWJsZSBv
dXRjb21lLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5GdXJ0aGVybW9y
ZSwgZXZlbiBpZiB0aGUgcGF5bG9hZCBpcyBlcnJvbmVvdXNseSBkZWxpdmVyZWQgdG8gYSBub2Rl
IG90aGVyIHRoYW4gaXRzIGludGVuZGVkIGRlc3RpbmF0aW9uLCB0aGF0IG5vZGUgd2lsbCBkaXNj
YXJkIHRoZSBwYWNrZXQgaWYgdGhlIHBheWxvYWQgaXMgYWxzbyBjb3JydXB0ZWQgb3IgaWYgdGhl
cmUgYXJlIG5vIGFwcGxpY2F0aW9ucyB3YWl0aW5nDQogdG8gY29uc3VtZSB0aGUgcGFja2V0Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmx0O05FVzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IFJvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
Ymx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBw
dCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gQmxhY2ss
IERhdmlkIFs8YSBocmVmPSJtYWlsdG86ZGF2aWQuYmxhY2tAZW1jLmNvbSI+bWFpbHRvOmRhdmlk
LmJsYWNrQGVtYy5jb208L2E+XQ0KPGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgTWFyY2ggMzAs
IDIwMTUgNzo0OCBQTTxicj4NCjxiPlRvOjwvYj4gUm9uYWxkIEJvbmljYTsgPGEgaHJlZj0ibWFp
bHRvOmludC1hcmVhQGlldGYub3JnIj5pbnQtYXJlYUBpZXRmLm9yZzwvYT47DQo8YSBocmVmPSJt
YWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBpZXRmLm9yZzwvYT48YnI+DQo8Yj5DYzo8L2I+IDxh
IGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmci
PmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzwvYT47DQo8YSBocmVm
PSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPmludGFyZWEtY2hhaXJzQGlldGYub3Jn
PC9hPjsgQmxhY2ssIERhdmlkPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBTdGFydCBvZiBXR0xD
IGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mZ3Q7DQo8L3NwYW4+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkFsc28sIHdoeSB3b3VsZCB5b3Ugb2JqZWN0IHRvIDNiPyBU
aGUgcGFja2V0IGVuZHMgdXAgYXQgdGhlIHJpZ2h0IG5vZGUsIGp1c3QgdmlhIGFuIHVuZXhwZWN0
ZWQgcm91dGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGF0IGFzc2VydGlvbiBpcyBiYXNl
ZCBvbiB0aGUgYXNzdW1wdGlvbiB0aGF0IHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uIGFkZHJlc3Mg
aXMgd29ybGR3aWRlIHVuaXF1ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlRoZXJlIGFyZSBs
b3RzIG9mIGNvdW50ZXJleGFtcGxlcyB0aGF0IHZvaWQgdGhlIGFzc3VtcHRpb24sIGUuZy4sIDEw
LjAuMC4wLzguPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlRoYW5rcyw8
YnI+DQotLURhdmlkPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAw
aW4gMGluIDQuMHB0Ij4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
IGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_2691CE0099834E4A9C5044EEC662BB9D5715558Ddfweml701chm_--


From nobody Wed Apr  1 00:25:49 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6A041AD06F; Tue, 31 Mar 2015 12:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4YiKW8vg1leX; Tue, 31 Mar 2015 12:48:46 -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 5A6641A8853; Tue, 31 Mar 2015 12:48:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQX49925; Tue, 31 Mar 2015 19:48:43 +0000 (GMT)
Received: from DFWEML703-CHM.china.huawei.com (10.193.5.130) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 31 Mar 2015 20:48:43 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml703-chm ([10.193.5.130]) with mapi id 14.03.0158.001; Tue, 31 Mar 2015 12:48:27 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Lucy yong <lucy.yong@huawei.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "Black, David" <david.black@emc.com>
Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAy+K+AAApXc7AAEy4w8A==
Date: Tue, 31 Mar 2015 19:48:26 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D571555B8@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <78DCD4FF-4030-4386-A0CA-7AA5FF1C2E4A@cisco.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.181]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D571555B8dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ou6lFJ2k80VOOT0vYSH8Pc_6BzU>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 19:48:48 -0000

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

DQpIaSBDYXJsb3MsDQoNCkkgYW0gbm90IGNsZWFyIHdoYXQgeW91IHByb3Bvc2UgaGVyZS4gVURQ
IGNoZWNrc3VtIGluY2x1ZGVzIElQIGhlYWRlciwgR1JFIGNoZWNrc3VtIGRvZXMgbm90Lg0KDQpS
ZWdhcmRzLA0KTHVjeQ0KDQpGcm9tOiBDYXJsb3MgUGlnbmF0YXJvIChjcGlnbmF0YSkgW21haWx0
bzpjcGlnbmF0YUBjaXNjby5jb21dDQpTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSAyOjAx
IFBNDQpUbzogQmxhY2ssIERhdmlkOyBMdWN5IHlvbmcNCkNjOiBSb25hbGQgUC4gQm9uaWNhOyBp
bnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3Jn
PG1haWx0bzppcHY2QGlldGYub3JnPjsgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xz
LmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5v
cmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5v
cmc+DQpTdWJqZWN0OiBSZTogW0ludC1hcmVhXSBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjYNCg0KSGksIEx1Y3ksDQoNCk9uZSBhcHByb2FjaCBpcyB0byBhZGQg
YSAzLmMpIHRvIHRoZSBsaXN0IHRoYXQgUm9uIHNoYXJlZC4gSSB0aGluayB0aGVyZSBpcyBhbm90
aGVyIHBvdGVudGlhbCBhcHByb2FjaCB0byB5b3VyIGluaXRpYWwgY29tbWVudDogd2UgY291bGQg
bm90ZSB0aGF0IGZvciBhIHR1bm5lbGluZyBwcm90b2NvbCAoR1JFKSwgdGhpcyBpcyBlcXVpdmFs
ZW50IHRvIHRoZSByZWxheGF0aW9uIG9mIHRoZSBVRFAgY2hlY2tzdW0gaW4gUkZDIDY5MzUsIGFu
ZCBrZWVwIHRoZSBleGlzdGluZyB0ZXh0Lg0KDQpGcmVkLCBSRkMgMjQ3MyBkb2VzIG5vdCBtZW50
aW9uIGNoZWNrc3Vtcy4NCg0KVGhhbmtzLA0KDQpDYXJsb3MuDQoNCg0K

--_000_2691CE0099834E4A9C5044EEC662BB9D571555B8dfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QFNpbVN1biI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv
QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv
b24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNw
YW4uQmFsbG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7
DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQi
Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLmFwcGxlLWNvbnZl
cnRlZC1zcGFjZQ0KCXttc28tc3R5bGUtbmFtZTphcHBsZS1jb252ZXJ0ZWQtc3BhY2U7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHls
ZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdv
cmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4w
aW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48
L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0i
ZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9
ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8
L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8
ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+SGkgQ2FybG9zLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SSBhbSBub3QgY2xlYXIg
d2hhdCB5b3UgcHJvcG9zZTwvc3Bhbj48Yj48aT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+DQo8L3NwYW4+PC9pPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+aGVyZTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+LiBVRFAgY2hlY2tzdW0gaW5jbHVkZXMgSVAgaGVhZGVyPC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4sPC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4NCiBHUkUgPC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5jaGVja3N1bQ0KPC9zcGFuPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5kb2VzIG5vdC4NCjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+THVjeTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+IENhcmxvcyBQaWduYXRhcm8gKGNwaWduYXRhKSBbPGEgaHJlZj0ibWFpbHRvOmNw
aWduYXRhQGNpc2NvLmNvbSI+bWFpbHRvOmNwaWduYXRhQGNpc2NvLmNvbTwvYT5dDQo8YnI+DQo8
Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgMjowMSBQTTxicj4NCjxiPlRvOjwv
Yj4gQmxhY2ssIERhdmlkOyBMdWN5IHlvbmc8YnI+DQo8Yj5DYzo8L2I+IFJvbmFsZCBQLiBCb25p
Y2E7IDxhIGhyZWY9Im1haWx0bzppbnQtYXJlYUBpZXRmLm9yZyI+aW50LWFyZWFAaWV0Zi5vcmc8
L2E+Ow0KPGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciPmlwdjZAaWV0Zi5vcmc8L2E+OyA8
YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3Jn
Ij4NCmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzwvYT47IDxhIGhy
ZWY9Im1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+DQppbnRhcmVhLWNoYWlyc0BpZXRm
Lm9yZzwvYT48YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtJbnQtYXJlYV0gU3RhcnQgb2YgV0dM
QyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGksIEx1Y3ksPG86cD48L286cD48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbmUgYXBwcm9hY2ggaXMgdG8gYWRkIGEgMy5jKSB0byB0
aGUgbGlzdCB0aGF0IFJvbiBzaGFyZWQuIEkgdGhpbmsgdGhlcmUgaXMgYW5vdGhlciBwb3RlbnRp
YWwgYXBwcm9hY2ggdG8geW91ciBpbml0aWFsIGNvbW1lbnQ6IHdlIGNvdWxkIG5vdGUgdGhhdCBm
b3IgYSB0dW5uZWxpbmcgcHJvdG9jb2wgKEdSRSksIHRoaXMgaXMgZXF1aXZhbGVudCB0byB0aGUg
cmVsYXhhdGlvbiBvZiB0aGUgVURQIGNoZWNrc3VtDQogaW4gUkZDJm5ic3A7NjkzNSwgYW5kIGtl
ZXAgdGhlIGV4aXN0aW5nIHRleHQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkZyZWQsIFJGQyAyNDczIGRvZXMgbm90IG1lbnRpb24gY2hlY2tz
dW1zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5UaGFua3MsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPkNhcmxvcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_2691CE0099834E4A9C5044EEC662BB9D571555B8dfweml701chm_--


From nobody Wed Apr  1 00:25:51 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAF21A7011; Tue, 31 Mar 2015 13:42:01 -0700 (PDT)
X-Quarantine-ID: <tx10Tb78ezX8>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...EF40@BLUPR05MB433.namprd05.prod.outlook.com>\n 
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tx10Tb78ezX8; Tue, 31 Mar 2015 13:41:58 -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 8F82B1A8764; Tue, 31 Mar 2015 13:41:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQX52261; Tue, 31 Mar 2015 20:41:54 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 31 Mar 2015 21:41:53 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0158.001; Tue, 31 Mar 2015 13:41:38 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Lucy yong <lucy.yong@huawei.com>, Ronald Bonica <rbonica@juniper.net>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYAAC3xTg
Date: Tue, 31 Mar 2015 20:41:38 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.181]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57155632dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NvosPyEZfJNdcXI5qPoxPUGyqcc>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 20:42:01 -0000

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

SGkgUm9uIGFuZCBDYXJsb3MsDQoNClRoZXJlIGlzIHRoZSBwcm9wb3NlZCB0ZXh0IGZvciB0aGUg
c2Vjb25kIHBhcmFncmFwaCBpbiBTZWN0aW9uIDQuMQ0KDQpCZWNhdXNlIHRoZSBJUHY2IGRlbGl2
ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzIG93biwgaXQgaXMg
c3ViamVjdCB0byBjb3JydXB0aW9uLiAgVGh1cyB0aGUgdXNlIG9mIGdyZSBpbiBJUHY2IG11c3Qg
YmUgaW4gZWl0aGVyIHRoZSBjYXNlIHdoZXJlIGFuIElQdjYgZGVsaXZlcnkgbmV0d29yayBjYW4g
ZW5zdXJlIHBhY2tldCBjb3JydXB0aW9uIGV4dHJlbWVseSB1bmxpa2VseSBvciB0aGUgY2FzZSB3
aGVyZSBHUkUgcGF5bG9hZCBpcyBhYmxlIHRvIHRvbGVyYXRlIHRoZSBwYWNrZXQgY29ycnVwdGlv
bi4NCg0KVGhhbmtzLA0KTHVjeQ0KDQoNCkZyb206IEx1Y3kgeW9uZw0KU2VudDogVHVlc2RheSwg
TWFyY2ggMzEsIDIwMTUgMjoyMyBQTQ0KVG86ICdSb25hbGQgQm9uaWNhJzsgQmxhY2ssIERhdmlk
OyBpbnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZw0KQ2M6IGRyYWZ0LWlldGYtaW50YXJl
YS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmcNClN1Ympl
Y3Q6IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0K
SGkgUm9uLA0KDQozYykgbWF5IGhhcHBlbiBmb3IgYSBWUE4gb3Igbm9uLVZQTiBjYXNlLiBUaGUg
cGF5bG9hZCBjYW4gYmUgaW4gbm9uLUlQdjYgc3BhY2UuICBJcyDigJxPdXRjb21lIDNjKSBpcyBu
b3QgYWNjZXB0YWJsZSwgYnV0IGl0IGV4dHJlbWVseSB1bmxpa2VseS7igJ0gZm9yIHBhcnRpY3Vs
YXIgbmV0d29yay91c2FnZSBpbiB5b3VyIG1pbmQ/DQoNCklzIHRoZSBnb2FsIGhlcmUgdG8gcHJv
dmUgc3VjaCBjb3JydXB0aW9uIGlzIGFjY2VwdGFibGUgb3IgZXh0cmVtZSB1bmxpa2VseT8NCg0K
UmVnYXJkcywNCkx1Y3kNCg0KRnJvbTogSW50LWFyZWEgW21haWx0bzppbnQtYXJlYS1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgUm9uYWxkIEJvbmljYQ0KU2VudDogVHVlc2RheSwgTWFy
Y2ggMzEsIDIwMTUgMTo0MyBQTQ0KVG86IEJsYWNrLCBEYXZpZDsgaW50LWFyZWFAaWV0Zi5vcmc8
bWFpbHRvOmludC1hcmVhQGlldGYub3JnPjsgaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRm
Lm9yZz4NCkNjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFp
bHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEt
Y2hhaXJzQGlldGYub3JnPG1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6
IFJlOiBbSW50LWFyZWFdIFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2Ng0KDQpSZXNlbmTigKYNCg0KRnJvbTogUm9uYWxkIEJvbmljYQ0KU2VudDogVHVlc2RheSwg
TWFyY2ggMzEsIDIwMTUgMjoyMyBQTQ0KVG86ICdCbGFjaywgRGF2aWQnOyBpbnQtYXJlYUBpZXRm
Lm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnPG1haWx0bzppcHY2
QGlldGYub3JnPg0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9y
ZzxtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPjsgaW50
YXJlYS1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnPg0KU3Vi
amVjdDogUkU6IFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0K
DQpEYXZpZCwgTHVjeSwNCg0KWW91IGFyZSBjb3JyZWN0LiAgTWF5YmUgdGhlIGZvbGxvd2luZyB0
ZXh0IHdpbGwgYWRkcmVzcyB0aGUgaXNzdWU6DQoNCk9MRD4NCiAgIEJlY2F1c2UgdGhlIElQdjYg
ZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90IGluY2x1ZGUgYSBjaGVja3N1bSBvZiBpdHMNCiAgIG93
biwgaXQgaXMgc3ViamVjdCB0byBjb3JydXB0aW9uLiAgSG93ZXZlciwgZXZlbiBpZiB0aGUgZGVs
aXZlcnkNCiAgIGhlYWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2VsaWhvb2Qgb2YgdGhhdCBjb3Jy
dXB0aW9uIHJlc3VsdGluZyBpbg0KICAgbWlzZGVsaXZlcnkgb2YgdGhlIHBheWxvYWQgaXMgZXh0
cmVtZWx5IGxvdy4NCjxPTEQNCg0KTkVXPg0KICAgQmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBo
ZWFkZXIgZG9lcyBub3QgaW5jbHVkZSBhIGNoZWNrc3VtIG9mIGl0cw0KICAgb3duLCAgdGhlIGRl
c3RpbmF0aW9uIGFkZHJlc3MgaW4gdGhlIGRlbGl2ZXJ5IGhlYWRlciBpcyBzdWJqZWN0IHRvDQog
ICBjb3JydXB0aW9uLiBJZiB0aGUgZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlciBo
ZWFkZXIgaXMgY29ycnVwdGVkLA0KICAgdGhlIGZvbGxvd2luZyBvdXRjb21lcyBhcmUgcG9zc2li
bGU6DQoNCg0KMSkgICAgICBUaGUgZGVsaXZlcnkgcGFja2V0IGlzIGRyb3BwZWQgYmVjYXVzZSB0
aGUgbmV3IGRlc3RpbmF0aW9uIGFkZHJlc3MgaXMgdW5yZWFjaGFibGUNCg0KMikgICAgICBUaGUg
ZGVsaXZlcnkgcGFja2V0IGlzIGRyb3BwZWQgYmVjYXVzZSB0aGUgbmV3IGRlc3RpbmF0aW9uIGFk
ZHJlc3MgaXMgcmVhY2hhYmxlLCBidXQgdGhhdCBub2RlIGlzIG5vdCBjb25maWd1cmVkIHRvIHBy
b2Nlc3MgR1JFIGRlbGl2ZXJ5IHBhY2tldHMgZnJvbSB0aGUgaW5ncmVzcw0KDQozKSAgICAgIFRo
ZSBkZWxpdmVyeSBwYWNrZXQgaXMgcHJvY2Vzc2VkIGJ5IGEgR1JFIGVncmVzcyBvdGhlciB0aGFu
IHRoYXQgd2hpY2ggd2FzIG9yaWdpbmFsbHkgc3BlY2lmaWVkIGJ5IHRoZSBHUkUgaW5ncmVzcy4g
UHJvY2Vzc2luZyBvcHRpb25zIGFyZToNCg0KYS4gICAgICAgVGhlIHBheWxvYWQgcGFja2V0IGlz
IGRyb3BwZWQgYmVjYXVzZSB0aGUgcGF5bG9hZCBkZXN0aW5hdGlvbiBpcyB1bnJlYWNoYWJsZSBm
cm9tIHRoZSBub2RlIHRoYXQgcHJvY2Vzc2VkIHRoZSBkZWxpdmVyeSBwYWNrZXQNCg0KYi4gICAg
ICBUaGUgcGF5bG9hZCBwYWNrZXQgaXMgZGVsaXZlcmVkIHRvIGl0cyBpbnRlbmRlZCBkZXN0aW5h
dGlvbg0KDQpjLiAgICAgICBUaGUgcGF5bG9hZCBwYWNrZXQgaXMgZXJyb25lb3VzbHkgZGVsaXZl
cmVkIHRvIGEgbm9kZSBvdGhlciB0aGFuIGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbi4gVGhlIGlu
dGVuZGVkIGRlc3RpbmF0aW9uIGFuZCB0aGUgbm9kZSB0byB3aGljaCB0aGUgcGF5bG9hZCBpcyBh
Y3R1YWxseSBkZWxpdmVyZWQgYXJlIG51bWJlcmVkIGlkZW50aWNhbGx5LCBidXQgcmVzaWRlIGlu
IGRpZmZlcmVudCBWUE5zLg0KDQpPdXRjb21lcyAxKSwgMiksIDNhKSBhbmQgM2IpIGFyZSBhY2Nl
cHRhYmxlLiBPdXRjb21lIDNjKSBpcyBub3QgYWNjZXB0YWJsZSwgYnV0IGl0IGV4dHJlbWVseSB1
bmxpa2VseS4gQmVjYXVzZSBJUHY2IGFkZHJlc3Mgc3BhY2UgaXMgc28gbGFyZ2UgYW5kIHNvIHNw
YXJzZWx5IHBvcHVsYXRlZCwgb3V0Y29tZSAxKSBpcyBieSBmYXIgdGhlIG1vc3QgcHJvYmFibGUu
IFRoZXJlZm9yZSwgdGhlIGNvbWJpbmVkIGxpa2VsaWhvb2Qgb2YgYWxsIGFjY2VwdGFibGUgb3V0
Y29tZXMgYnkgZmFyIGV4Y2VlZHMgdGhlIGxpa2VsaWhvb2Qgb2YgdGhlIG9uZSB1bmFjY2VwdGFi
bGUgb3V0Y29tZS4NCg0KRnVydGhlcm1vcmUsIGV2ZW4gaWYgdGhlIHBheWxvYWQgaXMgZXJyb25l
b3VzbHkgZGVsaXZlcmVkIHRvIGEgbm9kZSBvdGhlciB0aGFuIGl0cyBpbnRlbmRlZCBkZXN0aW5h
dGlvbiwgdGhhdCBub2RlIHdpbGwgZGlzY2FyZCB0aGUgcGFja2V0IGlmIHRoZSBwYXlsb2FkIGlz
IGFsc28gY29ycnVwdGVkIG9yIGlmIHRoZXJlIGFyZSBubyBhcHBsaWNhdGlvbnMgd2FpdGluZyB0
byBjb25zdW1lIHRoZSBwYWNrZXQuDQoNCjxORVcNCg0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBSb24NCg0KDQpGcm9tOiBCbGFjaywgRGF2aWQgW21haWx0bzpkYXZpZC5ibGFj
a0BlbWMuY29tXQ0KU2VudDogTW9uZGF5LCBNYXJjaCAzMCwgMjAxNSA3OjQ4IFBNDQpUbzogUm9u
YWxkIEJvbmljYTsgaW50LWFyZWFAaWV0Zi5vcmc8bWFpbHRvOmludC1hcmVhQGlldGYub3JnPjsg
aXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4NCkNjOiBkcmFmdC1pZXRmLWludGFy
ZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEtY2hhaXJzQGlldGYub3JnPG1haWx0bzppbnRh
cmVhLWNoYWlyc0BpZXRmLm9yZz47IEJsYWNrLCBEYXZpZA0KU3ViamVjdDogUkU6IFN0YXJ0IG9m
IFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KDQo+IEFsc28sIHdoeSB3b3Vs
ZCB5b3Ugb2JqZWN0IHRvIDNiPyBUaGUgcGFja2V0IGVuZHMgdXAgYXQgdGhlIHJpZ2h0IG5vZGUs
IGp1c3QgdmlhIGFuIHVuZXhwZWN0ZWQgcm91dGUuDQoNClRoYXQgYXNzZXJ0aW9uIGlzIGJhc2Vk
IG9uIHRoZSBhc3N1bXB0aW9uIHRoYXQgdGhlIHBheWxvYWQgZGVzdGluYXRpb24gYWRkcmVzcyBp
cyB3b3JsZHdpZGUgdW5pcXVlLg0KDQpUaGVyZSBhcmUgbG90cyBvZiBjb3VudGVyZXhhbXBsZXMg
dGhhdCB2b2lkIHRoZSBhc3N1bXB0aW9uLCBlLmcuLCAxMC4wLjAuMC84Lg0KDQpUaGFua3MsDQot
LURhdmlkDQoNCg0K

--_000_2691CE0099834E4A9C5044EEC662BB9D57155632dfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNv
bnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IlxAU2ltU3VuIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30N
Ci8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYu
TXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
MDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojOTU0
RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1z
b1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
bXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiO30NCnANCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJn
aW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1m
YW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZv
bnQtZmFtaWx5OkNvbnNvbGFzO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1z
b0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxs
b29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpw
Lk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdy
YXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4t
cmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1z
dHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpD
b25zb2xhczt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRl
eHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFp
biBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uQmFs
bG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZv
bnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpwLmltcHJpbnR1bmlxdWVpZCwgbGku
aW1wcmludHVuaXF1ZWlkLCBkaXYuaW1wcmludHVuaXF1ZWlkDQoJe21zby1zdHlsZS1uYW1lOmlt
cHJpbnR1bmlxdWVpZDsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbWFyZ2luOjBpbjsNCglt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToi
VGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTI2DQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUyNw0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMx
RjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNw
YW4uRW1haWxTdHlsZTI5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5
bGUzMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzENCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
IjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTMyDQoJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJ
Zm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlv
bjpub25lIG5vbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzMNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdE
O30NCnNwYW4uRW1haWxTdHlsZTM0DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVt
YWlsU3R5bGUzNQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzYN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1z
dHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAx
LjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8
ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPkhpIFJvbiBhbmQgQ2FybG9zLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+VGhlcmUgaXMgdGhlIHByb3Bvc2VkIHRleHQgZm9yIHRoZSBzZWNv
bmQgcGFyYWdyYXBoIGluIFNlY3Rpb24gNC4xPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOIiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+QmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIgZG9lcyBu
b3QgaW5jbHVkZSBhIGNoZWNrc3VtIG9mIGl0cyBvd24sIGl0IGlzIHN1YmplY3QgdG8gY29ycnVw
dGlvbi4mbmJzcDsgVGh1cyB0aGUgdXNlIG9mIGdyZSBpbiBJUHY2IG11c3QgYmUgaW4gZWl0aGVy
IHRoZSBjYXNlIHdoZXJlIGFuIElQdjYgZGVsaXZlcnkgbmV0d29yayBjYW4gZW5zdXJlDQogcGFj
a2V0IGNvcnJ1cHRpb24gZXh0cmVtZWx5IHVubGlrZWx5IG9yIHRoZSBjYXNlIHdoZXJlIEdSRSBw
YXlsb2FkIGlzIGFibGUgdG8gdG9sZXJhdGUgdGhlIHBhY2tldCBjb3JydXB0aW9uLiAmbmJzcDsm
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTiIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+VGhhbmtzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+THVjeTxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNC
NUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gTHVjeSB5b25nDQo8YnI+DQo8Yj5TZW50OjwvYj4gVHVl
c2RheSwgTWFyY2ggMzEsIDIwMTUgMjoyMyBQTTxicj4NCjxiPlRvOjwvYj4gJ1JvbmFsZCBCb25p
Y2EnOyBCbGFjaywgRGF2aWQ7IGludC1hcmVhQGlldGYub3JnOyBpcHY2QGlldGYub3JnPGJyPg0K
PGI+Q2M6PC9iPiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc7IGlu
dGFyZWEtY2hhaXJzQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBTdGFydCBvZiBX
R0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SGkg
Um9uLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+M2MpIG1heSBoYXBwZW4g
Zm9yIGEgVlBOIG9yIG5vbi1WUE4gY2FzZS4gVGhlIHBheWxvYWQgY2FuIGJlIGluIG5vbi1JUHY2
IHNwYWNlLiAmbmJzcDtJcyDigJxPdXRjb21lIDNjKSBpcyBub3QgYWNjZXB0YWJsZSwgYnV0IGl0
IGV4dHJlbWVseSB1bmxpa2VseS7igJ0gZm9yIHBhcnRpY3VsYXIgbmV0d29yay91c2FnZSBpbiB5
b3VyIG1pbmQ/DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPklzIHRoZSBn
b2FsIGhlcmUgdG8gcHJvdmUgc3VjaCBjb3JydXB0aW9uIGlzIGFjY2VwdGFibGUgb3IgZXh0cmVt
ZSB1bmxpa2VseT8mbmJzcDsgJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5MdWN5PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8
L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gSW50LWFyZWEgWzxhIGhyZWY9
Im1haWx0bzppbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnIj5tYWlsdG86aW50LWFyZWEtYm91bmNl
c0BpZXRmLm9yZzwvYT5dDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlJvbmFsZCBCb25pY2E8YnI+DQo8
Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgMTo0MyBQTTxicj4NCjxiPlRvOjwv
Yj4gQmxhY2ssIERhdmlkOyA8YSBocmVmPSJtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmciPmludC1h
cmVhQGlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGll
dGYub3JnPC9hPjxicj4NCjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtaW50
YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZyI+ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2
QHRvb2xzLmlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRm
Lm9yZyI+aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJl
OiBbSW50LWFyZWFdIFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2
NjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj5SZXNlbmTigKY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29s
aWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gUm9u
YWxkIEJvbmljYSA8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgMjoy
MyBQTTxicj4NCjxiPlRvOjwvYj4gJ0JsYWNrLCBEYXZpZCc7IDxhIGhyZWY9Im1haWx0bzppbnQt
YXJlYUBpZXRmLm9yZyI+aW50LWFyZWFAaWV0Zi5vcmc8L2E+Ow0KPGEgaHJlZj0ibWFpbHRvOmlw
djZAaWV0Zi5vcmciPmlwdjZAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJt
YWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnIj5kcmFmdC1p
ZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8L2E+Ow0KPGEgaHJlZj0ibWFpbHRv
OmludGFyZWEtY2hhaXJzQGlldGYub3JnIj5pbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzwvYT48YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUkU6IFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJl
YS1ncmUtaXB2NjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRhdmlkLCBMdWN5LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+WW91IGFyZSBjb3JyZWN0LiAmbmJzcDtNYXliZSB0aGUgZm9sbG93aW5n
IHRleHQgd2lsbCBhZGRyZXNzIHRoZSBpc3N1ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPk9MRCZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IEJlY2F1c2UgdGhl
IElQdjYgZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90IGluY2x1ZGUgYSBjaGVja3N1bSBvZiBpdHM8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IG93biwgaXQgaXMgc3ViamVjdCB0byBjb3JydXB0
aW9uLiZuYnNwOyBIb3dldmVyLCBldmVuIGlmIHRoZSBkZWxpdmVyeTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4m
bmJzcDsmbmJzcDsgaGVhZGVyIGlzIGNvcnJ1cHRlZCwgdG8gbGlrZWxpaG9vZCBvZiB0aGF0IGNv
cnJ1cHRpb24gcmVzdWx0aW5nIGluPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBtaXNkZWxp
dmVyeSBvZiB0aGUgcGF5bG9hZCBpcyBleHRyZW1lbHkgbG93LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbHQ7
T0xEPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5ORVcmZ3Q7PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPiZuYnNwOyZuYnNwOyBCZWNhdXNlIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBkb2Vz
IG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNw
OyBvd24sICZuYnNwO3RoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBkZWxpdmVyeSBoZWFk
ZXIgaXMgc3ViamVjdCB0bw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwO2NvcnJ1
cHRpb24uIElmIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBkZWxpdmVyIGhlYWRlciBp
cyBjb3JydXB0ZWQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyB0aGUgZm9sbG93aW5nIG91
dGNvbWVzIGFyZSBwb3NzaWJsZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDou
NzVpbjt0ZXh0LWluZGVudDotLjI1aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4xKTwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVz
IE5ldyBSb21hbiZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3
RCI+VGhlIGRlbGl2ZXJ5IHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5h
dGlvbiBhZGRyZXNzIGlzIHVucmVhY2hhYmxlPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDouNzVpbjt0ZXh0LWluZGVu
dDotLjI1aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4yKTwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90
OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+VGhlIGRlbGl2ZXJ5
IHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2UgdGhlIG5ldyBkZXN0aW5hdGlvbiBhZGRyZXNzIGlz
IHJlYWNoYWJsZSwgYnV0IHRoYXQgbm9kZSBpcyBub3QgY29uZmlndXJlZCB0byBwcm9jZXNzIEdS
RSBkZWxpdmVyeSBwYWNrZXRzIGZyb20gdGhlIGluZ3Jlc3M8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi43NWluO3Rl
eHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjMpPC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJv
bWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGUg
ZGVsaXZlcnkgcGFja2V0IGlzIHByb2Nlc3NlZCBieSBhIEdSRSBlZ3Jlc3Mgb3RoZXIgdGhhbiB0
aGF0IHdoaWNoIHdhcyBvcmlnaW5hbGx5IHNwZWNpZmllZCBieSB0aGUgR1JFIGluZ3Jlc3MuIFBy
b2Nlc3Npbmcgb3B0aW9ucyBhcmU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjI1aW47dGV4dC1pbmRlbnQ6LS4y
NWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+YS48L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1
b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBwYXlsb2Fk
IHBhY2tldCBpcyBkcm9wcGVkIGJlY2F1c2UgdGhlIHBheWxvYWQgZGVzdGluYXRpb24gaXMgdW5y
ZWFjaGFibGUgZnJvbSB0aGUgbm9kZSB0aGF0IHByb2Nlc3NlZCB0aGUgZGVsaXZlcnkgcGFja2V0
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxl
PSJtYXJnaW4tbGVmdDoxLjI1aW47dGV4dC1pbmRlbnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+Yi48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo3LjBwdDtmb250LWZh
bWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBwYXlsb2FkIHBhY2tldCBpcyBkZWxpdmVyZWQgdG8gaXRz
IGludGVuZGVkIGRlc3RpbmF0aW9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjI1aW47dGV4dC1pbmRlbnQ6LS4y
NWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Yy48L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1
b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBwYXlsb2Fk
IHBhY2tldCBpcyBlcnJvbmVvdXNseSBkZWxpdmVyZWQgdG8gYSBub2RlIG90aGVyIHRoYW4gaXRz
IGludGVuZGVkIGRlc3RpbmF0aW9uLiBUaGUgaW50ZW5kZWQgZGVzdGluYXRpb24gYW5kIHRoZSBu
b2RlIHRvIHdoaWNoIHRoZSBwYXlsb2FkIGlzIGFjdHVhbGx5IGRlbGl2ZXJlZCBhcmUgbnVtYmVy
ZWQgaWRlbnRpY2FsbHksIGJ1dCByZXNpZGUgaW4gZGlmZmVyZW50DQogVlBOcy48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPk91dGNvbWVzIDEpLCAyKSwgM2EpIGFuZCAzYikg
YXJlIGFjY2VwdGFibGUuIE91dGNvbWUgM2MpIGlzIG5vdCBhY2NlcHRhYmxlLCBidXQgaXQgZXh0
cmVtZWx5IHVubGlrZWx5LiBCZWNhdXNlIElQdjYgYWRkcmVzcyBzcGFjZSBpcyBzbyBsYXJnZSBh
bmQgc28gc3BhcnNlbHkgcG9wdWxhdGVkLCBvdXRjb21lIDEpIGlzIGJ5IGZhciB0aGUgbW9zdCBw
cm9iYWJsZS4NCiBUaGVyZWZvcmUsIHRoZSBjb21iaW5lZCBsaWtlbGlob29kIG9mIGFsbCBhY2Nl
cHRhYmxlIG91dGNvbWVzIGJ5IGZhciBleGNlZWRzIHRoZSBsaWtlbGlob29kIG9mIHRoZSBvbmUg
dW5hY2NlcHRhYmxlIG91dGNvbWUuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPkZ1cnRoZXJtb3JlLCBldmVuIGlmIHRoZSBwYXlsb2FkIGlzIGVycm9uZW91c2x5IGRlbGl2
ZXJlZCB0byBhIG5vZGUgb3RoZXIgdGhhbiBpdHMgaW50ZW5kZWQgZGVzdGluYXRpb24sIHRoYXQg
bm9kZSB3aWxsIGRpc2NhcmQgdGhlIHBhY2tldCBpZiB0aGUgcGF5bG9hZCBpcyBhbHNvIGNvcnJ1
cHRlZCBvciBpZiB0aGVyZSBhcmUgbm8gYXBwbGljYXRpb25zIHdhaXRpbmcNCiB0byBjb25zdW1l
IHRoZSBwYWNrZXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbHQ7TkVX
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgUm9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRp
dj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBw
dDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZy
b206PC9iPiBCbGFjaywgRGF2aWQgWzxhIGhyZWY9Im1haWx0bzpkYXZpZC5ibGFja0BlbWMuY29t
Ij5tYWlsdG86ZGF2aWQuYmxhY2tAZW1jLmNvbTwvYT5dDQo8YnI+DQo8Yj5TZW50OjwvYj4gTW9u
ZGF5LCBNYXJjaCAzMCwgMjAxNSA3OjQ4IFBNPGJyPg0KPGI+VG86PC9iPiBSb25hbGQgQm9uaWNh
OyA8YSBocmVmPSJtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmciPmludC1hcmVhQGlldGYub3JnPC9h
PjsNCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGlldGYub3JnPC9hPjxicj4N
CjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0
b29scy5pZXRmLm9yZyI+ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3Jn
PC9hPjsNCjxhIGhyZWY9Im1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+aW50YXJlYS1j
aGFpcnNAaWV0Zi5vcmc8L2E+OyBCbGFjaywgRGF2aWQ8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6
IFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZndDsN
Cjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+QWxzbywgd2h5IHdvdWxkIHlvdSBv
YmplY3QgdG8gM2I/IFRoZSBwYWNrZXQgZW5kcyB1cCBhdCB0aGUgcmlnaHQgbm9kZSwganVzdCB2
aWEgYW4gdW5leHBlY3RlZCByb3V0ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlRoYXQgYXNz
ZXJ0aW9uIGlzIGJhc2VkIG9uIHRoZSBhc3N1bXB0aW9uIHRoYXQgdGhlIHBheWxvYWQgZGVzdGlu
YXRpb24gYWRkcmVzcyBpcyB3b3JsZHdpZGUgdW5pcXVlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+VGhlcmUgYXJlIGxvdHMgb2YgY291bnRlcmV4YW1wbGVzIHRoYXQgdm9pZCB0aGUgYXNzdW1w
dGlvbiwgZS5nLiwgMTAuMC4wLjAvOC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+VGhhbmtzLDxicj4NCi0tRGF2aWQ8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBw
dCI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0
O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_2691CE0099834E4A9C5044EEC662BB9D57155632dfweml701chm_--


From nobody Wed Apr  1 00:25:52 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4EEA1A1BFA; Tue, 31 Mar 2015 16:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zWizClA7aPOT; Tue, 31 Mar 2015 16:35:04 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 6F75D1A1BC3; Tue, 31 Mar 2015 16:35:04 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2VNZ23A013354 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2015 19:35:02 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com t2VNZ23A013354
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427844903; bh=JncsuxU/MmM89a1bUdKQCZH/L50=; h=From:To:CC:Subject:Date:Message-ID:Content-Type:MIME-Version; b=XxK/7OabUxAba9G+o4XDavK5c/nOnine+h4USYdWkIjrfXCRmouOf5DpC67kszoYv cYxkuj9M6Bc5QbrIeUgHR7hnI4wOPrCcbsbVshq3R5QkMFweUCXQIxA9izTC2bo5Ar eDpIMkkw9tmsYAoFmUCDp8ru3foBs52yYWh6TW9c=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com t2VNZ23A013354
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd05.lss.emc.com (RSA Interceptor); Tue, 31 Mar 2015 19:34:29 -0400
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2VNYibm014573 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 19:34:45 -0400
Received: from MXHUB204.corp.emc.com (10.253.68.30) by mxhub34.corp.emc.com (10.254.93.82) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 31 Mar 2015 19:34:44 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB204.corp.emc.com ([10.253.68.30]) with mapi id 14.03.0224.002; Tue, 31 Mar 2015 19:34:43 -0400
From: "Black, David" <david.black@emc.com>
To: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Topic: WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Index: AdBsC0O9ImygMEJJSjuvdoFVvO3XwA==
Date: Tue, 31 Mar 2015 23:34:43 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949364312D6@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949364312D6MX104CL02corpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Q6y9_2SpwQC4f-cXUMELJy7jrhY>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 23:35:06 -0000
X-List-Received-Date: Tue, 31 Mar 2015 23:35:06 -0000

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

U2VjdGlvbiAyLjIgc2F5czoNCg0KICAgVGhlIFByb3RvY29sIFR5cGUgZmllbGQgY29udGFpbnMg
dGhlIHByb3RvY29sIHR5cGUgb2YgdGhlIHBheWxvYWQNCiAgIHBhY2tldC4gIFByb3RvY29sIFR5
cGVzIGFyZSBkZWZpbmVkIGluIFtFVFlQRVNdLiAgQW4gaW1wbGVtZW50YXRpb24NCiAgIHJlY2Vp
dmluZyBhIHBhY2tldCBjb250YWluaW5nIGEgUHJvdG9jb2wgVHlwZSB3aGljaCBpcyBub3QgbGlz
dGVkIGluDQogICBbRVRZUEVTXSBTSE9VTEQgZGlzY2FyZCB0aGUgcGFja2V0Lg0KDQpUaGF0IGxh
dHRlciBzZW50ZW5jZSBpcyBhbG1vc3QgcG9pbnRsZXNzLCBhbmQgbW9yZW92ZXIsIGl04oCZcyBh
bg0KdW5pbXBsZW1lbnRhYmxlIG1vdmluZyB0YXJnZXQuDQoNCkNvdWxkIHdlIHNheSB0aGF0IGFu
eSBHUkUgaW1wbGVtZW50YXRpb24gU0hPVUxEIGJlIGNvbmZpZ3VyZWQgd2l0aA0KdGhlIFByb3Rv
Y29sIFR5cGVzIHRoYXQgYXJlIGV4cGVjdGVkIGFuZCBTSE9VTEQgZGlzY2FyZCBhbnkgcGFja2V0
DQp0aGF0IGFycml2ZXMgd2l0aCBhbiB1bmV4cGVjdGVkIHByb3RvY29sIHR5cGU/DQoNCkkgd291
bGQgdGhpbmsgdGhhdCB0aGUgbnVtYmVyIG9mIGV4cGVjdGVkIHByb3RvY29sIHR5cGVzIGlzIHR5
cGljYWxseQ0KYSBzbWFsbCBudW1iZXIsIGFuZCB0aGF0IGNoZWNrIHByb3RlY3RzIGFnYWluc3Qg
bWlzaW50ZXJwcmV0aW5nIGEgaGVhZGVyDQpmb3IgZW5jYXBzdWxhdGVkIHByb3RvY29sIEEgYXMg
YSBoZWFkZXIgZm9yIGVuY2Fwc3VsYXRlZCBwcm90b2NvbCBCLA0Kd2hpY2ggdXN1YWxseSB3b27i
gJl0IGFjY29tcGxpc2ggbXVjaCwgYnV0IGNvdWxkIG9jY2FzaW9uYWxseSBjYXVzZQ0KcmF0aGVy
IHVuZGVzaXJhYmxlIHJlc3VsdHMuDQoNCkkgcmVhbGl6ZSB0aGF0IHRoaXMgdGV4dCB3YXMgY29w
aWVkIGZyb20gUkZDIDI3ODQsIGFuZCB0aGF0IGNvdWxkIGJlDQphIHJlYXNvbiB0byBub3QgbWFr
ZSB0aGlzIGNoYW5nZS4NCg0KVGhhbmtzLA0KLS1EYXZpZA0KDQpGcm9tOiBJbnQtYXJlYSBbbWFp
bHRvOmludC1hcmVhLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBadW5pZ2EsIEp1YW4g
Q2FybG9zDQpTZW50OiBNb25kYXksIE1hcmNoIDMwLCAyMDE1IDQ6MjcgUE0NClRvOiBpbnQtYXJl
YUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZw0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2
NkB0b29scy5pZXRmLm9yZzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFtJbnQt
YXJlYV0gU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQoNCg0K
RGVhciBJbnQtQXJlYSBhbmQgNm1hbiBXR3MsDQoNCg0KDQpBdCB0aGUgSW50LUFyZWEgV0cgbWVl
dGluZyBpbiBEYWxsYXMgdGhlcmUgd2VyZSBzb21lIGNvbW1lbnRzIG9uIGRyYWZ0LWlldGYtaW50
YXJlYS1ncmUtaXB2Ni4gSXQgd2FzIGRlY2lkZWQgdG8gc3VibWl0IHRoZSBkb2N1bWVudCBmb3Ig
V0cgTGFzdCBDYWxsIHRvIHRoZSBJbnQtQXJlYSAmIDZtYW4gV0dzIGFzIHNvb24gYXMgdGhlIGFn
cmVlZCBjaGFuZ2VzIHdlcmUgbWFkZS4NCg0KDQoNClRoZSBkb2N1bWVudCBoYXMgbm93IGJlZW4g
dXBkYXRlZCBhY2NvcmRpbmdseSwgc28gdGhpcyBlbWFpbCBzdGFydHMgYW4gSW50LUFyZWEvNm1h
biBXR3MgTGFzdCBDYWxsIG9uOg0KDQoNCg0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LTA0DQoNCg0KDQpQbGVhc2UgcmVzcG9uZCB0byB0aGlz
IGVtYWlsIHRvIHN1cHBvcnQgdGhlIGRvY3VtZW50IGFuZC9vciBzZW5kIGNvbW1lbnRzIGJ5IDIw
MTUtMDQtMDYuDQoNCg0KDQpJbiBhZGRpdGlvbiwgdG8gc2F0aXNmeSBSRkMgNjcwMiAiUHJvbW90
aW5nIENvbXBsaWFuY2Ugd2l0aCBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIChJUFIpIjoN
Cg0KQXJlIHlvdSBwZXJzb25hbGx5IGF3YXJlIG9mIGFueSBJUFIgdGhhdCBhcHBsaWVzIHRvIGRy
YWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Nj8NCg0KSWYgc28sIGhhcyB0aGlzIElQUiBiZWVuIGRp
c2Nsb3NlZCBpbiBjb21wbGlhbmNlIHdpdGggSUVURiBJUFIgcnVsZXM/DQoNCihTZWUgUkZDcyAz
OTc5LCA0ODc5LCAzNjY5LCBhbmQgNTM3OCBmb3IgbW9yZSBkZXRhaWxzLikNCg0KDQoNCkJlc3Qs
DQoNCg0KDQpKdWFuIENhcmxvcyBadW5pZ2ENCihhcyBJbnQtQXJlYSBXRyBjby1jaGFpcikNCg0K

--_000_CE03DB3D7B45C245BCA0D243277949364312D6MX104CL02corpemcc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1
NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3
MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29Q
bGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFt
aWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KcC5pbXByaW50dW5pcXVlaWQsIGxpLmlt
cHJpbnR1bmlxdWVpZCwgZGl2LmltcHJpbnR1bmlxdWVpZA0KCXttc28tc3R5bGUtbmFtZTppbXBy
aW50dW5pcXVlaWQ7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9u
dC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30N
CnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjAN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTIyDQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJ
Y29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0K
CXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlv
bjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGlu
O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNw
aWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBk
YXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0K
PGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYg
Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+U2VjdGlvbiAyLjIgc2F5czo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNw
OyZuYnNwOyBUaGUgUHJvdG9jb2wgVHlwZSBmaWVsZCBjb250YWlucyB0aGUgcHJvdG9jb2wgdHlw
ZSBvZiB0aGUgcGF5bG9hZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgcGFja2V0LiZuYnNwOyBQcm90
b2NvbCBUeXBlcyBhcmUgZGVmaW5lZCBpbiBbRVRZUEVTXS4mbmJzcDsgQW4gaW1wbGVtZW50YXRp
b248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IHJlY2VpdmluZyBhIHBhY2tldCBjb250YWluaW5nIGEg
UHJvdG9jb2wgVHlwZSB3aGljaCBpcyBub3QgbGlzdGVkIGluPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNw
OyBbRVRZUEVTXSBTSE9VTEQgZGlzY2FyZCB0aGUgcGFja2V0LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+VGhhdCBsYXR0ZXIgc2VudGVuY2UgaXMgYWxtb3N0IHBvaW50bGVzcywgYW5kIG1vcmVv
dmVyLCBpdOKAmXMgYW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+dW5pbXBsZW1lbnRhYmxlIG1vdmluZyB0YXJnZXQuPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5Db3VsZCB3ZSBzYXkgdGhhdCBhbnkgR1JFIGltcGxlbWVu
dGF0aW9uIFNIT1VMRCBiZSBjb25maWd1cmVkIHdpdGg8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+dGhlIFByb3RvY29sIFR5
cGVzIHRoYXQgYXJlIGV4cGVjdGVkIGFuZCBTSE9VTEQgZGlzY2FyZCBhbnkgcGFja2V0PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6Ymxh
Y2siPnRoYXQgYXJyaXZlcyB3aXRoIGFuIHVuZXhwZWN0ZWQgcHJvdG9jb2wgdHlwZT8mbmJzcDsN
CjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2Nv
bG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SSB3b3VsZCB0aGluayB0aGF0IHRoZSBudW1iZXIg
b2YgZXhwZWN0ZWQgcHJvdG9jb2wgdHlwZXMgaXMgdHlwaWNhbGx5PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPmEgc21hbGwg
bnVtYmVyLCBhbmQgdGhhdCBjaGVjayBwcm90ZWN0cyBhZ2FpbnN0IG1pc2ludGVycHJldGluZyBh
IGhlYWRlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7O2NvbG9yOmJsYWNrIj5mb3IgZW5jYXBzdWxhdGVkIHByb3RvY29sIEEgYXMgYSBoZWFkZXIg
Zm9yIGVuY2Fwc3VsYXRlZCBwcm90b2NvbCBCLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj53aGljaCB1c3VhbGx5IHdvbuKA
mXQgYWNjb21wbGlzaCBtdWNoLCBidXQgY291bGQgb2NjYXNpb25hbGx5IGNhdXNlPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PnJhdGhlciB1bmRlc2lyYWJsZSByZXN1bHRzLjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5JIHJlYWxp
emUgdGhhdCB0aGlzIHRleHQgd2FzIGNvcGllZCBmcm9tIFJGQyAyNzg0LCBhbmQgdGhhdCBjb3Vs
ZCBiZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOmJsYWNrIj5hIHJlYXNvbiB0byBub3QgbWFrZSB0aGlzIGNoYW5nZS48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+VGhhbmtzLDxicj4NCi0tRGF2aWQ8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7
cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IEludC1hcmVhIFtt
YWlsdG86aW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+WnVu
aWdhLCBKdWFuIENhcmxvczxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIE1hcmNoIDMwLCAyMDE1
IDQ6MjcgUE08YnI+DQo8Yj5Ubzo8L2I+IGludC1hcmVhQGlldGYub3JnOyBpcHY2QGlldGYub3Jn
PGJyPg0KPGI+Q2M6PC9iPiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5v
cmc7IGludGFyZWEtY2hhaXJzQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFtJbnQtYXJl
YV0gU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+RGVhciBJbnQtQXJlYSBh
bmQgNm1hbiBXR3MsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkF0IHRoZSBJbnQtQXJl
YSBXRyBtZWV0aW5nIGluIERhbGxhcyB0aGVyZSB3ZXJlIHNvbWUgY29tbWVudHMgb24gZHJhZnQt
aWV0Zi1pbnRhcmVhLWdyZS1pcHY2LiBJdCB3YXMgZGVjaWRlZCB0byBzdWJtaXQgdGhlIGRvY3Vt
ZW50IGZvciBXRyBMYXN0IENhbGwgdG8gdGhlIEludC1BcmVhICZhbXA7IDZtYW4gV0dzIGFzIHNv
b24gYXMgdGhlIGFncmVlZCBjaGFuZ2VzIHdlcmUgbWFkZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+VGhlIGRvY3VtZW50IGhhcyBub3cgYmVlbiB1cGRhdGVkIGFjY29yZGluZ2x5LCBz
byB0aGlzIGVtYWlsIHN0YXJ0cyBhbiBJbnQtQXJlYS82bWFuIFdHcyBMYXN0IENhbGwgb246PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni0wNCI+aHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LTA0PC9hPg0KPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPlBsZWFzZSByZXNwb25kIHRvIHRoaXMgZW1haWwgdG8gc3VwcG9y
dCB0aGUgZG9jdW1lbnQgYW5kL29yIHNlbmQgY29tbWVudHMgYnkgMjAxNS0wNC0wNi48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+SW4gYWRkaXRpb24sIHRvIHNhdGlzZnkgUkZDIDY3MDIg
JnF1b3Q7UHJvbW90aW5nIENvbXBsaWFuY2Ugd2l0aCBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmln
aHRzIChJUFIpJnF1b3Q7OjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
QXJlIHlvdSBwZXJzb25hbGx5IGF3YXJlIG9mIGFueSBJUFIgdGhhdCBhcHBsaWVzIHRvIGRyYWZ0
LWlldGYtaW50YXJlYS1ncmUtaXB2Nj8mbmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+SWYgc28sIGhhcyB0aGlzIElQUiBiZWVuIGRpc2Nsb3NlZCBpbiBjb21w
bGlhbmNlIHdpdGggSUVURiBJUFIgcnVsZXM/PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4oU2VlIFJGQ3MgMzk3OSwgNDg3OSwgMzY2OSwgYW5kIDUzNzggZm9yIG1vcmUg
ZGV0YWlscy4pPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkJlc3QsPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPkp1YW4gQ2FybG9zIFp1bmlnYSA8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPihhcyBJbnQtQXJlYSBXRyBjby1jaGFpcik8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CE03DB3D7B45C245BCA0D243277949364312D6MX104CL02corpemcc_--


From nobody Wed Apr  1 00:25:53 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01A51B29E8; Tue, 31 Mar 2015 17:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gofKjFscz2WL; Tue, 31 Mar 2015 17:59:06 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (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 023D51B29E2; Tue, 31 Mar 2015 17:59:05 -0700 (PDT)
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 t310x2eu027417 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2015 20:59:04 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com t310x2eu027417
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427849944; bh=IRtZBonfxwWnNfEu+qY11OQHGxA=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=wphwE0woffhXugbTeC8GQtAsXTGf0P1b+pMhNZ6ZUXdUezXyyw51IiOmiofSf8VpC 2KUuSkg6e5LEwxuJhqAS9uiFroPryTpHkRvxTeph1JaptzrCvnv8e4aEqdC4TOiZU+ Xc0CKAJjcW1AF2+lBc9EiGww4ZSimtHf1Xeum85c=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com t310x2eu027417
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 31 Mar 2015 20:57:03 -0400
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com [10.254.92.105]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t310wlxV017007 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 20:58:48 -0400
Received: from MXHUB204.corp.emc.com (10.253.68.30) by mxhub10.corp.emc.com (10.254.92.105) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 31 Mar 2015 20:58:47 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB204.corp.emc.com ([10.253.68.30]) with mapi id 14.03.0224.002; Tue, 31 Mar 2015 20:58:47 -0400
From: "Black, David" <david.black@emc.com>
To: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Topic: WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Index: AdBsC0O9ImygMEJJSjuvdoFVvO3XwAACaYSQAABqGzA=
Date: Wed, 1 Apr 2015 00:58:46 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936431400@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949364312D6@MX104CL02.corp.emc.com> <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D24327794936431400MX104CL02corpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/F921ySMt3glNwMKZWmmKwcW1oCQ>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 00:59:08 -0000
X-List-Received-Date: Wed, 01 Apr 2015 00:59:08 -0000

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

VGhhdCBzZWVtcyByZWFzb25hYmxlIC0gdGhlIHByb3ZlcmJpYWwg4oCccmlnaHQgdGhpbmcgdG8g
ZG/igJ0gd291bGQgYmUgdG8gdXBkYXRlIDI3ODQgdG8gYXBwbHkgdGhpcyByZWNvbW1lbmRhdGlv
biBhY3Jvc3MgdGhlIGJvYXJkLCBidXQgSeKAmW0gb2sgd2l0aCBzaW1wbHkgcmVtb3ZpbmcgdGhl
IFNlY3Rpb24gMi4yIHRleHQgYW5kIGxlYXZpbmcgdGhpbmdzIGFzIHRoZXkgYXJlIGluIDI3ODQu
DQoNClRoYW5rcywNCi0tRGF2aWQNCg0KRnJvbTogUm9uYWxkIEJvbmljYSBbbWFpbHRvOnJib25p
Y2FAanVuaXBlci5uZXRdDQpTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSA4OjUzIFBNDQpU
bzogQmxhY2ssIERhdmlkOyBadW5pZ2EsIEp1YW4gQ2FybG9zOyBpbnQtYXJlYUBpZXRmLm9yZzsg
aXB2NkBpZXRmLm9yZw0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRm
Lm9yZzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFJFOiBXR0xDIGZvciBkcmFm
dC1pZXRmLWludGFyZWEtZ3JlLWlwdjYgLSBFdGhlcnR5cGVzDQoNCkRhdmlkLA0KDQpPbmUgd2F5
IHRvIGFkZHJlc3MgdGhpcyBwcm9ibGVtIHdvdWxkIGJlIHRvIHJlbW92ZSBTZWN0aW9uIDIuMiBl
bnRpcmVseS4gU2luY2UgdGhlIHN5bnRheCBhbmQgc2VtYW50aWNzIG9mIHRoZSBQcm90b2NvbCBU
eXBlIGZpZWxkIGlzIHVuY2hhbmdlZCBmcm9tIFJGQyAyNzg0LCB0aGUgb21pc3Npb24gb2YgU2Vj
dGlvbiAyLjIgZG9lc27igJl0IGNoYW5nZSB0aGUgbWVhbmluZyBvZiB0aGUgZHJhZnQgYXQgYWxs
Lg0KDQpXb3VsZCB0aGF0IHNvbHV0aW9uIHdvcmsgZm9yIHlvdT8NCg0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9u
DQoNCg0KRnJvbTogQmxhY2ssIERhdmlkIFttYWlsdG86ZGF2aWQuYmxhY2tAZW1jLmNvbV0NClNl
bnQ6IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDc6MzUgUE0NClRvOiBadW5pZ2EsIEp1YW4gQ2Fy
bG9zOyBpbnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGll
dGYub3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2NkB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRv
b2xzLmlldGYub3JnPjsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hh
aXJzQGlldGYub3JnPjsgQmxhY2ssIERhdmlkDQpTdWJqZWN0OiBXR0xDIGZvciBkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjYgLSBFdGhlcnR5cGVzDQoNClNlY3Rpb24gMi4yIHNheXM6DQoNCiAg
IFRoZSBQcm90b2NvbCBUeXBlIGZpZWxkIGNvbnRhaW5zIHRoZSBwcm90b2NvbCB0eXBlIG9mIHRo
ZSBwYXlsb2FkDQogICBwYWNrZXQuICBQcm90b2NvbCBUeXBlcyBhcmUgZGVmaW5lZCBpbiBbRVRZ
UEVTXS4gIEFuIGltcGxlbWVudGF0aW9uDQogICByZWNlaXZpbmcgYSBwYWNrZXQgY29udGFpbmlu
ZyBhIFByb3RvY29sIFR5cGUgd2hpY2ggaXMgbm90IGxpc3RlZCBpbg0KICAgW0VUWVBFU10gU0hP
VUxEIGRpc2NhcmQgdGhlIHBhY2tldC4NCg0KVGhhdCBsYXR0ZXIgc2VudGVuY2UgaXMgYWxtb3N0
IHBvaW50bGVzcywgYW5kIG1vcmVvdmVyLCBpdOKAmXMgYW4NCnVuaW1wbGVtZW50YWJsZSBtb3Zp
bmcgdGFyZ2V0Lg0KDQpDb3VsZCB3ZSBzYXkgdGhhdCBhbnkgR1JFIGltcGxlbWVudGF0aW9uIFNI
T1VMRCBiZSBjb25maWd1cmVkIHdpdGgNCnRoZSBQcm90b2NvbCBUeXBlcyB0aGF0IGFyZSBleHBl
Y3RlZCBhbmQgU0hPVUxEIGRpc2NhcmQgYW55IHBhY2tldA0KdGhhdCBhcnJpdmVzIHdpdGggYW4g
dW5leHBlY3RlZCBwcm90b2NvbCB0eXBlPw0KDQpJIHdvdWxkIHRoaW5rIHRoYXQgdGhlIG51bWJl
ciBvZiBleHBlY3RlZCBwcm90b2NvbCB0eXBlcyBpcyB0eXBpY2FsbHkNCmEgc21hbGwgbnVtYmVy
LCBhbmQgdGhhdCBjaGVjayBwcm90ZWN0cyBhZ2FpbnN0IG1pc2ludGVycHJldGluZyBhIGhlYWRl
cg0KZm9yIGVuY2Fwc3VsYXRlZCBwcm90b2NvbCBBIGFzIGEgaGVhZGVyIGZvciBlbmNhcHN1bGF0
ZWQgcHJvdG9jb2wgQiwNCndoaWNoIHVzdWFsbHkgd29u4oCZdCBhY2NvbXBsaXNoIG11Y2gsIGJ1
dCBjb3VsZCBvY2Nhc2lvbmFsbHkgY2F1c2UNCnJhdGhlciB1bmRlc2lyYWJsZSByZXN1bHRzLg0K
SSByZWFsaXplIHRoYXQgdGhpcyB0ZXh0IHdhcyBjb3BpZWQgZnJvbSBSRkMgMjc4NCwgYW5kIHRo
YXQgY291bGQgYmUNCmEgcmVhc29uIHRvIG5vdCBtYWtlIHRoaXMgY2hhbmdlLg0KDQpUaGFua3Ms
DQotLURhdmlkDQoNCkZyb206IEludC1hcmVhIFttYWlsdG86aW50LWFyZWEtYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIFp1bmlnYSwgSnVhbiBDYXJsb3MNClNlbnQ6IE1vbmRheSwgTWFy
Y2ggMzAsIDIwMTUgNDoyNyBQTQ0KVG86IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJl
YUBpZXRmLm9yZz47IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+DQpDYzogZHJh
ZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9y
ZzxtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBbSW50LWFyZWFdIFN0
YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KDQoNCkRlYXIgSW50
LUFyZWEgYW5kIDZtYW4gV0dzLA0KDQoNCg0KQXQgdGhlIEludC1BcmVhIFdHIG1lZXRpbmcgaW4g
RGFsbGFzIHRoZXJlIHdlcmUgc29tZSBjb21tZW50cyBvbiBkcmFmdC1pZXRmLWludGFyZWEtZ3Jl
LWlwdjYuIEl0IHdhcyBkZWNpZGVkIHRvIHN1Ym1pdCB0aGUgZG9jdW1lbnQgZm9yIFdHIExhc3Qg
Q2FsbCB0byB0aGUgSW50LUFyZWEgJiA2bWFuIFdHcyBhcyBzb29uIGFzIHRoZSBhZ3JlZWQgY2hh
bmdlcyB3ZXJlIG1hZGUuDQoNCg0KDQpUaGUgZG9jdW1lbnQgaGFzIG5vdyBiZWVuIHVwZGF0ZWQg
YWNjb3JkaW5nbHksIHNvIHRoaXMgZW1haWwgc3RhcnRzIGFuIEludC1BcmVhLzZtYW4gV0dzIExh
c3QgQ2FsbCBvbjoNCg0KDQoNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYt
aW50YXJlYS1ncmUtaXB2Ni0wNA0KDQoNCg0KUGxlYXNlIHJlc3BvbmQgdG8gdGhpcyBlbWFpbCB0
byBzdXBwb3J0IHRoZSBkb2N1bWVudCBhbmQvb3Igc2VuZCBjb21tZW50cyBieSAyMDE1LTA0LTA2
Lg0KDQoNCg0KSW4gYWRkaXRpb24sIHRvIHNhdGlzZnkgUkZDIDY3MDIgIlByb21vdGluZyBDb21w
bGlhbmNlIHdpdGggSW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0cyAoSVBSKSI6DQoNCkFyZSB5
b3UgcGVyc29uYWxseSBhd2FyZSBvZiBhbnkgSVBSIHRoYXQgYXBwbGllcyB0byBkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjY/DQoNCklmIHNvLCBoYXMgdGhpcyBJUFIgYmVlbiBkaXNjbG9zZWQg
aW4gY29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzPw0KDQooU2VlIFJGQ3MgMzk3OSwgNDg3
OSwgMzY2OSwgYW5kIDUzNzggZm9yIG1vcmUgZGV0YWlscy4pDQoNCg0KDQpCZXN0LA0KDQoNCg0K
SnVhbiBDYXJsb3MgWnVuaWdhDQooYXMgSW50LUFyZWEgV0cgY28tY2hhaXIpDQoNCg==

--_000_CE03DB3D7B45C245BCA0D24327794936431400MX104CL02corpemcc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1
NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3
MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29Q
bGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFt
aWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0
YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiO30NCnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4
dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWlu
IFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KcC5pbXByaW50
dW5pcXVlaWQsIGxpLmltcHJpbnR1bmlxdWVpZCwgZGl2LmltcHJpbnR1bmlxdWVpZA0KCXttc28t
c3R5bGUtbmFtZTppbXByaW50dW5pcXVlaWQ7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1h
cmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJ
Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUy
MQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjINCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgljb2xv
cjpibGFjazsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7DQoJdGV4
dC1kZWNvcmF0aW9uOm5vbmUgbm9uZTt9DQpzcGFuLkVtYWlsU3R5bGUyMw0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNv
bG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkJh
bGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxp
bms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30N
CnNwYW4uRW1haWxTdHlsZTI2DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9y
bWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXpl
OjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFy
Z2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYz
QzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+VGhhdCBzZWVtcyByZWFzb25hYmxl
IC0gdGhlIHByb3ZlcmJpYWwg4oCccmlnaHQgdGhpbmcgdG8gZG/igJ0gd291bGQgYmUgdG8gdXBk
YXRlIDI3ODQgdG8gYXBwbHkgdGhpcyByZWNvbW1lbmRhdGlvbiBhY3Jvc3MgdGhlIGJvYXJkLCBi
dXQgSeKAmW0gb2sgd2l0aCBzaW1wbHkgcmVtb3ZpbmcgdGhlIFNlY3Rpb24NCiAyLjIgdGV4dCBh
bmQgbGVhdmluZyB0aGluZ3MgYXMgdGhleSBhcmUgaW4gMjc4NC48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+VGhhbmtzLDxicj4NCi0tRGF2aWQ8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzow
aW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IFJvbmFsZCBCb25pY2EgW21haWx0
bzpyYm9uaWNhQGp1bmlwZXIubmV0XQ0KPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1hcmNo
IDMxLCAyMDE1IDg6NTMgUE08YnI+DQo8Yj5Ubzo8L2I+IEJsYWNrLCBEYXZpZDsgWnVuaWdhLCBK
dWFuIENhcmxvczsgaW50LWFyZWFAaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmc8YnI+DQo8Yj5DYzo8
L2I+IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzsgaW50YXJlYS1j
aGFpcnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6IFdHTEMgZm9yIGRyYWZ0LWll
dGYtaW50YXJlYS1ncmUtaXB2NiAtIEV0aGVydHlwZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+RGF2aWQs
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5PbmUgd2F5IHRvIGFkZHJlc3Mg
dGhpcyBwcm9ibGVtIHdvdWxkIGJlIHRvIHJlbW92ZSBTZWN0aW9uIDIuMiBlbnRpcmVseS4gU2lu
Y2UgdGhlIHN5bnRheCBhbmQgc2VtYW50aWNzIG9mIHRoZSBQcm90b2NvbCBUeXBlIGZpZWxkIGlz
IHVuY2hhbmdlZCBmcm9tIFJGQyAyNzg0LCB0aGUgb21pc3Npb24gb2YgU2VjdGlvbiAyLjIgZG9l
c27igJl0IGNoYW5nZSB0aGUgbWVhbmluZw0KIG9mIHRoZSBkcmFmdCBhdCBhbGwuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5Xb3VsZCB0aGF0IHNvbHV0aW9uIHdvcmsgZm9y
IHlvdT88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBSb248
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUg
MS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGlu
IDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IEJsYWNrLCBEYXZp
ZCBbPGEgaHJlZj0ibWFpbHRvOmRhdmlkLmJsYWNrQGVtYy5jb20iPm1haWx0bzpkYXZpZC5ibGFj
a0BlbWMuY29tPC9hPl0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAx
NSA3OjM1IFBNPGJyPg0KPGI+VG86PC9iPiBadW5pZ2EsIEp1YW4gQ2FybG9zOyA8YSBocmVmPSJt
YWlsdG86aW50LWFyZWFAaWV0Zi5vcmciPmludC1hcmVhQGlldGYub3JnPC9hPjsNCjxhIGhyZWY9
Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGlldGYub3JnPC9hPjxicj4NCjxiPkNjOjwvYj4g
PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9y
ZyI+ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPC9hPjsNCjxhIGhy
ZWY9Im1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+aW50YXJlYS1jaGFpcnNAaWV0Zi5v
cmc8L2E+OyBCbGFjaywgRGF2aWQ8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gV0dMQyBmb3IgZHJhZnQt
aWV0Zi1pbnRhcmVhLWdyZS1pcHY2IC0gRXRoZXJ0eXBlczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlNlY3Rpb24gMi4yIHNheXM6
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgVGhlIFByb3RvY29sIFR5cGUg
ZmllbGQgY29udGFpbnMgdGhlIHByb3RvY29sIHR5cGUgb2YgdGhlIHBheWxvYWQ8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+
Jm5ic3A7Jm5ic3A7IHBhY2tldC4mbmJzcDsgUHJvdG9jb2wgVHlwZXMgYXJlIGRlZmluZWQgaW4g
W0VUWVBFU10uJm5ic3A7IEFuIGltcGxlbWVudGF0aW9uPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyBy
ZWNlaXZpbmcgYSBwYWNrZXQgY29udGFpbmluZyBhIFByb3RvY29sIFR5cGUgd2hpY2ggaXMgbm90
IGxpc3RlZCBpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgW0VUWVBFU10gU0hPVUxEIGRpc2NhcmQg
dGhlIHBhY2tldC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPlRoYXQgbGF0dGVyIHNlbnRlbmNl
IGlzIGFsbW9zdCBwb2ludGxlc3MsIGFuZCBtb3Jlb3ZlciwgaXTigJlzIGFuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPnVu
aW1wbGVtZW50YWJsZSBtb3ZpbmcgdGFyZ2V0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Q291
bGQgd2Ugc2F5IHRoYXQgYW55IEdSRSBpbXBsZW1lbnRhdGlvbiBTSE9VTEQgYmUgY29uZmlndXJl
ZCB3aXRoPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDs7Y29sb3I6YmxhY2siPnRoZSBQcm90b2NvbCBUeXBlcyB0aGF0IGFyZSBleHBlY3RlZCBhbmQg
U0hPVUxEIGRpc2NhcmQgYW55IHBhY2tldDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj50aGF0IGFycml2ZXMgd2l0aCBhbiB1
bmV4cGVjdGVkIHByb3RvY29sIHR5cGU/Jm5ic3A7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
Pkkgd291bGQgdGhpbmsgdGhhdCB0aGUgbnVtYmVyIG9mIGV4cGVjdGVkIHByb3RvY29sIHR5cGVz
IGlzIHR5cGljYWxseTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5hIHNtYWxsIG51bWJlciwgYW5kIHRoYXQgY2hlY2sgcHJv
dGVjdHMgYWdhaW5zdCBtaXNpbnRlcnByZXRpbmcgYSBoZWFkZXI8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Zm9yIGVuY2Fw
c3VsYXRlZCBwcm90b2NvbCBBIGFzIGEgaGVhZGVyIGZvciBlbmNhcHN1bGF0ZWQgcHJvdG9jb2wg
Qiw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+d2hpY2ggdXN1YWxseSB3b27igJl0IGFjY29tcGxpc2ggbXVjaCwgYnV0IGNv
dWxkIG9jY2FzaW9uYWxseSBjYXVzZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6Ymxh
Y2siPnJhdGhlciB1bmRlc2lyYWJsZSByZXN1bHRzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5JIHJlYWxpemUgdGhhdCB0
aGlzIHRleHQgd2FzIGNvcGllZCBmcm9tIFJGQyAyNzg0LCBhbmQgdGhhdCBjb3VsZCBiZTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj5hIHJlYXNvbiB0byBub3QgbWFrZSB0aGlzIGNoYW5nZS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+VGhhbmtzLDxicj4NCi0tRGF2aWQ8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzow
aW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IEludC1hcmVhIFs8YSBocmVmPSJt
YWlsdG86aW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOmludC1hcmVhLWJvdW5jZXNA
aWV0Zi5vcmc8L2E+XQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5adW5pZ2EsIEp1YW4gQ2FybG9zPGJy
Pg0KPGI+U2VudDo8L2I+IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDoyNyBQTTxicj4NCjxiPlRv
OjwvYj4gPGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj5pbnQtYXJlYUBpZXRmLm9y
ZzwvYT47IDxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj4NCmlwdjZAaWV0Zi5vcmc8L2E+
PGJyPg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1p
cHY2QHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0
Zi5vcmc8L2E+Ow0KPGEgaHJlZj0ibWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnIj5pbnRh
cmVhLWNoYWlyc0BpZXRmLm9yZzwvYT48YnI+DQo8Yj5TdWJqZWN0OjwvYj4gW0ludC1hcmVhXSBT
dGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5EZWFyIEludC1BcmVhIGFuZCA2
bWFuIFdHcyw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QXQgdGhlIEludC1BcmVhIFdH
IG1lZXRpbmcgaW4gRGFsbGFzIHRoZXJlIHdlcmUgc29tZSBjb21tZW50cyBvbiBkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjYuIEl0IHdhcyBkZWNpZGVkIHRvIHN1Ym1pdCB0aGUgZG9jdW1lbnQg
Zm9yIFdHIExhc3QgQ2FsbCB0byB0aGUgSW50LUFyZWEgJmFtcDsgNm1hbiBXR3MgYXMgc29vbiBh
cyB0aGUgYWdyZWVkIGNoYW5nZXMgd2VyZSBtYWRlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij5UaGUgZG9jdW1lbnQgaGFzIG5vdyBiZWVuIHVwZGF0ZWQgYWNjb3JkaW5nbHksIHNvIHRo
aXMgZW1haWwgc3RhcnRzIGFuIEludC1BcmVhLzZtYW4gV0dzIExhc3QgQ2FsbCBvbjo8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LTA0Ij5odHRwOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYtMDQ8L2E+DQo8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+UGxlYXNlIHJlc3BvbmQgdG8gdGhpcyBlbWFpbCB0byBzdXBwb3J0IHRo
ZSBkb2N1bWVudCBhbmQvb3Igc2VuZCBjb21tZW50cyBieSAyMDE1LTA0LTA2LjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij5JbiBhZGRpdGlvbiwgdG8gc2F0aXNmeSBSRkMgNjcwMiAmcXVv
dDtQcm9tb3RpbmcgQ29tcGxpYW5jZSB3aXRoIEludGVsbGVjdHVhbCBQcm9wZXJ0eSBSaWdodHMg
KElQUikmcXVvdDs6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5BcmUg
eW91IHBlcnNvbmFsbHkgYXdhcmUgb2YgYW55IElQUiB0aGF0IGFwcGxpZXMgdG8gZHJhZnQtaWV0
Zi1pbnRhcmVhLWdyZS1pcHY2PyZuYnNwOw0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij5JZiBzbywgaGFzIHRoaXMgSVBSIGJlZW4gZGlzY2xvc2VkIGluIGNvbXBsaWFu
Y2Ugd2l0aCBJRVRGIElQUiBydWxlcz88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPihTZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5LCBhbmQgNTM3OCBmb3IgbW9yZSBkZXRh
aWxzLik8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QmVzdCw8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+SnVhbiBDYXJsb3MgWnVuaWdhIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+KGFzIEludC1BcmVhIFdHIGNvLWNoYWlyKTxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CE03DB3D7B45C245BCA0D24327794936431400MX104CL02corpemcc_--


From nobody Wed Apr  1 00:25:55 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23CF11A007B; Tue, 31 Mar 2015 19:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvmL2-_feD2o; Tue, 31 Mar 2015 19:06:29 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (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 324981A00C0; Tue, 31 Mar 2015 19:06:26 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t3126INn013218 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2015 22:06:20 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t3126INn013218
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427853983; bh=IJ83JxOdbAmmcJZe1uku93jppuE=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=q/yKgzzmtyslA3brY3YaFp3kmATKQZ1pnCpwZ5n4v833YNESN9d2rcinaxRlfmvfR FGHV+UC8CrlMxzgrDQXUWfKhHkhe5ZiiuQ5edLaYXs8tUNimHbUY9OVlPilHxuTpYh ZNxVGnn2jD16BhTs+ptrScpQgW+66+GBATa3bRR4=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t3126INn013218
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd55.lss.emc.com (RSA Interceptor); Tue, 31 Mar 2015 22:05:31 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31265UH008854 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 22:06:05 -0400
Received: from MXHUB210.corp.emc.com (10.253.68.36) by mxhub26.corp.emc.com (10.254.110.182) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 31 Mar 2015 22:06:05 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB210.corp.emc.com ([10.253.68.36]) with mapi id 14.03.0224.002; Tue, 31 Mar 2015 22:06:04 -0400
From: "Black, David" <david.black@emc.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAw==
Date: Wed, 1 Apr 2015 02:06:04 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Unqa3mvLiyBng7_rqPD9KepccMw>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 02:06:34 -0000

So, I talked to Ron off-list and it looks like something is missing from
this discussion.

The "alternative configuration" is not motivated by a desire to allow
implementation flexibility or bless broken implementations.  It's motivated
by consideration of networks with operational practices wherein a GMTU of
less than 1280 octets is evidence that something is seriously wrong.  That
something might be misconfiguration (quoting RFC 5706, "Anything that
can be configured can be misconfigured."), or an attack on the GRE
ingress's PMTU estimation.

So, in the situation of interest (GMTU < 1280) something is wrong, and
the operator may be faced with a Hobson's choice: either blackhole the
traffic that can no longer be sent without fragmentation, or fragment a
lot of traffic, causing problems at the GRE egress by overwhelming its
reassembly code - there may be good operational and/or security reasons
to not want to do the latter.  All of this ought to be explained in the
draft.

Thanks,
--David

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Templin, F=
red L
> Sent: Tuesday, March 31, 2015 6:39 PM
> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
>=20
> Hi Ron,
>=20
> > -----Original Message-----
> > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > Sent: Tuesday, March 31, 2015 3:12 PM
> > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> intarea-chairs@ietf.org
> > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
> >
> > Fred,
> >
> > It appears that we disagree and have taken to repeating ourselves.
>=20
> This is not a disagreement; this is a case in which the text is actually
> broken
> which you have more or less acknowledged. You can fix the text in questio=
n
> as follows:
>=20
> OLD:
> ****
>    In its default configuration, the GRE ingress router MUST:
>=20
>    o  encapsulate the entire IPv6 packet in a single GRE header and IP
>       delivery header
>=20
>    o  fragment the delivery header, so that it can be reassembled by the
>       GRE egress
>=20
>    However, in an alternative configuration, the GRE ingress MAY:
>=20
>    o  discard the IPv6 packet
>=20
>    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the IPv6
>       packet source.  The MTU field in the ICMPv6 PTB message is set to
>       the GMTU.
>=20
> NEW:
> ****
>    The GRE ingress router MUST:
>=20
>    o  if the IPv6 payload packet includes a fragment header, fragment the
>        payload packet into fragments no larger than the GMTU and encapsul=
ate
>       each fragment in a single GRE header and IP delivery header. Otherw=
ise:
>=20
>       o encapsulate the entire IPv6 packet in a single GRE header and IP
>           delivery header
>=20
>       o fragment the delivery packet, so that it can be reassembled by th=
e
>           GRE egress
>=20
>      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the IPv6
>          packet source, subject to rate limiting.  The MTU field in the I=
CMPv6
> PTB
>         message is set to the GMTU.
>=20
> > So, why don't we solicit opinions from the rest of the WG and defer to =
their
> will.
>=20
> We can't do that for broken text. Ram-rodding broken text through the
> process based on popular opinion does not make it good.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> >
> >                                                         Ron
> >
> >
> > > -----Original Message-----
> > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> intarea-
> > > chairs@ietf.org
> > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
> > >
> > > Hi Ron,
> > >
> > > I will say again that the minimum IPv6 link MTU is 1280 bytes and so =
the
> > > design must account for tunnel paths that include links with such a s=
mall
> > > MTU. The design must also account for nested tunnels-within-tunnels,
> > > where the MTU seen by the first tunnel ingress may be reduced by
> > > potentially many layers of additional encapsulation.
> > >
> > > But again, the point is that the tunnel ingress cannot legitimately s=
end
> PTBs
> > > that report a size smaller than 1280 *and* perpetually drop packets
> smaller
> > > than 1280 which is exactly the behavior your text is permitting.
> > >
> > > Thanks - Fred
> > > fred.l.templin@boeing.com
> > >
> > > > -----Original Message-----
> > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.org=
;
> > > > intarea-chairs@ietf.org
> > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ip=
v6
> > > >
> > > > Fred,
> > > >
> > > > In the last network that I operated, all interior links had MTU
> > > > greater than 9k. If I configured a GRE tunnel between two points in=
 that
> > > network and detected a GMTU less than 1280, it would have indicated o=
ne of
> > > the following:
> > > >
> > > > - Phenomenal brokenness
> > > > - An ICMP PTB-based attack in progress
> > > >
> > > > In such cases, operators need some flexibility in how their network=
s
> > > > would behave. Why deny them this flexibility by taking away the
> > > configuration option?
> > > >
> > > > Isn't it an operator's prerogative to discard any packet that might
> degrade
> > > network performance?
> > > >
> > > >
> > > > Ron
> > > >
> > > > > -----Original Message-----
> > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.o=
rg;
> > > > > intarea- chairs@ietf.org
> > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > draft-ietf-intarea-gre-ipv6
> > > > >
> > > > > Hi Ron,
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > intarea-chairs@ietf.org
> > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > draft-ietf-intarea-gre-ipv6
> > > > > >
> > > > > > Fred,
> > > > > >
> > > > > > Some (if not most) operators maintain networks in which all lin=
ks
> > > > > > have MTU greater than or equal to 1500. In those networks, the
> > > > > > very detection of a GMTU smaller than 1280 indicates brokenness=
.
> > > > > > Those
> > > > > operators, the alternative behavior may be preferable to the defa=
ult.
> > > > >
> > > > > The minimum IPv6 MTU is 1280 bytes; that is how much the link mus=
t
> > > > > deliver no matter what. A GMTU smaller than 1280 does not indicat=
e
> > > > > brokennesss; it can naturally happen if 1) there is a link with a
> > > > > small MTU in the path, or
> > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > >
> > > > > As such, sustained dropping of packets less than 1280 is a no-no,
> > > > > and cannot be specified in a document like this.
> > > > >
> > > > > Thanks - Fred
> > > > > fred.l.templin@boeing.com
> > > > >
> > > > > >
> > > > > > Ron
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > intarea- chairs@ietf.org
> > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > >
> > > > > > > Hi Ron,
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > intarea-chairs@ietf.org
> > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > >
> > > > > > > > Hi Fred,
> > > > > > > >
> > > > > > > >      Inline.....
> > > > > > > >
> > > > > > > >                Ron
> > > > > > > >
> > > > > > > >
> > > > > > > > > Hi Juan Carlos,
> > > > > > > > >
> > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > >
> > > > > > > > >    ?However, in an alternative configuration, the GRE ing=
ress
> MAY:
> > > > > > > > >
> > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > >
> > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] messa=
ge
> > > > > > > > > to the
> > > > > IPv6
> > > > > > > > >       packet source.  The MTU field in the ICMPv6 PTB mes=
sage
> is set
> > > to
> > > > > > > > >       the GMTU.?
> > > > > > > > >
> > > > > > > > > This means that there may be circumstances when the GRE
> > > > > > > > > ingress sends a PTB reporting a size less than 1280.
> > > > > > > > > According to RFC2460, Section 5, the standard behavior fo=
r a
> > > > > > > > > host that receives
> > > > > such a PTB is:
> > > > > > > > >
> > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > >   is not required to reduce the size of subsequent packet=
s to
> less
> > > than
> > > > > > > > >    1280, but must include a Fragment header in those pack=
ets?
> > > > > > > > >
> > > > > > > > > So, hosts that obey RFC2460 Section 5 will see a perpetua=
l
> > > > > > > > > black hole if the GMTU is smaller than 1280 which is
> > > > > > > > > probably not what we
> > > > > > > want.
> > > > > > > >
> > > > > > > >
> > > > > > > > [RPB]
> > > > > > > > All true. This is why the WG decided to make this the
> > > > > > > > alternative behavior
> > > > > > > and not the default behavior.
> > > > > > >
> > > > > > > Behavior that is broken is still broken regardless of whether=
 it
> > > > > > > is alternative or default.
> > > > > > >
> > > > > > > > > ?draft-templin-6man-linkadapt? attempts to provide guidan=
ce
> > > > > > > > > to hosts on how to react to PTB messages that report a sm=
all
> size.
> > > > > > > > > But, as of right now,
> > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > [RPB]
> > > > > > > >
> > > > > > > > Absolutely correct. The procedures described in Section 5 o=
r
> > > > > > > > RFC
> > > > > > > > 246 are
> > > > > > > normative.
> > > > > > > >
> > > > > > > > I don't how this impacts the WG's LC decision regarding the
> > > > > > > > current
> > > > > draft.
> > > > > > >
> > > > > > > Broken behavior should not be specified, whether alternative =
or
> > > default.
> > > > > > >
> > > > > > > Thanks - Fred
> > > > > > > fred.l.templin@boeing.com
> > > > > > >
> > > > > > > >
> > > > > > > > Ron
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Thanks ? Fred
> > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > >
> > > > > > > >
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 00:25:56 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8DE1A8734; Tue, 31 Mar 2015 13:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYuEkB97wMR4; Tue, 31 Mar 2015 13:45:49 -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 D8D371A8764; Tue, 31 Mar 2015 13:45:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUI87544; Tue, 31 Mar 2015 20:45:45 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 31 Mar 2015 21:45:44 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0158.001; Tue, 31 Mar 2015 13:45:36 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Lucy yong <lucy.yong@huawei.com>, Ronald Bonica <rbonica@juniper.net>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYAAC3xTgAAB6KcA=
Date: Tue, 31 Mar 2015 20:45:36 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57155648@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.181]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57155648dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zgfZN1h24CPQW7bu2m7AbzfS4II>
X-Mailman-Approved-At: Wed, 01 Apr 2015 00:24:59 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 20:45:51 -0000

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

TWlub3IgdHdlYWsuIOKYug0KDQpGcm9tOiBMdWN5IHlvbmcNClNlbnQ6IFR1ZXNkYXksIE1hcmNo
IDMxLCAyMDE1IDM6NDIgUE0NClRvOiBMdWN5IHlvbmc7IFJvbmFsZCBCb25pY2E7IEJsYWNrLCBE
YXZpZDsgaW50LWFyZWFAaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmcNCkNjOiBkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc7IGludGFyZWEtY2hhaXJzQGlldGYub3JnDQpT
dWJqZWN0OiBSRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2
DQoNCkhpIFJvbiBhbmQgQ2FybG9zLA0KDQpIZXJlIGlzIHRoZSBwcm9wb3NlZCB0ZXh0IGZvciB0
aGUgc2Vjb25kIHBhcmFncmFwaCBpbiBTZWN0aW9uIDQuMQ0KDQpCZWNhdXNlIHRoZSBJUHY2IGRl
bGl2ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzIG93biwgaXQg
aXMgc3ViamVjdCB0byBjb3JydXB0aW9uLiAgVGh1cyB0aGUgdXNlIG9mIGdyZSBpbiBJUHY2IG11
c3QgYmUgaW4gdGhlIGNhc2Ugd2hlcmUgYW4gSVB2NiBkZWxpdmVyeSBuZXR3b3JrIGNhbiBlbnN1
cmUgcGFja2V0IGNvcnJ1cHRpb24gZXh0cmVtZWx5IHVubGlrZWx5IGFuZC9vciB0aGUgY2FzZSB3
aGVyZSBHUkUgcGF5bG9hZCBpcyBhYmxlIHRvIHRvbGVyYXRlIHRoZSBwYWNrZXQgY29ycnVwdGlv
bi4NCg0KVGhhbmtzLA0KTHVjeQ0KDQoNCkZyb206IEx1Y3kgeW9uZw0KU2VudDogVHVlc2RheSwg
TWFyY2ggMzEsIDIwMTUgMjoyMyBQTQ0KVG86ICdSb25hbGQgQm9uaWNhJzsgQmxhY2ssIERhdmlk
OyBpbnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYu
b3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2
NkB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xz
LmlldGYub3JnPjsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hhaXJz
QGlldGYub3JnPg0KU3ViamVjdDogUkU6IFN0YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50
YXJlYS1ncmUtaXB2Ng0KDQpIaSBSb24sDQoNCjNjKSBtYXkgaGFwcGVuIGZvciBhIFZQTiBvciBu
b24tVlBOIGNhc2UuIFRoZSBwYXlsb2FkIGNhbiBiZSBpbiBub24tSVB2NiBzcGFjZS4gIElzIOKA
nE91dGNvbWUgM2MpIGlzIG5vdCBhY2NlcHRhYmxlLCBidXQgaXQgZXh0cmVtZWx5IHVubGlrZWx5
LuKAnSBmb3IgcGFydGljdWxhciBuZXR3b3JrL3VzYWdlIGluIHlvdXIgbWluZD8NCg0KSXMgdGhl
IGdvYWwgaGVyZSB0byBwcm92ZSBzdWNoIGNvcnJ1cHRpb24gaXMgYWNjZXB0YWJsZSBvciBleHRy
ZW1lIHVubGlrZWx5Pw0KDQpSZWdhcmRzLA0KTHVjeQ0KDQpGcm9tOiBJbnQtYXJlYSBbbWFpbHRv
OmludC1hcmVhLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBSb25hbGQgQm9uaWNhDQpT
ZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSAxOjQzIFBNDQpUbzogQmxhY2ssIERhdmlkOyBp
bnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3Jn
PG1haWx0bzppcHY2QGlldGYub3JnPg0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0
b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmll
dGYub3JnPjsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hhaXJzQGll
dGYub3JnPg0KU3ViamVjdDogUmU6IFtJbnQtYXJlYV0gU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQt
aWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQoNClJlc2VuZOKApg0KDQpGcm9tOiBSb25hbGQgQm9uaWNh
DQpTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSAyOjIzIFBNDQpUbzogJ0JsYWNrLCBEYXZp
ZCc7IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBpZXRmLm9yZz47IGlwdjZAaWV0
Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+DQpDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1p
cHY2QHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9v
bHMuaWV0Zi5vcmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFp
cnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1p
bnRhcmVhLWdyZS1pcHY2DQoNCkRhdmlkLCBMdWN5LA0KDQpZb3UgYXJlIGNvcnJlY3QuICBNYXli
ZSB0aGUgZm9sbG93aW5nIHRleHQgd2lsbCBhZGRyZXNzIHRoZSBpc3N1ZToNCg0KT0xEPg0KICAg
QmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIgZG9lcyBub3QgaW5jbHVkZSBhIGNoZWNr
c3VtIG9mIGl0cw0KICAgb3duLCBpdCBpcyBzdWJqZWN0IHRvIGNvcnJ1cHRpb24uICBIb3dldmVy
LCBldmVuIGlmIHRoZSBkZWxpdmVyeQ0KICAgaGVhZGVyIGlzIGNvcnJ1cHRlZCwgdG8gbGlrZWxp
aG9vZCBvZiB0aGF0IGNvcnJ1cHRpb24gcmVzdWx0aW5nIGluDQogICBtaXNkZWxpdmVyeSBvZiB0
aGUgcGF5bG9hZCBpcyBleHRyZW1lbHkgbG93Lg0KPE9MRA0KDQpORVc+DQogICBCZWNhdXNlIHRo
ZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRz
DQogICBvd24sICB0aGUgZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlcnkgaGVhZGVy
IGlzIHN1YmplY3QgdG8NCiAgIGNvcnJ1cHRpb24uIElmIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNz
IGluIHRoZSBkZWxpdmVyIGhlYWRlciBpcyBjb3JydXB0ZWQsDQogICB0aGUgZm9sbG93aW5nIG91
dGNvbWVzIGFyZSBwb3NzaWJsZToNCg0KDQoxKSAgICAgIFRoZSBkZWxpdmVyeSBwYWNrZXQgaXMg
ZHJvcHBlZCBiZWNhdXNlIHRoZSBuZXcgZGVzdGluYXRpb24gYWRkcmVzcyBpcyB1bnJlYWNoYWJs
ZQ0KDQoyKSAgICAgIFRoZSBkZWxpdmVyeSBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBu
ZXcgZGVzdGluYXRpb24gYWRkcmVzcyBpcyByZWFjaGFibGUsIGJ1dCB0aGF0IG5vZGUgaXMgbm90
IGNvbmZpZ3VyZWQgdG8gcHJvY2VzcyBHUkUgZGVsaXZlcnkgcGFja2V0cyBmcm9tIHRoZSBpbmdy
ZXNzDQoNCjMpICAgICAgVGhlIGRlbGl2ZXJ5IHBhY2tldCBpcyBwcm9jZXNzZWQgYnkgYSBHUkUg
ZWdyZXNzIG90aGVyIHRoYW4gdGhhdCB3aGljaCB3YXMgb3JpZ2luYWxseSBzcGVjaWZpZWQgYnkg
dGhlIEdSRSBpbmdyZXNzLiBQcm9jZXNzaW5nIG9wdGlvbnMgYXJlOg0KDQphLiAgICAgICBUaGUg
cGF5bG9hZCBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9u
IGlzIHVucmVhY2hhYmxlIGZyb20gdGhlIG5vZGUgdGhhdCBwcm9jZXNzZWQgdGhlIGRlbGl2ZXJ5
IHBhY2tldA0KDQpiLiAgICAgIFRoZSBwYXlsb2FkIHBhY2tldCBpcyBkZWxpdmVyZWQgdG8gaXRz
IGludGVuZGVkIGRlc3RpbmF0aW9uDQoNCmMuICAgICAgIFRoZSBwYXlsb2FkIHBhY2tldCBpcyBl
cnJvbmVvdXNseSBkZWxpdmVyZWQgdG8gYSBub2RlIG90aGVyIHRoYW4gaXRzIGludGVuZGVkIGRl
c3RpbmF0aW9uLiBUaGUgaW50ZW5kZWQgZGVzdGluYXRpb24gYW5kIHRoZSBub2RlIHRvIHdoaWNo
IHRoZSBwYXlsb2FkIGlzIGFjdHVhbGx5IGRlbGl2ZXJlZCBhcmUgbnVtYmVyZWQgaWRlbnRpY2Fs
bHksIGJ1dCByZXNpZGUgaW4gZGlmZmVyZW50IFZQTnMuDQoNCk91dGNvbWVzIDEpLCAyKSwgM2Ep
IGFuZCAzYikgYXJlIGFjY2VwdGFibGUuIE91dGNvbWUgM2MpIGlzIG5vdCBhY2NlcHRhYmxlLCBi
dXQgaXQgZXh0cmVtZWx5IHVubGlrZWx5LiBCZWNhdXNlIElQdjYgYWRkcmVzcyBzcGFjZSBpcyBz
byBsYXJnZSBhbmQgc28gc3BhcnNlbHkgcG9wdWxhdGVkLCBvdXRjb21lIDEpIGlzIGJ5IGZhciB0
aGUgbW9zdCBwcm9iYWJsZS4gVGhlcmVmb3JlLCB0aGUgY29tYmluZWQgbGlrZWxpaG9vZCBvZiBh
bGwgYWNjZXB0YWJsZSBvdXRjb21lcyBieSBmYXIgZXhjZWVkcyB0aGUgbGlrZWxpaG9vZCBvZiB0
aGUgb25lIHVuYWNjZXB0YWJsZSBvdXRjb21lLg0KDQpGdXJ0aGVybW9yZSwgZXZlbiBpZiB0aGUg
cGF5bG9hZCBpcyBlcnJvbmVvdXNseSBkZWxpdmVyZWQgdG8gYSBub2RlIG90aGVyIHRoYW4gaXRz
IGludGVuZGVkIGRlc3RpbmF0aW9uLCB0aGF0IG5vZGUgd2lsbCBkaXNjYXJkIHRoZSBwYWNrZXQg
aWYgdGhlIHBheWxvYWQgaXMgYWxzbyBjb3JydXB0ZWQgb3IgaWYgdGhlcmUgYXJlIG5vIGFwcGxp
Y2F0aW9ucyB3YWl0aW5nIHRvIGNvbnN1bWUgdGhlIHBhY2tldC4NCg0KPE5FVw0KDQogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIFJvbg0KDQoNCkZyb206IEJsYWNrLCBEYXZpZCBb
bWFpbHRvOmRhdmlkLmJsYWNrQGVtYy5jb21dDQpTZW50OiBNb25kYXksIE1hcmNoIDMwLCAyMDE1
IDc6NDggUE0NClRvOiBSb25hbGQgQm9uaWNhOyBpbnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50
LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KQ2M6
IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQt
aWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPjsgaW50YXJlYS1jaGFpcnNAaWV0
Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnPjsgQmxhY2ssIERhdmlkDQpTdWJq
ZWN0OiBSRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQoN
Cj4gQWxzbywgd2h5IHdvdWxkIHlvdSBvYmplY3QgdG8gM2I/IFRoZSBwYWNrZXQgZW5kcyB1cCBh
dCB0aGUgcmlnaHQgbm9kZSwganVzdCB2aWEgYW4gdW5leHBlY3RlZCByb3V0ZS4NCg0KVGhhdCBh
c3NlcnRpb24gaXMgYmFzZWQgb24gdGhlIGFzc3VtcHRpb24gdGhhdCB0aGUgcGF5bG9hZCBkZXN0
aW5hdGlvbiBhZGRyZXNzIGlzIHdvcmxkd2lkZSB1bmlxdWUuDQoNClRoZXJlIGFyZSBsb3RzIG9m
IGNvdW50ZXJleGFtcGxlcyB0aGF0IHZvaWQgdGhlIGFzc3VtcHRpb24sIGUuZy4sIDEwLjAuMC4w
LzguDQoNClRoYW5rcywNCi0tRGF2aWQNCg0KDQo=

--_000_2691CE0099834E4A9C5044EEC662BB9D57155648dfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpTaW1TdW47DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6Q29uc29sYXM7DQoJcGFub3NlLTE6MiAxMSA2IDkgMiAyIDQgMyAyIDQ7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEBTaW1TdW4iOw0KCXBhbm9zZS0xOjIgMSA2IDAg
MyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5N
c29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4w
MDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb1Bs
YWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJnaW46
MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KcA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjEy
LjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnByZQ0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVk
IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6
ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29B
Y2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0
eWxlLWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNh
bnMtc2VyaWYiO30NCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2
Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6
MGluOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxl
ZnQ6LjVpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uSFRNTFByZWZvcm1hdHRl
ZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0K
CWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUt
bmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0
eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkJhbGxvb24gVGV4
dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv
b24gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnAuaW1wcmlu
dHVuaXF1ZWlkLCBsaS5pbXByaW50dW5pcXVlaWQsIGRpdi5pbXByaW50dW5pcXVlaWQNCgl7bXNv
LXN0eWxlLW5hbWU6aW1wcmludHVuaXF1ZWlkOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCglt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxl
MjYNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJz
YW5zLXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTI3DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUyOA0KCXttc28tc3R5bGUtdHlw
ZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9y
OiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30N
CnNwYW4uRW1haWxTdHlsZTMwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWls
U3R5bGUzMQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzINCgl7
bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCglj
b2xvcjpibGFjazsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7DQoJ
dGV4dC1kZWNvcmF0aW9uOm5vbmUgbm9uZTt9DQpzcGFuLkVtYWlsU3R5bGUzMw0KCXttc28tc3R5
bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0K
CWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzQNCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0
OTdEO30NCnNwYW4uRW1haWxTdHlsZTM1DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFu
LkVtYWlsU3R5bGUzNg0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToi
Q2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxl
MzcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21z
by1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBp
biAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwv
c3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJl
ZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0i
ZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPk1pbm9yIHR3ZWFrLiA8L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OldpbmdkaW5ncztjb2xvcjojMUY0OTdEIj5KPC9zcGFuPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRE
RiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9t
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDsiPiBMdWN5IHlvbmcNCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5
LCBNYXJjaCAzMSwgMjAxNSAzOjQyIFBNPGJyPg0KPGI+VG86PC9iPiBMdWN5IHlvbmc7IFJvbmFs
ZCBCb25pY2E7IEJsYWNrLCBEYXZpZDsgaW50LWFyZWFAaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmc8
YnI+DQo8Yj5DYzo8L2I+IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9y
ZzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6IFN0YXJ0
IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij5IaSBSb24gYW5kIENhcmxvcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
Pkg8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPmVyZSBpcyB0aGUgcHJvcG9zZWQg
dGV4dCBmb3IgdGhlIHNlY29uZCBwYXJhZ3JhcGggaW4gU2VjdGlvbiA0LjE8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4iIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5CZWNhdXNlIHRoZSBJUHY2IGRlbGl2
ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2YgaXRzIG93biwgaXQgaXMg
c3ViamVjdCB0byBjb3JydXB0aW9uLiZuYnNwOyBUaHVzIHRoZSB1c2Ugb2YgZ3JlIGluIElQdjYg
bXVzdCBiZSBpbiB0aGUgY2FzZSB3aGVyZSBhbiBJUHY2IGRlbGl2ZXJ5IG5ldHdvcmsgY2FuIGVu
c3VyZSBwYWNrZXQNCiBjb3JydXB0aW9uIGV4dHJlbWVseSB1bmxpa2VseSA8L3NwYW4+PHNwYW4g
bGFuZz0iRU4iIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5hbmQvPC9zcGFuPjxzcGFuIGxhbmc9IkVO
IiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+b3IgdGhlIGNhc2Ugd2hlcmUgR1JFIHBheWxvYWQgaXMg
YWJsZSB0byB0b2xlcmF0ZSB0aGUgcGFja2V0IGNvcnJ1cHRpb24uICZuYnNwOyZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOIiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4iIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGFu
a3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4iIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5MdWN5PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4iIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBw
dDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPiBMdWN5IHlvbmcNCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXJj
aCAzMSwgMjAxNSAyOjIzIFBNPGJyPg0KPGI+VG86PC9iPiAnUm9uYWxkIEJvbmljYSc7IEJsYWNr
LCBEYXZpZDsgPGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj5pbnQtYXJlYUBpZXRm
Lm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBpZXRmLm9yZzwv
YT48YnI+DQo8Yj5DYzo8L2I+IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3Jl
LWlwdjZAdG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5p
ZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPmlu
dGFyZWEtY2hhaXJzQGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPiBSRTogU3RhcnQg
b2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PkhpIFJvbiw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjNjKSBtYXkgaGFw
cGVuIGZvciBhIFZQTiBvciBub24tVlBOIGNhc2UuIFRoZSBwYXlsb2FkIGNhbiBiZSBpbiBub24t
SVB2NiBzcGFjZS4gJm5ic3A7SXMg4oCcT3V0Y29tZSAzYykgaXMgbm90IGFjY2VwdGFibGUsIGJ1
dCBpdCBleHRyZW1lbHkgdW5saWtlbHku4oCdIGZvciBwYXJ0aWN1bGFyIG5ldHdvcmsvdXNhZ2Ug
aW4geW91ciBtaW5kPw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5JcyB0
aGUgZ29hbCBoZXJlIHRvIHByb3ZlIHN1Y2ggY29ycnVwdGlvbiBpcyBhY2NlcHRhYmxlIG9yIGV4
dHJlbWUgdW5saWtlbHk/Jm5ic3A7ICZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+THVjeTxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZy
b206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IEludC1hcmVhIFs8YSBo
cmVmPSJtYWlsdG86aW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOmludC1hcmVhLWJv
dW5jZXNAaWV0Zi5vcmc8L2E+XQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5Sb25hbGQgQm9uaWNhPGJy
Pg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDE6NDMgUE08YnI+DQo8Yj5U
bzo8L2I+IEJsYWNrLCBEYXZpZDsgPGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj5p
bnQtYXJlYUBpZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2
NkBpZXRmLm9yZzwvYT48YnI+DQo8Yj5DYzo8L2I+IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2NkB0b29scy5pZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aW50YXJlYS1jaGFpcnNA
aWV0Zi5vcmciPmludGFyZWEtY2hhaXJzQGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9i
PiBSZTogW0ludC1hcmVhXSBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3Jl
LWlwdjY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+UmVzZW5k4oCmPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+
IFJvbmFsZCBCb25pY2EgPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1
IDI6MjMgUE08YnI+DQo8Yj5Ubzo8L2I+ICdCbGFjaywgRGF2aWQnOyA8YSBocmVmPSJtYWlsdG86
aW50LWFyZWFAaWV0Zi5vcmciPmludC1hcmVhQGlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0
bzppcHY2QGlldGYub3JnIj5pcHY2QGlldGYub3JnPC9hPjxicj4NCjxiPkNjOjwvYj4gPGEgaHJl
Zj0ibWFpbHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZyI+ZHJh
ZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1h
aWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8L2E+
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5EYXZpZCwgTHVjeSw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPllvdSBhcmUgY29ycmVjdC4gJm5ic3A7TWF5YmUgdGhlIGZvbGxv
d2luZyB0ZXh0IHdpbGwgYWRkcmVzcyB0aGUgaXNzdWU6PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj5PTEQmZ3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBCZWNhdXNl
IHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0gb2Yg
aXRzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBvd24sIGl0IGlzIHN1YmplY3QgdG8gY29y
cnVwdGlvbi4mbmJzcDsgSG93ZXZlciwgZXZlbiBpZiB0aGUgZGVsaXZlcnk8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3
RCI+Jm5ic3A7Jm5ic3A7IGhlYWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2VsaWhvb2Qgb2YgdGhh
dCBjb3JydXB0aW9uIHJlc3VsdGluZyBpbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgbWlz
ZGVsaXZlcnkgb2YgdGhlIHBheWxvYWQgaXMgZXh0cmVtZWx5IGxvdy48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
Jmx0O09MRDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+TkVXJmd0OzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgQmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIg
ZG9lcyBub3QgaW5jbHVkZSBhIGNoZWNrc3VtIG9mIGl0czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsm
bmJzcDsgb3duLCAmbmJzcDt0aGUgZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlcnkg
aGVhZGVyIGlzIHN1YmplY3QgdG8NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDtj
b3JydXB0aW9uLiBJZiB0aGUgZGVzdGluYXRpb24gYWRkcmVzcyBpbiB0aGUgZGVsaXZlciBoZWFk
ZXIgaXMgY29ycnVwdGVkLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgdGhlIGZvbGxvd2lu
ZyBvdXRjb21lcyBhcmUgcG9zc2libGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6Ljc1aW47dGV4dC1pbmRlbnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
MSk8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtU
aW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPlRoZSBkZWxpdmVyeSBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBuZXcgZGVz
dGluYXRpb24gYWRkcmVzcyBpcyB1bnJlYWNoYWJsZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1p
bmRlbnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Mik8L3NwYW4+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4m
cXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBkZWxp
dmVyeSBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBuZXcgZGVzdGluYXRpb24gYWRkcmVz
cyBpcyByZWFjaGFibGUsIGJ1dCB0aGF0IG5vZGUgaXMgbm90IGNvbmZpZ3VyZWQgdG8gcHJvY2Vz
cyBHUkUgZGVsaXZlcnkgcGFja2V0cyBmcm9tIHRoZSBpbmdyZXNzPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDouNzVp
bjt0ZXh0LWluZGVudDotLjI1aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4zKTwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5l
dyBSb21hbiZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
VGhlIGRlbGl2ZXJ5IHBhY2tldCBpcyBwcm9jZXNzZWQgYnkgYSBHUkUgZWdyZXNzIG90aGVyIHRo
YW4gdGhhdCB3aGljaCB3YXMgb3JpZ2luYWxseSBzcGVjaWZpZWQgYnkgdGhlIEdSRSBpbmdyZXNz
LiBQcm9jZXNzaW5nIG9wdGlvbnMgYXJlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4yNWluO3RleHQtaW5kZW50
Oi0uMjVpbiI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPmEuPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6Ny4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7
LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGUgcGF5
bG9hZCBwYWNrZXQgaXMgZHJvcHBlZCBiZWNhdXNlIHRoZSBwYXlsb2FkIGRlc3RpbmF0aW9uIGlz
IHVucmVhY2hhYmxlIGZyb20gdGhlIG5vZGUgdGhhdCBwcm9jZXNzZWQgdGhlIGRlbGl2ZXJ5IHBh
Y2tldDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6MS4yNWluO3RleHQtaW5kZW50Oi0uMjVpbiI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPmIuPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGUgcGF5bG9hZCBwYWNrZXQgaXMgZGVsaXZlcmVkIHRv
IGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4yNWluO3RleHQtaW5kZW50
Oi0uMjVpbiI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPmMuPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6Ny4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7
LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGUgcGF5
bG9hZCBwYWNrZXQgaXMgZXJyb25lb3VzbHkgZGVsaXZlcmVkIHRvIGEgbm9kZSBvdGhlciB0aGFu
IGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbi4gVGhlIGludGVuZGVkIGRlc3RpbmF0aW9uIGFuZCB0
aGUgbm9kZSB0byB3aGljaCB0aGUgcGF5bG9hZCBpcyBhY3R1YWxseSBkZWxpdmVyZWQgYXJlIG51
bWJlcmVkIGlkZW50aWNhbGx5LCBidXQgcmVzaWRlIGluIGRpZmZlcmVudA0KIFZQTnMuPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5PdXRjb21lcyAxKSwgMiksIDNhKSBhbmQg
M2IpIGFyZSBhY2NlcHRhYmxlLiBPdXRjb21lIDNjKSBpcyBub3QgYWNjZXB0YWJsZSwgYnV0IGl0
IGV4dHJlbWVseSB1bmxpa2VseS4gQmVjYXVzZSBJUHY2IGFkZHJlc3Mgc3BhY2UgaXMgc28gbGFy
Z2UgYW5kIHNvIHNwYXJzZWx5IHBvcHVsYXRlZCwgb3V0Y29tZSAxKSBpcyBieSBmYXIgdGhlIG1v
c3QgcHJvYmFibGUuDQogVGhlcmVmb3JlLCB0aGUgY29tYmluZWQgbGlrZWxpaG9vZCBvZiBhbGwg
YWNjZXB0YWJsZSBvdXRjb21lcyBieSBmYXIgZXhjZWVkcyB0aGUgbGlrZWxpaG9vZCBvZiB0aGUg
b25lIHVuYWNjZXB0YWJsZSBvdXRjb21lLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjoj
MUY0OTdEIj5GdXJ0aGVybW9yZSwgZXZlbiBpZiB0aGUgcGF5bG9hZCBpcyBlcnJvbmVvdXNseSBk
ZWxpdmVyZWQgdG8gYSBub2RlIG90aGVyIHRoYW4gaXRzIGludGVuZGVkIGRlc3RpbmF0aW9uLCB0
aGF0IG5vZGUgd2lsbCBkaXNjYXJkIHRoZSBwYWNrZXQgaWYgdGhlIHBheWxvYWQgaXMgYWxzbyBj
b3JydXB0ZWQgb3IgaWYgdGhlcmUgYXJlIG5vIGFwcGxpY2F0aW9ucyB3YWl0aW5nDQogdG8gY29u
c3VtZSB0aGUgcGFja2V0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmx0
O05FVzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IFJvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj5Gcm9tOjwvYj4gQmxhY2ssIERhdmlkIFs8YSBocmVmPSJtYWlsdG86ZGF2aWQuYmxhY2tAZW1j
LmNvbSI+bWFpbHRvOmRhdmlkLmJsYWNrQGVtYy5jb208L2E+XQ0KPGJyPg0KPGI+U2VudDo8L2I+
IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNzo0OCBQTTxicj4NCjxiPlRvOjwvYj4gUm9uYWxkIEJv
bmljYTsgPGEgaHJlZj0ibWFpbHRvOmludC1hcmVhQGlldGYub3JnIj5pbnQtYXJlYUBpZXRmLm9y
ZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBpZXRmLm9yZzwvYT48
YnI+DQo8Yj5DYzo8L2I+IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlw
djZAdG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRm
Lm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPmludGFy
ZWEtY2hhaXJzQGlldGYub3JnPC9hPjsgQmxhY2ssIERhdmlkPGJyPg0KPGI+U3ViamVjdDo8L2I+
IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4m
Z3Q7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkFsc28sIHdoeSB3b3VsZCB5
b3Ugb2JqZWN0IHRvIDNiPyBUaGUgcGFja2V0IGVuZHMgdXAgYXQgdGhlIHJpZ2h0IG5vZGUsIGp1
c3QgdmlhIGFuIHVuZXhwZWN0ZWQgcm91dGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGF0
IGFzc2VydGlvbiBpcyBiYXNlZCBvbiB0aGUgYXNzdW1wdGlvbiB0aGF0IHRoZSBwYXlsb2FkIGRl
c3RpbmF0aW9uIGFkZHJlc3MgaXMgd29ybGR3aWRlIHVuaXF1ZS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPlRoZXJlIGFyZSBsb3RzIG9mIGNvdW50ZXJleGFtcGxlcyB0aGF0IHZvaWQgdGhlIGFz
c3VtcHRpb24sIGUuZy4sIDEwLjAuMC4wLzguPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPlRoYW5rcyw8YnI+DQotLURhdmlkPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2Nv
bG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4g
NC4wcHQiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAx
LjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_2691CE0099834E4A9C5044EEC662BB9D57155648dfweml701chm_--


From nobody Wed Apr  1 01:14:54 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02821A8A71; Wed,  1 Apr 2015 01:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwUeU1zNTF6Y; Wed,  1 Apr 2015 01:14:51 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD8511A8A68; Wed,  1 Apr 2015 01:14:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1774; q=dns/txt; s=iport; t=1427876091; x=1429085691; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=neWwtskqYwqj1nE8gcB5njzUv7UmG/+SfHOqy8n4cGs=; b=cOOeNV+P70V+ABEjeVIhiNHLkYpFwKjzTFKcvPca7tkI9jDwcOCG+kgw eFtggqitcEFtEfpBs65Yg4sNhiTzEnqaTmgeY/95o6IrH6N962w7/gEE4 3mq/4o0zNF2iCNdSAuEB5LcQ9Jc5vwmt3qu0q7O6KkTAQaC7Q4Nu3HKaE c=;
X-IronPort-AV: E=Sophos;i="5.11,503,1422921600";  d="scan'208,217";a="406697298"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 01 Apr 2015 08:14:49 +0000
Received: from [10.55.98.183] (ams-stbryant-8816.cisco.com [10.55.98.183]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t318Emb9028843; Wed, 1 Apr 2015 08:14:48 GMT
Message-ID: <551BA8F8.1080706@cisco.com>
Date: Wed, 01 Apr 2015 09:14:48 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com>
In-Reply-To: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com>
Content-Type: multipart/alternative; boundary="------------000907070101040308030708"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FH64LP7vE7HU0dzsHzrRnhoORU0>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 08:14:52 -0000

This is a multi-part message in MIME format.
--------------000907070101040308030708
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Because the IPv6 delivery header does not include a checksum of its
own, it is subject to corruption.

SB> It is subject to corruption whether or not it has a checksum.
SB> The point is that there may be undetected corruption. However
SB> detection in only probabilistic even with a checksum. So
SB> I think that that this text should be:

Because the IPv6 delivery header does not include a checksum of its
own, it is subject to higher probability of undetected corruption.

- Stewart




--------------000907070101040308030708
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <meta http-equiv="content-type" content="text/html;
      charset=windows-1252">
    <pre class="newpage">Because the IPv6 delivery header does not include a checksum of its
own, it is subject to corruption. 

SB&gt; It is subject to corruption whether or not it has a checksum.
SB&gt; The point is that there may be undetected corruption. However
SB&gt; detection in only probabilistic even with a checksum. So
SB&gt; I think that that this text should be:

<meta http-equiv="content-type" content="text/html; charset=windows-1252">Because the IPv6 delivery header does not include a checksum of its
own, it is subject to higher probability of undetected corruption. 

- Stewart


<pre class="newpage"></pre>
</pre>
  </body>
</html>

--------------000907070101040308030708--


From nobody Wed Apr  1 01:24:27 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC481A8A7C; Wed,  1 Apr 2015 01:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTYyCF0eUpiA; Wed,  1 Apr 2015 01:24:22 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2FC71A895B; Wed,  1 Apr 2015 01:24:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17026; q=dns/txt; s=iport; t=1427876661; x=1429086261; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=pA/CumBDrP033Lcg8wv6YR08bIA/4HaK6ffx15GrZsI=; b=T38JS0cxzouWEj8XUgId/e0n5CppMeZbDbIr8JB+NeNsnglQdSsiNQmV mpKs1jG5lH0dCYtPHag1XDQTRkuOcVIFAd4VntMAmShyovBiqWnglZaJo ss6uN5KvDeYbv0UhfusFcCqZEivUTGdSkBTYFlB3/BwIldFCv0YF4ttn7 0=;
X-IronPort-AV: E=Sophos;i="5.11,503,1422921600";  d="scan'208,217";a="407115803"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 01 Apr 2015 08:24:18 +0000
Received: from [10.55.98.183] (ams-stbryant-8816.cisco.com [10.55.98.183]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t318OHLb024287; Wed, 1 Apr 2015 08:24:18 GMT
Message-ID: <551BAB31.40204@cisco.com>
Date: Wed, 01 Apr 2015 09:24:17 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, Lucy yong <lucy.yong@huawei.com>, "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------040003030408000300090408"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/l47K7YvEWyGAHTfnEwgIHfkZiWA>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 08:24:23 -0000

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

On 30/03/2015 22:49, Ronald Bonica wrote:
>
> Lucy,
>
> Would the following text work?
>
> OLD>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own, it is subject to corruption.  However, even if the delivery
>
>    header is corrupted, to likelihood of that corruption resulting in
>
>    misdelivery of the payload is extremely low.
>
> <OLD
>
> NEW>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own,  the destination address in the delivery header is subject to
>
>    corruption. If the destination address in the deliver header is 
> corrupted,
>
>    the following outcomes are possible:
>
> 1)The delivery packet is dropped because the new destination address 
> is unreachable
>
> 2)The delivery packet is dropped because the new destination address 
> is reachable, but that node is not configured to process GRE delivery 
> packets from the ingress
>
> 3)The delivery packet is processed by a GRE egress other than that 
> which was originally specified by the GRE ingress. Processing options are:
>
> a.The payload packet is dropped because the payload destination is 
> unreachable from the node that processed the delivery packet
>
> b.The payload packet is delivered to its intended destination because 
> the payload destination is reachable from the node that processed the 
> delivery packet
>
> All of these outcomes are acceptable.
>
> <NEW
>
> Ron
>
Ron, maybe I am missing a caveat, but suppose the payload is a packet 
with a non-globally unique address space (for example 10.x.x.x, but not 
limited to IP) then there is a case 3 c which is that the packet was 
delivered to a node that it was not the intended ultimate destination 
and one has to hope that there is sufficient resilency in the system 
receiving the packet that this is of no consequence.

Stewart

--------------040003030408000300090408
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">
    <div class="moz-cite-prefix">On 30/03/2015 22:49, Ronald Bonica
      wrote:<br>
    </div>
    <blockquote
cite="mid:BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@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: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;}
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;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
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;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
p.imprintuniqueid, li.imprintuniqueid, div.imprintuniqueid
	{mso-style-name:imprintuniqueid;
	mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",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:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:164978658;
	mso-list-type:hybrid;
	mso-list-template-ids:-1018763138 1691499564 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:1.75in;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:3.25in;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:4.75in;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:938875020;
	mso-list-type:hybrid;
	mso-list-template-ids:-418853720 174634458 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:2784;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1010837328;
	mso-list-type:hybrid;
	mso-list-template-ids:-1226434178 16530362 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-start-at:10;
	mso-level-text:%1;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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="MsoNormal"><span style="color:#1F497D">Lucy,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Would the
            following text work?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">OLD&gt;<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   Because the
            IPv6 delivery header does not include a checksum of its<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   own, it is
            subject to corruption.  However, even if the delivery<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   header is
            corrupted, to likelihood of that corruption resulting in<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   misdelivery
            of the payload is extremely low.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">&lt;OLD<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">NEW&gt;<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   Because the
            IPv6 delivery header does not include a checksum of its<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   own,  the
            destination address in the delivery header is subject to
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   corruption.
            If the destination address in the deliver header is
            corrupted,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">   the
            following outcomes are possible:<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:.75in;text-indent:-.25in;mso-list:l0 level1
          lfo3">
          <!--[if !supportLists]--><span style="color:#1F497D"><span
              style="mso-list:Ignore">1)<span style="font:7.0pt
                &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">The delivery packet is dropped because
            the new destination address is unreachable<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:.75in;text-indent:-.25in;mso-list:l0 level1
          lfo3">
          <!--[if !supportLists]--><span style="color:#1F497D"><span
              style="mso-list:Ignore">2)<span style="font:7.0pt
                &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">The delivery packet is dropped because
            the new destination address is reachable, but that node is
            not configured to process GRE delivery packets from the
            ingress<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:.75in;text-indent:-.25in;mso-list:l0 level1
          lfo3">
          <!--[if !supportLists]--><span style="color:#1F497D"><span
              style="mso-list:Ignore">3)<span style="font:7.0pt
                &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">The delivery packet is processed by a
            GRE egress other than that which was originally specified by
            the GRE ingress. Processing options are:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:1.25in;text-indent:-.25in;mso-list:l0
          level2 lfo3">
          <!--[if !supportLists]--><span style="color:#1F497D"><span
              style="mso-list:Ignore">a.<span style="font:7.0pt
                &quot;Times New Roman&quot;">      
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">The payload packet is dropped because
            the payload destination is unreachable from the node that
            processed the delivery packet<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:1.25in;text-indent:-.25in;mso-list:l0
          level2 lfo3">
          <!--[if !supportLists]--><span style="color:#1F497D"><span
              style="mso-list:Ignore">b.<span style="font:7.0pt
                &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">The payload packet is delivered to its
            intended destination because the payload destination is
            reachable from the node that processed the delivery packet<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">All of these
            outcomes are acceptable.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">&lt;NEW<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">                         
            Ron<o:p></o:p></span></p>
      </div>
    </blockquote>
    Ron, maybe I am missing a caveat, but suppose the payload is a
    packet with a non-globally unique address space (for example
    10.x.x.x, but not limited to IP) then there is a case 3 c which is
    that the packet was delivered to a node that it was not the intended
    ultimate destination and one has to hope that there is sufficient
    resilency in the system receiving the packet that this is of no
    consequence.<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------040003030408000300090408--


From nobody Wed Apr  1 01:30:55 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B64421A8AB9; Wed,  1 Apr 2015 01:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZrMsO9-N9keD; Wed,  1 Apr 2015 01:30:50 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A43DE1A1A06; Wed,  1 Apr 2015 01:30:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=36356; q=dns/txt; s=iport; t=1427877050; x=1429086650; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=KVQMpnAluwF/mJw+i8HFp0eiFBLTq0Iby7KHtBVa3Dk=; b=JnmjuBSNhiq+qhHi0jkoSDhx31HipubUDgb6EzhXTRZiGMz0sExAShCt Uo7yyOafmI+UBT/ovpwqeMH/5o8ePOo9RN2tCjaBHwYYksxW5wC7m4A+q srV6uVxYwRqQjU7q7C8O5uvUr5bP6U0uSHG6F5hUzu5KH/H4J6g14ZFjB I=;
X-IronPort-AV: E=Sophos;i="5.11,503,1422921600";  d="scan'208,217";a="411330505"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 01 Apr 2015 08:30:48 +0000
Received: from [10.55.98.183] (ams-stbryant-8816.cisco.com [10.55.98.183]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t318UlwU005909; Wed, 1 Apr 2015 08:30:47 GMT
Message-ID: <551BACB7.1030203@cisco.com>
Date: Wed, 01 Apr 2015 09:30:47 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, Lucy yong <lucy.yong@huawei.com>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715558D@dfweml701-chm> <BLUPR05MB433CBF724C50E3B6F631F8BAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB433CBF724C50E3B6F631F8BAEF40@BLUPR05MB433.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------000600020004090509080805"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Sw0FhkznTAjrDlfSRvjmIwmjhiY>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 08:30:53 -0000

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

Isn't systematic rather than random corruption more likely?

Stewart

On 31/03/2015 23:04, Ronald Bonica wrote:
>
> Lucy, David,
>
> The proposed text says that outcome 3c) is unacceptable but highly 
> unlikely. For example, assume the following:
>
> -That an IPv6 address is assigned to every milligram of matter on 
> earth, including every drop of water. (2**95 IPv6 addresses are assigned)
>
> -That every minute, the destination address on a delivery packet is 
> corrupted
>
> -The pattern of corruption is random
>
> Every time a destination address is corrupted, the odds are 1 / 
> 8,589,934,592 that the result will be an assigned address. This should 
> happen one ever 16, 331 years.
>
> Now, assume that only 1% of those of those 2**95 IPv6 addresses are 
> configured on devices that de-encapsulate GRE. In this case, outcomes 
> 3a), 3b) and 3c) will occur only once every 1,633,100 years!
>
> So, practically speaking, we don’t have much to worry about. But for 
> the purposes of the pedantry, we may need to say that GRE over IPv6 is 
> only practical when operators can deal with that risk.
>
> David, what is the minimum text that we can import to satisfy the 
> requirement.
>
> Ron
>
> *From:* Lucy yong [mailto:lucy.yong@huawei.com]
> *Sent:* Tuesday, March 31, 2015 3:21 PM
> *To:* Ronald Bonica; Black, David; int-area@ietf.org; ipv6@ietf.org
> *Cc:* draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> *Subject:* RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
> Hi Ron,
>
> 3c) may happen for a VPN or non-VPN case. The payload can be in 
> non-IPv6 space.  Is “Outcome 3c) is not acceptable, but it extremely 
> unlikely.” for particular network/usage in your mind?
>
> Is the goal here to prove such corruption is acceptable or extreme 
> unlikely?
>
> Regards,
>
> Lucy
>
> *From:*Int-area [mailto:int-area-bounces@ietf.org] *On Behalf Of 
> *Ronald Bonica
> *Sent:* Tuesday, March 31, 2015 1:43 PM
> *To:* Black, David; int-area@ietf.org <mailto:int-area@ietf.org>; 
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> *Cc:* draft-ietf-intarea-gre-ipv6@tools.ietf.org 
> <mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org>; 
> intarea-chairs@ietf.org <mailto:intarea-chairs@ietf.org>
> *Subject:* Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
>
> Resend…
>
> *From:* Ronald Bonica
> *Sent:* Tuesday, March 31, 2015 2:23 PM
> *To:* 'Black, David'; int-area@ietf.org <mailto:int-area@ietf.org>; 
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> *Cc:* draft-ietf-intarea-gre-ipv6@tools.ietf.org 
> <mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org>; 
> intarea-chairs@ietf.org <mailto:intarea-chairs@ietf.org>
> *Subject:* RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
> David, Lucy,
>
> You are correct.  Maybe the following text will address the issue:
>
> OLD>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own, it is subject to corruption.  However, even if the delivery
>
>    header is corrupted, to likelihood of that corruption resulting in
>
> misdelivery of the payload is extremely low.
>
> <OLD
>
> NEW>
>
>    Because the IPv6 delivery header does not include a checksum of its
>
>    own,  the destination address in the delivery header is subject to
>
>    corruption. If the destination address in the deliver header is 
> corrupted,
>
>    the following outcomes are possible:
>
> 1)The delivery packet is dropped because the new destination address 
> is unreachable
>
> 2)The delivery packet is dropped because the new destination address 
> is reachable, but that node is not configured to process GRE delivery 
> packets from the ingress
>
> 3)The delivery packet is processed by a GRE egress other than that 
> which was originally specified by the GRE ingress. Processing options are:
>
> a.The payload packet is dropped because the payload destination is 
> unreachable from the node that processed the delivery packet
>
> b.The payload packet is delivered to its intended destination
>
> c.The payload packet is erroneously delivered to a node other than its 
> intended destination. The intended destination and the node to which 
> the payload is actually delivered are numbered identically, but reside 
> in different VPNs.
>
> Outcomes 1), 2), 3a) and 3b) are acceptable. Outcome 3c) is not 
> acceptable, but it extremely unlikely. Because IPv6 address space is 
> so large and so sparsely populated, outcome 1) is by far the most 
> probable. Therefore, the combined likelihood of all acceptable 
> outcomes by far exceeds the likelihood of the one unacceptable outcome.
>
> Furthermore, even if the payload is erroneously delivered to a node 
> other than its intended destination, that node will discard the packet 
> if the payload is also corrupted or if there are no applications 
> waiting to consume the packet.
>
> <NEW
>
> Ron
>
> *From:* Black, David [mailto:david.black@emc.com]
> *Sent:* Monday, March 30, 2015 7:48 PM
> *To:* Ronald Bonica; int-area@ietf.org <mailto:int-area@ietf.org>; 
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> *Cc:* draft-ietf-intarea-gre-ipv6@tools.ietf.org 
> <mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org>; 
> intarea-chairs@ietf.org <mailto:intarea-chairs@ietf.org>; Black, David
> *Subject:* RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
>
> > Also, why would you object to 3b? The packet ends up at the right 
> node, just via an unexpected route.
>
> That assertion is based on the assumption that the payload destination 
> address is worldwide unique.
>
> There are lots of counterexamples that void the assumption, e.g., 
> 10.0.0.0/8.
>
> Thanks,
> --David
>
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------000600020004090509080805
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">
    <div class="moz-cite-prefix">Isn't systematic rather than random
      corruption more likely?<br>
      <br>
      Stewart<br>
      <br>
      On 31/03/2015 23:04, Ronald Bonica wrote:<br>
    </div>
    <blockquote
cite="mid:BLUPR05MB433CBF724C50E3B6F631F8BAEF40@BLUPR05MB433.namprd05.prod.outlook.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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@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: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;}
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;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
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;}
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;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma",sans-serif;}
p.imprintuniqueid, li.imprintuniqueid, div.imprintuniqueid
	{mso-style-name:imprintuniqueid;
	mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle36
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:773793774;
	mso-list-type:hybrid;
	mso-list-template-ids:-523705002 -1318781066 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1873297528;
	mso-list-type:hybrid;
	mso-list-template-ids:1340354874 531247408 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:2;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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="MsoNormal"><span style="color:#1F497D">Lucy, David,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">The proposed
            text says that outcome 3c) is unacceptable but highly
            unlikely. For example, assume the following:<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-.25in;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span
            style="color:#1F497D"><span style="mso-list:Ignore">-<span
                style="font:7.0pt &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">That an IPv6 address is assigned to
            every milligram of matter on earth, including every drop of
            water. (2**95 IPv6 addresses are assigned)<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-.25in;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span
            style="color:#1F497D"><span style="mso-list:Ignore">-<span
                style="font:7.0pt &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">That every minute, the destination
            address on a delivery packet is corrupted<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-.25in;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span
            style="color:#1F497D"><span style="mso-list:Ignore">-<span
                style="font:7.0pt &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
            style="color:#1F497D">The pattern of corruption is random<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Every time a
            destination address is corrupted, the odds are 1 /
            8,589,934,592 that the result will be an assigned address.
            This should happen one ever 16, 331 years.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Now, assume
            that only 1% of those of those 2**95 IPv6 addresses are
            configured on devices that de-encapsulate GRE. In this case,
            outcomes 3a), 3b) and 3c) will occur only once every
            1,633,100 years!<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">So, practically
            speaking, we don’t have much to worry about. But for the
            purposes of the pedantry, we may need to say that GRE over
            IPv6 is only practical when operators can deal with that
            risk.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">David, what is
            the minimum text that we can import to satisfy the
            requirement.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">                                                            
            Ron<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><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>From:</b> Lucy yong
                [<a class="moz-txt-link-freetext" href="mailto:lucy.yong@huawei.com">mailto:lucy.yong@huawei.com</a>] <br>
                <b>Sent:</b> Tuesday, March 31, 2015 3:21 PM<br>
                <b>To:</b> Ronald Bonica; Black, David;
                <a class="moz-txt-link-abbreviated" href="mailto:int-area@ietf.org">int-area@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org">draft-ietf-intarea-gre-ipv6@tools.ietf.org</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:intarea-chairs@ietf.org">intarea-chairs@ietf.org</a><br>
                <b>Subject:</b> RE: Start of WGLC for
                draft-ietf-intarea-gre-ipv6<o:p></o:p></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">Hi Ron,<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">3c) may
              happen for a VPN or non-VPN case. The payload can be in
              non-IPv6 space.  Is “Outcome 3c) is not acceptable, but it
              extremely unlikely.” for particular network/usage in your
              mind?
              <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">Is the goal
              here to prove such corruption is acceptable or extreme
              unlikely?   <o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">Lucy<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span
                    style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif">
                  Int-area [<a moz-do-not-send="true"
                    href="mailto:int-area-bounces@ietf.org">mailto:int-area-bounces@ietf.org</a>]
                  <b>On Behalf Of </b>Ronald Bonica<br>
                  <b>Sent:</b> Tuesday, March 31, 2015 1:43 PM<br>
                  <b>To:</b> Black, David; <a moz-do-not-send="true"
                    href="mailto:int-area@ietf.org">int-area@ietf.org</a>;
                  <a moz-do-not-send="true" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
                  <b>Cc:</b> <a moz-do-not-send="true"
                    href="mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org">draft-ietf-intarea-gre-ipv6@tools.ietf.org</a>;
                  <a moz-do-not-send="true"
                    href="mailto:intarea-chairs@ietf.org">intarea-chairs@ietf.org</a><br>
                  <b>Subject:</b> Re: [Int-area] Start of WGLC for
                  draft-ietf-intarea-gre-ipv6<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">Resend…<o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><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>From:</b> Ronald Bonica <br>
                  <b>Sent:</b> Tuesday, March 31, 2015 2:23 PM<br>
                  <b>To:</b> 'Black, David'; <a moz-do-not-send="true"
                    href="mailto:int-area@ietf.org">int-area@ietf.org</a>;
                  <a moz-do-not-send="true" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
                  <b>Cc:</b> <a moz-do-not-send="true"
                    href="mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org">draft-ietf-intarea-gre-ipv6@tools.ietf.org</a>;
                  <a moz-do-not-send="true"
                    href="mailto:intarea-chairs@ietf.org">intarea-chairs@ietf.org</a><br>
                  <b>Subject:</b> RE: Start of WGLC for
                  draft-ietf-intarea-gre-ipv6<o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal"><o:p> </o:p></p>
            <p class="MsoNormal"><span style="color:#1F497D">David,
                Lucy,<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">You are
                correct.  Maybe the following text will address the
                issue:<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">OLD&gt;<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   Because
                the IPv6 delivery header does not include a checksum of
                its<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   own, it
                is subject to corruption.  However, even if the delivery<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   header
                is corrupted, to likelihood of that corruption resulting
                in<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">  
                misdelivery of the payload is extremely low.<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">&lt;OLD<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">NEW&gt;<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   Because
                the IPv6 delivery header does not include a checksum of
                its<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   own,
                 the destination address in the delivery header is
                subject to
                <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   corruption.
                If the destination address in the deliver header is
                corrupted,<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">   the
                following outcomes are possible:<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoListParagraph"
              style="margin-left:.75in;text-indent:-.25in"><span
                style="color:#1F497D">1)</span><span
                style="font-size:7.0pt;font-family:&quot;Times New
                Roman&quot;,serif;color:#1F497D">     
              </span><span style="color:#1F497D">The delivery packet is
                dropped because the new destination address is
                unreachable<o:p></o:p></span></p>
            <p class="MsoListParagraph"
              style="margin-left:.75in;text-indent:-.25in"><span
                style="color:#1F497D">2)</span><span
                style="font-size:7.0pt;font-family:&quot;Times New
                Roman&quot;,serif;color:#1F497D">     
              </span><span style="color:#1F497D">The delivery packet is
                dropped because the new destination address is
                reachable, but that node is not configured to process
                GRE delivery packets from the ingress<o:p></o:p></span></p>
            <p class="MsoListParagraph"
              style="margin-left:.75in;text-indent:-.25in"><span
                style="color:#1F497D">3)</span><span
                style="font-size:7.0pt;font-family:&quot;Times New
                Roman&quot;,serif;color:#1F497D">     
              </span><span style="color:#1F497D">The delivery packet is
                processed by a GRE egress other than that which was
                originally specified by the GRE ingress. Processing
                options are:<o:p></o:p></span></p>
            <p class="MsoListParagraph"
              style="margin-left:1.25in;text-indent:-.25in"><span
                style="color:#1F497D">a.</span><span
                style="font-size:7.0pt;font-family:&quot;Times New
                Roman&quot;,serif;color:#1F497D">      
              </span><span style="color:#1F497D">The payload packet is
                dropped because the payload destination is unreachable
                from the node that processed the delivery packet<o:p></o:p></span></p>
            <p class="MsoListParagraph"
              style="margin-left:1.25in;text-indent:-.25in"><span
                style="color:#1F497D">b.</span><span
                style="font-size:7.0pt;font-family:&quot;Times New
                Roman&quot;,serif;color:#1F497D">     
              </span><span style="color:#1F497D">The payload packet is
                delivered to its intended destination<o:p></o:p></span></p>
            <p class="MsoListParagraph"
              style="margin-left:1.25in;text-indent:-.25in"><span
                style="color:#1F497D">c.</span><span
                style="font-size:7.0pt;font-family:&quot;Times New
                Roman&quot;,serif;color:#1F497D">      
              </span><span style="color:#1F497D">The payload packet is
                erroneously delivered to a node other than its intended
                destination. The intended destination and the node to
                which the payload is actually delivered are numbered
                identically, but reside in different VPNs.<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">Outcomes
                1), 2), 3a) and 3b) are acceptable. Outcome 3c) is not
                acceptable, but it extremely unlikely. Because IPv6
                address space is so large and so sparsely populated,
                outcome 1) is by far the most probable. Therefore, the
                combined likelihood of all acceptable outcomes by far
                exceeds the likelihood of the one unacceptable outcome.
                <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">Furthermore,
                even if the payload is erroneously delivered to a node
                other than its intended destination, that node will
                discard the packet if the payload is also corrupted or
                if there are no applications waiting to consume the
                packet.<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">&lt;NEW<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D">                                  
                Ron<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
            <p class="MsoNormal"><span style="color:#1F497D"><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>From:</b> Black, David [<a
                      moz-do-not-send="true"
                      href="mailto:david.black@emc.com">mailto:david.black@emc.com</a>]
                    <br>
                    <b>Sent:</b> Monday, March 30, 2015 7:48 PM<br>
                    <b>To:</b> Ronald Bonica; <a moz-do-not-send="true"
                      href="mailto:int-area@ietf.org">int-area@ietf.org</a>;
                    <a moz-do-not-send="true"
                      href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
                    <b>Cc:</b> <a moz-do-not-send="true"
                      href="mailto:draft-ietf-intarea-gre-ipv6@tools.ietf.org">draft-ietf-intarea-gre-ipv6@tools.ietf.org</a>;
                    <a moz-do-not-send="true"
                      href="mailto:intarea-chairs@ietf.org">intarea-chairs@ietf.org</a>;
                    Black, David<br>
                    <b>Subject:</b> RE: Start of WGLC for
                    draft-ietf-intarea-gre-ipv6<o:p></o:p></p>
                </div>
              </div>
              <p class="MsoNormal"><o:p> </o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black">&gt;
                </span><span style="color:#1F497D">Also, why would you
                  object to 3b? The packet ends up at the right node,
                  just via an unexpected route.<o:p></o:p></span></p>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black"><o:p> </o:p></span></p>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black">That assertion is based on the
                  assumption that the payload destination address is
                  worldwide unique.<o:p></o:p></span></p>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black"><o:p> </o:p></span></p>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black">There are lots of
                  counterexamples that void the assumption, e.g.,
                  10.0.0.0/8.<o:p></o:p></span></p>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black"><o:p> </o:p></span></p>
              <div>
                <div>
                  <p class="MsoNormal"><span
                      style="font-size:10.0pt;font-family:&quot;Courier
                      New&quot;;color:black">Thanks,<br>
                      --David</span><span
                      style="font-family:&quot;Courier
                      New&quot;;color:black"><o:p></o:p></span></p>
                </div>
              </div>
              <p class="MsoNormal"><span
                  style="font-size:10.0pt;font-family:&quot;Courier
                  New&quot;;color:black"><o:p> </o:p></span></p>
              <div style="border:none;border-left:solid blue
                1.5pt;padding:0in 0in 0in 4.0pt">
                <div style="border:none;border-left:solid blue
                  1.5pt;padding:0in 0in 0in 4.0pt">
                  <div style="border:none;border-left:solid blue
                    1.5pt;padding:0in 0in 0in 4.0pt">
                    <p class="MsoNormal"><o:p> </o:p></p>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Int-area mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Int-area@ietf.org">Int-area@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/int-area">https://www.ietf.org/mailman/listinfo/int-area</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------000600020004090509080805--


From nobody Wed Apr  1 07:13:33 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653431A9237; Wed,  1 Apr 2015 07:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SjrHehiEOJ_6; Wed,  1 Apr 2015 07:13:28 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10F291A89FA; Wed,  1 Apr 2015 07:13:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t31EDR3l012257; Wed, 1 Apr 2015 07:13:27 -0700
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t31EDMwA011971 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 1 Apr 2015 07:13:22 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.107]) with mapi id 14.03.0210.002; Wed, 1 Apr 2015 07:13:22 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72A
Date: Wed, 1 Apr 2015 14:13:20 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8QfkIkJtEcuxY9PGCSYQTZrMcws>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 14:13:32 -0000

Hi David,

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Tuesday, March 31, 2015 7:06 PM
> To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org; =
Black, David
> Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
>=20
> So, I talked to Ron off-list and it looks like something is missing from
> this discussion.
>=20
> The "alternative configuration" is not motivated by a desire to allow
> implementation flexibility or bless broken implementations.  It's motivat=
ed
> by consideration of networks with operational practices wherein a GMTU of
> less than 1280 octets is evidence that something is seriously wrong.  Tha=
t
> something might be misconfiguration (quoting RFC 5706, "Anything that
> can be configured can be misconfigured."), or an attack on the GRE
> ingress's PMTU estimation.
>=20
> So, in the situation of interest (GMTU < 1280) something is wrong, and
> the operator may be faced with a Hobson's choice: either blackhole the
> traffic that can no longer be sent without fragmentation, or fragment a
> lot of traffic, causing problems at the GRE egress by overwhelming its
> reassembly code - there may be good operational and/or security reasons
> to not want to do the latter.  All of this ought to be explained in the
> draft.

No, that's is not right. GMTU < 1280 is not necessarily an indication
that something is wrong, as explained in Section 7 of RFC2473. The
same considerations apply here.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Templin,=
 Fred L
> > Sent: Tuesday, March 31, 2015 6:39 PM
> > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
> >
> > Hi Ron,
> >
> > > -----Original Message-----
> > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > intarea-chairs@ietf.org
> > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
> > >
> > > Fred,
> > >
> > > It appears that we disagree and have taken to repeating ourselves.
> >
> > This is not a disagreement; this is a case in which the text is actuall=
y
> > broken
> > which you have more or less acknowledged. You can fix the text in quest=
ion
> > as follows:
> >
> > OLD:
> > ****
> >    In its default configuration, the GRE ingress router MUST:
> >
> >    o  encapsulate the entire IPv6 packet in a single GRE header and IP
> >       delivery header
> >
> >    o  fragment the delivery header, so that it can be reassembled by th=
e
> >       GRE egress
> >
> >    However, in an alternative configuration, the GRE ingress MAY:
> >
> >    o  discard the IPv6 packet
> >
> >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the IPv6
> >       packet source.  The MTU field in the ICMPv6 PTB message is set to
> >       the GMTU.
> >
> > NEW:
> > ****
> >    The GRE ingress router MUST:
> >
> >    o  if the IPv6 payload packet includes a fragment header, fragment t=
he
> >        payload packet into fragments no larger than the GMTU and encaps=
ulate
> >       each fragment in a single GRE header and IP delivery header. Othe=
rwise:
> >
> >       o encapsulate the entire IPv6 packet in a single GRE header and I=
P
> >           delivery header
> >
> >       o fragment the delivery packet, so that it can be reassembled by =
the
> >           GRE egress
> >
> >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the IP=
v6
> >          packet source, subject to rate limiting.  The MTU field in the=
 ICMPv6
> > PTB
> >         message is set to the GMTU.
> >
> > > So, why don't we solicit opinions from the rest of the WG and defer t=
o their
> > will.
> >
> > We can't do that for broken text. Ram-rodding broken text through the
> > process based on popular opinion does not make it good.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> > >
> > >                                                         Ron
> > >
> > >
> > > > -----Original Message-----
> > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.org=
;
> > intarea-
> > > > chairs@ietf.org
> > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ip=
v6
> > > >
> > > > Hi Ron,
> > > >
> > > > I will say again that the minimum IPv6 link MTU is 1280 bytes and s=
o the
> > > > design must account for tunnel paths that include links with such a=
 small
> > > > MTU. The design must also account for nested tunnels-within-tunnels=
,
> > > > where the MTU seen by the first tunnel ingress may be reduced by
> > > > potentially many layers of additional encapsulation.
> > > >
> > > > But again, the point is that the tunnel ingress cannot legitimately=
 send
> > PTBs
> > > > that report a size smaller than 1280 *and* perpetually drop packets
> > smaller
> > > > than 1280 which is exactly the behavior your text is permitting.
> > > >
> > > > Thanks - Fred
> > > > fred.l.templin@boeing.com
> > > >
> > > > > -----Original Message-----
> > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.o=
rg;
> > > > > intarea-chairs@ietf.org
> > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-=
ipv6
> > > > >
> > > > > Fred,
> > > > >
> > > > > In the last network that I operated, all interior links had MTU
> > > > > greater than 9k. If I configured a GRE tunnel between two points =
in that
> > > > network and detected a GMTU less than 1280, it would have indicated=
 one of
> > > > the following:
> > > > >
> > > > > - Phenomenal brokenness
> > > > > - An ICMP PTB-based attack in progress
> > > > >
> > > > > In such cases, operators need some flexibility in how their netwo=
rks
> > > > > would behave. Why deny them this flexibility by taking away the
> > > > configuration option?
> > > > >
> > > > > Isn't it an operator's prerogative to discard any packet that mig=
ht
> > degrade
> > > > network performance?
> > > > >
> > > > >
> > > > > Ron
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf=
.org;
> > > > > > intarea- chairs@ietf.org
> > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > draft-ietf-intarea-gre-ipv6
> > > > > >
> > > > > > Hi Ron,
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > intarea-chairs@ietf.org
> > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > >
> > > > > > > Fred,
> > > > > > >
> > > > > > > Some (if not most) operators maintain networks in which all l=
inks
> > > > > > > have MTU greater than or equal to 1500. In those networks, th=
e
> > > > > > > very detection of a GMTU smaller than 1280 indicates brokenne=
ss.
> > > > > > > Those
> > > > > > operators, the alternative behavior may be preferable to the de=
fault.
> > > > > >
> > > > > > The minimum IPv6 MTU is 1280 bytes; that is how much the link m=
ust
> > > > > > deliver no matter what. A GMTU smaller than 1280 does not indic=
ate
> > > > > > brokennesss; it can naturally happen if 1) there is a link with=
 a
> > > > > > small MTU in the path, or
> > > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > > >
> > > > > > As such, sustained dropping of packets less than 1280 is a no-n=
o,
> > > > > > and cannot be specified in a document like this.
> > > > > >
> > > > > > Thanks - Fred
> > > > > > fred.l.templin@boeing.com
> > > > > >
> > > > > > >
> > > > > > > Ron
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > intarea- chairs@ietf.org
> > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > >
> > > > > > > > Hi Ron,
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > >
> > > > > > > > > Hi Fred,
> > > > > > > > >
> > > > > > > > >      Inline.....
> > > > > > > > >
> > > > > > > > >                Ron
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > >
> > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > >
> > > > > > > > > >    ?However, in an alternative configuration, the GRE i=
ngress
> > MAY:
> > > > > > > > > >
> > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > >
> > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] mes=
sage
> > > > > > > > > > to the
> > > > > > IPv6
> > > > > > > > > >       packet source.  The MTU field in the ICMPv6 PTB m=
essage
> > is set
> > > > to
> > > > > > > > > >       the GMTU.?
> > > > > > > > > >
> > > > > > > > > > This means that there may be circumstances when the GRE
> > > > > > > > > > ingress sends a PTB reporting a size less than 1280.
> > > > > > > > > > According to RFC2460, Section 5, the standard behavior =
for a
> > > > > > > > > > host that receives
> > > > > > such a PTB is:
> > > > > > > > > >
> > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > >   is not required to reduce the size of subsequent pack=
ets to
> > less
> > > > than
> > > > > > > > > >    1280, but must include a Fragment header in those pa=
ckets?
> > > > > > > > > >
> > > > > > > > > > So, hosts that obey RFC2460 Section 5 will see a perpet=
ual
> > > > > > > > > > black hole if the GMTU is smaller than 1280 which is
> > > > > > > > > > probably not what we
> > > > > > > > want.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [RPB]
> > > > > > > > > All true. This is why the WG decided to make this the
> > > > > > > > > alternative behavior
> > > > > > > > and not the default behavior.
> > > > > > > >
> > > > > > > > Behavior that is broken is still broken regardless of wheth=
er it
> > > > > > > > is alternative or default.
> > > > > > > >
> > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to provide guid=
ance
> > > > > > > > > > to hosts on how to react to PTB messages that report a =
small
> > size.
> > > > > > > > > > But, as of right now,
> > > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > > [RPB]
> > > > > > > > >
> > > > > > > > > Absolutely correct. The procedures described in Section 5=
 or
> > > > > > > > > RFC
> > > > > > > > > 246 are
> > > > > > > > normative.
> > > > > > > > >
> > > > > > > > > I don't how this impacts the WG's LC decision regarding t=
he
> > > > > > > > > current
> > > > > > draft.
> > > > > > > >
> > > > > > > > Broken behavior should not be specified, whether alternativ=
e or
> > > > default.
> > > > > > > >
> > > > > > > > Thanks - Fred
> > > > > > > > fred.l.templin@boeing.com
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Ron
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Thanks ? Fred
> > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > >
> > > > > > > > >
> >
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 09:12:06 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB031AD065; Wed,  1 Apr 2015 09:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l75FTxEEKMC8; Wed,  1 Apr 2015 09:11:54 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E26E1ACED0; Wed,  1 Apr 2015 09:11:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t31GBpUq032131; Wed, 1 Apr 2015 09:11:51 -0700
Received: from XCH-PHX-410.sw.nos.boeing.com (xch-phx-410.sw.nos.boeing.com [10.57.37.41]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t31GBgR5031622 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 1 Apr 2015 09:11:43 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-PHX-410.sw.nos.boeing.com ([169.254.10.42]) with mapi id 14.03.0210.002; Wed, 1 Apr 2015 09:11:42 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0A==
Date: Wed, 1 Apr 2015 16:11:40 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GNQWdZAXDKw4hokHsJ4lXDRR4m0>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 16:11:58 -0000

Hi David,

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Wednesday, April 01, 2015 8:43 AM
> To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org; =
Black, David
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> Fred,
>=20
> > No, that's is not right. GMTU < 1280 is not necessarily an indication
> > that something is wrong, as explained in Section 7 of RFC2473. The
> > same considerations apply here.
>=20
> I agree with the text quoted above,

OK, then this document should cite Section 7 of RFC2473 normatively.

> but what I'm observing is that there
> are networks for which GMTU is an indication that something is wrong
> (this is a consequence of operator decisions that are specific to such
> a network).  The alternative configuration is intended for such networks,
> but is not intended for all networks, and would need to be qualified
> with words making it applicable primarily or only (or suggest some
> other words) to such networks.

If there is operational assurance that all links in the tunnel path configu=
re
a sufficiently large MTU, and there will never be a nesting of tunnels that
would result in a too-small MTU, then tunnel fragmentation would not
need to be invoked and there is no need to talk about sending PTBs with
GMTU less than 1280. Or, if you did want to include text that would tell
what to do in the case of misconfigurations, then this document would
need to update RFC2473 since the same considerations apply to generic
encapsulation over IPv6 and not just GRE encapsulation over IPv6.

Thanks - Fred
fred.l.templin@boeing.com

> Upshot: the use of "necessarily" in the text quoted above is correct, but
> misses the point.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > Sent: Wednesday, April 01, 2015 10:13 AM
> > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> >
> > Hi David,
> >
> > > -----Original Message-----
> > > From: Black, David [mailto:david.black@emc.com]
> > > Sent: Tuesday, March 31, 2015 7:06 PM
> > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg;
> > Black, David
> > > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
> > >
> > > So, I talked to Ron off-list and it looks like something is missing f=
rom
> > > this discussion.
> > >
> > > The "alternative configuration" is not motivated by a desire to allow
> > > implementation flexibility or bless broken implementations.  It's mot=
ivated
> > > by consideration of networks with operational practices wherein a GMT=
U of
> > > less than 1280 octets is evidence that something is seriously wrong. =
 That
> > > something might be misconfiguration (quoting RFC 5706, "Anything that
> > > can be configured can be misconfigured."), or an attack on the GRE
> > > ingress's PMTU estimation.
> > >
> > > So, in the situation of interest (GMTU < 1280) something is wrong, an=
d
> > > the operator may be faced with a Hobson's choice: either blackhole th=
e
> > > traffic that can no longer be sent without fragmentation, or fragment=
 a
> > > lot of traffic, causing problems at the GRE egress by overwhelming it=
s
> > > reassembly code - there may be good operational and/or security reaso=
ns
> > > to not want to do the latter.  All of this ought to be explained in t=
he
> > > draft.
> >
> > No, that's is not right. GMTU < 1280 is not necessarily an indication
> > that something is wrong, as explained in Section 7 of RFC2473. The
> > same considerations apply here.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> > > Thanks,
> > > --David
> > >
> > > > -----Original Message-----
> > > > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Temp=
lin,
> > Fred L
> > > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf=
.org
> > > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ip=
v6
> > > >
> > > > Hi Ron,
> > > >
> > > > > -----Original Message-----
> > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.o=
rg;
> > > > intarea-chairs@ietf.org
> > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-=
ipv6
> > > > >
> > > > > Fred,
> > > > >
> > > > > It appears that we disagree and have taken to repeating ourselves=
.
> > > >
> > > > This is not a disagreement; this is a case in which the text is act=
ually
> > > > broken
> > > > which you have more or less acknowledged. You can fix the text in q=
uestion
> > > > as follows:
> > > >
> > > > OLD:
> > > > ****
> > > >    In its default configuration, the GRE ingress router MUST:
> > > >
> > > >    o  encapsulate the entire IPv6 packet in a single GRE header and=
 IP
> > > >       delivery header
> > > >
> > > >    o  fragment the delivery header, so that it can be reassembled b=
y the
> > > >       GRE egress
> > > >
> > > >    However, in an alternative configuration, the GRE ingress MAY:
> > > >
> > > >    o  discard the IPv6 packet
> > > >
> > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the =
IPv6
> > > >       packet source.  The MTU field in the ICMPv6 PTB message is se=
t to
> > > >       the GMTU.
> > > >
> > > > NEW:
> > > > ****
> > > >    The GRE ingress router MUST:
> > > >
> > > >    o  if the IPv6 payload packet includes a fragment header, fragme=
nt the
> > > >        payload packet into fragments no larger than the GMTU and
> > encapsulate
> > > >       each fragment in a single GRE header and IP delivery header.
> > Otherwise:
> > > >
> > > >       o encapsulate the entire IPv6 packet in a single GRE header a=
nd IP
> > > >           delivery header
> > > >
> > > >       o fragment the delivery packet, so that it can be reassembled=
 by the
> > > >           GRE egress
> > > >
> > > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to th=
e IPv6
> > > >          packet source, subject to rate limiting.  The MTU field in=
 the
> > ICMPv6
> > > > PTB
> > > >         message is set to the GMTU.
> > > >
> > > > > So, why don't we solicit opinions from the rest of the WG and def=
er to
> > their
> > > > will.
> > > >
> > > > We can't do that for broken text. Ram-rodding broken text through t=
he
> > > > process based on popular opinion does not make it good.
> > > >
> > > > Thanks - Fred
> > > > fred.l.templin@boeing.com
> > > >
> > > > >
> > > > >                                                         Ron
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf=
.org;
> > > > intarea-
> > > > > > chairs@ietf.org
> > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gr=
e-ipv6
> > > > > >
> > > > > > Hi Ron,
> > > > > >
> > > > > > I will say again that the minimum IPv6 link MTU is 1280 bytes a=
nd so
> > the
> > > > > > design must account for tunnel paths that include links with su=
ch a
> > small
> > > > > > MTU. The design must also account for nested tunnels-within-tun=
nels,
> > > > > > where the MTU seen by the first tunnel ingress may be reduced b=
y
> > > > > > potentially many layers of additional encapsulation.
> > > > > >
> > > > > > But again, the point is that the tunnel ingress cannot legitima=
tely
> > send
> > > > PTBs
> > > > > > that report a size smaller than 1280 *and* perpetually drop pac=
kets
> > > > smaller
> > > > > > than 1280 which is exactly the behavior your text is permitting=
.
> > > > > >
> > > > > > Thanks - Fred
> > > > > > fred.l.templin@boeing.com
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ie=
tf.org;
> > > > > > > intarea-chairs@ietf.org
> > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-=
gre-
> > ipv6
> > > > > > >
> > > > > > > Fred,
> > > > > > >
> > > > > > > In the last network that I operated, all interior links had M=
TU
> > > > > > > greater than 9k. If I configured a GRE tunnel between two poi=
nts in
> > that
> > > > > > network and detected a GMTU less than 1280, it would have indic=
ated
> > one of
> > > > > > the following:
> > > > > > >
> > > > > > > - Phenomenal brokenness
> > > > > > > - An ICMP PTB-based attack in progress
> > > > > > >
> > > > > > > In such cases, operators need some flexibility in how their n=
etworks
> > > > > > > would behave. Why deny them this flexibility by taking away t=
he
> > > > > > configuration option?
> > > > > > >
> > > > > > > Isn't it an operator's prerogative to discard any packet that=
 might
> > > > degrade
> > > > > > network performance?
> > > > > > >
> > > > > > >
> > > > > > > Ron
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > ipv6@tools.ietf.org;
> > > > > > > > intarea- chairs@ietf.org
> > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > >
> > > > > > > > Hi Ron,
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > >
> > > > > > > > > Fred,
> > > > > > > > >
> > > > > > > > > Some (if not most) operators maintain networks in which a=
ll
> > links
> > > > > > > > > have MTU greater than or equal to 1500. In those networks=
, the
> > > > > > > > > very detection of a GMTU smaller than 1280 indicates brok=
enness.
> > > > > > > > > Those
> > > > > > > > operators, the alternative behavior may be preferable to th=
e
> > default.
> > > > > > > >
> > > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how much the li=
nk must
> > > > > > > > deliver no matter what. A GMTU smaller than 1280 does not i=
ndicate
> > > > > > > > brokennesss; it can naturally happen if 1) there is a link =
with a
> > > > > > > > small MTU in the path, or
> > > > > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > > > > >
> > > > > > > > As such, sustained dropping of packets less than 1280 is a =
no-no,
> > > > > > > > and cannot be specified in a document like this.
> > > > > > > >
> > > > > > > > Thanks - Fred
> > > > > > > > fred.l.templin@boeing.com
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Ron
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com=
]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > >
> > > > > > > > > > Hi Ron,
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > >
> > > > > > > > > > > Hi Fred,
> > > > > > > > > > >
> > > > > > > > > > >      Inline.....
> > > > > > > > > > >
> > > > > > > > > > >                Ron
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > > >
> > > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > > >
> > > > > > > > > > > >    ?However, in an alternative configuration, the G=
RE
> > ingress
> > > > MAY:
> > > > > > > > > > > >
> > > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > > >
> > > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443]
> > message
> > > > > > > > > > > > to the
> > > > > > > > IPv6
> > > > > > > > > > > >       packet source.  The MTU field in the ICMPv6 P=
TB
> > message
> > > > is set
> > > > > > to
> > > > > > > > > > > >       the GMTU.?
> > > > > > > > > > > >
> > > > > > > > > > > > This means that there may be circumstances when the=
 GRE
> > > > > > > > > > > > ingress sends a PTB reporting a size less than 1280=
.
> > > > > > > > > > > > According to RFC2460, Section 5, the standard behav=
ior for
> > a
> > > > > > > > > > > > host that receives
> > > > > > > > such a PTB is:
> > > > > > > > > > > >
> > > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > > >   is not required to reduce the size of subsequent =
packets
> > to
> > > > less
> > > > > > than
> > > > > > > > > > > >    1280, but must include a Fragment header in thos=
e
> > packets?
> > > > > > > > > > > >
> > > > > > > > > > > > So, hosts that obey RFC2460 Section 5 will see a pe=
rpetual
> > > > > > > > > > > > black hole if the GMTU is smaller than 1280 which i=
s
> > > > > > > > > > > > probably not what we
> > > > > > > > > > want.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > [RPB]
> > > > > > > > > > > All true. This is why the WG decided to make this the
> > > > > > > > > > > alternative behavior
> > > > > > > > > > and not the default behavior.
> > > > > > > > > >
> > > > > > > > > > Behavior that is broken is still broken regardless of w=
hether
> > it
> > > > > > > > > > is alternative or default.
> > > > > > > > > >
> > > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to provide
> > guidance
> > > > > > > > > > > > to hosts on how to react to PTB messages that repor=
t a
> > small
> > > > size.
> > > > > > > > > > > > But, as of right now,
> > > > > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > > > > [RPB]
> > > > > > > > > > >
> > > > > > > > > > > Absolutely correct. The procedures described in Secti=
on 5 or
> > > > > > > > > > > RFC
> > > > > > > > > > > 246 are
> > > > > > > > > > normative.
> > > > > > > > > > >
> > > > > > > > > > > I don't how this impacts the WG's LC decision regardi=
ng the
> > > > > > > > > > > current
> > > > > > > > draft.
> > > > > > > > > >
> > > > > > > > > > Broken behavior should not be specified, whether altern=
ative
> > or
> > > > > > default.
> > > > > > > > > >
> > > > > > > > > > Thanks - Fred
> > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Ron
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > >
> > > > > > > > > > >
> > > >
> > > > _______________________________________________
> > > > Int-area mailing list
> > > > Int-area@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 10:27:20 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5511ACDEF; Wed,  1 Apr 2015 08:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQzDLSKgEkQz; Wed,  1 Apr 2015 08:43:47 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 09C4E1ACDAC; Wed,  1 Apr 2015 08:43:46 -0700 (PDT)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31Fharl011769 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Apr 2015 11:43:42 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com t31Fharl011769
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427903022; bh=wWg/U0alBvZjqqwyLh0d8xtpGdg=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=g10yRQ1TiNt1yKICcMSPyt3JbgTAJE3EAgpyTafMsuQNTvnklzajIvj5MQt9lb2+v ARRSMoR5tbOi2/pW90p8r9oHNrg9g0gKJUv+RrlwevJtYlJIvMR7dZh2HJNqhYdVUz TbRFC/hyaLvfQEwX8yS36LA0OMEAH/JHWJ/X2J3k=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com t31Fharl011769
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd03.lss.emc.com (RSA Interceptor); Wed, 1 Apr 2015 11:43:18 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31FhLiX003540 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 11:43:23 -0400
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub18.corp.emc.com (10.254.93.47) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 1 Apr 2015 11:43:21 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0224.002; Wed, 1 Apr 2015 11:43:21 -0400
From: "Black, David" <david.black@emc.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0A=
Date: Wed, 1 Apr 2015 15:43:19 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/UCtrEqU7XJ3Fk0pS-imop_WL8Bo>
X-Mailman-Approved-At: Wed, 01 Apr 2015 10:27:17 -0700
Cc: "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 15:43:51 -0000

Fred,

> No, that's is not right. GMTU < 1280 is not necessarily an indication
> that something is wrong, as explained in Section 7 of RFC2473. The
> same considerations apply here.

I agree with the text quoted above, but what I'm observing is that there
are networks for which GMTU is an indication that something is wrong
(this is a consequence of operator decisions that are specific to such
a network).  The alternative configuration is intended for such networks,
but is not intended for all networks, and would need to be qualified
with words making it applicable primarily or only (or suggest some
other words) to such networks.

Upshot: the use of "necessarily" in the text quoted above is correct, but
misses the point.

Thanks,
--David

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Wednesday, April 01, 2015 10:13 AM
> To: Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> Hi David,
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Tuesday, March 31, 2015 7:06 PM
> > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org=
;
> Black, David
> > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuratio=
n
> >
> > So, I talked to Ron off-list and it looks like something is missing fro=
m
> > this discussion.
> >
> > The "alternative configuration" is not motivated by a desire to allow
> > implementation flexibility or bless broken implementations.  It's motiv=
ated
> > by consideration of networks with operational practices wherein a GMTU =
of
> > less than 1280 octets is evidence that something is seriously wrong.  T=
hat
> > something might be misconfiguration (quoting RFC 5706, "Anything that
> > can be configured can be misconfigured."), or an attack on the GRE
> > ingress's PMTU estimation.
> >
> > So, in the situation of interest (GMTU < 1280) something is wrong, and
> > the operator may be faced with a Hobson's choice: either blackhole the
> > traffic that can no longer be sent without fragmentation, or fragment a
> > lot of traffic, causing problems at the GRE egress by overwhelming its
> > reassembly code - there may be good operational and/or security reasons
> > to not want to do the latter.  All of this ought to be explained in the
> > draft.
>=20
> No, that's is not right. GMTU < 1280 is not necessarily an indication
> that something is wrong, as explained in Section 7 of RFC2473. The
> same considerations apply here.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> > Thanks,
> > --David
> >
> > > -----Original Message-----
> > > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Templi=
n,
> Fred L
> > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg
> > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
> > >
> > > Hi Ron,
> > >
> > > > -----Original Message-----
> > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.org=
;
> > > intarea-chairs@ietf.org
> > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ip=
v6
> > > >
> > > > Fred,
> > > >
> > > > It appears that we disagree and have taken to repeating ourselves.
> > >
> > > This is not a disagreement; this is a case in which the text is actua=
lly
> > > broken
> > > which you have more or less acknowledged. You can fix the text in que=
stion
> > > as follows:
> > >
> > > OLD:
> > > ****
> > >    In its default configuration, the GRE ingress router MUST:
> > >
> > >    o  encapsulate the entire IPv6 packet in a single GRE header and I=
P
> > >       delivery header
> > >
> > >    o  fragment the delivery header, so that it can be reassembled by =
the
> > >       GRE egress
> > >
> > >    However, in an alternative configuration, the GRE ingress MAY:
> > >
> > >    o  discard the IPv6 packet
> > >
> > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the IP=
v6
> > >       packet source.  The MTU field in the ICMPv6 PTB message is set =
to
> > >       the GMTU.
> > >
> > > NEW:
> > > ****
> > >    The GRE ingress router MUST:
> > >
> > >    o  if the IPv6 payload packet includes a fragment header, fragment=
 the
> > >        payload packet into fragments no larger than the GMTU and
> encapsulate
> > >       each fragment in a single GRE header and IP delivery header.
> Otherwise:
> > >
> > >       o encapsulate the entire IPv6 packet in a single GRE header and=
 IP
> > >           delivery header
> > >
> > >       o fragment the delivery packet, so that it can be reassembled b=
y the
> > >           GRE egress
> > >
> > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to the =
IPv6
> > >          packet source, subject to rate limiting.  The MTU field in t=
he
> ICMPv6
> > > PTB
> > >         message is set to the GMTU.
> > >
> > > > So, why don't we solicit opinions from the rest of the WG and defer=
 to
> their
> > > will.
> > >
> > > We can't do that for broken text. Ram-rodding broken text through the
> > > process based on popular opinion does not make it good.
> > >
> > > Thanks - Fred
> > > fred.l.templin@boeing.com
> > >
> > > >
> > > >                                                         Ron
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf.o=
rg;
> > > intarea-
> > > > > chairs@ietf.org
> > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gre-=
ipv6
> > > > >
> > > > > Hi Ron,
> > > > >
> > > > > I will say again that the minimum IPv6 link MTU is 1280 bytes and=
 so
> the
> > > > > design must account for tunnel paths that include links with such=
 a
> small
> > > > > MTU. The design must also account for nested tunnels-within-tunne=
ls,
> > > > > where the MTU seen by the first tunnel ingress may be reduced by
> > > > > potentially many layers of additional encapsulation.
> > > > >
> > > > > But again, the point is that the tunnel ingress cannot legitimate=
ly
> send
> > > PTBs
> > > > > that report a size smaller than 1280 *and* perpetually drop packe=
ts
> > > smaller
> > > > > than 1280 which is exactly the behavior your text is permitting.
> > > > >
> > > > > Thanks - Fred
> > > > > fred.l.templin@boeing.com
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf=
.org;
> > > > > > intarea-chairs@ietf.org
> > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gr=
e-
> ipv6
> > > > > >
> > > > > > Fred,
> > > > > >
> > > > > > In the last network that I operated, all interior links had MTU
> > > > > > greater than 9k. If I configured a GRE tunnel between two point=
s in
> that
> > > > > network and detected a GMTU less than 1280, it would have indicat=
ed
> one of
> > > > > the following:
> > > > > >
> > > > > > - Phenomenal brokenness
> > > > > > - An ICMP PTB-based attack in progress
> > > > > >
> > > > > > In such cases, operators need some flexibility in how their net=
works
> > > > > > would behave. Why deny them this flexibility by taking away the
> > > > > configuration option?
> > > > > >
> > > > > > Isn't it an operator's prerogative to discard any packet that m=
ight
> > > degrade
> > > > > network performance?
> > > > > >
> > > > > >
> > > > > > Ron
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> ipv6@tools.ietf.org;
> > > > > > > intarea- chairs@ietf.org
> > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > >
> > > > > > > Hi Ron,
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > intarea-chairs@ietf.org
> > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > >
> > > > > > > > Fred,
> > > > > > > >
> > > > > > > > Some (if not most) operators maintain networks in which all
> links
> > > > > > > > have MTU greater than or equal to 1500. In those networks, =
the
> > > > > > > > very detection of a GMTU smaller than 1280 indicates broken=
ness.
> > > > > > > > Those
> > > > > > > operators, the alternative behavior may be preferable to the
> default.
> > > > > > >
> > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how much the link=
 must
> > > > > > > deliver no matter what. A GMTU smaller than 1280 does not ind=
icate
> > > > > > > brokennesss; it can naturally happen if 1) there is a link wi=
th a
> > > > > > > small MTU in the path, or
> > > > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > > > >
> > > > > > > As such, sustained dropping of packets less than 1280 is a no=
-no,
> > > > > > > and cannot be specified in a document like this.
> > > > > > >
> > > > > > > Thanks - Fred
> > > > > > > fred.l.templin@boeing.com
> > > > > > >
> > > > > > > >
> > > > > > > > Ron
> > > > > > > >
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > >
> > > > > > > > > Hi Ron,
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > >
> > > > > > > > > > Hi Fred,
> > > > > > > > > >
> > > > > > > > > >      Inline.....
> > > > > > > > > >
> > > > > > > > > >                Ron
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > >
> > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > >
> > > > > > > > > > >    ?However, in an alternative configuration, the GRE
> ingress
> > > MAY:
> > > > > > > > > > >
> > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > >
> > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443]
> message
> > > > > > > > > > > to the
> > > > > > > IPv6
> > > > > > > > > > >       packet source.  The MTU field in the ICMPv6 PTB
> message
> > > is set
> > > > > to
> > > > > > > > > > >       the GMTU.?
> > > > > > > > > > >
> > > > > > > > > > > This means that there may be circumstances when the G=
RE
> > > > > > > > > > > ingress sends a PTB reporting a size less than 1280.
> > > > > > > > > > > According to RFC2460, Section 5, the standard behavio=
r for
> a
> > > > > > > > > > > host that receives
> > > > > > > such a PTB is:
> > > > > > > > > > >
> > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > >   is not required to reduce the size of subsequent pa=
ckets
> to
> > > less
> > > > > than
> > > > > > > > > > >    1280, but must include a Fragment header in those
> packets?
> > > > > > > > > > >
> > > > > > > > > > > So, hosts that obey RFC2460 Section 5 will see a perp=
etual
> > > > > > > > > > > black hole if the GMTU is smaller than 1280 which is
> > > > > > > > > > > probably not what we
> > > > > > > > > want.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [RPB]
> > > > > > > > > > All true. This is why the WG decided to make this the
> > > > > > > > > > alternative behavior
> > > > > > > > > and not the default behavior.
> > > > > > > > >
> > > > > > > > > Behavior that is broken is still broken regardless of whe=
ther
> it
> > > > > > > > > is alternative or default.
> > > > > > > > >
> > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to provide
> guidance
> > > > > > > > > > > to hosts on how to react to PTB messages that report =
a
> small
> > > size.
> > > > > > > > > > > But, as of right now,
> > > > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > > > [RPB]
> > > > > > > > > >
> > > > > > > > > > Absolutely correct. The procedures described in Section=
 5 or
> > > > > > > > > > RFC
> > > > > > > > > > 246 are
> > > > > > > > > normative.
> > > > > > > > > >
> > > > > > > > > > I don't how this impacts the WG's LC decision regarding=
 the
> > > > > > > > > > current
> > > > > > > draft.
> > > > > > > > >
> > > > > > > > > Broken behavior should not be specified, whether alternat=
ive
> or
> > > > > default.
> > > > > > > > >
> > > > > > > > > Thanks - Fred
> > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Ron
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > >
> > > > > > > > > >
> > >
> > > _______________________________________________
> > > Int-area mailing list
> > > Int-area@ietf.org
> > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 10:27:21 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FD451ACDF0; Wed,  1 Apr 2015 08:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BArg6lFPaWCf; Wed,  1 Apr 2015 08:47:55 -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 4C5C91ACDFA; Wed,  1 Apr 2015 08:47:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQY42582; Wed, 01 Apr 2015 15:47:52 +0000 (GMT)
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 1 Apr 2015 16:47:51 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml705-chm ([10.193.5.142]) with mapi id 14.03.0158.001; Wed, 1 Apr 2015 08:47:46 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "Black, David" <david.black@emc.com>, Ronald Bonica <rbonica@juniper.net>,  "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Topic: WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Index: AdBsC0O9ImygMEJJSjuvdoFVvO3XwAACaYSQAABqGzAAHuWoQA==
Date: Wed, 1 Apr 2015 15:47:46 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57155BE6@dfweml701-chm>
References: <CE03DB3D7B45C245BCA0D243277949364312D6@MX104CL02.corp.emc.com> <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com> <CE03DB3D7B45C245BCA0D24327794936431400@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936431400@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.153.159]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57155BE6dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qP4MEMZ5WIiGOkl67KeFjFpgK4Y>
X-Mailman-Approved-At: Wed, 01 Apr 2015 10:27:17 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 15:47:58 -0000

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

SSBhbSBmaW5lIHdpdGggcHJvcG9zZWQgd29yayBhcm91bmQgdG8gU2VjdGlvbiAyLjIgYnV0IHRo
YXQgZG9lcyBub3QgcmVzb2x2ZSB0aGUgdGV4dCBpbiBTZWN0aW9uIDQuMS4gSWYgdGhpcyBkb2N1
bWVudCBpcyBqdXN0IHRvIGRvY3VtZW50IGV4aXN0aW5nIGltcGxlbWVudGF0aW9uLCBpdCBuZWVk
cyBwb2ludCBvdXQgdGhlIHVzYWdlIGNvbnN0cmFpbnRzIHdoZW4gSVB2NiBpcyBhcyBkZWxpdmVy
eSBuZXR3b3JrLiBJIHByb3Bvc2VkIHRoZSBkcmFmdCB0ZXh0LCBUb20gaGFkIHRoZSByZXZpc2Vk
IHRleHQuIERvIHlvdSBhZ3JlZSB0aGF0IHN1Y2ggdGV4dCBpcyBuZWNlc3Nhcnk/DQoNCkx1Y3kN
Cg0KRnJvbTogSW50LWFyZWEgW21haWx0bzppbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnXSBPbiBC
ZWhhbGYgT2YgQmxhY2ssIERhdmlkDQpTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSA3OjU5
IFBNDQpUbzogUm9uYWxkIEJvbmljYTsgaW50LWFyZWFAaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmcN
CkNjOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc7IGludGFyZWEt
Y2hhaXJzQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0ludC1hcmVhXSBXR0xDIGZvciBkcmFmdC1p
ZXRmLWludGFyZWEtZ3JlLWlwdjYgLSBFdGhlcnR5cGVzDQoNClRoYXQgc2VlbXMgcmVhc29uYWJs
ZSAtIHRoZSBwcm92ZXJiaWFsIOKAnHJpZ2h0IHRoaW5nIHRvIGRv4oCdIHdvdWxkIGJlIHRvIHVw
ZGF0ZSAyNzg0IHRvIGFwcGx5IHRoaXMgcmVjb21tZW5kYXRpb24gYWNyb3NzIHRoZSBib2FyZCwg
YnV0IEnigJltIG9rIHdpdGggc2ltcGx5IHJlbW92aW5nIHRoZSBTZWN0aW9uIDIuMiB0ZXh0IGFu
ZCBsZWF2aW5nIHRoaW5ncyBhcyB0aGV5IGFyZSBpbiAyNzg0Lg0KDQpUaGFua3MsDQotLURhdmlk
DQoNCkZyb206IFJvbmFsZCBCb25pY2EgW21haWx0bzpyYm9uaWNhQGp1bmlwZXIubmV0XQ0KU2Vu
dDogVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgODo1MyBQTQ0KVG86IEJsYWNrLCBEYXZpZDsgWnVu
aWdhLCBKdWFuIENhcmxvczsgaW50LWFyZWFAaWV0Zi5vcmc8bWFpbHRvOmludC1hcmVhQGlldGYu
b3JnPjsgaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4NCkNjOiBkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtaW50YXJl
YS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZz47IGludGFyZWEtY2hhaXJzQGlldGYub3JnPG1haWx0
bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBXR0xDIGZvciBkcmFmdC1p
ZXRmLWludGFyZWEtZ3JlLWlwdjYgLSBFdGhlcnR5cGVzDQoNCkRhdmlkLA0KDQpPbmUgd2F5IHRv
IGFkZHJlc3MgdGhpcyBwcm9ibGVtIHdvdWxkIGJlIHRvIHJlbW92ZSBTZWN0aW9uIDIuMiBlbnRp
cmVseS4gU2luY2UgdGhlIHN5bnRheCBhbmQgc2VtYW50aWNzIG9mIHRoZSBQcm90b2NvbCBUeXBl
IGZpZWxkIGlzIHVuY2hhbmdlZCBmcm9tIFJGQyAyNzg0LCB0aGUgb21pc3Npb24gb2YgU2VjdGlv
biAyLjIgZG9lc27igJl0IGNoYW5nZSB0aGUgbWVhbmluZyBvZiB0aGUgZHJhZnQgYXQgYWxsLg0K
DQpXb3VsZCB0aGF0IHNvbHV0aW9uIHdvcmsgZm9yIHlvdT8NCg0KICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoN
Cg0KRnJvbTogQmxhY2ssIERhdmlkIFttYWlsdG86ZGF2aWQuYmxhY2tAZW1jLmNvbV0NClNlbnQ6
IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDc6MzUgUE0NClRvOiBadW5pZ2EsIEp1YW4gQ2FybG9z
OyBpbnQtYXJlYUBpZXRmLm9yZzxtYWlsdG86aW50LWFyZWFAaWV0Zi5vcmc+OyBpcHY2QGlldGYu
b3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KQ2M6IGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2
NkB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xz
LmlldGYub3JnPjsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOmludGFyZWEtY2hhaXJz
QGlldGYub3JnPjsgQmxhY2ssIERhdmlkDQpTdWJqZWN0OiBXR0xDIGZvciBkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjYgLSBFdGhlcnR5cGVzDQoNClNlY3Rpb24gMi4yIHNheXM6DQoNCiAgIFRo
ZSBQcm90b2NvbCBUeXBlIGZpZWxkIGNvbnRhaW5zIHRoZSBwcm90b2NvbCB0eXBlIG9mIHRoZSBw
YXlsb2FkDQogICBwYWNrZXQuICBQcm90b2NvbCBUeXBlcyBhcmUgZGVmaW5lZCBpbiBbRVRZUEVT
XS4gIEFuIGltcGxlbWVudGF0aW9uDQogICByZWNlaXZpbmcgYSBwYWNrZXQgY29udGFpbmluZyBh
IFByb3RvY29sIFR5cGUgd2hpY2ggaXMgbm90IGxpc3RlZCBpbg0KICAgW0VUWVBFU10gU0hPVUxE
IGRpc2NhcmQgdGhlIHBhY2tldC4NCg0KVGhhdCBsYXR0ZXIgc2VudGVuY2UgaXMgYWxtb3N0IHBv
aW50bGVzcywgYW5kIG1vcmVvdmVyLCBpdOKAmXMgYW4NCnVuaW1wbGVtZW50YWJsZSBtb3Zpbmcg
dGFyZ2V0Lg0KDQpDb3VsZCB3ZSBzYXkgdGhhdCBhbnkgR1JFIGltcGxlbWVudGF0aW9uIFNIT1VM
RCBiZSBjb25maWd1cmVkIHdpdGgNCnRoZSBQcm90b2NvbCBUeXBlcyB0aGF0IGFyZSBleHBlY3Rl
ZCBhbmQgU0hPVUxEIGRpc2NhcmQgYW55IHBhY2tldA0KdGhhdCBhcnJpdmVzIHdpdGggYW4gdW5l
eHBlY3RlZCBwcm90b2NvbCB0eXBlPw0KDQpJIHdvdWxkIHRoaW5rIHRoYXQgdGhlIG51bWJlciBv
ZiBleHBlY3RlZCBwcm90b2NvbCB0eXBlcyBpcyB0eXBpY2FsbHkNCmEgc21hbGwgbnVtYmVyLCBh
bmQgdGhhdCBjaGVjayBwcm90ZWN0cyBhZ2FpbnN0IG1pc2ludGVycHJldGluZyBhIGhlYWRlcg0K
Zm9yIGVuY2Fwc3VsYXRlZCBwcm90b2NvbCBBIGFzIGEgaGVhZGVyIGZvciBlbmNhcHN1bGF0ZWQg
cHJvdG9jb2wgQiwNCndoaWNoIHVzdWFsbHkgd29u4oCZdCBhY2NvbXBsaXNoIG11Y2gsIGJ1dCBj
b3VsZCBvY2Nhc2lvbmFsbHkgY2F1c2UNCnJhdGhlciB1bmRlc2lyYWJsZSByZXN1bHRzLg0KSSBy
ZWFsaXplIHRoYXQgdGhpcyB0ZXh0IHdhcyBjb3BpZWQgZnJvbSBSRkMgMjc4NCwgYW5kIHRoYXQg
Y291bGQgYmUNCmEgcmVhc29uIHRvIG5vdCBtYWtlIHRoaXMgY2hhbmdlLg0KDQpUaGFua3MsDQot
LURhdmlkDQoNCkZyb206IEludC1hcmVhIFttYWlsdG86aW50LWFyZWEtYm91bmNlc0BpZXRmLm9y
Z10gT24gQmVoYWxmIE9mIFp1bmlnYSwgSnVhbiBDYXJsb3MNClNlbnQ6IE1vbmRheSwgTWFyY2gg
MzAsIDIwMTUgNDoyNyBQTQ0KVG86IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJlYUBp
ZXRmLm9yZz47IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+DQpDYzogZHJhZnQt
aWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxt
YWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBbSW50LWFyZWFdIFN0YXJ0
IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KDQoNCkRlYXIgSW50LUFy
ZWEgYW5kIDZtYW4gV0dzLA0KDQoNCg0KQXQgdGhlIEludC1BcmVhIFdHIG1lZXRpbmcgaW4gRGFs
bGFzIHRoZXJlIHdlcmUgc29tZSBjb21tZW50cyBvbiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlw
djYuIEl0IHdhcyBkZWNpZGVkIHRvIHN1Ym1pdCB0aGUgZG9jdW1lbnQgZm9yIFdHIExhc3QgQ2Fs
bCB0byB0aGUgSW50LUFyZWEgJiA2bWFuIFdHcyBhcyBzb29uIGFzIHRoZSBhZ3JlZWQgY2hhbmdl
cyB3ZXJlIG1hZGUuDQoNCg0KDQpUaGUgZG9jdW1lbnQgaGFzIG5vdyBiZWVuIHVwZGF0ZWQgYWNj
b3JkaW5nbHksIHNvIHRoaXMgZW1haWwgc3RhcnRzIGFuIEludC1BcmVhLzZtYW4gV0dzIExhc3Qg
Q2FsbCBvbjoNCg0KDQoNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaW50
YXJlYS1ncmUtaXB2Ni0wNA0KDQoNCg0KUGxlYXNlIHJlc3BvbmQgdG8gdGhpcyBlbWFpbCB0byBz
dXBwb3J0IHRoZSBkb2N1bWVudCBhbmQvb3Igc2VuZCBjb21tZW50cyBieSAyMDE1LTA0LTA2Lg0K
DQoNCg0KSW4gYWRkaXRpb24sIHRvIHNhdGlzZnkgUkZDIDY3MDIgIlByb21vdGluZyBDb21wbGlh
bmNlIHdpdGggSW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0cyAoSVBSKSI6DQoNCkFyZSB5b3Ug
cGVyc29uYWxseSBhd2FyZSBvZiBhbnkgSVBSIHRoYXQgYXBwbGllcyB0byBkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjY/DQoNCklmIHNvLCBoYXMgdGhpcyBJUFIgYmVlbiBkaXNjbG9zZWQgaW4g
Y29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzPw0KDQooU2VlIFJGQ3MgMzk3OSwgNDg3OSwg
MzY2OSwgYW5kIDUzNzggZm9yIG1vcmUgZGV0YWlscy4pDQoNCg0KDQpCZXN0LA0KDQoNCg0KSnVh
biBDYXJsb3MgWnVuaWdhDQooYXMgSW50LUFyZWEgV0cgY28tY2hhaXIpDQoNCg==

--_000_2691CE0099834E4A9C5044EEC662BB9D57155BE6dfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QFNpbVN1biI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29QbGFpblRleHQsIGRp
di5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5r
OiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1h
cmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBO
ZXcgUm9tYW4iLCJzZXJpZiI7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv
QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv
b24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNw
YW4uUGxhaW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCglt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5CYWxsb29uVGV4dENoYXIN
Cgl7bXNvLXN0eWxlLW5hbWU6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCI7DQoJZm9udC1mYW1pbHk6IlRh
aG9tYSIsInNhbnMtc2VyaWYiO30NCnAuaW1wcmludHVuaXF1ZWlkLCBsaS5pbXByaW50dW5pcXVl
aWQsIGRpdi5pbXByaW50dW5pcXVlaWQNCgl7bXNvLXN0eWxlLW5hbWU6aW1wcmludHVuaXF1ZWlk
Ow0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9t
YW4iLCJzZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjMNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0
ZXh0O30NCnNwYW4uRW1haWxTdHlsZTI0DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9y
bWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0K
c3Bhbi5FbWFpbFN0eWxlMjUNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxT
dHlsZTI2DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVy
IE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6
bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjcN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1z
dHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAx
LjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8
ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPkkgYW0gZmluZSB3aXRoIHByb3Bvc2VkIHdvcmsgYXJvdW5kIHRv
IFNlY3Rpb24gMi4yIGJ1dCB0aGF0IGRvZXMgbm90IHJlc29sdmUgdGhlIHRleHQgaW4gU2VjdGlv
biA0LjEuIElmIHRoaXMgZG9jdW1lbnQgaXMganVzdCB0byBkb2N1bWVudCBleGlzdGluZyBpbXBs
ZW1lbnRhdGlvbiwgaXQgbmVlZHMgcG9pbnQgb3V0IHRoZSB1c2FnZSBjb25zdHJhaW50cyB3aGVu
DQogSVB2NiBpcyBhcyBkZWxpdmVyeSBuZXR3b3JrLiBJIHByb3Bvc2VkIHRoZSBkcmFmdCB0ZXh0
LCBUb20gaGFkIHRoZSByZXZpc2VkIHRleHQuIERvIHlvdSBhZ3JlZSB0aGF0IHN1Y2ggdGV4dCBp
cyBuZWNlc3Nhcnk/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5MdWN5PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij4gSW50LWFyZWEgW21haWx0bzppbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVo
YWxmIE9mIDwvYj5CbGFjaywgRGF2aWQ8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2gg
MzEsIDIwMTUgNzo1OSBQTTxicj4NCjxiPlRvOjwvYj4gUm9uYWxkIEJvbmljYTsgaW50LWFyZWFA
aWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmc8YnI+DQo8Yj5DYzo8L2I+IGRyYWZ0LWlldGYtaW50YXJl
YS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8YnI+DQo8
Yj5TdWJqZWN0OjwvYj4gUmU6IFtJbnQtYXJlYV0gV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVh
LWdyZS1pcHY2IC0gRXRoZXJ0eXBlczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGF0IHNlZW1zIHJlYXNvbmFibGUg
LSB0aGUgcHJvdmVyYmlhbCDigJxyaWdodCB0aGluZyB0byBkb+KAnSB3b3VsZCBiZSB0byB1cGRh
dGUgMjc4NCB0byBhcHBseSB0aGlzIHJlY29tbWVuZGF0aW9uIGFjcm9zcyB0aGUgYm9hcmQsIGJ1
dCBJ4oCZbSBvayB3aXRoIHNpbXBseSByZW1vdmluZyB0aGUgU2VjdGlvbg0KIDIuMiB0ZXh0IGFu
ZCBsZWF2aW5nIHRoaW5ncyBhcyB0aGV5IGFyZSBpbiAyNzg0LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGFua3MsPGJyPg0KLS1EYXZpZDwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3Nw
YW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gUm9uYWxkIEJvbmljYSBbPGEgaHJl
Zj0ibWFpbHRvOnJib25pY2FAanVuaXBlci5uZXQiPm1haWx0bzpyYm9uaWNhQGp1bmlwZXIubmV0
PC9hPl0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSA4OjUzIFBN
PGJyPg0KPGI+VG86PC9iPiBCbGFjaywgRGF2aWQ7IFp1bmlnYSwgSnVhbiBDYXJsb3M7IDxhIGhy
ZWY9Im1haWx0bzppbnQtYXJlYUBpZXRmLm9yZyI+DQppbnQtYXJlYUBpZXRmLm9yZzwvYT47IDxh
IGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGlldGYub3JnPC9hPjxicj4NCjxiPkNj
OjwvYj4gPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5p
ZXRmLm9yZyI+ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnPC9hPjsN
CjxhIGhyZWY9Im1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+aW50YXJlYS1jaGFpcnNA
aWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBXR0xDIGZvciBkcmFmdC1pZXRm
LWludGFyZWEtZ3JlLWlwdjYgLSBFdGhlcnR5cGVzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRhdmlkLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+T25lIHdheSB0byBhZGRyZXNzIHRo
aXMgcHJvYmxlbSB3b3VsZCBiZSB0byByZW1vdmUgU2VjdGlvbiAyLjIgZW50aXJlbHkuIFNpbmNl
IHRoZSBzeW50YXggYW5kIHNlbWFudGljcyBvZiB0aGUgUHJvdG9jb2wgVHlwZSBmaWVsZCBpcyB1
bmNoYW5nZWQgZnJvbSBSRkMgMjc4NCwgdGhlIG9taXNzaW9uIG9mIFNlY3Rpb24gMi4yIGRvZXNu
4oCZdCBjaGFuZ2UgdGhlIG1lYW5pbmcNCiBvZiB0aGUgZHJhZnQgYXQgYWxsLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+V291bGQgdGhhdCBzb2x1dGlvbiB3b3JrIGZvciB5
b3U/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgUm9uPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAw
aW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBCbGFjaywgRGF2aWQg
WzxhIGhyZWY9Im1haWx0bzpkYXZpZC5ibGFja0BlbWMuY29tIj5tYWlsdG86ZGF2aWQuYmxhY2tA
ZW1jLmNvbTwvYT5dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUg
NzozNSBQTTxicj4NCjxiPlRvOjwvYj4gWnVuaWdhLCBKdWFuIENhcmxvczsgPGEgaHJlZj0ibWFp
bHRvOmludC1hcmVhQGlldGYub3JnIj5pbnQtYXJlYUBpZXRmLm9yZzwvYT47DQo8YSBocmVmPSJt
YWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBpZXRmLm9yZzwvYT48YnI+DQo8Yj5DYzo8L2I+IDxh
IGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmci
PmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzwvYT47DQo8YSBocmVm
PSJtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmciPmludGFyZWEtY2hhaXJzQGlldGYub3Jn
PC9hPjsgQmxhY2ssIERhdmlkPGJyPg0KPGI+U3ViamVjdDo8L2I+IFdHTEMgZm9yIGRyYWZ0LWll
dGYtaW50YXJlYS1ncmUtaXB2NiAtIEV0aGVydHlwZXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5TZWN0aW9uIDIuMiBzYXlzOjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IFRoZSBQcm90b2NvbCBUeXBlIGZp
ZWxkIGNvbnRhaW5zIHRoZSBwcm90b2NvbCB0eXBlIG9mIHRoZSBwYXlsb2FkPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZu
YnNwOyZuYnNwOyBwYWNrZXQuJm5ic3A7IFByb3RvY29sIFR5cGVzIGFyZSBkZWZpbmVkIGluIFtF
VFlQRVNdLiZuYnNwOyBBbiBpbXBsZW1lbnRhdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsgcmVj
ZWl2aW5nIGEgcGFja2V0IGNvbnRhaW5pbmcgYSBQcm90b2NvbCBUeXBlIHdoaWNoIGlzIG5vdCBs
aXN0ZWQgaW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90Oztjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7IFtFVFlQRVNdIFNIT1VMRCBkaXNjYXJkIHRo
ZSBwYWNrZXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGF0IGxhdHRlciBzZW50ZW5jZSBp
cyBhbG1vc3QgcG9pbnRsZXNzLCBhbmQgbW9yZW92ZXIsIGl04oCZcyBhbjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj51bmlt
cGxlbWVudGFibGUgbW92aW5nIHRhcmdldC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkNvdWxk
IHdlIHNheSB0aGF0IGFueSBHUkUgaW1wbGVtZW50YXRpb24gU0hPVUxEIGJlIGNvbmZpZ3VyZWQg
d2l0aDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOmJsYWNrIj50aGUgUHJvdG9jb2wgVHlwZXMgdGhhdCBhcmUgZXhwZWN0ZWQgYW5kIFNI
T1VMRCBkaXNjYXJkIGFueSBwYWNrZXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+dGhhdCBhcnJpdmVzIHdpdGggYW4gdW5l
eHBlY3RlZCBwcm90b2NvbCB0eXBlPyZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5J
IHdvdWxkIHRoaW5rIHRoYXQgdGhlIG51bWJlciBvZiBleHBlY3RlZCBwcm90b2NvbCB0eXBlcyBp
cyB0eXBpY2FsbHk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+YSBzbWFsbCBudW1iZXIsIGFuZCB0aGF0IGNoZWNrIHByb3Rl
Y3RzIGFnYWluc3QgbWlzaW50ZXJwcmV0aW5nIGEgaGVhZGVyPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPmZvciBlbmNhcHN1
bGF0ZWQgcHJvdG9jb2wgQSBhcyBhIGhlYWRlciBmb3IgZW5jYXBzdWxhdGVkIHByb3RvY29sIEIs
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6YmxhY2siPndoaWNoIHVzdWFsbHkgd29u4oCZdCBhY2NvbXBsaXNoIG11Y2gsIGJ1dCBjb3Vs
ZCBvY2Nhc2lvbmFsbHkgY2F1c2U8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij5yYXRoZXIgdW5kZXNpcmFibGUgcmVzdWx0cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SSByZWFsaXplIHRoYXQgdGhp
cyB0ZXh0IHdhcyBjb3BpZWQgZnJvbSBSRkMgMjc4NCwgYW5kIHRoYXQgY291bGQgYmU8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+YSByZWFzb24gdG8gbm90IG1ha2UgdGhpcyBjaGFuZ2UuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPlRoYW5rcyw8YnI+DQotLURhdmlkPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGlu
IDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFo
b21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBJbnQtYXJlYSBbPGEgaHJlZj0ibWFp
bHRvOmludC1hcmVhLWJvdW5jZXNAaWV0Zi5vcmciPm1haWx0bzppbnQtYXJlYS1ib3VuY2VzQGll
dGYub3JnPC9hPl0NCjxiPk9uIEJlaGFsZiBPZiA8L2I+WnVuaWdhLCBKdWFuIENhcmxvczxicj4N
CjxiPlNlbnQ6PC9iPiBNb25kYXksIE1hcmNoIDMwLCAyMDE1IDQ6MjcgUE08YnI+DQo8Yj5Ubzo8
L2I+IDxhIGhyZWY9Im1haWx0bzppbnQtYXJlYUBpZXRmLm9yZyI+aW50LWFyZWFAaWV0Zi5vcmc8
L2E+OyA8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+DQppcHY2QGlldGYub3JnPC9hPjxi
cj4NCjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2
NkB0b29scy5pZXRmLm9yZyI+ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYu
b3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzppbnRhcmVhLWNoYWlyc0BpZXRmLm9yZyI+aW50YXJl
YS1jaGFpcnNAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8L2I+IFtJbnQtYXJlYV0gU3Rh
cnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+RGVhciBJbnQtQXJlYSBhbmQgNm1h
biBXR3MsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkF0IHRoZSBJbnQtQXJlYSBXRyBt
ZWV0aW5nIGluIERhbGxhcyB0aGVyZSB3ZXJlIHNvbWUgY29tbWVudHMgb24gZHJhZnQtaWV0Zi1p
bnRhcmVhLWdyZS1pcHY2LiBJdCB3YXMgZGVjaWRlZCB0byBzdWJtaXQgdGhlIGRvY3VtZW50IGZv
ciBXRyBMYXN0IENhbGwgdG8gdGhlIEludC1BcmVhICZhbXA7IDZtYW4gV0dzIGFzIHNvb24gYXMg
dGhlIGFncmVlZCBjaGFuZ2VzIHdlcmUgbWFkZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+VGhlIGRvY3VtZW50IGhhcyBub3cgYmVlbiB1cGRhdGVkIGFjY29yZGluZ2x5LCBzbyB0aGlz
IGVtYWlsIHN0YXJ0cyBhbiBJbnQtQXJlYS82bWFuIFdHcyBMYXN0IENhbGwgb246PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni0wNCI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LTA0PC9hPg0KPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPlBsZWFzZSByZXNwb25kIHRvIHRoaXMgZW1haWwgdG8gc3VwcG9ydCB0aGUg
ZG9jdW1lbnQgYW5kL29yIHNlbmQgY29tbWVudHMgYnkgMjAxNS0wNC0wNi48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+SW4gYWRkaXRpb24sIHRvIHNhdGlzZnkgUkZDIDY3MDIgJnF1b3Q7
UHJvbW90aW5nIENvbXBsaWFuY2Ugd2l0aCBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIChJ
UFIpJnF1b3Q7OjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QXJlIHlv
dSBwZXJzb25hbGx5IGF3YXJlIG9mIGFueSBJUFIgdGhhdCBhcHBsaWVzIHRvIGRyYWZ0LWlldGYt
aW50YXJlYS1ncmUtaXB2Nj8mbmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+SWYgc28sIGhhcyB0aGlzIElQUiBiZWVuIGRpc2Nsb3NlZCBpbiBjb21wbGlhbmNl
IHdpdGggSUVURiBJUFIgcnVsZXM/PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij4oU2VlIFJGQ3MgMzk3OSwgNDg3OSwgMzY2OSwgYW5kIDUzNzggZm9yIG1vcmUgZGV0YWls
cy4pPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkJlc3QsPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPkp1YW4gQ2FybG9zIFp1bmlnYSA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPihhcyBJbnQtQXJlYSBXRyBjby1jaGFpcik8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_2691CE0099834E4A9C5044EEC662BB9D57155BE6dfweml701chm_--


From nobody Wed Apr  1 10:35:22 2015
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC9BD1A1A43; Wed,  1 Apr 2015 10:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: 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-nD6a7ol87T; Wed,  1 Apr 2015 10:35:17 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 349711A19F0; Wed,  1 Apr 2015 10:35:17 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t31HYjIX026043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 1 Apr 2015 10:34:45 -0700 (PDT)
Message-ID: <551C2C35.1070502@isi.edu>
Date: Wed, 01 Apr 2015 10:34:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, "Black, David" <david.black@emc.com>,  "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
References: <CE03DB3D7B45C245BCA0D243277949364312D6@MX104CL02.corp.emc.com> <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZKKfhPrJr7Ts67ZqmS_6Zkb-spE>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 17:35:19 -0000

On 3/31/2015 5:53 PM, Ronald Bonica wrote:
> David,
> 
>  
> 
> One way to address this problem would be to remove Section 2.2 entirely.
> Since the syntax and semantics of the Protocol Type field is unchanged
> from RFC 2784, the omission of Section 2.2 doesn’t change the meaning of
> the draft at all.

Yes, but it might still be useful to point out that IPv6 (unfortunately,
and undermining the whole point of the IP version number) uses a
different ethertype than IPv4.

(this is what happens when we let temporary hardware optimizations
influence long-term protocol design)

Joe


From nobody Wed Apr  1 10:39:17 2015
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE6651A01C6; Wed,  1 Apr 2015 10:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41MjXRt9LVw8; Wed,  1 Apr 2015 10:39:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD601A01AE; Wed,  1 Apr 2015 10:39:15 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t31HcLkQ026426 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 1 Apr 2015 10:38:21 -0700 (PDT)
Message-ID: <551C2D0E.5040303@isi.edu>
Date: Wed, 01 Apr 2015 10:38:22 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: stbryant@cisco.com, "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <551BA8F8.1080706@cisco.com>
In-Reply-To: <551BA8F8.1080706@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/G2zRhQBQLxePXLGaRJYYr3Suq4E>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 17:39:16 -0000

On 4/1/2015 1:14 AM, Stewart Bryant wrote:
> Because the IPv6 delivery header does not include a checksum of its
> own, it is subject to corruption. 
> 
> SB> It is subject to corruption whether or not it has a checksum.
> SB> The point is that there may be undetected corruption. However
> SB> detection in only probabilistic even with a checksum. So
> SB> I think that that this text should be:
> 
> Because the IPv6 delivery header does not include a checksum of its
> own, it is subject to higher probability of undetected corruption. 

The probability of undetected corruption is 100%. And a checksum isn't
the only way to detect errors.

IMO:

Because the IPv6 delivery header does not include error detection, it is
subject to undetected corruption.

Joe


From nobody Wed Apr  1 10:41:38 2015
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8691A0419; Wed,  1 Apr 2015 10:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvygiEDN7GnI; Wed,  1 Apr 2015 10:41:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 049A11A00B2; Wed,  1 Apr 2015 10:41:35 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t31Hf9Vd027093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 1 Apr 2015 10:41:10 -0700 (PDT)
Message-ID: <551C2DB6.1040906@isi.edu>
Date: Wed, 01 Apr 2015 10:41:10 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <BLUPR05MB4330BC16BBAB27EC4C224B6AEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831832E2EA83@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E2EA83@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/dF68V2lTfo9zHsVLtJ3yPzCJ8zg>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 17:41:37 -0000

+1

On 3/31/2015 10:29 AM, Templin, Fred L wrote:
> Broken behavior should not be specified, whether alternative or default.


From nobody Wed Apr  1 11:05:17 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79FC1A1AAE; Wed,  1 Apr 2015 11:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHnBUw6ksjWy; Wed,  1 Apr 2015 11:05:13 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 190E61A6F0A; Wed,  1 Apr 2015 11:05:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3340; q=dns/txt; s=iport; t=1427911503; x=1429121103; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=rW7L0P8r1QzyhhS909yiXbTYllc0FWft/5+t/VSEJdo=; b=QFE/ahzYQuy6jAEB8jObow57fMicJgnRGb2Z7gIJGM0D+EOnvKD4i725 +xaqPXyfk+0i+9EXtFYZnB94Qc/sJK52m3nsTyP/QyQ5gOskvh9qUp+py LQWVJbO90rY82vZWo7ZXJ1TmnTdkFXyrfn3o49e/x7eM8hPvvskZ+fX8p k=;
X-IronPort-AV: E=Sophos;i="5.11,505,1422921600";  d="scan'208,217";a="407751813"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 01 Apr 2015 18:05:01 +0000
Received: from [10.55.98.183] (ams-stbryant-8816.cisco.com [10.55.98.183]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t31I512q006431; Wed, 1 Apr 2015 18:05:01 GMT
Message-ID: <551C334C.6000503@cisco.com>
Date: Wed, 01 Apr 2015 19:05:00 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <551BA8F8.1080706@cisco.com> <551C2D0E.5040303@isi.edu>
In-Reply-To: <551C2D0E.5040303@isi.edu>
Content-Type: multipart/alternative; boundary="------------050003000909060305060003"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AcbtIN9zQLhmwZUpezzqgmzCGHs>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 18:05:16 -0000

This is a multi-part message in MIME format.
--------------050003000909060305060003
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 01/04/2015 18:38, Joe Touch wrote:
>
> On 4/1/2015 1:14 AM, Stewart Bryant wrote:
>> Because the IPv6 delivery header does not include a checksum of its
>> own, it is subject to corruption.
>>
>> SB> It is subject to corruption whether or not it has a checksum.
>> SB> The point is that there may be undetected corruption. However
>> SB> detection in only probabilistic even with a checksum. So
>> SB> I think that that this text should be:
>>
>> Because the IPv6 delivery header does not include a checksum of its
>> own, it is subject to higher probability of undetected corruption.
> The probability of undetected corruption is 100%. And a checksum isn't
> the only way to detect errors.
>
> IMO:
>
> Because the IPv6 delivery header does not include error detection, it is
> subject to undetected corruption.
>
> Joe
> .
>
I accept that there are other possible error checking technique, but
the original text is talking about checksum. However no check is
perfect so I still think it needs to be:

Because the IPv6 delivery header does not include error detection,
it is subject to a higher probability of undetected corruption.

- Stewart


--------------050003000909060305060003
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 01/04/2015 18:38, Joe Touch wrote:<br>
    </div>
    <blockquote cite="mid:551C2D0E.5040303@isi.edu" type="cite">
      <pre wrap="">

On 4/1/2015 1:14 AM, Stewart Bryant wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Because the IPv6 delivery header does not include a checksum of its
own, it is subject to corruption. 

SB&gt; It is subject to corruption whether or not it has a checksum.
SB&gt; The point is that there may be undetected corruption. However
SB&gt; detection in only probabilistic even with a checksum. So
SB&gt; I think that that this text should be:

Because the IPv6 delivery header does not include a checksum of its
own, it is subject to higher probability of undetected corruption. 
</pre>
      </blockquote>
      <pre wrap="">
The probability of undetected corruption is 100%. And a checksum isn't
the only way to detect errors.

IMO:

Because the IPv6 delivery header does not include error detection, it is
subject to undetected corruption.

Joe
.

</pre>
    </blockquote>
    <font color="#ff0000"><font color="#006600">I accept that there are
        other possible error checking technique, but<br>
        the original text is talking about checksum. However no check is
        <br>
        perfect so I still think it needs to be:<br>
        <br>
        Because the IPv6 delivery header does not include error
        detection, <br>
        it is
        subject to a higher probability of undetected corruption.
        <br>
        <br>
        - Stewart</font><br>
    </font><br>
  </body>
</html>

--------------050003000909060305060003--


From nobody Wed Apr  1 11:28:37 2015
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66EFA1A8830; Wed,  1 Apr 2015 11:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdMx2b4Ho63E; Wed,  1 Apr 2015 11:28:33 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7F51A8AEB; Wed,  1 Apr 2015 11:28:32 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t31ISIa5005281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 1 Apr 2015 11:28:18 -0700 (PDT)
Message-ID: <551C38C2.1040006@isi.edu>
Date: Wed, 01 Apr 2015 11:28:18 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: stbryant@cisco.com, "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-ipv6
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <551BA8F8.1080706@cisco.com> <551C2D0E.5040303@isi.edu> <551C334C.6000503@cisco.com>
In-Reply-To: <551C334C.6000503@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rATv7FXqxyUXtDZV71YOHBRP8-M>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 18:28:34 -0000

On 4/1/2015 11:05 AM, Stewart Bryant wrote:
> On 01/04/2015 18:38, Joe Touch wrote:
>>
>> On 4/1/2015 1:14 AM, Stewart Bryant wrote:
>>> Because the IPv6 delivery header does not include a checksum of its
>>> own, it is subject to corruption. 
>>>
>>> SB> It is subject to corruption whether or not it has a checksum.
>>> SB> The point is that there may be undetected corruption. However
>>> SB> detection in only probabilistic even with a checksum. So
>>> SB> I think that that this text should be:
>>>
>>> Because the IPv6 delivery header does not include a checksum of its
>>> own, it is subject to higher probability of undetected corruption. 
>> The probability of undetected corruption is 100%. And a checksum isn't
>> the only way to detect errors.
>>
>> IMO:
>>
>> Because the IPv6 delivery header does not include error detection, it is
>> subject to undetected corruption.
>>
>> Joe
>> .
>>
> I accept that there are other possible error checking technique, but
> the original text is talking about checksum. However no check is
> perfect so I still think it needs to be:
> 
> Because the IPv6 delivery header does not include error detection,
> it is subject to a higher probability of undetected corruption.

Point taken. Better.

Joe


From nobody Wed Apr  1 12:21:10 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001711A8849 for <ipv6@ietfa.amsl.com>; Wed,  1 Apr 2015 12:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 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, SPF_PASS=-0.001] autolearn=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 NGNTiJpeFIX0 for <ipv6@ietfa.amsl.com>; Wed,  1 Apr 2015 12:21:06 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::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 DB67D1A8A8B for <ipv6@ietf.org>; Wed,  1 Apr 2015 12:21:05 -0700 (PDT)
Received: by labe2 with SMTP id e2so44415928lab.3 for <ipv6@ietf.org>; Wed, 01 Apr 2015 12:21:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; bh=8l2oS6IqvnZ3b0nfkxwaAbfOl+iSFAugziVM8BBPWws=; b=Uh8Lo07lCf6AT05PvmDX3ysL/f6ukuvNfIzSgA+C+uppwNcqNEtJ6gEZYDyCp5rPWU G8xDAt7clkZyAxnA7ZzUHSgWmUxppwgiPgPPw04eUw++HaGmz+hN22qdaM6az6Bda7GF tnyVmG+SzkcpKAGzNieou8HXj3hSU4Qg669Dh4GxtzPEVp9iFdl8A8U2AF0lwNXCAv8S GLP1tl/+ZgDxpsUZnC/9N7ODuJt0mp0tSOaC/dbIz5lSRSbKGqpM1w4JpHPgcmjLXzbc 6p8HDEuQBL8a7f1I2uLXny7+xHWIJ389ob0fGnIAea1AAZN4yrtCSJc7YsEQdzbMjSiq nrJA==
MIME-Version: 1.0
X-Received: by 10.152.37.69 with SMTP id w5mr37268912laj.15.1427916064421; Wed, 01 Apr 2015 12:21:04 -0700 (PDT)
Received: by 10.114.59.103 with HTTP; Wed, 1 Apr 2015 12:21:04 -0700 (PDT)
Date: Wed, 1 Apr 2015 14:21:04 -0500
Message-ID: <CAC8QAccQ6hmEpOE5KB=L361nt41V1JcwfFn9o7=Y1sS7yw0aMA@mail.gmail.com>
Subject: Re: RA Option Guidelines
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/j4Nzyc26WKCTjEhuHnd0Tz_tYAU>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 19:21:09 -0000

 I don't understand why DHCPv6 is being discussed under RA Option Guidelines?
If DHCPv6 is being used instead of RA, like in Australia, that
supports our position that we should also define DHCPv6 options for
SADR.

Regards,
Behcet

On Tue, Mar 31, 2015 at 9:33 PM, Mark ZZZ Smith
<markzzzsmith@yahoo.com.au> wrote:
> Hi Barbara,
>
> ________________________________
> From: "STARK, BARBARA H" <bs7652@att.com>
> To: Hemant Singh (shemant) <shemant@cisco.com>; Mark ZZZ Smith
> <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@innovationslab.net>;
> "ipv6@ietf.org" <ipv6@ietf.org>
> Sent: Wednesday, 1 April 2015, 0:24
> Subject: RE: RA Option Guidelines
>
>
>
>> The problem that Mark  raised and also provided a solution for is to add
>> DHCPv6 relay functionality to the CE router.  He is also correct that RFC
>> 6204
>> does not include DHCPv6 relay agent functionality in the CE router.
>>
>> The other choice for a solution is to include the DHCPv6 options in the
>> RA.
>> For this solution to work the SP will send new DHCPv6 options in the RA to
>> the CE router WAN.  The RA terminates at the CE WAN.  The CE generates a
>> new RA for the LAN.  RFC 6204 does not include functionality to bridge the
>> SP
>> RA received on the CE WAN to the CE LAN.  So even for the RA solution to
>> work, a new requirement would need to be added to RFC 6204.  Did I miss
>> anything in the RA solution I described above?  If not, either way, one
>> adds a
>> new requirement to the CE router and if it's DHCPv6 options, let DHCPv6
>> protocol deal with it.
>
>
> RFC 7084 already says:
>   L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>           options (as listed in Section 5.3 of [RFC3736]) received from
>           the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>           server.
> Where the RFC3736 list of options is for DNS Recursive Name Servers, DNS
> search list, and SIP Servers.
>
> My personal, as-a-consumer, freaking-out-about-privacy opinion is that the
> idea of my ISPs (both of them, but potentially 3) sending any configuration
> options they feel like down to my personal and private LAN host devices is
> not to my liking. I realize that some people are blithely happy to turn over
> their privacy to ISPs. So maybe relay of all unrecognized options could be
> something an ISP puts into CE routers they supply to their customers. I
> prefer for it not to be in the retail ones I purchase, and I would be
> adamant about it not being on by default in such retail CE routers. So let
> such relay requirements go into eRouter or BBF specs, but please keep them
> out of IETF and homenet specs.
>
> / I think you're already trusting your ISP possibly much more than you might
> realise. They're already supplying you with the Internet addressing you use,
> you're probably using their DNS resolvers, you may be using their email
> servers, and of course they can tap your clear text traffic without you
> knowing.
>
> / Even if you only used their addressing and encrypted all of your traffic
> over a tunnel through their infrastructure, you'd still then be trusting the
> remote tunnel endpoint provider, likely to be another party other than
> yourself.
>
> Since I'm in the process of setting up my new homenet router (Pierre flashed
> my new router for me last week) to connect upstream to both my ISPs (one
> cable provider and one telco), I also really don't want dueling relayed
> options reaching my LAN hosts. I do think that in the future a significant
> number of people will choose to subscribe to multiple providers -- as long
> as it's easy to do. The ISPs get to configure the CE router WAN interfaces
> to work with their access networks -- and that needs to be the extent of
> their reach unless I specifically give them conscious permission to do more.
> If they want to configure devices inside my LAN, I think they should use a
> higher layer configuration protocol with mandatory and default-on security
> (which neither RA nor DHCPv6 have).
>
> / So I think the world is moving in the other direction. People have been
> outsourcing the maintenance of their devices in droves as they adopt
> smartphones and tablets, and more recently with devices like Google's
> Chromebooks. They're giving up control rather than desiring more of it, for
> the gains of more convenience and lower costs.
>
> / Regards,
> Mark.
>
>
> Barbara
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Wed Apr  1 14:13:10 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D351AC3E6; Wed,  1 Apr 2015 14:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czTOeYitUf7O; Wed,  1 Apr 2015 14:13:06 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0129.outbound.protection.outlook.com [65.55.169.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B6B41AC3BA; Wed,  1 Apr 2015 14:13:03 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.1.130.23; Wed, 1 Apr 2015 21:13:01 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Wed, 1 Apr 2015 21:13:01 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Joe Touch <touch@isi.edu>, "Black, David" <david.black@emc.com>, "Zuniga,  Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Topic: [Int-area] WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
Thread-Index: AdBsC0O9ImygMEJJSjuvdoFVvO3XwAACaYSQACNOuYAAB4U9QA==
Date: Wed, 1 Apr 2015 21:13:01 +0000
Message-ID: <CO1PR05MB4426DC95EED8A1B1E49C61EAEF30@CO1PR05MB442.namprd05.prod.outlook.com>
References: <CE03DB3D7B45C245BCA0D243277949364312D6@MX104CL02.corp.emc.com> <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com> <551C2C35.1070502@isi.edu>
In-Reply-To: <551C2C35.1070502@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
authentication-results: isi.edu; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB442;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(979002)(6009001)(479174004)(51704005)(377454003)(13464003)(24454002)(33656002)(77156002)(230783001)(62966003)(87936001)(2656002)(19580395003)(2171001)(76576001)(19580405001)(102836002)(66066001)(92566002)(2501003)(2201001)(99286002)(74316001)(86362001)(50986999)(54356999)(76176999)(2950100001)(46102003)(122556002)(40100003)(2900100001)(7059030)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
x-microsoft-antispam-prvs: <CO1PR05MB4425375986F8C28406BA1A0AEF30@CO1PR05MB442.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CO1PR05MB442; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB442; 
x-forefront-prvs: 053315510E
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2015 21:13:01.0498 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB442
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Cm1juF1cj9q9DIWJ45eAyavEp30>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 21:13:08 -0000

Joe,

The reminder that you mention is already in Section 3. Text is included at =
the bottom of this message.

                                                   Ron

TEXT
------
3. IPv6 as a GRE Payload

When the GRE payload is IPv6, the Protocol Type field in the GRE header MUS=
T be set to Ether Type [ETYPES] 0x86DD.

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Wednesday, April 01, 2015 1:35 PM
> To: Ronald Bonica; Black, David; Zuniga, Juan Carlos; int-area@ietf.org;
> ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: Re: [Int-area] WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
>=20
>=20
>=20
> On 3/31/2015 5:53 PM, Ronald Bonica wrote:
> > David,
> >
> >
> >
> > One way to address this problem would be to remove Section 2.2 entirely=
.
> > Since the syntax and semantics of the Protocol Type field is unchanged
> > from RFC 2784, the omission of Section 2.2 doesn't change the meaning
> > of the draft at all.
>=20
> Yes, but it might still be useful to point out that IPv6 (unfortunately, =
and
> undermining the whole point of the IP version number) uses a different
> ethertype than IPv4.
>=20
> (this is what happens when we let temporary hardware optimizations
> influence long-term protocol design)
>=20
> Joe


From nobody Wed Apr  1 14:25:45 2015
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E48111A1ACA; Wed,  1 Apr 2015 14:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fzz7BHE7ghk6; Wed,  1 Apr 2015 14:25:42 -0700 (PDT)
Received: from webspace.isi.edu (webspace.isi.edu [128.9.64.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC1FB1A1A79; Wed,  1 Apr 2015 14:25:42 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id t31LNNrM021791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 1 Apr 2015 14:23:23 -0700 (PDT)
Message-ID: <551C61CC.1000006@isi.edu>
Date: Wed, 01 Apr 2015 14:23:24 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, "Black, David" <david.black@emc.com>,  "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
References: <CE03DB3D7B45C245BCA0D243277949364312D6@MX104CL02.corp.emc.com> <CO1PR05MB4428318DEE150733EA56C16AEF30@CO1PR05MB442.namprd05.prod.outlook.com> <551C2C35.1070502@isi.edu> <CO1PR05MB4426DC95EED8A1B1E49C61EAEF30@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4426DC95EED8A1B1E49C61EAEF30@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GJNyvsvsHJ2-_caUy4B3thUkv6g>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 21:25:44 -0000

Ahh - thanks. I don't think it matters in what section it appears.

Joe

On 4/1/2015 2:13 PM, Ronald Bonica wrote:
> Joe,
> 
> The reminder that you mention is already in Section 3. Text is included at the bottom of this message.
> 
>                                                    Ron
> 
> TEXT
> ------
> 3. IPv6 as a GRE Payload
> 
> When the GRE payload is IPv6, the Protocol Type field in the GRE header MUST be set to Ether Type [ETYPES] 0x86DD.
> 
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Wednesday, April 01, 2015 1:35 PM
>> To: Ronald Bonica; Black, David; Zuniga, Juan Carlos; int-area@ietf.org;
>> ipv6@ietf.org
>> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
>> Subject: Re: [Int-area] WGLC for draft-ietf-intarea-gre-ipv6 - Ethertypes
>>
>>
>>
>> On 3/31/2015 5:53 PM, Ronald Bonica wrote:
>>> David,
>>>
>>>
>>>
>>> One way to address this problem would be to remove Section 2.2 entirely.
>>> Since the syntax and semantics of the Protocol Type field is unchanged
>>> from RFC 2784, the omission of Section 2.2 doesn't change the meaning
>>> of the draft at all.
>>
>> Yes, but it might still be useful to point out that IPv6 (unfortunately, and
>> undermining the whole point of the IP version number) uses a different
>> ethertype than IPv4.
>>
>> (this is what happens when we let temporary hardware optimizations
>> influence long-term protocol design)
>>
>> Joe


From nobody Wed Apr  1 14:33:51 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0AE51A01E2; Wed,  1 Apr 2015 14:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V32Boq5XUx4F; Wed,  1 Apr 2015 14:33:42 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91F2B1A1BD4; Wed,  1 Apr 2015 14:33:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t31LXfI1005211; Wed, 1 Apr 2015 14:33:41 -0700
Received: from XCH-BLV-408.nw.nos.boeing.com (xch-blv-408.nw.nos.boeing.com [130.247.25.166]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t31LXZNR005166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 1 Apr 2015 14:33:36 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-BLV-408.nw.nos.boeing.com ([169.254.8.179]) with mapi id 14.03.0210.002; Wed, 1 Apr 2015 14:33:35 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYgAALjyCA=
Date: Wed, 1 Apr 2015 21:33:34 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/IiQ8Y03Nda6Sym0YjULjgJ4qZpI>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 21:33:48 -0000

Hi David,

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Wednesday, April 01, 2015 1:26 PM
> To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org; =
Black, David
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> Fred,
>=20
> > > > No, that's is not right. GMTU < 1280 is not necessarily an indicati=
on
> > > > that something is wrong, as explained in Section 7 of RFC2473. The
> > > > same considerations apply here.
> > >
> > > I agree with the text quoted above,
>=20
> Adding the rest of the sentence ...
>=20
> > > but what I'm observing is that there
> > > are networks for which GMTU is an indication that something is wrong
> > > (this is a consequence of operator decisions that are specific to suc=
h
> > > a network).
>=20
> > OK, then this document should cite Section 7 of RFC2473 normatively.
>=20
> I think it would be better to directly explain the GRE situation here, an=
d
> add an informative citation of RFC 2473 as providing additional explanati=
on,
> particularly for situations in which different operational practices are =
used.

How is the GRE situation any different than for any generic encapsulation
in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific use
cases"? Section 7 of RFC2473 already provides guidance that applies also
to GRE in any use case.=20

> > If there is operational assurance that all links in the tunnel path con=
figure
> > a sufficiently large MTU, and there will never be a nesting of tunnels =
that
> > would result in a too-small MTU, then tunnel fragmentation would not
> > need to be invoked and there is no need to talk about sending PTBs with
> > GMTU less than 1280.
>=20
> Never say "never" ... quoting RFC 5706, "Anything that can be configured =
can
> be misconfigured." ;-).

Right, that's what I said (having used that phrase many times in
the past myself).

> I'll leave the rationale for sending PTBs to Ron, but keep in mind that
> "running code" (i.e., existing implementations) is(are) an important
> consideration - see the second sentence in the Introduction.

Sending PTB with MTU<1280 is supposed to have an effect as described
in Section 5 of RFC. Namely, the original source is supposed to start
including IPv6 fragment headers in subsequent packets and the network
is supposed to find some way to get them through. What Ron's text
is suggesting is that the original source lives up to its part of the barga=
in
but then the network dumps the packets into a black hole.

> > Or, if you did want to include text that would tell
> > what to do in the case of misconfigurations, then this document would
> > need to update RFC2473 since the same considerations apply to generic
> > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
>=20
> It's more than misconfigurations - attacks on PMTU monitoring can have
> similar effects.

If you want to start talking about PTB forgery, then we should also talk
about  PTB filtering and how the mechanisms work when PTBs are lost.
RFC2473 itself is imperfect in that regard, and this draft is not proposing
anything different than RFC2473.

> Beyond that, if an update to RFC 2473 is desired, this GRE-scoped draft
> seems like a poor vehicle for that purpose (e.g., as RFC 2784 does not
> cite RFC 2473); I think a separate draft would be more appropriate.

OK, then have this draft simply cite RFC2473, Section 7 normatively
and break the exception cases out into a separate document like
intarea-tunnels. The exception cases are not limited to GRE in
particular, and apply also to any generic tunneling in IPv6.

Thanks - Fred
fred.l.templin@boeing.com


> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > Sent: Wednesday, April 01, 2015 12:12 PM
> > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> >
> > Hi David,
> >
> > > -----Original Message-----
> > > From: Black, David [mailto:david.black@emc.com]
> > > Sent: Wednesday, April 01, 2015 8:43 AM
> > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg;
> > Black, David
> > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative config=
uration
> > >
> > > Fred,
> > >
> > > > No, that's is not right. GMTU < 1280 is not necessarily an indicati=
on
> > > > that something is wrong, as explained in Section 7 of RFC2473. The
> > > > same considerations apply here.
> > >
> > > I agree with the text quoted above,
> >
> > OK, then this document should cite Section 7 of RFC2473 normatively.
> >
> > > but what I'm observing is that there
> > > are networks for which GMTU is an indication that something is wrong
> > > (this is a consequence of operator decisions that are specific to suc=
h
> > > a network).  The alternative configuration is intended for such netwo=
rks,
> > > but is not intended for all networks, and would need to be qualified
> > > with words making it applicable primarily or only (or suggest some
> > > other words) to such networks.
> >
> > If there is operational assurance that all links in the tunnel path con=
figure
> > a sufficiently large MTU, and there will never be a nesting of tunnels =
that
> > would result in a too-small MTU, then tunnel fragmentation would not
> > need to be invoked and there is no need to talk about sending PTBs with
> > GMTU less than 1280. Or, if you did want to include text that would tel=
l
> > what to do in the case of misconfigurations, then this document would
> > need to update RFC2473 since the same considerations apply to generic
> > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> > > Upshot: the use of "necessarily" in the text quoted above is correct,=
 but
> > > misses the point.
> > >
> > > Thanks,
> > > --David
> > >
> > > > -----Original Message-----
> > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > Sent: Wednesday, April 01, 2015 10:13 AM
> > > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf=
.org
> > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > configuration
> > > >
> > > > Hi David,
> > > >
> > > > > -----Original Message-----
> > > > > From: Black, David [mailto:david.black@emc.com]
> > > > > Sent: Tuesday, March 31, 2015 7:06 PM
> > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ie=
tf.org;
> > > > Black, David
> > > > > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative config=
uration
> > > > >
> > > > > So, I talked to Ron off-list and it looks like something is missi=
ng from
> > > > > this discussion.
> > > > >
> > > > > The "alternative configuration" is not motivated by a desire to a=
llow
> > > > > implementation flexibility or bless broken implementations.  It's
> > motivated
> > > > > by consideration of networks with operational practices wherein a=
 GMTU
> > of
> > > > > less than 1280 octets is evidence that something is seriously wro=
ng.
> > That
> > > > > something might be misconfiguration (quoting RFC 5706, "Anything =
that
> > > > > can be configured can be misconfigured."), or an attack on the GR=
E
> > > > > ingress's PMTU estimation.
> > > > >
> > > > > So, in the situation of interest (GMTU < 1280) something is wrong=
, and
> > > > > the operator may be faced with a Hobson's choice: either blackhol=
e the
> > > > > traffic that can no longer be sent without fragmentation, or frag=
ment a
> > > > > lot of traffic, causing problems at the GRE egress by overwhelmin=
g its
> > > > > reassembly code - there may be good operational and/or security r=
easons
> > > > > to not want to do the latter.  All of this ought to be explained =
in the
> > > > > draft.
> > > >
> > > > No, that's is not right. GMTU < 1280 is not necessarily an indicati=
on
> > > > that something is wrong, as explained in Section 7 of RFC2473. The
> > > > same considerations apply here.
> > > >
> > > > Thanks - Fred
> > > > fred.l.templin@boeing.com
> > > >
> > > > > Thanks,
> > > > > --David
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of
> > Templin,
> > > > Fred L
> > > > > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > chairs@ietf.org
> > > > > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gr=
e-ipv6
> > > > > >
> > > > > > Hi Ron,
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ie=
tf.org;
> > > > > > intarea-chairs@ietf.org
> > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-=
gre-
> > ipv6
> > > > > > >
> > > > > > > Fred,
> > > > > > >
> > > > > > > It appears that we disagree and have taken to repeating ourse=
lves.
> > > > > >
> > > > > > This is not a disagreement; this is a case in which the text is
> > actually
> > > > > > broken
> > > > > > which you have more or less acknowledged. You can fix the text =
in
> > question
> > > > > > as follows:
> > > > > >
> > > > > > OLD:
> > > > > > ****
> > > > > >    In its default configuration, the GRE ingress router MUST:
> > > > > >
> > > > > >    o  encapsulate the entire IPv6 packet in a single GRE header=
 and IP
> > > > > >       delivery header
> > > > > >
> > > > > >    o  fragment the delivery header, so that it can be reassembl=
ed by
> > the
> > > > > >       GRE egress
> > > > > >
> > > > > >    However, in an alternative configuration, the GRE ingress MA=
Y:
> > > > > >
> > > > > >    o  discard the IPv6 packet
> > > > > >
> > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to =
the
> > IPv6
> > > > > >       packet source.  The MTU field in the ICMPv6 PTB message i=
s set
> > to
> > > > > >       the GMTU.
> > > > > >
> > > > > > NEW:
> > > > > > ****
> > > > > >    The GRE ingress router MUST:
> > > > > >
> > > > > >    o  if the IPv6 payload packet includes a fragment header, fr=
agment
> > the
> > > > > >        payload packet into fragments no larger than the GMTU an=
d
> > > > encapsulate
> > > > > >       each fragment in a single GRE header and IP delivery head=
er.
> > > > Otherwise:
> > > > > >
> > > > > >       o encapsulate the entire IPv6 packet in a single GRE head=
er and
> > IP
> > > > > >           delivery header
> > > > > >
> > > > > >       o fragment the delivery packet, so that it can be reassem=
bled by
> > the
> > > > > >           GRE egress
> > > > > >
> > > > > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message t=
o the
> > IPv6
> > > > > >          packet source, subject to rate limiting.  The MTU fiel=
d in
> > the
> > > > ICMPv6
> > > > > > PTB
> > > > > >         message is set to the GMTU.
> > > > > >
> > > > > > > So, why don't we solicit opinions from the rest of the WG and=
 defer
> > to
> > > > their
> > > > > > will.
> > > > > >
> > > > > > We can't do that for broken text. Ram-rodding broken text throu=
gh the
> > > > > > process based on popular opinion does not make it good.
> > > > > >
> > > > > > Thanks - Fred
> > > > > > fred.l.templin@boeing.com
> > > > > >
> > > > > > >
> > > > > > >                                                         Ron
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > ipv6@tools.ietf.org;
> > > > > > intarea-
> > > > > > > > chairs@ietf.org
> > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intare=
a-gre-
> > ipv6
> > > > > > > >
> > > > > > > > Hi Ron,
> > > > > > > >
> > > > > > > > I will say again that the minimum IPv6 link MTU is 1280 byt=
es and
> > so
> > > > the
> > > > > > > > design must account for tunnel paths that include links wit=
h such
> > a
> > > > small
> > > > > > > > MTU. The design must also account for nested tunnels-within=
-
> > tunnels,
> > > > > > > > where the MTU seen by the first tunnel ingress may be reduc=
ed by
> > > > > > > > potentially many layers of additional encapsulation.
> > > > > > > >
> > > > > > > > But again, the point is that the tunnel ingress cannot
> > legitimately
> > > > send
> > > > > > PTBs
> > > > > > > > that report a size smaller than 1280 *and* perpetually drop
> > packets
> > > > > > smaller
> > > > > > > > than 1280 which is exactly the behavior your text is permit=
ting.
> > > > > > > >
> > > > > > > > Thanks - Fred
> > > > > > > > fred.l.templin@boeing.com
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > ipv6@tools.ietf.org;
> > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-inta=
rea-
> > gre-
> > > > ipv6
> > > > > > > > >
> > > > > > > > > Fred,
> > > > > > > > >
> > > > > > > > > In the last network that I operated, all interior links h=
ad MTU
> > > > > > > > > greater than 9k. If I configured a GRE tunnel between two=
 points
> > in
> > > > that
> > > > > > > > network and detected a GMTU less than 1280, it would have
> > indicated
> > > > one of
> > > > > > > > the following:
> > > > > > > > >
> > > > > > > > > - Phenomenal brokenness
> > > > > > > > > - An ICMP PTB-based attack in progress
> > > > > > > > >
> > > > > > > > > In such cases, operators need some flexibility in how the=
ir
> > networks
> > > > > > > > > would behave. Why deny them this flexibility by taking aw=
ay the
> > > > > > > > configuration option?
> > > > > > > > >
> > > > > > > > > Isn't it an operator's prerogative to discard any packet =
that
> > might
> > > > > > degrade
> > > > > > > > network performance?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Ron
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com=
]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > ipv6@tools.ietf.org;
> > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > >
> > > > > > > > > > Hi Ron,
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > >
> > > > > > > > > > > Fred,
> > > > > > > > > > >
> > > > > > > > > > > Some (if not most) operators maintain networks in whi=
ch all
> > > > links
> > > > > > > > > > > have MTU greater than or equal to 1500. In those netw=
orks,
> > the
> > > > > > > > > > > very detection of a GMTU smaller than 1280 indicates
> > brokenness.
> > > > > > > > > > > Those
> > > > > > > > > > operators, the alternative behavior may be preferable t=
o the
> > > > default.
> > > > > > > > > >
> > > > > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how much th=
e link
> > must
> > > > > > > > > > deliver no matter what. A GMTU smaller than 1280 does n=
ot
> > indicate
> > > > > > > > > > brokennesss; it can naturally happen if 1) there is a l=
ink
> > with a
> > > > > > > > > > small MTU in the path, or
> > > > > > > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > > > > > > >
> > > > > > > > > > As such, sustained dropping of packets less than 1280 i=
s a no-
> > no,
> > > > > > > > > > and cannot be specified in a document like this.
> > > > > > > > > >
> > > > > > > > > > Thanks - Fred
> > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Ron
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing=
.com]
> > > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Ron,
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Fred,
> > > > > > > > > > > > >
> > > > > > > > > > > > >      Inline.....
> > > > > > > > > > > > >
> > > > > > > > > > > > >                Ron
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >    ?However, in an alternative configuration, t=
he GRE
> > > > ingress
> > > > > > MAY:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4=
443]
> > > > message
> > > > > > > > > > > > > > to the
> > > > > > > > > > IPv6
> > > > > > > > > > > > > >       packet source.  The MTU field in the ICMP=
v6 PTB
> > > > message
> > > > > > is set
> > > > > > > > to
> > > > > > > > > > > > > >       the GMTU.?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > This means that there may be circumstances when=
 the
> > GRE
> > > > > > > > > > > > > > ingress sends a PTB reporting a size less than =
1280.
> > > > > > > > > > > > > > According to RFC2460, Section 5, the standard b=
ehavior
> > for
> > > > a
> > > > > > > > > > > > > > host that receives
> > > > > > > > > > such a PTB is:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > > > > >   is not required to reduce the size of subsequ=
ent
> > packets
> > > > to
> > > > > > less
> > > > > > > > than
> > > > > > > > > > > > > >    1280, but must include a Fragment header in =
those
> > > > packets?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > So, hosts that obey RFC2460 Section 5 will see =
a
> > perpetual
> > > > > > > > > > > > > > black hole if the GMTU is smaller than 1280 whi=
ch is
> > > > > > > > > > > > > > probably not what we
> > > > > > > > > > > > want.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > All true. This is why the WG decided to make this=
 the
> > > > > > > > > > > > > alternative behavior
> > > > > > > > > > > > and not the default behavior.
> > > > > > > > > > > >
> > > > > > > > > > > > Behavior that is broken is still broken regardless =
of
> > whether
> > > > it
> > > > > > > > > > > > is alternative or default.
> > > > > > > > > > > >
> > > > > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to prov=
ide
> > > > guidance
> > > > > > > > > > > > > > to hosts on how to react to PTB messages that r=
eport a
> > > > small
> > > > > > size.
> > > > > > > > > > > > > > But, as of right now,
> > > > > > > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > >
> > > > > > > > > > > > > Absolutely correct. The procedures described in S=
ection
> > 5 or
> > > > > > > > > > > > > RFC
> > > > > > > > > > > > > 246 are
> > > > > > > > > > > > normative.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I don't how this impacts the WG's LC decision reg=
arding
> > the
> > > > > > > > > > > > > current
> > > > > > > > > > draft.
> > > > > > > > > > > >
> > > > > > > > > > > > Broken behavior should not be specified, whether
> > alternative
> > > > or
> > > > > > > > default.
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ron
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Int-area mailing list
> > > > > > Int-area@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 14:40:04 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DECC1AC3BE; Wed,  1 Apr 2015 13:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49wTtxHC3S8O; Wed,  1 Apr 2015 13:27:00 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 4B49F1A9173; Wed,  1 Apr 2015 13:26:20 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31KQE5U015137 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Apr 2015 16:26:17 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t31KQE5U015137
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427919977; bh=QGQcnoV2blk2t3fFYHAfEUwBeQU=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=IhfmKz2EZDGzaGqexRkeQlqCBDfUtYTvgy3vl6aDiRNUyTJHpkX4J2cCwy1L/91vp Dv547xAM5jvs3zBXx0/K2iqoIDOtluP6vjKImHRfhwYmwPKGjEVhqIS59dCjqEdwfa ISMTNbwb7L8Xs6q3Cs+QzLm+OSHBgnkyvKxpeXjs=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t31KQE5U015137
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd02.lss.emc.com (RSA Interceptor); Wed, 1 Apr 2015 16:25:47 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31KQ1CX016694 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 16:26:03 -0400
Received: from MXHUB206.corp.emc.com (10.253.68.32) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 1 Apr 2015 16:26:00 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB206.corp.emc.com ([10.253.68.32]) with mapi id 14.03.0224.002; Wed, 1 Apr 2015 16:26:00 -0400
From: "Black, David" <david.black@emc.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYg
Date: Wed, 1 Apr 2015 20:26:00 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vxY0-RkLNUZaZZzY_OVcM3OVIK8>
X-Mailman-Approved-At: Wed, 01 Apr 2015 14:40:03 -0700
Cc: "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 20:27:04 -0000

Fred,

> > > No, that's is not right. GMTU < 1280 is not necessarily an indication
> > > that something is wrong, as explained in Section 7 of RFC2473. The
> > > same considerations apply here.
> >
> > I agree with the text quoted above,

Adding the rest of the sentence ...

> > but what I'm observing is that there
> > are networks for which GMTU is an indication that something is wrong
> > (this is a consequence of operator decisions that are specific to such
> > a network).

> OK, then this document should cite Section 7 of RFC2473 normatively.

I think it would be better to directly explain the GRE situation here, and
add an informative citation of RFC 2473 as providing additional explanation=
,
particularly for situations in which different operational practices are us=
ed.

> If there is operational assurance that all links in the tunnel path confi=
gure
> a sufficiently large MTU, and there will never be a nesting of tunnels th=
at
> would result in a too-small MTU, then tunnel fragmentation would not
> need to be invoked and there is no need to talk about sending PTBs with
> GMTU less than 1280.

Never say "never" ... quoting RFC 5706, "Anything that can be configured ca=
n
be misconfigured." ;-).

I'll leave the rationale for sending PTBs to Ron, but keep in mind that
"running code" (i.e., existing implementations) is(are) an important
consideration - see the second sentence in the Introduction.

> Or, if you did want to include text that would tell
> what to do in the case of misconfigurations, then this document would
> need to update RFC2473 since the same considerations apply to generic
> encapsulation over IPv6 and not just GRE encapsulation over IPv6.

It's more than misconfigurations - attacks on PMTU monitoring can have
similar effects.

Beyond that, if an update to RFC 2473 is desired, this GRE-scoped draft
seems like a poor vehicle for that purpose (e.g., as RFC 2784 does not
cite RFC 2473); I think a separate draft would be more appropriate.

Thanks,
--David

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Wednesday, April 01, 2015 12:12 PM
> To: Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> Hi David,
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Wednesday, April 01, 2015 8:43 AM
> > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org=
;
> Black, David
> > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> >
> > Fred,
> >
> > > No, that's is not right. GMTU < 1280 is not necessarily an indication
> > > that something is wrong, as explained in Section 7 of RFC2473. The
> > > same considerations apply here.
> >
> > I agree with the text quoted above,
>=20
> OK, then this document should cite Section 7 of RFC2473 normatively.
>=20
> > but what I'm observing is that there
> > are networks for which GMTU is an indication that something is wrong
> > (this is a consequence of operator decisions that are specific to such
> > a network).  The alternative configuration is intended for such network=
s,
> > but is not intended for all networks, and would need to be qualified
> > with words making it applicable primarily or only (or suggest some
> > other words) to such networks.
>=20
> If there is operational assurance that all links in the tunnel path confi=
gure
> a sufficiently large MTU, and there will never be a nesting of tunnels th=
at
> would result in a too-small MTU, then tunnel fragmentation would not
> need to be invoked and there is no need to talk about sending PTBs with
> GMTU less than 1280. Or, if you did want to include text that would tell
> what to do in the case of misconfigurations, then this document would
> need to update RFC2473 since the same considerations apply to generic
> encapsulation over IPv6 and not just GRE encapsulation over IPv6.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> > Upshot: the use of "necessarily" in the text quoted above is correct, b=
ut
> > misses the point.
> >
> > Thanks,
> > --David
> >
> > > -----Original Message-----
> > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > Sent: Wednesday, April 01, 2015 10:13 AM
> > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg
> > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> configuration
> > >
> > > Hi David,
> > >
> > > > -----Original Message-----
> > > > From: Black, David [mailto:david.black@emc.com]
> > > > Sent: Tuesday, March 31, 2015 7:06 PM
> > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf=
.org;
> > > Black, David
> > > > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> > > >
> > > > So, I talked to Ron off-list and it looks like something is missing=
 from
> > > > this discussion.
> > > >
> > > > The "alternative configuration" is not motivated by a desire to all=
ow
> > > > implementation flexibility or bless broken implementations.  It's
> motivated
> > > > by consideration of networks with operational practices wherein a G=
MTU
> of
> > > > less than 1280 octets is evidence that something is seriously wrong=
.
> That
> > > > something might be misconfiguration (quoting RFC 5706, "Anything th=
at
> > > > can be configured can be misconfigured."), or an attack on the GRE
> > > > ingress's PMTU estimation.
> > > >
> > > > So, in the situation of interest (GMTU < 1280) something is wrong, =
and
> > > > the operator may be faced with a Hobson's choice: either blackhole =
the
> > > > traffic that can no longer be sent without fragmentation, or fragme=
nt a
> > > > lot of traffic, causing problems at the GRE egress by overwhelming =
its
> > > > reassembly code - there may be good operational and/or security rea=
sons
> > > > to not want to do the latter.  All of this ought to be explained in=
 the
> > > > draft.
> > >
> > > No, that's is not right. GMTU < 1280 is not necessarily an indication
> > > that something is wrong, as explained in Section 7 of RFC2473. The
> > > same considerations apply here.
> > >
> > > Thanks - Fred
> > > fred.l.templin@boeing.com
> > >
> > > > Thanks,
> > > > --David
> > > >
> > > > > -----Original Message-----
> > > > > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of
> Templin,
> > > Fred L
> > > > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> chairs@ietf.org
> > > > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-gre-=
ipv6
> > > > >
> > > > > Hi Ron,
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-ipv6@tools.ietf=
.org;
> > > > > intarea-chairs@ietf.org
> > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-gr=
e-
> ipv6
> > > > > >
> > > > > > Fred,
> > > > > >
> > > > > > It appears that we disagree and have taken to repeating ourselv=
es.
> > > > >
> > > > > This is not a disagreement; this is a case in which the text is
> actually
> > > > > broken
> > > > > which you have more or less acknowledged. You can fix the text in
> question
> > > > > as follows:
> > > > >
> > > > > OLD:
> > > > > ****
> > > > >    In its default configuration, the GRE ingress router MUST:
> > > > >
> > > > >    o  encapsulate the entire IPv6 packet in a single GRE header a=
nd IP
> > > > >       delivery header
> > > > >
> > > > >    o  fragment the delivery header, so that it can be reassembled=
 by
> the
> > > > >       GRE egress
> > > > >
> > > > >    However, in an alternative configuration, the GRE ingress MAY:
> > > > >
> > > > >    o  discard the IPv6 packet
> > > > >
> > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to th=
e
> IPv6
> > > > >       packet source.  The MTU field in the ICMPv6 PTB message is =
set
> to
> > > > >       the GMTU.
> > > > >
> > > > > NEW:
> > > > > ****
> > > > >    The GRE ingress router MUST:
> > > > >
> > > > >    o  if the IPv6 payload packet includes a fragment header, frag=
ment
> the
> > > > >        payload packet into fragments no larger than the GMTU and
> > > encapsulate
> > > > >       each fragment in a single GRE header and IP delivery header=
.
> > > Otherwise:
> > > > >
> > > > >       o encapsulate the entire IPv6 packet in a single GRE header=
 and
> IP
> > > > >           delivery header
> > > > >
> > > > >       o fragment the delivery packet, so that it can be reassembl=
ed by
> the
> > > > >           GRE egress
> > > > >
> > > > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message to =
the
> IPv6
> > > > >          packet source, subject to rate limiting.  The MTU field =
in
> the
> > > ICMPv6
> > > > > PTB
> > > > >         message is set to the GMTU.
> > > > >
> > > > > > So, why don't we solicit opinions from the rest of the WG and d=
efer
> to
> > > their
> > > > > will.
> > > > >
> > > > > We can't do that for broken text. Ram-rodding broken text through=
 the
> > > > > process based on popular opinion does not make it good.
> > > > >
> > > > > Thanks - Fred
> > > > > fred.l.templin@boeing.com
> > > > >
> > > > > >
> > > > > >                                                         Ron
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> ipv6@tools.ietf.org;
> > > > > intarea-
> > > > > > > chairs@ietf.org
> > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intarea-=
gre-
> ipv6
> > > > > > >
> > > > > > > Hi Ron,
> > > > > > >
> > > > > > > I will say again that the minimum IPv6 link MTU is 1280 bytes=
 and
> so
> > > the
> > > > > > > design must account for tunnel paths that include links with =
such
> a
> > > small
> > > > > > > MTU. The design must also account for nested tunnels-within-
> tunnels,
> > > > > > > where the MTU seen by the first tunnel ingress may be reduced=
 by
> > > > > > > potentially many layers of additional encapsulation.
> > > > > > >
> > > > > > > But again, the point is that the tunnel ingress cannot
> legitimately
> > > send
> > > > > PTBs
> > > > > > > that report a size smaller than 1280 *and* perpetually drop
> packets
> > > > > smaller
> > > > > > > than 1280 which is exactly the behavior your text is permitti=
ng.
> > > > > > >
> > > > > > > Thanks - Fred
> > > > > > > fred.l.templin@boeing.com
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> ipv6@tools.ietf.org;
> > > > > > > > intarea-chairs@ietf.org
> > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intare=
a-
> gre-
> > > ipv6
> > > > > > > >
> > > > > > > > Fred,
> > > > > > > >
> > > > > > > > In the last network that I operated, all interior links had=
 MTU
> > > > > > > > greater than 9k. If I configured a GRE tunnel between two p=
oints
> in
> > > that
> > > > > > > network and detected a GMTU less than 1280, it would have
> indicated
> > > one of
> > > > > > > the following:
> > > > > > > >
> > > > > > > > - Phenomenal brokenness
> > > > > > > > - An ICMP PTB-based attack in progress
> > > > > > > >
> > > > > > > > In such cases, operators need some flexibility in how their
> networks
> > > > > > > > would behave. Why deny them this flexibility by taking away=
 the
> > > > > > > configuration option?
> > > > > > > >
> > > > > > > > Isn't it an operator's prerogative to discard any packet th=
at
> might
> > > > > degrade
> > > > > > > network performance?
> > > > > > > >
> > > > > > > >
> > > > > > > > Ron
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > ipv6@tools.ietf.org;
> > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > >
> > > > > > > > > Hi Ron,
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > >
> > > > > > > > > > Fred,
> > > > > > > > > >
> > > > > > > > > > Some (if not most) operators maintain networks in which=
 all
> > > links
> > > > > > > > > > have MTU greater than or equal to 1500. In those networ=
ks,
> the
> > > > > > > > > > very detection of a GMTU smaller than 1280 indicates
> brokenness.
> > > > > > > > > > Those
> > > > > > > > > operators, the alternative behavior may be preferable to =
the
> > > default.
> > > > > > > > >
> > > > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how much the =
link
> must
> > > > > > > > > deliver no matter what. A GMTU smaller than 1280 does not
> indicate
> > > > > > > > > brokennesss; it can naturally happen if 1) there is a lin=
k
> with a
> > > > > > > > > small MTU in the path, or
> > > > > > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > > > > > >
> > > > > > > > > As such, sustained dropping of packets less than 1280 is =
a no-
> no,
> > > > > > > > > and cannot be specified in a document like this.
> > > > > > > > >
> > > > > > > > > Thanks - Fred
> > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Ron
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.c=
om]
> > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > >
> > > > > > > > > > > Hi Ron,
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Fred,
> > > > > > > > > > > >
> > > > > > > > > > > >      Inline.....
> > > > > > > > > > > >
> > > > > > > > > > > >                Ron
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > > > >
> > > > > > > > > > > > >    ?However, in an alternative configuration, the=
 GRE
> > > ingress
> > > > > MAY:
> > > > > > > > > > > > >
> > > > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > > > >
> > > > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC444=
3]
> > > message
> > > > > > > > > > > > > to the
> > > > > > > > > IPv6
> > > > > > > > > > > > >       packet source.  The MTU field in the ICMPv6=
 PTB
> > > message
> > > > > is set
> > > > > > > to
> > > > > > > > > > > > >       the GMTU.?
> > > > > > > > > > > > >
> > > > > > > > > > > > > This means that there may be circumstances when t=
he
> GRE
> > > > > > > > > > > > > ingress sends a PTB reporting a size less than 12=
80.
> > > > > > > > > > > > > According to RFC2460, Section 5, the standard beh=
avior
> for
> > > a
> > > > > > > > > > > > > host that receives
> > > > > > > > > such a PTB is:
> > > > > > > > > > > > >
> > > > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > > > >   is not required to reduce the size of subsequen=
t
> packets
> > > to
> > > > > less
> > > > > > > than
> > > > > > > > > > > > >    1280, but must include a Fragment header in th=
ose
> > > packets?
> > > > > > > > > > > > >
> > > > > > > > > > > > > So, hosts that obey RFC2460 Section 5 will see a
> perpetual
> > > > > > > > > > > > > black hole if the GMTU is smaller than 1280 which=
 is
> > > > > > > > > > > > > probably not what we
> > > > > > > > > > > want.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > [RPB]
> > > > > > > > > > > > All true. This is why the WG decided to make this t=
he
> > > > > > > > > > > > alternative behavior
> > > > > > > > > > > and not the default behavior.
> > > > > > > > > > >
> > > > > > > > > > > Behavior that is broken is still broken regardless of
> whether
> > > it
> > > > > > > > > > > is alternative or default.
> > > > > > > > > > >
> > > > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to provid=
e
> > > guidance
> > > > > > > > > > > > > to hosts on how to react to PTB messages that rep=
ort a
> > > small
> > > > > size.
> > > > > > > > > > > > > But, as of right now,
> > > > > > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > > > > > [RPB]
> > > > > > > > > > > >
> > > > > > > > > > > > Absolutely correct. The procedures described in Sec=
tion
> 5 or
> > > > > > > > > > > > RFC
> > > > > > > > > > > > 246 are
> > > > > > > > > > > normative.
> > > > > > > > > > > >
> > > > > > > > > > > > I don't how this impacts the WG's LC decision regar=
ding
> the
> > > > > > > > > > > > current
> > > > > > > > > draft.
> > > > > > > > > > >
> > > > > > > > > > > Broken behavior should not be specified, whether
> alternative
> > > or
> > > > > > > default.
> > > > > > > > > > >
> > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Ron
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Int-area mailing list
> > > > > Int-area@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 16:17:41 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF74B1ACC81; Wed,  1 Apr 2015 16:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-JSLN-R0qOn; Wed,  1 Apr 2015 16:17:33 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18D121ACC7F; Wed,  1 Apr 2015 16:17:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t31NHW74009537; Wed, 1 Apr 2015 16:17:32 -0700
Received: from XCH-BLV-302.nw.nos.boeing.com (xch-blv-302.nw.nos.boeing.com [130.247.25.214]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t31NHTIr009064 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 1 Apr 2015 16:17:29 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-BLV-302.nw.nos.boeing.com ([169.254.2.195]) with mapi id 14.03.0210.002; Wed, 1 Apr 2015 16:17:28 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYgAALjyCAAAhGi8AAB9x+Q
Date: Wed, 1 Apr 2015 23:17:27 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E30214@XCH-BLV-504.nw.nos.boeing.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-3ec1uMUdpuST_7JXgQna3Ro0x4>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:17:39 -0000

Hi David,

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Wednesday, April 01, 2015 4:08 PM
> To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> > > I think it would be better to directly explain the GRE situation here=
, and
> > > add an informative citation of RFC 2473 as providing additional expla=
nation,
> > > particularly for situations in which different operational practices =
are
> > > used.
> >
> > How is the GRE situation any different than for any generic encapsulati=
on
> > in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific us=
e
> > cases"?
>=20
> Yes, specifically networks where a GMTU < 1280 always indicates a problem=
.

OK, for specific use cases then, i.e., the same as for any generic
IPv6 encapsulation in specific use cases and not only for GRE.

> > Section 7 of RFC2473 already provides guidance that applies also
> > to GRE in any use case.
>=20
> Ok, as previously noted - the text here is specific to GRE and certain
> networks.

Specific to certain networks, perhaps, but not specific to GRE.

> > > Beyond that, if an update to RFC 2473 is desired, this GRE-scoped dra=
ft
> > > seems like a poor vehicle for that purpose (e.g., as RFC 2784 does no=
t
> > > cite RFC 2473); I think a separate draft would be more appropriate.
> >
> > OK, then have this draft simply cite RFC2473, Section 7 normatively
> > and break the exception cases out into a separate document like
> > intarea-tunnels. The exception cases are not limited to GRE in
> > particular, and apply also to any generic tunneling in IPv6.
>=20
> Right now, the exception case is proposed as GRE-only, and hence is
> appropriate for this draft.  I hesitate to generalize it to all IPv6
> tunnels or have the GRE provisions await that being done.

This is where we differ - there is nothing in this recommendation
that is specific to GRE - the recommendation applies to any generic
IPv6 encapsulation and is appropriate to only those use cases where
shutting down the tunnel altogether is preferable to allowing the
tunnel to fragment. This is a generic IPv6 encapsulation consideration;
not a GRE consideration.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > Sent: Wednesday, April 01, 2015 5:34 PM
> > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> >
> > Hi David,
> >
> > > -----Original Message-----
> > > From: Black, David [mailto:david.black@emc.com]
> > > Sent: Wednesday, April 01, 2015 1:26 PM
> > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg;
> > Black, David
> > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative config=
uration
> > >
> > > Fred,
> > >
> > > > > > No, that's is not right. GMTU < 1280 is not necessarily an indi=
cation
> > > > > > that something is wrong, as explained in Section 7 of RFC2473. =
The
> > > > > > same considerations apply here.
> > > > >
> > > > > I agree with the text quoted above,
> > >
> > > Adding the rest of the sentence ...
> > >
> > > > > but what I'm observing is that there
> > > > > are networks for which GMTU is an indication that something is wr=
ong
> > > > > (this is a consequence of operator decisions that are specific to=
 such
> > > > > a network).
> > >
> > > > OK, then this document should cite Section 7 of RFC2473 normatively=
.
> > >
> > > I think it would be better to directly explain the GRE situation here=
, and
> > > add an informative citation of RFC 2473 as providing additional expla=
nation,
> > > particularly for situations in which different operational practices =
are
> > used.
> >
> > How is the GRE situation any different than for any generic encapsulati=
on
> > in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific us=
e
> > cases"? Section 7 of RFC2473 already provides guidance that applies als=
o
> > to GRE in any use case.
> >
> > > > If there is operational assurance that all links in the tunnel path
> > configure
> > > > a sufficiently large MTU, and there will never be a nesting of tunn=
els
> > that
> > > > would result in a too-small MTU, then tunnel fragmentation would no=
t
> > > > need to be invoked and there is no need to talk about sending PTBs =
with
> > > > GMTU less than 1280.
> > >
> > > Never say "never" ... quoting RFC 5706, "Anything that can be configu=
red can
> > > be misconfigured." ;-).
> >
> > Right, that's what I said (having used that phrase many times in
> > the past myself).
> >
> > > I'll leave the rationale for sending PTBs to Ron, but keep in mind th=
at
> > > "running code" (i.e., existing implementations) is(are) an important
> > > consideration - see the second sentence in the Introduction.
> >
> > Sending PTB with MTU<1280 is supposed to have an effect as described
> > in Section 5 of RFC. Namely, the original source is supposed to start
> > including IPv6 fragment headers in subsequent packets and the network
> > is supposed to find some way to get them through. What Ron's text
> > is suggesting is that the original source lives up to its part of the b=
argain
> > but then the network dumps the packets into a black hole.
> >
> > > > Or, if you did want to include text that would tell
> > > > what to do in the case of misconfigurations, then this document wou=
ld
> > > > need to update RFC2473 since the same considerations apply to gener=
ic
> > > > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> > >
> > > It's more than misconfigurations - attacks on PMTU monitoring can hav=
e
> > > similar effects.
> >
> > If you want to start talking about PTB forgery, then we should also tal=
k
> > about  PTB filtering and how the mechanisms work when PTBs are lost.
> > RFC2473 itself is imperfect in that regard, and this draft is not propo=
sing
> > anything different than RFC2473.
> >
> > > Beyond that, if an update to RFC 2473 is desired, this GRE-scoped dra=
ft
> > > seems like a poor vehicle for that purpose (e.g., as RFC 2784 does no=
t
> > > cite RFC 2473); I think a separate draft would be more appropriate.
> >
> > OK, then have this draft simply cite RFC2473, Section 7 normatively
> > and break the exception cases out into a separate document like
> > intarea-tunnels. The exception cases are not limited to GRE in
> > particular, and apply also to any generic tunneling in IPv6.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >
> > > Thanks,
> > > --David
> > >
> > > > -----Original Message-----
> > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > Sent: Wednesday, April 01, 2015 12:12 PM
> > > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf=
.org
> > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > configuration
> > > >
> > > > Hi David,
> > > >
> > > > > -----Original Message-----
> > > > > From: Black, David [mailto:david.black@emc.com]
> > > > > Sent: Wednesday, April 01, 2015 8:43 AM
> > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ie=
tf.org;
> > > > Black, David
> > > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > configuration
> > > > >
> > > > > Fred,
> > > > >
> > > > > > No, that's is not right. GMTU < 1280 is not necessarily an indi=
cation
> > > > > > that something is wrong, as explained in Section 7 of RFC2473. =
The
> > > > > > same considerations apply here.
> > > > >
> > > > > I agree with the text quoted above,
> > > >
> > > > OK, then this document should cite Section 7 of RFC2473 normatively=
.
> > > >
> > > > > but what I'm observing is that there
> > > > > are networks for which GMTU is an indication that something is wr=
ong
> > > > > (this is a consequence of operator decisions that are specific to=
 such
> > > > > a network).  The alternative configuration is intended for such
> > networks,
> > > > > but is not intended for all networks, and would need to be qualif=
ied
> > > > > with words making it applicable primarily or only (or suggest som=
e
> > > > > other words) to such networks.
> > > >
> > > > If there is operational assurance that all links in the tunnel path
> > configure
> > > > a sufficiently large MTU, and there will never be a nesting of tunn=
els
> > that
> > > > would result in a too-small MTU, then tunnel fragmentation would no=
t
> > > > need to be invoked and there is no need to talk about sending PTBs =
with
> > > > GMTU less than 1280. Or, if you did want to include text that would=
 tell
> > > > what to do in the case of misconfigurations, then this document wou=
ld
> > > > need to update RFC2473 since the same considerations apply to gener=
ic
> > > > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> > > >
> > > > Thanks - Fred
> > > > fred.l.templin@boeing.com
> > > >
> > > > > Upshot: the use of "necessarily" in the text quoted above is corr=
ect,
> > but
> > > > > misses the point.
> > > > >
> > > > > Thanks,
> > > > > --David
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > Sent: Wednesday, April 01, 2015 10:13 AM
> > > > > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > chairs@ietf.org
> > > > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > > > configuration
> > > > > >
> > > > > > Hi David,
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Black, David [mailto:david.black@emc.com]
> > > > > > > Sent: Tuesday, March 31, 2015 7:06 PM
> > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > chairs@ietf.org;
> > > > > > Black, David
> > > > > > > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > configuration
> > > > > > >
> > > > > > > So, I talked to Ron off-list and it looks like something is m=
issing
> > from
> > > > > > > this discussion.
> > > > > > >
> > > > > > > The "alternative configuration" is not motivated by a desire =
to
> > allow
> > > > > > > implementation flexibility or bless broken implementations.  =
It's
> > > > motivated
> > > > > > > by consideration of networks with operational practices where=
in a
> > GMTU
> > > > of
> > > > > > > less than 1280 octets is evidence that something is seriously=
 wrong.
> > > > That
> > > > > > > something might be misconfiguration (quoting RFC 5706, "Anyth=
ing
> > that
> > > > > > > can be configured can be misconfigured."), or an attack on th=
e GRE
> > > > > > > ingress's PMTU estimation.
> > > > > > >
> > > > > > > So, in the situation of interest (GMTU < 1280) something is w=
rong,
> > and
> > > > > > > the operator may be faced with a Hobson's choice: either blac=
khole
> > the
> > > > > > > traffic that can no longer be sent without fragmentation, or
> > fragment a
> > > > > > > lot of traffic, causing problems at the GRE egress by overwhe=
lming
> > its
> > > > > > > reassembly code - there may be good operational and/or securi=
ty
> > reasons
> > > > > > > to not want to do the latter.  All of this ought to be explai=
ned in
> > the
> > > > > > > draft.
> > > > > >
> > > > > > No, that's is not right. GMTU < 1280 is not necessarily an indi=
cation
> > > > > > that something is wrong, as explained in Section 7 of RFC2473. =
The
> > > > > > same considerations apply here.
> > > > > >
> > > > > > Thanks - Fred
> > > > > > fred.l.templin@boeing.com
> > > > > >
> > > > > > > Thanks,
> > > > > > > --David
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf=
 Of
> > > > Templin,
> > > > > > Fred L
> > > > > > > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > > > chairs@ietf.org
> > > > > > > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intare=
a-gre-
> > ipv6
> > > > > > > >
> > > > > > > > Hi Ron,
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > ipv6@tools.ietf.org;
> > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-inta=
rea-
> > gre-
> > > > ipv6
> > > > > > > > >
> > > > > > > > > Fred,
> > > > > > > > >
> > > > > > > > > It appears that we disagree and have taken to repeating
> > ourselves.
> > > > > > > >
> > > > > > > > This is not a disagreement; this is a case in which the tex=
t is
> > > > actually
> > > > > > > > broken
> > > > > > > > which you have more or less acknowledged. You can fix the t=
ext in
> > > > question
> > > > > > > > as follows:
> > > > > > > >
> > > > > > > > OLD:
> > > > > > > > ****
> > > > > > > >    In its default configuration, the GRE ingress router MUS=
T:
> > > > > > > >
> > > > > > > >    o  encapsulate the entire IPv6 packet in a single GRE he=
ader
> > and IP
> > > > > > > >       delivery header
> > > > > > > >
> > > > > > > >    o  fragment the delivery header, so that it can be reass=
embled
> > by
> > > > the
> > > > > > > >       GRE egress
> > > > > > > >
> > > > > > > >    However, in an alternative configuration, the GRE ingres=
s MAY:
> > > > > > > >
> > > > > > > >    o  discard the IPv6 packet
> > > > > > > >
> > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message=
 to the
> > > > IPv6
> > > > > > > >       packet source.  The MTU field in the ICMPv6 PTB messa=
ge is
> > set
> > > > to
> > > > > > > >       the GMTU.
> > > > > > > >
> > > > > > > > NEW:
> > > > > > > > ****
> > > > > > > >    The GRE ingress router MUST:
> > > > > > > >
> > > > > > > >    o  if the IPv6 payload packet includes a fragment header=
,
> > fragment
> > > > the
> > > > > > > >        payload packet into fragments no larger than the GMT=
U and
> > > > > > encapsulate
> > > > > > > >       each fragment in a single GRE header and IP delivery =
header.
> > > > > > Otherwise:
> > > > > > > >
> > > > > > > >       o encapsulate the entire IPv6 packet in a single GRE =
header
> > and
> > > > IP
> > > > > > > >           delivery header
> > > > > > > >
> > > > > > > >       o fragment the delivery packet, so that it can be
> > reassembled by
> > > > the
> > > > > > > >           GRE egress
> > > > > > > >
> > > > > > > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] messa=
ge to
> > the
> > > > IPv6
> > > > > > > >          packet source, subject to rate limiting.  The MTU =
field
> > in
> > > > the
> > > > > > ICMPv6
> > > > > > > > PTB
> > > > > > > >         message is set to the GMTU.
> > > > > > > >
> > > > > > > > > So, why don't we solicit opinions from the rest of the WG=
 and
> > defer
> > > > to
> > > > > > their
> > > > > > > > will.
> > > > > > > >
> > > > > > > > We can't do that for broken text. Ram-rodding broken text t=
hrough
> > the
> > > > > > > > process based on popular opinion does not make it good.
> > > > > > > >
> > > > > > > > Thanks - Fred
> > > > > > > > fred.l.templin@boeing.com
> > > > > > > >
> > > > > > > > >
> > > > > > > > >                                                         R=
on
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com=
]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > ipv6@tools.ietf.org;
> > > > > > > > intarea-
> > > > > > > > > > chairs@ietf.org
> > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-in=
tarea-
> > gre-
> > > > ipv6
> > > > > > > > > >
> > > > > > > > > > Hi Ron,
> > > > > > > > > >
> > > > > > > > > > I will say again that the minimum IPv6 link MTU is 1280=
 bytes
> > and
> > > > so
> > > > > > the
> > > > > > > > > > design must account for tunnel paths that include links=
 with
> > such
> > > > a
> > > > > > small
> > > > > > > > > > MTU. The design must also account for nested tunnels-wi=
thin-
> > > > tunnels,
> > > > > > > > > > where the MTU seen by the first tunnel ingress may be r=
educed
> > by
> > > > > > > > > > potentially many layers of additional encapsulation.
> > > > > > > > > >
> > > > > > > > > > But again, the point is that the tunnel ingress cannot
> > > > legitimately
> > > > > > send
> > > > > > > > PTBs
> > > > > > > > > > that report a size smaller than 1280 *and* perpetually =
drop
> > > > packets
> > > > > > > > smaller
> > > > > > > > > > than 1280 which is exactly the behavior your text is
> > permitting.
> > > > > > > > > >
> > > > > > > > > > Thanks - Fred
> > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > ipv6@tools.ietf.org;
> > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-
> > intarea-
> > > > gre-
> > > > > > ipv6
> > > > > > > > > > >
> > > > > > > > > > > Fred,
> > > > > > > > > > >
> > > > > > > > > > > In the last network that I operated, all interior lin=
ks had
> > MTU
> > > > > > > > > > > greater than 9k. If I configured a GRE tunnel between=
 two
> > points
> > > > in
> > > > > > that
> > > > > > > > > > network and detected a GMTU less than 1280, it would ha=
ve
> > > > indicated
> > > > > > one of
> > > > > > > > > > the following:
> > > > > > > > > > >
> > > > > > > > > > > - Phenomenal brokenness
> > > > > > > > > > > - An ICMP PTB-based attack in progress
> > > > > > > > > > >
> > > > > > > > > > > In such cases, operators need some flexibility in how=
 their
> > > > networks
> > > > > > > > > > > would behave. Why deny them this flexibility by takin=
g away
> > the
> > > > > > > > > > configuration option?
> > > > > > > > > > >
> > > > > > > > > > > Isn't it an operator's prerogative to discard any pac=
ket
> > that
> > > > might
> > > > > > > > degrade
> > > > > > > > > > network performance?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Ron
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing=
.com]
> > > > > > > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > > > ipv6@tools.ietf.org;
> > > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Ron,
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf=
.org
> > > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > >
> > > > > > > > > > > > > Fred,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Some (if not most) operators maintain networks in=
 which
> > all
> > > > > > links
> > > > > > > > > > > > > have MTU greater than or equal to 1500. In those
> > networks,
> > > > the
> > > > > > > > > > > > > very detection of a GMTU smaller than 1280 indica=
tes
> > > > brokenness.
> > > > > > > > > > > > > Those
> > > > > > > > > > > > operators, the alternative behavior may be preferab=
le to
> > the
> > > > > > default.
> > > > > > > > > > > >
> > > > > > > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how muc=
h the
> > link
> > > > must
> > > > > > > > > > > > deliver no matter what. A GMTU smaller than 1280 do=
es not
> > > > indicate
> > > > > > > > > > > > brokennesss; it can naturally happen if 1) there is=
 a link
> > > > with a
> > > > > > > > > > > > small MTU in the path, or
> > > > > > > > > > > > 2) there are multiple tunnel nesting levels, or bot=
h.
> > > > > > > > > > > >
> > > > > > > > > > > > As such, sustained dropping of packets less than 12=
80 is a
> > no-
> > > > no,
> > > > > > > > > > > > and cannot be specified in a document like this.
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Ron
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > From: Templin, Fred L
> > [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf=
.org
> > > > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Ron,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.n=
et]
> > > > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Fred,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >      Inline.....
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >                Ron
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >    ?However, in an alternative configuratio=
n, the
> > GRE
> > > > > > ingress
> > > > > > > > MAY:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB)
> > [RFC4443]
> > > > > > message
> > > > > > > > > > > > > > > > to the
> > > > > > > > > > > > IPv6
> > > > > > > > > > > > > > > >       packet source.  The MTU field in the =
ICMPv6
> > PTB
> > > > > > message
> > > > > > > > is set
> > > > > > > > > > to
> > > > > > > > > > > > > > > >       the GMTU.?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > This means that there may be circumstances =
when
> > the
> > > > GRE
> > > > > > > > > > > > > > > > ingress sends a PTB reporting a size less t=
han
> > 1280.
> > > > > > > > > > > > > > > > According to RFC2460, Section 5, the standa=
rd
> > behavior
> > > > for
> > > > > > a
> > > > > > > > > > > > > > > > host that receives
> > > > > > > > > > > > such a PTB is:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > > > > > > >   is not required to reduce the size of sub=
sequent
> > > > packets
> > > > > > to
> > > > > > > > less
> > > > > > > > > > than
> > > > > > > > > > > > > > > >    1280, but must include a Fragment header=
 in
> > those
> > > > > > packets?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > So, hosts that obey RFC2460 Section 5 will =
see a
> > > > perpetual
> > > > > > > > > > > > > > > > black hole if the GMTU is smaller than 1280=
 which
> > is
> > > > > > > > > > > > > > > > probably not what we
> > > > > > > > > > > > > > want.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > > > All true. This is why the WG decided to make =
this
> > the
> > > > > > > > > > > > > > > alternative behavior
> > > > > > > > > > > > > > and not the default behavior.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Behavior that is broken is still broken regardl=
ess of
> > > > whether
> > > > > > it
> > > > > > > > > > > > > > is alternative or default.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to =
provide
> > > > > > guidance
> > > > > > > > > > > > > > > > to hosts on how to react to PTB messages th=
at
> > report a
> > > > > > small
> > > > > > > > size.
> > > > > > > > > > > > > > > > But, as of right now,
> > > > > > > > > > > > > > > > RFC2460 Section 5 is the normative behavior=
.
> > > > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Absolutely correct. The procedures described =
in
> > Section
> > > > 5 or
> > > > > > > > > > > > > > > RFC
> > > > > > > > > > > > > > > 246 are
> > > > > > > > > > > > > > normative.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I don't how this impacts the WG's LC decision
> > regarding
> > > > the
> > > > > > > > > > > > > > > current
> > > > > > > > > > > > draft.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Broken behavior should not be specified, whethe=
r
> > > > alternative
> > > > > > or
> > > > > > > > > > default.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Ron
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Int-area mailing list
> > > > > > > > Int-area@ietf.org
> > > > > > > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 16:23:42 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A391A90DB for <ipv6@ietfa.amsl.com>; Wed,  1 Apr 2015 16:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 lOC-9qVI1ctm for <ipv6@ietfa.amsl.com>; Wed,  1 Apr 2015 16:23:33 -0700 (PDT)
Received: from nm32-vm6.bullet.mail.bf1.yahoo.com (nm32-vm6.bullet.mail.bf1.yahoo.com [72.30.239.142]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A0CE1A1B73 for <ipv6@ietf.org>; Wed,  1 Apr 2015 16:23:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1427930612; bh=erWHGBb3tSVLKklP8yaK6UV4ORAYBWX6puz47/jiJGw=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=INS6Apac2n5PPaGeVkXMJmuuAjTLo0Ch/oQtUipETQSpLrpq/+GZRl03fD6WljfUaLHANrx9Syd1o/nvcGRRisMHOrO+eAJP24JvaWXOzquptCZtxokIGWYWvgAhQjXCDmy9CDTOKScagrDEUpiYyhAIwtGKRXnNGEjPX2ppDsTXqMiUoNH1tYEsXjjAIhxtcedkVzYcMhmm5VFQaQ2kde3CLVW1wR4kNXVOp0IFZyYD43mB8e/CkBlPAg3KQtrBo+ucjx2Wvzs/S0qEPoSPIb4tBoT/Mq6PnY/jb+/s4lm5ioJffb4Tcxilz+pAnY7u0TLIRamgeKJQtEbvs8LGRg==
Received: from [66.196.81.174] by nm32.bullet.mail.bf1.yahoo.com with NNFMP; 01 Apr 2015 23:23:32 -0000
Received: from [98.139.215.229] by tm20.bullet.mail.bf1.yahoo.com with NNFMP;  01 Apr 2015 23:23:32 -0000
Received: from [127.0.0.1] by omp1069.mail.bf1.yahoo.com with NNFMP; 01 Apr 2015 23:23:32 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 233665.70363.bm@omp1069.mail.bf1.yahoo.com
X-YMail-OSG: XuJu6qIVM1mN_5Rc8kZE0xiTtUBkjBbpnEjhPuISuPcg4MOSiHhlLgpHYjR5lDQ j6QApXtRBp13nTsRjEcX0Htv4GkkvM0IB1gaTeLUFp1N3cdD_j_BFpdACO0MX2h9fmc8OMEIgeoE z_Gbxexap2Od1jvLjwDDZX7qvu3a_xJ5r..AOuhBzwrHa5fHgfoAGJVtVeJtDGw5kURIog84.ujA O0Sr_Fk0UEOsTPz1tycGriUyM1wVjUAYgtCRiwOfqT2WPD1LZ1MIopHHYfbC1iIZI5Htl39uCHDj 48ZGU9Dfm.aZ6YB19Rk3vJIgNMxQef8hSxeAzyrBs0TwTV.Z3akDFNl.DQQoRKq5D32UEsAvyHlq 8yxJUIOSfYPkESA.bhXR0jYsXCP3w_u8x03HjhCI9CJ.AtHEVVmcN3fiVxSmV6rCXw.ZtOmhalU8 NBYih6l9i.FDXm_71BDdOanzqTvT7qm_Ck.Hv68xgctraANVwQopo_Il5WfAILZkp_XsPokAJDRQ 6Yjn98Gi.YwcErWU4QU38f.RU5cXa0g.A9hM413CP
Received: by 76.13.27.55; Wed, 01 Apr 2015 23:23:31 +0000 
Date: Wed, 1 Apr 2015 23:23:30 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>
Message-ID: <1678786622.4013980.1427930610519.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAC8QAccQ6hmEpOE5KB=L361nt41V1JcwfFn9o7=Y1sS7yw0aMA@mail.gmail.com>
References: <CAC8QAccQ6hmEpOE5KB=L361nt41V1JcwfFn9o7=Y1sS7yw0aMA@mail.gmail.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/giTGoXnWvpCdcTvlBwojM-0jF-0>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:23:35 -0000

Hi Behcet,


----- Original Message -----
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Cc: "STARK, BARBARA H" <bs7652@att.com>; Hemant Singh (shemant) <shemant@cisco.com>; "ipv6@ietf.org" <ipv6@ietf.org>
Sent: Thursday, 2 April 2015, 6:21
Subject: Re: RA Option Guidelines

I don't understand why DHCPv6 is being discussed under RA Option Guidelines?
If DHCPv6 is being used instead of RA, like in Australia, that
supports our position that we should also define DHCPv6 options for
SADR.

/ DHCPv6 isn't being used instead of RAs in Australia.

/ I think the fundamental problem is people are considering RAs and DHCPv6 to be functional equivalents (like e.g., OSPF vs IS-IS), and therefore thinking that DHCPv6 options should be imported into RAs and vice versa.

/ There are critical operational limitations that RAs have that DHCPv6 doesn't (because the RA mechanisms are much simpler), and by trying to use RAs for the same purpose as DHCPv6, all the problems already solved for DHCPv6 would have to be solved again for RAs. The desired simplicity of using RAs only would disappear because the complexity of replicating DHCPv6 mechanisms, and the additional significant operational overheads of constant firmware upgrades to routers to add RA options.

Regards,

Mark.



Regards,
Behcet


On Tue, Mar 31, 2015 at 9:33 PM, Mark ZZZ Smith
<markzzzsmith@yahoo.com.au> wrote:
> Hi Barbara,
>
> ________________________________
> From: "STARK, BARBARA H" <bs7652@att.com>
> To: Hemant Singh (shemant) <shemant@cisco.com>; Mark ZZZ Smith
> <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@innovationslab.net>;
> "ipv6@ietf.org" <ipv6@ietf.org>
> Sent: Wednesday, 1 April 2015, 0:24
> Subject: RE: RA Option Guidelines
>
>
>
>> The problem that Mark  raised and also provided a solution for is to add
>> DHCPv6 relay functionality to the CE router.  He is also correct that RFC
>> 6204
>> does not include DHCPv6 relay agent functionality in the CE router.
>>
>> The other choice for a solution is to include the DHCPv6 options in the
>> RA.
>> For this solution to work the SP will send new DHCPv6 options in the RA to
>> the CE router WAN.  The RA terminates at the CE WAN.  The CE generates a
>> new RA for the LAN.  RFC 6204 does not include functionality to bridge the
>> SP
>> RA received on the CE WAN to the CE LAN.  So even for the RA solution to
>> work, a new requirement would need to be added to RFC 6204.  Did I miss
>> anything in the RA solution I described above?  If not, either way, one
>> adds a
>> new requirement to the CE router and if it's DHCPv6 options, let DHCPv6
>> protocol deal with it.
>
>
> RFC 7084 already says:
>   L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>           options (as listed in Section 5.3 of [RFC3736]) received from
>           the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>           server.
> Where the RFC3736 list of options is for DNS Recursive Name Servers, DNS
> search list, and SIP Servers.
>
> My personal, as-a-consumer, freaking-out-about-privacy opinion is that the
> idea of my ISPs (both of them, but potentially 3) sending any configuration
> options they feel like down to my personal and private LAN host devices is
> not to my liking. I realize that some people are blithely happy to turn over
> their privacy to ISPs. So maybe relay of all unrecognized options could be
> something an ISP puts into CE routers they supply to their customers. I
> prefer for it not to be in the retail ones I purchase, and I would be
> adamant about it not being on by default in such retail CE routers. So let
> such relay requirements go into eRouter or BBF specs, but please keep them
> out of IETF and homenet specs.
>
> / I think you're already trusting your ISP possibly much more than you might
> realise. They're already supplying you with the Internet addressing you use,
> you're probably using their DNS resolvers, you may be using their email
> servers, and of course they can tap your clear text traffic without you
> knowing.
>
> / Even if you only used their addressing and encrypted all of your traffic
> over a tunnel through their infrastructure, you'd still then be trusting the
> remote tunnel endpoint provider, likely to be another party other than
> yourself.
>
> Since I'm in the process of setting up my new homenet router (Pierre flashed
> my new router for me last week) to connect upstream to both my ISPs (one
> cable provider and one telco), I also really don't want dueling relayed
> options reaching my LAN hosts. I do think that in the future a significant
> number of people will choose to subscribe to multiple providers -- as long
> as it's easy to do. The ISPs get to configure the CE router WAN interfaces
> to work with their access networks -- and that needs to be the extent of
> their reach unless I specifically give them conscious permission to do more.
> If they want to configure devices inside my LAN, I think they should use a
> higher layer configuration protocol with mandatory and default-on security
> (which neither RA nor DHCPv6 have).
>
> / So I think the world is moving in the other direction. People have been
> outsourcing the maintenance of their devices in droves as they adopt
> smartphones and tablets, and more recently with devices like Google's
> Chromebooks. They're giving up control rather than desiring more of it, for
> the gains of more convenience and lower costs.
>
> / Regards,
> Mark.
>
>
> Barbara
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Wed Apr  1 23:42:49 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C65991AC82C; Wed,  1 Apr 2015 16:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lVOE6dwkvFKt; Wed,  1 Apr 2015 16:07:57 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 F08C41AC446; Wed,  1 Apr 2015 16:07:56 -0700 (PDT)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31N7pxD024301 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Apr 2015 19:07:52 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t31N7pxD024301
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427929673; bh=dSWDbqyX2IKLrpOrJyvmqlz/4Gk=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ZwF4/dW5Yzy2rdVC1QMdcEjcSapRtGjrw4jb+vIsYADPpra5ngcQ/Sl3WtBTUHQMK M6I4k24WUSZRFeoVJwVYLeUHM7rhXvw9C3EUiT4KRAqFXLC5yOdnf8qOsgENKe05P0 8R/i/18O2fWSEqYfY/CekxRPvnT71ZDasIeh2LBc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t31N7pxD024301
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd06.lss.emc.com (RSA Interceptor); Wed, 1 Apr 2015 19:07:43 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31N7ivf003683 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 19:07:45 -0400
Received: from MXHUB210.corp.emc.com (10.253.68.36) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 1 Apr 2015 19:07:43 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB210.corp.emc.com ([10.253.68.36]) with mapi id 14.03.0224.002; Wed, 1 Apr 2015 19:07:44 -0400
From: "Black, David" <david.black@emc.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYgAALjyCAAAhGi8A==
Date: Wed, 1 Apr 2015 23:07:43 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SUXQ7BL-cdRt8Eq6QHybH-KmAKs>
X-Mailman-Approved-At: Wed, 01 Apr 2015 23:42:44 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:08:03 -0000

> > I think it would be better to directly explain the GRE situation here, =
and
> > add an informative citation of RFC 2473 as providing additional explana=
tion,
> > particularly for situations in which different operational practices ar=
e
> > used.
>
> How is the GRE situation any different than for any generic encapsulation
> in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific use
> cases"?

Yes, specifically networks where a GMTU < 1280 always indicates a problem.

> Section 7 of RFC2473 already provides guidance that applies also
> to GRE in any use case.

Ok, as previously noted - the text here is specific to GRE and certain
networks.

> > Beyond that, if an update to RFC 2473 is desired, this GRE-scoped draft
> > seems like a poor vehicle for that purpose (e.g., as RFC 2784 does not
> > cite RFC 2473); I think a separate draft would be more appropriate.
>
> OK, then have this draft simply cite RFC2473, Section 7 normatively
> and break the exception cases out into a separate document like
> intarea-tunnels. The exception cases are not limited to GRE in
> particular, and apply also to any generic tunneling in IPv6.

Right now, the exception case is proposed as GRE-only, and hence is
appropriate for this draft.  I hesitate to generalize it to all IPv6
tunnels or have the GRE provisions await that being done.

Thanks,
--David

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Wednesday, April 01, 2015 5:34 PM
> To: Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> Hi David,
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Wednesday, April 01, 2015 1:26 PM
> > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org=
;
> Black, David
> > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> >
> > Fred,
> >
> > > > > No, that's is not right. GMTU < 1280 is not necessarily an indica=
tion
> > > > > that something is wrong, as explained in Section 7 of RFC2473. Th=
e
> > > > > same considerations apply here.
> > > >
> > > > I agree with the text quoted above,
> >
> > Adding the rest of the sentence ...
> >
> > > > but what I'm observing is that there
> > > > are networks for which GMTU is an indication that something is wron=
g
> > > > (this is a consequence of operator decisions that are specific to s=
uch
> > > > a network).
> >
> > > OK, then this document should cite Section 7 of RFC2473 normatively.
> >
> > I think it would be better to directly explain the GRE situation here, =
and
> > add an informative citation of RFC 2473 as providing additional explana=
tion,
> > particularly for situations in which different operational practices ar=
e
> used.
>=20
> How is the GRE situation any different than for any generic encapsulation
> in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific use
> cases"? Section 7 of RFC2473 already provides guidance that applies also
> to GRE in any use case.
>=20
> > > If there is operational assurance that all links in the tunnel path
> configure
> > > a sufficiently large MTU, and there will never be a nesting of tunnel=
s
> that
> > > would result in a too-small MTU, then tunnel fragmentation would not
> > > need to be invoked and there is no need to talk about sending PTBs wi=
th
> > > GMTU less than 1280.
> >
> > Never say "never" ... quoting RFC 5706, "Anything that can be configure=
d can
> > be misconfigured." ;-).
>=20
> Right, that's what I said (having used that phrase many times in
> the past myself).
>=20
> > I'll leave the rationale for sending PTBs to Ron, but keep in mind that
> > "running code" (i.e., existing implementations) is(are) an important
> > consideration - see the second sentence in the Introduction.
>=20
> Sending PTB with MTU<1280 is supposed to have an effect as described
> in Section 5 of RFC. Namely, the original source is supposed to start
> including IPv6 fragment headers in subsequent packets and the network
> is supposed to find some way to get them through. What Ron's text
> is suggesting is that the original source lives up to its part of the bar=
gain
> but then the network dumps the packets into a black hole.
>=20
> > > Or, if you did want to include text that would tell
> > > what to do in the case of misconfigurations, then this document would
> > > need to update RFC2473 since the same considerations apply to generic
> > > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> >
> > It's more than misconfigurations - attacks on PMTU monitoring can have
> > similar effects.
>=20
> If you want to start talking about PTB forgery, then we should also talk
> about  PTB filtering and how the mechanisms work when PTBs are lost.
> RFC2473 itself is imperfect in that regard, and this draft is not proposi=
ng
> anything different than RFC2473.
>=20
> > Beyond that, if an update to RFC 2473 is desired, this GRE-scoped draft
> > seems like a poor vehicle for that purpose (e.g., as RFC 2784 does not
> > cite RFC 2473); I think a separate draft would be more appropriate.
>=20
> OK, then have this draft simply cite RFC2473, Section 7 normatively
> and break the exception cases out into a separate document like
> intarea-tunnels. The exception cases are not limited to GRE in
> particular, and apply also to any generic tunneling in IPv6.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
>=20
> > Thanks,
> > --David
> >
> > > -----Original Message-----
> > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > Sent: Wednesday, April 01, 2015 12:12 PM
> > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg
> > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> configuration
> > >
> > > Hi David,
> > >
> > > > -----Original Message-----
> > > > From: Black, David [mailto:david.black@emc.com]
> > > > Sent: Wednesday, April 01, 2015 8:43 AM
> > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf=
.org;
> > > Black, David
> > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> configuration
> > > >
> > > > Fred,
> > > >
> > > > > No, that's is not right. GMTU < 1280 is not necessarily an indica=
tion
> > > > > that something is wrong, as explained in Section 7 of RFC2473. Th=
e
> > > > > same considerations apply here.
> > > >
> > > > I agree with the text quoted above,
> > >
> > > OK, then this document should cite Section 7 of RFC2473 normatively.
> > >
> > > > but what I'm observing is that there
> > > > are networks for which GMTU is an indication that something is wron=
g
> > > > (this is a consequence of operator decisions that are specific to s=
uch
> > > > a network).  The alternative configuration is intended for such
> networks,
> > > > but is not intended for all networks, and would need to be qualifie=
d
> > > > with words making it applicable primarily or only (or suggest some
> > > > other words) to such networks.
> > >
> > > If there is operational assurance that all links in the tunnel path
> configure
> > > a sufficiently large MTU, and there will never be a nesting of tunnel=
s
> that
> > > would result in a too-small MTU, then tunnel fragmentation would not
> > > need to be invoked and there is no need to talk about sending PTBs wi=
th
> > > GMTU less than 1280. Or, if you did want to include text that would t=
ell
> > > what to do in the case of misconfigurations, then this document would
> > > need to update RFC2473 since the same considerations apply to generic
> > > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> > >
> > > Thanks - Fred
> > > fred.l.templin@boeing.com
> > >
> > > > Upshot: the use of "necessarily" in the text quoted above is correc=
t,
> but
> > > > misses the point.
> > > >
> > > > Thanks,
> > > > --David
> > > >
> > > > > -----Original Message-----
> > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > Sent: Wednesday, April 01, 2015 10:13 AM
> > > > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> chairs@ietf.org
> > > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > > configuration
> > > > >
> > > > > Hi David,
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Black, David [mailto:david.black@emc.com]
> > > > > > Sent: Tuesday, March 31, 2015 7:06 PM
> > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> chairs@ietf.org;
> > > > > Black, David
> > > > > > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> configuration
> > > > > >
> > > > > > So, I talked to Ron off-list and it looks like something is mis=
sing
> from
> > > > > > this discussion.
> > > > > >
> > > > > > The "alternative configuration" is not motivated by a desire to
> allow
> > > > > > implementation flexibility or bless broken implementations.  It=
's
> > > motivated
> > > > > > by consideration of networks with operational practices wherein=
 a
> GMTU
> > > of
> > > > > > less than 1280 octets is evidence that something is seriously w=
rong.
> > > That
> > > > > > something might be misconfiguration (quoting RFC 5706, "Anythin=
g
> that
> > > > > > can be configured can be misconfigured."), or an attack on the =
GRE
> > > > > > ingress's PMTU estimation.
> > > > > >
> > > > > > So, in the situation of interest (GMTU < 1280) something is wro=
ng,
> and
> > > > > > the operator may be faced with a Hobson's choice: either blackh=
ole
> the
> > > > > > traffic that can no longer be sent without fragmentation, or
> fragment a
> > > > > > lot of traffic, causing problems at the GRE egress by overwhelm=
ing
> its
> > > > > > reassembly code - there may be good operational and/or security
> reasons
> > > > > > to not want to do the latter.  All of this ought to be explaine=
d in
> the
> > > > > > draft.
> > > > >
> > > > > No, that's is not right. GMTU < 1280 is not necessarily an indica=
tion
> > > > > that something is wrong, as explained in Section 7 of RFC2473. Th=
e
> > > > > same considerations apply here.
> > > > >
> > > > > Thanks - Fred
> > > > > fred.l.templin@boeing.com
> > > > >
> > > > > > Thanks,
> > > > > > --David
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf O=
f
> > > Templin,
> > > > > Fred L
> > > > > > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > > chairs@ietf.org
> > > > > > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-intarea-=
gre-
> ipv6
> > > > > > >
> > > > > > > Hi Ron,
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> ipv6@tools.ietf.org;
> > > > > > > intarea-chairs@ietf.org
> > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-intare=
a-
> gre-
> > > ipv6
> > > > > > > >
> > > > > > > > Fred,
> > > > > > > >
> > > > > > > > It appears that we disagree and have taken to repeating
> ourselves.
> > > > > > >
> > > > > > > This is not a disagreement; this is a case in which the text =
is
> > > actually
> > > > > > > broken
> > > > > > > which you have more or less acknowledged. You can fix the tex=
t in
> > > question
> > > > > > > as follows:
> > > > > > >
> > > > > > > OLD:
> > > > > > > ****
> > > > > > >    In its default configuration, the GRE ingress router MUST:
> > > > > > >
> > > > > > >    o  encapsulate the entire IPv6 packet in a single GRE head=
er
> and IP
> > > > > > >       delivery header
> > > > > > >
> > > > > > >    o  fragment the delivery header, so that it can be reassem=
bled
> by
> > > the
> > > > > > >       GRE egress
> > > > > > >
> > > > > > >    However, in an alternative configuration, the GRE ingress =
MAY:
> > > > > > >
> > > > > > >    o  discard the IPv6 packet
> > > > > > >
> > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message t=
o the
> > > IPv6
> > > > > > >       packet source.  The MTU field in the ICMPv6 PTB message=
 is
> set
> > > to
> > > > > > >       the GMTU.
> > > > > > >
> > > > > > > NEW:
> > > > > > > ****
> > > > > > >    The GRE ingress router MUST:
> > > > > > >
> > > > > > >    o  if the IPv6 payload packet includes a fragment header,
> fragment
> > > the
> > > > > > >        payload packet into fragments no larger than the GMTU =
and
> > > > > encapsulate
> > > > > > >       each fragment in a single GRE header and IP delivery he=
ader.
> > > > > Otherwise:
> > > > > > >
> > > > > > >       o encapsulate the entire IPv6 packet in a single GRE he=
ader
> and
> > > IP
> > > > > > >           delivery header
> > > > > > >
> > > > > > >       o fragment the delivery packet, so that it can be
> reassembled by
> > > the
> > > > > > >           GRE egress
> > > > > > >
> > > > > > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] message=
 to
> the
> > > IPv6
> > > > > > >          packet source, subject to rate limiting.  The MTU fi=
eld
> in
> > > the
> > > > > ICMPv6
> > > > > > > PTB
> > > > > > >         message is set to the GMTU.
> > > > > > >
> > > > > > > > So, why don't we solicit opinions from the rest of the WG a=
nd
> defer
> > > to
> > > > > their
> > > > > > > will.
> > > > > > >
> > > > > > > We can't do that for broken text. Ram-rodding broken text thr=
ough
> the
> > > > > > > process based on popular opinion does not make it good.
> > > > > > >
> > > > > > > Thanks - Fred
> > > > > > > fred.l.templin@boeing.com
> > > > > > >
> > > > > > > >
> > > > > > > >                                                         Ron
> > > > > > > >
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > ipv6@tools.ietf.org;
> > > > > > > intarea-
> > > > > > > > > chairs@ietf.org
> > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-inta=
rea-
> gre-
> > > ipv6
> > > > > > > > >
> > > > > > > > > Hi Ron,
> > > > > > > > >
> > > > > > > > > I will say again that the minimum IPv6 link MTU is 1280 b=
ytes
> and
> > > so
> > > > > the
> > > > > > > > > design must account for tunnel paths that include links w=
ith
> such
> > > a
> > > > > small
> > > > > > > > > MTU. The design must also account for nested tunnels-with=
in-
> > > tunnels,
> > > > > > > > > where the MTU seen by the first tunnel ingress may be red=
uced
> by
> > > > > > > > > potentially many layers of additional encapsulation.
> > > > > > > > >
> > > > > > > > > But again, the point is that the tunnel ingress cannot
> > > legitimately
> > > > > send
> > > > > > > PTBs
> > > > > > > > > that report a size smaller than 1280 *and* perpetually dr=
op
> > > packets
> > > > > > > smaller
> > > > > > > > > than 1280 which is exactly the behavior your text is
> permitting.
> > > > > > > > >
> > > > > > > > > Thanks - Fred
> > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > ipv6@tools.ietf.org;
> > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-
> intarea-
> > > gre-
> > > > > ipv6
> > > > > > > > > >
> > > > > > > > > > Fred,
> > > > > > > > > >
> > > > > > > > > > In the last network that I operated, all interior links=
 had
> MTU
> > > > > > > > > > greater than 9k. If I configured a GRE tunnel between t=
wo
> points
> > > in
> > > > > that
> > > > > > > > > network and detected a GMTU less than 1280, it would have
> > > indicated
> > > > > one of
> > > > > > > > > the following:
> > > > > > > > > >
> > > > > > > > > > - Phenomenal brokenness
> > > > > > > > > > - An ICMP PTB-based attack in progress
> > > > > > > > > >
> > > > > > > > > > In such cases, operators need some flexibility in how t=
heir
> > > networks
> > > > > > > > > > would behave. Why deny them this flexibility by taking =
away
> the
> > > > > > > > > configuration option?
> > > > > > > > > >
> > > > > > > > > > Isn't it an operator's prerogative to discard any packe=
t
> that
> > > might
> > > > > > > degrade
> > > > > > > > > network performance?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Ron
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.c=
om]
> > > > > > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > > ipv6@tools.ietf.org;
> > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > >
> > > > > > > > > > > Hi Ron,
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.o=
rg
> > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > >
> > > > > > > > > > > > Fred,
> > > > > > > > > > > >
> > > > > > > > > > > > Some (if not most) operators maintain networks in w=
hich
> all
> > > > > links
> > > > > > > > > > > > have MTU greater than or equal to 1500. In those
> networks,
> > > the
> > > > > > > > > > > > very detection of a GMTU smaller than 1280 indicate=
s
> > > brokenness.
> > > > > > > > > > > > Those
> > > > > > > > > > > operators, the alternative behavior may be preferable=
 to
> the
> > > > > default.
> > > > > > > > > > >
> > > > > > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how much =
the
> link
> > > must
> > > > > > > > > > > deliver no matter what. A GMTU smaller than 1280 does=
 not
> > > indicate
> > > > > > > > > > > brokennesss; it can naturally happen if 1) there is a=
 link
> > > with a
> > > > > > > > > > > small MTU in the path, or
> > > > > > > > > > > 2) there are multiple tunnel nesting levels, or both.
> > > > > > > > > > >
> > > > > > > > > > > As such, sustained dropping of packets less than 1280=
 is a
> no-
> > > no,
> > > > > > > > > > > and cannot be specified in a document like this.
> > > > > > > > > > >
> > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Ron
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Templin, Fred L
> [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.o=
rg
> > > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Ron,
> > > > > > > > > > > > >
> > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net=
]
> > > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi Fred,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >      Inline.....
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >                Ron
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >    ?However, in an alternative configuration,=
 the
> GRE
> > > > > ingress
> > > > > > > MAY:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB)
> [RFC4443]
> > > > > message
> > > > > > > > > > > > > > > to the
> > > > > > > > > > > IPv6
> > > > > > > > > > > > > > >       packet source.  The MTU field in the IC=
MPv6
> PTB
> > > > > message
> > > > > > > is set
> > > > > > > > > to
> > > > > > > > > > > > > > >       the GMTU.?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > This means that there may be circumstances wh=
en
> the
> > > GRE
> > > > > > > > > > > > > > > ingress sends a PTB reporting a size less tha=
n
> 1280.
> > > > > > > > > > > > > > > According to RFC2460, Section 5, the standard
> behavior
> > > for
> > > > > a
> > > > > > > > > > > > > > > host that receives
> > > > > > > > > > > such a PTB is:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > > > > > >   is not required to reduce the size of subse=
quent
> > > packets
> > > > > to
> > > > > > > less
> > > > > > > > > than
> > > > > > > > > > > > > > >    1280, but must include a Fragment header i=
n
> those
> > > > > packets?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > So, hosts that obey RFC2460 Section 5 will se=
e a
> > > perpetual
> > > > > > > > > > > > > > > black hole if the GMTU is smaller than 1280 w=
hich
> is
> > > > > > > > > > > > > > > probably not what we
> > > > > > > > > > > > > want.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > > All true. This is why the WG decided to make th=
is
> the
> > > > > > > > > > > > > > alternative behavior
> > > > > > > > > > > > > and not the default behavior.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Behavior that is broken is still broken regardles=
s of
> > > whether
> > > > > it
> > > > > > > > > > > > > is alternative or default.
> > > > > > > > > > > > >
> > > > > > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts to pr=
ovide
> > > > > guidance
> > > > > > > > > > > > > > > to hosts on how to react to PTB messages that
> report a
> > > > > small
> > > > > > > size.
> > > > > > > > > > > > > > > But, as of right now,
> > > > > > > > > > > > > > > RFC2460 Section 5 is the normative behavior.
> > > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Absolutely correct. The procedures described in
> Section
> > > 5 or
> > > > > > > > > > > > > > RFC
> > > > > > > > > > > > > > 246 are
> > > > > > > > > > > > > normative.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I don't how this impacts the WG's LC decision
> regarding
> > > the
> > > > > > > > > > > > > > current
> > > > > > > > > > > draft.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Broken behavior should not be specified, whether
> > > alternative
> > > > > or
> > > > > > > > > default.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ron
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Int-area mailing list
> > > > > > > Int-area@ietf.org
> > > > > > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Wed Apr  1 23:42:50 2015
Return-Path: <david.black@emc.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B23DA1A90A1; Wed,  1 Apr 2015 16:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IH4Q-WXeVloR; Wed,  1 Apr 2015 16:27:12 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (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 6E0F21AC3C6; Wed,  1 Apr 2015 16:27:10 -0700 (PDT)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31NR5Fw004993 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Apr 2015 19:27:06 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com t31NR5Fw004993
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1427930826; bh=dk48oiin5lFW+YDk6xH2Mn+fkAI=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ccsbXK84Ehu+bI/fbOZ4+WgBEfaJE7liDvcxdYPFb0CBLH71GcpyCybZkU1eCgD4c y4dBxsacHcpxConhb+TXTbJL/Zt1ybkBPJ2PcirdDfybig0CwH5FWtq5tP8sjG9GlI 5mS24pEJeU67iSZEM4Y1/We0qgfQpRYGxqHOsRPs=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com t31NR5Fw004993
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd52.lss.emc.com (RSA Interceptor); Wed, 1 Apr 2015 19:27:00 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t31NQh2S003646 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 19:26:43 -0400
Received: from MXHUB201.corp.emc.com (10.253.68.27) by mxhub33.corp.emc.com (10.254.93.81) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 1 Apr 2015 19:26:42 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB201.corp.emc.com ([10.253.68.27]) with mapi id 14.03.0224.002; Wed, 1 Apr 2015 19:26:43 -0400
From: "Black, David" <david.black@emc.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYgAALjyCAAAhGi8AAB9x+QAACAahA=
Date: Wed, 1 Apr 2015 23:26:42 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936432C22@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E30214@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E30214@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/st0exs46mIpvZmu_YQNd3va3r_o>
X-Mailman-Approved-At: Wed, 01 Apr 2015 23:42:44 -0700
Cc: "Black, David" <david.black@emc.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:27:17 -0000

One more inline ...

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Wednesday, April 01, 2015 7:17 PM
> To: Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configurat=
ion
>=20
> Hi David,
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Wednesday, April 01, 2015 4:08 PM
> > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configur=
ation
> >
> > > > I think it would be better to directly explain the GRE situation he=
re,
> and
> > > > add an informative citation of RFC 2473 as providing additional
> explanation,
> > > > particularly for situations in which different operational practice=
s are
> > > > used.
> > >
> > > How is the GRE situation any different than for any generic encapsula=
tion
> > > in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific =
use
> > > cases"?
> >
> > Yes, specifically networks where a GMTU < 1280 always indicates a probl=
em.
>=20
> OK, for specific use cases then, i.e., the same as for any generic
> IPv6 encapsulation in specific use cases and not only for GRE.
>=20
> > > Section 7 of RFC2473 already provides guidance that applies also
> > > to GRE in any use case.
> >
> > Ok, as previously noted - the text here is specific to GRE and certain
> > networks.
>=20
> Specific to certain networks, perhaps, but not specific to GRE.
>=20
> > > > Beyond that, if an update to RFC 2473 is desired, this GRE-scoped d=
raft
> > > > seems like a poor vehicle for that purpose (e.g., as RFC 2784 does =
not
> > > > cite RFC 2473); I think a separate draft would be more appropriate.
> > >
> > > OK, then have this draft simply cite RFC2473, Section 7 normatively
> > > and break the exception cases out into a separate document like
> > > intarea-tunnels. The exception cases are not limited to GRE in
> > > particular, and apply also to any generic tunneling in IPv6.
> >
> > Right now, the exception case is proposed as GRE-only, and hence is
> > appropriate for this draft.  I hesitate to generalize it to all IPv6
> > tunnels or have the GRE provisions await that being done.
>=20
> This is where we differ - there is nothing in this recommendation
> that is specific to GRE - the recommendation applies to any generic
> IPv6 encapsulation and is appropriate to only those use cases where
> shutting down the tunnel altogether is preferable to allowing the
> tunnel to fragment. This is a generic IPv6 encapsulation consideration;
> not a GRE consideration.

The "running code" involved here is GRE.  I am concerned that we lack
the foundation to update 2473 for all encapsulated protocols.

>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> > Thanks,
> > --David
> >
> > > -----Original Message-----
> > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > Sent: Wednesday, April 01, 2015 5:34 PM
> > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.o=
rg
> > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> configuration
> > >
> > > Hi David,
> > >
> > > > -----Original Message-----
> > > > From: Black, David [mailto:david.black@emc.com]
> > > > Sent: Wednesday, April 01, 2015 1:26 PM
> > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf=
.org;
> > > Black, David
> > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> configuration
> > > >
> > > > Fred,
> > > >
> > > > > > > No, that's is not right. GMTU < 1280 is not necessarily an
> indication
> > > > > > > that something is wrong, as explained in Section 7 of RFC2473=
. The
> > > > > > > same considerations apply here.
> > > > > >
> > > > > > I agree with the text quoted above,
> > > >
> > > > Adding the rest of the sentence ...
> > > >
> > > > > > but what I'm observing is that there
> > > > > > are networks for which GMTU is an indication that something is =
wrong
> > > > > > (this is a consequence of operator decisions that are specific =
to
> such
> > > > > > a network).
> > > >
> > > > > OK, then this document should cite Section 7 of RFC2473 normative=
ly.
> > > >
> > > > I think it would be better to directly explain the GRE situation he=
re,
> and
> > > > add an informative citation of RFC 2473 as providing additional
> explanation,
> > > > particularly for situations in which different operational practice=
s are
> > > used.
> > >
> > > How is the GRE situation any different than for any generic encapsula=
tion
> > > in IPv6 situation (RFC2473)? Are you meaning to say "GRE in specific =
use
> > > cases"? Section 7 of RFC2473 already provides guidance that applies a=
lso
> > > to GRE in any use case.
> > >
> > > > > If there is operational assurance that all links in the tunnel pa=
th
> > > configure
> > > > > a sufficiently large MTU, and there will never be a nesting of tu=
nnels
> > > that
> > > > > would result in a too-small MTU, then tunnel fragmentation would =
not
> > > > > need to be invoked and there is no need to talk about sending PTB=
s
> with
> > > > > GMTU less than 1280.
> > > >
> > > > Never say "never" ... quoting RFC 5706, "Anything that can be confi=
gured
> can
> > > > be misconfigured." ;-).
> > >
> > > Right, that's what I said (having used that phrase many times in
> > > the past myself).
> > >
> > > > I'll leave the rationale for sending PTBs to Ron, but keep in mind =
that
> > > > "running code" (i.e., existing implementations) is(are) an importan=
t
> > > > consideration - see the second sentence in the Introduction.
> > >
> > > Sending PTB with MTU<1280 is supposed to have an effect as described
> > > in Section 5 of RFC. Namely, the original source is supposed to start
> > > including IPv6 fragment headers in subsequent packets and the network
> > > is supposed to find some way to get them through. What Ron's text
> > > is suggesting is that the original source lives up to its part of the
> bargain
> > > but then the network dumps the packets into a black hole.
> > >
> > > > > Or, if you did want to include text that would tell
> > > > > what to do in the case of misconfigurations, then this document w=
ould
> > > > > need to update RFC2473 since the same considerations apply to gen=
eric
> > > > > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> > > >
> > > > It's more than misconfigurations - attacks on PMTU monitoring can h=
ave
> > > > similar effects.
> > >
> > > If you want to start talking about PTB forgery, then we should also t=
alk
> > > about  PTB filtering and how the mechanisms work when PTBs are lost.
> > > RFC2473 itself is imperfect in that regard, and this draft is not
> proposing
> > > anything different than RFC2473.
> > >
> > > > Beyond that, if an update to RFC 2473 is desired, this GRE-scoped d=
raft
> > > > seems like a poor vehicle for that purpose (e.g., as RFC 2784 does =
not
> > > > cite RFC 2473); I think a separate draft would be more appropriate.
> > >
> > > OK, then have this draft simply cite RFC2473, Section 7 normatively
> > > and break the exception cases out into a separate document like
> > > intarea-tunnels. The exception cases are not limited to GRE in
> > > particular, and apply also to any generic tunneling in IPv6.
> > >
> > > Thanks - Fred
> > > fred.l.templin@boeing.com
> > >
> > >
> > > > Thanks,
> > > > --David
> > > >
> > > > > -----Original Message-----
> > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > Sent: Wednesday, April 01, 2015 12:12 PM
> > > > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> chairs@ietf.org
> > > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > > configuration
> > > > >
> > > > > Hi David,
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Black, David [mailto:david.black@emc.com]
> > > > > > Sent: Wednesday, April 01, 2015 8:43 AM
> > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> chairs@ietf.org;
> > > > > Black, David
> > > > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > > configuration
> > > > > >
> > > > > > Fred,
> > > > > >
> > > > > > > No, that's is not right. GMTU < 1280 is not necessarily an
> indication
> > > > > > > that something is wrong, as explained in Section 7 of RFC2473=
. The
> > > > > > > same considerations apply here.
> > > > > >
> > > > > > I agree with the text quoted above,
> > > > >
> > > > > OK, then this document should cite Section 7 of RFC2473 normative=
ly.
> > > > >
> > > > > > but what I'm observing is that there
> > > > > > are networks for which GMTU is an indication that something is =
wrong
> > > > > > (this is a consequence of operator decisions that are specific =
to
> such
> > > > > > a network).  The alternative configuration is intended for such
> > > networks,
> > > > > > but is not intended for all networks, and would need to be qual=
ified
> > > > > > with words making it applicable primarily or only (or suggest s=
ome
> > > > > > other words) to such networks.
> > > > >
> > > > > If there is operational assurance that all links in the tunnel pa=
th
> > > configure
> > > > > a sufficiently large MTU, and there will never be a nesting of tu=
nnels
> > > that
> > > > > would result in a too-small MTU, then tunnel fragmentation would =
not
> > > > > need to be invoked and there is no need to talk about sending PTB=
s
> with
> > > > > GMTU less than 1280. Or, if you did want to include text that wou=
ld
> tell
> > > > > what to do in the case of misconfigurations, then this document w=
ould
> > > > > need to update RFC2473 since the same considerations apply to gen=
eric
> > > > > encapsulation over IPv6 and not just GRE encapsulation over IPv6.
> > > > >
> > > > > Thanks - Fred
> > > > > fred.l.templin@boeing.com
> > > > >
> > > > > > Upshot: the use of "necessarily" in the text quoted above is
> correct,
> > > but
> > > > > > misses the point.
> > > > > >
> > > > > > Thanks,
> > > > > > --David
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> > > > > > > Sent: Wednesday, April 01, 2015 10:13 AM
> > > > > > > To: Black, David; int-area@ietf.org; ipv6@ietf.org
> > > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > > chairs@ietf.org
> > > > > > > Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternativ=
e
> > > > > configuration
> > > > > > >
> > > > > > > Hi David,
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Black, David [mailto:david.black@emc.com]
> > > > > > > > Sent: Tuesday, March 31, 2015 7:06 PM
> > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > > chairs@ietf.org;
> > > > > > > Black, David
> > > > > > > > Subject: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative
> > > configuration
> > > > > > > >
> > > > > > > > So, I talked to Ron off-list and it looks like something is
> missing
> > > from
> > > > > > > > this discussion.
> > > > > > > >
> > > > > > > > The "alternative configuration" is not motivated by a desir=
e to
> > > allow
> > > > > > > > implementation flexibility or bless broken implementations.
> It's
> > > > > motivated
> > > > > > > > by consideration of networks with operational practices whe=
rein
> a
> > > GMTU
> > > > > of
> > > > > > > > less than 1280 octets is evidence that something is serious=
ly
> wrong.
> > > > > That
> > > > > > > > something might be misconfiguration (quoting RFC 5706, "Any=
thing
> > > that
> > > > > > > > can be configured can be misconfigured."), or an attack on =
the
> GRE
> > > > > > > > ingress's PMTU estimation.
> > > > > > > >
> > > > > > > > So, in the situation of interest (GMTU < 1280) something is
> wrong,
> > > and
> > > > > > > > the operator may be faced with a Hobson's choice: either
> blackhole
> > > the
> > > > > > > > traffic that can no longer be sent without fragmentation, o=
r
> > > fragment a
> > > > > > > > lot of traffic, causing problems at the GRE egress by
> overwhelming
> > > its
> > > > > > > > reassembly code - there may be good operational and/or secu=
rity
> > > reasons
> > > > > > > > to not want to do the latter.  All of this ought to be expl=
ained
> in
> > > the
> > > > > > > > draft.
> > > > > > >
> > > > > > > No, that's is not right. GMTU < 1280 is not necessarily an
> indication
> > > > > > > that something is wrong, as explained in Section 7 of RFC2473=
. The
> > > > > > > same considerations apply here.
> > > > > > >
> > > > > > > Thanks - Fred
> > > > > > > fred.l.templin@boeing.com
> > > > > > >
> > > > > > > > Thanks,
> > > > > > > > --David
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Int-area [mailto:int-area-bounces@ietf.org] On Beha=
lf Of
> > > > > Templin,
> > > > > > > Fred L
> > > > > > > > > Sent: Tuesday, March 31, 2015 6:39 PM
> > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-
> > > > > chairs@ietf.org
> > > > > > > > > Subject: Re: [Int-area] Start of WGLC for draft-ietf-inta=
rea-
> gre-
> > > ipv6
> > > > > > > > >
> > > > > > > > > Hi Ron,
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > Sent: Tuesday, March 31, 2015 3:12 PM
> > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > ipv6@tools.ietf.org;
> > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-
> intarea-
> > > gre-
> > > > > ipv6
> > > > > > > > > >
> > > > > > > > > > Fred,
> > > > > > > > > >
> > > > > > > > > > It appears that we disagree and have taken to repeating
> > > ourselves.
> > > > > > > > >
> > > > > > > > > This is not a disagreement; this is a case in which the t=
ext
> is
> > > > > actually
> > > > > > > > > broken
> > > > > > > > > which you have more or less acknowledged. You can fix the=
 text
> in
> > > > > question
> > > > > > > > > as follows:
> > > > > > > > >
> > > > > > > > > OLD:
> > > > > > > > > ****
> > > > > > > > >    In its default configuration, the GRE ingress router M=
UST:
> > > > > > > > >
> > > > > > > > >    o  encapsulate the entire IPv6 packet in a single GRE
> header
> > > and IP
> > > > > > > > >       delivery header
> > > > > > > > >
> > > > > > > > >    o  fragment the delivery header, so that it can be
> reassembled
> > > by
> > > > > the
> > > > > > > > >       GRE egress
> > > > > > > > >
> > > > > > > > >    However, in an alternative configuration, the GRE ingr=
ess
> MAY:
> > > > > > > > >
> > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > >
> > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] messa=
ge to
> the
> > > > > IPv6
> > > > > > > > >       packet source.  The MTU field in the ICMPv6 PTB mes=
sage
> is
> > > set
> > > > > to
> > > > > > > > >       the GMTU.
> > > > > > > > >
> > > > > > > > > NEW:
> > > > > > > > > ****
> > > > > > > > >    The GRE ingress router MUST:
> > > > > > > > >
> > > > > > > > >    o  if the IPv6 payload packet includes a fragment head=
er,
> > > fragment
> > > > > the
> > > > > > > > >        payload packet into fragments no larger than the G=
MTU
> and
> > > > > > > encapsulate
> > > > > > > > >       each fragment in a single GRE header and IP deliver=
y
> header.
> > > > > > > Otherwise:
> > > > > > > > >
> > > > > > > > >       o encapsulate the entire IPv6 packet in a single GR=
E
> header
> > > and
> > > > > IP
> > > > > > > > >           delivery header
> > > > > > > > >
> > > > > > > > >       o fragment the delivery packet, so that it can be
> > > reassembled by
> > > > > the
> > > > > > > > >           GRE egress
> > > > > > > > >
> > > > > > > > >      o  send an ICMPv6 Packet Too Big (PTB) [RFC4443] mes=
sage
> to
> > > the
> > > > > IPv6
> > > > > > > > >          packet source, subject to rate limiting.  The MT=
U
> field
> > > in
> > > > > the
> > > > > > > ICMPv6
> > > > > > > > > PTB
> > > > > > > > >         message is set to the GMTU.
> > > > > > > > >
> > > > > > > > > > So, why don't we solicit opinions from the rest of the =
WG
> and
> > > defer
> > > > > to
> > > > > > > their
> > > > > > > > > will.
> > > > > > > > >
> > > > > > > > > We can't do that for broken text. Ram-rodding broken text
> through
> > > the
> > > > > > > > > process based on popular opinion does not make it good.
> > > > > > > > >
> > > > > > > > > Thanks - Fred
> > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >                                                        =
 Ron
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.c=
om]
> > > > > > > > > > > Sent: Tuesday, March 31, 2015 4:38 PM
> > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > > ipv6@tools.ietf.org;
> > > > > > > > > intarea-
> > > > > > > > > > > chairs@ietf.org
> > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-ietf-
> intarea-
> > > gre-
> > > > > ipv6
> > > > > > > > > > >
> > > > > > > > > > > Hi Ron,
> > > > > > > > > > >
> > > > > > > > > > > I will say again that the minimum IPv6 link MTU is 12=
80
> bytes
> > > and
> > > > > so
> > > > > > > the
> > > > > > > > > > > design must account for tunnel paths that include lin=
ks
> with
> > > such
> > > > > a
> > > > > > > small
> > > > > > > > > > > MTU. The design must also account for nested tunnels-
> within-
> > > > > tunnels,
> > > > > > > > > > > where the MTU seen by the first tunnel ingress may be
> reduced
> > > by
> > > > > > > > > > > potentially many layers of additional encapsulation.
> > > > > > > > > > >
> > > > > > > > > > > But again, the point is that the tunnel ingress canno=
t
> > > > > legitimately
> > > > > > > send
> > > > > > > > > PTBs
> > > > > > > > > > > that report a size smaller than 1280 *and* perpetuall=
y
> drop
> > > > > packets
> > > > > > > > > smaller
> > > > > > > > > > > than 1280 which is exactly the behavior your text is
> > > permitting.
> > > > > > > > > > >
> > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net]
> > > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:21 PM
> > > > > > > > > > > > To: Templin, Fred L; int-area@ietf.org; ipv6@ietf.o=
rg
> > > > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > > ipv6@tools.ietf.org;
> > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for draft-iet=
f-
> > > intarea-
> > > > > gre-
> > > > > > > ipv6
> > > > > > > > > > > >
> > > > > > > > > > > > Fred,
> > > > > > > > > > > >
> > > > > > > > > > > > In the last network that I operated, all interior l=
inks
> had
> > > MTU
> > > > > > > > > > > > greater than 9k. If I configured a GRE tunnel betwe=
en
> two
> > > points
> > > > > in
> > > > > > > that
> > > > > > > > > > > network and detected a GMTU less than 1280, it would =
have
> > > > > indicated
> > > > > > > one of
> > > > > > > > > > > the following:
> > > > > > > > > > > >
> > > > > > > > > > > > - Phenomenal brokenness
> > > > > > > > > > > > - An ICMP PTB-based attack in progress
> > > > > > > > > > > >
> > > > > > > > > > > > In such cases, operators need some flexibility in h=
ow
> their
> > > > > networks
> > > > > > > > > > > > would behave. Why deny them this flexibility by tak=
ing
> away
> > > the
> > > > > > > > > > > configuration option?
> > > > > > > > > > > >
> > > > > > > > > > > > Isn't it an operator's prerogative to discard any p=
acket
> > > that
> > > > > might
> > > > > > > > > degrade
> > > > > > > > > > > network performance?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Ron
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Templin, Fred L
> [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 3:01 PM
> > > > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.o=
rg
> > > > > > > > > > > > > Cc: Zuniga, Juan Carlos; draft-ietf-intarea-gre-
> > > > > > > ipv6@tools.ietf.org;
> > > > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Ron,
> > > > > > > > > > > > >
> > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper.net=
]
> > > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 11:38 AM
> > > > > > > > > > > > > > To: Templin, Fred L; int-area@ietf.org;
> ipv6@ietf.org
> > > > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Fred,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Some (if not most) operators maintain networks =
in
> which
> > > all
> > > > > > > links
> > > > > > > > > > > > > > have MTU greater than or equal to 1500. In thos=
e
> > > networks,
> > > > > the
> > > > > > > > > > > > > > very detection of a GMTU smaller than 1280 indi=
cates
> > > > > brokenness.
> > > > > > > > > > > > > > Those
> > > > > > > > > > > > > operators, the alternative behavior may be prefer=
able
> to
> > > the
> > > > > > > default.
> > > > > > > > > > > > >
> > > > > > > > > > > > > The minimum IPv6 MTU is 1280 bytes; that is how m=
uch
> the
> > > link
> > > > > must
> > > > > > > > > > > > > deliver no matter what. A GMTU smaller than 1280 =
does
> not
> > > > > indicate
> > > > > > > > > > > > > brokennesss; it can naturally happen if 1) there =
is a
> link
> > > > > with a
> > > > > > > > > > > > > small MTU in the path, or
> > > > > > > > > > > > > 2) there are multiple tunnel nesting levels, or b=
oth.
> > > > > > > > > > > > >
> > > > > > > > > > > > > As such, sustained dropping of packets less than =
1280
> is a
> > > no-
> > > > > no,
> > > > > > > > > > > > > and cannot be specified in a document like this.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ron
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > From: Templin, Fred L
> > > [mailto:Fred.L.Templin@boeing.com]
> > > > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 1:30 PM
> > > > > > > > > > > > > > > To: Ronald Bonica; int-area@ietf.org;
> ipv6@ietf.org
> > > > > > > > > > > > > > > Cc: Zuniga, Juan Carlos;
> > > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > > > intarea- chairs@ietf.org
> > > > > > > > > > > > > > > Subject: RE: [Int-area] Start of WGLC for
> > > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Ron,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > > From: Ronald Bonica [mailto:rbonica@juniper=
.net]
> > > > > > > > > > > > > > > > Sent: Tuesday, March 31, 2015 10:18 AM
> > > > > > > > > > > > > > > > To: int-area@ietf.org; ipv6@ietf.org
> > > > > > > > > > > > > > > > Cc: Zuniga, Juan Carlos; Templin, Fred L;
> > > > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6@tools.ietf.org;
> > > > > > > > > > > > > > > > intarea-chairs@ietf.org
> > > > > > > > > > > > > > > > Subject: Re: [Int-area] Start of WGLC for
> > > > > > > > > > > > > > > > draft-ietf-intarea-gre-ipv6
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hi Fred,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >      Inline.....
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >                Ron
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hi Juan Carlos,
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Final passage of Section 3.1 says:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >    ?However, in an alternative configurat=
ion,
> the
> > > GRE
> > > > > > > ingress
> > > > > > > > > MAY:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >    o  discard the IPv6 packet
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >    o  send an ICMPv6 Packet Too Big (PTB)
> > > [RFC4443]
> > > > > > > message
> > > > > > > > > > > > > > > > > to the
> > > > > > > > > > > > > IPv6
> > > > > > > > > > > > > > > > >       packet source.  The MTU field in th=
e
> ICMPv6
> > > PTB
> > > > > > > message
> > > > > > > > > is set
> > > > > > > > > > > to
> > > > > > > > > > > > > > > > >       the GMTU.?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > This means that there may be circumstance=
s
> when
> > > the
> > > > > GRE
> > > > > > > > > > > > > > > > > ingress sends a PTB reporting a size less=
 than
> > > 1280.
> > > > > > > > > > > > > > > > > According to RFC2460, Section 5, the stan=
dard
> > > behavior
> > > > > for
> > > > > > > a
> > > > > > > > > > > > > > > > > host that receives
> > > > > > > > > > > > > such a PTB is:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >    ?In that case, the IPv6 node
> > > > > > > > > > > > > > > > >   is not required to reduce the size of
> subsequent
> > > > > packets
> > > > > > > to
> > > > > > > > > less
> > > > > > > > > > > than
> > > > > > > > > > > > > > > > >    1280, but must include a Fragment head=
er in
> > > those
> > > > > > > packets?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > So, hosts that obey RFC2460 Section 5 wil=
l see
> a
> > > > > perpetual
> > > > > > > > > > > > > > > > > black hole if the GMTU is smaller than 12=
80
> which
> > > is
> > > > > > > > > > > > > > > > > probably not what we
> > > > > > > > > > > > > > > want.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > > > > All true. This is why the WG decided to mak=
e
> this
> > > the
> > > > > > > > > > > > > > > > alternative behavior
> > > > > > > > > > > > > > > and not the default behavior.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Behavior that is broken is still broken regar=
dless
> of
> > > > > whether
> > > > > > > it
> > > > > > > > > > > > > > > is alternative or default.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > ?draft-templin-6man-linkadapt? attempts t=
o
> provide
> > > > > > > guidance
> > > > > > > > > > > > > > > > > to hosts on how to react to PTB messages =
that
> > > report a
> > > > > > > small
> > > > > > > > > size.
> > > > > > > > > > > > > > > > > But, as of right now,
> > > > > > > > > > > > > > > > > RFC2460 Section 5 is the normative behavi=
or.
> > > > > > > > > > > > > > > > [RPB]
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Absolutely correct. The procedures describe=
d in
> > > Section
> > > > > 5 or
> > > > > > > > > > > > > > > > RFC
> > > > > > > > > > > > > > > > 246 are
> > > > > > > > > > > > > > > normative.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I don't how this impacts the WG's LC decisi=
on
> > > regarding
> > > > > the
> > > > > > > > > > > > > > > > current
> > > > > > > > > > > > > draft.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Broken behavior should not be specified, whet=
her
> > > > > alternative
> > > > > > > or
> > > > > > > > > > > default.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks - Fred
> > > > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Ron
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Thanks ? Fred
> > > > > > > > > > > > > > > > > fred.l.templin@boeing.com
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > Int-area mailing list
> > > > > > > > > Int-area@ietf.org
> > > > > > > > > https://www.ietf.org/mailman/listinfo/int-area


From nobody Thu Apr  2 07:49:16 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 077261A9147; Thu,  2 Apr 2015 07:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lbf_TcziCFLf; Thu,  2 Apr 2015 07:49:11 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF5761A9138; Thu,  2 Apr 2015 07:49:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t32EnAiC007613; Thu, 2 Apr 2015 09:49:11 -0500
Received: from XCH-PHX-212.sw.nos.boeing.com (xch-phx-212.sw.nos.boeing.com [130.247.25.141]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t32Emp3v006874 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 2 Apr 2015 09:49:06 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-PHX-212.sw.nos.boeing.com ([169.254.12.72]) with mapi id 14.03.0210.002; Thu, 2 Apr 2015 07:49:03 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYgAALjyCAAAhGi8AAB9x+QAACAahAAIAzugA==
Date: Thu, 2 Apr 2015 14:49:02 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E30D40@XCH-BLV-504.nw.nos.boeing.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E30214@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432C22@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936432C22@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/d5Se37o8vP7i4l-iPZjU6XY4pwM>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 14:49:13 -0000

Hi David,

> > This is where we differ - there is nothing in this recommendation
> > that is specific to GRE - the recommendation applies to any generic
> > IPv6 encapsulation and is appropriate to only those use cases where
> > shutting down the tunnel altogether is preferable to allowing the
> > tunnel to fragment. This is a generic IPv6 encapsulation consideration;
> > not a GRE consideration.
>=20
> The "running code" involved here is GRE.  I am concerned that we lack
> the foundation to update 2473 for all encapsulated protocols.

I don't get that. Just write a 3-pager that says it is OK for any kind of
tunnel to collapse if it gets into a state where fragmentation is needed;
a halt-and-catch-fire clause. But, why would you even need an RFC for that?

Thanks - Fred
fred.l.templin@boeing.com


From nobody Thu Apr  2 08:08:06 2015
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF2381B2CC8; Thu,  2 Apr 2015 08:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2X41pV03jUYo; Thu,  2 Apr 2015 08:08:02 -0700 (PDT)
Received: from webspace.isi.edu (webspace.isi.edu [128.9.64.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 622CF1B2CC1; Thu,  2 Apr 2015 08:08:02 -0700 (PDT)
Received: from [192.168.1.10] (pool-71-103-148-202.lsanca.dsl-w.verizon.net [71.103.148.202]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id t32F6H09011985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 2 Apr 2015 08:06:28 -0700 (PDT)
Message-ID: <551D5AE7.6050806@isi.edu>
Date: Thu, 02 Apr 2015 08:06:15 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E30214@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432C22@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E30D40@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E30D40@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/daqNMN1cxrBf0QyuEoxQb4kJemI>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 15:08:04 -0000

On 4/2/2015 7:49 AM, Templin, Fred L wrote:
> Hi David,
> 
>>> This is where we differ - there is nothing in this recommendation
>>> that is specific to GRE - the recommendation applies to any generic
>>> IPv6 encapsulation and is appropriate to only those use cases where
>>> shutting down the tunnel altogether is preferable to allowing the
>>> tunnel to fragment. This is a generic IPv6 encapsulation consideration;
>>> not a GRE consideration.
>>
>> The "running code" involved here is GRE.  I am concerned that we lack
>> the foundation to update 2473 for all encapsulated protocols.
> 
> I don't get that. Just write a 3-pager that says it is OK for any kind of
> tunnel to collapse if it gets into a state where fragmentation is needed;
> a halt-and-catch-fire clause. But, why would you even need an RFC for that?

For the benefit of others, here's my view on this (as I posted to Fred
yesterday, which is where collapsing the tunnel comes from):

defs:
	ingress packet - what arrives at the tunnel ingress

	egress packet - what leaves at the tunnel egress

	tunnel packet - packet that traverses from the
			ingress to egress, that contains
			the ingress packet plus encapsulation

	tunnel MTU - MTU of the path between ingress and egress
		of tunneled packets

	reassembly MTU - largest tunnel packet that can be
		reassembled at the egress

General rules (which apply to more than GRE; they should apply to ANY
tunnel that carries ANY packet):

	ingress packet <= (tunnel MTU - encapsulation)
		send through the tunnel as one tunnel packet

	ingress packet > (reassembly MTU - encapsulation)
		drop and send ICMP PTB back

	(tunnel MTU - encaps) < ingress packet <= (reassy MTU - encaps)
		do one of the following:

		a) fragment at ingress and reassemble at egress

		b) drop and declare the link down to all further
		traffic until a probe of size "reassy MTU"
		succeeds to the egress

		(this is what Fred just called "halt and catch fire",
		but it has an important property:
			- stay down while the required tunnel MTU
			cannot traverse without fragmentation
			- come up when the required tunnel MTU
			is supported)

		(a) is more robust but more expensive to implement

The tunnel MTU is defined by the protocols over which the tunnel is
defined as transiting.

The egress MTU is defined by the encapsulation protocol.
		
Note: the (b) case is allowed because a link can always declare itself
down. What it should never do is fail to transit packets that should fit
while allowing other smaller packets to get through - i.e., a link
should never be allowed to redefine the specs of the type of protocol
link it intends to support.

The rules are augmented a bit when the ingress packet can be re-fragmented:

	ingress packet <= (tunnel MTU - encapsulation)
		send through the tunnel as one tunnel packet

	ingress packet > (reassembly MTU - encapsulation)
		refragment the ingress packet to fit the tunnel MTU

	(tunnel MTU - encaps) < ingress packet <= (reassy MTU - encaps)
		do one of the following:
		a) fragment at ingress and reassemble at egress

		b) refragment the ingress packet to fit the tunnel MTU

		in this case, (b) is preferred
---



From nobody Thu Apr  2 08:35:05 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59671B2D33; Thu,  2 Apr 2015 08:35:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1AB6XHaYpuX; Thu,  2 Apr 2015 08:35:02 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D8081B2D2D; Thu,  2 Apr 2015 08:35:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t32FZ17J032610; Thu, 2 Apr 2015 08:35:01 -0700
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t32FYw4A032481 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 2 Apr 2015 08:34:59 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.107]) with mapi id 14.03.0210.002; Thu, 2 Apr 2015 08:34:58 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Topic: [Int-area] draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative configuration
Thread-Index: AdBsIGaY/gSp6LdDRyOAYy9uht3UAwAZR72AAAMZN0AAANCb0AAIDWYgAALjyCAAAhGi8AAB9x+QAACAahAAIAzugAAPfLGAAA3hYcA=
Date: Thu, 2 Apr 2015 15:34:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E30EAC@XCH-BLV-504.nw.nos.boeing.com>
References: <CE03DB3D7B45C245BCA0D243277949364314CF@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2F84E@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936431F30@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E2FA16@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D2432779493643267B@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E300C8@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432B99@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E30214@XCH-BLV-504.nw.nos.boeing.com> <CE03DB3D7B45C245BCA0D24327794936432C22@MX104CL02.corp.emc.com> <2134F8430051B64F815C691A62D9831832E30D40@XCH-BLV-504.nw.nos.boeing.com> <551D5AE7.6050806@isi.edu>
In-Reply-To: <551D5AE7.6050806@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8Q76k7gCnZrnFyRF5hwtEAL_Xkk>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 15:35:04 -0000

Hi Joe,

It looks from your description that you have at least read Section 3.13 of
draft-templin-aerolink, because there are many similarities. However,
AERO is more comprehensive in the way it minimizes fragmentation and
turns off fragmentation when it is no longer needed. AERO also allows
larger packets through even if they are larger than the maximum size the
egress is capable of reassembling. There is no reason the egress' maximum
reassembly unit needs to be as large as the largest packet that can travers=
e
the tunnel in one piece.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Thursday, April 02, 2015 8:06 AM
> To: Templin, Fred L; Black, David; int-area@ietf.org; ipv6@ietf.org
> Cc: draft-ietf-intarea-gre-ipv6@tools.ietf.org; intarea-chairs@ietf.org
> Subject: Re: [Int-area] draft-ietf-intarea-gre-ipv6 - Sec 3.1 alternative=
 configuration
>=20
>=20
>=20
> On 4/2/2015 7:49 AM, Templin, Fred L wrote:
> > Hi David,
> >
> >>> This is where we differ - there is nothing in this recommendation
> >>> that is specific to GRE - the recommendation applies to any generic
> >>> IPv6 encapsulation and is appropriate to only those use cases where
> >>> shutting down the tunnel altogether is preferable to allowing the
> >>> tunnel to fragment. This is a generic IPv6 encapsulation consideratio=
n;
> >>> not a GRE consideration.
> >>
> >> The "running code" involved here is GRE.  I am concerned that we lack
> >> the foundation to update 2473 for all encapsulated protocols.
> >
> > I don't get that. Just write a 3-pager that says it is OK for any kind =
of
> > tunnel to collapse if it gets into a state where fragmentation is neede=
d;
> > a halt-and-catch-fire clause. But, why would you even need an RFC for t=
hat?
>=20
> For the benefit of others, here's my view on this (as I posted to Fred
> yesterday, which is where collapsing the tunnel comes from):
>=20
> defs:
> 	ingress packet - what arrives at the tunnel ingress
>=20
> 	egress packet - what leaves at the tunnel egress
>=20
> 	tunnel packet - packet that traverses from the
> 			ingress to egress, that contains
> 			the ingress packet plus encapsulation
>=20
> 	tunnel MTU - MTU of the path between ingress and egress
> 		of tunneled packets
>=20
> 	reassembly MTU - largest tunnel packet that can be
> 		reassembled at the egress
>=20
> General rules (which apply to more than GRE; they should apply to ANY
> tunnel that carries ANY packet):
>=20
> 	ingress packet <=3D (tunnel MTU - encapsulation)
> 		send through the tunnel as one tunnel packet
>=20
> 	ingress packet > (reassembly MTU - encapsulation)
> 		drop and send ICMP PTB back
>=20
> 	(tunnel MTU - encaps) < ingress packet <=3D (reassy MTU - encaps)
> 		do one of the following:
>=20
> 		a) fragment at ingress and reassemble at egress
>=20
> 		b) drop and declare the link down to all further
> 		traffic until a probe of size "reassy MTU"
> 		succeeds to the egress
>=20
> 		(this is what Fred just called "halt and catch fire",
> 		but it has an important property:
> 			- stay down while the required tunnel MTU
> 			cannot traverse without fragmentation
> 			- come up when the required tunnel MTU
> 			is supported)
>=20
> 		(a) is more robust but more expensive to implement
>=20
> The tunnel MTU is defined by the protocols over which the tunnel is
> defined as transiting.
>=20
> The egress MTU is defined by the encapsulation protocol.
>=20
> Note: the (b) case is allowed because a link can always declare itself
> down. What it should never do is fail to transit packets that should fit
> while allowing other smaller packets to get through - i.e., a link
> should never be allowed to redefine the specs of the type of protocol
> link it intends to support.
>=20
> The rules are augmented a bit when the ingress packet can be re-fragmente=
d:
>=20
> 	ingress packet <=3D (tunnel MTU - encapsulation)
> 		send through the tunnel as one tunnel packet
>=20
> 	ingress packet > (reassembly MTU - encapsulation)
> 		refragment the ingress packet to fit the tunnel MTU
>=20
> 	(tunnel MTU - encaps) < ingress packet <=3D (reassy MTU - encaps)
> 		do one of the following:
> 		a) fragment at ingress and reassemble at egress
>=20
> 		b) refragment the ingress packet to fit the tunnel MTU
>=20
> 		in this case, (b) is preferred
> ---
>=20


From nobody Thu Apr  2 09:53:36 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E36AE1A9131 for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 09:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 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, SPF_PASS=-0.001] autolearn=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 HX5VUO0wIin5 for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 09:53:33 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::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 8D2E11A890F for <ipv6@ietf.org>; Thu,  2 Apr 2015 09:53:32 -0700 (PDT)
Received: by lbbzk7 with SMTP id zk7so47526466lbb.0 for <ipv6@ietf.org>; Thu, 02 Apr 2015 09:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=0lFf1KRhF5GZ2LZFisB9UgCFwCVV7SzgEVgOQ4CvXuM=; b=V2lwE1AIYilwaA3zMsQ4sEiEgLZmPMS7/OSsJLc6iI5KaSS8OI5bandiRFnZkWZr5K Qog2lLfVXIWuBdHcfBA9vDvv0z1K5NTMO/WfiWbvxq6aacH8x/UuQAd4H8GwQWIQ9ke/ S6KizFAMnF+kwfx+xkqMHDO9RAD2Bz8OiU6EWc2kQ8QQ9V+LkogdXVMAHoHLwxkVAT8+ snm6E03qXK8FzrmRee9aQb305KqOu4edH7TW3vgvmExs5/ZXyQ/vpuErsVfSXjYP99KF rGv8EzYqlkwSio8EwwSj04vScso7kfHs1KB5tV9wM/uT9mdMs1FHyqoTezVn93LrVeaS s7rg==
MIME-Version: 1.0
X-Received: by 10.152.121.72 with SMTP id li8mr4856139lab.11.1427993611050; Thu, 02 Apr 2015 09:53:31 -0700 (PDT)
Received: by 10.114.59.103 with HTTP; Thu, 2 Apr 2015 09:53:30 -0700 (PDT)
In-Reply-To: <1678786622.4013980.1427930610519.JavaMail.yahoo@mail.yahoo.com>
References: <CAC8QAccQ6hmEpOE5KB=L361nt41V1JcwfFn9o7=Y1sS7yw0aMA@mail.gmail.com> <1678786622.4013980.1427930610519.JavaMail.yahoo@mail.yahoo.com>
Date: Thu, 2 Apr 2015 11:53:30 -0500
Message-ID: <CAC8QAcdQuZ+re33QUq4eD1HXz=mNG49EbmccFHpzfNT359kovQ@mail.gmail.com>
Subject: Re: RA Option Guidelines
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/C-jQr8iLZmmbo6qJCEZaZD4iMtE>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 16:53:35 -0000

On Wed, Apr 1, 2015 at 6:23 PM, Mark ZZZ Smith
<markzzzsmith@yahoo.com.au> wrote:
> Hi Behcet,
>
>
> ----- Original Message -----
> From: Behcet Sarikaya <sarikaya2012@gmail.com>
> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
> Cc: "STARK, BARBARA H" <bs7652@att.com>; Hemant Singh (shemant) <shemant@=
cisco.com>; "ipv6@ietf.org" <ipv6@ietf.org>
> Sent: Thursday, 2 April 2015, 6:21
> Subject: Re: RA Option Guidelines
>
> I don't understand why DHCPv6 is being discussed under RA Option Guidelin=
es?
> If DHCPv6 is being used instead of RA, like in Australia, that
> supports our position that we should also define DHCPv6 options for
> SADR.
>
> / DHCPv6 isn't being used instead of RAs in Australia.
>
> / I think the fundamental problem is people are considering RAs and DHCPv=
6 to be functional equivalents (like e.g., OSPF vs IS-IS), and therefore th=
inking that DHCPv6 options should be imported into RAs and vice versa.
>

No, I don't think anybody proposed that, not at myself.
I think you are missing the context here.

> / There are critical operational limitations that RAs have that DHCPv6 do=
esn't (because the RA mechanisms are much simpler), and by trying to use RA=
s for the same purpose as DHCPv6,

No, I don't know how you got this? I am sure it is not from SADR discussion=
s.

> all the problems already solved for DHCPv6 would have to be solved again =
for RAs. The desired simplicity of using RAs only would disappear because t=
he complexity of replicating DHCPv6 mechanisms, and the additional signific=
ant operational overheads of constant firmware upgrades to routers to add R=
A options.
>

Yes, there are some parallels like DHCP option guidelines document. I
think that you are blowing it out of proportion.
If it were like you thought then one would say whatever DHCP
guidelines says applies to RA options also and that's it.

The context as I see it is that there are new RA options that are
being defined, maybe it is time to come up with some guidelines. I
view it is natural that this is happening because IPv6 is being
deployed more and more.

DHCP options in this context came about because some people say maybe
we should define the corresponding DHCP options not vice versa. Please
see
http://tools.ietf.org/wg/mif/draft-ietf-mif-mpvd-arch/

and
https://tools.ietf.org/html/draft-ietf-mif-mpvd-ndp-support-01
https://tools.ietf.org/html/draft-ietf-mif-mpvd-dhcp-support-01

Regards,

Behcet


> Regards,
>
> Mark.
>
>
>
> Regards,
> Behcet
>
>
> On Tue, Mar 31, 2015 at 9:33 PM, Mark ZZZ Smith
> <markzzzsmith@yahoo.com.au> wrote:
>> Hi Barbara,
>>
>> ________________________________
>> From: "STARK, BARBARA H" <bs7652@att.com>
>> To: Hemant Singh (shemant) <shemant@cisco.com>; Mark ZZZ Smith
>> <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@innovationslab.net>;
>> "ipv6@ietf.org" <ipv6@ietf.org>
>> Sent: Wednesday, 1 April 2015, 0:24
>> Subject: RE: RA Option Guidelines
>>
>>
>>
>>> The problem that Mark  raised and also provided a solution for is to ad=
d
>>> DHCPv6 relay functionality to the CE router.  He is also correct that R=
FC
>>> 6204
>>> does not include DHCPv6 relay agent functionality in the CE router.
>>>
>>> The other choice for a solution is to include the DHCPv6 options in the
>>> RA.
>>> For this solution to work the SP will send new DHCPv6 options in the RA=
 to
>>> the CE router WAN.  The RA terminates at the CE WAN.  The CE generates =
a
>>> new RA for the LAN.  RFC 6204 does not include functionality to bridge =
the
>>> SP
>>> RA received on the CE WAN to the CE LAN.  So even for the RA solution t=
o
>>> work, a new requirement would need to be added to RFC 6204.  Did I miss
>>> anything in the RA solution I described above?  If not, either way, one
>>> adds a
>>> new requirement to the CE router and if it's DHCPv6 options, let DHCPv6
>>> protocol deal with it.
>>
>>
>> RFC 7084 already says:
>>   L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>>           options (as listed in Section 5.3 of [RFC3736]) received from
>>           the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>>           server.
>> Where the RFC3736 list of options is for DNS Recursive Name Servers, DNS
>> search list, and SIP Servers.
>>
>> My personal, as-a-consumer, freaking-out-about-privacy opinion is that t=
he
>> idea of my ISPs (both of them, but potentially 3) sending any configurat=
ion
>> options they feel like down to my personal and private LAN host devices =
is
>> not to my liking. I realize that some people are blithely happy to turn =
over
>> their privacy to ISPs. So maybe relay of all unrecognized options could =
be
>> something an ISP puts into CE routers they supply to their customers. I
>> prefer for it not to be in the retail ones I purchase, and I would be
>> adamant about it not being on by default in such retail CE routers. So l=
et
>> such relay requirements go into eRouter or BBF specs, but please keep th=
em
>> out of IETF and homenet specs.
>>
>> / I think you're already trusting your ISP possibly much more than you m=
ight
>> realise. They're already supplying you with the Internet addressing you =
use,
>> you're probably using their DNS resolvers, you may be using their email
>> servers, and of course they can tap your clear text traffic without you
>> knowing.
>>
>> / Even if you only used their addressing and encrypted all of your traff=
ic
>> over a tunnel through their infrastructure, you'd still then be trusting=
 the
>> remote tunnel endpoint provider, likely to be another party other than
>> yourself.
>>
>> Since I'm in the process of setting up my new homenet router (Pierre fla=
shed
>> my new router for me last week) to connect upstream to both my ISPs (one
>> cable provider and one telco), I also really don't want dueling relayed
>> options reaching my LAN hosts. I do think that in the future a significa=
nt
>> number of people will choose to subscribe to multiple providers -- as lo=
ng
>> as it's easy to do. The ISPs get to configure the CE router WAN interfac=
es
>> to work with their access networks -- and that needs to be the extent of
>> their reach unless I specifically give them conscious permission to do m=
ore.
>> If they want to configure devices inside my LAN, I think they should use=
 a
>> higher layer configuration protocol with mandatory and default-on securi=
ty
>> (which neither RA nor DHCPv6 have).
>>
>> / So I think the world is moving in the other direction. People have bee=
n
>> outsourcing the maintenance of their devices in droves as they adopt
>> smartphones and tablets, and more recently with devices like Google's
>> Chromebooks. They're giving up control rather than desiring more of it, =
for
>> the gains of more convenience and lower costs.
>>
>> / Regards,
>> Mark.
>>
>>
>> Barbara
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>


From nobody Thu Apr  2 12:07:11 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76E0B1A0364 for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 12:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMe2SKsnznay for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 12:07:04 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 242841A0113 for <ipv6@ietf.org>; Thu,  2 Apr 2015 12:07:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33700; q=dns/txt; s=iport; t=1428001624; x=1429211224; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=1TfmSOid7u0nOBqVA4XkTAc56l+uFKLnJzYxfZPTPiU=; b=WqiihXIVTd2bNVxmfLlqVRAQYbp62ekAEr56O+CthPtjiSHDZmN7gIKT mQM0Xx1F+KN3dpftsguuuPdNe7lLgyzeWlJQLpZ66j2zZ6mvrR5TMpWKR a8Jb8BSYi/1HsG/oo0J5vZeD4sHA6z2Z/lr7NUB9GyS5hBG+LiXIlS5mp Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AyDAA8kh1V/4kNJK1cgkVDUlwFgxDFBYNKAhyBL0wBAQEBAQF+hB4BAQEEIwpYBAIBCBEEAQELFgcDAgICMBQJCAIEARIIiBMDEbYBmBYBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiymCR4FnCREnEAEGgmIvgRYFhRAKiUGCD4g5gmSGEoYcToJng0gig29vgQRAfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,512,1422921600";  d="scan'208,217";a="408782598"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-3.cisco.com with ESMTP; 02 Apr 2015 19:07:03 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t32J73pn020227 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 19:07:03 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 14:07:02 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, "STARK, BARBARA H" <bs7652@att.com>, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRsw
Date: Thu, 2 Apr 2015 19:07:01 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <137497078.3130141.1427853117870.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <137497078.3130141.1427853117870.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.71.118]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B8916837EE3xmbrcdx06ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/kWHvcfotJBV7YxAhVq1CHvas6pk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 19:07:10 -0000

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

TWFyaywNCg0KVGhlIHN0YXRlbGVzcyBESENQdjYgc2VydmVyIGluIFJGQzM3MzYgYWxsb3dzIGZv
ciBuZXcgb3B0aW9ucyB0byBiZSBzZXJ2ZWQgYnkgdGhlIHN0YXRlbGVzcyBzZXJ2ZXIuICAgUmVh
ZCB0aGUgZmlyc3QgcGFyYWdyYXBoIG9mIHNlY3Rpb24gNS4zIGluIFJGQzM3MzYuICBTbyB0aGUg
bmV3IG9wdGlvbnMgeW91IHdhbnQgdG8gc2VydmUgY2FuIGJlIHNlcnZlZCBieSB0aGUgQ0Ugc3Rh
dGVsZXNzIERIQ1B2NiBzZXJ2ZXIuICAgTm93LCBpZiB0aGUgc2VydmljZSBwcm92aWRlciBjb25m
aWd1cmVzIGhpcy9oZXIgREhDUHY2IHNlcnZlciB0byByZXR1cm4gbmV3IG9wdGlvbnMgdG8gdGhl
IENFIFdBTiBpbnRlcmZhY2UgYWRkcmVzcyBhY3F1aXNpdGlvbiwgdGhlIENFIHVzZXMgdGhlIG9w
dGlvbnMgb24gdGhlIExBTi4gIFNlZSBidWxsZXQgTC0xMiBvZiBSRkMgNzA4NC4gIEV4aXN0aW5n
IFJGQ3Mgc3VwcG9ydCB5b3VyIHVzZSBjYXNlIGFuZCBubyBkaGNwdjYgcmVsYXkgaXMgcmVxdWly
ZWQgaW4gdGhlIENFLg0KDQpCYXJiYXJhLA0KDQpGb3IgeW91ciB1c2UgY2FzZSwgdGhlIHNlcnZp
Y2UgcHJvdmlkZXIgY29uZmlndXJlcyB0aGUgREhDUHY2IHNlcnZlciB0byBvbmx5IHNlcnZlIG9w
dGlvbnMgc3BlY2lmaWVkIGluIFJGQyA3MDg0LiAgVGh1cyBpbiB0aGlzIGRlcGxveW1lbnQgbm8g
ZXh0cmEgb3B0aW9ucyBleGlzdCB0byBzZXJ2ZSB0byB0aGUgQ0Ugcm91dGVyIExBTi4NCg0KQm90
aCB1c2UgY2FzZXMgY2FuIGJlIHN1cHBvcnRlZCB1c2luZyBleGlzdGluZyBSRkPigJlzLg0KDQpI
ZW1hbnQNCg0KRnJvbTogTWFyayBaWlogU21pdGggW21haWx0bzptYXJrenp6c21pdGhAeWFob28u
Y29tLmF1XQ0KU2VudDogVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgOTo1MiBQTQ0KVG86IEhlbWFu
dCBTaW5naCAoc2hlbWFudCk7IFNUQVJLLCBCQVJCQVJBIEg7IEJyaWFuIEhhYmVybWFuOyBpcHY2
QGlldGYub3JnDQpTdWJqZWN0OiBSZTogUkEgT3B0aW9uIEd1aWRlbGluZXMNCg0KSGkgSGVtYW50
LA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogSGVtYW50IFNpbmdo
IChzaGVtYW50KSA8c2hlbWFudEBjaXNjby5jb208bWFpbHRvOnNoZW1hbnRAY2lzY28uY29tPj4N
ClRvOiAiU1RBUkssIEJBUkJBUkEgSCIgPGJzNzY1MkBhdHQuY29tPG1haWx0bzpiczc2NTJAYXR0
LmNvbT4+OyBNYXJrIFpaWiBTbWl0aCA8bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdTxtYWlsdG86
bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdT4+OyBCcmlhbiBIYWJlcm1hbiA8YnJpYW5AaW5ub3Zh
dGlvbnNsYWIubmV0PG1haWx0bzpicmlhbkBpbm5vdmF0aW9uc2xhYi5uZXQ+PjsgImlwdjZAaWV0
Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+IiA8aXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBp
ZXRmLm9yZz4+DQpTZW50OiBXZWRuZXNkYXksIDEgQXByaWwgMjAxNSwgMToyNw0KU3ViamVjdDog
UkU6IFJBIE9wdGlvbiBHdWlkZWxpbmVzDQoNCkJhcmJhcmEsDQoNClRoYW5rcyBmb3IgcmVwbHlp
bmcuDQoNCk1hcmssDQoNCklmIG5ldyBESENQdjYgb3B0aW9ucyBhcmUgYWRkZWQgdG8gYmUgc3Vw
cG9ydGVkIGJ5IFJGQzM3MzYsIHRoZW4gdGhlIFNQIGluY2x1ZGVzIHRoZSBuZXcgb3B0aW9uIGlu
IHRoZSBESENQdjYgcmVzcG9uc2VzIHRvIHRoZSBDUEUgV0FOLiAgVGhlbiB0aGUgQ1BFIGluY2x1
ZGVzIHRoZSBuZXcgb3B0aW9uIHRvIGl0cyBMQU4gREhDUHY2IGNsaWVudHMuDQoNCi8gIFNvIGhl
cmUgaXMgYSBzY2VuYXJpby4NCg0KLyBBcyBhbiBJU1AsIG15IGN1c3RvbWVycyBoYXZlIFZvSVAg
aGFuZHNldHMgdGhhdCBtaWdodCBzdXBwb3J0IHRoZSBPUFRJT05fR0VPTE9DQVRJT04gREhDUHY2
IG9wdGlvbiAoSSBtaWdodCBrbm93IHRoYXQgYSBwb3J0aW9uIG9mIHRoZW0gZG8sIGJlY2F1c2Ug
dGhleSd2ZSBib3VnaHQgdGhvc2UgVm9JUCBoYW5kc2V0cyBmcm9tIG1lKS4gSG93IGxvbmcgaXMg
aXQgZ29pbmcgdG8gdGFrZSBmb3IgbWUgdG8gZ2V0IHRoYXQgb3B0aW9uIGFkZGVkIHRvIGFuIHVw
ZGF0ZWQgUkZDMzczNiBhbmQgUkZDNzA4NCwgdG8gZ2V0IG15IENQRSB2ZW5kb3IgdG8gdXBkYXRl
IGFuZCByZWxlYXNlIHRoZWlyIGZpcm13YXJlIHRvIHN1cHBvcnQgdGhhdCBvcHRpb24sIGFuZCB0
ZXN0IHRoYXQgbmV3IENQRSBmaXJtd2FyZSBhbmQgdGhlbiB0byBkZXBsb3kgdGhhdCBuZXcgZmly
bXdhcmU/DQoNCi8gSSB0aGluayBJJ2QgYmUgbHVja3kgaWYgaXQgb25seSB0b29rIDIgeWVhcnMu
DQoNCi8gQSBmZXcgbW9udGhzIGxhdGVyIEkgZGVjaWRlIEkgd2FudCB0byBwcm92aWRlIE9QVElP
Tl9ORVdfUE9TSVhfVElNRVpPTkUgdG8gbXkgY3VzdG9tZXJzIGlmIHRoZWlyIGhvc3RzIHJlcXVl
c3QgaXQuIFNvIG5vdyBJIGhhdmUgdG8gdHJ5IHRvIGdldCBPUFRJT05fTkVXX1BPU0lYX1RJTUVa
T05FIGFkZGVkIHRvIHRoZSB1cGRhdGVkIFJGQzM3MzYsIHRvIGdldCBteSBDUEUgdmVuZG9yIHRv
IHVwZGF0ZSBhbmQgcmVsZWFzZSB0aGVpciBmaXJtd2FyZSB0byBzdXBwb3J0IHRoYXQgb3B0aW9u
LCBhbmQgdGVzdCB0aGF0IG5ldyBDUEUgZmlybXdhcmUgYW5kIHRoZW4gdG8gZGVwbG95IHRoYXQg
bmV3IGZpcm13YXJlLg0KDQovIE5vdyBpZiBJJ20gbHVja3kgSSBjb3VsZCBhZGQgaXQgdG8gdGhl
IGRyYWZ0IGZvciBPUFRJT05fR0VPTE9DQVRJT04sIHNvIGl0IGlzIHN0aWxsICJvbmx5IiAyIHll
YXJzIHRvIGdldCB0byBhIHBvaW50IHdoZXJlIEkgY291bGQgcHJvdmlkZSB0aG9zZSBvcHRpb25z
IHRvIG15IGN1c3RvbWVycy4gQnV0IHdoYXQgaWYgdGhhdCBkcmFmdCBoYXMgcHJvZ3Jlc3NlZCB0
b28gZmFyIHRob3VnaCB0aGUgSUVURiBwdWJsaXNoaW5nIHByb2Nlc3M/IEkgaGF2ZSB0byBjcmVh
dGUgYSBuZXcgZHJhZnQgdXBkYXRpbmcgdGhlIHRvIGJlIHB1Ymxpc2hlZCBkcmFmdC4NCg0KLyBT
bywgdG8gYWNoaWV2ZSB3aGF0IHNob3VsZCBiZSBhIHNpbXBsZSB0YXNrIG9mIHByb3ZpZGluZyBs
b2NhdGlvbiBvciB0aW1lem9uZSBpbmZvcm1hdGlvbiB0byBjdXN0b21lcnMnIGVuZCBob3N0cyBp
ZiB0aGV5IHdhbnQgaXQsIHdlJ3ZlIGp1c3QgaW5jdXJyZWQgdGhlIG1hc3NpdmUgY29zdHMgYW5k
IHRpbWUgZGVsYXlzIG9mIHRoZSBJRVRGIHB1Ymxpc2hpbmcgcHJvY2VzcywgdmVuZG9yIGZpcm13
YXJlIHVwZ3JhZGVzLCBmaXJtd2FyZSB0ZXN0aW5nIGFuZCBmaXJtd2FyZSBkZXBsb3ltZW50LiBT
b3VuZHMgbGlrZSBob3cgaGFyZCBJIHVuZGVyc3RhbmQgaXQgd2FzIHRvIHJvbGwgb3V0IGZlYXR1
cmVzIGxpa2UgQ0xJIGluIFBTVE4gbmV0d29ya3MgLi4uDQoNCiBXaGF0IGlzIG9uZSBvcHRpb24g
eW91J2QgbGlrZSB0aGUgaG9zdCBvbiB0aGUgTEFOIHRvIGluY2x1ZGUgc28gdGhhdCB3ZSBjYW4g
dW5kZXJzdGFuZCB5b3VyIHVzZSBjYXNlIGJldHRlcj8NCg0KLyBJJ20gZ29pbmcgdG8gbWFrZSB0
aGUgcHJvYmxlbSBtdWNoIGhhcmRlciBmb3IgeW91LiBJIHdhbnQgdGhlIENQRSB0byAic3VwcG9y
dCIgb3IgYmV0dGVyLCBiZSB0cmFuc3BhcmVudCB0bywgYWxsIGN1cnJlbnQgYW5kIGZ1dHVyZSBE
SENQdjYgb3B0aW9ucywgYW5kIEkgZG9uJ3Qgd2FudCB0byBoYXZlIHRvIHVwZ3JhZGUgb3IgYXNr
IG15IGN1c3RvbWVycyB0byBzdWNjZXNzZnVsbHkgdXBncmFkZSB0aGVpciBDUEUgZWFjaCBhbmQg
ZXZlcnkgdGltZSB0aGVyZSBpcyBhIG5ldyBESENQdjYgb3B0aW9uIGRlZmluZWQgdGhhdCBtaWdo
dCBiZSB1c2VmdWwgdG8gbWUgYW5kIHRoZW0uIEkgd2FudCB0byBiZSBhYmxlIHRvIHByb3ZpZGUg
c2VydmljZSBwYXJhbWV0ZXJzIHRvIG15IGN1c3RvbWVycyBob3N0cywgZGlyZWN0bHkgb3IgaW5k
aXJlY3RseSwgd2l0aG91dCB0aGUgc29mdHdhcmUgcmV2aXNpb24gb3IgbW9kZWwgb2YgdGhlaXIg
Q1BFIGJlaW5nIHRoZSBjb25zdHJhaW50Lg0KDQpUaGUgU0lQIHNlcnZlciBpcyBhbHJlYWR5IGlu
Y2x1ZGVkIGFzIG9uZSBvcHRpb24gc3VwcG9ydGVkIGJ5IFJGQzM3MzYuICBDZXJ0YWlubHksIGlm
IHRoZSBTSVAgc2VydmVyIHN1cHBvcnQgaXMgbmVlZGVkIGluIHRoZSBSQSwgSSBhbSBvcGVuIGZv
ciBpdCBzaW5jZSB0aGUgUkEgYWxyZWFkeSBpbmNsdWRlcyBETlMgaW5mb3JtYXRpb24uDQoNCi8g
SSBkb24ndCB0aGluayBETlMgaW4gUkFzIHdhcyBhIGdvb2QgaWRlYSwgYW5kIG5laXRoZXIgd2Vy
ZSBTSVAgb3B0aW9ucyB3aGVuIHRoZXkgd2VyZSBwcm9wb3NlZC4gU2VlIHRoYXQgdGltZSBjb25z
dW1pbmcgYW5kIHNlcnZpY2UgZGlzcnVwdGluZyBmaXJtd2FyZSB1cGdyYWRlIGN5Y2xlIGZvciBu
ZXcgREhDUHY2IG9wdGlvbnM/IFNhbWUgcHJvYmxlbSBpZiB5b3UgdXNlIFJBIG9wdGlvbnMgdG8g
YWNoaWV2ZSB0aGUgc2FtZSBnb2FsLiBOZXcgZmlybXdhcmUgdXBncmFkZSBlYWNoIHRpbWUgeW91
IHdhbnQgdG8gc3VwcG9ydCBhIG5ldyBSQSBvcHRpb24uDQoNCi8gRHVwbGljYXRpb24gYmV0d2Vl
biBSQSBvcHRpb25zIGFuZCBESENQdjYgb3B0aW9ucyBhbHNvIGNhdXNlcyBtb3JlIHByb2JsZW1z
LiBXaGljaCBpcyBwcmVmZXJyZWQ/IEFyZSB0aGV5IHRyZWF0ZWQgZXF1YWxseSBvciBkb2VzIG9u
ZSB0YWtlIHByZWNlZGVuY2Ugb3ZlciB0aGUgb3RoZXI/IEFzIGZhciBhcyBJJ20gYXdhcmUsIHRo
ZXNlIHF1ZXN0aW9ucyBoYXZlbid0IGJlZW4gYW5zd2VyZWQgZm9yIHRoZSBESENQdjYgRE5TIGFu
ZCBSQSBETlMgb3B0aW9ucyB5ZXQuIEl0IG1pZ2h0IGJlIHNpbXBsZSB0byBjb21lIHVwIHdpdGgg
YSBzaW1wbGUgcnVsZSBmb3IgbW9yZSBESENQdjYgb3B0aW9ucyBhcmUgZHVwbGljYXRlZCBpbnRv
IFJBcywgaG93ZXZlciB0aGVpciBtaWdodCBiZSBzb21lIHNwZWNpZmljIGNhc2VzIHdoZXJlIHRo
ZSBSQSBvcHRpb24gdmFsdWUgc2hvdWxkIGJlIHByZWZlcnJlZCBvdmVyIHRoZSBESENQdjYgZXF1
aXZhbGVudCBvcHRpb24gYW5kIHZpY2UtdmVyc2EuDQoNCkhvd2V2ZXIsIEkgc3RpbGwgYXNrIHRo
ZSBxdWVzdGlvbiBhcyB0byBob3cgYW4gUkEgcmVjZWl2ZWQgYXQgdGhlIFdBTiBvZiB0aGUgQ1BF
IGhhcyBpdHMgb3B0aW9ucyBwcm9wYWdhdGVkIHRvIHRoZSBSQSBvbiB0aGUgTEFOPyAgQXQgdGhl
IHRpbWUgb2Ygd3JpdGluZyBSRkMgNjIwNCBvciBSRkMgNzA4NCwgdGhlcmUgaXMgbm8gc3VjaCBw
cm92aXNpb24gYmV0d2VlbiB0aGUgUkEgcmVjZWl2ZWQgb24gdGhlIFdBTiBhbmQgdGhlIFJBIGlz
c3VlZCBvbiB0aGUgTEFOIG9mIHRoZSBDRSByb3V0ZXIuDQoNCi8gVXNlIGEgREhDUHY2IHJlbGF5
IGluIHRoZSBDUEUuIFRoZW4gdGhlcmUgaXNuJ3QgYSBwcm9ibGVtLCBuZXcgREhDUHY2IG9wdGlv
bnMgdGhhdCBhcmUgdW5rbm93biBieSB0aGUgQ1BFIHdpbGwgcGFzcyByaWdodCB0aHJvdWdoIGl0
IHRyYW5zcGFyZW50bHkuIFRoZSBvbmx5IGNvbXBsaWNhdGlvbiBpcyB3aGVuIHN0YXRlZnVsIERI
Q1B2NiBhZGRyZXNzaW5nIGlzIHVzZWQgb24gdGhlIENQRSBMQU4gaW50ZXJmYWNlLCBhbmQgSSBz
dWdnZXN0ZWQgYSBoeWJyaWQgbW9kZSBvZiBvcGVyYXRpb24gZm9yIGEgREhDUHY2IHNlcnZlciBp
biB0aGF0IGRyYWZ0IHdoaWNoIEkgdGhpbmsgc29sdmVzIHRoYXQgcHJvYmxlbS4NCg0KT3RoZXJz
LA0KDQpBbHNvLCB3aHkgZG9lcyBvbmUgbmVlZCBhbiBSQSBPcHRpb24gR3VpZGVsaW5lPyAgUkZD
NDg2MSBzcGVjaWZpZXMgYSBUTFYgZm9ybWF0IGFuZCBhbiBvcHRpb24gVHlwZS4gIEkgZG9uJ3Qg
c2VlIGFueXRoaW5nIGVsc2UgbmVlZGVkIGlmIEkgbmVlZCB0byBzcGVjaWZ5IGEgbmV3IFJBIG9w
dGlvbi4NCg0KVGhhbmtzLA0KDQpIZW1hbnQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IFNUQVJLLCBCQVJCQVJBIEggW21haWx0bzpiczc2NTJAYXR0LmNvbTxtYWlsdG86YnM3
NjUyQGF0dC5jb20+XQ0KU2VudDogVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgOToyNSBBTQ0KVG86
IEhlbWFudCBTaW5naCAoc2hlbWFudCk7IE1hcmsgWlpaIFNtaXRoOyBCcmlhbiBIYWJlcm1hbjsg
aXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBSQSBPcHRp
b24gR3VpZGVsaW5lcw0KDQoNCg0KDQpSRkMgNzA4NCBhbHJlYWR5IHNheXM6DQogIEwtMTI6ICBU
aGUgSVB2NiBDRSByb3V0ZXIgU0hPVUxEIG1ha2UgYXZhaWxhYmxlIGEgc3Vic2V0IG9mIERIQ1B2
Ng0KICAgICAgICAgIG9wdGlvbnMgKGFzIGxpc3RlZCBpbiBTZWN0aW9uIDUuMyBvZiBbUkZDMzcz
Nl0pIHJlY2VpdmVkIGZyb20NCiAgICAgICAgICB0aGUgREhDUHY2IGNsaWVudCBvbiBpdHMgV0FO
IGludGVyZmFjZSB0byBpdHMgTEFOLXNpZGUgREhDUHY2DQogICAgICAgICAgc2VydmVyLg0KDQo=

--_000_75B6FA9F576969419E42BECB86CB1B8916837EE3xmbrcdx06ciscoc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OkhlbHZldGljYTsNCglwYW5vc2UtMToyIDExIDYgNCAyIDIgMiAyIDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkhlbHZldGljYTsNCglwYW5vc2UtMToyIDEx
IDYgNCAyIDIgMiAyIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVm
aW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7
bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsN
Cglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCmE6bGluaywgc3Bhbi5N
c29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4
dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9s
bG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1z
b0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxs
b29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpz
cGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIi
Ow0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0
IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxl
MTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21z
by1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBp
biAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwv
c3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJl
ZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0i
ZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxk
aXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TWFyayw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoZSBzdGF0
ZWxlc3MgREhDUHY2IHNlcnZlciBpbiBSRkMzNzM2IGFsbG93cyBmb3IgbmV3IG9wdGlvbnMgdG8g
YmUgc2VydmVkIGJ5IHRoZSBzdGF0ZWxlc3Mgc2VydmVyLiZuYnNwOyZuYnNwOyBSZWFkIHRoZSBm
aXJzdCBwYXJhZ3JhcGggb2Ygc2VjdGlvbiA1LjMgaW4gUkZDMzczNi4mbmJzcDsgU28NCiB0aGUg
bmV3IG9wdGlvbnMgeW91IHdhbnQgdG8gc2VydmUgY2FuIGJlIHNlcnZlZCBieSB0aGUgQ0Ugc3Rh
dGVsZXNzIERIQ1B2NiBzZXJ2ZXIuJm5ic3A7ICZuYnNwO05vdywgaWYgdGhlIHNlcnZpY2UgcHJv
dmlkZXIgY29uZmlndXJlcyBoaXMvaGVyIERIQ1B2NiBzZXJ2ZXIgdG8gcmV0dXJuIG5ldyBvcHRp
b25zIHRvIHRoZSBDRSBXQU4gaW50ZXJmYWNlIGFkZHJlc3MgYWNxdWlzaXRpb24sIHRoZSBDRSB1
c2VzIHRoZSBvcHRpb25zIG9uIHRoZSBMQU4uJm5ic3A7IFNlZSBidWxsZXQNCiBMLTEyIG9mIFJG
QyA3MDg0LiZuYnNwOyBFeGlzdGluZyBSRkNzIHN1cHBvcnQgeW91ciB1c2UgY2FzZSBhbmQgbm8g
ZGhjcHY2IHJlbGF5IGlzIHJlcXVpcmVkIGluIHRoZSBDRS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkJhcmJhcmEsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj5Gb3IgeW91ciB1c2UgY2FzZSwgdGhlIHNlcnZpY2UgcHJvdmlkZXIgY29uZmlndXJl
cyB0aGUgREhDUHY2IHNlcnZlciB0byBvbmx5IHNlcnZlIG9wdGlvbnMgc3BlY2lmaWVkIGluIFJG
QyA3MDg0LiZuYnNwOyBUaHVzIGluIHRoaXMgZGVwbG95bWVudCBubyBleHRyYSBvcHRpb25zDQog
ZXhpc3QgdG8gc2VydmUgdG8gdGhlIENFIHJvdXRlciBMQU4uPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPiZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkJvdGggdXNl
IGNhc2VzIGNhbiBiZSBzdXBwb3J0ZWQgdXNpbmcgZXhpc3RpbmcgUkZD4oCZcy48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PkhlbWFudDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xp
ZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IE1hcmsgWlpaIFNtaXRoIFttYWlsdG86bWFya3p6
enNtaXRoQHlhaG9vLmNvbS5hdV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXJjaCAz
MSwgMjAxNSA5OjUyIFBNPGJyPg0KPGI+VG86PC9iPiBIZW1hbnQgU2luZ2ggKHNoZW1hbnQpOyBT
VEFSSywgQkFSQkFSQSBIOyBCcmlhbiBIYWJlcm1hbjsgaXB2NkBpZXRmLm9yZzxicj4NCjxiPlN1
YmplY3Q6PC9iPiBSZTogUkEgT3B0aW9uIEd1aWRlbGluZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYxOTNfMzcyOSI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOmJsYWNrIj5IaSBIZW1hbnQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IGlkPSJ5dWlf
M18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzIwIj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI3
ODQ5MjQ2MTkzXzM3MTkiPg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYxOTNfMzcy
OCI+DQo8ZGl2IGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0LWFs
aWduOmNlbnRlcjtiYWNrZ3JvdW5kOndoaXRlIj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+
DQo8aHIgc2l6ZT0iMSIgd2lkdGg9IjEwMCUiIGFsaWduPSJjZW50ZXIiPg0KPC9zcGFuPjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPkZyb206PC9zcGFuPjwvYj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4gSGVtYW50IFNpbmdoIChzaGVtYW50KSAm
bHQ7PGEgaHJlZj0ibWFpbHRvOnNoZW1hbnRAY2lzY28uY29tIj5zaGVtYW50QGNpc2NvLmNvbTwv
YT4mZ3Q7PGJyPg0KPGI+VG86PC9iPiAmcXVvdDtTVEFSSywgQkFSQkFSQSBIJnF1b3Q7ICZsdDs8
YSBocmVmPSJtYWlsdG86YnM3NjUyQGF0dC5jb20iPmJzNzY1MkBhdHQuY29tPC9hPiZndDs7IE1h
cmsgWlpaIFNtaXRoICZsdDs8YSBocmVmPSJtYWlsdG86bWFya3p6enNtaXRoQHlhaG9vLmNvbS5h
dSI+bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdTwvYT4mZ3Q7OyBCcmlhbiBIYWJlcm1hbiAmbHQ7
PGEgaHJlZj0ibWFpbHRvOmJyaWFuQGlubm92YXRpb25zbGFiLm5ldCI+YnJpYW5AaW5ub3ZhdGlv
bnNsYWIubmV0PC9hPiZndDs7DQogJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmci
PmlwdjZAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9y
ZyI+aXB2NkBpZXRmLm9yZzwvYT4mZ3Q7DQo8YnI+DQo8Yj5TZW50OjwvYj4gV2VkbmVzZGF5LCAx
IEFwcmlsIDIwMTUsIDE6Mjc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6IFJBIE9wdGlvbiBHdWlk
ZWxpbmVzPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6YmxhY2siPjxicj4NCkJhcmJhcmEsPGJyPg0KPGJyPg0KVGhhbmtzIGZvciByZXBs
eWluZy4mbmJzcDsgJm5ic3A7IDxicj4NCjxicj4NCk1hcmssPGJyPg0KPGJyPg0KSWYgbmV3IERI
Q1B2NiBvcHRpb25zIGFyZSBhZGRlZCB0byBiZSBzdXBwb3J0ZWQgYnkgUkZDMzczNiwgdGhlbiB0
aGUgU1AgaW5jbHVkZXMgdGhlIG5ldyBvcHRpb24gaW4gdGhlIERIQ1B2NiByZXNwb25zZXMgdG8g
dGhlIENQRSBXQU4uJm5ic3A7IFRoZW4gdGhlIENQRSBpbmNsdWRlcyB0aGUgbmV3IG9wdGlvbiB0
byBpdHMgTEFOIERIQ1B2NiBjbGllbnRzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2
XzBfMV8xNDI3ODQ5MjQ2MTkzXzM3MTgiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJh
Y2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Em
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+LyAmbmJzcDtTbyBoZXJl
IGlzIGEgc2NlbmFyaW8uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5
dWlfM18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4
NDkyNDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3
aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4vIEFzIGFuIElTUCwgbXkgY3VzdG9tZXJz
IGhhdmUgVm9JUCBoYW5kc2V0cyB0aGF0IG1pZ2h0IHN1cHBvcnQgdGhlJm5ic3A7T1BUSU9OX0dF
T0xPQ0FUSU9OIERIQ1B2NiBvcHRpb24gKEkgbWlnaHQga25vdyB0aGF0IGEgcG9ydGlvbiBvZiB0
aGVtIGRvLCBiZWNhdXNlDQogdGhleSd2ZSBib3VnaHQgdGhvc2UgVm9JUCBoYW5kc2V0cyBmcm9t
IG1lKS4gSG93IGxvbmcgaXMgaXQgZ29pbmcgdG8gdGFrZSBmb3IgbWUgdG8gZ2V0IHRoYXQgb3B0
aW9uIGFkZGVkIHRvIGFuIHVwZGF0ZWQgUkZDMzczNiBhbmQgUkZDNzA4NCwgdG8gZ2V0IG15IENQ
RSB2ZW5kb3IgdG8gdXBkYXRlIGFuZCByZWxlYXNlIHRoZWlyIGZpcm13YXJlIHRvIHN1cHBvcnQg
dGhhdCBvcHRpb24sIGFuZCB0ZXN0IHRoYXQgbmV3IENQRSBmaXJtd2FyZSBhbmQNCiB0aGVuIHRv
IGRlcGxveSB0aGF0IG5ldyBmaXJtd2FyZT88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI3ODQ5MjQ2MTkzXzM3MTgiPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFj
ayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18x
Nl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPi8gSSB0aGluayBJJ2Qg
YmUgbHVja3kgaWYgaXQgb25seSB0b29rIDIgeWVhcnMuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0i
eXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hl
bHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4vIEEgZmV3
IG1vbnRocyBsYXRlciBJIGRlY2lkZSBJIHdhbnQgdG8gcHJvdmlkZSZuYnNwO09QVElPTl9ORVdf
UE9TSVhfVElNRVpPTkUgdG8gbXkgY3VzdG9tZXJzIGlmIHRoZWlyIGhvc3RzIHJlcXVlc3QgaXQu
IFNvIG5vdyBJIGhhdmUgdG8gdHJ5IHRvIGdldCBPUFRJT05fTkVXX1BPU0lYX1RJTUVaT05FDQog
YWRkZWQgdG8gdGhlIHVwZGF0ZWQmbmJzcDtSRkMzNzM2LCB0byBnZXQgbXkgQ1BFIHZlbmRvciB0
byB1cGRhdGUgYW5kIHJlbGVhc2UgdGhlaXIgZmlybXdhcmUgdG8gc3VwcG9ydCB0aGF0IG9wdGlv
biwgYW5kIHRlc3QgdGhhdCBuZXcgQ1BFIGZpcm13YXJlIGFuZCB0aGVuIHRvIGRlcGxveSB0aGF0
IG5ldyBmaXJtd2FyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1
aV8zXzE2XzBfMV8xNDI3ODQ5MjQ2MTkzXzM3MTgiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2
ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyNzg0
OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndo
aXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPi8gTm93IGlmIEknbSBsdWNreSBJIGNvdWxk
IGFkZCBpdCB0byB0aGUgZHJhZnQgZm9yJm5ic3A7T1BUSU9OX0dFT0xPQ0FUSU9OLCBzbyBpdCBp
cyBzdGlsbCAmcXVvdDtvbmx5JnF1b3Q7IDIgeWVhcnMgdG8gZ2V0IHRvIGEgcG9pbnQgd2hlcmUg
SSBjb3VsZCBwcm92aWRlIHRob3NlIG9wdGlvbnMNCiB0byBteSBjdXN0b21lcnMuIEJ1dCB3aGF0
IGlmIHRoYXQgZHJhZnQgaGFzIHByb2dyZXNzZWQgdG9vIGZhciB0aG91Z2ggdGhlIElFVEYgcHVi
bGlzaGluZyBwcm9jZXNzPyBJIGhhdmUgdG8gY3JlYXRlIGEgbmV3IGRyYWZ0IHVwZGF0aW5nIHRo
ZSB0byBiZSBwdWJsaXNoZWQgZHJhZnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZf
MF8xXzE0Mjc4NDkyNDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFj
a2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4vIFNvLCB0byBhY2hpZXZl
IHdoYXQgc2hvdWxkIGJlIGEgc2ltcGxlIHRhc2sgb2YgcHJvdmlkaW5nIGxvY2F0aW9uIG9yIHRp
bWV6b25lIGluZm9ybWF0aW9uIHRvIGN1c3RvbWVycycgZW5kIGhvc3RzIGlmIHRoZXkgd2FudCBp
dCwgd2UndmUganVzdCBpbmN1cnJlZA0KIHRoZSBtYXNzaXZlIGNvc3RzIGFuZCB0aW1lIGRlbGF5
cyBvZiB0aGUgSUVURiBwdWJsaXNoaW5nIHByb2Nlc3MsIHZlbmRvciBmaXJtd2FyZSB1cGdyYWRl
cywgZmlybXdhcmUgdGVzdGluZyBhbmQgZmlybXdhcmUgZGVwbG95bWVudC4gU291bmRzIGxpa2Ug
aG93IGhhcmQgSSB1bmRlcnN0YW5kIGl0IHdhcyB0byByb2xsIG91dCBmZWF0dXJlcyBsaWtlIENM
SSBpbiBQU1ROIG5ldHdvcmtzIC4uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
diBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBf
MV8xNDI3ODQ5MjQ2MTkzXzM3MTgiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7V2hhdCBpcyBvbmUg
b3B0aW9uIHlvdSdkIGxpa2UgdGhlIGhvc3Qgb24gdGhlIExBTiB0byBpbmNsdWRlIHNvIHRoYXQg
d2UgY2FuIHVuZGVyc3RhbmQgeW91ciB1c2UgY2FzZSBiZXR0ZXI/ICZuYnNwOzxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYxOTNf
MzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48YnI+DQovIEknbSBnb2luZyB0byBtYWtlIHRoZSBwcm9i
bGVtIG11Y2ggaGFyZGVyIGZvciB5b3UuIEkgd2FudCB0aGUgQ1BFIHRvICZxdW90O3N1cHBvcnQm
cXVvdDsgb3IgYmV0dGVyLCBiZSB0cmFuc3BhcmVudCB0bywgYWxsIGN1cnJlbnQgYW5kIGZ1dHVy
ZSBESENQdjYgb3B0aW9ucywgYW5kIEkgZG9uJ3Qgd2FudCB0byBoYXZlIHRvIHVwZ3JhZGUgb3Ig
YXNrIG15IGN1c3RvbWVycyB0byBzdWNjZXNzZnVsbHkgdXBncmFkZSB0aGVpciBDUEUgZWFjaCBh
bmQgZXZlcnkgdGltZQ0KIHRoZXJlIGlzIGEgbmV3IERIQ1B2NiBvcHRpb24gZGVmaW5lZCB0aGF0
IG1pZ2h0IGJlIHVzZWZ1bCB0byBtZSBhbmQgdGhlbS4gSSB3YW50IHRvIGJlIGFibGUgdG8gcHJv
dmlkZSBzZXJ2aWNlIHBhcmFtZXRlcnMgdG8gbXkgY3VzdG9tZXJzIGhvc3RzLCBkaXJlY3RseSBv
ciBpbmRpcmVjdGx5LCB3aXRob3V0IHRoZSBzb2Z0d2FyZSByZXZpc2lvbiBvciBtb2RlbCBvZiB0
aGVpciBDUEUgYmVpbmcgdGhlIGNvbnN0cmFpbnQuPGJyPg0KPGJyPg0KVGhlIFNJUCBzZXJ2ZXIg
aXMgYWxyZWFkeSBpbmNsdWRlZCBhcyBvbmUgb3B0aW9uIHN1cHBvcnRlZCBieSBSRkMzNzM2LiZu
YnNwOyBDZXJ0YWlubHksIGlmIHRoZSBTSVAgc2VydmVyIHN1cHBvcnQgaXMgbmVlZGVkIGluIHRo
ZSBSQSwgSSBhbSBvcGVuIGZvciBpdCBzaW5jZSB0aGUgUkEgYWxyZWFkeSBpbmNsdWRlcyBETlMg
aW5mb3JtYXRpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlf
M18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDky
NDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0
ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4vIEkgZG9uJ3QgdGhpbmsgRE5TIGluIFJBcyB3
YXMgYSBnb29kIGlkZWEsIGFuZCBuZWl0aGVyIHdlcmUgU0lQIG9wdGlvbnMgd2hlbiB0aGV5IHdl
cmUgcHJvcG9zZWQuIFNlZSB0aGF0IHRpbWUgY29uc3VtaW5nIGFuZCBzZXJ2aWNlIGRpc3J1cHRp
bmcgZmlybXdhcmUNCiB1cGdyYWRlIGN5Y2xlIGZvciBuZXcgREhDUHY2IG9wdGlvbnM/IFNhbWUg
cHJvYmxlbSBpZiB5b3UgdXNlIFJBIG9wdGlvbnMgdG8gYWNoaWV2ZSB0aGUgc2FtZSBnb2FsLiBO
ZXcgZmlybXdhcmUgdXBncmFkZSBlYWNoIHRpbWUgeW91IHdhbnQgdG8gc3VwcG9ydCBhIG5ldyBS
QSBvcHRpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18x
Nl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJi
YWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDkyNDYx
OTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4vIER1cGxpY2F0aW9uIGJldHdlZW4gUkEgb3B0aW9u
cyBhbmQgREhDUHY2IG9wdGlvbnMgYWxzbyBjYXVzZXMgbW9yZSBwcm9ibGVtcy4gV2hpY2ggaXMg
cHJlZmVycmVkPyBBcmUgdGhleSB0cmVhdGVkIGVxdWFsbHkgb3IgZG9lcyBvbmUgdGFrZSBwcmVj
ZWRlbmNlDQogb3ZlciB0aGUgb3RoZXI/IEFzIGZhciBhcyBJJ20gYXdhcmUsIHRoZXNlIHF1ZXN0
aW9ucyBoYXZlbid0IGJlZW4gYW5zd2VyZWQgZm9yIHRoZSBESENQdjYgRE5TIGFuZCBSQSBETlMg
b3B0aW9ucyB5ZXQuIEl0IG1pZ2h0IGJlIHNpbXBsZSB0byBjb21lIHVwIHdpdGggYSBzaW1wbGUg
cnVsZSBmb3IgbW9yZSBESENQdjYgb3B0aW9ucyBhcmUgZHVwbGljYXRlZCBpbnRvIFJBcywgaG93
ZXZlciB0aGVpciBtaWdodCBiZSBzb21lIHNwZWNpZmljIGNhc2VzDQogd2hlcmUgdGhlIFJBIG9w
dGlvbiB2YWx1ZSBzaG91bGQgYmUgcHJlZmVycmVkIG92ZXIgdGhlIERIQ1B2NiBlcXVpdmFsZW50
IG9wdGlvbiBhbmQgdmljZS12ZXJzYS4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI3ODQ5MjQ2MTkzXzM3MTgiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlf
M18xNl8wXzFfMTQyNzg0OTI0NjE5M18zNzE4Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPkhvd2V2ZXIsIEkg
c3RpbGwgYXNrIHRoZSBxdWVzdGlvbiBhcyB0byBob3cgYW4gUkEgcmVjZWl2ZWQgYXQgdGhlIFdB
TiBvZiB0aGUgQ1BFIGhhcyBpdHMgb3B0aW9ucyBwcm9wYWdhdGVkIHRvIHRoZSBSQSBvbiB0aGUg
TEFOPyZuYnNwOyBBdCB0aGUgdGltZSBvZiB3cml0aW5nDQogUkZDIDYyMDQgb3IgUkZDIDcwODQs
IHRoZXJlIGlzIG5vIHN1Y2ggcHJvdmlzaW9uIGJldHdlZW4gdGhlIFJBIHJlY2VpdmVkIG9uIHRo
ZSBXQU4gYW5kIHRoZSBSQSBpc3N1ZWQgb24gdGhlIExBTiBvZiB0aGUgQ0Ugcm91dGVyLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0Mjc4NDky
NDYxOTNfMzcxOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0
ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI3ODQ5MjQ2MTkzXzM3MTgiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjpibGFjayI+LyBVc2UgYSBESENQdjYgcmVsYXkgaW4gdGhlIENQRS4gVGhlbiB0aGVyZSBp
c24ndCBhIHByb2JsZW0sIG5ldyBESENQdjYgb3B0aW9ucyB0aGF0IGFyZSB1bmtub3duIGJ5IHRo
ZSBDUEUgd2lsbCBwYXNzIHJpZ2h0IHRocm91Z2ggaXQgdHJhbnNwYXJlbnRseS4NCiBUaGUgb25s
eSBjb21wbGljYXRpb24gaXMgd2hlbiBzdGF0ZWZ1bCBESENQdjYgYWRkcmVzc2luZyBpcyB1c2Vk
IG9uIHRoZSBDUEUgTEFOIGludGVyZmFjZSwgYW5kIEkgc3VnZ2VzdGVkIGEgaHlicmlkIG1vZGUg
b2Ygb3BlcmF0aW9uIGZvciBhIERIQ1B2NiBzZXJ2ZXIgaW4gdGhhdCBkcmFmdCB3aGljaCBJIHRo
aW5rIHNvbHZlcyB0aGF0IHByb2JsZW0uPGJyPg0KPGJyPg0KT3RoZXJzLDxicj4NCjxicj4NCkFs
c28sIHdoeSBkb2VzIG9uZSBuZWVkIGFuIFJBIE9wdGlvbiBHdWlkZWxpbmU/Jm5ic3A7IFJGQzQ4
NjEgc3BlY2lmaWVzIGEgVExWIGZvcm1hdCBhbmQgYW4gb3B0aW9uIFR5cGUuJm5ic3A7IEkgZG9u
J3Qgc2VlIGFueXRoaW5nIGVsc2UgbmVlZGVkIGlmIEkgbmVlZCB0byBzcGVjaWZ5IGEgbmV3IFJB
IG9wdGlvbi4NCjxicj4NCjxicj4NClRoYW5rcyw8YnI+DQo8YnI+DQpIZW1hbnQ8YnI+DQo8YnI+
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFNUQVJLLCBCQVJCQVJBIEgg
W21haWx0bzo8YSBocmVmPSJtYWlsdG86YnM3NjUyQGF0dC5jb20iPmJzNzY1MkBhdHQuY29tPC9h
Pl0NCjxicj4NClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDk6MjUgQU08YnI+DQpUbzog
SGVtYW50IFNpbmdoIChzaGVtYW50KTsgTWFyayBaWlogU21pdGg7IEJyaWFuIEhhYmVybWFuOyA8
YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+DQppcHY2QGlldGYub3JnPC9hPjxicj4NClN1
YmplY3Q6IFJFOiBSQSBPcHRpb24gR3VpZGVsaW5lczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQ7YmFj
a2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9InlxdGZkODY0NDciPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFj
ayI+PGJyPg0KPGJyPg0KPGJyPg0KUkZDIDcwODQgYWxyZWFkeSBzYXlzOiA8YnI+DQombmJzcDsg
TC0xMjombmJzcDsgVGhlIElQdjYgQ0Ugcm91dGVyIFNIT1VMRCBtYWtlIGF2YWlsYWJsZSBhIHN1
YnNldCBvZiBESENQdjY8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG9w
dGlvbnMgKGFzIGxpc3RlZCBpbiBTZWN0aW9uIDUuMyBvZiBbUkZDMzczNl0pIHJlY2VpdmVkIGZy
b208YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHRoZSBESENQdjYgY2xp
ZW50IG9uIGl0cyBXQU4gaW50ZXJmYWNlIHRvIGl0cyBMQU4tc2lkZSBESENQdjY8YnI+DQombmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlcnZlci48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEy
LjBwdDtiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_75B6FA9F576969419E42BECB86CB1B8916837EE3xmbrcdx06ciscoc_--


From nobody Thu Apr  2 12:39:19 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3C51A0103; Thu,  2 Apr 2015 12:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3RIPn4zWY33; Thu,  2 Apr 2015 12:39:15 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0705.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::705]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 934A61A00FD; Thu,  2 Apr 2015 12:39:14 -0700 (PDT)
Received: from BLUPR05MB433.namprd05.prod.outlook.com (10.141.27.140) by BLUPR05MB435.namprd05.prod.outlook.com (10.141.27.150) with Microsoft SMTP Server (TLS) id 15.1.130.23; Thu, 2 Apr 2015 19:38:52 +0000
Received: from BLUPR05MB433.namprd05.prod.outlook.com ([169.254.6.195]) by BLUPR05MB433.namprd05.prod.outlook.com ([169.254.6.195]) with mapi id 15.01.0125.002; Thu, 2 Apr 2015 19:38:52 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Lucy yong <lucy.yong@huawei.com>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYAAC3xTgAFhv1xA=
Date: Thu, 2 Apr 2015 19:38:52 +0000
Message-ID: <BLUPR05MB433CD2BDA87CC868451C6B7AEF20@BLUPR05MB433.namprd05.prod.outlook.com>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.18]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB435;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(99286002)(19625215002)(33656002)(230783001)(16236675004)(2201001)(93886004)(87936001)(46102003)(2656002)(76576001)(74316001)(19300405004)(2501003)(2950100001)(66066001)(62966003)(122556002)(77156002)(2900100001)(15975445007)(92566002)(102836002)(50986999)(86362001)(76176999)(54356999)(19580395003)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB435; H:BLUPR05MB433.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR05MB4355AF9A78CE16BC14BBD85AEF20@BLUPR05MB435.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR05MB435; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB435; 
x-forefront-prvs: 0534947130
Content-Type: multipart/alternative; boundary="_000_BLUPR05MB433CD2BDA87CC868451C6B7AEF20BLUPR05MB433namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2015 19:38:52.3860 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB435
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EJjgeATbdq6p7ith8XaJ6Pfk4Ww>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 19:39:17 -0000

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

THVjeSwgVG9tLCBTdGV3YXJkLA0KDQpJIGFncmVlIHdpdGggd2hhdCB5b3UgYXJlIHNheWluZyBh
bmQgaGF2ZSB0cmllZCB0byBjcmFmdCBzb21lIHRleHQgdGhhdCBhZGRyZXNzZXMgYWxsIG9mIHlv
dXIgY29tbWVudHMuIFBsZWFzZSB0ZWxsIG1lIGlmIHRoZSBmb2xsb3dpbmcgdGV4dCBkb2VzIHRo
ZSB0cmljay4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSb24NCg0K
T0xEPg0KICAgQXMgc3RhdGVkIGluIFtSRkMyNzg0XSwgdGhlIENoZWNrc3VtIGZpZWxkIGNvbnRh
aW5zIHRoZSBJUCAob25lJ3MNCiAgIGNvbXBsZW1lbnQpIGNoZWNrc3VtIHN1bSBvZiB0aGUgYWxs
IHRoZSAxNiBiaXQgd29yZHMgaW4gdGhlIEdSRQ0KICAgaGVhZGVyIGFuZCB0aGUgcGF5bG9hZCBw
YWNrZXQuICBUaGVyZWZvcmUsIHRoZSBjaGVja3N1bSBkb2VzIG5vdA0KICAgZW5zdXJlIHRoZSBp
bnRlZ3JpdHkgb2YgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyLg0KDQogIEJlY2F1c2UgdGhlIElQ
djYgZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90IGluY2x1ZGUgYSBjaGVja3N1bSBvZiBpdHMNCiAg
IG93biwgaXQgaXMgc3ViamVjdCB0byBjb3JydXB0aW9uLiAgSG93ZXZlciwgZXZlbiBpZiB0aGUg
ZGVsaXZlcnkNCiAgIGhlYWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2VsaWhvb2Qgb2YgdGhhdCBj
b3JydXB0aW9uIHJlc3VsdGluZyBpbg0KICAgbWlzZGVsaXZlcnkgb2YgdGhlIHBheWxvYWQgaXMg
ZXh0cmVtZWx5IGxvdy4NCjxPTEQNCg0KTkVXPg0KICAgQXMgc3RhdGVkIGluIFtSRkMyNzg0XSwg
dGhlIEdSRSBoZWFkZXIgY2FuIGNvbnRhaW4gYSBjaGVja3N1bS4NCiAgIElmIHByZXNlbnQsIHRo
ZSBHUkUgaGVhZGVyIGNoZWNrc3VtIGNhbiBiZSB1c2VkIHRvIGRldGVjdA0KICAgY29ycnVwdGlv
biBvZiB0aGUgR1JFIGhlYWRlciBhbmQgR1JFIHBheWxvYWQuDQoNCiAgIFRoZSBHUkUgaGVhZGVy
IGNoZWNrc3VtIGNhbm5vdCBiZSB1c2VkIHRvIGRldGVjdCBjb3JydXB0aW9uDQogICAgb2YgdGhl
IElQdjYgZGVsaXZlcnkgaGVhZGVyLiBGdXJ0aGVybW9yZSwgdGhlIElQdjYgZGVsaXZlcnkgaGVh
ZGVyDQogICBkb2VzIG5vdCBjb250YWluICBhIGNoZWNrc3VtIG9yIGl0cyBvd24uIFRoZXJlZm9y
ZSwgbm8gY2hlY2tzdW0NCiAgIGNhbiBiZSB1c2VkIHRvIGRldGVjdCBjb3JydXB0aW9uIG9mIHRo
ZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci4NCg0KICAgSW4gb25lIGZhaWx1cmUgc2NlbmFyaW8sIHRo
ZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBJUHY2IGRlbGl2ZXJ5DQogICBoZWFkZXIgaXMg
Y29ycnVwdGVkLiBBcyBhIHJlc3VsdCwgdGhlIElQdjYgZGVsaXZlcnkgcGFja2V0IGlzIGRlbGl2
ZXJlZA0KICAgdG8gIGEgbm9kZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCBHUkUgZWdyZXNzIG5v
ZGUuIERlcGVuZGluZyB1cG9uDQogICB0aGUgc3RhdGUgYW5kIGNvbmZpZ3VyYXRpb24gb2YgdGhh
dCBub2RlLCBpdCB3aWxsIGVpdGhlcjoNCg0KDQphKSAgICAgIERyb3AgdGhlIHBhY2tldA0KDQpi
KSAgICAgIERlLWVuY2Fwc3VsYXRlIHRoZSBwYXlsb2FkIGFuZCBmb3J3YXJkIGl0IHRvIGl0cyBp
bnRlbmRlZCBkZXN0aW5hdGlvbg0KDQpjKSAgICAgICBEZS1lbmNhcHN1bGF0ZSB0aGUgcGF5bG9h
ZCBhbmQgZm9yd2FyZCBpdCB0byBhIG5vZGUgb3RoZXIgdGhhbiBpdHMgaW50ZW5kZWQgZGVzdGlu
YXRpb24uIEZvciBleGFtcGxlLCB0aGUgcGF5bG9hZCBtaWdodCBiZSBpbnRlbmRlZCBmb3IgYSBu
b2RlIG9uIG9uZSBWUE4sIGJ1dCBkZWxpdmVyZWQgdG8gYW4gaWRlbnRpY2FsbHkgbnVtYmVyZWQg
bm9kZSBpbiBhbm90aGVyIFZQTi4NCg0KDQpCZWhhdmlvcnMgYSkgYW5kIGIpIGFyZSBhY2NlcHRh
YmxlLiBCZWhhdmlvciBjKSBpcyBub3QgYWNjZXB0YWJsZS4NCg0KQmVmb3JlIGRlcGxveWluZyBH
UkUgb3ZlciBJUHY2LCBuZXR3b3JrIG9wZXJhdG9ycyBzaG91bGQgY29uc2lkZXIgdGhlDQpsaWtl
bGlob29kIG9mIGJlaGF2aW9yIGMpIGluIHRoZWlyIG5ldHdvcmsuIE5ldHdvcmsgb3BlcmF0b3Jz
IHNob3VsZCBkZXBsb3kNCkdSRSBvdmVyIElQdjYgaWYgdGhleSBjYW4gdG9sZXJhdGUgdGhlIHJp
c2sgYXNzb2NpYXRlZCB3aXRoIGJlaGF2aW9yIGMpLg0KDQo8TkVXDQoNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoNCg0KDQoNCg==

--_000_BLUPR05MB433CD2BDA87CC868451C6B7AEF20BLUPR05MB433namprd_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0K
CXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29QbGFpblRleHQsIGRp
di5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5r
OiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
fQ0KcA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJn
aW4tbGVmdDowaW47DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIixzZXJpZjt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHls
ZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OkNvbnNvbGFz
O30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJ
bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjguMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUYWhvbWEiLHNhbnMtc2VyaWY7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBs
aS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJp
b3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowaW47DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltYXJnaW4t
Ym90dG9tOjBpbjsNCgltYXJnaW4tbGVmdDouNWluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsN
Cglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30N
CnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9y
bWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi
SFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnNwYW4uUGxhaW5U
ZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uQmFsbG9vblRleHRDaGFyDQoJe21zby1zdHls
ZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLHNhbnMt
c2VyaWY7fQ0KcC5pbXByaW50dW5pcXVlaWQsIGxpLmltcHJpbnR1bmlxdWVpZCwgZGl2LmltcHJp
bnR1bmlxdWVpZA0KCXttc28tc3R5bGUtbmFtZTppbXByaW50dW5pcXVlaWQ7DQoJbXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZv
bnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0K
c3Bhbi5FbWFpbFN0eWxlMjYNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWls
U3R5bGUyNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTI4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
Ow0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjkNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFG
NDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUzMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4u
RW1haWxTdHlsZTMxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzIN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsN
Cgljb2xvcjpibGFjazsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7
DQoJdGV4dC1kZWNvcmF0aW9uOm5vbmUgbm9uZTt9DQpzcGFuLkVtYWlsU3R5bGUzMw0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsN
Cgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTM0DQoJe21zby1zdHlsZS10eXBlOnBl
cnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5
N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzUNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVt
YWlsU3R5bGUzNg0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTM3DQoJ
e21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlv
bjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGlu
O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZp
bml0aW9ucyAqLw0KQGxpc3QgbDANCgl7bXNvLWxpc3QtaWQ6Mjc0NTU2MjA5Ow0KCW1zby1saXN0
LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczotMTIzOTE0MDM1OCAtMTE3NzYz
MTQyNCA2NzY5ODcxMyA2NzY5ODcxNSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcxNSA2NzY5ODcw
MyA2NzY5ODcxMyA2NzY5ODcxNTt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRleHQ6IiUxXCkiOw0KCW1zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJn
aW4tbGVmdDouNzVpbjsNCgl0ZXh0LWluZGVudDotLjI1aW47fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDox
LjI1aW47DQoJdGV4dC1pbmRlbnQ6LS4yNWluO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0Ow0KCW1hcmdpbi1sZWZ0OjEuNzVpbjsN
Cgl0ZXh0LWluZGVudDotOS4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVm
dDoyLjI1aW47DQoJdGV4dC1pbmRlbnQ6LS4yNWluO30NCkBsaXN0IGwwOmxldmVsNQ0KCXttc28t
bGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBoYS1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6Mi43NWlu
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6cm9tYW4tbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpyaWdodDsNCgltYXJnaW4tbGVmdDozLjI1aW47DQoJdGV4
dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2ZWwtdGFiLXN0b3A6
bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6My43
NWluOw0KCXRleHQtaW5kZW50Oi0uMjVpbjt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjQuMjVpbjsNCgl0
ZXh0LWluZGVudDotLjI1aW47fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246cmlnaHQ7DQoJbWFyZ2luLWxlZnQ6NC43NWluOw0KCXRleHQtaW5k
ZW50Oi05LjBwdDt9DQpAbGlzdCBsMQ0KCXttc28tbGlzdC1pZDozMzYwMDgwMzc7DQoJbXNvLWxp
c3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjk5OTMyODAwNiAtNTMwNzA4
MDQ2IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5
IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwxOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6
bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4y
NWluOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWZv
bnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21h
biI7fQ0KQGxpc3QgbDE6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1p
bHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMTpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6
bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4y
NWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMTpsZXZlbDQNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDUN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBs
aXN0IGwxOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxl
dmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2lu
Z2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxs
ZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9u
dC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDE6bGV2ZWw5DQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxl
dmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRl
eHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDINCgl7
bXNvLWxpc3QtaWQ6NTgwNzk0MDY0Ow0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0
LXRlbXBsYXRlLWlkczotMjEzMDc3MzU5NCAxMDU3OTg2MTQgNjc2OTg2OTEgNjc2OTg2OTMgNjc2
OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxp
c3QgbDI6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28t
YmlkaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQpAbGlzdCBsMjpsZXZlbDINCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNv
LWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0
IGwyOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVs
LXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2Rp
bmdzO30NCkBsaXN0IGwyOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7
DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1m
YW1pbHk6U3ltYm9sO30NCkBsaXN0IGwyOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDI6bGV2ZWw2DQoJe21zby1sZXZl
bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVs
LXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQt
aW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDI6bGV2ZWw3
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3Qg
bDI6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwt
dGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3Ijt9DQpAbGlzdCBsMjpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQt
ZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJn
aW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iIzA1
NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5MdWN5LCBUb20sIFN0
ZXdhcmQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5JIGFncmVlIHdpdGgg
d2hhdCB5b3UgYXJlIHNheWluZyBhbmQgaGF2ZSB0cmllZCB0byBjcmFmdCBzb21lIHRleHQgdGhh
dCBhZGRyZXNzZXMgYWxsIG9mIHlvdXIgY29tbWVudHMuIFBsZWFzZSB0ZWxsIG1lIGlmIHRoZSBm
b2xsb3dpbmcgdGV4dCBkb2VzIHRoZSB0cmljay48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBSb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPk9MRCZndDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IEFzIHN0YXRlZCBpbiBbUkZDMjc4NF0sIHRoZSBDaGVj
a3N1bSBmaWVsZCBjb250YWlucyB0aGUgSVAgKG9uZSdzPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZu
YnNwOyBjb21wbGVtZW50KSBjaGVja3N1bSBzdW0gb2YgdGhlIGFsbCB0aGUgMTYgYml0IHdvcmRz
IGluIHRoZSBHUkU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IGhlYWRlciBhbmQgdGhlIHBh
eWxvYWQgcGFja2V0LiZuYnNwOyBUaGVyZWZvcmUsIHRoZSBjaGVja3N1bSBkb2VzIG5vdDxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgZW5zdXJlIHRoZSBpbnRlZ3JpdHkgb2YgdGhlIElQdjYg
ZGVsaXZlcnkgaGVhZGVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5i
c3A7Jm5ic3A7QmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIgZG9lcyBub3QgaW5jbHVk
ZSBhIGNoZWNrc3VtIG9mIGl0czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgb3duLCBpdCBp
cyBzdWJqZWN0IHRvIGNvcnJ1cHRpb24uJm5ic3A7IEhvd2V2ZXIsIGV2ZW4gaWYgdGhlIGRlbGl2
ZXJ5PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBoZWFkZXIgaXMgY29ycnVwdGVkLCB0byBs
aWtlbGlob29kIG9mIHRoYXQgY29ycnVwdGlvbiByZXN1bHRpbmcgaW48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
Jm5ic3A7Jm5ic3A7IG1pc2RlbGl2ZXJ5IG9mIHRoZSBwYXlsb2FkIGlzIGV4dHJlbWVseSBsb3cu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPiZsdDtPTEQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPk5FVyZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IEFzIHN0YXRlZCBpbiBbUkZD
Mjc4NF0sIHRoZSBHUkUgaGVhZGVyIGNhbiBjb250YWluIGEgY2hlY2tzdW0uPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPiZuYnNwOyZuYnNwOyBJZiBwcmVzZW50LCB0aGUgR1JFIGhlYWRlciBjaGVja3N1bSBjYW4g
YmUgdXNlZCB0byBkZXRlY3Q8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IGNvcnJ1cHRpb24g
b2YgdGhlIEdSRSBoZWFkZXIgYW5kIEdSRSBwYXlsb2FkLg0KPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgVGhlIEdSRSBoZWFkZXIgY2hlY2tzdW0gY2Fu
bm90IGJlIHVzZWQgdG8gZGV0ZWN0IGNvcnJ1cHRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7IG9mIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci4gRnVydGhlcm1vcmUsIHRoZSBJ
UHY2IGRlbGl2ZXJ5IGhlYWRlcg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwO2Rv
ZXMgbm90IGNvbnRhaW4gJm5ic3A7YSBjaGVja3N1bSBvciBpdHMgb3duLiBUaGVyZWZvcmUsIG5v
IGNoZWNrc3VtPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBjYW4gYmUgdXNlZCB0byBkZXRl
Y3QgY29ycnVwdGlvbiBvZiB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgSW4gb25lIGZhaWx1cmUgc2NlbmFy
aW8sIHRoZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBJUHY2IGRlbGl2ZXJ5DQo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7aGVhZGVyIGlzIGNvcnJ1cHRlZC4gQXMgYSByZXN1
bHQsIHRoZSBJUHY2IGRlbGl2ZXJ5IHBhY2tldCBpcyBkZWxpdmVyZWQ8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
Jm5ic3A7Jm5ic3A7IHRvICZuYnNwO2Egbm9kZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCBHUkUg
ZWdyZXNzIG5vZGUuIERlcGVuZGluZyB1cG9uDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7dGhlIHN0YXRlIGFuZCBjb25maWd1cmF0aW9uIG9mIHRoYXQgbm9kZSwgaXQgd2lsbCBl
aXRoZXI6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRl
bnQ6LS4yNWluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNd
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3Jl
Ij5hKTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtl
bmRpZl0+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRyb3AgdGhlIHBhY2tldDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2lu
LWxlZnQ6Ljc1aW47dGV4dC1pbmRlbnQ6LS4yNWluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj4N
CjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48c3BhbiBz
dHlsZT0ibXNvLWxpc3Q6SWdub3JlIj5iKTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3Nw
YW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRl
LWVuY2Fwc3VsYXRlIHRoZSBwYXlsb2FkIGFuZCBmb3J3YXJkIGl0IHRvIGl0cyBpbnRlbmRlZCBk
ZXN0aW5hdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdy
YXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRlbnQ6LS4yNWluO21zby1saXN0
OmwwIGxldmVsMSBsZm8xIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj5jKTxzcGFuIHN0eWxlPSJm
b250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRlLWVuY2Fwc3VsYXRlIHRoZSBwYXlsb2FkIGFuZCBmb3J3
YXJkIGl0IHRvIGEgbm9kZSBvdGhlciB0aGFuIGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbi4gRm9y
IGV4YW1wbGUsIHRoZSBwYXlsb2FkIG1pZ2h0IGJlIGludGVuZGVkIGZvciBhIG5vZGUgb24gb25l
IFZQTiwgYnV0IGRlbGl2ZXJlZCB0byBhbiBpZGVudGljYWxseSBudW1iZXJlZCBub2RlDQogaW4g
YW5vdGhlciBWUE4uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJh
Z3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDouNzVpbiI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5CZWhhdmlvcnMgYSkgYW5kIGIpIGFyZSBhY2NlcHRh
YmxlLiBCZWhhdmlvciBjKSBpcyBub3QgYWNjZXB0YWJsZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPkJlZm9yZSBkZXBsb3lpbmcgR1JFIG92ZXIgSVB2NiwgbmV0d29yayBv
cGVyYXRvcnMgc2hvdWxkIGNvbnNpZGVyIHRoZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5saWtlbGlob29kIG9m
IGJlaGF2aW9yIGMpIGluIHRoZWlyIG5ldHdvcmsuIE5ldHdvcmsgb3BlcmF0b3JzIHNob3VsZCBk
ZXBsb3k8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+R1JFIG92ZXIgSVB2NiBpZiB0aGV5IGNhbiB0b2xlcmF0ZSB0
aGUgcmlzayBhc3NvY2lhdGVkIHdpdGggYmVoYXZpb3IgYykuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj4mbHQ7TkVXPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgUm9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBp
biAwaW4gNC4wcHQiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
Ymx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXYgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0
LjBwdCI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_BLUPR05MB433CD2BDA87CC868451C6B7AEF20BLUPR05MB433namprd_--


From nobody Thu Apr  2 13:29:10 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: expand-draft-ietf-6man-resilient-rs.all@virtual.ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id C3FB81A1A2C; Thu,  2 Apr 2015 11:59:07 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-6man-resilient-rs.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-6man-resilient-rs.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2641A0364; Thu,  2 Apr 2015 11:59:07 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Szp4duxfqfqe; Thu,  2 Apr 2015 11:59:02 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::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 5A5611A0687; Thu,  2 Apr 2015 11:59:02 -0700 (PDT)
Received: by pabsx10 with SMTP id sx10so856977pab.3; Thu, 02 Apr 2015 11:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=PIfcOixfGCSie9rV5U2cKwMSMqCGkH6WtUfXOxV+sec=; b=bMJnKDO/Ghxq8rJZuXET9m85wBRxcZyf0xq/r1vOubFmMvegE0C2B0ziq8X7YtheG1 XbtJHffqR/m9ZM0qCtOiXqVU1j3sdBa2hOtDtxXhUKLYyM04LlzkiEv8csaronud1i0I b2MpBnwHAFGkuNOMD0EQ1epP2UAB9OLOcDRxRK+FyQxPJrwi/iRZjtE9tgw4/L2uqXkT AnMviNw9zbv1R/aNH5tQDwj+qcERcHYF/6i/LRoMmpX/F3mpT9DmUPsgkFmQnt2cfYVW cN81doNMIintLTKkNUvVlgvkMPO3a4FK3/Uce6D5ixpf5AE5vdLYH3jyn1c3YHfbhPeO 2tCQ==
X-Received: by 10.68.229.233 with SMTP id st9mr90596586pbc.160.1428001142054;  Thu, 02 Apr 2015 11:59:02 -0700 (PDT)
Received: from ?IPv6:2406:e007:4dd0:1:28cc:dc4c:9703:6781? ([2406:e007:4dd0:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id pb2sm5963811pdb.33.2015.04.02.11.58.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2015 11:59:00 -0700 (PDT)
Message-ID: <551D917A.3040400@gmail.com>
Date: Fri, 03 Apr 2015 07:59:06 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: draft-ietf-6man-resilient-rs.all@ietf.org,  General Area Review Team <gen-art@ietf.org>
Subject: Gen-ART telechat review of draft-ietf-6man-resilient-rs-05
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xhwLVhvWJ_FVjjBnWtgI8AHwdRM>
X-Mailman-Approved-At: Thu, 02 Apr 2015 13:29:09 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 18:59:07 -0000

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

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-6man-resilient-rs-05.txt.txt
Reviewer: Brian Carpenter
Review Date: 2015-04-03
IETF LC End Date: 2015-02-16
IESG Telechat date: 2015-04-09

Summary: Ready
--------

Comment: Thanks for taking care of my Last Call comments
--------


From nobody Thu Apr  2 13:29:11 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE6D11A035F; Thu,  2 Apr 2015 13:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyqSG-Kyeew9; Thu,  2 Apr 2015 13:02:16 -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 AF18C1A033B; Thu,  2 Apr 2015 13:02:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQZ58339; Thu, 02 Apr 2015 20:02:12 +0000 (GMT)
Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Apr 2015 20:58:11 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Thu, 2 Apr 2015 12:58:07 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, "Black, David" <david.black@emc.com>,  "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>,  "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYAAC3xTgAFhv1xAACo9RgA==
Date: Thu, 2 Apr 2015 19:58:06 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57156796@dfweml701-chm>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm> <BLUPR05MB433CD2BDA87CC868451C6B7AEF20@BLUPR05MB433.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB433CD2BDA87CC868451C6B7AEF20@BLUPR05MB433.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.155.126]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57156796dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qkHltjoSskH06dvuL0USSTpyUdU>
X-Mailman-Approved-At: Thu, 02 Apr 2015 13:29:09 -0700
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 20:02:17 -0000

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

SGkgUm9uLA0KDQpHb29kIFRyeS4gU2VlIGlubGluZSBiZWxvdy4NCg0KRnJvbTogUm9uYWxkIEJv
bmljYSBbbWFpbHRvOnJib25pY2FAanVuaXBlci5uZXRdDQpTZW50OiBUaHVyc2RheSwgQXByaWwg
MDIsIDIwMTUgMjozOSBQTQ0KVG86IEx1Y3kgeW9uZzsgQmxhY2ssIERhdmlkOyBpbnQtYXJlYUBp
ZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzsgU3Rld2FydCBCcnlhbnQgKHN0YnJ5YW50KQ0KQ2M6IGRy
YWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NkB0b29scy5pZXRmLm9yZzsgaW50YXJlYS1jaGFpcnNA
aWV0Zi5vcmcNClN1YmplY3Q6IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFy
ZWEtZ3JlLWlwdjYNCg0KTHVjeSwgVG9tLCBTdGV3YXJkLA0KDQpJIGFncmVlIHdpdGggd2hhdCB5
b3UgYXJlIHNheWluZyBhbmQgaGF2ZSB0cmllZCB0byBjcmFmdCBzb21lIHRleHQgdGhhdCBhZGRy
ZXNzZXMgYWxsIG9mIHlvdXIgY29tbWVudHMuIFBsZWFzZSB0ZWxsIG1lIGlmIHRoZSBmb2xsb3dp
bmcgdGV4dCBkb2VzIHRoZSB0cmljay4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBSb24NCg0KT0xEPg0KICAgQXMgc3RhdGVkIGluIFtSRkMyNzg0XSwgdGhlIENoZWNr
c3VtIGZpZWxkIGNvbnRhaW5zIHRoZSBJUCAob25lJ3MNCiAgIGNvbXBsZW1lbnQpIGNoZWNrc3Vt
IHN1bSBvZiB0aGUgYWxsIHRoZSAxNiBiaXQgd29yZHMgaW4gdGhlIEdSRQ0KICAgaGVhZGVyIGFu
ZCB0aGUgcGF5bG9hZCBwYWNrZXQuICBUaGVyZWZvcmUsIHRoZSBjaGVja3N1bSBkb2VzIG5vdA0K
ICAgZW5zdXJlIHRoZSBpbnRlZ3JpdHkgb2YgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyLg0KDQog
IEJlY2F1c2UgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyIGRvZXMgbm90IGluY2x1ZGUgYSBjaGVj
a3N1bSBvZiBpdHMNCiAgIG93biwgaXQgaXMgc3ViamVjdCB0byBjb3JydXB0aW9uLiAgSG93ZXZl
ciwgZXZlbiBpZiB0aGUgZGVsaXZlcnkNCiAgIGhlYWRlciBpcyBjb3JydXB0ZWQsIHRvIGxpa2Vs
aWhvb2Qgb2YgdGhhdCBjb3JydXB0aW9uIHJlc3VsdGluZyBpbg0KICAgbWlzZGVsaXZlcnkgb2Yg
dGhlIHBheWxvYWQgaXMgZXh0cmVtZWx5IGxvdy4NCjxPTEQNCg0KTkVXPg0KICAgQXMgc3RhdGVk
IGluIFtSRkMyNzg0XSwgdGhlIEdSRSBoZWFkZXIgY2FuIGNvbnRhaW4gYSBjaGVja3N1bS4NCiAg
IElmIHByZXNlbnQsIHRoZSBHUkUgaGVhZGVyIGNoZWNrc3VtIGNhbiBiZSB1c2VkIHRvIGRldGVj
dA0KICAgY29ycnVwdGlvbiBvZiB0aGUgR1JFIGhlYWRlciBhbmQgR1JFIHBheWxvYWQuDQoNCiAg
IFRoZSBHUkUgaGVhZGVyIGNoZWNrc3VtIGNhbm5vdCBiZSB1c2VkIHRvIGRldGVjdCBjb3JydXB0
aW9uDQogICAgb2YgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyLiBGdXJ0aGVybW9yZSwgdGhlIElQ
djYgZGVsaXZlcnkgaGVhZGVyDQogICBkb2VzIG5vdCBjb250YWluICBhIGNoZWNrc3VtIG9yIGl0
cyBvd24uIFRoZXJlZm9yZSwgbm8gY2hlY2tzdW0NCiAgIGNhbiBiZSB1c2VkIHRvIGRldGVjdCBj
b3JydXB0aW9uIG9mIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci4NCltMdWN5XSBuaXQ6IOKAnG9u
IGl0cyBvd27igJ0NCiAgIEluIG9uZSBmYWlsdXJlIHNjZW5hcmlvLCB0aGUgZGVzdGluYXRpb24g
YWRkcmVzcyBpbiB0aGUgSVB2NiBkZWxpdmVyeQ0KICAgaGVhZGVyIGlzIGNvcnJ1cHRlZC4gQXMg
YSByZXN1bHQsIHRoZSBJUHY2IGRlbGl2ZXJ5IHBhY2tldCBpcyBkZWxpdmVyZWQNCiAgIHRvICBh
IG5vZGUgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgR1JFIGVncmVzcyBub2RlLiBEZXBlbmRpbmcg
dXBvbg0KICAgdGhlIHN0YXRlIGFuZCBjb25maWd1cmF0aW9uIG9mIHRoYXQgbm9kZSwgaXQgd2ls
bCBlaXRoZXI6DQoNCg0KYSkgICAgICBEcm9wIHRoZSBwYWNrZXQNCg0KYikgICAgICBEZS1lbmNh
cHN1bGF0ZSB0aGUgcGF5bG9hZCBhbmQgZm9yd2FyZCBpdCB0byBpdHMgaW50ZW5kZWQgZGVzdGlu
YXRpb24NCg0KYykgICAgICAgRGUtZW5jYXBzdWxhdGUgdGhlIHBheWxvYWQgYW5kIGZvcndhcmQg
aXQgdG8gYSBub2RlIG90aGVyIHRoYW4gaXRzIGludGVuZGVkIGRlc3RpbmF0aW9uLiBGb3IgZXhh
bXBsZSwgdGhlIHBheWxvYWQgbWlnaHQgYmUgaW50ZW5kZWQgZm9yIGEgbm9kZSBvbiBvbmUgVlBO
LCBidXQgZGVsaXZlcmVkIHRvIGFuIGlkZW50aWNhbGx5IG51bWJlcmVkIG5vZGUgaW4gYW5vdGhl
ciBWUE4uDQoNCg0KQmVoYXZpb3JzIGEpIGFuZCBiKSBhcmUgYWNjZXB0YWJsZS4gQmVoYXZpb3Ig
YykgaXMgbm90IGFjY2VwdGFibGUuDQoNCkJlZm9yZSBkZXBsb3lpbmcgR1JFIG92ZXIgSVB2Niwg
bmV0d29yayBvcGVyYXRvcnMgc2hvdWxkIGNvbnNpZGVyIHRoZQ0KbGlrZWxpaG9vZCBvZiBiZWhh
dmlvciBjKSBpbiB0aGVpciBuZXR3b3JrLiBOZXR3b3JrIG9wZXJhdG9ycyBzaG91bGQgZGVwbG95
DQpHUkUgb3ZlciBJUHY2IGlmIHRoZXkgY2FuIHRvbGVyYXRlIHRoZSByaXNrIGFzc29jaWF0ZWQg
d2l0aCBiZWhhdmlvciBjKS4NCltMdWN5XSDigJxjYW4gZGVwbG954oCdIGlzIGJldHRlciB0aGFu
IOKAnHNob3VsZCBkZXBsb3nigJ0NCg0KSSBhbSBmaW5lIHdpdGggdGhlIHRleHQgZm9yIHRoZSBj
b3JydXB0aW9uIGNhc2UuIERvIHdlIG5lZWQgdG8gYWRkcmVzcyBtaXNkZWxpdmVyeSBhcyB3ZWxs
Lg0KDQpUaGFua3MsDQpMdWN5DQoNCjxORVcNCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICBSb24NCg0KDQoNCg0K

--_000_2691CE0099834E4A9C5044EEC662BB9D57156796dfweml701chm_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QFNpbVN1biI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30N
Ci8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYu
TXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
MDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojOTU0
RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1z
b1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
bXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiO30NCnANCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJn
aW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1m
YW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZv
bnQtZmFtaWx5OkNvbnNvbGFzO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1z
b0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxs
b29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpw
Lk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdy
YXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4t
cmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1z
dHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpD
b25zb2xhczt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRl
eHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFp
biBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uQmFs
bG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZv
bnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpwLmltcHJpbnR1bmlxdWVpZCwgbGku
aW1wcmludHVuaXF1ZWlkLCBkaXYuaW1wcmludHVuaXF1ZWlkDQoJe21zby1zdHlsZS1uYW1lOmlt
cHJpbnR1bmlxdWVpZDsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbWFyZ2luOjBpbjsNCglt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToi
VGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTI2DQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUyNw0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMx
RjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNw
YW4uRW1haWxTdHlsZTI5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5
bGUzMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzENCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
IjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTMyDQoJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJ
Zm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlv
bjpub25lIG5vbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzMNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdE
O30NCnNwYW4uRW1haWxTdHlsZTM0DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVt
YWlsU3R5bGUzNQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzYN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTM3DQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUzOA0KCXttc28tc3R5bGUtdHlwZTpwZXJz
b25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9y
OiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7
DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAx
MS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlv
bjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8
L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0
IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNo
YXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMi
IGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9u
MSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SGkg
Um9uLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+R29vZCBUcnkuIFNlZSBp
bmxpbmUgYmVsb3cuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij4gUm9uYWxkIEJvbmljYSBbbWFpbHRvOnJib25pY2FAanVuaXBlci5u
ZXRdDQo8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIEFwcmlsIDAyLCAyMDE1IDI6MzkgUE08
YnI+DQo8Yj5Ubzo8L2I+IEx1Y3kgeW9uZzsgQmxhY2ssIERhdmlkOyBpbnQtYXJlYUBpZXRmLm9y
ZzsgaXB2NkBpZXRmLm9yZzsgU3Rld2FydCBCcnlhbnQgKHN0YnJ5YW50KTxicj4NCjxiPkNjOjwv
Yj4gZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnOyBpbnRhcmVhLWNo
YWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSRTogU3RhcnQgb2YgV0dMQyBmb3Ig
ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkx1Y3ksIFRvbSwg
U3Rld2FyZCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkkgYWdyZWUgd2l0
aCB3aGF0IHlvdSBhcmUgc2F5aW5nIGFuZCBoYXZlIHRyaWVkIHRvIGNyYWZ0IHNvbWUgdGV4dCB0
aGF0IGFkZHJlc3NlcyBhbGwgb2YgeW91ciBjb21tZW50cy4gUGxlYXNlIHRlbGwgbWUgaWYgdGhl
IGZvbGxvd2luZyB0ZXh0IGRvZXMgdGhlIHRyaWNrLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IFJvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+T0xEJmd0Ozxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgQXMgc3RhdGVkIGluIFtSRkMyNzg0XSwgdGhlIENo
ZWNrc3VtIGZpZWxkIGNvbnRhaW5zIHRoZSBJUCAob25lJ3M8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7
Jm5ic3A7IGNvbXBsZW1lbnQpIGNoZWNrc3VtIHN1bSBvZiB0aGUgYWxsIHRoZSAxNiBiaXQgd29y
ZHMgaW4gdGhlIEdSRTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgaGVhZGVyIGFuZCB0aGUg
cGF5bG9hZCBwYWNrZXQuJm5ic3A7IFRoZXJlZm9yZSwgdGhlIGNoZWNrc3VtIGRvZXMgbm90PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBlbnN1cmUgdGhlIGludGVncml0eSBvZiB0aGUgSVB2
NiBkZWxpdmVyeSBoZWFkZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4m
bmJzcDsmbmJzcDtCZWNhdXNlIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNs
dWRlIGEgY2hlY2tzdW0gb2YgaXRzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBvd24sIGl0
IGlzIHN1YmplY3QgdG8gY29ycnVwdGlvbi4mbmJzcDsgSG93ZXZlciwgZXZlbiBpZiB0aGUgZGVs
aXZlcnk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IGhlYWRlciBpcyBjb3JydXB0ZWQsIHRv
IGxpa2VsaWhvb2Qgb2YgdGhhdCBjb3JydXB0aW9uIHJlc3VsdGluZyBpbjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij4mbmJzcDsmbmJzcDsgbWlzZGVsaXZlcnkgb2YgdGhlIHBheWxvYWQgaXMgZXh0cmVtZWx5IGxv
dy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+Jmx0O09MRDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+TkVXJmd0OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgQXMgc3RhdGVkIGluIFtS
RkMyNzg0XSwgdGhlIEdSRSBoZWFkZXIgY2FuIGNvbnRhaW4gYSBjaGVja3N1bS48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+Jm5ic3A7Jm5ic3A7IElmIHByZXNlbnQsIHRoZSBHUkUgaGVhZGVyIGNoZWNrc3VtIGNh
biBiZSB1c2VkIHRvIGRldGVjdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgY29ycnVwdGlv
biBvZiB0aGUgR1JFIGhlYWRlciBhbmQgR1JFIHBheWxvYWQuDQo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBUaGUgR1JFIGhlYWRlciBjaGVja3N1bSBj
YW5ub3QgYmUgdXNlZCB0byBkZXRlY3QgY29ycnVwdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsm
bmJzcDsmbmJzcDsgb2YgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyLiBGdXJ0aGVybW9yZSwgdGhl
IElQdjYgZGVsaXZlcnkgaGVhZGVyDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
ZG9lcyBub3QgY29udGFpbiAmbmJzcDthIGNoZWNrc3VtIG9yIGl0cyBvd24uIFRoZXJlZm9yZSwg
bm8gY2hlY2tzdW08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IGNhbiBiZSB1c2VkIHRvIGRl
dGVjdCBjb3JydXB0aW9uIG9mIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+W0x1Y3ldIDwvc3Bhbj48L2k+PC9iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij5uaXQ6IOKAnG9uIGl0cyBvd27igJ08L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgSW4gb25lIGZhaWx1cmUgc2NlbmFyaW8sIHRo
ZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGluIHRoZSBJUHY2IGRlbGl2ZXJ5DQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3
RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7aGVhZGVyIGlzIGNvcnJ1cHRlZC4gQXMgYSByZXN1bHQsIHRo
ZSBJUHY2IGRlbGl2ZXJ5IHBhY2tldCBpcyBkZWxpdmVyZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7
Jm5ic3A7IHRvICZuYnNwO2Egbm9kZSBvdGhlciB0aGFuIHRoZSBpbnRlbmRlZCBHUkUgZWdyZXNz
IG5vZGUuIERlcGVuZGluZyB1cG9uDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
dGhlIHN0YXRlIGFuZCBjb25maWd1cmF0aW9uIG9mIHRoYXQgbm9kZSwgaXQgd2lsbCBlaXRoZXI6
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRlbnQ6LS4y
NWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+YSk8L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1
b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRyb3AgdGhlIHBhY2tldDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRlbnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+Yik8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo3LjBwdDtmb250LWZhbWls
eTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPkRlLWVuY2Fwc3VsYXRlIHRoZSBwYXlsb2FkIGFuZCBmb3J3YXJkIGl0
IHRvIGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1aW47dGV4dC1pbmRl
bnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Yyk8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo3LjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkRlLWVu
Y2Fwc3VsYXRlIHRoZSBwYXlsb2FkIGFuZCBmb3J3YXJkIGl0IHRvIGEgbm9kZSBvdGhlciB0aGFu
IGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbi4gRm9yIGV4YW1wbGUsIHRoZSBwYXlsb2FkIG1pZ2h0
IGJlIGludGVuZGVkIGZvciBhIG5vZGUgb24gb25lIFZQTiwgYnV0IGRlbGl2ZXJlZCB0byBhbiBp
ZGVudGljYWxseSBudW1iZXJlZCBub2RlIGluIGFub3RoZXIgVlBOLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6Ljc1
aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+QmVo
YXZpb3JzIGEpIGFuZCBiKSBhcmUgYWNjZXB0YWJsZS4gQmVoYXZpb3IgYykgaXMgbm90IGFjY2Vw
dGFibGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5CZWZvcmUgZGVwbG95
aW5nIEdSRSBvdmVyIElQdjYsIG5ldHdvcmsgb3BlcmF0b3JzIHNob3VsZCBjb25zaWRlciB0aGU8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+bGlrZWxpaG9vZCBvZiBiZWhhdmlvciBjKSBpbiB0aGVpciBuZXR3b3Jr
LiBOZXR3b3JrIG9wZXJhdG9ycyBzaG91bGQgZGVwbG95PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkdSRSBvdmVy
IElQdjYgaWYgdGhleSBjYW4gdG9sZXJhdGUgdGhlIHJpc2sgYXNzb2NpYXRlZCB3aXRoIGJlaGF2
aW9yIGMpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxp
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5bTHVjeV0g4oCcY2FuIGRlcGxveeKAnSBpcyBi
ZXR0ZXIgdGhhbiDigJxzaG91bGQgZGVwbG954oCdPG86cD48L286cD48L3NwYW4+PC9pPjwvYj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48Yj48aT48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SSBhbSBmaW5lIHdpdGggdGhl
IHRleHQgZm9yIHRoZSBjb3JydXB0aW9uIGNhc2UuIERvIHdlIG5lZWQgdG8gYWRkcmVzcyBtaXNk
ZWxpdmVyeSBhcyB3ZWxsLjxvOnA+PC9vOnA+PC9zcGFuPjwvaT48L2I+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvaT48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNw
YW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L2k+PC9i
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxpPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5MdWN5PC9zcGFuPjwvaT48L2I+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmx0O05FVzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFJvbjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJs
dWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4w
cHQiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVw
dDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8
ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRp
bmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxl
ZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_2691CE0099834E4A9C5044EEC662BB9D57156796dfweml701chm_--


From nobody Thu Apr  2 15:01:08 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF411A854B; Thu,  2 Apr 2015 15:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2J3oYA1wiZX; Thu,  2 Apr 2015 15:01:03 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0103.outbound.protection.outlook.com [207.46.100.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FB511A8547; Thu,  2 Apr 2015 15:01:03 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.1.130.23; Thu, 2 Apr 2015 22:01:01 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Thu, 2 Apr 2015 22:01:01 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Lucy yong <lucy.yong@huawei.com>, "Black, David" <david.black@emc.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgAC9ARgAAFkw8AAAT40EAAAitxwAAB0qeAAArfCMAAmU5wwAAGCFgAAAO0wYAAC3xTgAFhv1xAACo9RgAAEsy7g
Date: Thu, 2 Apr 2015 22:01:01 +0000
Message-ID: <CO1PR05MB442208874C186B2A18B08F5AEF20@CO1PR05MB442.namprd05.prod.outlook.com>
References: <785DB11636645E438E2E096E1ADA47C40DAC8053@KAMACITE.InterDigital.com> <2691CE0099834E4A9C5044EEC662BB9D57154F13@dfweml701-chm> <BLUPR05MB4336B6AEC1D94C4A91F0BBDAEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F68@dfweml701-chm> <BLUPR05MB4331B3E4E081608B45AA4F2AEF50@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57154F85@dfweml701-chm> <CE03DB3D7B45C245BCA0D2432779493642FBD9@MX104CL02.corp.emc.com> <BLUPR05MB4337AC68F8F0456DF90104DAEF40@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57155632@dfweml701-chm> <BLUPR05MB433CD2BDA87CC868451C6B7AEF20@BLUPR05MB433.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D57156796@dfweml701-chm>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D57156796@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB442;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(979002)(377454003)(57704003)(164054003)(86362001)(46102003)(54356999)(50986999)(2201001)(74316001)(93886004)(19300405004)(122556002)(40100003)(2900100001)(2950100001)(76176999)(19580395003)(2656002)(87936001)(19580405001)(19625215002)(76576001)(77156002)(33656002)(62966003)(230783001)(92566002)(66066001)(2501003)(99286002)(102836002)(15975445007)(16236675004)(7059030)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
x-microsoft-antispam-prvs: <CO1PR05MB442699EEBE3D0121772100DAEF20@CO1PR05MB442.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CO1PR05MB442; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB442; 
x-forefront-prvs: 0534947130
Content-Type: multipart/alternative; boundary="_000_CO1PR05MB442208874C186B2A18B08F5AEF20CO1PR05MB442namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2015 22:01:01.3254 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB442
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/y0KtoFaC0Tjvk-oU2Lgt_pF1Phg>
Cc: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 22:01:06 -0000

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

THVjeSwNCg0KQm90aCBnb29kIGNhdGNoZXMuIFN0YW5kIGJ5IGZvciB0ZXh0IG9uIG1pc2RlbGl2
ZXJ5Lg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFJvbg0K
DQoNCkZyb206IEx1Y3kgeW9uZyBbbWFpbHRvOmx1Y3kueW9uZ0BodWF3ZWkuY29tXQ0KU2VudDog
VGh1cnNkYXksIEFwcmlsIDAyLCAyMDE1IDM6NTggUE0NClRvOiBSb25hbGQgQm9uaWNhOyBCbGFj
aywgRGF2aWQ7IGludC1hcmVhQGlldGYub3JnOyBpcHY2QGlldGYub3JnOyBTdGV3YXJ0IEJyeWFu
dCAoc3RicnlhbnQpDQpDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYu
b3JnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUkU6IFN0YXJ0IG9mIFdHTEMg
Zm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ng0KDQpIaSBSb24sDQoNCkdvb2QgVHJ5LiBT
ZWUgaW5saW5lIGJlbG93Lg0KDQpGcm9tOiBSb25hbGQgQm9uaWNhIFttYWlsdG86cmJvbmljYUBq
dW5pcGVyLm5ldF0NClNlbnQ6IFRodXJzZGF5LCBBcHJpbCAwMiwgMjAxNSAyOjM5IFBNDQpUbzog
THVjeSB5b25nOyBCbGFjaywgRGF2aWQ7IGludC1hcmVhQGlldGYub3JnPG1haWx0bzppbnQtYXJl
YUBpZXRmLm9yZz47IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+OyBTdGV3YXJ0
IEJyeWFudCAoc3RicnlhbnQpDQpDYzogZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xz
LmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5v
cmc+OyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86aW50YXJlYS1jaGFpcnNAaWV0Zi5v
cmc+DQpTdWJqZWN0OiBSRTogU3RhcnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdy
ZS1pcHY2DQoNCkx1Y3ksIFRvbSwgU3Rld2FyZCwNCg0KSSBhZ3JlZSB3aXRoIHdoYXQgeW91IGFy
ZSBzYXlpbmcgYW5kIGhhdmUgdHJpZWQgdG8gY3JhZnQgc29tZSB0ZXh0IHRoYXQgYWRkcmVzc2Vz
IGFsbCBvZiB5b3VyIGNvbW1lbnRzLiBQbGVhc2UgdGVsbCBtZSBpZiB0aGUgZm9sbG93aW5nIHRl
eHQgZG9lcyB0aGUgdHJpY2suDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgUm9uDQoNCk9MRD4NCiAgIEFzIHN0YXRlZCBpbiBbUkZDMjc4NF0sIHRoZSBDaGVja3N1bSBm
aWVsZCBjb250YWlucyB0aGUgSVAgKG9uZSdzDQogICBjb21wbGVtZW50KSBjaGVja3N1bSBzdW0g
b2YgdGhlIGFsbCB0aGUgMTYgYml0IHdvcmRzIGluIHRoZSBHUkUNCiAgIGhlYWRlciBhbmQgdGhl
IHBheWxvYWQgcGFja2V0LiAgVGhlcmVmb3JlLCB0aGUgY2hlY2tzdW0gZG9lcyBub3QNCiAgIGVu
c3VyZSB0aGUgaW50ZWdyaXR5IG9mIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci4NCg0KICBCZWNh
dXNlIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlciBkb2VzIG5vdCBpbmNsdWRlIGEgY2hlY2tzdW0g
b2YgaXRzDQogICBvd24sIGl0IGlzIHN1YmplY3QgdG8gY29ycnVwdGlvbi4gIEhvd2V2ZXIsIGV2
ZW4gaWYgdGhlIGRlbGl2ZXJ5DQogICBoZWFkZXIgaXMgY29ycnVwdGVkLCB0byBsaWtlbGlob29k
IG9mIHRoYXQgY29ycnVwdGlvbiByZXN1bHRpbmcgaW4NCiAgIG1pc2RlbGl2ZXJ5IG9mIHRoZSBw
YXlsb2FkIGlzIGV4dHJlbWVseSBsb3cuDQo8T0xEDQoNCk5FVz4NCiAgIEFzIHN0YXRlZCBpbiBb
UkZDMjc4NF0sIHRoZSBHUkUgaGVhZGVyIGNhbiBjb250YWluIGEgY2hlY2tzdW0uDQogICBJZiBw
cmVzZW50LCB0aGUgR1JFIGhlYWRlciBjaGVja3N1bSBjYW4gYmUgdXNlZCB0byBkZXRlY3QNCiAg
IGNvcnJ1cHRpb24gb2YgdGhlIEdSRSBoZWFkZXIgYW5kIEdSRSBwYXlsb2FkLg0KDQogICBUaGUg
R1JFIGhlYWRlciBjaGVja3N1bSBjYW5ub3QgYmUgdXNlZCB0byBkZXRlY3QgY29ycnVwdGlvbg0K
ICAgIG9mIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci4gRnVydGhlcm1vcmUsIHRoZSBJUHY2IGRl
bGl2ZXJ5IGhlYWRlcg0KICAgZG9lcyBub3QgY29udGFpbiAgYSBjaGVja3N1bSBvciBpdHMgb3du
LiBUaGVyZWZvcmUsIG5vIGNoZWNrc3VtDQogICBjYW4gYmUgdXNlZCB0byBkZXRlY3QgY29ycnVw
dGlvbiBvZiB0aGUgSVB2NiBkZWxpdmVyeSBoZWFkZXIuDQpbTHVjeV0gbml0OiDigJxvbiBpdHMg
b3du4oCdDQogICBJbiBvbmUgZmFpbHVyZSBzY2VuYXJpbywgdGhlIGRlc3RpbmF0aW9uIGFkZHJl
c3MgaW4gdGhlIElQdjYgZGVsaXZlcnkNCiAgIGhlYWRlciBpcyBjb3JydXB0ZWQuIEFzIGEgcmVz
dWx0LCB0aGUgSVB2NiBkZWxpdmVyeSBwYWNrZXQgaXMgZGVsaXZlcmVkDQogICB0byAgYSBub2Rl
IG90aGVyIHRoYW4gdGhlIGludGVuZGVkIEdSRSBlZ3Jlc3Mgbm9kZS4gRGVwZW5kaW5nIHVwb24N
CiAgIHRoZSBzdGF0ZSBhbmQgY29uZmlndXJhdGlvbiBvZiB0aGF0IG5vZGUsIGl0IHdpbGwgZWl0
aGVyOg0KDQoNCmEpICAgICAgRHJvcCB0aGUgcGFja2V0DQoNCmIpICAgICAgRGUtZW5jYXBzdWxh
dGUgdGhlIHBheWxvYWQgYW5kIGZvcndhcmQgaXQgdG8gaXRzIGludGVuZGVkIGRlc3RpbmF0aW9u
DQoNCmMpICAgICAgIERlLWVuY2Fwc3VsYXRlIHRoZSBwYXlsb2FkIGFuZCBmb3J3YXJkIGl0IHRv
IGEgbm9kZSBvdGhlciB0aGFuIGl0cyBpbnRlbmRlZCBkZXN0aW5hdGlvbi4gRm9yIGV4YW1wbGUs
IHRoZSBwYXlsb2FkIG1pZ2h0IGJlIGludGVuZGVkIGZvciBhIG5vZGUgb24gb25lIFZQTiwgYnV0
IGRlbGl2ZXJlZCB0byBhbiBpZGVudGljYWxseSBudW1iZXJlZCBub2RlIGluIGFub3RoZXIgVlBO
Lg0KDQoNCkJlaGF2aW9ycyBhKSBhbmQgYikgYXJlIGFjY2VwdGFibGUuIEJlaGF2aW9yIGMpIGlz
IG5vdCBhY2NlcHRhYmxlLg0KDQpCZWZvcmUgZGVwbG95aW5nIEdSRSBvdmVyIElQdjYsIG5ldHdv
cmsgb3BlcmF0b3JzIHNob3VsZCBjb25zaWRlciB0aGUNCmxpa2VsaWhvb2Qgb2YgYmVoYXZpb3Ig
YykgaW4gdGhlaXIgbmV0d29yay4gTmV0d29yayBvcGVyYXRvcnMgc2hvdWxkIGRlcGxveQ0KR1JF
IG92ZXIgSVB2NiBpZiB0aGV5IGNhbiB0b2xlcmF0ZSB0aGUgcmlzayBhc3NvY2lhdGVkIHdpdGgg
YmVoYXZpb3IgYykuDQpbTHVjeV0g4oCcY2FuIGRlcGxveeKAnSBpcyBiZXR0ZXIgdGhhbiDigJxz
aG91bGQgZGVwbG954oCdDQoNCkkgYW0gZmluZSB3aXRoIHRoZSB0ZXh0IGZvciB0aGUgY29ycnVw
dGlvbiBjYXNlLiBEbyB3ZSBuZWVkIHRvIGFkZHJlc3MgbWlzZGVsaXZlcnkgYXMgd2VsbC4NCg0K
VGhhbmtzLA0KTHVjeQ0KDQo8TkVXDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgUm9uDQoNCg0KDQoNCg==

--_000_CO1PR05MB442208874C186B2A18B08F5AEF20CO1PR05MB442namprd_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2
IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglw
YW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0
DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBD
aGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6
MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnANCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdo
dDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0K
CWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7
fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQ
cmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7
DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpDb25zb2xhczt9DQpwLk1zb0FjZXRh
dGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0YXRlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJ
bWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo4LjBwdDsNCglmb250LWZhbWlseToi
VGFob21hIixzYW5zLXNlcmlmO30NCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFn
cmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1h
cmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJ
bWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEx
LjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLkhUTUxQcmVm
b3JtYXR0ZWRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsN
Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0
dGVkIjsNCglmb250LWZhbWlseTpDb25zb2xhczt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNv
LXN0eWxlLW5hbWU6IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fu
cy1zZXJpZjt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9v
biBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi
QmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIixzYW5zLXNlcmlmO30NCnAuaW1w
cmludHVuaXF1ZWlkLCBsaS5pbXByaW50dW5pcXVlaWQsIGRpdi5pbXByaW50dW5pcXVlaWQNCgl7
bXNvLXN0eWxlLW5hbWU6aW1wcmludHVuaXF1ZWlkOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsN
CgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uRW1haWxTdHls
ZTI2DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUyOA0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0
OTdEO30NCnNwYW4uRW1haWxTdHlsZTI5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMzANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUzMQ0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTMyDQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7
DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3Jh
dGlvbjpub25lIG5vbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzMNCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3
RDt9DQpzcGFuLkVtYWlsU3R5bGUzNA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1h
aWxTdHlsZTM1DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMzYNCgl7
bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUzNw0KCXttc28tc3R5bGUtdHlw
ZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjoj
MUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTM4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMzkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4g
MS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9u
MTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0
cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRt
YXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5k
aWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iIzA1NjNDMSIgdmxpbms9
IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5MdWN5LDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+Qm90aCBnb29kIGNhdGNoZXMuIFN0YW5kIGJ5IGZvciB0ZXh0IG9u
IG1pc2RlbGl2ZXJ5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFJvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVy
Om5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQu
MHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNF
MUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48Yj5Gcm9tOjwvYj4gTHVjeSB5b25nIFttYWlsdG86bHVjeS55b25nQGh1YXdlaS5jb21d
IDxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgQXByaWwgMDIsIDIwMTUgMzo1OCBQTTxicj4N
CjxiPlRvOjwvYj4gUm9uYWxkIEJvbmljYTsgQmxhY2ssIERhdmlkOyBpbnQtYXJlYUBpZXRmLm9y
ZzsgaXB2NkBpZXRmLm9yZzsgU3Rld2FydCBCcnlhbnQgKHN0YnJ5YW50KTxicj4NCjxiPkNjOjwv
Yj4gZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnOyBpbnRhcmVhLWNo
YWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSRTogU3RhcnQgb2YgV0dMQyBmb3Ig
ZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SGkgUm9uLDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+R29vZCBUcnkuIFNlZSBpbmxpbmUgYmVsb3cuPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssc2Fucy1zZXJp
ZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1RhaG9tYSZxdW90OyxzYW5zLXNlcmlmIj4gUm9uYWxkIEJvbmljYSBbPGEgaHJl
Zj0ibWFpbHRvOnJib25pY2FAanVuaXBlci5uZXQiPm1haWx0bzpyYm9uaWNhQGp1bmlwZXIubmV0
PC9hPl0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgQXByaWwgMDIsIDIwMTUgMjozOSBQ
TTxicj4NCjxiPlRvOjwvYj4gTHVjeSB5b25nOyBCbGFjaywgRGF2aWQ7IDxhIGhyZWY9Im1haWx0
bzppbnQtYXJlYUBpZXRmLm9yZyI+aW50LWFyZWFAaWV0Zi5vcmc8L2E+Ow0KPGEgaHJlZj0ibWFp
bHRvOmlwdjZAaWV0Zi5vcmciPmlwdjZAaWV0Zi5vcmc8L2E+OyBTdGV3YXJ0IEJyeWFudCAoc3Ri
cnlhbnQpPGJyPg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1pbnRhcmVh
LWdyZS1pcHY2QHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9v
bHMuaWV0Zi5vcmc8L2E+Ow0KPGEgaHJlZj0ibWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3Jn
Ij5pbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzwvYT48YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6IFN0
YXJ0IG9mIFdHTEMgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2NjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5MdWN5LCBUb20sIFN0ZXdhcmQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5JIGFncmVlIHdpdGggd2hhdCB5b3UgYXJlIHNheWluZyBhbmQgaGF2ZSB0cmllZCB0byBj
cmFmdCBzb21lIHRleHQgdGhhdCBhZGRyZXNzZXMgYWxsIG9mIHlvdXIgY29tbWVudHMuIFBsZWFz
ZSB0ZWxsIG1lIGlmIHRoZSBmb2xsb3dpbmcgdGV4dCBkb2VzIHRoZSB0cmljay48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBSb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPk9MRCZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IEFzIHN0YXRlZCBpbiBb
UkZDMjc4NF0sIHRoZSBDaGVja3N1bSBmaWVsZCBjb250YWlucyB0aGUgSVAgKG9uZSdzPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBjb21wbGVtZW50KSBjaGVja3N1bSBzdW0gb2YgdGhlIGFs
bCB0aGUgMTYgYml0IHdvcmRzIGluIHRoZSBHUkU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7
IGhlYWRlciBhbmQgdGhlIHBheWxvYWQgcGFja2V0LiZuYnNwOyBUaGVyZWZvcmUsIHRoZSBjaGVj
a3N1bSBkb2VzIG5vdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgZW5zdXJlIHRoZSBpbnRl
Z3JpdHkgb2YgdGhlIElQdjYgZGVsaXZlcnkgaGVhZGVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7QmVjYXVzZSB0aGUgSVB2NiBkZWxpdmVyeSBoZWFk
ZXIgZG9lcyBub3QgaW5jbHVkZSBhIGNoZWNrc3VtIG9mIGl0czxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJz
cDsmbmJzcDsgb3duLCBpdCBpcyBzdWJqZWN0IHRvIGNvcnJ1cHRpb24uJm5ic3A7IEhvd2V2ZXIs
IGV2ZW4gaWYgdGhlIGRlbGl2ZXJ5PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBoZWFkZXIg
aXMgY29ycnVwdGVkLCB0byBsaWtlbGlob29kIG9mIHRoYXQgY29ycnVwdGlvbiByZXN1bHRpbmcg
aW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7IG1pc2RlbGl2ZXJ5IG9mIHRoZSBwYXlsb2Fk
IGlzIGV4dHJlbWVseSBsb3cuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZsdDtPTEQ8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPk5FVyZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7
IEFzIHN0YXRlZCBpbiBbUkZDMjc4NF0sIHRoZSBHUkUgaGVhZGVyIGNhbiBjb250YWluIGEgY2hl
Y2tzdW0uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBJZiBwcmVzZW50LCB0aGUgR1JFIGhl
YWRlciBjaGVja3N1bSBjYW4gYmUgdXNlZCB0byBkZXRlY3Q8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7
Jm5ic3A7IGNvcnJ1cHRpb24gb2YgdGhlIEdSRSBoZWFkZXIgYW5kIEdSRSBwYXlsb2FkLg0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgVGhlIEdSRSBo
ZWFkZXIgY2hlY2tzdW0gY2Fubm90IGJlIHVzZWQgdG8gZGV0ZWN0IGNvcnJ1cHRpb248bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IG9mIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlci4g
RnVydGhlcm1vcmUsIHRoZSBJUHY2IGRlbGl2ZXJ5IGhlYWRlcg0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZu
YnNwOyZuYnNwOyZuYnNwO2RvZXMgbm90IGNvbnRhaW4gJm5ic3A7YSBjaGVja3N1bSBvciBpdHMg
b3duLiBUaGVyZWZvcmUsIG5vIGNoZWNrc3VtPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyBj
YW4gYmUgdXNlZCB0byBkZXRlY3QgY29ycnVwdGlvbiBvZiB0aGUgSVB2NiBkZWxpdmVyeSBoZWFk
ZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNw
YW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPltMdWN5XSA8L3NwYW4+PC9pPjwvYj48c3BhbiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+bml0OiDigJxvbiBpdHMgb3du4oCdPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZu
YnNwOyZuYnNwOyBJbiBvbmUgZmFpbHVyZSBzY2VuYXJpbywgdGhlIGRlc3RpbmF0aW9uIGFkZHJl
c3MgaW4gdGhlIElQdjYgZGVsaXZlcnkNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJz
cDtoZWFkZXIgaXMgY29ycnVwdGVkLiBBcyBhIHJlc3VsdCwgdGhlIElQdjYgZGVsaXZlcnkgcGFj
a2V0IGlzIGRlbGl2ZXJlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsgdG8gJm5ic3A7YSBu
b2RlIG90aGVyIHRoYW4gdGhlIGludGVuZGVkIEdSRSBlZ3Jlc3Mgbm9kZS4gRGVwZW5kaW5nIHVw
b24NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDt0aGUgc3RhdGUgYW5kIGNvbmZp
Z3VyYXRpb24gb2YgdGhhdCBub2RlLCBpdCB3aWxsIGVpdGhlcjo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0
eWxlPSJtYXJnaW4tbGVmdDouNzVpbjt0ZXh0LWluZGVudDotLjI1aW4iPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj5hKTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyxzZXJpZjtjb2xvcjojMUY0OTdEIj4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+RHJvcCB0aGUgcGFja2V0PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDouNzVpbjt0ZXh0LWluZGVudDot
LjI1aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5iKTwvc3Bhbj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90Oyxz
ZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bh
bj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+RGUtZW5jYXBzdWxhdGUgdGhlIHBheWxvYWQg
YW5kIGZvcndhcmQgaXQgdG8gaXRzIGludGVuZGVkIGRlc3RpbmF0aW9uPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDou
NzVpbjt0ZXh0LWluZGVudDotLjI1aW4iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5jKTwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVz
IE5ldyBSb21hbiZxdW90OyxzZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+RGUt
ZW5jYXBzdWxhdGUgdGhlIHBheWxvYWQgYW5kIGZvcndhcmQgaXQgdG8gYSBub2RlIG90aGVyIHRo
YW4gaXRzIGludGVuZGVkIGRlc3RpbmF0aW9uLiBGb3IgZXhhbXBsZSwgdGhlIHBheWxvYWQgbWln
aHQgYmUgaW50ZW5kZWQgZm9yIGEgbm9kZSBvbiBvbmUgVlBOLCBidXQgZGVsaXZlcmVkIHRvIGFu
IGlkZW50aWNhbGx5IG51bWJlcmVkIG5vZGUgaW4gYW5vdGhlciBWUE4uPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDou
NzVpbiI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5C
ZWhhdmlvcnMgYSkgYW5kIGIpIGFyZSBhY2NlcHRhYmxlLiBCZWhhdmlvciBjKSBpcyBub3QgYWNj
ZXB0YWJsZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkJlZm9yZSBkZXBs
b3lpbmcgR1JFIG92ZXIgSVB2NiwgbmV0d29yayBvcGVyYXRvcnMgc2hvdWxkIGNvbnNpZGVyIHRo
ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj5saWtlbGlob29kIG9mIGJlaGF2aW9yIGMpIGluIHRoZWlyIG5ldHdv
cmsuIE5ldHdvcmsgb3BlcmF0b3JzIHNob3VsZCBkZXBsb3k8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+R1JFIG92
ZXIgSVB2NiBpZiB0aGV5IGNhbiB0b2xlcmF0ZSB0aGUgcmlzayBhc3NvY2lhdGVkIHdpdGggYmVo
YXZpb3IgYykuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+
PGk+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPltMdWN5XSDigJxjYW4gZGVwbG954oCdIGlz
IGJldHRlciB0aGFuIOKAnHNob3VsZCBkZXBsb3nigJ08bzpwPjwvbzpwPjwvc3Bhbj48L2k+PC9i
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxpPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2k+PC9iPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxpPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5JIGFtIGZpbmUgd2l0aCB0
aGUgdGV4dCBmb3IgdGhlIGNvcnJ1cHRpb24gY2FzZS4gRG8gd2UgbmVlZCB0byBhZGRyZXNzIG1p
c2RlbGl2ZXJ5IGFzIHdlbGwuPG86cD48L286cD48L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48aT48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48
c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+VGhhbmtzLDxvOnA+PC9vOnA+PC9zcGFuPjwvaT48
L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPkx1Y3k8L3NwYW4+PC9pPjwvYj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbHQ7TkVXPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgUm9uPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
Ymx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXYgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0
LjBwdCI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFk
ZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_CO1PR05MB442208874C186B2A18B08F5AEF20CO1PR05MB442namprd_--


From nobody Thu Apr  2 17:52:08 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F3B1A8A10 for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 17:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 NCsEqG_e5qpa for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 17:52:05 -0700 (PDT)
Received: from nm49-vm10.bullet.mail.bf1.yahoo.com (nm49-vm10.bullet.mail.bf1.yahoo.com [216.109.114.251]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92B01A8A11 for <ipv6@ietf.org>; Thu,  2 Apr 2015 17:52:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428022323; bh=J9rgQ96CAVcgqblWZ45TI+PwQ5NiH6tKRAXuyB37+/4=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=rbTTKs5Zpaz92JEH48L+nKLuXKlMvFs2x8y+dQ4pNro7tmUN8Oj5cyV3+w0yaxi9gyDKJdMvilL+G+3StbodtLKDWb/PVdxY/Ic0WZ77ej/6zuEEbVpScwEc1siQh6T7tLx7q8hN48msCvxtaxb9JCm4bBvES3mx80hYcdDEhiME8MvFlIIoBwQMHddv7W5zRB2U+WnsputGTBoCAIcqc6za399hd4ITWLKVVTZjep1eg5xX2nK4nZesKvd1Q90/2rjKkVpUgSMqE0a6nYixb/kEOqD/6AusNeqZ71vElxpZi0K5jhpbn3H7r0YbqhFeaTulUQ9FRtJ5Dd/PL6OrNQ==
Received: from [98.139.215.143] by nm49.bullet.mail.bf1.yahoo.com with NNFMP;  03 Apr 2015 00:52:03 -0000
Received: from [98.139.212.229] by tm14.bullet.mail.bf1.yahoo.com with NNFMP;  03 Apr 2015 00:52:03 -0000
Received: from [127.0.0.1] by omp1038.mail.bf1.yahoo.com with NNFMP; 03 Apr 2015 00:52:03 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 821881.64155.bm@omp1038.mail.bf1.yahoo.com
X-YMail-OSG: 5hhYvDIVM1lQqWkscfbAub6LYxoCWMvo.Q9HeUdS0JYfEqKikzh60jjEueUMdqO HF8rkvganLRpXgswYJf.egvbZhB9JcomXSJz3qifzoNUJBJpCH1qOHqt26CdEka94zXKfGMdvh40 XYPL_HzEjhUE3_gnWb5f47XJaajQG_UFbNQqSGir.Xd4lTqGCxm8_55ZuRlyclUNJNkMkgyxZi8O HhQT531znifyUf6_YbV7fGqU04q7VlORH0.O5VFAd8pHmCcMVlf7SYVet5QDBKkmMbaqrp0TJLqq qPT9hC5NHSekFHByWU4wkp_2d75R6izl.HiPcyr7g_FCFsVbGIFGGQj4riZvvuML7i5703KVVb3w n3TA_MRN2vKCwmq4jkDOWonyzixqpww4nqM_kKuvnpnce04l48Cwrh8HQyNJs7OPMm8s6Xyx7SdF RrKG0A0foRlA0U.QLiIDR_ICcGskR5fzi4z1Kr0zz4RgnINQi7vlrtmbRhtZXlqK2TvNcltCeMKD eSQTUFpnH.EkORjQUeyAi6RM16RGca1F4j_wMr4qK
Received: by 76.13.26.110; Fri, 03 Apr 2015 00:52:03 +0000 
Date: Fri, 3 Apr 2015 00:52:02 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>
Message-ID: <362433359.4884562.1428022322318.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAC8QAcdQuZ+re33QUq4eD1HXz=mNG49EbmccFHpzfNT359kovQ@mail.gmail.com>
References: <CAC8QAcdQuZ+re33QUq4eD1HXz=mNG49EbmccFHpzfNT359kovQ@mail.gmail.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3-2rfIb8tDVIyCFsMXxMO6uD4ns>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 00:52:08 -0000

Hi Behcet,




________________________________
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au> 
Cc: "STARK, BARBARA H" <bs7652@att.com>; Hemant Singh (shemant) <shemant@cisco.com>; "ipv6@ietf.org" <ipv6@ietf.org> 
Sent: Friday, 3 April 2015, 3:53
Subject: Re: RA Option Guidelines


On Wed, Apr 1, 2015 at 6:23 PM, Mark ZZZ Smith
<markzzzsmith@yahoo.com.au> wrote:
> Hi Behcet,
>
>
> ----- Original Message -----
> From: Behcet Sarikaya <sarikaya2012@gmail.com>
> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
> Cc: "STARK, BARBARA H" <bs7652@att.com>; Hemant Singh (shemant) <shemant@cisco.com>; "ipv6@ietf.org" <ipv6@ietf.org>
> Sent: Thursday, 2 April 2015, 6:21
> Subject: Re: RA Option Guidelines
>
> I don't understand why DHCPv6 is being discussed under RA Option Guidelines?
> If DHCPv6 is being used instead of RA, like in Australia, that
> supports our position that we should also define DHCPv6 options for
> SADR.
>
> / DHCPv6 isn't being used instead of RAs in Australia.
>
> / I think the fundamental problem is people are considering RAs and DHCPv6 to be functional equivalents (like e.g., OSPF vs IS-IS), and therefore thinking that DHCPv6 options should be imported into RAs and vice versa.
>

No, I don't think anybody proposed that, not at myself.
I think you are missing the context here.


/ I think when ever there is a proposal to add options to RAs and to DHCPv6 to carry literally the same values, then I think people are considering them to be functional equivalents, even though they aren't.

> / There are critical operational limitations that RAs have that DHCPv6 doesn't (because the RA mechanisms are much simpler), and by trying to use RAs for the same purpose as DHCPv6,

No, I don't know how you got this? I am sure it is not from SADR discussions.

/ I thought this thread was about what should and shouldn't go into RA options. 

> all the problems already solved for DHCPv6 would have to be solved again for RAs. The desired simplicity of using RAs only would disappear because the complexity of replicating DHCPv6 mechanisms, and the additional significant operational overheads of constant firmware upgrades to routers to add RA options.
>

Yes, there are some parallels like DHCP option guidelines document. I
think that you are blowing it out of proportion.
If it were like you thought then one would say whatever DHCP
guidelines says applies to RA options also and that's it.

The context as I see it is that there are new RA options that are
being defined, maybe it is time to come up with some guidelines. I
view it is natural that this is happening because IPv6 is being
deployed more and more.

/ Right. I agree with guidelines. What I'm pointing out is that the decision on what to put in RAs or not is strongly influenced by factors people seem to not commonly be recognising, including one as fundamental as Internet application transparency. 


DHCP options in this context came about because some people say maybe
we should define the corresponding DHCP options not vice versa. Please
see
http://tools.ietf.org/wg/mif/draft-ietf-mif-mpvd-arch/

and
https://tools.ietf.org/html/draft-ietf-mif-mpvd-ndp-support-01
https://tools.ietf.org/html/draft-ietf-mif-mpvd-dhcp-support-01

/ I'll have a more thorough read to better understand the problem, however the fundamental question I have is are those provisioning domain parameters (which may be useful to consider more generally in an RA guidelines document)

(a) link specific (meaning that every attached host is part of the same provisioning domain, and more explicitly, different hosts can't be part of different provisioning domains when they're attached to the same link)?

(b) host specific (meaning different hosts attached to the same link can be part of different provisioning domains, even if commonly they might be part of the same provisioning domain when attached to the same link)?

If the answer is (a), then I think those options are probably appropriate in RAs, as RA contents can't or can't easily be made host specific (i.e., in the later case you have to stop multicasting RAs, and build host specific unicast RAs, and you only have link-local or MAC addresses to identify the individual hosts). DHCPv6 might still be a better place for them because it is a more flexible protocol, and allows host by host piecemeal deployment of new options.

If the answer is (b), then DHCPv6 is the more appropriate location, because DHCPv6 is fundamentally designed to provide host specific parameters e.g., through the use of host specific attributes such as Client Identification Option, the Vendor Class Option or the Vendor-specific Information Option.


Looking at the example in MPVD architecture, with my limited understanding, I think the answer is both (a) and (b) above, but not duplication across both:


"Typical examples of information in a provisioning domain learned
from the network are:

*  Source address prefixes for use by connections within the
provisioning domain

*  IP address(es) of DNS server(s)

*  Name of HTTP proxy server (if available)

*  DNS suffixes associated with the network

*  Default gateway address"



- Source address prefixes for use by connections within the provisioning domain and Default gateway address are link specific (the same for all hosts attached to the link), so should be conveyed in PV specific RAs options


-  DNS server addresses, proxy servers, DNS suffixes are can be host specific, so should be conveyed in PV specific DHCPv6 options


That break down might not be correct, if all of those parameters are host specific, then they should be conveyed in DHCPv6 because DHCPv6 has the mechanisms to do host specific parameters.

I always think it is important to fall back to this fundamental principle from RFC1958, "Architectural Principles of the Internet", which is why I think it is a choice between RA options or DHCPv6 options, rather than doing both:


"3.2 If there are several ways of doing the same thing, choose one.
If a previous design, in the Internet context or elsewhere, has
successfully solved the same problem, choose the same solution unless
there is a good technical reason not to.  Duplication of the same
protocol functionality should be avoided as far as possible, without
of course using this argument to reject improvements."

I suspect the argument for putting DHCPv6-like information into RAs is fundamentally, "what if there isn't a DHCPv6 server (relay) to use". My answer would be that if you want to do XYZ, then you need a DHCPv6 server (instead of overloading RAs with DHCPv6 functionality.)



Regards,
Mark.




Regards,




Behcet


> Regards,
>
> Mark.
>
>
>
> Regards,
> Behcet
>
>
> On Tue, Mar 31, 2015 at 9:33 PM, Mark ZZZ Smith
> <markzzzsmith@yahoo.com.au> wrote:
>> Hi Barbara,
>>
>> ________________________________
>> From: "STARK, BARBARA H" <bs7652@att.com>
>> To: Hemant Singh (shemant) <shemant@cisco.com>; Mark ZZZ Smith
>> <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@innovationslab.net>;
>> "ipv6@ietf.org" <ipv6@ietf.org>
>> Sent: Wednesday, 1 April 2015, 0:24
>> Subject: RE: RA Option Guidelines
>>
>>
>>
>>> The problem that Mark  raised and also provided a solution for is to add
>>> DHCPv6 relay functionality to the CE router.  He is also correct that RFC
>>> 6204
>>> does not include DHCPv6 relay agent functionality in the CE router.
>>>
>>> The other choice for a solution is to include the DHCPv6 options in the
>>> RA.
>>> For this solution to work the SP will send new DHCPv6 options in the RA to
>>> the CE router WAN.  The RA terminates at the CE WAN.  The CE generates a
>>> new RA for the LAN.  RFC 6204 does not include functionality to bridge the
>>> SP
>>> RA received on the CE WAN to the CE LAN.  So even for the RA solution to
>>> work, a new requirement would need to be added to RFC 6204.  Did I miss
>>> anything in the RA solution I described above?  If not, either way, one
>>> adds a
>>> new requirement to the CE router and if it's DHCPv6 options, let DHCPv6
>>> protocol deal with it.
>>
>>
>> RFC 7084 already says:
>>   L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>>           options (as listed in Section 5.3 of [RFC3736]) received from
>>           the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>>           server.
>> Where the RFC3736 list of options is for DNS Recursive Name Servers, DNS
>> search list, and SIP Servers.
>>
>> My personal, as-a-consumer, freaking-out-about-privacy opinion is that the
>> idea of my ISPs (both of them, but potentially 3) sending any configuration
>> options they feel like down to my personal and private LAN host devices is
>> not to my liking. I realize that some people are blithely happy to turn over
>> their privacy to ISPs. So maybe relay of all unrecognized options could be
>> something an ISP puts into CE routers they supply to their customers. I
>> prefer for it not to be in the retail ones I purchase, and I would be
>> adamant about it not being on by default in such retail CE routers. So let
>> such relay requirements go into eRouter or BBF specs, but please keep them
>> out of IETF and homenet specs.
>>
>> / I think you're already trusting your ISP possibly much more than you might
>> realise. They're already supplying you with the Internet addressing you use,
>> you're probably using their DNS resolvers, you may be using their email
>> servers, and of course they can tap your clear text traffic without you
>> knowing.
>>
>> / Even if you only used their addressing and encrypted all of your traffic
>> over a tunnel through their infrastructure, you'd still then be trusting the
>> remote tunnel endpoint provider, likely to be another party other than
>> yourself.
>>
>> Since I'm in the process of setting up my new homenet router (Pierre flashed
>> my new router for me last week) to connect upstream to both my ISPs (one
>> cable provider and one telco), I also really don't want dueling relayed
>> options reaching my LAN hosts. I do think that in the future a significant
>> number of people will choose to subscribe to multiple providers -- as long
>> as it's easy to do. The ISPs get to configure the CE router WAN interfaces
>> to work with their access networks -- and that needs to be the extent of
>> their reach unless I specifically give them conscious permission to do more.
>> If they want to configure devices inside my LAN, I think they should use a
>> higher layer configuration protocol with mandatory and default-on security
>> (which neither RA nor DHCPv6 have).
>>
>> / So I think the world is moving in the other direction. People have been
>> outsourcing the maintenance of their devices in droves as they adopt
>> smartphones and tablets, and more recently with devices like Google's
>> Chromebooks. They're giving up control rather than desiring more of it, for
>> the gains of more convenience and lower costs.
>>
>> / Regards,
>> Mark.
>>
>>
>> Barbara
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>


From nobody Thu Apr  2 19:20:14 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 912CD1A9046 for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 19:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.502
X-Spam-Level: 
X-Spam-Status: No, score=0.502 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 vbQW5Iex-C_n for <ipv6@ietfa.amsl.com>; Thu,  2 Apr 2015 19:20:09 -0700 (PDT)
Received: from nm41.bullet.mail.bf1.yahoo.com (nm41.bullet.mail.bf1.yahoo.com [216.109.114.57]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C34E1A9036 for <ipv6@ietf.org>; Thu,  2 Apr 2015 19:20:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428027608; bh=6fum53iXnEcCXuXsVFLMKRo22Ja9MCw1eRCMsiOKqAM=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=TshDh724wYl7OGSNDnqwb3IXp/vTh+DOyGH9MUcLOyPjdepRrZ6aN9Dp2Y6PEK4dyCYPlo9avJFB5FjFHgn9bqTeO/s/1amj+qjthpz7SvakCnQ2x277GlSp7TmhDovuLcH6ibQkrBmQVtOxUduq9H8Vw0g6Ozv4+RuKtLCd71Yxl8tODUmnyWyiJ3uMb74t8p+wATXunZPihUPL/OAqlSIHG6pK0JMnvVivJIadlGIi5yo1o8QV6xk5l1oPun8IFSBKt21USf8t5fKYtfPwii/ii2yMOMWu+4WO2OF/fUnm8HVSODwe+sJw2vPad2G8/Xf7GzW0zKhbDUMRFXEFXw==
Received: from [98.139.170.182] by nm41.bullet.mail.bf1.yahoo.com with NNFMP;  03 Apr 2015 02:20:08 -0000
Received: from [98.139.212.198] by tm25.bullet.mail.bf1.yahoo.com with NNFMP;  03 Apr 2015 02:19:08 -0000
Received: from [127.0.0.1] by omp1007.mail.bf1.yahoo.com with NNFMP; 03 Apr 2015 02:19:08 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 158252.90413.bm@omp1007.mail.bf1.yahoo.com
X-YMail-OSG: e6s1qEsVM1lATAf6rMR_Qf9K4t5JLwRft_34eRdRtNPjS6UXyW3KFuisP6KBSZS MUHTUAa_Dha0RrAz2CkGp422YHII01sLqMzaEJZUtygMJNywjpazU8PZzBu3j5_cQw7ecARs7l0d Kxn7X0GbjlutWKhsCbe67R0cO0LDobEKzm3iuHUSIgodCj4DiVZHW0Nxbq3iPomSfT4OuM22xzUc 6mK6zP_kzBceuBjo2u7_pDdpd9Yv6CTCHUkhHSoOs5_A29ohI7XpLE1as6GAOTbgRPWyxT8r3XCB g5p5TySXB61IRRKUuRmJra0C_u34HpGdjaPgyPWQhnoPE8tA0po0CKYvfrGGfJ_3E8yLeXwSnntU 7AdB59kfFR3SqHwKsuLR2ptQrF14bQI9GD_Uh5ZVNCoRTugKp8E2Y65GDikTG3iCXFkLEyZZnt22 0I0PZWvNl.ZnOx0LqBZMSbPrmXXTJea3h6NYvqwFXGszjMllFKNdz9vRM29ImelJDQicszNovL9T llqxXVztuTDzECModonH4bxXRjFd1nRPlJwuE9pok
Received: by 66.196.80.150; Fri, 03 Apr 2015 02:19:07 +0000 
Date: Fri, 3 Apr 2015 02:19:06 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,  "STARK, BARBARA H" <bs7652@att.com>,  Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_4941872_1627707809.1428027546689"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4o6Ozg72-gxPYEZa40mB1PltpFU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 02:20:12 -0000

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

Hi Hemant,


________________________________
 From: Hemant Singh (shemant) <shemant@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs7652@=
att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@=
ietf.org>=20
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines
=20


Mark,
=C2=A0
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.=C2=A0=C2=A0 Read the first paragraph of section 5.=
3 in RFC3736.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.

/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration=C2=A0information to clients; note that othe=
r options for configuration=C2=A0information may be specified in future Int=
ernet Standards:" reads to me like a later version of this RFC will specify=
 more stateless DHCPv6 server supported options. A statement such as=C2=A0"=
Other additional DHCPv6 options appropriate for stateless DHCPv6 operation =
may be supported by an implementation." would make it much clearer that the=
 supported options were up to the implementer once the minimum had been imp=
lemented.
/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.
=C2=A0 So the new options you want to serve can be served by the CE statele=
ss DHCPv6 server.=C2=A0 =C2=A0Now, if the service provider configures his/h=
er DHCPv6 server to return new options to the CE WAN interface address acqu=
isition, the CE uses the options on the LAN.=C2=A0 See bullet L-12 of RFC 7=
084.=C2=A0 Existing RFCs support your use case and no dhcpv6 relay is requi=
red in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.
/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.
/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.
/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).
/ Regards,/ Mark.
=C2=A0Barbara,
=C2=A0
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.=C2=A0 Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.
=C2=A0=20
Both use cases can be supported using existing RFC=E2=80=99s.
=C2=A0
Hemant
=C2=A0


From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org
Subject: Re: RA Option Guidelines
=C2=A0
Hi Hemant,
=C2=A0

________________________________
=20
From:Hemant Singh (shemant) <shemant@cisco.com>
To: "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@yahoo=
.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@=
ietf.org>=20
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.=C2=A0 =C2=A0=20

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.=C2=A0 Then the=
 CPE includes the new option to its LAN DHCPv6 clients.
=C2=A0
/ =C2=A0So here is a scenario.
=C2=A0
/ As an ISP, my customers have VoIP handsets that might support the=C2=A0OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to an updated RFC3736 and RFC7084, to g=
et my CPE vendor to update and release their firmware to support that optio=
n, and test that new CPE firmware and then to deploy that new firmware?
=C2=A0
/ I think I'd be lucky if it only took 2 years.
=C2=A0
/ A few months later I decide I want to provide=C2=A0OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated=C2=A0RFC3736, to get my CPE =
vendor to update and release their firmware to support that option, and tes=
t that new CPE firmware and then to deploy that new firmware.
=C2=A0
/ Now if I'm lucky I could add it to the draft for=C2=A0OPTION_GEOLOCATION,=
 so it is still "only" 2 years to get to a point where I could provide thos=
e options to my customers. But what if that draft has progressed too far th=
ough the IETF publishing process? I have to create a new draft updating the=
 to be published draft.
=C2=A0
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...
=C2=A0
=C2=A0What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? =C2=A0

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
 there is a new DHCPv6 option defined that might be useful to me and them. =
I want to be able to provide service parameters to my customers hosts, dire=
ctly or indirectly, without the software revision or model of their CPE bei=
ng the constraint.

The SIP server is already included as one option supported by RFC3736.=C2=
=A0 Certainly, if the SIP server support is needed in the RA, I am open for=
 it since the RA already includes DNS information.
=C2=A0
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.
=C2=A0
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.=C2=A0
=C2=A0
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?=C2=A0 At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on the LAN of the CE router.
=C2=A0
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?=C2=A0 RFC4861 specifies a T=
LV format and an option Type.=C2=A0 I don't see anything else needed if I n=
eed to specify a new RA option.=20

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]=20
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org
Subject: RE: RA Option Guidelines
=C2=A0



RFC 7084 already says:=20
=C2=A0 L-12:=C2=A0 The IPv6 CE router SHOULD make available a subset of DHC=
Pv6
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 options (as listed in Section 5.3 of [RF=
C3736]) received from
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 server.
------=_Part_4941872_1627707809.1428027546689
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px">Hi Hemant,<br><br><br>__________=
______________________<br> From: Hemant Singh (shemant) &lt;shemant@cisco.c=
om&gt;<br>To: Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt;; "STARK, BAR=
BARA H" &lt;bs7652@att.com&gt;; Brian Haberman &lt;brian@innovationslab.net=
&gt;; "ipv6@ietf.org" &lt;ipv6@ietf.org&gt; <br>Sent: Friday, 3 April 2015,=
 6:07<br>Subject: RE: RA Option Guidelines<br> <br><br><br>Mark,<br>&nbsp;<=
br>The stateless DHCPv6 server in RFC3736 allows for new options to be serv=
ed by the stateless server.&nbsp;&nbsp; Read the first paragraph of section=
 5.3 in RFC3736.<br><br>/ So there are a few reasons why I wouldn't come to=
 that conclusion without some very careful reading:<br><br>/ - The explicit=
ly identified set of required and optional DHCPv6 options that can be suppo=
rted by a stateless DHCPv6 server<br><br>/ - The lack of any overt discussi=
on that this set of required and optional DHCPv6 options are a minimum, and=
 that further DHCPv6 options could be provided by a stateless DHCPv6 server=
 if supported by the implementation, are appropriate and requested by the c=
lient. It being a minimum is subtly eluded to in a few sentences in the Abs=
tract and the Introduction, however I think they could easily be missed. I'=
d expect that if this is the case, it is much clearer and obvious.<br><br><=
div dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_61004">/ - I think text yo=
u refer to in 5.3, "<span style=3D"font-family: 'Helvetica Neue-Light', 'He=
lvetica Neue Light', 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', s=
ans-serif; font-size: 16px;" id=3D"yui_3_16_0_1_1428018555944_60471">Client=
s and servers use the following options to pass configuration&nbsp;</span><=
span style=3D"font-family: 'Helvetica Neue-Light', 'Helvetica Neue Light', =
'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size:=
 16px;" id=3D"yui_3_16_0_1_1428018555944_60560">information to clients; not=
e that other options for configuration&nbsp;</span><span style=3D"font-fami=
ly: 'Helvetica Neue-Light', 'Helvetica Neue Light', 'Helvetica Neue', Helve=
tica, Arial, 'Lucida Grande', sans-serif; font-size: 16px;" id=3D"yui_3_16_=
0_1_1428018555944_60463">information may be specified in future Internet St=
andards:" reads to me like a later version of this RFC will specify more st=
ateless DHCPv6 server supported options. A statement such as&nbsp;</span>"O=
ther additional DHCPv6 options appropriate for stateless DHCPv6 operation m=
ay be supported by an implementation." would make it much clearer that the =
supported options were up to the implementer once the minimum had been impl=
emented.</div><br><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60546">=
/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.</div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60546"><br></div=
><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60546">&nbsp; So the new=
 options you want to serve can be served by the CE stateless DHCPv6 server.=
&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 server =
to return new options to the CE WAN interface address acquisition, the CE u=
ses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Existi=
ng RFCs support your use case and no dhcpv6 relay is required in the CE.<br=
></div><div id=3D"yui_3_16_0_1_1428018555944_60638"><br></div><div dir=3D"l=
tr" id=3D"yui_3_16_0_1_1428018555944_60642">/ I also cannot find text in RF=
C3315 or its updates on how to handle received options that were not reques=
ted by the client in the Option Request Option. So if the CE WAN DHCPv6 cli=
ent doesn't request an option in its ORO to the SP's DHCPv6 server, I don't=
 think it is possible for the CE to pass options it doesn't know about onto=
 the downstream LAN devices that do understand those DHCPv6 options.</div><=
div dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60642"><br></div><div dir=
=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60642">/ If it is possible to sen=
d a DHCPv6 client "ORO type" options that it didn't request, then the behav=
iour is still ambiguous. If the DHCPv6 client is a host, then it would be q=
uite reasonable and expected to silently ignore those received unknown opti=
ons. However, if the DHCPv6 client is on the WAN side of a CE device, then =
those options should instead be passed to the LAN DHCPv6 server, which pres=
umably should know how to correctly handle options it doesn't understand - =
in the specific CE case, remember those options in case a downstream LAN DH=
CPv6 client requests them. I think RFC7084 and it's ancestor RFC6204 are th=
e only RFCs which describe this combination of DHCPv6 client/server working=
 together, and neither of them have discussed passing unknown options from =
the DHCPv6 WAN client to the DHCPv6 LAN server.</div><div dir=3D"ltr" id=3D=
"yui_3_16_0_1_1428018555944_60642"><br></div><div dir=3D"ltr" id=3D"yui_3_1=
6_0_1_1428018555944_60642">/ Are you aware of any CE DHCPv6 WAN client/DHCP=
v6 LAN server implementations that are unknown DHCPv6 option transparent? L=
ooking at RFC7084, this behaviour seems to be very explicitly prohibited, b=
y limiting the LAN DHCPv6 server support to only those options described in=
 RFC7084, or to those described in RFC3736.</div><div dir=3D"ltr" id=3D"yui=
_3_16_0_1_1428018555944_60642"><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_=
1_1428018555944_60642">/ I think this level of DHCPv6 option transparency b=
etween CE LAN attached hosts and the upstream SP's DHCPv6 server(s) can onl=
y be achieved by using a DHCPv6 relay on the CE LAN interface, because DHCP=
v6 relays are DHCPv6 option transparent. (A CE would still have a DHCPv6 cl=
ient on its WAN interface for its own parameters and DHCPv6-PD prefixes).</=
div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60642"><br></div><div=
 dir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60642">/ Regards,</div><div d=
ir=3D"ltr" id=3D"yui_3_16_0_1_1428018555944_60642">/ Mark.</div><div dir=3D=
"ltr" id=3D"yui_3_16_0_1_1428018555944_60642"><br></div><div id=3D"yui_3_16=
_0_1_1428018555944_60751">&nbsp;</div>Barbara,<br>&nbsp;<br>For your use ca=
se, the service provider configures the DHCPv6 server to only serve options=
 specified in RFC 7084.&nbsp; Thus in this deployment no extra options exis=
t to serve to the CE router LAN.<br>&nbsp; <br>Both use cases can be suppor=
ted using existing RFC=E2=80=99s.<br>&nbsp;<br>Hemant<br>&nbsp;<br><br><br>=
From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au] <br>Sent: Tuesday, M=
arch 31, 2015 9:52 PM<br>To: Hemant Singh (shemant); STARK, BARBARA H; Bria=
n Haberman; ipv6@ietf.org<br>Subject: Re: RA Option Guidelines<br>&nbsp;<br=
>Hi Hemant,<br>&nbsp;<br><br>________________________________<br> <br>From:=
Hemant Singh (shemant) &lt;shemant@cisco.com&gt;<br>To: "STARK, BARBARA H" =
&lt;bs7652@att.com&gt;; Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt;; B=
rian Haberman &lt;brian@innovationslab.net&gt;; "ipv6@ietf.org" &lt;ipv6@ie=
tf.org&gt; <br>Sent: Wednesday, 1 April 2015, 1:27<br>Subject: RE: RA Optio=
n Guidelines<br><br>Barbara,<br><br>Thanks for replying.&nbsp; &nbsp; <br><=
br>Mark,<br><br>If new DHCPv6 options are added to be supported by RFC3736,=
 then the SP includes the new option in the DHCPv6 responses to the CPE WAN=
.&nbsp; Then the CPE includes the new option to its LAN DHCPv6 clients.<br>=
&nbsp;<br>/ &nbsp;So here is a scenario.<br>&nbsp;<br>/ As an ISP, my custo=
mers have VoIP handsets that might support the&nbsp;OPTION_GEOLOCATION DHCP=
v6 option (I might know that a portion of them do, because they've bought t=
hose VoIP handsets from me). How long is it going to take for me to get tha=
t option added to an updated RFC3736 and RFC7084, to get my CPE vendor to u=
pdate and release their firmware to support that option, and test that new =
CPE firmware and then to deploy that new firmware?<br>&nbsp;<br>/ I think I=
'd be lucky if it only took 2 years.<br>&nbsp;<br>/ A few months later I de=
cide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZONE to my customers if th=
eir hosts request it. So now I have to try to get OPTION_NEW_POSIX_TIMEZONE=
 added to the updated&nbsp;RFC3736, to get my CPE vendor to update and rele=
ase their firmware to support that option, and test that new CPE firmware a=
nd then to deploy that new firmware.<br>&nbsp;<br>/ Now if I'm lucky I coul=
d add it to the draft for&nbsp;OPTION_GEOLOCATION, so it is still "only" 2 =
years to get to a point where I could provide those options to my customers=
. But what if that draft has progressed too far though the IETF publishing =
process? I have to create a new draft updating the to be published draft.<b=
r>&nbsp;<br>/ So, to achieve what should be a simple task of providing loca=
tion or timezone information to customers' end hosts if they want it, we've=
 just incurred the massive costs and time delays of the IETF publishing pro=
cess, vendor firmware upgrades, firmware testing and firmware deployment. S=
ounds like how hard I understand it was to roll out features like CLI in PS=
TN networks ...<br>&nbsp;<br>&nbsp;What is one option you'd like the host o=
n the LAN to include so that we can understand your use case better? &nbsp;=
<br><br>/ I'm going to make the problem much harder for you. I want the CPE=
 to "support" or better, be transparent to, all current and future DHCPv6 o=
ptions, and I don't want to have to upgrade or ask my customers to successf=
ully upgrade their CPE each and every time<br> there is a new DHCPv6 option=
 defined that might be useful to me and them. I want to be able to provide =
service parameters to my customers hosts, directly or indirectly, without t=
he software revision or model of their CPE being the constraint.<br><br>The=
 SIP server is already included as one option supported by RFC3736.&nbsp; C=
ertainly, if the SIP server support is needed in the RA, I am open for it s=
ince the RA already includes DNS information.<br>&nbsp;<br>/ I don't think =
DNS in RAs was a good idea, and neither were SIP options when they were pro=
posed. See that time consuming and service disrupting firmware upgrade cycl=
e for new DHCPv6 options? Same problem if you use RA options to achieve the=
 same goal. New firmware upgrade each time you want to support a new RA opt=
ion.<br>&nbsp;<br>/ Duplication between RA options and DHCPv6 options also =
causes more problems. Which is preferred? Are they treated equally or does =
one take precedence over the other? As far as I'm aware, these questions ha=
ven't been answered for the DHCPv6 DNS and RA DNS options yet. It might be =
simple to come up with a simple rule for more DHCPv6 options are duplicated=
 into RAs, however their might be some specific cases where the RA option v=
alue should be preferred over the DHCPv6 equivalent option and vice-versa.&=
nbsp;<br>&nbsp;<br>However, I still ask the question as to how an RA receiv=
ed at the WAN of the CPE has its options propagated to the RA on the LAN?&n=
bsp; At the time of writing RFC 6204 or RFC 7084, there is no such provisio=
n between the RA received on the WAN and the RA issued on the LAN of the CE=
 router.<br>&nbsp;<br>/ Use a DHCPv6 relay in the CPE. Then there isn't a p=
roblem, new DHCPv6 options that are unknown by the CPE will pass right thro=
ugh it transparently. The only complication is when stateful DHCPv6 address=
ing is used on the CPE LAN interface, and I suggested a hybrid mode of oper=
ation for a DHCPv6 server in that draft which I think solves that problem.<=
br><br>Others,<br><br>Also, why does one need an RA Option Guideline?&nbsp;=
 RFC4861 specifies a TLV format and an option Type.&nbsp; I don't see anyth=
ing else needed if I need to specify a new RA option. <br><br>Thanks,<br><b=
r>Hemant<br><br>-----Original Message-----<br>From: STARK, BARBARA H [mailt=
o:bs7652@att.com] <br>Sent: Tuesday, March 31, 2015 9:25 AM<br>To: Hemant S=
ingh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<br>Subject: R=
E: RA Option Guidelines<br>&nbsp;<br><br><br><br>RFC 7084 already says: <br=
>&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DH=
CPv6<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.=
3 of [RFC3736]) received from<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHC=
Pv6 client on its WAN interface to its LAN-side DHCPv6<br>&nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; server.</div></body></html>
------=_Part_4941872_1627707809.1428027546689--


From nobody Fri Apr  3 04:09:59 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 179C11A87E6 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DZp2OYnSVGz for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:09:53 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59DBF1A8784 for <ipv6@ietf.org>; Fri,  3 Apr 2015 04:09:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41734; q=dns/txt; s=iport; t=1428059395; x=1429268995; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=J5RRiw23oA3G+4nbDbACjB97zjKS4Tss6eHQv9ZzhgE=; b=PbPADUrBTqXQo9uwdUJEH3pEi+sOQtk8LSccVXv7PUodBS8xjW7Q+P9i 3eMEuSZqFYeIFcpFdEjG4rBTPLMcA27ANPluxK/JTDspBHRUE/tl2mL3P v4tsPdyVLurZ2KSfGA3N9sgl3++nhPmWQkz6QEIPo/UVovJrp8oTUnv13 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AyDQBtdB5V/5BdJa1cgkhDUlwFgxDFDoNKAhyBEEwBAQEBAQF+hB4BAQEEGgkKTAwEAgEIEQQBAQsWBwMCAgIwFAkIAgQBDQUIiBMDEbQ6mB0BAQEBAQEBAQEBAQEBAQEBAQEBAQEXiymCR4FnCREWGwYBBoJiL4EWBYUQColBgg+IOYJkgzWCYIYcToJng0gig29vgQRAfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="408932449"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-5.cisco.com with ESMTP; 03 Apr 2015 11:09:52 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t33B9p5F023956 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 11:09:51 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 06:09:50 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, "STARK, BARBARA H" <bs7652@att.com>, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sA==
Date: Fri, 3 Apr 2015 11:09:50 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.158]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B8916838870xmbrcdx06ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AN9sCI7voDUyEmC979RGlSqzySc>
Cc: Ted Lemon <Ted.Lemon@nominum.com>, "Bernie Volz \(volz\)" <volz@cisco.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 11:09:58 -0000

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

Q291bGQgdGhlIERIQ1B2NiBndXJ1cyBpbiBSYWxwaCwgQmVybmllLCBhbmQgVGVkIHBsZWFzZSBo
ZWxwIHJlc29sdmUgdGhpcyB0aHJlYWQgZm9yIHN0YXRlbGVzcyBESENQdjYgY3VycmVudCB2cy4g
ZnV0dXJlIG9wdGlvbnMgYW5kIHRoZSBPUk8gb3B0aW9uLg0KDQpUaGFua3MsDQoNCkhlbWFudA0K
DQpGcm9tOiBNYXJrIFpaWiBTbWl0aCBbbWFpbHRvOm1hcmt6enpzbWl0aEB5YWhvby5jb20uYXVd
DQpTZW50OiBUaHVyc2RheSwgQXByaWwgMDIsIDIwMTUgMTA6MTkgUE0NClRvOiBIZW1hbnQgU2lu
Z2ggKHNoZW1hbnQpOyBTVEFSSywgQkFSQkFSQSBIOyBCcmlhbiBIYWJlcm1hbjsgaXB2NkBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IFJBIE9wdGlvbiBHdWlkZWxpbmVzDQoNCkhpIEhlbWFudCwNCg0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogSGVtYW50IFNpbmdoIChz
aGVtYW50KSA8c2hlbWFudEBjaXNjby5jb208bWFpbHRvOnNoZW1hbnRAY2lzY28uY29tPj4NClRv
OiBNYXJrIFpaWiBTbWl0aCA8bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdTxtYWlsdG86bWFya3p6
enNtaXRoQHlhaG9vLmNvbS5hdT4+OyAiU1RBUkssIEJBUkJBUkEgSCIgPGJzNzY1MkBhdHQuY29t
PG1haWx0bzpiczc2NTJAYXR0LmNvbT4+OyBCcmlhbiBIYWJlcm1hbiA8YnJpYW5AaW5ub3ZhdGlv
bnNsYWIubmV0PG1haWx0bzpicmlhbkBpbm5vdmF0aW9uc2xhYi5uZXQ+PjsgImlwdjZAaWV0Zi5v
cmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+IiA8aXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRm
Lm9yZz4+DQpTZW50OiBGcmlkYXksIDMgQXByaWwgMjAxNSwgNjowNw0KU3ViamVjdDogUkU6IFJB
IE9wdGlvbiBHdWlkZWxpbmVzDQoNCg0KDQpNYXJrLA0KDQpUaGUgc3RhdGVsZXNzIERIQ1B2NiBz
ZXJ2ZXIgaW4gUkZDMzczNiBhbGxvd3MgZm9yIG5ldyBvcHRpb25zIHRvIGJlIHNlcnZlZCBieSB0
aGUgc3RhdGVsZXNzIHNlcnZlci4gICBSZWFkIHRoZSBmaXJzdCBwYXJhZ3JhcGggb2Ygc2VjdGlv
biA1LjMgaW4gUkZDMzczNi4NCg0KLyBTbyB0aGVyZSBhcmUgYSBmZXcgcmVhc29ucyB3aHkgSSB3
b3VsZG4ndCBjb21lIHRvIHRoYXQgY29uY2x1c2lvbiB3aXRob3V0IHNvbWUgdmVyeSBjYXJlZnVs
IHJlYWRpbmc6DQoNCi8gLSBUaGUgZXhwbGljaXRseSBpZGVudGlmaWVkIHNldCBvZiByZXF1aXJl
ZCBhbmQgb3B0aW9uYWwgREhDUHY2IG9wdGlvbnMgdGhhdCBjYW4gYmUgc3VwcG9ydGVkIGJ5IGEg
c3RhdGVsZXNzIERIQ1B2NiBzZXJ2ZXINCg0KLyAtIFRoZSBsYWNrIG9mIGFueSBvdmVydCBkaXNj
dXNzaW9uIHRoYXQgdGhpcyBzZXQgb2YgcmVxdWlyZWQgYW5kIG9wdGlvbmFsIERIQ1B2NiBvcHRp
b25zIGFyZSBhIG1pbmltdW0sIGFuZCB0aGF0IGZ1cnRoZXIgREhDUHY2IG9wdGlvbnMgY291bGQg
YmUgcHJvdmlkZWQgYnkgYSBzdGF0ZWxlc3MgREhDUHY2IHNlcnZlciBpZiBzdXBwb3J0ZWQgYnkg
dGhlIGltcGxlbWVudGF0aW9uLCBhcmUgYXBwcm9wcmlhdGUgYW5kIHJlcXVlc3RlZCBieSB0aGUg
Y2xpZW50LiBJdCBiZWluZyBhIG1pbmltdW0gaXMgc3VidGx5IGVsdWRlZCB0byBpbiBhIGZldyBz
ZW50ZW5jZXMgaW4gdGhlIEFic3RyYWN0IGFuZCB0aGUgSW50cm9kdWN0aW9uLCBob3dldmVyIEkg
dGhpbmsgdGhleSBjb3VsZCBlYXNpbHkgYmUgbWlzc2VkLiBJJ2QgZXhwZWN0IHRoYXQgaWYgdGhp
cyBpcyB0aGUgY2FzZSwgaXQgaXMgbXVjaCBjbGVhcmVyIGFuZCBvYnZpb3VzLg0KLyAtIEkgdGhp
bmsgdGV4dCB5b3UgcmVmZXIgdG8gaW4gNS4zLCAiQ2xpZW50cyBhbmQgc2VydmVycyB1c2UgdGhl
IGZvbGxvd2luZyBvcHRpb25zIHRvIHBhc3MgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlvbiB0byBj
bGllbnRzOyBub3RlIHRoYXQgb3RoZXIgb3B0aW9ucyBmb3IgY29uZmlndXJhdGlvbiBpbmZvcm1h
dGlvbiBtYXkgYmUgc3BlY2lmaWVkIGluIGZ1dHVyZSBJbnRlcm5ldCBTdGFuZGFyZHM6IiByZWFk
cyB0byBtZSBsaWtlIGEgbGF0ZXIgdmVyc2lvbiBvZiB0aGlzIFJGQyB3aWxsIHNwZWNpZnkgbW9y
ZSBzdGF0ZWxlc3MgREhDUHY2IHNlcnZlciBzdXBwb3J0ZWQgb3B0aW9ucy4gQSBzdGF0ZW1lbnQg
c3VjaCBhcyAiT3RoZXIgYWRkaXRpb25hbCBESENQdjYgb3B0aW9ucyBhcHByb3ByaWF0ZSBmb3Ig
c3RhdGVsZXNzIERIQ1B2NiBvcGVyYXRpb24gbWF5IGJlIHN1cHBvcnRlZCBieSBhbiBpbXBsZW1l
bnRhdGlvbi4iIHdvdWxkIG1ha2UgaXQgbXVjaCBjbGVhcmVyIHRoYXQgdGhlIHN1cHBvcnRlZCBv
cHRpb25zIHdlcmUgdXAgdG8gdGhlIGltcGxlbWVudGVyIG9uY2UgdGhlIG1pbmltdW0gaGFkIGJl
ZW4gaW1wbGVtZW50ZWQuDQoNCi8gU28gaWYgSSB3ZXJlIGltcGxlbWVudGluZyBhIHN0YXRlbGVz
cyBESENQdjYgc2VydmVyIGFzIHBlciBSRkMzNzM2LCBJJ2QgdGhpbmsgdGhlIGltcGxlbWVudGF0
aW9uIHdhcyBjb21wbGV0ZSB3aGVuIEkgaGFkIGltcGxlbWVudGVkIHRoZSBvcHRpb25zIHNwZWNp
ZmllZC4gSSB3b3VsZG4ndCBwdXQgYW55IGVmZm9ydCBpbnRvIG1ha2luZyBpdCBhbHNvIHRyYW5z
cGFyZW50IHRvIGFueSBvcHRpb25zIHRoYXQgd2VyZW4ndCBpZGVudGlmaWVkIGluIFJGQzM3MzYs
IGFzIHRoZXJlIGlzIG5vIHRleHQgZGlzY3Vzc2luZyB0aGF0Lg0KDQogIFNvIHRoZSBuZXcgb3B0
aW9ucyB5b3Ugd2FudCB0byBzZXJ2ZSBjYW4gYmUgc2VydmVkIGJ5IHRoZSBDRSBzdGF0ZWxlc3Mg
REhDUHY2IHNlcnZlci4gICBOb3csIGlmIHRoZSBzZXJ2aWNlIHByb3ZpZGVyIGNvbmZpZ3VyZXMg
aGlzL2hlciBESENQdjYgc2VydmVyIHRvIHJldHVybiBuZXcgb3B0aW9ucyB0byB0aGUgQ0UgV0FO
IGludGVyZmFjZSBhZGRyZXNzIGFjcXVpc2l0aW9uLCB0aGUgQ0UgdXNlcyB0aGUgb3B0aW9ucyBv
biB0aGUgTEFOLiAgU2VlIGJ1bGxldCBMLTEyIG9mIFJGQyA3MDg0LiAgRXhpc3RpbmcgUkZDcyBz
dXBwb3J0IHlvdXIgdXNlIGNhc2UgYW5kIG5vIGRoY3B2NiByZWxheSBpcyByZXF1aXJlZCBpbiB0
aGUgQ0UuDQoNCi8gSSBhbHNvIGNhbm5vdCBmaW5kIHRleHQgaW4gUkZDMzMxNSBvciBpdHMgdXBk
YXRlcyBvbiBob3cgdG8gaGFuZGxlIHJlY2VpdmVkIG9wdGlvbnMgdGhhdCB3ZXJlIG5vdCByZXF1
ZXN0ZWQgYnkgdGhlIGNsaWVudCBpbiB0aGUgT3B0aW9uIFJlcXVlc3QgT3B0aW9uLiBTbyBpZiB0
aGUgQ0UgV0FOIERIQ1B2NiBjbGllbnQgZG9lc24ndCByZXF1ZXN0IGFuIG9wdGlvbiBpbiBpdHMg
T1JPIHRvIHRoZSBTUCdzIERIQ1B2NiBzZXJ2ZXIsIEkgZG9uJ3QgdGhpbmsgaXQgaXMgcG9zc2li
bGUgZm9yIHRoZSBDRSB0byBwYXNzIG9wdGlvbnMgaXQgZG9lc24ndCBrbm93IGFib3V0IG9udG8g
dGhlIGRvd25zdHJlYW0gTEFOIGRldmljZXMgdGhhdCBkbyB1bmRlcnN0YW5kIHRob3NlIERIQ1B2
NiBvcHRpb25zLg0KDQovIElmIGl0IGlzIHBvc3NpYmxlIHRvIHNlbmQgYSBESENQdjYgY2xpZW50
ICJPUk8gdHlwZSIgb3B0aW9ucyB0aGF0IGl0IGRpZG4ndCByZXF1ZXN0LCB0aGVuIHRoZSBiZWhh
dmlvdXIgaXMgc3RpbGwgYW1iaWd1b3VzLiBJZiB0aGUgREhDUHY2IGNsaWVudCBpcyBhIGhvc3Qs
IHRoZW4gaXQgd291bGQgYmUgcXVpdGUgcmVhc29uYWJsZSBhbmQgZXhwZWN0ZWQgdG8gc2lsZW50
bHkgaWdub3JlIHRob3NlIHJlY2VpdmVkIHVua25vd24gb3B0aW9ucy4gSG93ZXZlciwgaWYgdGhl
IERIQ1B2NiBjbGllbnQgaXMgb24gdGhlIFdBTiBzaWRlIG9mIGEgQ0UgZGV2aWNlLCB0aGVuIHRo
b3NlIG9wdGlvbnMgc2hvdWxkIGluc3RlYWQgYmUgcGFzc2VkIHRvIHRoZSBMQU4gREhDUHY2IHNl
cnZlciwgd2hpY2ggcHJlc3VtYWJseSBzaG91bGQga25vdyBob3cgdG8gY29ycmVjdGx5IGhhbmRs
ZSBvcHRpb25zIGl0IGRvZXNuJ3QgdW5kZXJzdGFuZCAtIGluIHRoZSBzcGVjaWZpYyBDRSBjYXNl
LCByZW1lbWJlciB0aG9zZSBvcHRpb25zIGluIGNhc2UgYSBkb3duc3RyZWFtIExBTiBESENQdjYg
Y2xpZW50IHJlcXVlc3RzIHRoZW0uIEkgdGhpbmsgUkZDNzA4NCBhbmQgaXQncyBhbmNlc3RvciBS
RkM2MjA0IGFyZSB0aGUgb25seSBSRkNzIHdoaWNoIGRlc2NyaWJlIHRoaXMgY29tYmluYXRpb24g
b2YgREhDUHY2IGNsaWVudC9zZXJ2ZXIgd29ya2luZyB0b2dldGhlciwgYW5kIG5laXRoZXIgb2Yg
dGhlbSBoYXZlIGRpc2N1c3NlZCBwYXNzaW5nIHVua25vd24gb3B0aW9ucyBmcm9tIHRoZSBESENQ
djYgV0FOIGNsaWVudCB0byB0aGUgREhDUHY2IExBTiBzZXJ2ZXIuDQoNCi8gQXJlIHlvdSBhd2Fy
ZSBvZiBhbnkgQ0UgREhDUHY2IFdBTiBjbGllbnQvREhDUHY2IExBTiBzZXJ2ZXIgaW1wbGVtZW50
YXRpb25zIHRoYXQgYXJlIHVua25vd24gREhDUHY2IG9wdGlvbiB0cmFuc3BhcmVudD8gTG9va2lu
ZyBhdCBSRkM3MDg0LCB0aGlzIGJlaGF2aW91ciBzZWVtcyB0byBiZSB2ZXJ5IGV4cGxpY2l0bHkg
cHJvaGliaXRlZCwgYnkgbGltaXRpbmcgdGhlIExBTiBESENQdjYgc2VydmVyIHN1cHBvcnQgdG8g
b25seSB0aG9zZSBvcHRpb25zIGRlc2NyaWJlZCBpbiBSRkM3MDg0LCBvciB0byB0aG9zZSBkZXNj
cmliZWQgaW4gUkZDMzczNi4NCg0KLyBJIHRoaW5rIHRoaXMgbGV2ZWwgb2YgREhDUHY2IG9wdGlv
biB0cmFuc3BhcmVuY3kgYmV0d2VlbiBDRSBMQU4gYXR0YWNoZWQgaG9zdHMgYW5kIHRoZSB1cHN0
cmVhbSBTUCdzIERIQ1B2NiBzZXJ2ZXIocykgY2FuIG9ubHkgYmUgYWNoaWV2ZWQgYnkgdXNpbmcg
YSBESENQdjYgcmVsYXkgb24gdGhlIENFIExBTiBpbnRlcmZhY2UsIGJlY2F1c2UgREhDUHY2IHJl
bGF5cyBhcmUgREhDUHY2IG9wdGlvbiB0cmFuc3BhcmVudC4gKEEgQ0Ugd291bGQgc3RpbGwgaGF2
ZSBhIERIQ1B2NiBjbGllbnQgb24gaXRzIFdBTiBpbnRlcmZhY2UgZm9yIGl0cyBvd24gcGFyYW1l
dGVycyBhbmQgREhDUHY2LVBEIHByZWZpeGVzKS4NCg0KLyBSZWdhcmRzLA0KLyBNYXJrLg0KDQoN
CkJhcmJhcmEsDQoNCkZvciB5b3VyIHVzZSBjYXNlLCB0aGUgc2VydmljZSBwcm92aWRlciBjb25m
aWd1cmVzIHRoZSBESENQdjYgc2VydmVyIHRvIG9ubHkgc2VydmUgb3B0aW9ucyBzcGVjaWZpZWQg
aW4gUkZDIDcwODQuICBUaHVzIGluIHRoaXMgZGVwbG95bWVudCBubyBleHRyYSBvcHRpb25zIGV4
aXN0IHRvIHNlcnZlIHRvIHRoZSBDRSByb3V0ZXIgTEFOLg0KDQpCb3RoIHVzZSBjYXNlcyBjYW4g
YmUgc3VwcG9ydGVkIHVzaW5nIGV4aXN0aW5nIFJGQ+KAmXMuDQoNCkhlbWFudA0KDQoNCg0KRnJv
bTpNYXJrIFpaWiBTbWl0aCBbbWFpbHRvOm1hcmt6enpzbWl0aEB5YWhvby5jb20uYXVdDQpTZW50
OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSA5OjUyIFBNDQpUbzogSGVtYW50IFNpbmdoIChzaGVt
YW50KTsgU1RBUkssIEJBUkJBUkEgSDsgQnJpYW4gSGFiZXJtYW47IGlwdjZAaWV0Zi5vcmc8bWFp
bHRvOmlwdjZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogUkEgT3B0aW9uIEd1aWRlbGluZXMNCg0K
SGkgSGVtYW50LA0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkZyb206
SGVtYW50IFNpbmdoIChzaGVtYW50KSA8c2hlbWFudEBjaXNjby5jb208bWFpbHRvOnNoZW1hbnRA
Y2lzY28uY29tPj4NClRvOiAiU1RBUkssIEJBUkJBUkEgSCIgPGJzNzY1MkBhdHQuY29tPG1haWx0
bzpiczc2NTJAYXR0LmNvbT4+OyBNYXJrIFpaWiBTbWl0aCA8bWFya3p6enNtaXRoQHlhaG9vLmNv
bS5hdTxtYWlsdG86bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdT4+OyBCcmlhbiBIYWJlcm1hbiA8
YnJpYW5AaW5ub3ZhdGlvbnNsYWIubmV0PG1haWx0bzpicmlhbkBpbm5vdmF0aW9uc2xhYi5uZXQ+
PjsgImlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+IiA8aXB2NkBpZXRmLm9yZzxt
YWlsdG86aXB2NkBpZXRmLm9yZz4+DQpTZW50OiBXZWRuZXNkYXksIDEgQXByaWwgMjAxNSwgMToy
Nw0KU3ViamVjdDogUkU6IFJBIE9wdGlvbiBHdWlkZWxpbmVzDQoNCkJhcmJhcmEsDQoNClRoYW5r
cyBmb3IgcmVwbHlpbmcuDQoNCk1hcmssDQoNCklmIG5ldyBESENQdjYgb3B0aW9ucyBhcmUgYWRk
ZWQgdG8gYmUgc3VwcG9ydGVkIGJ5IFJGQzM3MzYsIHRoZW4gdGhlIFNQIGluY2x1ZGVzIHRoZSBu
ZXcgb3B0aW9uIGluIHRoZSBESENQdjYgcmVzcG9uc2VzIHRvIHRoZSBDUEUgV0FOLiAgVGhlbiB0
aGUgQ1BFIGluY2x1ZGVzIHRoZSBuZXcgb3B0aW9uIHRvIGl0cyBMQU4gREhDUHY2IGNsaWVudHMu
DQoNCi8gIFNvIGhlcmUgaXMgYSBzY2VuYXJpby4NCg0KLyBBcyBhbiBJU1AsIG15IGN1c3RvbWVy
cyBoYXZlIFZvSVAgaGFuZHNldHMgdGhhdCBtaWdodCBzdXBwb3J0IHRoZSBPUFRJT05fR0VPTE9D
QVRJT04gREhDUHY2IG9wdGlvbiAoSSBtaWdodCBrbm93IHRoYXQgYSBwb3J0aW9uIG9mIHRoZW0g
ZG8sIGJlY2F1c2UgdGhleSd2ZSBib3VnaHQgdGhvc2UgVm9JUCBoYW5kc2V0cyBmcm9tIG1lKS4g
SG93IGxvbmcgaXMgaXQgZ29pbmcgdG8gdGFrZSBmb3IgbWUgdG8gZ2V0IHRoYXQgb3B0aW9uIGFk
ZGVkIHRvIGFuIHVwZGF0ZWQgUkZDMzczNiBhbmQgUkZDNzA4NCwgdG8gZ2V0IG15IENQRSB2ZW5k
b3IgdG8gdXBkYXRlIGFuZCByZWxlYXNlIHRoZWlyIGZpcm13YXJlIHRvIHN1cHBvcnQgdGhhdCBv
cHRpb24sIGFuZCB0ZXN0IHRoYXQgbmV3IENQRSBmaXJtd2FyZSBhbmQgdGhlbiB0byBkZXBsb3kg
dGhhdCBuZXcgZmlybXdhcmU/DQoNCi8gSSB0aGluayBJJ2QgYmUgbHVja3kgaWYgaXQgb25seSB0
b29rIDIgeWVhcnMuDQoNCi8gQSBmZXcgbW9udGhzIGxhdGVyIEkgZGVjaWRlIEkgd2FudCB0byBw
cm92aWRlIE9QVElPTl9ORVdfUE9TSVhfVElNRVpPTkUgdG8gbXkgY3VzdG9tZXJzIGlmIHRoZWly
IGhvc3RzIHJlcXVlc3QgaXQuIFNvIG5vdyBJIGhhdmUgdG8gdHJ5IHRvIGdldCBPUFRJT05fTkVX
X1BPU0lYX1RJTUVaT05FIGFkZGVkIHRvIHRoZSB1cGRhdGVkIFJGQzM3MzYsIHRvIGdldCBteSBD
UEUgdmVuZG9yIHRvIHVwZGF0ZSBhbmQgcmVsZWFzZSB0aGVpciBmaXJtd2FyZSB0byBzdXBwb3J0
IHRoYXQgb3B0aW9uLCBhbmQgdGVzdCB0aGF0IG5ldyBDUEUgZmlybXdhcmUgYW5kIHRoZW4gdG8g
ZGVwbG95IHRoYXQgbmV3IGZpcm13YXJlLg0KDQovIE5vdyBpZiBJJ20gbHVja3kgSSBjb3VsZCBh
ZGQgaXQgdG8gdGhlIGRyYWZ0IGZvciBPUFRJT05fR0VPTE9DQVRJT04sIHNvIGl0IGlzIHN0aWxs
ICJvbmx5IiAyIHllYXJzIHRvIGdldCB0byBhIHBvaW50IHdoZXJlIEkgY291bGQgcHJvdmlkZSB0
aG9zZSBvcHRpb25zIHRvIG15IGN1c3RvbWVycy4gQnV0IHdoYXQgaWYgdGhhdCBkcmFmdCBoYXMg
cHJvZ3Jlc3NlZCB0b28gZmFyIHRob3VnaCB0aGUgSUVURiBwdWJsaXNoaW5nIHByb2Nlc3M/IEkg
aGF2ZSB0byBjcmVhdGUgYSBuZXcgZHJhZnQgdXBkYXRpbmcgdGhlIHRvIGJlIHB1Ymxpc2hlZCBk
cmFmdC4NCg0KLyBTbywgdG8gYWNoaWV2ZSB3aGF0IHNob3VsZCBiZSBhIHNpbXBsZSB0YXNrIG9m
IHByb3ZpZGluZyBsb2NhdGlvbiBvciB0aW1lem9uZSBpbmZvcm1hdGlvbiB0byBjdXN0b21lcnMn
IGVuZCBob3N0cyBpZiB0aGV5IHdhbnQgaXQsIHdlJ3ZlIGp1c3QgaW5jdXJyZWQgdGhlIG1hc3Np
dmUgY29zdHMgYW5kIHRpbWUgZGVsYXlzIG9mIHRoZSBJRVRGIHB1Ymxpc2hpbmcgcHJvY2Vzcywg
dmVuZG9yIGZpcm13YXJlIHVwZ3JhZGVzLCBmaXJtd2FyZSB0ZXN0aW5nIGFuZCBmaXJtd2FyZSBk
ZXBsb3ltZW50LiBTb3VuZHMgbGlrZSBob3cgaGFyZCBJIHVuZGVyc3RhbmQgaXQgd2FzIHRvIHJv
bGwgb3V0IGZlYXR1cmVzIGxpa2UgQ0xJIGluIFBTVE4gbmV0d29ya3MgLi4uDQoNCiBXaGF0IGlz
IG9uZSBvcHRpb24geW91J2QgbGlrZSB0aGUgaG9zdCBvbiB0aGUgTEFOIHRvIGluY2x1ZGUgc28g
dGhhdCB3ZSBjYW4gdW5kZXJzdGFuZCB5b3VyIHVzZSBjYXNlIGJldHRlcj8NCg0KLyBJJ20gZ29p
bmcgdG8gbWFrZSB0aGUgcHJvYmxlbSBtdWNoIGhhcmRlciBmb3IgeW91LiBJIHdhbnQgdGhlIENQ
RSB0byAic3VwcG9ydCIgb3IgYmV0dGVyLCBiZSB0cmFuc3BhcmVudCB0bywgYWxsIGN1cnJlbnQg
YW5kIGZ1dHVyZSBESENQdjYgb3B0aW9ucywgYW5kIEkgZG9uJ3Qgd2FudCB0byBoYXZlIHRvIHVw
Z3JhZGUgb3IgYXNrIG15IGN1c3RvbWVycyB0byBzdWNjZXNzZnVsbHkgdXBncmFkZSB0aGVpciBD
UEUgZWFjaCBhbmQgZXZlcnkgdGltZQ0KdGhlcmUgaXMgYSBuZXcgREhDUHY2IG9wdGlvbiBkZWZp
bmVkIHRoYXQgbWlnaHQgYmUgdXNlZnVsIHRvIG1lIGFuZCB0aGVtLiBJIHdhbnQgdG8gYmUgYWJs
ZSB0byBwcm92aWRlIHNlcnZpY2UgcGFyYW1ldGVycyB0byBteSBjdXN0b21lcnMgaG9zdHMsIGRp
cmVjdGx5IG9yIGluZGlyZWN0bHksIHdpdGhvdXQgdGhlIHNvZnR3YXJlIHJldmlzaW9uIG9yIG1v
ZGVsIG9mIHRoZWlyIENQRSBiZWluZyB0aGUgY29uc3RyYWludC4NCg0KVGhlIFNJUCBzZXJ2ZXIg
aXMgYWxyZWFkeSBpbmNsdWRlZCBhcyBvbmUgb3B0aW9uIHN1cHBvcnRlZCBieSBSRkMzNzM2LiAg
Q2VydGFpbmx5LCBpZiB0aGUgU0lQIHNlcnZlciBzdXBwb3J0IGlzIG5lZWRlZCBpbiB0aGUgUkEs
IEkgYW0gb3BlbiBmb3IgaXQgc2luY2UgdGhlIFJBIGFscmVhZHkgaW5jbHVkZXMgRE5TIGluZm9y
bWF0aW9uLg0KDQovIEkgZG9uJ3QgdGhpbmsgRE5TIGluIFJBcyB3YXMgYSBnb29kIGlkZWEsIGFu
ZCBuZWl0aGVyIHdlcmUgU0lQIG9wdGlvbnMgd2hlbiB0aGV5IHdlcmUgcHJvcG9zZWQuIFNlZSB0
aGF0IHRpbWUgY29uc3VtaW5nIGFuZCBzZXJ2aWNlIGRpc3J1cHRpbmcgZmlybXdhcmUgdXBncmFk
ZSBjeWNsZSBmb3IgbmV3IERIQ1B2NiBvcHRpb25zPyBTYW1lIHByb2JsZW0gaWYgeW91IHVzZSBS
QSBvcHRpb25zIHRvIGFjaGlldmUgdGhlIHNhbWUgZ29hbC4gTmV3IGZpcm13YXJlIHVwZ3JhZGUg
ZWFjaCB0aW1lIHlvdSB3YW50IHRvIHN1cHBvcnQgYSBuZXcgUkEgb3B0aW9uLg0KDQovIER1cGxp
Y2F0aW9uIGJldHdlZW4gUkEgb3B0aW9ucyBhbmQgREhDUHY2IG9wdGlvbnMgYWxzbyBjYXVzZXMg
bW9yZSBwcm9ibGVtcy4gV2hpY2ggaXMgcHJlZmVycmVkPyBBcmUgdGhleSB0cmVhdGVkIGVxdWFs
bHkgb3IgZG9lcyBvbmUgdGFrZSBwcmVjZWRlbmNlIG92ZXIgdGhlIG90aGVyPyBBcyBmYXIgYXMg
SSdtIGF3YXJlLCB0aGVzZSBxdWVzdGlvbnMgaGF2ZW4ndCBiZWVuIGFuc3dlcmVkIGZvciB0aGUg
REhDUHY2IEROUyBhbmQgUkEgRE5TIG9wdGlvbnMgeWV0LiBJdCBtaWdodCBiZSBzaW1wbGUgdG8g
Y29tZSB1cCB3aXRoIGEgc2ltcGxlIHJ1bGUgZm9yIG1vcmUgREhDUHY2IG9wdGlvbnMgYXJlIGR1
cGxpY2F0ZWQgaW50byBSQXMsIGhvd2V2ZXIgdGhlaXIgbWlnaHQgYmUgc29tZSBzcGVjaWZpYyBj
YXNlcyB3aGVyZSB0aGUgUkEgb3B0aW9uIHZhbHVlIHNob3VsZCBiZSBwcmVmZXJyZWQgb3ZlciB0
aGUgREhDUHY2IGVxdWl2YWxlbnQgb3B0aW9uIGFuZCB2aWNlLXZlcnNhLg0KDQpIb3dldmVyLCBJ
IHN0aWxsIGFzayB0aGUgcXVlc3Rpb24gYXMgdG8gaG93IGFuIFJBIHJlY2VpdmVkIGF0IHRoZSBX
QU4gb2YgdGhlIENQRSBoYXMgaXRzIG9wdGlvbnMgcHJvcGFnYXRlZCB0byB0aGUgUkEgb24gdGhl
IExBTj8gIEF0IHRoZSB0aW1lIG9mIHdyaXRpbmcgUkZDIDYyMDQgb3IgUkZDIDcwODQsIHRoZXJl
IGlzIG5vIHN1Y2ggcHJvdmlzaW9uIGJldHdlZW4gdGhlIFJBIHJlY2VpdmVkIG9uIHRoZSBXQU4g
YW5kIHRoZSBSQSBpc3N1ZWQgb24gdGhlIExBTiBvZiB0aGUgQ0Ugcm91dGVyLg0KDQovIFVzZSBh
IERIQ1B2NiByZWxheSBpbiB0aGUgQ1BFLiBUaGVuIHRoZXJlIGlzbid0IGEgcHJvYmxlbSwgbmV3
IERIQ1B2NiBvcHRpb25zIHRoYXQgYXJlIHVua25vd24gYnkgdGhlIENQRSB3aWxsIHBhc3Mgcmln
aHQgdGhyb3VnaCBpdCB0cmFuc3BhcmVudGx5LiBUaGUgb25seSBjb21wbGljYXRpb24gaXMgd2hl
biBzdGF0ZWZ1bCBESENQdjYgYWRkcmVzc2luZyBpcyB1c2VkIG9uIHRoZSBDUEUgTEFOIGludGVy
ZmFjZSwgYW5kIEkgc3VnZ2VzdGVkIGEgaHlicmlkIG1vZGUgb2Ygb3BlcmF0aW9uIGZvciBhIERI
Q1B2NiBzZXJ2ZXIgaW4gdGhhdCBkcmFmdCB3aGljaCBJIHRoaW5rIHNvbHZlcyB0aGF0IHByb2Js
ZW0uDQoNCk90aGVycywNCg0KQWxzbywgd2h5IGRvZXMgb25lIG5lZWQgYW4gUkEgT3B0aW9uIEd1
aWRlbGluZT8gIFJGQzQ4NjEgc3BlY2lmaWVzIGEgVExWIGZvcm1hdCBhbmQgYW4gb3B0aW9uIFR5
cGUuICBJIGRvbid0IHNlZSBhbnl0aGluZyBlbHNlIG5lZWRlZCBpZiBJIG5lZWQgdG8gc3BlY2lm
eSBhIG5ldyBSQSBvcHRpb24uDQoNClRoYW5rcywNCg0KSGVtYW50DQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBTVEFSSywgQkFSQkFSQSBIIFttYWlsdG86YnM3NjUyQGF0dC5j
b21dDQpTZW50OiBUdWVzZGF5LCBNYXJjaCAzMSwgMjAxNSA5OjI1IEFNDQpUbzogSGVtYW50IFNp
bmdoIChzaGVtYW50KTsgTWFyayBaWlogU21pdGg7IEJyaWFuIEhhYmVybWFuOyBpcHY2QGlldGYu
b3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KU3ViamVjdDogUkU6IFJBIE9wdGlvbiBHdWlkZWxp
bmVzDQoNCg0KDQoNClJGQyA3MDg0IGFscmVhZHkgc2F5czoNCiAgTC0xMjogIFRoZSBJUHY2IENF
IHJvdXRlciBTSE9VTEQgbWFrZSBhdmFpbGFibGUgYSBzdWJzZXQgb2YgREhDUHY2DQogICAgICAg
ICAgb3B0aW9ucyAoYXMgbGlzdGVkIGluIFNlY3Rpb24gNS4zIG9mIFtSRkMzNzM2XSkgcmVjZWl2
ZWQgZnJvbQ0KICAgICAgICAgIHRoZSBESENQdjYgY2xpZW50IG9uIGl0cyBXQU4gaW50ZXJmYWNl
IHRvIGl0cyBMQU4tc2lkZSBESENQdjYNCiAgICAgICAgICBzZXJ2ZXIuDQo=

--_000_75B6FA9F576969419E42BECB86CB1B8916838870xmbrcdx06ciscoc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5N
c29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJU
aW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsN
CgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNwYW4uQmFsbG9vblRleHRD
aGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZvbnQtZmFtaWx5
OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi
Ow0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5X
b3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEw
MjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAv
Pg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFu
Zz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNl
Y3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5Db3VsZCB0aGUgREhDUHY2IGd1cnVzIGluIFJhbHBoLCBCZXJuaWUs
IGFuZCBUZWQgcGxlYXNlIGhlbHAgcmVzb2x2ZSB0aGlzIHRocmVhZCBmb3Igc3RhdGVsZXNzIERI
Q1B2NiBjdXJyZW50IHZzLiBmdXR1cmUgb3B0aW9ucyBhbmQgdGhlIE9STyBvcHRpb24uDQo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhlbWFudDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGlu
IDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IE1hcmsg
WlpaIFNtaXRoIFttYWlsdG86bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdV0NCjxicj4NCjxiPlNl
bnQ6PC9iPiBUaHVyc2RheSwgQXByaWwgMDIsIDIwMTUgMTA6MTkgUE08YnI+DQo8Yj5Ubzo8L2I+
IEhlbWFudCBTaW5naCAoc2hlbWFudCk7IFNUQVJLLCBCQVJCQVJBIEg7IEJyaWFuIEhhYmVybWFu
OyBpcHY2QGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBSQSBPcHRpb24gR3VpZGVs
aW5lczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQ7YmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOmJsYWNrIj5IaSBIZW1hbnQsPGJyPg0KPGJyPg0KPGJyPg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188YnI+DQpGcm9tOiBIZW1hbnQgU2luZ2ggKHNoZW1hbnQpICZs
dDs8YSBocmVmPSJtYWlsdG86c2hlbWFudEBjaXNjby5jb20iPnNoZW1hbnRAY2lzY28uY29tPC9h
PiZndDs8YnI+DQpUbzogTWFyayBaWlogU21pdGggJmx0OzxhIGhyZWY9Im1haWx0bzptYXJrenp6
c21pdGhAeWFob28uY29tLmF1Ij5tYXJrenp6c21pdGhAeWFob28uY29tLmF1PC9hPiZndDs7ICZx
dW90O1NUQVJLLCBCQVJCQVJBIEgmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpiczc2NTJAYXR0
LmNvbSI+YnM3NjUyQGF0dC5jb208L2E+Jmd0OzsgQnJpYW4gSGFiZXJtYW4gJmx0OzxhIGhyZWY9
Im1haWx0bzpicmlhbkBpbm5vdmF0aW9uc2xhYi5uZXQiPmJyaWFuQGlubm92YXRpb25zbGFiLm5l
dDwvYT4mZ3Q7Ow0KICZxdW90OzxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGll
dGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciPmlwdjZA
aWV0Zi5vcmc8L2E+Jmd0Ow0KPGJyPg0KU2VudDogRnJpZGF5LCAzIEFwcmlsIDIwMTUsIDY6MDc8
YnI+DQpTdWJqZWN0OiBSRTogUkEgT3B0aW9uIEd1aWRlbGluZXM8YnI+DQo8YnI+DQo8YnI+DQo8
YnI+DQpNYXJrLDxicj4NCiZuYnNwOzxicj4NClRoZSBzdGF0ZWxlc3MgREhDUHY2IHNlcnZlciBp
biBSRkMzNzM2IGFsbG93cyBmb3IgbmV3IG9wdGlvbnMgdG8gYmUgc2VydmVkIGJ5IHRoZSBzdGF0
ZWxlc3Mgc2VydmVyLiZuYnNwOyZuYnNwOyBSZWFkIHRoZSBmaXJzdCBwYXJhZ3JhcGggb2Ygc2Vj
dGlvbiA1LjMgaW4gUkZDMzczNi48YnI+DQo8YnI+DQovIFNvIHRoZXJlIGFyZSBhIGZldyByZWFz
b25zIHdoeSBJIHdvdWxkbid0IGNvbWUgdG8gdGhhdCBjb25jbHVzaW9uIHdpdGhvdXQgc29tZSB2
ZXJ5IGNhcmVmdWwgcmVhZGluZzo8YnI+DQo8YnI+DQovIC0gVGhlIGV4cGxpY2l0bHkgaWRlbnRp
ZmllZCBzZXQgb2YgcmVxdWlyZWQgYW5kIG9wdGlvbmFsIERIQ1B2NiBvcHRpb25zIHRoYXQgY2Fu
IGJlIHN1cHBvcnRlZCBieSBhIHN0YXRlbGVzcyBESENQdjYgc2VydmVyPGJyPg0KPGJyPg0KLyAt
IFRoZSBsYWNrIG9mIGFueSBvdmVydCBkaXNjdXNzaW9uIHRoYXQgdGhpcyBzZXQgb2YgcmVxdWly
ZWQgYW5kIG9wdGlvbmFsIERIQ1B2NiBvcHRpb25zIGFyZSBhIG1pbmltdW0sIGFuZCB0aGF0IGZ1
cnRoZXIgREhDUHY2IG9wdGlvbnMgY291bGQgYmUgcHJvdmlkZWQgYnkgYSBzdGF0ZWxlc3MgREhD
UHY2IHNlcnZlciBpZiBzdXBwb3J0ZWQgYnkgdGhlIGltcGxlbWVudGF0aW9uLCBhcmUgYXBwcm9w
cmlhdGUgYW5kIHJlcXVlc3RlZCBieSB0aGUNCiBjbGllbnQuIEl0IGJlaW5nIGEgbWluaW11bSBp
cyBzdWJ0bHkgZWx1ZGVkIHRvIGluIGEgZmV3IHNlbnRlbmNlcyBpbiB0aGUgQWJzdHJhY3QgYW5k
IHRoZSBJbnRyb2R1Y3Rpb24sIGhvd2V2ZXIgSSB0aGluayB0aGV5IGNvdWxkIGVhc2lseSBiZSBt
aXNzZWQuIEknZCBleHBlY3QgdGhhdCBpZiB0aGlzIGlzIHRoZSBjYXNlLCBpdCBpcyBtdWNoIGNs
ZWFyZXIgYW5kIG9idmlvdXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdiBpZD0ieXVpXzNf
MTZfMF8xXzE0MjgwMTg1NTU5NDRfNjEwMDQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+LyAtIEkgdGhpbmsg
dGV4dCB5b3UgcmVmZXIgdG8gaW4gNS4zLCAmcXVvdDtDbGllbnRzIGFuZCBzZXJ2ZXJzIHVzZSB0
aGUgZm9sbG93aW5nIG9wdGlvbnMgdG8gcGFzcyBjb25maWd1cmF0aW9uJm5ic3A7aW5mb3JtYXRp
b24gdG8gY2xpZW50czsgbm90ZSB0aGF0IG90aGVyIG9wdGlvbnMNCiBmb3IgY29uZmlndXJhdGlv
biZuYnNwO2luZm9ybWF0aW9uIG1heSBiZSBzcGVjaWZpZWQgaW4gZnV0dXJlIEludGVybmV0IFN0
YW5kYXJkczomcXVvdDsgcmVhZHMgdG8gbWUgbGlrZSBhIGxhdGVyIHZlcnNpb24gb2YgdGhpcyBS
RkMgd2lsbCBzcGVjaWZ5IG1vcmUgc3RhdGVsZXNzIERIQ1B2NiBzZXJ2ZXIgc3VwcG9ydGVkIG9w
dGlvbnMuIEEgc3RhdGVtZW50IHN1Y2ggYXMmbmJzcDsmcXVvdDtPdGhlciBhZGRpdGlvbmFsIERI
Q1B2NiBvcHRpb25zIGFwcHJvcHJpYXRlIGZvciBzdGF0ZWxlc3MNCiBESENQdjYgb3BlcmF0aW9u
IG1heSBiZSBzdXBwb3J0ZWQgYnkgYW4gaW1wbGVtZW50YXRpb24uJnF1b3Q7IHdvdWxkIG1ha2Ug
aXQgbXVjaCBjbGVhcmVyIHRoYXQgdGhlIHN1cHBvcnRlZCBvcHRpb25zIHdlcmUgdXAgdG8gdGhl
IGltcGxlbWVudGVyIG9uY2UgdGhlIG1pbmltdW0gaGFkIGJlZW4gaW1wbGVtZW50ZWQuPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFj
a2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyODAxODU1NTk0NF82MDU0NiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOmJsYWNrIj4vIFNvIGlmIEkgd2VyZSBpbXBsZW1lbnRpbmcgYSBzdGF0ZWxlc3Mg
REhDUHY2IHNlcnZlciBhcyBwZXIgUkZDMzczNiwgSSdkIHRoaW5rIHRoZSBpbXBsZW1lbnRhdGlv
biB3YXMgY29tcGxldGUgd2hlbiBJIGhhZCBpbXBsZW1lbnRlZCB0aGUgb3B0aW9ucyBzcGVjaWZp
ZWQuDQogSSB3b3VsZG4ndCBwdXQgYW55IGVmZm9ydCBpbnRvIG1ha2luZyBpdCBhbHNvIHRyYW5z
cGFyZW50IHRvIGFueSBvcHRpb25zIHRoYXQgd2VyZW4ndCBpZGVudGlmaWVkIGluIFJGQzM3MzYs
IGFzIHRoZXJlIGlzIG5vIHRleHQgZGlzY3Vzc2luZyB0aGF0LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0MjgwMTg1NTU5NDRfNjA1NDYiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
IGlkPSJ5dWlfM18xNl8wXzFfMTQyODAxODU1NTk0NF82MDU0NiI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4m
bmJzcDsgU28gdGhlIG5ldyBvcHRpb25zIHlvdSB3YW50IHRvIHNlcnZlIGNhbiBiZSBzZXJ2ZWQg
YnkgdGhlIENFIHN0YXRlbGVzcyBESENQdjYgc2VydmVyLiZuYnNwOyAmbmJzcDtOb3csIGlmIHRo
ZSBzZXJ2aWNlIHByb3ZpZGVyIGNvbmZpZ3VyZXMgaGlzL2hlciBESENQdjYgc2VydmVyDQogdG8g
cmV0dXJuIG5ldyBvcHRpb25zIHRvIHRoZSBDRSBXQU4gaW50ZXJmYWNlIGFkZHJlc3MgYWNxdWlz
aXRpb24sIHRoZSBDRSB1c2VzIHRoZSBvcHRpb25zIG9uIHRoZSBMQU4uJm5ic3A7IFNlZSBidWxs
ZXQgTC0xMiBvZiBSRkMgNzA4NC4mbmJzcDsgRXhpc3RpbmcgUkZDcyBzdXBwb3J0IHlvdXIgdXNl
IGNhc2UgYW5kIG5vIGRoY3B2NiByZWxheSBpcyByZXF1aXJlZCBpbiB0aGUgQ0UuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyODAxODU1NTk0
NF82MDYzOCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI4MDE4NTU1OTQ0XzYwNjQyIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6YmxhY2siPi8gSSBhbHNvIGNhbm5vdCBmaW5kIHRleHQgaW4gUkZDMzMxNSBvciBpdHMgdXBk
YXRlcyBvbiBob3cgdG8gaGFuZGxlIHJlY2VpdmVkIG9wdGlvbnMgdGhhdCB3ZXJlIG5vdCByZXF1
ZXN0ZWQgYnkgdGhlIGNsaWVudCBpbiB0aGUgT3B0aW9uIFJlcXVlc3QgT3B0aW9uLg0KIFNvIGlm
IHRoZSBDRSBXQU4gREhDUHY2IGNsaWVudCBkb2Vzbid0IHJlcXVlc3QgYW4gb3B0aW9uIGluIGl0
cyBPUk8gdG8gdGhlIFNQJ3MgREhDUHY2IHNlcnZlciwgSSBkb24ndCB0aGluayBpdCBpcyBwb3Nz
aWJsZSBmb3IgdGhlIENFIHRvIHBhc3Mgb3B0aW9ucyBpdCBkb2Vzbid0IGtub3cgYWJvdXQgb250
byB0aGUgZG93bnN0cmVhbSBMQU4gZGV2aWNlcyB0aGF0IGRvIHVuZGVyc3RhbmQgdGhvc2UgREhD
UHY2IG9wdGlvbnMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlf
M18xNl8wXzFfMTQyODAxODU1NTk0NF82MDY0MiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZl
dGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI4MDE4
NTU1OTQ0XzYwNjQyIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndo
aXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPi8gSWYgaXQgaXMgcG9zc2libGUgdG8gc2Vu
ZCBhIERIQ1B2NiBjbGllbnQgJnF1b3Q7T1JPIHR5cGUmcXVvdDsgb3B0aW9ucyB0aGF0IGl0IGRp
ZG4ndCByZXF1ZXN0LCB0aGVuIHRoZSBiZWhhdmlvdXIgaXMgc3RpbGwgYW1iaWd1b3VzLiBJZiB0
aGUgREhDUHY2IGNsaWVudCBpcw0KIGEgaG9zdCwgdGhlbiBpdCB3b3VsZCBiZSBxdWl0ZSByZWFz
b25hYmxlIGFuZCBleHBlY3RlZCB0byBzaWxlbnRseSBpZ25vcmUgdGhvc2UgcmVjZWl2ZWQgdW5r
bm93biBvcHRpb25zLiBIb3dldmVyLCBpZiB0aGUgREhDUHY2IGNsaWVudCBpcyBvbiB0aGUgV0FO
IHNpZGUgb2YgYSBDRSBkZXZpY2UsIHRoZW4gdGhvc2Ugb3B0aW9ucyBzaG91bGQgaW5zdGVhZCBi
ZSBwYXNzZWQgdG8gdGhlIExBTiBESENQdjYgc2VydmVyLCB3aGljaCBwcmVzdW1hYmx5DQogc2hv
dWxkIGtub3cgaG93IHRvIGNvcnJlY3RseSBoYW5kbGUgb3B0aW9ucyBpdCBkb2Vzbid0IHVuZGVy
c3RhbmQgLSBpbiB0aGUgc3BlY2lmaWMgQ0UgY2FzZSwgcmVtZW1iZXIgdGhvc2Ugb3B0aW9ucyBp
biBjYXNlIGEgZG93bnN0cmVhbSBMQU4gREhDUHY2IGNsaWVudCByZXF1ZXN0cyB0aGVtLiBJIHRo
aW5rIFJGQzcwODQgYW5kIGl0J3MgYW5jZXN0b3IgUkZDNjIwNCBhcmUgdGhlIG9ubHkgUkZDcyB3
aGljaCBkZXNjcmliZSB0aGlzIGNvbWJpbmF0aW9uDQogb2YgREhDUHY2IGNsaWVudC9zZXJ2ZXIg
d29ya2luZyB0b2dldGhlciwgYW5kIG5laXRoZXIgb2YgdGhlbSBoYXZlIGRpc2N1c3NlZCBwYXNz
aW5nIHVua25vd24gb3B0aW9ucyBmcm9tIHRoZSBESENQdjYgV0FOIGNsaWVudCB0byB0aGUgREhD
UHY2IExBTiBzZXJ2ZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5
dWlfM18xNl8wXzFfMTQyODAxODU1NTk0NF82MDY0MiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hl
bHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI4
MDE4NTU1OTQ0XzYwNjQyIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPi8gQXJlIHlvdSBhd2FyZSBvZiBhbnkg
Q0UgREhDUHY2IFdBTiBjbGllbnQvREhDUHY2IExBTiBzZXJ2ZXIgaW1wbGVtZW50YXRpb25zIHRo
YXQgYXJlIHVua25vd24gREhDUHY2IG9wdGlvbiB0cmFuc3BhcmVudD8gTG9va2luZyBhdCBSRkM3
MDg0LCB0aGlzIGJlaGF2aW91cg0KIHNlZW1zIHRvIGJlIHZlcnkgZXhwbGljaXRseSBwcm9oaWJp
dGVkLCBieSBsaW1pdGluZyB0aGUgTEFOIERIQ1B2NiBzZXJ2ZXIgc3VwcG9ydCB0byBvbmx5IHRo
b3NlIG9wdGlvbnMgZGVzY3JpYmVkIGluIFJGQzcwODQsIG9yIHRvIHRob3NlIGRlc2NyaWJlZCBp
biBSRkMzNzM2LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNf
MTZfMF8xXzE0MjgwMTg1NTU5NDRfNjA2NDIiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyODAxODU1
NTk0NF82MDY0MiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0
ZSI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4vIEkgdGhpbmsgdGhpcyBsZXZlbCBvZiBESENQ
djYgb3B0aW9uIHRyYW5zcGFyZW5jeSBiZXR3ZWVuIENFIExBTiBhdHRhY2hlZCBob3N0cyBhbmQg
dGhlIHVwc3RyZWFtIFNQJ3MgREhDUHY2IHNlcnZlcihzKSBjYW4gb25seSBiZSBhY2hpZXZlZCBi
eSB1c2luZw0KIGEgREhDUHY2IHJlbGF5IG9uIHRoZSBDRSBMQU4gaW50ZXJmYWNlLCBiZWNhdXNl
IERIQ1B2NiByZWxheXMgYXJlIERIQ1B2NiBvcHRpb24gdHJhbnNwYXJlbnQuIChBIENFIHdvdWxk
IHN0aWxsIGhhdmUgYSBESENQdjYgY2xpZW50IG9uIGl0cyBXQU4gaW50ZXJmYWNlIGZvciBpdHMg
b3duIHBhcmFtZXRlcnMgYW5kIERIQ1B2Ni1QRCBwcmVmaXhlcykuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJ5dWlfM18xNl8wXzFfMTQyODAxODU1NTk0NF82MDY0MiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI4MDE4NTU1OTQ0XzYwNjQyIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2si
Pi8gUmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8z
XzE2XzBfMV8xNDI4MDE4NTU1OTQ0XzYwNjQyIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPi8gTWFyay48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9Inl1aV8zXzE2XzBfMV8xNDI4MDE4
NTU1OTQ0XzYwNjQyIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndo
aXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdiBpZD0ieXVpXzNfMTZfMF8xXzE0MjgwMTg1NTU5NDRfNjA3NTEiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjpibGFjayI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOmJsYWNrIj5CYXJiYXJhLDxicj4NCiZuYnNwOzxicj4NCkZvciB5b3VyIHVzZSBjYXNlLCB0
aGUgc2VydmljZSBwcm92aWRlciBjb25maWd1cmVzIHRoZSBESENQdjYgc2VydmVyIHRvIG9ubHkg
c2VydmUgb3B0aW9ucyBzcGVjaWZpZWQgaW4gUkZDIDcwODQuJm5ic3A7IFRodXMgaW4gdGhpcyBk
ZXBsb3ltZW50IG5vIGV4dHJhIG9wdGlvbnMgZXhpc3QgdG8gc2VydmUgdG8gdGhlIENFIHJvdXRl
ciBMQU4uPGJyPg0KJm5ic3A7IDxicj4NCkJvdGggdXNlIGNhc2VzIGNhbiBiZSBzdXBwb3J0ZWQg
dXNpbmcgZXhpc3RpbmcgUkZD4oCZcy48YnI+DQombmJzcDs8YnI+DQpIZW1hbnQ8YnI+DQombmJz
cDs8YnI+DQo8YnI+DQo8YnI+DQpGcm9tOk1hcmsgWlpaIFNtaXRoIFs8YSBocmVmPSJtYWlsdG86
bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdSI+bWFpbHRvOm1hcmt6enpzbWl0aEB5YWhvby5jb20u
YXU8L2E+XQ0KPGJyPg0KU2VudDogVHVlc2RheSwgTWFyY2ggMzEsIDIwMTUgOTo1MiBQTTxicj4N
ClRvOiBIZW1hbnQgU2luZ2ggKHNoZW1hbnQpOyBTVEFSSywgQkFSQkFSQSBIOyBCcmlhbiBIYWJl
cm1hbjsgPGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciPg0KaXB2NkBpZXRmLm9yZzwvYT48
YnI+DQpTdWJqZWN0OiBSZTogUkEgT3B0aW9uIEd1aWRlbGluZXM8YnI+DQombmJzcDs8YnI+DQpI
aSBIZW1hbnQsPGJyPg0KJm5ic3A7PGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188YnI+DQo8YnI+DQpGcm9tOkhlbWFudCBTaW5naCAoc2hlbWFudCkgJmx0OzxhIGhy
ZWY9Im1haWx0bzpzaGVtYW50QGNpc2NvLmNvbSI+c2hlbWFudEBjaXNjby5jb208L2E+Jmd0Ozxi
cj4NClRvOiAmcXVvdDtTVEFSSywgQkFSQkFSQSBIJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86
YnM3NjUyQGF0dC5jb20iPmJzNzY1MkBhdHQuY29tPC9hPiZndDs7IE1hcmsgWlpaIFNtaXRoICZs
dDs8YSBocmVmPSJtYWlsdG86bWFya3p6enNtaXRoQHlhaG9vLmNvbS5hdSI+bWFya3p6enNtaXRo
QHlhaG9vLmNvbS5hdTwvYT4mZ3Q7OyBCcmlhbiBIYWJlcm1hbiAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmJyaWFuQGlubm92YXRpb25zbGFiLm5ldCI+YnJpYW5AaW5ub3ZhdGlvbnNsYWIubmV0PC9hPiZn
dDs7DQogJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciPmlwdjZAaWV0Zi5vcmc8
L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBpZXRmLm9y
ZzwvYT4mZ3Q7DQo8YnI+DQpTZW50OiBXZWRuZXNkYXksIDEgQXByaWwgMjAxNSwgMToyNzxicj4N
ClN1YmplY3Q6IFJFOiBSQSBPcHRpb24gR3VpZGVsaW5lczxicj4NCjxicj4NCkJhcmJhcmEsPGJy
Pg0KPGJyPg0KVGhhbmtzIGZvciByZXBseWluZy4mbmJzcDsgJm5ic3A7IDxicj4NCjxicj4NCk1h
cmssPGJyPg0KPGJyPg0KSWYgbmV3IERIQ1B2NiBvcHRpb25zIGFyZSBhZGRlZCB0byBiZSBzdXBw
b3J0ZWQgYnkgUkZDMzczNiwgdGhlbiB0aGUgU1AgaW5jbHVkZXMgdGhlIG5ldyBvcHRpb24gaW4g
dGhlIERIQ1B2NiByZXNwb25zZXMgdG8gdGhlIENQRSBXQU4uJm5ic3A7IFRoZW4gdGhlIENQRSBp
bmNsdWRlcyB0aGUgbmV3IG9wdGlvbiB0byBpdHMgTEFOIERIQ1B2NiBjbGllbnRzLjxicj4NCiZu
YnNwOzxicj4NCi8gJm5ic3A7U28gaGVyZSBpcyBhIHNjZW5hcmlvLjxicj4NCiZuYnNwOzxicj4N
Ci8gQXMgYW4gSVNQLCBteSBjdXN0b21lcnMgaGF2ZSBWb0lQIGhhbmRzZXRzIHRoYXQgbWlnaHQg
c3VwcG9ydCB0aGUmbmJzcDtPUFRJT05fR0VPTE9DQVRJT04gREhDUHY2IG9wdGlvbiAoSSBtaWdo
dCBrbm93IHRoYXQgYSBwb3J0aW9uIG9mIHRoZW0gZG8sIGJlY2F1c2UgdGhleSd2ZSBib3VnaHQg
dGhvc2UgVm9JUCBoYW5kc2V0cyBmcm9tIG1lKS4gSG93IGxvbmcgaXMgaXQgZ29pbmcgdG8gdGFr
ZSBmb3IgbWUgdG8gZ2V0IHRoYXQgb3B0aW9uIGFkZGVkIHRvDQogYW4gdXBkYXRlZCBSRkMzNzM2
IGFuZCBSRkM3MDg0LCB0byBnZXQgbXkgQ1BFIHZlbmRvciB0byB1cGRhdGUgYW5kIHJlbGVhc2Ug
dGhlaXIgZmlybXdhcmUgdG8gc3VwcG9ydCB0aGF0IG9wdGlvbiwgYW5kIHRlc3QgdGhhdCBuZXcg
Q1BFIGZpcm13YXJlIGFuZCB0aGVuIHRvIGRlcGxveSB0aGF0IG5ldyBmaXJtd2FyZT88YnI+DQom
bmJzcDs8YnI+DQovIEkgdGhpbmsgSSdkIGJlIGx1Y2t5IGlmIGl0IG9ubHkgdG9vayAyIHllYXJz
Ljxicj4NCiZuYnNwOzxicj4NCi8gQSBmZXcgbW9udGhzIGxhdGVyIEkgZGVjaWRlIEkgd2FudCB0
byBwcm92aWRlJm5ic3A7T1BUSU9OX05FV19QT1NJWF9USU1FWk9ORSB0byBteSBjdXN0b21lcnMg
aWYgdGhlaXIgaG9zdHMgcmVxdWVzdCBpdC4gU28gbm93IEkgaGF2ZSB0byB0cnkgdG8gZ2V0IE9Q
VElPTl9ORVdfUE9TSVhfVElNRVpPTkUgYWRkZWQgdG8gdGhlIHVwZGF0ZWQmbmJzcDtSRkMzNzM2
LCB0byBnZXQgbXkgQ1BFIHZlbmRvciB0byB1cGRhdGUgYW5kIHJlbGVhc2UgdGhlaXIgZmlybXdh
cmUNCiB0byBzdXBwb3J0IHRoYXQgb3B0aW9uLCBhbmQgdGVzdCB0aGF0IG5ldyBDUEUgZmlybXdh
cmUgYW5kIHRoZW4gdG8gZGVwbG95IHRoYXQgbmV3IGZpcm13YXJlLjxicj4NCiZuYnNwOzxicj4N
Ci8gTm93IGlmIEknbSBsdWNreSBJIGNvdWxkIGFkZCBpdCB0byB0aGUgZHJhZnQgZm9yJm5ic3A7
T1BUSU9OX0dFT0xPQ0FUSU9OLCBzbyBpdCBpcyBzdGlsbCAmcXVvdDtvbmx5JnF1b3Q7IDIgeWVh
cnMgdG8gZ2V0IHRvIGEgcG9pbnQgd2hlcmUgSSBjb3VsZCBwcm92aWRlIHRob3NlIG9wdGlvbnMg
dG8gbXkgY3VzdG9tZXJzLiBCdXQgd2hhdCBpZiB0aGF0IGRyYWZ0IGhhcyBwcm9ncmVzc2VkIHRv
byBmYXIgdGhvdWdoIHRoZSBJRVRGIHB1Ymxpc2hpbmcgcHJvY2Vzcz8gSSBoYXZlDQogdG8gY3Jl
YXRlIGEgbmV3IGRyYWZ0IHVwZGF0aW5nIHRoZSB0byBiZSBwdWJsaXNoZWQgZHJhZnQuPGJyPg0K
Jm5ic3A7PGJyPg0KLyBTbywgdG8gYWNoaWV2ZSB3aGF0IHNob3VsZCBiZSBhIHNpbXBsZSB0YXNr
IG9mIHByb3ZpZGluZyBsb2NhdGlvbiBvciB0aW1lem9uZSBpbmZvcm1hdGlvbiB0byBjdXN0b21l
cnMnIGVuZCBob3N0cyBpZiB0aGV5IHdhbnQgaXQsIHdlJ3ZlIGp1c3QgaW5jdXJyZWQgdGhlIG1h
c3NpdmUgY29zdHMgYW5kIHRpbWUgZGVsYXlzIG9mIHRoZSBJRVRGIHB1Ymxpc2hpbmcgcHJvY2Vz
cywgdmVuZG9yIGZpcm13YXJlIHVwZ3JhZGVzLCBmaXJtd2FyZSB0ZXN0aW5nDQogYW5kIGZpcm13
YXJlIGRlcGxveW1lbnQuIFNvdW5kcyBsaWtlIGhvdyBoYXJkIEkgdW5kZXJzdGFuZCBpdCB3YXMg
dG8gcm9sbCBvdXQgZmVhdHVyZXMgbGlrZSBDTEkgaW4gUFNUTiBuZXR3b3JrcyAuLi48YnI+DQom
bmJzcDs8YnI+DQombmJzcDtXaGF0IGlzIG9uZSBvcHRpb24geW91J2QgbGlrZSB0aGUgaG9zdCBv
biB0aGUgTEFOIHRvIGluY2x1ZGUgc28gdGhhdCB3ZSBjYW4gdW5kZXJzdGFuZCB5b3VyIHVzZSBj
YXNlIGJldHRlcj8gJm5ic3A7PGJyPg0KPGJyPg0KLyBJJ20gZ29pbmcgdG8gbWFrZSB0aGUgcHJv
YmxlbSBtdWNoIGhhcmRlciBmb3IgeW91LiBJIHdhbnQgdGhlIENQRSB0byAmcXVvdDtzdXBwb3J0
JnF1b3Q7IG9yIGJldHRlciwgYmUgdHJhbnNwYXJlbnQgdG8sIGFsbCBjdXJyZW50IGFuZCBmdXR1
cmUgREhDUHY2IG9wdGlvbnMsIGFuZCBJIGRvbid0IHdhbnQgdG8gaGF2ZSB0byB1cGdyYWRlIG9y
IGFzayBteSBjdXN0b21lcnMgdG8gc3VjY2Vzc2Z1bGx5IHVwZ3JhZGUgdGhlaXIgQ1BFIGVhY2gg
YW5kIGV2ZXJ5IHRpbWU8YnI+DQp0aGVyZSBpcyBhIG5ldyBESENQdjYgb3B0aW9uIGRlZmluZWQg
dGhhdCBtaWdodCBiZSB1c2VmdWwgdG8gbWUgYW5kIHRoZW0uIEkgd2FudCB0byBiZSBhYmxlIHRv
IHByb3ZpZGUgc2VydmljZSBwYXJhbWV0ZXJzIHRvIG15IGN1c3RvbWVycyBob3N0cywgZGlyZWN0
bHkgb3IgaW5kaXJlY3RseSwgd2l0aG91dCB0aGUgc29mdHdhcmUgcmV2aXNpb24gb3IgbW9kZWwg
b2YgdGhlaXIgQ1BFIGJlaW5nIHRoZSBjb25zdHJhaW50Ljxicj4NCjxicj4NClRoZSBTSVAgc2Vy
dmVyIGlzIGFscmVhZHkgaW5jbHVkZWQgYXMgb25lIG9wdGlvbiBzdXBwb3J0ZWQgYnkgUkZDMzcz
Ni4mbmJzcDsgQ2VydGFpbmx5LCBpZiB0aGUgU0lQIHNlcnZlciBzdXBwb3J0IGlzIG5lZWRlZCBp
biB0aGUgUkEsIEkgYW0gb3BlbiBmb3IgaXQgc2luY2UgdGhlIFJBIGFscmVhZHkgaW5jbHVkZXMg
RE5TIGluZm9ybWF0aW9uLjxicj4NCiZuYnNwOzxicj4NCi8gSSBkb24ndCB0aGluayBETlMgaW4g
UkFzIHdhcyBhIGdvb2QgaWRlYSwgYW5kIG5laXRoZXIgd2VyZSBTSVAgb3B0aW9ucyB3aGVuIHRo
ZXkgd2VyZSBwcm9wb3NlZC4gU2VlIHRoYXQgdGltZSBjb25zdW1pbmcgYW5kIHNlcnZpY2UgZGlz
cnVwdGluZyBmaXJtd2FyZSB1cGdyYWRlIGN5Y2xlIGZvciBuZXcgREhDUHY2IG9wdGlvbnM/IFNh
bWUgcHJvYmxlbSBpZiB5b3UgdXNlIFJBIG9wdGlvbnMgdG8gYWNoaWV2ZSB0aGUgc2FtZSBnb2Fs
LiBOZXcNCiBmaXJtd2FyZSB1cGdyYWRlIGVhY2ggdGltZSB5b3Ugd2FudCB0byBzdXBwb3J0IGEg
bmV3IFJBIG9wdGlvbi48YnI+DQombmJzcDs8YnI+DQovIER1cGxpY2F0aW9uIGJldHdlZW4gUkEg
b3B0aW9ucyBhbmQgREhDUHY2IG9wdGlvbnMgYWxzbyBjYXVzZXMgbW9yZSBwcm9ibGVtcy4gV2hp
Y2ggaXMgcHJlZmVycmVkPyBBcmUgdGhleSB0cmVhdGVkIGVxdWFsbHkgb3IgZG9lcyBvbmUgdGFr
ZSBwcmVjZWRlbmNlIG92ZXIgdGhlIG90aGVyPyBBcyBmYXIgYXMgSSdtIGF3YXJlLCB0aGVzZSBx
dWVzdGlvbnMgaGF2ZW4ndCBiZWVuIGFuc3dlcmVkIGZvciB0aGUgREhDUHY2IEROUyBhbmQgUkEg
RE5TDQogb3B0aW9ucyB5ZXQuIEl0IG1pZ2h0IGJlIHNpbXBsZSB0byBjb21lIHVwIHdpdGggYSBz
aW1wbGUgcnVsZSBmb3IgbW9yZSBESENQdjYgb3B0aW9ucyBhcmUgZHVwbGljYXRlZCBpbnRvIFJB
cywgaG93ZXZlciB0aGVpciBtaWdodCBiZSBzb21lIHNwZWNpZmljIGNhc2VzIHdoZXJlIHRoZSBS
QSBvcHRpb24gdmFsdWUgc2hvdWxkIGJlIHByZWZlcnJlZCBvdmVyIHRoZSBESENQdjYgZXF1aXZh
bGVudCBvcHRpb24gYW5kIHZpY2UtdmVyc2EuJm5ic3A7PGJyPg0KJm5ic3A7PGJyPg0KSG93ZXZl
ciwgSSBzdGlsbCBhc2sgdGhlIHF1ZXN0aW9uIGFzIHRvIGhvdyBhbiBSQSByZWNlaXZlZCBhdCB0
aGUgV0FOIG9mIHRoZSBDUEUgaGFzIGl0cyBvcHRpb25zIHByb3BhZ2F0ZWQgdG8gdGhlIFJBIG9u
IHRoZSBMQU4/Jm5ic3A7IEF0IHRoZSB0aW1lIG9mIHdyaXRpbmcgUkZDIDYyMDQgb3IgUkZDIDcw
ODQsIHRoZXJlIGlzIG5vIHN1Y2ggcHJvdmlzaW9uIGJldHdlZW4gdGhlIFJBIHJlY2VpdmVkIG9u
IHRoZSBXQU4gYW5kIHRoZSBSQSBpc3N1ZWQgb24NCiB0aGUgTEFOIG9mIHRoZSBDRSByb3V0ZXIu
PGJyPg0KJm5ic3A7PGJyPg0KLyBVc2UgYSBESENQdjYgcmVsYXkgaW4gdGhlIENQRS4gVGhlbiB0
aGVyZSBpc24ndCBhIHByb2JsZW0sIG5ldyBESENQdjYgb3B0aW9ucyB0aGF0IGFyZSB1bmtub3du
IGJ5IHRoZSBDUEUgd2lsbCBwYXNzIHJpZ2h0IHRocm91Z2ggaXQgdHJhbnNwYXJlbnRseS4gVGhl
IG9ubHkgY29tcGxpY2F0aW9uIGlzIHdoZW4gc3RhdGVmdWwgREhDUHY2IGFkZHJlc3NpbmcgaXMg
dXNlZCBvbiB0aGUgQ1BFIExBTiBpbnRlcmZhY2UsIGFuZCBJIHN1Z2dlc3RlZA0KIGEgaHlicmlk
IG1vZGUgb2Ygb3BlcmF0aW9uIGZvciBhIERIQ1B2NiBzZXJ2ZXIgaW4gdGhhdCBkcmFmdCB3aGlj
aCBJIHRoaW5rIHNvbHZlcyB0aGF0IHByb2JsZW0uPGJyPg0KPGJyPg0KT3RoZXJzLDxicj4NCjxi
cj4NCkFsc28sIHdoeSBkb2VzIG9uZSBuZWVkIGFuIFJBIE9wdGlvbiBHdWlkZWxpbmU/Jm5ic3A7
IFJGQzQ4NjEgc3BlY2lmaWVzIGEgVExWIGZvcm1hdCBhbmQgYW4gb3B0aW9uIFR5cGUuJm5ic3A7
IEkgZG9uJ3Qgc2VlIGFueXRoaW5nIGVsc2UgbmVlZGVkIGlmIEkgbmVlZCB0byBzcGVjaWZ5IGEg
bmV3IFJBIG9wdGlvbi4NCjxicj4NCjxicj4NClRoYW5rcyw8YnI+DQo8YnI+DQpIZW1hbnQ8YnI+
DQo8YnI+DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFNUQVJLLCBCQVJC
QVJBIEggWzxhIGhyZWY9Im1haWx0bzpiczc2NTJAYXR0LmNvbSI+bWFpbHRvOmJzNzY1MkBhdHQu
Y29tPC9hPl0NCjxicj4NClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDMxLCAyMDE1IDk6MjUgQU08YnI+
DQpUbzogSGVtYW50IFNpbmdoIChzaGVtYW50KTsgTWFyayBaWlogU21pdGg7IEJyaWFuIEhhYmVy
bWFuOyA8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+DQppcHY2QGlldGYub3JnPC9hPjxi
cj4NClN1YmplY3Q6IFJFOiBSQSBPcHRpb24gR3VpZGVsaW5lczxicj4NCiZuYnNwOzxicj4NCjxi
cj4NCjxicj4NCjxicj4NClJGQyA3MDg0IGFscmVhZHkgc2F5czogPGJyPg0KJm5ic3A7IEwtMTI6
Jm5ic3A7IFRoZSBJUHY2IENFIHJvdXRlciBTSE9VTEQgbWFrZSBhdmFpbGFibGUgYSBzdWJzZXQg
b2YgREhDUHY2PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBvcHRpb25z
IChhcyBsaXN0ZWQgaW4gU2VjdGlvbiA1LjMgb2YgW1JGQzM3MzZdKSByZWNlaXZlZCBmcm9tPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB0aGUgREhDUHY2IGNsaWVudCBv
biBpdHMgV0FOIGludGVyZmFjZSB0byBpdHMgTEFOLXNpZGUgREhDUHY2PGJyPg0KJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzZXJ2ZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_75B6FA9F576969419E42BECB86CB1B8916838870xmbrcdx06ciscoc_--


From nobody Fri Apr  3 04:33:22 2015
Return-Path: <volz@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 626A21A88EC for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nVthcS1xDzFd for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:33:16 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 883E61A87E6 for <ipv6@ietf.org>; Fri,  3 Apr 2015 04:33:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32778; q=dns/txt; s=iport; t=1428060796; x=1429270396; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=845Xhm7+xPo4EOvIYNT/F4UForFgqtHZlixkaDCuobc=; b=haoIF5BUSf/TRtKUSoPUWD3QFTTFQqHAGYWNi4OZdKZZjBcRxfoJbJRj +4SRSP3Mf32yhqE4asJhinGoeDGxKj2lcz6tY1s14gnBZP7n8OcLx9f8S 4kXUf3ASshxITf3+1Uq/5wJB7/hzLtuEmpvA1DoY+9n0LIna+kIYYOdxP w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AoDQDNeR5V/40NJK1cgkhDgSIMyCODSgKBLUwBAQEBAQF+hB4BAQEEGhNMDAQCAQgRBAEBIQcHMhQJCAIEDgWIGwMRzE0BAQEBAQEBAQEBAQEBAQEBAQEBAQEXiymCR4FnCUIGAQaDEYEWBYUQColBgg+IOYFHgR2DNYJghhxOgmeDSCKDb2+BBIE/AQEB
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="137912733"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-1.cisco.com with ESMTP; 03 Apr 2015 11:33:14 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t33BXEsx000597 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 11:33:14 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 06:33:14 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlnXXmv757w0ecSSL/v887950xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAB4Ta
Date: Fri, 3 Apr 2015 11:33:13 +0000
Message-ID: <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_AD05F764D89B410CB0500AE260C26D97ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/f38QsP4UHYQiokVVGmkNBN_F0d8>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 11:33:21 -0000

--_000_AD05F764D89B410CB0500AE260C26D97ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:

Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC=92s.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

--_000_AD05F764D89B410CB0500AE260C26D97ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>I didn't study the complete thread but I am sure everyone would unders=
tand that new options should be allowed to be requested. The ORO list canno=
t be frozen ... At the time the rfc was written, that was the list. But new=
 option documents are not required
 to update RFC3736.</div>
<div><br>
</div>
<div>There are no interop issues either as if either side (client or server=
) doesn't know of an option, it just doesn't include or ignores it.<br>
<br>
- Bernie (from iPad)</div>
<div><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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.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-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]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Could the DHCPv6 gurus in=
 Ralph, Bernie, and Ted please help resolve this thread for stateless DHCPv=
6 current vs. future options and the ORO option.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mark ZZZ=
 Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@ya=
hoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:b=
lack">Hi Hemant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.<o:p></=
o:p></span></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ - I think tex=
t you refer to in 5.3, &quot;Clients and servers use the following options =
to pass configuration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ So if I were =
implementing a stateless DHCPv6 server as per RFC3736, I'd think the implem=
entation was complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.<o:p=
></o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp; So the n=
ew options you want to serve can be served by the CE stateless DHCPv6 serve=
r.&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 serve=
r
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.<o=
:p></o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I also cannot=
 find text in RFC3315 or its updates on how to handle received options that=
 were not requested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.<o:p></o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ If it is poss=
ible to send a DHCPv6 client &quot;ORO type&quot; options that it didn't re=
quest, then the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.<o:p></o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Are you aware=
 of any CE DHCPv6 WAN client/DHCPv6 LAN server implementations that are unk=
nown DHCPv6 option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.<o:p></o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I think this =
level of DHCPv6 option transparency between CE LAN attached hosts and the u=
pstream SP's DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).<o:p></o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Regards,<o:p>=
</o:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Mark.<o:p></o=
:p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:=
p></span></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></o:=
p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC=92s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.<o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_AD05F764D89B410CB0500AE260C26D97ciscocom_--


From nobody Fri Apr  3 04:43:37 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF471A89A2 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyza4Em-9E-8 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:43:21 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58E391A88AB for <ipv6@ietf.org>; Fri,  3 Apr 2015 04:43:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41123; q=dns/txt; s=iport; t=1428061402; x=1429271002; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KfW1vmePgD6nHZ5nhaN5eS8e25jibMFuJ1cAmkWdKR8=; b=iAvaMpSrCMWad7fMsseTr8amRieLk7dS2IFP9QQfy7buGzADfd0kS8va y7skJV+YZJRuht2JVFS/TbrRfDQkwzK7eYQtEawKOnDB8j3WcDLTOurrz oBg4/p20eMczLhHZ9Ro3I1GBYY3iBxgLGKvFQqMRs6cjSHiQusZcFBwDX E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AuDQBkfB5V/5JdJa1cgkhDUlAMBcgeg0oCgS1MAQEBAQEBfoQeAQEBBBoTTAwEAgEIEQQBAQsWAQYHMhQJCAIEDgUIiBMDEcxSAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4spgkeBZwkRMQYBBoMRgRYFhRAKiUGCD4g5gmSDNYJghhxOgmeDSCKCAxyBUG+BBEB/AQEB
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="137965815"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-6.cisco.com with ESMTP; 03 Apr 2015 11:43:20 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t33BhIbC000386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 11:43:19 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 06:43:18 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAW1SA//+sUIA=
Date: Fri, 3 Apr 2015 11:43:17 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>
In-Reply-To: <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.158]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B891683896Exmbrcdx06ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XPSIbFqb7l92EkjAE45Kl8uOPlY>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 11:43:30 -0000

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

Bernie,

Appreciate the quick reply.  Let me summarize the issues and then you can c=
larify.


1.       The CE WAN interface does not include a new option in DHCPV6_NEW_O=
PTION1 in the ORO option of the SOLICIT to the server.  If the server is co=
nfigured to return the DHCPV6_NEW_OPTION1 to clients, then will the server =
reply with DHCPV6_NEW_OPTION1 even when the client did not request the opti=
on in the ORO?   In this scenario, no code changes on the CE, and just the =
server configuration takes care of the issue.

2.       The CE WAN interface does include a new option in DHCPV6_NEW_OPTIO=
N1 in the ORO option of the SOLICIT to the server.  If the server is config=
ured to return DHCPV6_NEW_OPTION1 to clients, then will the server reply wi=
th DHCPV6_NEW_OPTION1?

Mark,

Note Bernie agrees with how I and Wes Beebee (who I discussed this thread w=
ith) also interpreted RFC3736.  New options can be served by the stateless =
DHCPv6 server without revising RFC3736.

Thanks all,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:33 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ralph =
Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC's.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

--_000_75B6FA9F576969419E42BECB86CB1B891683896Exmbrcdx06ciscoc_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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.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";}
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:"Times New Roman","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;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:1463378006;
	mso-list-type:hybrid;
	mso-list-template-ids:809150956 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Appreciate the quick repl=
y.&nbsp; Let me summarize the issues and then you can clarify.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interf=
ace does not include a new option in DHCPV6_NEW_OPTION1 in the ORO option o=
f the SOLICIT to the server.&nbsp; If the server is configured
 to return the DHCPV6_NEW_OPTION1 to clients, then will the server reply wi=
th DHCPV6_NEW_OPTION1 even when the client did not request the option in th=
e ORO?&nbsp; &nbsp;In this scenario, no code changes on the CE, and just th=
e server configuration takes care of the issue.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interf=
ace does include a new option in DHCPV6_NEW_OPTION1 in the ORO option of th=
e SOLICIT to the server.&nbsp; If the server is configured
 to return DHCPV6_NEW_OPTION1 to clients, then will the server reply with D=
HCPV6_NEW_OPTION1?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mark,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Note Bernie agrees with h=
ow I and Wes Beebee (who I discussed this thread with) also interpreted RFC=
3736.&nbsp; New options can be served by the stateless DHCPv6
 server without revising RFC3736.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks all,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:33 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org;=
 Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I didn't study the complete thread but I am sure eve=
ryone would understand that new options should be allowed to be requested. =
The ORO list cannot be frozen ... At the time the rfc was written, that was=
 the list. But new option documents
 are not required to update RFC3736.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are no interop issues either as if either side=
 (client or server) doesn't know of an option, it just doesn't include or i=
gnores it.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Could the DHCPv6 gurus in=
 Ralph, Bernie, and Ted please help resolve this thread for stateless DHCPv=
6 current vs. future options and the ORO option.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mark ZZZ=
 Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@ya=
hoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:b=
lack">Hi Hemant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.</span>=
<o:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ - I think tex=
t you refer to in 5.3, &quot;Clients and servers use the following options =
to pass configuration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ So if I were =
implementing a stateless DHCPv6 server as per RFC3736, I'd think the implem=
entation was complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.</sp=
an><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp; So the n=
ew options you want to serve can be served by the CE stateless DHCPv6 serve=
r.&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 serve=
r
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.</=
span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I also cannot=
 find text in RFC3315 or its updates on how to handle received options that=
 were not requested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ If it is poss=
ible to send a DHCPv6 client &quot;ORO type&quot; options that it didn't re=
quest, then the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Are you aware=
 of any CE DHCPv6 WAN client/DHCPv6 LAN server implementations that are unk=
nown DHCPv6 option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I think this =
level of DHCPv6 option transparency between CE LAN attached hosts and the u=
pstream SP's DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Regards,</spa=
n><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Mark.</span><=
o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC&#8217;s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</body>
</html>

--_000_75B6FA9F576969419E42BECB86CB1B891683896Exmbrcdx06ciscoc_--


From nobody Fri Apr  3 04:48:08 2015
Return-Path: <volz@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 198CB1A88F5 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i54KEfLUhR22 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 04:48:03 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519FA1A88AB for <ipv6@ietf.org>; Fri,  3 Apr 2015 04:48:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=42402; q=dns/txt; s=iport; t=1428061683; x=1429271283; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dHgjb2pUaR9A2zNEWfsIGtme0KfMlPInVW3Vxif9PXo=; b=Qg6rcHP5j1kyzQEF3Ay16D1OETnMMwQGChvNFjwaFgJB67ErwWWtBsD+ 8PV6iPVG+21eUaWy+wQmNGwyyCZOBbQPfHd/uTAGW3tJa7mDmmKxYVOS0 Uoxpx9cp3hycvnlLA9zDoEtdIYYjazRXZMQnE8Q8Y85MNuJ/chMKWy+GL g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ApDQDEfR5V/5RdJa1cgkhDgSIMyCODSgKBLUwBAQEBAQF+hB4BAQEEGhNMDAQCAQgRBAEBIQEGBzIUCQgCBA4FiBsDEcxOAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4spgkeBZwlCBgEGgxGBFgWFEAqJQYIPiDmBR4EdgzWCYIYcToJng0giggMcgVBvgQSBPwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="137968311"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-2.cisco.com with ESMTP; 03 Apr 2015 11:48:01 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t33Bm1Km030792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 11:48:01 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 06:48:01 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlnXXmv757w0ecSSL/v887950xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAB4TagABWoID//62BWA==
Date: Fri, 3 Apr 2015 11:48:00 +0000
Message-ID: <F07AD006-79CB-4E37-A2D4-2E1EAEBFD381@cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>, <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_F07AD00679CB4E37A2D42E1EAEBFD381ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/v2Q10DBbwSwQQRE6Jz79KbEPQ84>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 11:48:08 -0000

--_000_F07AD00679CB4E37A2D42E1EAEBFD381ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).

#2 is normal DHCP operation.

Note that while I think you were discussing stateless, it is true for state=
ful and stateless dhcp.

- Bernie (from iPad)

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:

Bernie,

Appreciate the quick reply.  Let me summarize the issues and then you can c=
larify.


1.       The CE WAN interface does not include a new option in DHCPV6_NEW_O=
PTION1 in the ORO option of the SOLICIT to the server.  If the server is co=
nfigured to return the DHCPV6_NEW_OPTION1 to clients, then will the server =
reply with DHCPV6_NEW_OPTION1 even when the client did not request the opti=
on in the ORO?   In this scenario, no code changes on the CE, and just the =
server configuration takes care of the issue.

2.       The CE WAN interface does include a new option in DHCPV6_NEW_OPTIO=
N1 in the ORO option of the SOLICIT to the server.  If the server is config=
ured to return DHCPV6_NEW_OPTION1 to clients, then will the server reply wi=
th DHCPV6_NEW_OPTION1?

Mark,

Note Bernie agrees with how I and Wes Beebee (who I discussed this thread w=
ith) also interpreted RFC3736.  New options can be served by the stateless =
DHCPv6 server without revising RFC3736.

Thanks all,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:33 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC=92s.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

--_000_F07AD00679CB4E37A2D42E1EAEBFD381ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>All options MUST be in ORO for server to return (there are some &quot;=
protocol&quot; options, such as client-id and server-id that are NOT suppos=
ed to be in ORO). So client controls the options it gets. So #1 is not true=
 (some servers, such as CPNR, can be configured
 to return options the client did not request, but generally that is useles=
s since the client will most likely ignore it).</div>
<div><br>
</div>
<div>#2 is normal DHCP operation.</div>
<div><br>
</div>
<div>Note that while I think you were discussing stateless, it is true for =
stateful and stateless dhcp.<br>
<br>
- Bernie (from iPad)</div>
<div><br>
On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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.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";}
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:"Times New Roman","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;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:1463378006;
	mso-list-type:hybrid;
	mso-list-template-ids:809150956 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Appreciate the quick repl=
y.&nbsp; Let me summarize the issues and then you can clarify.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"=
mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><!--[endif]--><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN in=
terface does not include a new option in DHCPV6_NEW_OPTION1 in the ORO opti=
on of the SOLICIT to the server.&nbsp; If the server is configured
 to return the DHCPV6_NEW_OPTION1 to clients, then will the server reply wi=
th DHCPV6_NEW_OPTION1 even when the client did not request the option in th=
e ORO?&nbsp; &nbsp;In this scenario, no code changes on the CE, and just th=
e server configuration takes care of the issue.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><!--[if !supportLists]--><span style=3D"font-size:11.0pt;font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"=
mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><!--[endif]--><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN in=
terface does include a new option in DHCPV6_NEW_OPTION1 in the ORO option o=
f the SOLICIT to the server.&nbsp; If the server is configured
 to return DHCPV6_NEW_OPTION1 to clients, then will the server reply with D=
HCPV6_NEW_OPTION1?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mark,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Note Bernie agrees with h=
ow I and Wes Beebee (who I discussed this thread with) also interpreted RFC=
3736.&nbsp; New options can be served by the stateless DHCPv6
 server without revising RFC3736.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks all,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:33 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I didn't study the complete thread but I am sure eve=
ryone would understand that new options should be allowed to be requested. =
The ORO list cannot be frozen ... At the time the rfc was written, that was=
 the list. But new option documents
 are not required to update RFC3736.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are no interop issues either as if either side=
 (client or server) doesn't know of an option, it just doesn't include or i=
gnores it.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Could the DHCPv6 gurus in=
 Ralph, Bernie, and Ted please help resolve this thread for stateless DHCPv=
6 current vs. future options and the ORO option.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mark ZZZ=
 Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@ya=
hoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:b=
lack">Hi Hemant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.</span>=
<o:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ - I think tex=
t you refer to in 5.3, &quot;Clients and servers use the following options =
to pass configuration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ So if I were =
implementing a stateless DHCPv6 server as per RFC3736, I'd think the implem=
entation was complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.</sp=
an><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp; So the n=
ew options you want to serve can be served by the CE stateless DHCPv6 serve=
r.&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 serve=
r
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.</=
span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I also cannot=
 find text in RFC3315 or its updates on how to handle received options that=
 were not requested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ If it is poss=
ible to send a DHCPv6 client &quot;ORO type&quot; options that it didn't re=
quest, then the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Are you aware=
 of any CE DHCPv6 WAN client/DHCPv6 LAN server implementations that are unk=
nown DHCPv6 option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I think this =
level of DHCPv6 option transparency between CE LAN attached hosts and the u=
pstream SP's DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Regards,</spa=
n><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Mark.</span><=
o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC=92s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>

--_000_F07AD00679CB4E37A2D42E1EAEBFD381ciscocom_--


From nobody Fri Apr  3 05:28:39 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F871A90DB for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 05:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id esdqQxGyYxRP for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 05:28:28 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2F541A90CC for <ipv6@ietf.org>; Fri,  3 Apr 2015 05:28:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=46688; q=dns/txt; s=iport; t=1428064108; x=1429273708; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Z/Gd6CK9wNm244jJSIKRi6bUbABUxX1OH5iSOutzkkA=; b=JzHh/+Mv7we/fXdcWQohWIjGd//F1jBeXAqBFqjT9qjL8GvtTr/2vQNc UYJllCCF/6HQd69eYGA2q/dSga5LhiqvKEhxQ4wEs7gMDhIUqvOFmN+lt +CQX0Qr+ZnwAB0D6H2B/WorTLvSvRAyGlKCp5vIdzJPaL7AwZCa/joriL A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYCwDlhh5V/40NJK1cgkhDUlAMBcgeg0oCgS1MAQEBAQEBfoQeAQEBBBoTTAwEAgEIEQQBAQsWAQYHMhQJCAIEDgUIiBMDEcxqAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4spgkeBZwkRMQYBBoMRgRYFhRAKiUKCD4g5gmSDNYJghh1OgmeDSCKCAxyBUG+BBEB/AQEB
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="137975793"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-2.cisco.com with ESMTP; 03 Apr 2015 12:28:25 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t33CSPRW006383 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 12:28:25 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 07:28:25 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAW1SA//+sUICAAFfRAP//smqA
Date: Fri, 3 Apr 2015 12:28:24 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>, <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com> <F07AD006-79CB-4E37-A2D4-2E1EAEBFD381@cisco.com>
In-Reply-To: <F07AD006-79CB-4E37-A2D4-2E1EAEBFD381@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.158]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B891683899Cxmbrcdx06ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Uyb0cZatOmouT5I4A35hL8OkTXQ>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 12:28:38 -0000

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

Bernie,

Got it - thanks much!  So the CE router implementation has to change to be =
configurable to include a new DHCPv6 option in the ORO for the WAN interfac=
e.  Once the new option is returned by the server, the CE uses the new opti=
on for stateless DHCPv6 services on the LAN.  Note, it is the same service =
provider who has configured the CE for the new DHCPv6 option and thus the s=
ame service provider also provisions the DHCPv6 server to return the new op=
tion, if asked for.  There is no need for DHCPv6 relay in the CE for this n=
ew option support.

In summary, both Mark's and Barbara's goals are met.

Thanks,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:48 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ralph =
Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).

#2 is normal DHCP operation.

Note that while I think you were discussing stateless, it is true for state=
ful and stateless dhcp.

- Bernie (from iPad)

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Bernie,

Appreciate the quick reply.  Let me summarize the issues and then you can c=
larify.


1.     The CE WAN interface does not include a new option in DHCPV6_NEW_OPT=
ION1 in the ORO option of the SOLICIT to the server.  If the server is conf=
igured to return the DHCPV6_NEW_OPTION1 to clients, then will the server re=
ply with DHCPV6_NEW_OPTION1 even when the client did not request the option=
 in the ORO?   In this scenario, no code changes on the CE, and just the se=
rver configuration takes care of the issue.

2.     The CE WAN interface does include a new option in DHCPV6_NEW_OPTION1=
 in the ORO option of the SOLICIT to the server.  If the server is configur=
ed to return DHCPV6_NEW_OPTION1 to clients, then will the server reply with=
 DHCPV6_NEW_OPTION1?

Mark,

Note Bernie agrees with how I and Wes Beebee (who I discussed this thread w=
ith) also interpreted RFC3736.  New options can be served by the stateless =
DHCPv6 server without revising RFC3736.

Thanks all,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:33 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC's.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

--_000_75B6FA9F576969419E42BECB86CB1B891683899Cxmbrcdx06ciscoc_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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.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";}
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:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:1463378006;
	mso-list-type:hybrid;
	mso-list-template-ids:809150956 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Got it &#8211; thanks muc=
h!&nbsp; So the CE router implementation has to change to be configurable t=
o include a new DHCPv6 option in the ORO for the WAN interface.&nbsp; Once
 the new option is returned by the server, the CE uses the new option for s=
tateless DHCPv6 services on the LAN.&nbsp; Note, it is the same service pro=
vider who has configured the CE for the new DHCPv6 option and thus the same=
 service provider also provisions the
 DHCPv6 server to return the new option, if asked for.&nbsp; There is no ne=
ed for DHCPv6 relay in the CE for this new option support.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In summary, both Mark&#82=
17;s and Barbara&#8217;s goals are met.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:48 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org;=
 Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">All options MUST be in ORO for server to return (the=
re are some &quot;protocol&quot; options, such as client-id and server-id t=
hat are NOT supposed to be in ORO). So client controls the options it gets.=
 So #1 is not true (some servers, such as CPNR,
 can be configured to return options the client did not request, but genera=
lly that is useless since the client will most likely ignore it).<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">#2 is normal DHCP operation.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Note that while I think you were discussing stateles=
s, it is true for stateful and stateless dhcp.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Appreciate the quick repl=
y.&nbsp; Let me summarize the issues and then you can clarify.</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interface doe=
s not include a new option in DHCPV6_NEW_OPTION1 in the ORO option of the S=
OLICIT to the server.&nbsp; If the server is configured to
 return the DHCPV6_NEW_OPTION1 to clients, then will the server reply with =
DHCPV6_NEW_OPTION1 even when the client did not request the option in the O=
RO?&nbsp; &nbsp;In this scenario, no code changes on the CE, and just the s=
erver configuration takes care of the issue.</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interface doe=
s include a new option in DHCPV6_NEW_OPTION1 in the ORO option of the SOLIC=
IT to the server.&nbsp; If the server is configured to return
 DHCPV6_NEW_OPTION1 to clients, then will the server reply with DHCPV6_NEW_=
OPTION1?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mark,</span><o:p></o:p></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Note Bernie agrees with h=
ow I and Wes Beebee (who I discussed this thread with) also interpreted RFC=
3736.&nbsp; New options can be served by the stateless DHCPv6
 server without revising RFC3736.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks all,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:33 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">I didn't study the complete thread but I am sure eve=
ryone would understand that new options should be allowed to be requested. =
The ORO list cannot be frozen ... At the time the rfc was written, that was=
 the list. But new option documents
 are not required to update RFC3736.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are no interop issues either as if either side=
 (client or server) doesn't know of an option, it just doesn't include or i=
gnores it.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Could the DHCPv6 gurus in=
 Ralph, Bernie, and Ted please help resolve this thread for stateless DHCPv=
6 current vs. future options and the ORO option.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mark ZZZ=
 Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@ya=
hoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:b=
lack">Hi Hemant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.</span>=
<o:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ - I think tex=
t you refer to in 5.3, &quot;Clients and servers use the following options =
to pass configuration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ So if I were =
implementing a stateless DHCPv6 server as per RFC3736, I'd think the implem=
entation was complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.</sp=
an><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp; So the n=
ew options you want to serve can be served by the CE stateless DHCPv6 serve=
r.&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 serve=
r
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.</=
span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I also cannot=
 find text in RFC3315 or its updates on how to handle received options that=
 were not requested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ If it is poss=
ible to send a DHCPv6 client &quot;ORO type&quot; options that it didn't re=
quest, then the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Are you aware=
 of any CE DHCPv6 WAN client/DHCPv6 LAN server implementations that are unk=
nown DHCPv6 option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I think this =
level of DHCPv6 option transparency between CE LAN attached hosts and the u=
pstream SP's DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Regards,</spa=
n><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Mark.</span><=
o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC&#8217;s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</body>
</html>

--_000_75B6FA9F576969419E42BECB86CB1B891683899Cxmbrcdx06ciscoc_--


From nobody Fri Apr  3 05:36:29 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0967E1A916B for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 05:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wt_Z7ICfFGf for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 05:36:17 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C9BE1A9165 for <ipv6@ietf.org>; Fri,  3 Apr 2015 05:36:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=48766; q=dns/txt; s=iport; t=1428064577; x=1429274177; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ex97zxeTkk8jQOYYCNpEPpZp2v2C4g5hdzXDE6829XE=; b=QaYoUiwymV2WGul3znaSgfCUs5VDxu5Tml/TQ9nRvBimDzvLflnER3o6 E92j6fsdBDChdURNvf3I//nl9p9vpXfSZQ0pXUuZxLhygj+dbcTmetrGi S3OX64C1viH9ib3QVi/Xgi8wLElCxJCEXam+3H688imgLH2+oQXQO59/K M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYCwAGiR5V/4MNJK1cgkhDUlAMBcgeg0oCgS1MAQEBAQEBfoQeAQEBBBoTTAwEAgEIEQQBAQsWAQYHMhQJCAIEAQ0FCIgTAxHMdwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLKYJHgWcJETEGAQaDEYEWBYUQColCgg+IOYJkgzWCYIYdToJng0giggMcgVBvgQRAfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="137980298"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP; 03 Apr 2015 12:35:59 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t33CZxHn008696 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 12:35:59 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 07:35:59 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAW1SA//+sUICAAFfRAP//smqAAADWtxA=
Date: Fri, 3 Apr 2015 12:35:59 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B89168389D0@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>, <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com> <F07AD006-79CB-4E37-A2D4-2E1EAEBFD381@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.158]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B89168389D0xmbrcdx06ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Fip0O_oZYhNEzPi66FoNi_D1vew>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 12:36:28 -0000

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

Also, since RFC7084 was managed in v6ops, the minor DHC update to the CE ro=
uter to cater to Mark's request, I plan to submit a short note to v6ops.

Hemant

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (sheman=
t)
Sent: Friday, April 03, 2015 8:28 AM
To: Bernie Volz (volz)
Cc: ipv6@ietf.org; Brian Haberman; Ralph Droms (rdroms); Ted Lemon
Subject: RE: RA Option Guidelines

Bernie,

Got it - thanks much!  So the CE router implementation has to change to be =
configurable to include a new DHCPv6 option in the ORO for the WAN interfac=
e.  Once the new option is returned by the server, the CE uses the new opti=
on for stateless DHCPv6 services on the LAN.  Note, it is the same service =
provider who has configured the CE for the new DHCPv6 option and thus the s=
ame service provider also provisions the DHCPv6 server to return the new op=
tion, if asked for.  There is no need for DHCPv6 relay in the CE for this n=
ew option support.

In summary, both Mark's and Barbara's goals are met.

Thanks,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:48 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).

#2 is normal DHCP operation.

Note that while I think you were discussing stateless, it is true for state=
ful and stateless dhcp.

- Bernie (from iPad)

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Bernie,

Appreciate the quick reply.  Let me summarize the issues and then you can c=
larify.


1.     The CE WAN interface does not include a new option in DHCPV6_NEW_OPT=
ION1 in the ORO option of the SOLICIT to the server.  If the server is conf=
igured to return the DHCPV6_NEW_OPTION1 to clients, then will the server re=
ply with DHCPV6_NEW_OPTION1 even when the client did not request the option=
 in the ORO?   In this scenario, no code changes on the CE, and just the se=
rver configuration takes care of the issue.

2.     The CE WAN interface does include a new option in DHCPV6_NEW_OPTION1=
 in the ORO option of the SOLICIT to the server.  If the server is configur=
ed to return DHCPV6_NEW_OPTION1 to clients, then will the server reply with=
 DHCPV6_NEW_OPTION1?

Mark,

Note Bernie agrees with how I and Wes Beebee (who I discussed this thread w=
ith) also interpreted RFC3736.  New options can be served by the stateless =
DHCPv6 server without revising RFC3736.

Thanks all,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:33 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC's.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

--_000_75B6FA9F576969419E42BECB86CB1B89168389D0xmbrcdx06ciscoc_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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.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";}
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:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:1463378006;
	mso-list-type:hybrid;
	mso-list-template-ids:809150956 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Also, since RFC7084 was m=
anaged in v6ops, the minor DHC update to the CE router to cater to Mark&#82=
17;s request, I plan to submit a short note to v6ops.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ipv6 [ma=
ilto:ipv6-bounces@ietf.org]
<b>On Behalf Of </b>Hemant Singh (shemant)<br>
<b>Sent:</b> Friday, April 03, 2015 8:28 AM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> ipv6@ietf.org; Brian Haberman; Ralph Droms (rdroms); Ted Lemon<b=
r>
<b>Subject:</b> RE: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Got it &#8211; thanks muc=
h!&nbsp; So the CE router implementation has to change to be configurable t=
o include a new DHCPv6 option in the ORO for the WAN interface.&nbsp; Once
 the new option is returned by the server, the CE uses the new option for s=
tateless DHCPv6 services on the LAN.&nbsp; Note, it is the same service pro=
vider who has configured the CE for the new DHCPv6 option and thus the same=
 service provider also provisions the
 DHCPv6 server to return the new option, if asked for.&nbsp; There is no ne=
ed for DHCPv6 relay in the CE for this new option support.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In summary, both Mark&#82=
17;s and Barbara&#8217;s goals are met.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:48 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">All options MUST be in ORO for server to return (the=
re are some &quot;protocol&quot; options, such as client-id and server-id t=
hat are NOT supposed to be in ORO). So client controls the options it gets.=
 So #1 is not true (some servers, such as CPNR,
 can be configured to return options the client did not request, but genera=
lly that is useless since the client will most likely ignore it).<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">#2 is normal DHCP operation.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Note that while I think you were discussing stateles=
s, it is true for stateful and stateless dhcp.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Appreciate the quick repl=
y.&nbsp; Let me summarize the issues and then you can clarify.</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interface doe=
s not include a new option in DHCPV6_NEW_OPTION1 in the ORO option of the S=
OLICIT to the server.&nbsp; If the server is configured to
 return the DHCPV6_NEW_OPTION1 to clients, then will the server reply with =
DHCPV6_NEW_OPTION1 even when the client did not request the option in the O=
RO?&nbsp; &nbsp;In this scenario, no code changes on the CE, and just the s=
erver configuration takes care of the issue.</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interface doe=
s include a new option in DHCPV6_NEW_OPTION1 in the ORO option of the SOLIC=
IT to the server.&nbsp; If the server is configured to return
 DHCPV6_NEW_OPTION1 to clients, then will the server reply with DHCPV6_NEW_=
OPTION1?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mark,</span><o:p></o:p></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Note Bernie agrees with h=
ow I and Wes Beebee (who I discussed this thread with) also interpreted RFC=
3736.&nbsp; New options can be served by the stateless DHCPv6
 server without revising RFC3736.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks all,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:33 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">I didn't study the complete thread but I am sure eve=
ryone would understand that new options should be allowed to be requested. =
The ORO list cannot be frozen ... At the time the rfc was written, that was=
 the list. But new option documents
 are not required to update RFC3736.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are no interop issues either as if either side=
 (client or server) doesn't know of an option, it just doesn't include or i=
gnores it.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Could the DHCPv6 gurus in=
 Ralph, Bernie, and Ted please help resolve this thread for stateless DHCPv=
6 current vs. future options and the ORO option.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mark ZZZ=
 Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@ya=
hoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:b=
lack">Hi Hemant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.</span>=
<o:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ - I think tex=
t you refer to in 5.3, &quot;Clients and servers use the following options =
to pass configuration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ So if I were =
implementing a stateless DHCPv6 server as per RFC3736, I'd think the implem=
entation was complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.</sp=
an><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp; So the n=
ew options you want to serve can be served by the CE stateless DHCPv6 serve=
r.&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 serve=
r
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.</=
span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I also cannot=
 find text in RFC3315 or its updates on how to handle received options that=
 were not requested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ If it is poss=
ible to send a DHCPv6 client &quot;ORO type&quot; options that it didn't re=
quest, then the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Are you aware=
 of any CE DHCPv6 WAN client/DHCPv6 LAN server implementations that are unk=
nown DHCPv6 option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I think this =
level of DHCPv6 option transparency between CE LAN attached hosts and the u=
pstream SP's DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Regards,</spa=
n><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Mark.</span><=
o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC&#8217;s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</body>
</html>

--_000_75B6FA9F576969419E42BECB86CB1B89168389D0xmbrcdx06ciscoc_--


From nobody Fri Apr  3 05:39:01 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99E9A1A9139 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 05:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gh9GS7PvvtFh for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 05:38:59 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 AEAB51A90F8 for <ipv6@ietf.org>; Fri,  3 Apr 2015 05:38:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 5D3ABDA00CE; Fri,  3 Apr 2015 12:38:59 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 3 Apr 2015 05:38:59 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: RA Option Guidelines
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com>
Date: Fri, 3 Apr 2015 08:38:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <71AB54EB-A061-4A38-9C02-DEF4AF3D3CE5@nominum.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6KcsVZQp5owDjINNEDF7TX8WB6M>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Bernie Volz <volz@cisco.com>, Brian Haberman <brian@innovationslab.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 12:39:00 -0000

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com> =
wrote:
> 1.       The CE WAN interface does not include a new option in =
DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the server.  If =
the server is configured to return the DHCPV6_NEW_OPTION1 to clients, =
then will the server reply with DHCPV6_NEW_OPTION1 even when the client =
did not request the option in the ORO?   In this scenario, no code =
changes on the CE, and just the server configuration takes care of the =
issue.

There's no point in the DHCP server sending an option the client didn't =
request.


From nobody Fri Apr  3 06:29:02 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A2A1A92DF for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 06:29:01 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dnekaRfVqKcB for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 06:29:00 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31D5F1A92BA for <ipv6@ietf.org>; Fri,  3 Apr 2015 06:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=412; q=dns/txt; s=iport; t=1428067740; x=1429277340; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hDhzBH11fsDkwz94DJ1/Y548FXlic2+31K4BxiLpVTw=; b=OsTrsfntbe1IKseNM2Z28x7XKUkU+KmzoFk+w2LWxO9rZH9oZxtsFo8b 2isP59eUw+r8arwlKJXJZmIn0pCC4CR976LHy87v9OM815xxfbpIlHSPf 3e0gTYsFneatV1VHFCUItTzz7Fwjg+RD+VpkhsIsgM5SwQ9hhAU+RDiM0 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A+BQDYlB5V/4kNJK1cgwuBLgXLaAKBL0wBAQEBAQF+hB4BAQEEOj8MBAIBCBEEAQELFAkHMhQJCAIEDgUIiCfNAQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLKYQuGjEHBoMRgRYBBJBrnkwig29vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600"; d="scan'208";a="137937972"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-1.cisco.com with ESMTP; 03 Apr 2015 13:28:59 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t33DSwuh015243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 13:28:59 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 08:28:58 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAW1SA//+sUICAAGYKAP//ueWg
Date: Fri, 3 Apr 2015 13:28:57 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B8916838A4F@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com> <71AB54EB-A061-4A38-9C02-DEF4AF3D3CE5@nominum.com>
In-Reply-To: <71AB54EB-A061-4A38-9C02-DEF4AF3D3CE5@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.71.118]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pv1JqmobQxkECD3ltSpM_KHOBGo>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Brian Haberman <brian@innovationslab.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 13:29:01 -0000

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Friday, April 03, 2015 8:39 AM
To: Hemant Singh (shemant)
Cc: Bernie Volz (volz); Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; i=
pv6@ietf.org; Ralph Droms (rdroms)
Subject: Re: RA Option Guidelines

>There's no point in the DHCP server sending an option the client didn't re=
quest.

Thanks, Ted.

Hemant


From nobody Fri Apr  3 06:43:26 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63CC1A90F9 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 06:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHf_yfU9_t11 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 06:43:15 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEEE01A8ABD for <ipv6@ietf.org>; Fri,  3 Apr 2015 06:43:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=51888; q=dns/txt; s=iport; t=1428068594; x=1429278194; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=yGaVrFX9i+iiRGAoVeNudahlnq75XCsYtQ3O5oMbIp8=; b=GU/l83uaSJZzxOIVUo8PEkav2Cr+tbPuqcAB/nsmNpkUGZEtmXhB3BvR JRS9TP2B7FWjQRzBpVJe2DuWsO9c94ninTCIPDCLbeUZGKSmgB21IdsWD NvzWUrQHtkBFYfyeAGBT2f1olucWgU1NodolXYhK9T1MI5y7/oDYgN0JD U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYCwC+mB5V/40NJK1cgkhDUlAMBcgeg0oCgS9MAQEBAQEBfoQeAQEBBBoTTAwEAgEIEQQBAQsWAQYHMhQJCAIEAQ0FCIgTAxHMfwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLKYJHgWcJETEGAQaDEYEWBYUQColCgg+IOYJkgzWCYIYdToJng0giggMcgVBvgQRAfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,517,1422921600";  d="scan'208,217";a="137994445"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-2.cisco.com with ESMTP; 03 Apr 2015 13:43:10 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t33DhAmW017319 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Apr 2015 13:43:10 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 08:43:10 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlpWnT4rYh306OWNEaYMLZKp0xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAW1SA//+sUICAAFfRAP//smqAAADWtxAAAkZo0A==
Date: Fri, 3 Apr 2015 13:43:09 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B8916838A68@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>, <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com> <F07AD006-79CB-4E37-A2D4-2E1EAEBFD381@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com> <75B6FA9F576969419E42BECB86CB1B89168389D0@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B89168389D0@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.71.118]
Content-Type: multipart/alternative; boundary="_000_75B6FA9F576969419E42BECB86CB1B8916838A68xmbrcdx06ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LZhBl6IaCb3ZZt-U9JU3v6J0dI8>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 13:43:25 -0000

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

Hmm, after more discussion, I am now corrected that a new document is not n=
eeded.  RFC 7084 does not block a new DHCPv6 option to be included in the O=
RO sent by the WAN.  Thus if the CE is configured to use a new DHCPv6 optio=
n, the CE will work fine.  The CE includes the new option in the ORO on the=
 WAN and serves the new option to the LAN via stateless DHCPv6 operation.

How the CE is configured for a new DHCPv6 option is out of scope for RFC708=
4.

Hemant

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (sheman=
t)
Sent: Friday, April 03, 2015 8:36 AM
To: Bernie Volz (volz); Fred Baker (fred)
Cc: Brian Haberman; ipv6@ietf.org; Ted Lemon; Ralph Droms (rdroms)
Subject: RE: RA Option Guidelines

Also, since RFC7084 was managed in v6ops, the minor DHC update to the CE ro=
uter to cater to Mark's request, I plan to submit a short note to v6ops.

Hemant

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (sheman=
t)
Sent: Friday, April 03, 2015 8:28 AM
To: Bernie Volz (volz)
Cc: ipv6@ietf.org<mailto:ipv6@ietf.org>; Brian Haberman; Ralph Droms (rdrom=
s); Ted Lemon
Subject: RE: RA Option Guidelines

Bernie,

Got it - thanks much!  So the CE router implementation has to change to be =
configurable to include a new DHCPv6 option in the ORO for the WAN interfac=
e.  Once the new option is returned by the server, the CE uses the new opti=
on for stateless DHCPv6 services on the LAN.  Note, it is the same service =
provider who has configured the CE for the new DHCPv6 option and thus the s=
ame service provider also provisions the DHCPv6 server to return the new op=
tion, if asked for.  There is no need for DHCPv6 relay in the CE for this n=
ew option support.

In summary, both Mark's and Barbara's goals are met.

Thanks,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:48 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).

#2 is normal DHCP operation.

Note that while I think you were discussing stateless, it is true for state=
ful and stateless dhcp.

- Bernie (from iPad)

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Bernie,

Appreciate the quick reply.  Let me summarize the issues and then you can c=
larify.


1.     The CE WAN interface does not include a new option in DHCPV6_NEW_OPT=
ION1 in the ORO option of the SOLICIT to the server.  If the server is conf=
igured to return the DHCPV6_NEW_OPTION1 to clients, then will the server re=
ply with DHCPV6_NEW_OPTION1 even when the client did not request the option=
 in the ORO?   In this scenario, no code changes on the CE, and just the se=
rver configuration takes care of the issue.

2.     The CE WAN interface does include a new option in DHCPV6_NEW_OPTION1=
 in the ORO option of the SOLICIT to the server.  If the server is configur=
ed to return DHCPV6_NEW_OPTION1 to clients, then will the server reply with=
 DHCPV6_NEW_OPTION1?

Mark,

Note Bernie agrees with how I and Wes Beebee (who I discussed this thread w=
ith) also interpreted RFC3736.  New options can be served by the stateless =
DHCPv6 server without revising RFC3736.

Thanks all,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:33 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC's.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

--_000_75B6FA9F576969419E42BECB86CB1B8916838A68xmbrcdx06ciscoc_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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.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";}
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:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:1463378006;
	mso-list-type:hybrid;
	mso-list-template-ids:809150956 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hmm, after more discussio=
n, I am now corrected that a new document is not needed.&nbsp; RFC 7084 doe=
s not block a new DHCPv6 option to be included in the ORO sent
 by the WAN.&nbsp; Thus if the CE is configured to use a new DHCPv6 option,=
 the CE will work fine.&nbsp; The CE includes the new option in the ORO on =
the WAN and serves the new option to the LAN via stateless DHCPv6 operation=
.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">How the CE is configured =
for a new DHCPv6 option is out of scope for RFC7084.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ipv6 [ma=
ilto:ipv6-bounces@ietf.org]
<b>On Behalf Of </b>Hemant Singh (shemant)<br>
<b>Sent:</b> Friday, April 03, 2015 8:36 AM<br>
<b>To:</b> Bernie Volz (volz); Fred Baker (fred)<br>
<b>Cc:</b> Brian Haberman; ipv6@ietf.org; Ted Lemon; Ralph Droms (rdroms)<b=
r>
<b>Subject:</b> RE: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Also, since RFC7084 was m=
anaged in v6ops, the minor DHC update to the CE router to cater to Mark&#82=
17;s request, I plan to submit a short note to v6ops.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ipv6 [<a=
 href=3D"mailto:ipv6-bounces@ietf.org">mailto:ipv6-bounces@ietf.org</a>]
<b>On Behalf Of </b>Hemant Singh (shemant)<br>
<b>Sent:</b> Friday, April 03, 2015 8:28 AM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>; Brian Haberm=
an; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> RE: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Got it &#8211; thanks muc=
h!&nbsp; So the CE router implementation has to change to be configurable t=
o include a new DHCPv6 option in the ORO for the WAN interface.&nbsp; Once
 the new option is returned by the server, the CE uses the new option for s=
tateless DHCPv6 services on the LAN.&nbsp; Note, it is the same service pro=
vider who has configured the CE for the new DHCPv6 option and thus the same=
 service provider also provisions the
 DHCPv6 server to return the new option, if asked for.&nbsp; There is no ne=
ed for DHCPv6 relay in the CE for this new option support.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In summary, both Mark&#82=
17;s and Barbara&#8217;s goals are met.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:48 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">All options MUST be in ORO for server to return (the=
re are some &quot;protocol&quot; options, such as client-id and server-id t=
hat are NOT supposed to be in ORO). So client controls the options it gets.=
 So #1 is not true (some servers, such as CPNR,
 can be configured to return options the client did not request, but genera=
lly that is useless since the client will most likely ignore it).<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">#2 is normal DHCP operation.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Note that while I think you were discussing stateles=
s, it is true for stateful and stateless dhcp.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Appreciate the quick repl=
y.&nbsp; Let me summarize the issues and then you can clarify.</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interface doe=
s not include a new option in DHCPV6_NEW_OPTION1 in the ORO option of the S=
OLICIT to the server.&nbsp; If the server is configured to
 return the DHCPV6_NEW_OPTION1 to clients, then will the server reply with =
DHCPV6_NEW_OPTION1 even when the client did not request the option in the O=
RO?&nbsp; &nbsp;In this scenario, no code changes on the CE, and just the s=
erver configuration takes care of the issue.</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The CE WAN interface doe=
s include a new option in DHCPV6_NEW_OPTION1 in the ORO option of the SOLIC=
IT to the server.&nbsp; If the server is configured to return
 DHCPV6_NEW_OPTION1 to clients, then will the server reply with DHCPV6_NEW_=
OPTION1?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mark,</span><o:p></o:p></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Note Bernie agrees with h=
ow I and Wes Beebee (who I discussed this thread with) also interpreted RFC=
3736.&nbsp; New options can be served by the stateless DHCPv6
 server without revising RFC3736.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks all,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bernie V=
olz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:33 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">I didn't study the complete thread but I am sure eve=
ryone would understand that new options should be allowed to be requested. =
The ORO list cannot be frozen ... At the time the rfc was written, that was=
 the list. But new option documents
 are not required to update RFC3736.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are no interop issues either as if either side=
 (client or server) doesn't know of an option, it just doesn't include or i=
gnores it.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Could the DHCPv6 gurus in=
 Ralph, Bernie, and Ted please help resolve this thread for stateless DHCPv=
6 current vs. future options and the ORO option.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hemant</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mark ZZZ=
 Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@ya=
hoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:b=
lack">Hi Hemant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.</span>=
<o:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ - I think tex=
t you refer to in 5.3, &quot;Clients and servers use the following options =
to pass configuration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ So if I were =
implementing a stateless DHCPv6 server as per RFC3736, I'd think the implem=
entation was complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.</sp=
an><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp; So the n=
ew options you want to serve can be served by the CE stateless DHCPv6 serve=
r.&nbsp; &nbsp;Now, if the service provider configures his/her DHCPv6 serve=
r
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.</=
span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I also cannot=
 find text in RFC3315 or its updates on how to handle received options that=
 were not requested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ If it is poss=
ible to send a DHCPv6 client &quot;ORO type&quot; options that it didn't re=
quest, then the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Are you aware=
 of any CE DHCPv6 WAN client/DHCPv6 LAN server implementations that are unk=
nown DHCPv6 option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ I think this =
level of DHCPv6 option transparency between CE LAN attached hosts and the u=
pstream SP's DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Regards,</spa=
n><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">/ Mark.</span><=
o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">&nbsp;</span><o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,&quot;sans-serif&quot;;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC&#8217;s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</body>
</html>

--_000_75B6FA9F576969419E42BECB86CB1B8916838A68xmbrcdx06ciscoc_--


From nobody Fri Apr  3 06:46:45 2015
Return-Path: <bs7652@att.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B191A92F8 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 06:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6juwnXlmc7z for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 06:46:33 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA9D1A90F9 for <ipv6@ietf.org>; Fri,  3 Apr 2015 06:46:32 -0700 (PDT)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id 8b99e155.2b81f9e22940.4294436.00-2444.11310507.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 03 Apr 2015 13:46:32 +0000 (UTC)
X-MXL-Hash: 551e99b8285758ca-b39532c23614e00fb4ade30cab597c11767773a2
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 6a99e155.0.4294263.00-2262.11310031.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 03 Apr 2015 13:46:15 +0000 (UTC)
X-MXL-Hash: 551e99a779c2154c-0a1c949b5eb6fe17de7b80f2528d11922ef3dd99
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t33DkET7013549; Fri, 3 Apr 2015 09:46:14 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t33Dk71c013473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 3 Apr 2015 09:46:07 -0400
Received: from GAALPA1MSGHUBAB.ITServices.sbc.com (GAALPA1MSGHUBAB.itservices.sbc.com [130.8.218.151]) by alpi131.aldc.att.com (RSA Interceptor); Fri, 3 Apr 2015 13:45:59 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.35]) by GAALPA1MSGHUBAB.ITServices.sbc.com ([130.8.218.151]) with mapi id 14.03.0224.002; Fri, 3 Apr 2015 09:45:59 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Bernie Volz (volz)" <volz@cisco.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQo49fpAu1QJUCtkvSmw9Np5Z0w81+AgAUtv4CAALj8AP//vltwgABXBoCAAL8pgIACs4eAgAB4uQCAAJRJAIAABomAgAAC0ICAAAFRAIAAC0oAgAACHoCAABLEgP//vXHw
Date: Fri, 3 Apr 2015 13:45:58 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F9B995@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <75B6FA9F576969419E42BECB86CB1B8916837EE3@xmb-rcd-x06.cisco.com> <1518852567.4941873.1428027546693.JavaMail.yahoo@mail.yahoo.com>, <75B6FA9F576969419E42BECB86CB1B8916838870@xmb-rcd-x06.cisco.com> <AD05F764-D89B-410C-B050-0AE260C26D97@cisco.com>, <75B6FA9F576969419E42BECB86CB1B891683896E@xmb-rcd-x06.cisco.com> <F07AD006-79CB-4E37-A2D4-2E1EAEBFD381@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com> <75B6FA9F576969419E42BECB86CB1B89168389D0@xmb-rcd-x06.cisco.com> <75B6FA9F576969419E42BECB86CB1B8916838A68@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B8916838A68@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.182.232]
Content-Type: multipart/alternative; boundary="_000_2D09D61DDFA73D4C884805CC7865E61130F9B995GAALPA1MSGUSRBF_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=DqThDhD+ c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=FVCBr1gxU_EA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqp]
X-AnalysisOut: [o32RAAAA:8 a=e9J7MTPGsLIA:10 a=48vgC7mUAAAA:8 a=AUd_NHdVAA]
X-AnalysisOut: [AA:8 a=LX9nTfyjAAAA:8 a=wnRk2I__AAAA:8 a=pCq9DBes1lRJgZkhU]
X-AnalysisOut: [ygA:9 a=CjuIK1q_8ugA:10 a=nCBVUKARg4_SK7iy:21 a=TkysJYlipa]
X-AnalysisOut: [JBeyri:21 a=L65ASTPstfCty979:21 a=yMhMjlubAAAA:8 a=SSmOFEA]
X-AnalysisOut: [CAAAA:8 a=7anj_rWaQwHTuPl19JYA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7]
X-AnalysisOut: [L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=FvvzkpABu]
X-AnalysisOut: [Xy4RkqO:21 a=h5E1Byqvs-_IMAcv:21 a=X_W6SCLsajKzmat4:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/OeNi47tf1N62UKbUZtmZU0N86Ec>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 13:46:43 -0000

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

Thx. You've saved me from having to right an email explaining why I'm oppos=
ed to changes to RFC 7084 resulting from this discussion thread.
Barbara

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (sheman=
t)
Sent: Friday, April 03, 2015 9:43 AM
To: Bernie Volz (volz); Fred Baker (fred)
Cc: Brian Haberman; ipv6@ietf.org; Ted Lemon; Ralph Droms (rdroms)
Subject: RE: RA Option Guidelines

Hmm, after more discussion, I am now corrected that a new document is not n=
eeded.  RFC 7084 does not block a new DHCPv6 option to be included in the O=
RO sent by the WAN.  Thus if the CE is configured to use a new DHCPv6 optio=
n, the CE will work fine.  The CE includes the new option in the ORO on the=
 WAN and serves the new option to the LAN via stateless DHCPv6 operation.

How the CE is configured for a new DHCPv6 option is out of scope for RFC708=
4.

Hemant

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (sheman=
t)
Sent: Friday, April 03, 2015 8:36 AM
To: Bernie Volz (volz); Fred Baker (fred)
Cc: Brian Haberman; ipv6@ietf.org<mailto:ipv6@ietf.org>; Ted Lemon; Ralph D=
roms (rdroms)
Subject: RE: RA Option Guidelines

Also, since RFC7084 was managed in v6ops, the minor DHC update to the CE ro=
uter to cater to Mark's request, I plan to submit a short note to v6ops.

Hemant

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Hemant Singh (sheman=
t)
Sent: Friday, April 03, 2015 8:28 AM
To: Bernie Volz (volz)
Cc: ipv6@ietf.org<mailto:ipv6@ietf.org>; Brian Haberman; Ralph Droms (rdrom=
s); Ted Lemon
Subject: RE: RA Option Guidelines

Bernie,

Got it - thanks much!  So the CE router implementation has to change to be =
configurable to include a new DHCPv6 option in the ORO for the WAN interfac=
e.  Once the new option is returned by the server, the CE uses the new opti=
on for stateless DHCPv6 services on the LAN.  Note, it is the same service =
provider who has configured the CE for the new DHCPv6 option and thus the s=
ame service provider also provisions the DHCPv6 server to return the new op=
tion, if asked for.  There is no need for DHCPv6 relay in the CE for this n=
ew option support.

In summary, both Mark's and Barbara's goals are met.

Thanks,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:48 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).

#2 is normal DHCP operation.

Note that while I think you were discussing stateless, it is true for state=
ful and stateless dhcp.

- Bernie (from iPad)

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Bernie,

Appreciate the quick reply.  Let me summarize the issues and then you can c=
larify.


1.      The CE WAN interface does not include a new option in DHCPV6_NEW_OP=
TION1 in the ORO option of the SOLICIT to the server.  If the server is con=
figured to return the DHCPV6_NEW_OPTION1 to clients, then will the server r=
eply with DHCPV6_NEW_OPTION1 even when the client did not request the optio=
n in the ORO?   In this scenario, no code changes on the CE, and just the s=
erver configuration takes care of the issue.

2.      The CE WAN interface does include a new option in DHCPV6_NEW_OPTION=
1 in the ORO option of the SOLICIT to the server.  If the server is configu=
red to return DHCPV6_NEW_OPTION1 to clients, then will the server reply wit=
h DHCPV6_NEW_OPTION1?

Mark,

Note Bernie agrees with how I and Wes Beebee (who I discussed this thread w=
ith) also interpreted RFC3736.  New options can be served by the stateless =
DHCPv6 server without revising RFC3736.

Thanks all,

Hemant

From: Bernie Volz (volz)
Sent: Friday, April 03, 2015 7:33 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailto:=
ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines

I didn't study the complete thread but I am sure everyone would understand =
that new options should be allowed to be requested. The ORO list cannot be =
frozen ... At the time the rfc was written, that was the list. But new opti=
on documents are not required to update RFC3736.

There are no interop issues either as if either side (client or server) doe=
sn't know of an option, it just doesn't include or ignores it.

- Bernie (from iPad)

On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<mailt=
o:shemant@cisco.com>> wrote:
Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this t=
hread for stateless DHCPv6 current vs. future options and the ORO option.

Thanks,

Hemant

From: Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Thursday, April 02, 2015 10:19 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________
From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Friday, 3 April 2015, 6:07
Subject: RE: RA Option Guidelines



Mark,

The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.   Read the first paragraph of section 5.3 in RFC37=
36.

/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:

/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server

/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the client. It being a minimum is subtly elude=
d to in a few sentences in the Abstract and the Introduction, however I thi=
nk they could easily be missed. I'd expect that if this is the case, it is =
much clearer and obvious.
/ - I think text you refer to in 5.3, "Clients and servers use the followin=
g options to pass configuration information to clients; note that other opt=
ions for configuration information may be specified in future Internet Stan=
dards:" reads to me like a later version of this RFC will specify more stat=
eless DHCPv6 server supported options. A statement such as "Other additiona=
l DHCPv6 options appropriate for stateless DHCPv6 operation may be supporte=
d by an implementation." would make it much clearer that the supported opti=
ons were up to the implementer once the minimum had been implemented.

/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd t=
hink the implementation was complete when I had implemented the options spe=
cified. I wouldn't put any effort into making it also transparent to any op=
tions that weren't identified in RFC3736, as there is no text discussing th=
at.

  So the new options you want to serve can be served by the CE stateless DH=
CPv6 server.   Now, if the service provider configures his/her DHCPv6 serve=
r to return new options to the CE WAN interface address acquisition, the CE=
 uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs =
support your use case and no dhcpv6 relay is required in the CE.

/ I also cannot find text in RFC3315 or its updates on how to handle receiv=
ed options that were not requested by the client in the Option Request Opti=
on. So if the CE WAN DHCPv6 client doesn't request an option in its ORO to =
the SP's DHCPv6 server, I don't think it is possible for the CE to pass opt=
ions it doesn't know about onto the downstream LAN devices that do understa=
nd those DHCPv6 options.

/ If it is possible to send a DHCPv6 client "ORO type" options that it didn=
't request, then the behaviour is still ambiguous. If the DHCPv6 client is =
a host, then it would be quite reasonable and expected to silently ignore t=
hose received unknown options. However, if the DHCPv6 client is on the WAN =
side of a CE device, then those options should instead be passed to the LAN=
 DHCPv6 server, which presumably should know how to correctly handle option=
s it doesn't understand - in the specific CE case, remember those options i=
n case a downstream LAN DHCPv6 client requests them. I think RFC7084 and it=
's ancestor RFC6204 are the only RFCs which describe this combination of DH=
CPv6 client/server working together, and neither of them have discussed pas=
sing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.

/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementatio=
ns that are unknown DHCPv6 option transparent? Looking at RFC7084, this beh=
aviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6 s=
erver support to only those options described in RFC7084, or to those descr=
ibed in RFC3736.

/ I think this level of DHCPv6 option transparency between CE LAN attached =
hosts and the upstream SP's DHCPv6 server(s) can only be achieved by using =
a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 op=
tion transparent. (A CE would still have a DHCPv6 client on its WAN interfa=
ce for its own parameters and DHCPv6-PD prefixes).

/ Regards,
/ Mark.


Barbara,

For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.  Thus in this deployment no extra op=
tions exist to serve to the CE router LAN.

Both use cases can be supported using existing RFC's.

Hemant



From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]
Sent: Tuesday, March 31, 2015 9:52 PM
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.org=
<mailto:ipv6@ietf.org>
Subject: Re: RA Option Guidelines

Hi Hemant,


________________________________

From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>
To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZZ Sm=
ith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Brian Ha=
berman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6@i=
etf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Sent: Wednesday, 1 April 2015, 1:27
Subject: RE: RA Option Guidelines

Barbara,

Thanks for replying.

Mark,

If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CPE =
includes the new option to its LAN DHCPv6 clients.

/  So here is a scenario.

/ As an ISP, my customers have VoIP handsets that might support the OPTION_=
GEOLOCATION DHCPv6 option (I might know that a portion of them do, because =
they've bought those VoIP handsets from me). How long is it going to take f=
or me to get that option added to an updated RFC3736 and RFC7084, to get my=
 CPE vendor to update and release their firmware to support that option, an=
d test that new CPE firmware and then to deploy that new firmware?

/ I think I'd be lucky if it only took 2 years.

/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE t=
o my customers if their hosts request it. So now I have to try to get OPTIO=
N_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor to =
update and release their firmware to support that option, and test that new=
 CPE firmware and then to deploy that new firmware.

/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so i=
t is still "only" 2 years to get to a point where I could provide those opt=
ions to my customers. But what if that draft has progressed too far though =
the IETF publishing process? I have to create a new draft updating the to b=
e published draft.

/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing and firmware deployment. Sounds like h=
ow hard I understand it was to roll out features like CLI in PSTN networks =
...

 What is one option you'd like the host on the LAN to include so that we ca=
n understand your use case better?

/ I'm going to make the problem much harder for you. I want the CPE to "sup=
port" or better, be transparent to, all current and future DHCPv6 options, =
and I don't want to have to upgrade or ask my customers to successfully upg=
rade their CPE each and every time
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.

The SIP server is already included as one option supported by RFC3736.  Cer=
tainly, if the SIP server support is needed in the RA, I am open for it sin=
ce the RA already includes DNS information.

/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New firmware upgrade each time you want to supp=
ort a new RA option.

/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS options yet. It might be simple to come up =
with a simple rule for more DHCPv6 options are duplicated into RAs, however=
 their might be some specific cases where the RA option value should be pre=
ferred over the DHCPv6 equivalent option and vice-versa.

However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?  At the time of writ=
ing RFC 6204 or RFC 7084, there is no such provision between the RA receive=
d on the WAN and the RA issued on the LAN of the CE router.

/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested a hybrid mode of operation for a DHCPv6 ser=
ver in that draft which I think solves that problem.

Others,

Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV fo=
rmat and an option Type.  I don't see anything else needed if I need to spe=
cify a new RA option.

Thanks,

Hemant

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com]
Sent: Tuesday, March 31, 2015 9:25 AM
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org<m=
ailto:ipv6@ietf.org>
Subject: RE: RA Option Guidelines




RFC 7084 already says:
  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
          options (as listed in Section 5.3 of [RFC3736]) received from
          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
          server.

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

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/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:Helvetica;
	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;}
@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;}
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:"Times New Roman",serif;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle26
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:1463378006;
	mso-list-type:hybrid;
	mso-list-template-ids:809150956 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Thx. You&#8217;ve saved me from havin=
g to right an email explaining why I&#8217;m opposed to changes to RFC 7084=
 resulting from this discussion thread.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Barbara<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><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=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> ipv6 [mailto:ipv6-bounces@ietf=
.org]
<b>On Behalf Of </b>Hemant Singh (shemant)<br>
<b>Sent:</b> Friday, April 03, 2015 9:43 AM<br>
<b>To:</b> Bernie Volz (volz); Fred Baker (fred)<br>
<b>Cc:</b> Brian Haberman; ipv6@ietf.org; Ted Lemon; Ralph Droms (rdroms)<b=
r>
<b>Subject:</b> RE: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Hmm, after more discussion, I am now =
corrected that a new document is not needed.&nbsp; RFC 7084 does not block =
a new DHCPv6 option to be included in the ORO sent
 by the WAN.&nbsp; Thus if the CE is configured to use a new DHCPv6 option,=
 the CE will work fine.&nbsp; The CE includes the new option in the ORO on =
the WAN and serves the new option to the LAN via stateless DHCPv6 operation=
.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">How the CE is configured for a new DH=
CPv6 option is out of scope for RFC7084.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Hemant<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,sans-serif">From:</span></b><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,sans-serif"> ipv6 [<a href=3D"mailto:ipv6-bou=
nces@ietf.org">mailto:ipv6-bounces@ietf.org</a>]
<b>On Behalf Of </b>Hemant Singh (shemant)<br>
<b>Sent:</b> Friday, April 03, 2015 8:36 AM<br>
<b>To:</b> Bernie Volz (volz); Fred Baker (fred)<br>
<b>Cc:</b> Brian Haberman; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</=
a>; Ted Lemon; Ralph Droms (rdroms)<br>
<b>Subject:</b> RE: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Also, since RFC7084 was managed in v6=
ops, the minor DHC update to the CE router to cater to Mark&#8217;s request=
, I plan to submit a short note to v6ops.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Hemant<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,sans-serif">From:</span></b><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,sans-serif"> ipv6 [<a href=3D"mailto:ipv6-bou=
nces@ietf.org">mailto:ipv6-bounces@ietf.org</a>]
<b>On Behalf Of </b>Hemant Singh (shemant)<br>
<b>Sent:</b> Friday, April 03, 2015 8:28 AM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>; Brian Haberm=
an; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> RE: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Bernie,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Got it &#8211; thanks much!&nbsp; So =
the CE router implementation has to change to be configurable to include a =
new DHCPv6 option in the ORO for the WAN interface.&nbsp; Once
 the new option is returned by the server, the CE uses the new option for s=
tateless DHCPv6 services on the LAN.&nbsp; Note, it is the same service pro=
vider who has configured the CE for the new DHCPv6 option and thus the same=
 service provider also provisions the
 DHCPv6 server to return the new option, if asked for.&nbsp; There is no ne=
ed for DHCPv6 relay in the CE for this new option support.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">In summary, both Mark&#8217;s and Bar=
bara&#8217;s goals are met.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Hemant<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,sans-serif">From:</span></b><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,sans-serif"> Bernie Volz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:48 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">All options MUST be in ORO for server to return (the=
re are some &quot;protocol&quot; options, such as client-id and server-id t=
hat are NOT supposed to be in ORO). So client controls the options it gets.=
 So #1 is not true (some servers, such as CPNR,
 can be configured to return options the client did not request, but genera=
lly that is useless since the client will most likely ignore it).<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">#2 is normal DHCP operation.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Note that while I think you were discussing stateles=
s, it is true for stateful and stateless dhcp.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Bernie,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Appreciate the quick reply.&nbsp; Let=
 me summarize the issues and then you can clarify.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,sans-serif;color:#1F497D">The CE WAN interface does not includ=
e a new option in DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to th=
e server.&nbsp; If the server is configured to return
 the DHCPV6_NEW_OPTION1 to clients, then will the server reply with DHCPV6_=
NEW_OPTION1 even when the client did not request the option in the ORO?&nbs=
p; &nbsp;In this scenario, no code changes on the CE, and just the server c=
onfiguration takes care of the issue.</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,sans-serif;color:#1F497D">The CE WAN interface does include a =
new option in DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the se=
rver.&nbsp; If the server is configured to return
 DHCPV6_NEW_OPTION1 to clients, then will the server reply with DHCPV6_NEW_=
OPTION1?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Mark,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Note Bernie agrees with how I and Wes=
 Beebee (who I discussed this thread with) also interpreted RFC3736.&nbsp; =
New options can be served by the stateless DHCPv6 server
 without revising RFC3736.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Thanks all,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Hemant</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,sans-serif">From:</span></b><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,sans-serif"> Bernie Volz (volz)
<br>
<b>Sent:</b> Friday, April 03, 2015 7:33 AM<br>
<b>To:</b> Hemant Singh (shemant)<br>
<b>Cc:</b> Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a href=3D"mai=
lto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">I didn't study the complete thread but I am sure eve=
ryone would understand that new options should be allowed to be requested. =
The ORO list cannot be frozen ... At the time the rfc was written, that was=
 the list. But new option documents
 are not required to update RFC3736.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are no interop issues either as if either side=
 (client or server) doesn't know of an option, it just doesn't include or i=
gnores it.<br>
<br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</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:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Could the DHCPv6 gurus in Ralph, Bern=
ie, and Ted please help resolve this thread for stateless DHCPv6 current vs=
. future options and the ORO option.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Thanks,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Hemant</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,sans-serif">From:</span></b><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,sans-serif"> Mark ZZZ Smith [<a href=3D"mailt=
o:markzzzsmith@yahoo.com.au">mailto:markzzzsmith@yahoo.com.au</a>]
<br>
<b>Sent:</b> Thursday, April 02, 2015 10:19 PM<br>
<b>To:</b> Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a hre=
f=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
<b>Subject:</b> Re: RA Option Guidelines</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;background:white"><spa=
n style=3D"font-family:&quot;Helvetica&quot;,sans-serif;color:black">Hi Hem=
ant,<br>
<br>
<br>
________________________________<br>
From: Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">shema=
nt@cisco.com</a>&gt;<br>
To: Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo.com.au">markzzz=
smith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mai=
lto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Friday, 3 April 2015, 6:07<br>
Subject: RE: RA Option Guidelines<br>
<br>
<br>
<br>
Mark,<br>
&nbsp;<br>
The stateless DHCPv6 server in RFC3736 allows for new options to be served =
by the stateless server.&nbsp;&nbsp; Read the first paragraph of section 5.=
3 in RFC3736.<br>
<br>
/ So there are a few reasons why I wouldn't come to that conclusion without=
 some very careful reading:<br>
<br>
/ - The explicitly identified set of required and optional DHCPv6 options t=
hat can be supported by a stateless DHCPv6 server<br>
<br>
/ - The lack of any overt discussion that this set of required and optional=
 DHCPv6 options are a minimum, and that further DHCPv6 options could be pro=
vided by a stateless DHCPv6 server if supported by the implementation, are =
appropriate and requested by the
 client. It being a minimum is subtly eluded to in a few sentences in the A=
bstract and the Introduction, however I think they could easily be missed. =
I'd expect that if this is the case, it is much clearer and obvious.</span>=
<o:p></o:p></p>
<div id=3D"yui_3_16_0_1_1428018555944_61004">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ - I think text you refer =
to in 5.3, &quot;Clients and servers use the following options to pass conf=
iguration&nbsp;information to clients; note that other options
 for configuration&nbsp;information may be specified in future Internet Sta=
ndards:&quot; reads to me like a later version of this RFC will specify mor=
e stateless DHCPv6 server supported options. A statement such as&nbsp;&quot=
;Other additional DHCPv6 options appropriate for stateless
 DHCPv6 operation may be supported by an implementation.&quot; would make i=
t much clearer that the supported options were up to the implementer once t=
he minimum had been implemented.</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ So if I were implementing=
 a stateless DHCPv6 server as per RFC3736, I'd think the implementation was=
 complete when I had implemented the options specified.
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.</sp=
an><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60546">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp; So the new options y=
ou want to serve can be served by the CE stateless DHCPv6 server.&nbsp; &nb=
sp;Now, if the service provider configures his/her DHCPv6 server
 to return new options to the CE WAN interface address acquisition, the CE =
uses the options on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Exist=
ing RFCs support your use case and no dhcpv6 relay is required in the CE.</=
span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60638">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ I also cannot find text i=
n RFC3315 or its updates on how to handle received options that were not re=
quested by the client in the Option Request Option.
 So if the CE WAN DHCPv6 client doesn't request an option in its ORO to the=
 SP's DHCPv6 server, I don't think it is possible for the CE to pass option=
s it doesn't know about onto the downstream LAN devices that do understand =
those DHCPv6 options.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ If it is possible to send=
 a DHCPv6 client &quot;ORO type&quot; options that it didn't request, then =
the behaviour is still ambiguous. If the DHCPv6 client is
 a host, then it would be quite reasonable and expected to silently ignore =
those received unknown options. However, if the DHCPv6 client is on the WAN=
 side of a CE device, then those options should instead be passed to the LA=
N DHCPv6 server, which presumably
 should know how to correctly handle options it doesn't understand - in the=
 specific CE case, remember those options in case a downstream LAN DHCPv6 c=
lient requests them. I think RFC7084 and it's ancestor RFC6204 are the only=
 RFCs which describe this combination
 of DHCPv6 client/server working together, and neither of them have discuss=
ed passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN ser=
ver.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ Are you aware of any CE D=
HCPv6 WAN client/DHCPv6 LAN server implementations that are unknown DHCPv6 =
option transparent? Looking at RFC7084, this behaviour
 seems to be very explicitly prohibited, by limiting the LAN DHCPv6 server =
support to only those options described in RFC7084, or to those described i=
n RFC3736.</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ I think this level of DHC=
Pv6 option transparency between CE LAN attached hosts and the upstream SP's=
 DHCPv6 server(s) can only be achieved by using
 a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 o=
ption transparent. (A CE would still have a DHCPv6 client on its WAN interf=
ace for its own parameters and DHCPv6-PD prefixes).</span><o:p></o:p></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ Regards,</span><o:p></o:p=
></p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">/ Mark.</span><o:p></o:p></=
p>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60642">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<div id=3D"yui_3_16_0_1_1428018555944_60751">
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">&nbsp;</span><o:p></o:p></p=
>
</div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil=
y:&quot;Helvetica&quot;,sans-serif;color:black">Barbara,<br>
&nbsp;<br>
For your use case, the service provider configures the DHCPv6 server to onl=
y serve options specified in RFC 7084.&nbsp; Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.<br>
&nbsp; <br>
Both use cases can be supported using existing RFC&#8217;s.<br>
&nbsp;<br>
Hemant<br>
&nbsp;<br>
<br>
<br>
From:Mark ZZZ Smith [<a href=3D"mailto:markzzzsmith@yahoo.com.au">mailto:ma=
rkzzzsmith@yahoo.com.au</a>]
<br>
Sent: Tuesday, March 31, 2015 9:52 PM<br>
To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; <a href=3D"ma=
ilto:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: Re: RA Option Guidelines<br>
&nbsp;<br>
Hi Hemant,<br>
&nbsp;<br>
<br>
________________________________<br>
<br>
From:Hemant Singh (shemant) &lt;<a href=3D"mailto:shemant@cisco.com">sheman=
t@cisco.com</a>&gt;<br>
To: &quot;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com">bs76=
52@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsmith@yahoo=
.com.au">markzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a href=3D"m=
ailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br>
Sent: Wednesday, 1 April 2015, 1:27<br>
Subject: RE: RA Option Guidelines<br>
<br>
Barbara,<br>
<br>
Thanks for replying.&nbsp; &nbsp; <br>
<br>
Mark,<br>
<br>
If new DHCPv6 options are added to be supported by RFC3736, then the SP inc=
ludes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; Then the=
 CPE includes the new option to its LAN DHCPv6 clients.<br>
&nbsp;<br>
/ &nbsp;So here is a scenario.<br>
&nbsp;<br>
/ As an ISP, my customers have VoIP handsets that might support the&nbsp;OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added to
 an updated RFC3736 and RFC7084, to get my CPE vendor to update and release=
 their firmware to support that option, and test that new CPE firmware and =
then to deploy that new firmware?<br>
&nbsp;<br>
/ I think I'd be lucky if it only took 2 years.<br>
&nbsp;<br>
/ A few months later I decide I want to provide&nbsp;OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated&nbsp;RFC3736, to get my CPE =
vendor to update and release their firmware
 to support that option, and test that new CPE firmware and then to deploy =
that new firmware.<br>
&nbsp;<br>
/ Now if I'm lucky I could add it to the draft for&nbsp;OPTION_GEOLOCATION,=
 so it is still &quot;only&quot; 2 years to get to a point where I could pr=
ovide those options to my customers. But what if that draft has progressed =
too far though the IETF publishing process? I have
 to create a new draft updating the to be published draft.<br>
&nbsp;<br>
/ So, to achieve what should be a simple task of providing location or time=
zone information to customers' end hosts if they want it, we've just incurr=
ed the massive costs and time delays of the IETF publishing process, vendor=
 firmware upgrades, firmware testing
 and firmware deployment. Sounds like how hard I understand it was to roll =
out features like CLI in PSTN networks ...<br>
&nbsp;<br>
&nbsp;What is one option you'd like the host on the LAN to include so that =
we can understand your use case better? &nbsp;<br>
<br>
/ I'm going to make the problem much harder for you. I want the CPE to &quo=
t;support&quot; or better, be transparent to, all current and future DHCPv6=
 options, and I don't want to have to upgrade or ask my customers to succes=
sfully upgrade their CPE each and every time<br>
there is a new DHCPv6 option defined that might be useful to me and them. I=
 want to be able to provide service parameters to my customers hosts, direc=
tly or indirectly, without the software revision or model of their CPE bein=
g the constraint.<br>
<br>
The SIP server is already included as one option supported by RFC3736.&nbsp=
; Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.<br>
&nbsp;<br>
/ I don't think DNS in RAs was a good idea, and neither were SIP options wh=
en they were proposed. See that time consuming and service disrupting firmw=
are upgrade cycle for new DHCPv6 options? Same problem if you use RA option=
s to achieve the same goal. New
 firmware upgrade each time you want to support a new RA option.<br>
&nbsp;<br>
/ Duplication between RA options and DHCPv6 options also causes more proble=
ms. Which is preferred? Are they treated equally or does one take precedenc=
e over the other? As far as I'm aware, these questions haven't been answere=
d for the DHCPv6 DNS and RA DNS
 options yet. It might be simple to come up with a simple rule for more DHC=
Pv6 options are duplicated into RAs, however their might be some specific c=
ases where the RA option value should be preferred over the DHCPv6 equivale=
nt option and vice-versa.&nbsp;<br>
&nbsp;<br>
However, I still ask the question as to how an RA received at the WAN of th=
e CPE has its options propagated to the RA on the LAN?&nbsp; At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued on
 the LAN of the CE router.<br>
&nbsp;<br>
/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 opt=
ions that are unknown by the CPE will pass right through it transparently. =
The only complication is when stateful DHCPv6 addressing is used on the CPE=
 LAN interface, and I suggested
 a hybrid mode of operation for a DHCPv6 server in that draft which I think=
 solves that problem.<br>
<br>
Others,<br>
<br>
Also, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a T=
LV format and an option Type.&nbsp; I don't see anything else needed if I n=
eed to specify a new RA option.
<br>
<br>
Thanks,<br>
<br>
Hemant<br>
<br>
-----Original Message-----<br>
From: STARK, BARBARA H [<a href=3D"mailto:bs7652@att.com">mailto:bs7652@att=
.com</a>]
<br>
Sent: Tuesday, March 31, 2015 9:25 AM<br>
To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a href=3D"mail=
to:ipv6@ietf.org">
ipv6@ietf.org</a><br>
Subject: RE: RA Option Guidelines<br>
&nbsp;<br>
<br>
<br>
<br>
RFC 7084 already says: <br>
&nbsp; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset of DHC=
Pv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 of [RF=
C3736]) received from<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interface t=
o its LAN-side DHCPv6<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; server.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--_000_2D09D61DDFA73D4C884805CC7865E61130F9B995GAALPA1MSGUSRBF_--


From nobody Fri Apr  3 12:16:30 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1741B2A2C for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 12:16: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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id os9UNXPfasfQ for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 12:16:26 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::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 6E7671AD34D for <ipv6@ietf.org>; Fri,  3 Apr 2015 12:16:26 -0700 (PDT)
Received: by pdbni2 with SMTP id ni2so130027563pdb.1 for <ipv6@ietf.org>; Fri, 03 Apr 2015 12:16:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XoBLSVh/siIyx3QQThVHfqsWBL4B1snIZWFUEyjhi0c=; b=OXCgFtKvaTaZN+t05w+1pvDCGyq1he6a4fLTplb0T8h4dhKKxX7S7x98ydnxSABxhx 4ZLe/gjsDojdopG13TgJc3FZX5SsP4IEVMhx0EAzgaWgGR2sZJygRv/av5sL5H/pOSIS gy8bLRfEDSJIS6QLzAIncViGjjove2Rmm72HBwr3FB8o6/gD7FlzTin8TKngXXoZ7C28 TgWRMPhY5Xqcbs4GtbWzJS0nqFE/9qVmSaAUH9uvXbq71/DqTMJLijON+lVm7uKBri+z ETiNuQcM+4g9GDYkN6ikROtEMkSF1+APGRP9pyJzVclOp6J+oyw4DddqgnrTR/jZjtIv ++xQ==
X-Received: by 10.66.119.136 with SMTP id ku8mr6751518pab.29.1428088586196; Fri, 03 Apr 2015 12:16:26 -0700 (PDT)
Received: from ?IPv6:2406:e007:61ce:1:28cc:dc4c:9703:6781? ([2406:e007:61ce:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id sb4sm8809088pbb.5.2015.04.03.12.16.22 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Apr 2015 12:16:24 -0700 (PDT)
Message-ID: <551EE710.2050301@gmail.com>
Date: Sat, 04 Apr 2015 08:16:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>,  "STARK, BARBARA H" <bs7652@att.com>, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>,  Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: RA Option Guidelines
References: <5515A9A7.3080508@innovationslab.net> <281018849.2116525.1427767749309.JavaMail.yahoo@mail.yahoo.com> <75B6FA9F576969419E42BECB86CB1B8916834620@xmb-rcd-x06.cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F8C7AF@GAALPA1MSGUSRBF.ITServices.sbc.com> <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <551AF4E5.7000207@gmail.com>
In-Reply-To: <551AF4E5.7000207@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1Kat-gL8HLx3aSUZutuY-98JSbA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 19:16:28 -0000

I'm glad y'all have got DHCPv6 sorted out. Now, as to the original
subject of this thread:
On 01/04/2015 08:26, Brian E Carpenter wrote:
> On 01/04/2015 03:27, Hemant Singh (shemant) wrote:
> ...
>> Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV format and an option Type.   I don't see anything else needed if I need to specify a new RA option. 
> 
> Section 9 "Extensibility - Option Processing" gives some general advice, too.
> 
> The question is what do we collectively want. I liked Mark's restrictive
> criterion "RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only)". DHCPv6 is available as the kitchen sink
> protocol for other stuff. I'm not sure whether we want to write this down;
> it seems as if  one or two sentences should be added to RFC4861bis if
> there ever is such a document.

Do we actually agree on this, or rather on a slightly expanded version:

RA options should be limited to link-local/subnet specific parameters
(i.e., layer 3 parameters only) necessary for a simple unmanaged network.
The only exception is RFC 6106 (DNS Configuration). More complex situations
are better handled by other configuration metods such as DHCPv6.

   Brian


From nobody Fri Apr  3 13:18:31 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 495841A006F for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 13:18:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQz9StDN8ruN for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 13:18:29 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29001A0058 for <ipv6@ietf.org>; Fri,  3 Apr 2015 13:18:29 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 0AF0361B1; Fri,  3 Apr 2015 13:18:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=o2VokVSGoEHLLbOa2kKeAScyBvY=; b= XRaEPmGT9T5/A7apCYl8fBv7C8gJ3Ib0XXGw1Wp+qLk8tHAMCPMWqhVk59ldR9r2 uc3yBChVJu9ZelqM1ntJFD9kEFm8WoY0tqzMgR2I0TSgLF/zkyY5saEamWVB7jz4 GP/IlQxuRrVYURcwsTnyX7mmW0y3cB7ZlVy+FKo6FLA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=E/UnFS6f5nb/O8wKO+Sx602Xyq /Xcr5LNkaSEDteCGy9HisnXrfPXUFQurkY5euQrSPbhMuXPNZJtAKfb6SXGei2E0 g8P9BtFsFYpvh7Bh4+cOYbmf4nl+a2jyEH/cYJyiEHJhav1teVQiHEJVNlMpFPaf r3ZyAprYKRfp6/wRk=
Received: from gomlefisk.localdomain (46.66.185.247.tmi.telenormobil.no [46.66.185.247]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 63B0A61AD; Fri,  3 Apr 2015 13:18:27 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 9F0DB41F01CF; Fri,  3 Apr 2015 22:18:22 +0200 (CEST)
Subject: Re: RA Option Guidelines
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2097\))
Content-Type: multipart/signed; boundary="Apple-Mail=_CE1307A6-F7D6-4FF4-B2EB-FAF82F3A8200"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <551EE710.2050301@gmail.com>
Date: Fri, 3 Apr 2015 22:18:21 +0200
Message-Id: <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
References: <5515A9A7.3080508@innovationslab.net> <281018849.2116525.1427767749309.JavaMail.yahoo@mail.yahoo.com> <75B6FA9F576969419E42BECB86CB1B8916834620@xmb-rcd-x06.cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F8C7AF@GAALPA1MSGUSRBF.ITServices.sbc.com> <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <551AF4E5.7000207@gmail.com> <551EE710.2050301@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2097)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gCv3emYUTP7pMlzHQSWvnJzyXiA>
Cc: 6man WG <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 20:18:31 -0000

--Apple-Mail=_CE1307A6-F7D6-4FF4-B2EB-FAF82F3A8200
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>=20
> Do we actually agree on this, or rather on a slightly expanded =
version:
>=20
> RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only) necessary for a simple unmanaged =
network.
> The only exception is RFC 6106 (DNS Configuration). More complex =
situations
> are better handled by other configuration metods such as DHCPv6.

I agree only with this part:
=E2=80=9CRA options should be limited to link-local/subnet specific =
parameters (i.e. layer 3 parameters only). The only exception is RFC6106 =
(DNS Configuration).=E2=80=9D

RA=E2=80=99s aren=E2=80=99t unmanaged. they certainly don=E2=80=99t =
require the network to be simple.
there was a thread on the DHC list a while back appearing to reach the =
conclusion that DHCP should only be used to configure the network layer =
(although there are many exceptions).
the main difference between RA and DHCP is that one is per subnet, the =
other per host.

cheers,
Ole



--Apple-Mail=_CE1307A6-F7D6-4FF4-B2EB-FAF82F3A8200
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

iQEcBAEBCgAGBQJVHvWOAAoJEFuJXizso86gn6QH/2HWKcrdJHeky2FgpXqxbR8g
CWQRbfmNJpQ8zLKdyPyRmPBIY6wnTJkRQiK+J4Pp7f5noL/32abQYBb85ZZklQtv
VDtgoflHXOfjL5YM3qJ86Ks72vaWa7ZjJPVoHViRkniqMMTqPPvxvFJ75FNt+Q9T
Y4CViKUHi4l+sjrdwpPiYhIbHxsNaCrWo0AF3mjBv834u8bwX4Misscps2ORXW2J
QpqhDdHaiLXxB4/AatiiKOYVE7u1jqjEdsV3FW11GXTGKABkuEksOJ/lT1YA6qcy
DzFg9F4m/LuO0OzpGXNg5bJXCUH6tdr9+cQRy5RxLa8P1rUtFEkCgSMg3klVgX8=
=U7nA
-----END PGP SIGNATURE-----

--Apple-Mail=_CE1307A6-F7D6-4FF4-B2EB-FAF82F3A8200--


From nobody Fri Apr  3 13:54:43 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 674371A0B00 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 13:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PROwdWHs37_U for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 13:54:39 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD42A1A19EF for <ipv6@ietf.org>; Fri,  3 Apr 2015 13:54:37 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 89B5D6146; Fri,  3 Apr 2015 13:54:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=CeuaqHFnjgDuBt1vYsrl+Np+ulA=; b= q8MSWoJSi/t8dW/898mNDUBfAAvUYAD7tpCRuBLzigZeSTBkG1kleSnL4pmPVlSn P0gynFR/FFnclCU4fEyaw3lY53Y0opTxIgO9jVAULE88o6STGwxmN34SAFPmzXPm MpqkM2HqBT0b72UvEfi9nRYAm91duPq7jcdHLX22DV8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=qtYPJ7ps1+ZWanDA3cBTC3nl1o kRpG6H1E44M5CMndy0kceS496f05PVL0l9R8QaXMig6akAsF64HnqT1WrAS/53KD axjQLHW7qbzfu+PK5RibPvfo5z3v2059Kgd6+U1DFREQqyo9CxBn81GuYToul1yQ ZBCapRPMI3eq2p9wQ=
Received: from gomlefisk.localdomain (46.66.185.247.tmi.telenormobil.no [46.66.185.247]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 1E02D6141; Fri,  3 Apr 2015 13:54:36 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 7633441F12FA; Fri,  3 Apr 2015 22:54:33 +0200 (CEST)
Subject: Re: IPv6 as a Standard? 
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2097\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F0A83BEE-03CD-4E0C-A9D3-057EA2BAE113"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <201503302354.t2UNsMwV067446@givry.fdupont.fr>
Date: Fri, 3 Apr 2015 22:54:33 +0200
Message-Id: <4FFB4718-271C-4E8A-BA15-E6E38C88485A@employees.org>
References: <201503302354.t2UNsMwV067446@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.2097)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/znRpBc3J9RE7AQ9kGkS0_P9Mp3E>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 20:54:41 -0000

--Apple-Mail=_F0A83BEE-03CD-4E0C-A9D3-057EA2BAE113
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>>> IPv6 is 20 year old (cf my next message) so it is time to launch the
>>> process to make it a (full) Standard!
>>=20
>> Age is not the question - does it meet the criteria in RFC 6410?
>> I think the answer is yes, but the questions about errata and unused
>> features have to be answered.
>>=20
>> And there is a practical problem caused by "Updated by RFC5095, =
RFC5722,
>> RFC5871, RFC6437, RFC6564, RFC6935, RFC6946, RFC7045, RFC7112". =
There's
>> no way 2460 can be promoted as-is.
>=20
> =3D> I believe the answer is in your second sentence, i.e., errata and
> unused features are in the updating RFCs. So:
> (1) 2 implementations: no issue
> (2) errata: to be done (*)
> (3) unused feature: to be done (*)
> (4) IPR: none
> So we have to produce a "consolidated" version of RFC 2460 merging =
most
> of the updating RFCs (what I marked with (*)). The token is in the =
hands
> of the WG chairs=E2=80=A6

Bob and I had a look at sub-set of the IPv6 core RFCs that are at draft =
standard during IETF week.
at least for 2460 the errata do not look to be an issue. nor are we =
aware of any unused features.

RFC6410 says nothing about =E2=80=9CUpdated by=E2=80=9D RFCs, and we =
have asked our AD to get a clarification from the IESG.
in case we are required to incorporate the "Updated by=E2=80=9D RFCs, as =
opposed to promote the document as-is, it might require a more thorough =
discussion. I did a first pass at incorporating the changes suggested in =
those RFCs, and it turns out that a couple of them are not just simple =
editorial changes. likewise we need to consider if it is wise to publish =
the IPv6 specification under a new RFC number.

Best regards,
Ole


--Apple-Mail=_F0A83BEE-03CD-4E0C-A9D3-057EA2BAE113
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

iQEcBAEBCgAGBQJVHv4JAAoJEFuJXizso86g5YgH/RYbT+pHc6R60G9YY23dzz7d
AIFh73e00z9eFhieGMLaHsCH8v9NXNuMysSrXqhhhh3vFzgLBdEVY1+LAi8d+OUV
H2rNrytZlNqYGXWuUZFc7h5UeIy7+MSZNQ9l6J/lM8MmqspeLhAmg//K7ji61Nwc
7Nzth7BZjpCTWxExN36xou/9tVnES+zdrgujWeBVQAwB92/3RszKz9nq8gyIellE
X/6LJ/L6XBAbMZni7yH6IyT+Pn6KJ0WCV2l9v18T5D5wjpiBvJ0L8JDUgfVZFC5Q
KyegmbrFikcwmgIRV2IzQ8giVxUCwjGoSPBrfcKjkQEdbUlkdL8K5bEE+IW4PwE=
=RzkJ
-----END PGP SIGNATURE-----

--Apple-Mail=_F0A83BEE-03CD-4E0C-A9D3-057EA2BAE113--


From nobody Fri Apr  3 14:03:54 2015
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 765DB1A1A2D for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 14:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xZCDHNK0heuI for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 14:03:52 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 645D91A19F2 for <ipv6@ietf.org>; Fri,  3 Apr 2015 14:03:52 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id t33L3ptj025661 for <ipv6@ietf.org>; Fri, 3 Apr 2015 14:03:52 -0700
Received: from XCH-BLV-312.nw.nos.boeing.com (xch-blv-312.nw.nos.boeing.com [137.136.239.125]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t33L3pBQ025658 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 3 Apr 2015 14:03:51 -0700
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.27]) by XCH-BLV-312.nw.nos.boeing.com ([169.254.12.131]) with mapi id 14.03.0210.002;  Fri, 3 Apr 2015 14:03:51 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQbkKxdA3s2P5rdU6O+b9Cj9A14Z08L3uA//+VXwA=
Date: Fri, 3 Apr 2015 21:03:50 +0000
Message-ID: <021E64FECA7E5A4699562F4E66716481534B9A9C@XCH-PHX-503.sw.nos.boeing.com>
References: <5515A9A7.3080508@innovationslab.net> <281018849.2116525.1427767749309.JavaMail.yahoo@mail.yahoo.com> <75B6FA9F576969419E42BECB86CB1B8916834620@xmb-rcd-x06.cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F8C7AF@GAALPA1MSGUSRBF.ITServices.sbc.com> <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <551AF4E5.7000207@gmail.com> <551EE710.2050301@gmail.com> <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
In-Reply-To: <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xulDYDNbNGNu2PSPszAhZ3SAfAQ>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 21:03:53 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgT2xlIFRyb2FuDQo+IFNlbnQ6IEZyaWRheSwg
QXByaWwgMDMsIDIwMTUgMTY6MTgNCj4gVG86IEJyaWFuIEUgQ2FycGVudGVyDQo+IENjOiA2bWFu
IFdHOyBCcmlhbiBIYWJlcm1hbg0KPiBTdWJqZWN0OiBSZTogUkEgT3B0aW9uIEd1aWRlbGluZXMN
Cj4gDQo+ID4NCj4gPiBEbyB3ZSBhY3R1YWxseSBhZ3JlZSBvbiB0aGlzLCBvciByYXRoZXIgb24g
YSBzbGlnaHRseSBleHBhbmRlZCB2ZXJzaW9uOg0KPiA+DQo+ID4gUkEgb3B0aW9ucyBzaG91bGQg
YmUgbGltaXRlZCB0byBsaW5rLWxvY2FsL3N1Ym5ldCBzcGVjaWZpYyBwYXJhbWV0ZXJzDQo+ID4g
KGkuZS4sIGxheWVyIDMgcGFyYW1ldGVycyBvbmx5KSBuZWNlc3NhcnkgZm9yIGEgc2ltcGxlIHVu
bWFuYWdlZCBuZXR3b3JrLg0KPiA+IFRoZSBvbmx5IGV4Y2VwdGlvbiBpcyBSRkMgNjEwNiAoRE5T
IENvbmZpZ3VyYXRpb24pLiBNb3JlIGNvbXBsZXggc2l0dWF0aW9ucw0KPiA+IGFyZSBiZXR0ZXIg
aGFuZGxlZCBieSBvdGhlciBjb25maWd1cmF0aW9uIG1ldG9kcyBzdWNoIGFzIERIQ1B2Ni4NCg0K
SSBhZ3JlZSB3aXRoIHRoaXMuDQoNCkFuZCBPbGUgcmVwbGllcywgYW1vbmcgb3RoZXIgdGhpbmdz
Og0KDQo+IHRoZSBtYWluIGRpZmZlcmVuY2UgYmV0d2VlbiBSQSBhbmQgREhDUCBpcyB0aGF0IG9u
ZSBpcyBwZXIgc3VibmV0LCB0aGUgb3RoZXINCj4gcGVyIGhvc3QuDQoNCldoaWNoIGlzIGFib3V0
IGFzIHN1Y2NpbmN0bHktcHV0IGFzIEkndmUgZXZlciBzZWVuLg0KDQpNYW5hZ2luZyBlYWNoIGhv
c3QgaW5kaXZpZHVhbGx5IGlzIGEgbW9yZSBjb21wbGV4IHByb2JsZW0gdGhhdCBtYW5hZ2luZyB0
aGUgbmV0d29yayB3aXRob3V0IGZvY3VzaW5nIG9uIGluZGl2aWR1YWwgaG9zdHMuIFBlcmhhcHMg
dGhlIG9ubHkgY2hhbmdlIHRvIEJyaWFuJ3MgcG9pbnQgaXMgdG8gZGVsZXRlIHRoZSB3b3JkICJz
aW1wbGUsIiB0aGVuLiBJJ2QgZ28gd2l0aCBPbGUncyB3ZWxsLWRpc3RpbGxlZCBzaW5nbGUgc2Vu
dGVuY2UuDQoNCkJlcnQNCg0K


From nobody Fri Apr  3 18:41:05 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D19A1A3BA3 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 18:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 ksTe5nyala-2 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 18:41:01 -0700 (PDT)
Received: from nm11-vm1.bullet.mail.bf1.yahoo.com (nm11-vm1.bullet.mail.bf1.yahoo.com [98.139.213.152]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531091A212A for <ipv6@ietf.org>; Fri,  3 Apr 2015 18:41:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428111660; bh=YomGfoYqB8rvUYQMCGkdlD9NzRAFvKLr/RhhJLXPggo=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=lZtGR+CBq7gPHcKD8WmJH1uPC9bSygGpWqI68F8/LWsOYVScW6vOmbEACg2Jb8Rc66MrMaKFVoHYpcGZ1/KRHY4eCG4fWjgrzROavE9QggR0rHqjZNCAAskPr9qp7OQkwRrho0ZHUs6LlmfcI4xkJUvTPrBSJ1kgOV/ssX5HSfXryvIbLUTdvVzfNGX2wX3kG/pMtVSVyZxWSUrZaCkxmGzXt4SOksVhWLoyLzz966nwsnJFaNcO8oOqoLPUNR0/lYPP0yI0UF9W63u9mGuBVd2MxvHXFcPZSDZSnCMWgv+faERz7xNGoejElaKtMEyNVKo/XGRkgVMbo46HaH+1Ng==
Received: from [66.196.81.174] by nm11.bullet.mail.bf1.yahoo.com with NNFMP; 04 Apr 2015 01:41:00 -0000
Received: from [98.139.212.204] by tm20.bullet.mail.bf1.yahoo.com with NNFMP;  04 Apr 2015 01:41:00 -0000
Received: from [127.0.0.1] by omp1013.mail.bf1.yahoo.com with NNFMP; 04 Apr 2015 01:41:00 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 407798.62094.bm@omp1013.mail.bf1.yahoo.com
X-YMail-OSG: BRtRUYAVM1k59Ldngk4mL2Z7UcBCxC.zE4GHT8w2W4BZwi1tEH7_W0RS86xV.9Y 6xQYnbpWcHB.pQZSnxVVrgrCfBv4wE6PYMrVKLrZ5CfB0LV1BaCMPinsu2OjuqPhGfD3q3hMY3da HEYSVqSWSXUDNZqgt6z.Ht.MMXo_AH1znBhInb7MpAf7WpxNUuz0ymbOn1qBcUxXn_NYG0WJNWAc WCI53m.MHfM8B6G3kznBZXg7GFOmlw1LsfP_nfldiv1hwsw0BTAMt1I9i.egWO1qiTQCa2j2qOeG F7XsDjg_rSoAH8wayffG3DtDTS2u70FnZDLNQosQ3V1A7KpZV2Lxh7PmaMMjjPxINCRN7FQ20Xi8 ldiBRqELpnlCgMJ4GaGqA4p0BjjEHEdJjRz9HtOUvqzNvpD0na2s0QFB_p03wkTb7yKQD7FsB2za I7s7RgZspY0sFo2CeyN6jeUq4qAzmtdno8097nHi3ZJK8W3A2aKVBM6OtsPYk5yVO_N9VsvmMdTb KCOqky5Y_OOuTj8xC2gZi3lsxpldHK5uL2WPjxBXDRcQ-
Received: by 66.196.80.126; Sat, 04 Apr 2015 01:40:59 +0000 
Date: Sat, 4 Apr 2015 01:40:58 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,  "Bernie Volz (volz)" <volz@cisco.com>
Message-ID: <1191072814.5381.1428111658759.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/IUIdwKZOg3up3wOLMiK4SOdPfiY>
Cc: Brian Haberman <brian@innovationslab.net>, Ted Lemon <Ted.Lemon@nominum.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 01:41:04 -0000

I don't think it is.

Can this ever work, because this is the scenario I'm talking about:

(LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) <-> (CE: !DHCPV6_NEW_OPTION1,=
 so no ORO for it) <-> (ISP: DHCPV6_NEW_OPTION1)


Is a combined DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unknown*=
 DHCPv6 option transparent, like a DHCPv6 relay is? I think the answer is n=
o based on what Bernie said.

________________________________
From: Hemant Singh (shemant) <shemant@cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>=20
Cc: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs7652@=
att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@=
ietf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>; Ted Lemon <Ted.Lemon@no=
minum.com>=20
Sent: Friday, 3 April 2015, 23:28
Subject: RE: RA Option Guidelines



Bernie,
=20
Got it =E2=80=93 thanks much!  So the CE router implementation has to chang=
e to be configurable to include a new DHCPv6 option in the ORO for the WAN =
interface.  Once the new option is returned by the server, the CE uses the =
new option for stateless DHCPv6 services on the LAN.  Note, it is the same =
service provider who has configured the CE for the new DHCPv6 option and th=
us the same service provider also provisions the DHCPv6 server to return th=
e new option, if asked for.  There is no need for DHCPv6 relay in the CE fo=
r this new option support. =20
=20
In summary, both Mark=E2=80=99s and Barbara=E2=80=99s goals are met.
=20
Thanks,
=20
Hemant
=20


From:Bernie Volz (volz)=20
Sent: Friday, April 03, 2015 7:48 AM
To: Hemant Singh (shemant)
Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ralph =
Droms (rdroms); Ted Lemon
Subject: Re: RA Option Guidelines
=20
All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).
=20
#2 is normal DHCP operation.
=20
Note that while I think you were discussing stateless, it is true for state=
ful and stateless dhcp.

- Bernie (from iPad)

On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com> wrot=
e:
Bernie,
>=20
>Appreciate the quick reply.  Let me summarize the issues and then you can =
clarify.
>=20
>1.     The CE WAN interface does not include a new option in DHCPV6_NEW_OP=
TION1 in the ORO option of the SOLICIT to the server.  If the server is con=
figured to return the DHCPV6_NEW_OPTION1 to clients, then will the server r=
eply with DHCPV6_NEW_OPTION1 even when the client did not request the optio=
n in the ORO?   In this scenario, no code changes on the CE, and just the s=
erver configuration takes care of the issue.
>2.     The CE WAN interface does include a new option in DHCPV6_NEW_OPTION=
1 in the ORO option of the SOLICIT to the server.  If the server is configu=
red to return DHCPV6_NEW_OPTION1 to clients, then will the server reply wit=
h DHCPV6_NEW_OPTION1?
>=20
>Mark,
>=20
>Note Bernie agrees with how I and Wes Beebee (who I discussed this thread =
with) also interpreted RFC3736.  New options can be served by the stateless=
 DHCPv6 server without revising RFC3736.
>=20
>Thanks all,
>=20
>Hemant
>=20
>From:Bernie Volz (volz)=20
>Sent: Friday, April 03, 2015 7:33 AM
>To: Hemant Singh (shemant)
>Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ralph=
 Droms (rdroms); Ted Lemon
>Subject: Re: RA Option Guidelines
>=20
>I didn't study the complete thread but I am sure everyone would understand=
 that new options should be allowed to be requested. The ORO list cannot be=
 frozen ... At the time the rfc was written, that was the list. But new opt=
ion documents are not required to update RFC3736.
>=20
>There are no interop issues either as if either side (client or server) do=
esn't know of an option, it just doesn't include or ignores it.
>
>- Bernie (from iPad)
>
>On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com> wro=
te:
>Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve this =
thread for stateless DHCPv6 current vs. future options and the ORO option.=
=20
>>=20
>>Thanks,
>>=20
>>Hemant
>>=20
>>From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>Sent: Thursday, April 02, 2015 10:19 PM
>>To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.o=
rg
>>Subject: Re: RA Option Guidelines
>>=20
>>Hi Hemant,
>>
>>
>>________________________________
>>From: Hemant Singh (shemant) <shemant@cisco.com>
>>To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs765=
2@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv=
6@ietf.org>=20
>>Sent: Friday, 3 April 2015, 6:07
>>Subject: RE: RA Option Guidelines
>>
>>
>>
>>Mark,
>>=20
>>The stateless DHCPv6 server in RFC3736 allows for new options to be serve=
d by the stateless server.   Read the first paragraph of section 5.3 in RFC=
3736.
>>
>>/ So there are a few reasons why I wouldn't come to that conclusion witho=
ut some very careful reading:
>>
>>/ - The explicitly identified set of required and optional DHCPv6 options=
 that can be supported by a stateless DHCPv6 server
>>
>>/ - The lack of any overt discussion that this set of required and option=
al DHCPv6 options are a minimum, and that further DHCPv6 options could be p=
rovided by a stateless DHCPv6 server if supported by the implementation, ar=
e appropriate and requested by the
client. It being a minimum is subtly eluded to in a few sentences in the Ab=
stract and the Introduction, however I think they could easily be missed. I=
'd expect that if this is the case, it is much clearer and obvious.
>>/ - I think text you refer to in 5.3, "Clients and servers use the follow=
ing options to pass configuration information to clients; note that other o=
ptions for configuration information may be specified in future Internet St=
andards:" reads to me like a later version of this RFC will specify more st=
ateless DHCPv6 server supported options. A statement such as "Other additio=
nal DHCPv6 options appropriate for stateless DHCPv6 operation may be suppor=
ted by an implementation." would make it much clearer that the supported op=
tions were up to the implementer once the minimum had been implemented.
>>=20
>>/ So if I were implementing a stateless DHCPv6 server as per RFC3736, I'd=
 think the implementation was complete when I had implemented the options s=
pecified. I wouldn't put any effort into making it also transparent to any =
options that weren't identified in RFC3736, as there is no text discussing =
that.
>>=20
>>  So the new options you want to serve can be served by the CE stateless =
DHCPv6 server.   Now, if the service provider configures his/her DHCPv6 ser=
ver to return new options to the CE WAN interface address acquisition, the =
CE uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFC=
s support your use case and no dhcpv6 relay is required in the CE.
>>=20
>>/ I also cannot find text in RFC3315 or its updates on how to handle rece=
ived options that were not requested by the client in the Option Request Op=
tion. So if the CE WAN DHCPv6 client doesn't request an option in its ORO t=
o the SP's DHCPv6 server, I don't think it is possible for the CE to pass o=
ptions it doesn't know about onto the downstream LAN devices that do unders=
tand those DHCPv6 options.
>>=20
>>/ If it is possible to send a DHCPv6 client "ORO type" options that it di=
dn't request, then the behaviour is still ambiguous. If the DHCPv6 client i=
s a host, then it would be quite reasonable and expected to silently ignore=
 those received unknown options. However, if the DHCPv6 client is on the WA=
N side of a CE device, then those options should instead be passed to the L=
AN DHCPv6 server, which presumably should know how to correctly handle opti=
ons it doesn't understand - in the specific CE case, remember those options=
 in case a downstream LAN DHCPv6 client requests them. I think RFC7084 and =
it's ancestor RFC6204 are the only RFCs which describe this combination of =
DHCPv6 client/server working together, and neither of them have discussed p=
assing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN server.
>>=20
>>/ Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implementat=
ions that are unknown DHCPv6 option transparent? Looking at RFC7084, this b=
ehaviour seems to be very explicitly prohibited, by limiting the LAN DHCPv6=
 server support to only those options described in RFC7084, or to those des=
cribed in RFC3736.
>>=20
>>/ I think this level of DHCPv6 option transparency between CE LAN attache=
d hosts and the upstream SP's DHCPv6 server(s) can only be achieved by usin=
g a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv6 =
option transparent. (A CE would still have a DHCPv6 client on its WAN inter=
face for its own parameters and DHCPv6-PD prefixes).
>>=20
>>/ Regards,
>>/ Mark.
>>=20
>>=20
>>Barbara,
>>=20
>>For your use case, the service provider configures the DHCPv6 server to o=
nly serve options specified in RFC 7084.  Thus in this deployment no extra =
options exist to serve to the CE router LAN.
>> =20
>>Both use cases can be supported using existing RFC=E2=80=99s.
>>=20
>>Hemant
>>=20
>>
>>
>>From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>Sent: Tuesday, March 31, 2015 9:52 PM
>>To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf.o=
rg
>>Subject: Re: RA Option Guidelines
>>=20
>>Hi Hemant,
>>=20
>>
>>________________________________
>>
>>From:Hemant Singh (shemant) <shemant@cisco.com>
>>To: "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@yah=
oo.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv=
6@ietf.org>=20
>>Sent: Wednesday, 1 April 2015, 1:27
>>Subject: RE: RA Option Guidelines
>>
>>Barbara,
>>
>>Thanks for replying.   =20
>>
>>Mark,
>>
>>If new DHCPv6 options are added to be supported by RFC3736, then the SP i=
ncludes the new option in the DHCPv6 responses to the CPE WAN.  Then the CP=
E includes the new option to its LAN DHCPv6 clients.
>>=20
>>/  So here is a scenario.
>>=20
>>/ As an ISP, my customers have VoIP handsets that might support the OPTIO=
N_GEOLOCATION DHCPv6 option (I might know that a portion of them do, becaus=
e they've bought those VoIP handsets from me). How long is it going to take=
 for me to get that option added to
an updated RFC3736 and RFC7084, to get my CPE vendor to update and release =
their firmware to support that option, and test that new CPE firmware and t=
hen to deploy that new firmware?
>>=20
>>/ I think I'd be lucky if it only took 2 years.
>>=20
>>/ A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZONE=
 to my customers if their hosts request it. So now I have to try to get OPT=
ION_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor t=
o update and release their firmware
to support that option, and test that new CPE firmware and then to deploy t=
hat new firmware.
>>=20
>>/ Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, so=
 it is still "only" 2 years to get to a point where I could provide those o=
ptions to my customers. But what if that draft has progressed too far thoug=
h the IETF publishing process? I have
to create a new draft updating the to be published draft.
>>=20
>>/ So, to achieve what should be a simple task of providing location or ti=
mezone information to customers' end hosts if they want it, we've just incu=
rred the massive costs and time delays of the IETF publishing process, vend=
or firmware upgrades, firmware testing
and firmware deployment. Sounds like how hard I understand it was to roll o=
ut features like CLI in PSTN networks ...
>>=20
>> What is one option you'd like the host on the LAN to include so that we =
can understand your use case better? =20
>>
>>/ I'm going to make the problem much harder for you. I want the CPE to "s=
upport" or better, be transparent to, all current and future DHCPv6 options=
, and I don't want to have to upgrade or ask my customers to successfully u=
pgrade their CPE each and every time
>>there is a new DHCPv6 option defined that might be useful to me and them.=
 I want to be able to provide service parameters to my customers hosts, dir=
ectly or indirectly, without the software revision or model of their CPE be=
ing the constraint.
>>
>>The SIP server is already included as one option supported by RFC3736.  C=
ertainly, if the SIP server support is needed in the RA, I am open for it s=
ince the RA already includes DNS information.
>>=20
>>/ I don't think DNS in RAs was a good idea, and neither were SIP options =
when they were proposed. See that time consuming and service disrupting fir=
mware upgrade cycle for new DHCPv6 options? Same problem if you use RA opti=
ons to achieve the same goal. New
firmware upgrade each time you want to support a new RA option.
>>=20
>>/ Duplication between RA options and DHCPv6 options also causes more prob=
lems. Which is preferred? Are they treated equally or does one take precede=
nce over the other? As far as I'm aware, these questions haven't been answe=
red for the DHCPv6 DNS and RA DNS
options yet. It might be simple to come up with a simple rule for more DHCP=
v6 options are duplicated into RAs, however their might be some specific ca=
ses where the RA option value should be preferred over the DHCPv6 equivalen=
t option and vice-versa.=20
>>=20
>>However, I still ask the question as to how an RA received at the WAN of =
the CPE has its options propagated to the RA on the LAN?  At the time of wr=
iting RFC 6204 or RFC 7084, there is no such provision between the RA recei=
ved on the WAN and the RA issued on
the LAN of the CE router.
>>=20
>>/ Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6 o=
ptions that are unknown by the CPE will pass right through it transparently=
. The only complication is when stateful DHCPv6 addressing is used on the C=
PE LAN interface, and I suggested
a hybrid mode of operation for a DHCPv6 server in that draft which I think =
solves that problem.
>>
>>Others,
>>
>>Also, why does one need an RA Option Guideline?  RFC4861 specifies a TLV =
format and an option Type.  I don't see anything else needed if I need to s=
pecify a new RA option.=20
>>
>>Thanks,
>>
>>Hemant
>>
>>-----Original Message-----
>>From: STARK, BARBARA H [mailto:bs7652@att.com]=20
>>Sent: Tuesday, March 31, 2015 9:25 AM
>>To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.org
>>Subject: RE: RA Option Guidelines
>>=20
>>
>>
>>
>>RFC 7084 already says:=20
>>  L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>>          options (as listed in Section 5.3 of [RFC3736]) received from
>>          the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>>          server.


From nobody Fri Apr  3 18:45:57 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0FE91A6F17 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 18:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 ROH0UdQrk2Ld for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 18:45:55 -0700 (PDT)
Received: from nm46-vm7.bullet.mail.bf1.yahoo.com (nm46-vm7.bullet.mail.bf1.yahoo.com [216.109.115.110]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 512631A6F11 for <ipv6@ietf.org>; Fri,  3 Apr 2015 18:45:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428111954; bh=CJHGRtqTs079TI6BNtmRtpOPnuTN9fJGSo9w6H0cg98=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=q/jhuqxLXIF3ipkzUFGH9uMhavxm3MSzfhCsLDF/sHx97LyU+ldnodHizaOrRHIRMaRQpkgqwBDHBX3Fp3BwM4duT4I0OJb+EkZnYLJaNC4OwkPp3TMHT3/KLB5S+40jJQUGv3ufOmLVNRE0pxII8RZ7Nb8WKdVAUsRNEQx2hJxr6PyuDngV8t4xvYzNYU2gIfK9pzqNaNgN/rzj/6kCjc49EWP/Q3Zuij877YJgnTN2KxuMlZYNmCF2mQ0WSMBwYIyfKgSGhu6Dm0M/9JISv7oToomidX2PiuJBk1gjE/1wwNrMUmqF/lujD9iFkmY4HlIjyOWlMbMy1p5oIK1DIw==
Received: from [98.139.214.32] by nm46.bullet.mail.bf1.yahoo.com with NNFMP; 04 Apr 2015 01:45:54 -0000
Received: from [98.139.212.220] by tm15.bullet.mail.bf1.yahoo.com with NNFMP;  04 Apr 2015 01:45:54 -0000
Received: from [127.0.0.1] by omp1029.mail.bf1.yahoo.com with NNFMP; 04 Apr 2015 01:45:54 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 399819.77199.bm@omp1029.mail.bf1.yahoo.com
X-YMail-OSG: eXyVZtUVM1kFHYveMG5F3MzMbPoBp2vuUmXUl8WnlNr_zv16axdoeq6OcUgKu6F aV_WBAz1YLgGuoxZUFMlfknvhTf7O5RxxENM_BaesbRGHEZrosbvVro4XYX0c0HaUKD2ZzMT_o0N wvpzM7RwDhMdfjcE8xq.bO8Yxg5uXf4k1FSnK6pzWb3iykxYS_2_QPgfm6OEKNbsDvZlmsEmtG0U cLmLcsyfGPn2AxJZFK4OQ1hSPs57aUxMGcJawov7jmex9zaSO5fzZkJ9S0MTiygg34Ivl0S5JHhT 9rYVMyZiI9GwgREd.v03PEe3OEtxvpON3oscKLDK9ZfAH2KHQwPxTDdDI2nO8msihkM4QPf4u7aa eNJ_aUoWIknMVYdZYdYq03cL8yi1Nlp1YacNxQF8YLfdJeSCtN9_35hl3XdE_DPenHcciilhhvVz Gg3H4Uu7iyt5uypOhfStO6nvWrZOvCpFV_iuc7O62VDg9WkprDwRcymXX.Zlo6iTIgB0YjBWSEVE 2QSEbHOLMtSVnazpNQ_rgdXOPrAYxMqgVR8PL7SdVQE8-
Received: by 76.13.27.35; Sat, 04 Apr 2015 01:45:53 +0000 
Date: Sat, 4 Apr 2015 01:45:52 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Ole Troan <otroan@employees.org>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1826701307.5558007.1428111952812.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
References: <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yy96XN4kwulEfVM1pOXDohhGW4g>
Cc: Brian Haberman <brian@innovationslab.net>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 01:45:56 -0000

So,=20

RA options should be used for link specific attributes and parameters that =
all hosts attached to the link use, because it is hard to do host specific =
RAs and,

DHCPv6 options should be used for host specific attributes and parameters, =
because it is easy to do host specific DHCPv6 messages

?




----- Original Message -----
From: Ole Troan <otroan@employees.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Hemant Singh (shemant) <shemant@cisco.com>; Barbara Stark <bs7652@att.c=
om>; Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@inno=
vationslab.net>; 6man WG <ipv6@ietf.org>
Sent: Saturday, 4 April 2015, 7:18
Subject: Re: RA Option Guidelines


>=20
> Do we actually agree on this, or rather on a slightly expanded version:
>=20
> RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only) necessary for a simple unmanaged network.
> The only exception is RFC 6106 (DNS Configuration). More complex situatio=
ns
> are better handled by other configuration metods such as DHCPv6.

I agree only with this part:
=E2=80=9CRA options should be limited to link-local/subnet specific paramet=
ers (i.e. layer 3 parameters only). The only exception is RFC6106 (DNS Conf=
iguration).=E2=80=9D

RA=E2=80=99s aren=E2=80=99t unmanaged. they certainly don=E2=80=99t require=
 the network to be simple.
there was a thread on the DHC list a while back appearing to reach the conc=
lusion that DHCP should only be used to configure the network layer (althou=
gh there are many exceptions).
the main difference between RA and DHCP is that one is per subnet, the othe=
r per host.

cheers,
Ole


From nobody Fri Apr  3 20:25:14 2015
Return-Path: <volz@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 994871A892F for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 20:25:13 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0MjInXor_vOS for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 20:25:10 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2680A1A893C for <ipv6@ietf.org>; Fri,  3 Apr 2015 20:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16689; q=dns/txt; s=iport; t=1428117910; x=1429327510; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=K7NA2FvHYLVxGMWw8C/0TPyxL1uZsbYVatsR35ABOLs=; b=k4NKjzEB322ZCjB6TCMfuwDbgDjUsvkVVrK+4VksnaxSVcdDc1eKYKcM GdYQkr9diaSaU8AKls8lsl0UmLVwrQqEQ9YqJWu1rn+jkm5enjSs6nd6A OVEGm/zJR3FvI3Rg26BjYVL7DJuMb8E5xSckW7NdMyIWZZi9yS2M/e9iJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C2CACoWB9V/4UNJK1cgwtSXMVpCoIzg0oCgSxMAQEBAQEBfoQeAQEBAwEBAQEkRAMLBQcEAgEIEQQBAQEnBycLFAkIAgQOBYgbAwkIDcwtAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLKYJHgWcJDwgrBwIEgxGBFgWFEAqBBIpNiDmBR4EdgzWCYIYdToJng0giggMcgVBvgQSBPwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,521,1422921600"; d="scan'208";a="409072249"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-7.cisco.com with ESMTP; 04 Apr 2015 03:25:09 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t343P8iW024715 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 4 Apr 2015 03:25:08 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 22:25:08 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlnXXmv757w0ecSSL/v887950xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAB4TagABWoID//62BWIAAXxoAgADdcQD//8lI5g==
Date: Sat, 4 Apr 2015 03:25:07 +0000
Message-ID: <C9212BE0-A9D1-4AC8-8886-2B4A5CA858A0@cisco.com>
References: <75B6FA9F576969419E42BECB86CB1B891683899C@xmb-rcd-x06.cisco.com>,  <1191072814.5381.1428111658759.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1191072814.5381.1428111658759.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/idhUdgiqCSOLcoiJkRZrv9QddIY>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 03:25:13 -0000

Yes, in that situation the CE would not have requested the option from the =
ISP. You would need to update firmware on CE.

As new options get assigned, clients & servers need to be updated to make u=
se of them.

You could also provide some CE configuration to request and save arbitary o=
ptions, but that only is useful to expert CE users and probably has securit=
y issues.

- Bernie (from iPad)

> On Apr 3, 2015, at 9:41 PM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au> wr=
ote:
>=20
> I don't think it is.
>=20
> Can this ever work, because this is the scenario I'm talking about:
>=20
> (LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) <-> (CE: !DHCPV6_NEW_OPTION=
1, so no ORO for it) <-> (ISP: DHCPV6_NEW_OPTION1)
>=20
>=20
> Is a combined DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unknow=
n* DHCPv6 option transparent, like a DHCPv6 relay is? I think the answer is=
 no based on what Bernie said.
>=20
> ________________________________
> From: Hemant Singh (shemant) <shemant@cisco.com>
> To: Bernie Volz (volz) <volz@cisco.com>=20
> Cc: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs765=
2@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv=
6@ietf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>; Ted Lemon <Ted.Lemon@=
nominum.com>=20
> Sent: Friday, 3 April 2015, 23:28
> Subject: RE: RA Option Guidelines
>=20
>=20
>=20
> Bernie,
>=20
> Got it =96 thanks much!  So the CE router implementation has to change to=
 be configurable to include a new DHCPv6 option in the ORO for the WAN inte=
rface.  Once the new option is returned by the server, the CE uses the new =
option for stateless DHCPv6 services on the LAN.  Note, it is the same serv=
ice provider who has configured the CE for the new DHCPv6 option and thus t=
he same service provider also provisions the DHCPv6 server to return the ne=
w option, if asked for.  There is no need for DHCPv6 relay in the CE for th=
is new option support. =20
>=20
> In summary, both Mark=92s and Barbara=92s goals are met.
>=20
> Thanks,
>=20
> Hemant
>=20
>=20
>=20
> From:Bernie Volz (volz)=20
> Sent: Friday, April 03, 2015 7:48 AM
> To: Hemant Singh (shemant)
> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ralp=
h Droms (rdroms); Ted Lemon
> Subject: Re: RA Option Guidelines
>=20
> All options MUST be in ORO for server to return (there are some "protocol=
" options, such as client-id and server-id that are NOT supposed to be in O=
RO). So client controls the options it gets. So #1 is not true (some server=
s, such as CPNR, can be configured to return options the client did not req=
uest, but generally that is useless since the client will most likely ignor=
e it).
>=20
> #2 is normal DHCP operation.
>=20
> Note that while I think you were discussing stateless, it is true for sta=
teful and stateless dhcp.
>=20
> - Bernie (from iPad)
>=20
>> On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com> w=
rote:
>> Bernie,
>>=20
>> Appreciate the quick reply.  Let me summarize the issues and then you ca=
n clarify.
>>=20
>> 1.     The CE WAN interface does not include a new option in DHCPV6_NEW_=
OPTION1 in the ORO option of the SOLICIT to the server.  If the server is c=
onfigured to return the DHCPV6_NEW_OPTION1 to clients, then will the server=
 reply with DHCPV6_NEW_OPTION1 even when the client did not request the opt=
ion in the ORO?   In this scenario, no code changes on the CE, and just the=
 server configuration takes care of the issue.
>> 2.     The CE WAN interface does include a new option in DHCPV6_NEW_OPTI=
ON1 in the ORO option of the SOLICIT to the server.  If the server is confi=
gured to return DHCPV6_NEW_OPTION1 to clients, then will the server reply w=
ith DHCPV6_NEW_OPTION1?
>>=20
>> Mark,
>>=20
>> Note Bernie agrees with how I and Wes Beebee (who I discussed this threa=
d with) also interpreted RFC3736.  New options can be served by the statele=
ss DHCPv6 server without revising RFC3736.
>>=20
>> Thanks all,
>>=20
>> Hemant
>>=20
>> From:Bernie Volz (volz)=20
>> Sent: Friday, April 03, 2015 7:33 AM
>> To: Hemant Singh (shemant)
>> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ral=
ph Droms (rdroms); Ted Lemon
>> Subject: Re: RA Option Guidelines
>>=20
>> I didn't study the complete thread but I am sure everyone would understa=
nd that new options should be allowed to be requested. The ORO list cannot =
be frozen ... At the time the rfc was written, that was the list. But new o=
ption documents are not required to update RFC3736.
>>=20
>> There are no interop issues either as if either side (client or server) =
doesn't know of an option, it just doesn't include or ignores it.
>>=20
>> - Bernie (from iPad)
>>=20
>>> On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com> =
wrote:
>>> Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve th=
is thread for stateless DHCPv6 current vs. future options and the ORO optio=
n.=20
>>>=20
>>> Thanks,
>>>=20
>>> Hemant
>>>=20
>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>> Sent: Thursday, April 02, 2015 10:19 PM
>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf=
.org
>>> Subject: Re: RA Option Guidelines
>>>=20
>>> Hi Hemant,
>>>=20
>>>=20
>>> ________________________________
>>> From: Hemant Singh (shemant) <shemant@cisco.com>
>>> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs7=
652@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <i=
pv6@ietf.org>=20
>>> Sent: Friday, 3 April 2015, 6:07
>>> Subject: RE: RA Option Guidelines
>>>=20
>>>=20
>>>=20
>>> Mark,
>>>=20
>>> The stateless DHCPv6 server in RFC3736 allows for new options to be ser=
ved by the stateless server.   Read the first paragraph of section 5.3 in R=
FC3736.
>>>=20
>>> / So there are a few reasons why I wouldn't come to that conclusion wit=
hout some very careful reading:
>>>=20
>>> / - The explicitly identified set of required and optional DHCPv6 optio=
ns that can be supported by a stateless DHCPv6 server
>>>=20
>>> / - The lack of any overt discussion that this set of required and opti=
onal DHCPv6 options are a minimum, and that further DHCPv6 options could be=
 provided by a stateless DHCPv6 server if supported by the implementation, =
are appropriate and requested by the
> client. It being a minimum is subtly eluded to in a few sentences in the =
Abstract and the Introduction, however I think they could easily be missed.=
 I'd expect that if this is the case, it is much clearer and obvious.
>>> / - I think text you refer to in 5.3, "Clients and servers use the foll=
owing options to pass configuration information to clients; note that other=
 options for configuration information may be specified in future Internet =
Standards:" reads to me like a later version of this RFC will specify more =
stateless DHCPv6 server supported options. A statement such as "Other addit=
ional DHCPv6 options appropriate for stateless DHCPv6 operation may be supp=
orted by an implementation." would make it much clearer that the supported =
options were up to the implementer once the minimum had been implemented.
>>>=20
>>> / So if I were implementing a stateless DHCPv6 server as per RFC3736, I=
'd think the implementation was complete when I had implemented the options=
 specified. I wouldn't put any effort into making it also transparent to an=
y options that weren't identified in RFC3736, as there is no text discussin=
g that.
>>>=20
>>> So the new options you want to serve can be served by the CE stateless =
DHCPv6 server.   Now, if the service provider configures his/her DHCPv6 ser=
ver to return new options to the CE WAN interface address acquisition, the =
CE uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFC=
s support your use case and no dhcpv6 relay is required in the CE.
>>>=20
>>> / I also cannot find text in RFC3315 or its updates on how to handle re=
ceived options that were not requested by the client in the Option Request =
Option. So if the CE WAN DHCPv6 client doesn't request an option in its ORO=
 to the SP's DHCPv6 server, I don't think it is possible for the CE to pass=
 options it doesn't know about onto the downstream LAN devices that do unde=
rstand those DHCPv6 options.
>>>=20
>>> / If it is possible to send a DHCPv6 client "ORO type" options that it =
didn't request, then the behaviour is still ambiguous. If the DHCPv6 client=
 is a host, then it would be quite reasonable and expected to silently igno=
re those received unknown options. However, if the DHCPv6 client is on the =
WAN side of a CE device, then those options should instead be passed to the=
 LAN DHCPv6 server, which presumably should know how to correctly handle op=
tions it doesn't understand - in the specific CE case, remember those optio=
ns in case a downstream LAN DHCPv6 client requests them. I think RFC7084 an=
d it's ancestor RFC6204 are the only RFCs which describe this combination o=
f DHCPv6 client/server working together, and neither of them have discussed=
 passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN serve=
r.
>>>=20
>>> / Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implement=
ations that are unknown DHCPv6 option transparent? Looking at RFC7084, this=
 behaviour seems to be very explicitly prohibited, by limiting the LAN DHCP=
v6 server support to only those options described in RFC7084, or to those d=
escribed in RFC3736.
>>>=20
>>> / I think this level of DHCPv6 option transparency between CE LAN attac=
hed hosts and the upstream SP's DHCPv6 server(s) can only be achieved by us=
ing a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv=
6 option transparent. (A CE would still have a DHCPv6 client on its WAN int=
erface for its own parameters and DHCPv6-PD prefixes).
>>>=20
>>> / Regards,
>>> / Mark.
>>>=20
>>>=20
>>> Barbara,
>>>=20
>>> For your use case, the service provider configures the DHCPv6 server to=
 only serve options specified in RFC 7084.  Thus in this deployment no extr=
a options exist to serve to the CE router LAN.
>>>=20
>>> Both use cases can be supported using existing RFC=92s.
>>>=20
>>> Hemant
>>>=20
>>>=20
>>>=20
>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>> Sent: Tuesday, March 31, 2015 9:52 PM
>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf=
.org
>>> Subject: Re: RA Option Guidelines
>>>=20
>>> Hi Hemant,
>>>=20
>>>=20
>>> ________________________________
>>>=20
>>> From:Hemant Singh (shemant) <shemant@cisco.com>
>>> To: "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@y=
ahoo.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <i=
pv6@ietf.org>=20
>>> Sent: Wednesday, 1 April 2015, 1:27
>>> Subject: RE: RA Option Guidelines
>>>=20
>>> Barbara,
>>>=20
>>> Thanks for replying.   =20
>>>=20
>>> Mark,
>>>=20
>>> If new DHCPv6 options are added to be supported by RFC3736, then the SP=
 includes the new option in the DHCPv6 responses to the CPE WAN.  Then the =
CPE includes the new option to its LAN DHCPv6 clients.
>>>=20
>>> /  So here is a scenario.
>>>=20
>>> / As an ISP, my customers have VoIP handsets that might support the OPT=
ION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, beca=
use they've bought those VoIP handsets from me). How long is it going to ta=
ke for me to get that option added to
> an updated RFC3736 and RFC7084, to get my CPE vendor to update and releas=
e their firmware to support that option, and test that new CPE firmware and=
 then to deploy that new firmware?
>>>=20
>>> / I think I'd be lucky if it only took 2 years.
>>>=20
>>> / A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZO=
NE to my customers if their hosts request it. So now I have to try to get O=
PTION_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor=
 to update and release their firmware
> to support that option, and test that new CPE firmware and then to deploy=
 that new firmware.
>>>=20
>>> / Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, =
so it is still "only" 2 years to get to a point where I could provide those=
 options to my customers. But what if that draft has progressed too far tho=
ugh the IETF publishing process? I have
> to create a new draft updating the to be published draft.
>>>=20
>>> / So, to achieve what should be a simple task of providing location or =
timezone information to customers' end hosts if they want it, we've just in=
curred the massive costs and time delays of the IETF publishing process, ve=
ndor firmware upgrades, firmware testing
> and firmware deployment. Sounds like how hard I understand it was to roll=
 out features like CLI in PSTN networks ...
>>>=20
>>> What is one option you'd like the host on the LAN to include so that we=
 can understand your use case better? =20
>>>=20
>>> / I'm going to make the problem much harder for you. I want the CPE to =
"support" or better, be transparent to, all current and future DHCPv6 optio=
ns, and I don't want to have to upgrade or ask my customers to successfully=
 upgrade their CPE each and every time
>>> there is a new DHCPv6 option defined that might be useful to me and the=
m. I want to be able to provide service parameters to my customers hosts, d=
irectly or indirectly, without the software revision or model of their CPE =
being the constraint.
>>>=20
>>> The SIP server is already included as one option supported by RFC3736. =
 Certainly, if the SIP server support is needed in the RA, I am open for it=
 since the RA already includes DNS information.
>>>=20
>>> / I don't think DNS in RAs was a good idea, and neither were SIP option=
s when they were proposed. See that time consuming and service disrupting f=
irmware upgrade cycle for new DHCPv6 options? Same problem if you use RA op=
tions to achieve the same goal. New
> firmware upgrade each time you want to support a new RA option.
>>>=20
>>> / Duplication between RA options and DHCPv6 options also causes more pr=
oblems. Which is preferred? Are they treated equally or does one take prece=
dence over the other? As far as I'm aware, these questions haven't been ans=
wered for the DHCPv6 DNS and RA DNS
> options yet. It might be simple to come up with a simple rule for more DH=
CPv6 options are duplicated into RAs, however their might be some specific =
cases where the RA option value should be preferred over the DHCPv6 equival=
ent option and vice-versa.=20
>>>=20
>>> However, I still ask the question as to how an RA received at the WAN o=
f the CPE has its options propagated to the RA on the LAN?  At the time of =
writing RFC 6204 or RFC 7084, there is no such provision between the RA rec=
eived on the WAN and the RA issued on
> the LAN of the CE router.
>>>=20
>>> / Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6=
 options that are unknown by the CPE will pass right through it transparent=
ly. The only complication is when stateful DHCPv6 addressing is used on the=
 CPE LAN interface, and I suggested
> a hybrid mode of operation for a DHCPv6 server in that draft which I thin=
k solves that problem.
>>>=20
>>> Others,
>>>=20
>>> Also, why does one need an RA Option Guideline?  RFC4861 specifies a TL=
V format and an option Type.  I don't see anything else needed if I need to=
 specify a new RA option.=20
>>>=20
>>> Thanks,
>>>=20
>>> Hemant
>>>=20
>>> -----Original Message-----
>>> From: STARK, BARBARA H [mailto:bs7652@att.com]=20
>>> Sent: Tuesday, March 31, 2015 9:25 AM
>>> To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.o=
rg
>>> Subject: RE: RA Option Guidelines
>>>=20
>>>=20
>>>=20
>>>=20
>>> RFC 7084 already says:=20
>>> L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>>>         options (as listed in Section 5.3 of [RFC3736]) received from
>>>         the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>>>         server.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Apr  3 21:34:45 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 961301A89A8 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 21:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.502
X-Spam-Level: 
X-Spam-Status: No, score=0.502 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 5AehtBWBUWM9 for <ipv6@ietfa.amsl.com>; Fri,  3 Apr 2015 21:34:39 -0700 (PDT)
Received: from nm1-vm1.bullet.mail.bf1.yahoo.com (nm1-vm1.bullet.mail.bf1.yahoo.com [98.139.213.163]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D02B71A89A3 for <ipv6@ietf.org>; Fri,  3 Apr 2015 21:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428122078; bh=yuF2KfkULttw1VKbmf8XbVoNoAYRjsysn635WINb6WA=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=pGWx4AB2cEk16Nyudt7uzZffJxamuZcswcQqydLGJY4VJBAHJyZWLSZtl1ITVGC/qAc8z+ml7EtshaM4WBpq6s4sSHCYx9zfBT+bt+AfqsVwU95CPFxnSq+2NENnAqbVZNp62CvwyeEAnb7wEhWrbkbqEuWFSvMOMeT094cpzYiTFiUzVYekN8Lfa1E1EuL6uFUJVkrAf3ViJsSaw+Q7zL4hJ8pttwqVDxapN5U+DtKje22lw4zrkJOqnGuuC+khEgqo0mGXysiZ4ndtjYiSbBQJfgLdjyPncr9RLkttFBbRbt3j80BU2JpTf0MqkG94LfePOQ5WkYF/FdRiFOwJJg==
Received: from [98.139.215.143] by nm1.bullet.mail.bf1.yahoo.com with NNFMP; 04 Apr 2015 04:34:38 -0000
Received: from [98.139.212.232] by tm14.bullet.mail.bf1.yahoo.com with NNFMP;  04 Apr 2015 04:34:38 -0000
Received: from [127.0.0.1] by omp1041.mail.bf1.yahoo.com with NNFMP; 04 Apr 2015 04:34:38 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 8916.1380.bm@omp1041.mail.bf1.yahoo.com
X-YMail-OSG: sT.e6DgVM1lX5DUj5JbeptvW8xnHZ9m8SZtSvr708lDTyr2UFFqZ7eMC6QbTDq0 15aPYjSwp9rizAoR0VDLByrqeVOtgk5wu8VI.PQV9D8La3DgFsE.FYlFc07CoQBqmMxl4hmur9wT d_eP92A143w3JGKZVhiLMfP4qec5.NMhOJt4TxJEIVg9k22vNRe2XDblLrX1_FYVWFvSFP__5XeQ 1ukexKZAMsTxaKa_LJzOqzc_mc1mxZPGRrSrAoAB4qPEtOD__4czvRldEMPBY6SqEO3gvJ2NnvaJ insGR7uhvGPqpQ_1TYyV8Jd78osBOlgixNpD1LZ_TXT7wlTMBGIp_AIMeCvyh1wV_2._yh_X1NO4 YgS3E58hely.EJzN9f3YtsrvufkrNatqxo7h8LTWjkMoHvQ7hBW3b33Ve039MqJCnNHE2ukN9vw6 SLEatHH7g0AEwdFTwMXvIiiEgiIl3PbmIWmDS_gEHJoEslLJ20oddhzU2q3I1Gn9SwdijhMKmePP _g3PUdxFhQf5ogzK9zJ5Um0bBWRHY6iD0eRmqRCqsnAE-
Received: by 66.196.80.126; Sat, 04 Apr 2015 04:34:37 +0000 
Date: Sat, 4 Apr 2015 04:34:04 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "Bernie Volz (volz)" <volz@cisco.com>
Message-ID: <630957669.32929.1428122044593.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <C9212BE0-A9D1-4AC8-8886-2B4A5CA858A0@cisco.com>
References: <C9212BE0-A9D1-4AC8-8886-2B4A5CA858A0@cisco.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_32928_1181099829.1428122044583"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vpp8N1k6qRMHLtxwhNqm37HaU_I>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 04:34:44 -0000

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

Hi Bernie,
      From: Bernie Volz (volz) <volz@cisco.com>
 To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>=20
Cc: Hemant Singh (shemant) <shemant@cisco.com>; Brian Haberman <brian@innov=
ationslab.net>; Ted Lemon <Ted.Lemon@nominum.com>; "ipv6@ietf.org" <ipv6@ie=
tf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>=20
 Sent: Saturday, 4 April 2015, 14:25
 Subject: Re: RA Option Guidelines
  =20
Yes, in that situation the CE would not have requested the option from the =
ISP. You would need to update firmware on CE.
/ Thank you for confirming that.
/ Having to update firmware on the CE is the exact situation I think should=
 be avoided.
/ If CE devices have to be upgraded to deploy new applications and services=
 (and I think 'deployment' includes automated configuration of them), then =
in my opinion Internet (application) transparency has been lost.

As new options get assigned, clients & servers need to be updated to make u=
se of them.
/ If the CE device is DHCPv6 option transparent (i.e., is running a LAN DHC=
Pv6 relay), then upgrades are only required to the hosts that want to use t=
he new DHCPv6 options, which is much less disruptive than also requiring CE=
 firmware upgrades.

You could also provide some CE configuration to request and save arbitary o=
ptions, but that only is useful to expert CE users and probably has securit=
y issues.
/ Agree, not practical for typical residential users.
/ Regards,/ Mark.

- Bernie (from iPad)



> On Apr 3, 2015, at 9:41 PM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au> wr=
ote:
>=20
> I don't think it is.
>=20
> Can this ever work, because this is the scenario I'm talking about:
>=20
> (LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) <-> (CE: !DHCPV6_NEW_OPTION=
1, so no ORO for it) <-> (ISP: DHCPV6_NEW_OPTION1)
>=20
>=20
> Is a combined DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unknow=
n* DHCPv6 option transparent, like a DHCPv6 relay is? I think the answer is=
 no based on what Bernie said.
>=20
> ________________________________
> From: Hemant Singh (shemant) <shemant@cisco.com>
> To: Bernie Volz (volz) <volz@cisco.com>=20
> Cc: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs765=
2@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv=
6@ietf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>; Ted Lemon <Ted.Lemon@=
nominum.com>=20
> Sent: Friday, 3 April 2015, 23:28
> Subject: RE: RA Option Guidelines
>=20
>=20
>=20
> Bernie,
>=20
> Got it =E2=80=93 thanks much!=C2=A0 So the CE router implementation has t=
o change to be configurable to include a new DHCPv6 option in the ORO for t=
he WAN interface.=C2=A0 Once the new option is returned by the server, the =
CE uses the new option for stateless DHCPv6 services on the LAN.=C2=A0 Note=
, it is the same service provider who has configured the CE for the new DHC=
Pv6 option and thus the same service provider also provisions the DHCPv6 se=
rver to return the new option, if asked for.=C2=A0 There is no need for DHC=
Pv6 relay in the CE for this new option support.=C2=A0=20
>=20
> In summary, both Mark=E2=80=99s and Barbara=E2=80=99s goals are met.
>=20
> Thanks,
>=20
> Hemant
>=20
>=20
>=20
> From:Bernie Volz (volz)=20
> Sent: Friday, April 03, 2015 7:48 AM
> To: Hemant Singh (shemant)
> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ralp=
h Droms (rdroms); Ted Lemon
> Subject: Re: RA Option Guidelines
>=20
> All options MUST be in ORO for server to return (there are some "protocol=
" options, such as client-id and server-id that are NOT supposed to be in O=
RO). So client controls the options it gets. So #1 is not true (some server=
s, such as CPNR, can be configured to return options the client did not req=
uest, but generally that is useless since the client will most likely ignor=
e it).
>=20
> #2 is normal DHCP operation.
>=20
> Note that while I think you were discussing stateless, it is true for sta=
teful and stateless dhcp.
>=20
> - Bernie (from iPad)
>=20
>> On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com> w=
rote:
>> Bernie,
>>=20
>> Appreciate the quick reply.=C2=A0 Let me summarize the issues and then y=
ou can clarify.
>>=20
>> 1.=C2=A0 =C2=A0 The CE WAN interface does not include a new option in DH=
CPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the server.=C2=A0 If t=
he server is configured to return the DHCPV6_NEW_OPTION1 to clients, then w=
ill the server reply with DHCPV6_NEW_OPTION1 even when the client did not r=
equest the option in the ORO?=C2=A0 In this scenario, no code changes on th=
e CE, and just the server configuration takes care of the issue.
>> 2.=C2=A0 =C2=A0 The CE WAN interface does include a new option in DHCPV6=
_NEW_OPTION1 in the ORO option of the SOLICIT to the server.=C2=A0 If the s=
erver is configured to return DHCPV6_NEW_OPTION1 to clients, then will the =
server reply with DHCPV6_NEW_OPTION1?
>>=20
>> Mark,
>>=20
>> Note Bernie agrees with how I and Wes Beebee (who I discussed this threa=
d with) also interpreted RFC3736.=C2=A0 New options can be served by the st=
ateless DHCPv6 server without revising RFC3736.
>>=20
>> Thanks all,
>>=20
>> Hemant
>>=20
>> From:Bernie Volz (volz)=20
>> Sent: Friday, April 03, 2015 7:33 AM
>> To: Hemant Singh (shemant)
>> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ral=
ph Droms (rdroms); Ted Lemon
>> Subject: Re: RA Option Guidelines
>>=20
>> I didn't study the complete thread but I am sure everyone would understa=
nd that new options should be allowed to be requested. The ORO list cannot =
be frozen ... At the time the rfc was written, that was the list. But new o=
ption documents are not required to update RFC3736.
>>=20
>> There are no interop issues either as if either side (client or server) =
doesn't know of an option, it just doesn't include or ignores it.
>>=20
>> - Bernie (from iPad)
>>=20
>>> On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com> =
wrote:
>>> Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve th=
is thread for stateless DHCPv6 current vs. future options and the ORO optio=
n.=20
>>>=20
>>> Thanks,
>>>=20
>>> Hemant
>>>=20
>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>> Sent: Thursday, April 02, 2015 10:19 PM
>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf=
.org
>>> Subject: Re: RA Option Guidelines
>>>=20
>>> Hi Hemant,
>>>=20
>>>=20
>>> ________________________________
>>> From: Hemant Singh (shemant) <shemant@cisco.com>
>>> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs7=
652@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <i=
pv6@ietf.org>=20
>>> Sent: Friday, 3 April 2015, 6:07
>>> Subject: RE: RA Option Guidelines
>>>=20
>>>=20
>>>=20
>>> Mark,
>>>=20
>>> The stateless DHCPv6 server in RFC3736 allows for new options to be ser=
ved by the stateless server.=C2=A0 Read the first paragraph of section 5.3 =
in RFC3736.
>>>=20
>>> / So there are a few reasons why I wouldn't come to that conclusion wit=
hout some very careful reading:
>>>=20
>>> / - The explicitly identified set of required and optional DHCPv6 optio=
ns that can be supported by a stateless DHCPv6 server
>>>=20
>>> / - The lack of any overt discussion that this set of required and opti=
onal DHCPv6 options are a minimum, and that further DHCPv6 options could be=
 provided by a stateless DHCPv6 server if supported by the implementation, =
are appropriate and requested by the
> client. It being a minimum is subtly eluded to in a few sentences in the =
Abstract and the Introduction, however I think they could easily be missed.=
 I'd expect that if this is the case, it is much clearer and obvious.
>>> / - I think text you refer to in 5.3, "Clients and servers use the foll=
owing options to pass configuration information to clients; note that other=
 options for configuration information may be specified in future Internet =
Standards:" reads to me like a later version of this RFC will specify more =
stateless DHCPv6 server supported options. A statement such as "Other addit=
ional DHCPv6 options appropriate for stateless DHCPv6 operation may be supp=
orted by an implementation." would make it much clearer that the supported =
options were up to the implementer once the minimum had been implemented.
>>>=20
>>> / So if I were implementing a stateless DHCPv6 server as per RFC3736, I=
'd think the implementation was complete when I had implemented the options=
 specified. I wouldn't put any effort into making it also transparent to an=
y options that weren't identified in RFC3736, as there is no text discussin=
g that.
>>>=20
>>> So the new options you want to serve can be served by the CE stateless =
DHCPv6 server.=C2=A0 Now, if the service provider configures his/her DHCPv6=
 server to return new options to the CE WAN interface address acquisition, =
the CE uses the options on the LAN.=C2=A0 See bullet L-12 of RFC 7084.=C2=
=A0 Existing RFCs support your use case and no dhcpv6 relay is required in =
the CE.
>>>=20
>>> / I also cannot find text in RFC3315 or its updates on how to handle re=
ceived options that were not requested by the client in the Option Request =
Option. So if the CE WAN DHCPv6 client doesn't request an option in its ORO=
 to the SP's DHCPv6 server, I don't think it is possible for the CE to pass=
 options it doesn't know about onto the downstream LAN devices that do unde=
rstand those DHCPv6 options.
>>>=20
>>> / If it is possible to send a DHCPv6 client "ORO type" options that it =
didn't request, then the behaviour is still ambiguous. If the DHCPv6 client=
 is a host, then it would be quite reasonable and expected to silently igno=
re those received unknown options. However, if the DHCPv6 client is on the =
WAN side of a CE device, then those options should instead be passed to the=
 LAN DHCPv6 server, which presumably should know how to correctly handle op=
tions it doesn't understand - in the specific CE case, remember those optio=
ns in case a downstream LAN DHCPv6 client requests them. I think RFC7084 an=
d it's ancestor RFC6204 are the only RFCs which describe this combination o=
f DHCPv6 client/server working together, and neither of them have discussed=
 passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN serve=
r.
>>>=20
>>> / Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implement=
ations that are unknown DHCPv6 option transparent? Looking at RFC7084, this=
 behaviour seems to be very explicitly prohibited, by limiting the LAN DHCP=
v6 server support to only those options described in RFC7084, or to those d=
escribed in RFC3736.
>>>=20
>>> / I think this level of DHCPv6 option transparency between CE LAN attac=
hed hosts and the upstream SP's DHCPv6 server(s) can only be achieved by us=
ing a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv=
6 option transparent. (A CE would still have a DHCPv6 client on its WAN int=
erface for its own parameters and DHCPv6-PD prefixes).
>>>=20
>>> / Regards,
>>> / Mark.
>>>=20
>>>=20
>>> Barbara,
>>>=20
>>> For your use case, the service provider configures the DHCPv6 server to=
 only serve options specified in RFC 7084.=C2=A0 Thus in this deployment no=
 extra options exist to serve to the CE router LAN.
>>>=20
>>> Both use cases can be supported using existing RFC=E2=80=99s.
>>>=20
>>> Hemant
>>>=20
>>>=20
>>>=20
>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>> Sent: Tuesday, March 31, 2015 9:52 PM
>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf=
.org
>>> Subject: Re: RA Option Guidelines
>>>=20
>>> Hi Hemant,
>>>=20
>>>=20
>>> ________________________________
>>>=20
>>> From:Hemant Singh (shemant) <shemant@cisco.com>
>>> To: "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@y=
ahoo.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <i=
pv6@ietf.org>=20
>>> Sent: Wednesday, 1 April 2015, 1:27
>>> Subject: RE: RA Option Guidelines
>>>=20
>>> Barbara,
>>>=20
>>> Thanks for replying.=C2=A0 =C2=A0=20
>>>=20
>>> Mark,
>>>=20
>>> If new DHCPv6 options are added to be supported by RFC3736, then the SP=
 includes the new option in the DHCPv6 responses to the CPE WAN.=C2=A0 Then=
 the CPE includes the new option to its LAN DHCPv6 clients.
>>>=20
>>> /=C2=A0 So here is a scenario.
>>>=20
>>> / As an ISP, my customers have VoIP handsets that might support the OPT=
ION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, beca=
use they've bought those VoIP handsets from me). How long is it going to ta=
ke for me to get that option added to
> an updated RFC3736 and RFC7084, to get my CPE vendor to update and releas=
e their firmware to support that option, and test that new CPE firmware and=
 then to deploy that new firmware?
>>>=20
>>> / I think I'd be lucky if it only took 2 years.
>>>=20
>>> / A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZO=
NE to my customers if their hosts request it. So now I have to try to get O=
PTION_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor=
 to update and release their firmware
> to support that option, and test that new CPE firmware and then to deploy=
 that new firmware.
>>>=20
>>> / Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, =
so it is still "only" 2 years to get to a point where I could provide those=
 options to my customers. But what if that draft has progressed too far tho=
ugh the IETF publishing process? I have
> to create a new draft updating the to be published draft.
>>>=20
>>> / So, to achieve what should be a simple task of providing location or =
timezone information to customers' end hosts if they want it, we've just in=
curred the massive costs and time delays of the IETF publishing process, ve=
ndor firmware upgrades, firmware testing
> and firmware deployment. Sounds like how hard I understand it was to roll=
 out features like CLI in PSTN networks ...
>>>=20
>>> What is one option you'd like the host on the LAN to include so that we=
 can understand your use case better?=C2=A0=20
>>>=20
>>> / I'm going to make the problem much harder for you. I want the CPE to =
"support" or better, be transparent to, all current and future DHCPv6 optio=
ns, and I don't want to have to upgrade or ask my customers to successfully=
 upgrade their CPE each and every time
>>> there is a new DHCPv6 option defined that might be useful to me and the=
m. I want to be able to provide service parameters to my customers hosts, d=
irectly or indirectly, without the software revision or model of their CPE =
being the constraint.
>>>=20
>>> The SIP server is already included as one option supported by RFC3736.=
=C2=A0 Certainly, if the SIP server support is needed in the RA, I am open =
for it since the RA already includes DNS information.
>>>=20
>>> / I don't think DNS in RAs was a good idea, and neither were SIP option=
s when they were proposed. See that time consuming and service disrupting f=
irmware upgrade cycle for new DHCPv6 options? Same problem if you use RA op=
tions to achieve the same goal. New
> firmware upgrade each time you want to support a new RA option.
>>>=20
>>> / Duplication between RA options and DHCPv6 options also causes more pr=
oblems. Which is preferred? Are they treated equally or does one take prece=
dence over the other? As far as I'm aware, these questions haven't been ans=
wered for the DHCPv6 DNS and RA DNS
> options yet. It might be simple to come up with a simple rule for more DH=
CPv6 options are duplicated into RAs, however their might be some specific =
cases where the RA option value should be preferred over the DHCPv6 equival=
ent option and vice-versa.=20
>>>=20
>>> However, I still ask the question as to how an RA received at the WAN o=
f the CPE has its options propagated to the RA on the LAN?=C2=A0 At the tim=
e of writing RFC 6204 or RFC 7084, there is no such provision between the R=
A received on the WAN and the RA issued on
> the LAN of the CE router.
>>>=20
>>> / Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6=
 options that are unknown by the CPE will pass right through it transparent=
ly. The only complication is when stateful DHCPv6 addressing is used on the=
 CPE LAN interface, and I suggested
> a hybrid mode of operation for a DHCPv6 server in that draft which I thin=
k solves that problem.
>>>=20
>>> Others,
>>>=20
>>> Also, why does one need an RA Option Guideline?=C2=A0 RFC4861 specifies=
 a TLV format and an option Type.=C2=A0 I don't see anything else needed if=
 I need to specify a new RA option.=20
>>>=20
>>> Thanks,
>>>=20
>>> Hemant
>>>=20
>>> -----Original Message-----
>>> From: STARK, BARBARA H [mailto:bs7652@att.com]=20
>>> Sent: Tuesday, March 31, 2015 9:25 AM
>>> To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.o=
rg
>>> Subject: RE: RA Option Guidelines
>>>=20
>>>=20
>>>=20
>>>=20
>>> RFC 7084 already says:=20
>>> L-12:=C2=A0 The IPv6 CE router SHOULD make available a subset of DHCPv6
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 options (as listed in Section 5.3 of [RFC373=
6]) received from
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 the DHCPv6 client on its WAN interface to it=
s LAN-side DHCPv6
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 server.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

  
------=_Part_32928_1181099829.1428122044583
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div id=3D"yui_3_16_0_1_14281204=
09298_5500" dir=3D"ltr"><span>Hi Bernie,</span></div><br>  <div style=3D"fo=
nt-family: Helvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helv=
etica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id=3D"yui_3_16_0=
_1_1428120409298_4116"> <div style=3D"font-family: HelveticaNeue, Helvetica=
 Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id=3D=
"yui_3_16_0_1_1428120409298_4115"> <div dir=3D"ltr" id=3D"yui_3_16_0_1_1428=
120409298_4114"> <hr size=3D"1" id=3D"yui_3_16_0_1_1428120409298_5499">  <f=
ont size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_1_1428120409298_4113"> <b><s=
pan style=3D"font-weight:bold;">From:</span></b> Bernie Volz (volz) &lt;vol=
z@cisco.com&gt;<br> <b><span style=3D"font-weight: bold;">To:</span></b> Ma=
rk ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt; <br><b><span style=3D"font-w=
eight: bold;">Cc:</span></b> Hemant Singh (shemant) &lt;shemant@cisco.com&g=
t;; Brian Haberman &lt;brian@innovationslab.net&gt;; Ted Lemon &lt;Ted.Lemo=
n@nominum.com&gt;; "ipv6@ietf.org" &lt;ipv6@ietf.org&gt;; Ralph Droms (rdro=
ms) &lt;rdroms@cisco.com&gt; <br> <b><span style=3D"font-weight: bold;">Sen=
t:</span></b> Saturday, 4 April 2015, 14:25<br> <b><span style=3D"font-weig=
ht: bold;">Subject:</span></b> Re: RA Option Guidelines<br> </font> </div> =
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>Y=
es, in that situation the CE would not have requested the option from the I=
SP. You would need to update firmware on CE.</div><div class=3D"y_msg_conta=
iner" id=3D"yui_3_16_0_1_1428120409298_4118"><br></div><div class=3D"y_msg_=
container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=3D"ltr">/ Thank you f=
or confirming that.</div><div class=3D"y_msg_container" id=3D"yui_3_16_0_1_=
1428120409298_4118"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16=
_0_1_1428120409298_4118" dir=3D"ltr">/ Having to update firmware on the CE =
is the exact situation I think should be avoided.</div><div class=3D"y_msg_=
container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=3D"ltr"><br></div><di=
v class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=3D"l=
tr">/ If CE devices have to be upgraded to deploy new applications and serv=
ices (and I think 'deployment' includes automated configuration of them), t=
hen in my opinion Internet (application) transparency has been lost.</div><=
div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br cl=
ear=3D"none"><br clear=3D"none">As new options get assigned, clients &amp; =
servers need to be updated to make use of them.</div><div class=3D"y_msg_co=
ntainer" id=3D"yui_3_16_0_1_1428120409298_4118"><br></div><div class=3D"y_m=
sg_container" id=3D"yui_3_16_0_1_1428120409298_4118">/ If the CE device is =
DHCPv6 option transparent (i.e., is running a LAN DHCPv6 relay), then upgra=
des are only required to the hosts that want to use the new DHCPv6 options,=
 which is much less disruptive than also requiring CE firmware upgrades.<br=
 clear=3D"none"><br clear=3D"none">You could also provide some CE configura=
tion to request and save arbitary options, but that only is useful to exper=
t CE users and probably has security issues.</div><div class=3D"y_msg_conta=
iner" id=3D"yui_3_16_0_1_1428120409298_4118"><br></div><div class=3D"y_msg_=
container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=3D"ltr">/ Agree, not =
practical for typical residential users.</div><div class=3D"y_msg_container=
" id=3D"yui_3_16_0_1_1428120409298_4118"><br></div><div class=3D"y_msg_cont=
ainer" id=3D"yui_3_16_0_1_1428120409298_4118">/ Regards,</div><div class=3D=
"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118">/ Mark.<br clear=
=3D"none"><br clear=3D"none">- Bernie (from iPad)<br clear=3D"none"><div cl=
ass=3D"qtdSeparateBR"><br><br></div><div class=3D"yqt6274444161" id=3D"yqtf=
d18973"><br clear=3D"none">&gt; On Apr 3, 2015, at 9:41 PM, Mark ZZZ Smith =
&lt;<a shape=3D"rect" ymailto=3D"mailto:markzzzsmith@yahoo.com.au" href=3D"=
mailto:markzzzsmith@yahoo.com.au">markzzzsmith@yahoo.com.au</a>&gt; wrote:<=
br clear=3D"none">&gt; <br clear=3D"none">&gt; I don't think it is.<br clea=
r=3D"none">&gt; <br clear=3D"none">&gt; Can this ever work, because this is=
 the scenario I'm talking about:<br clear=3D"none">&gt; <br clear=3D"none">=
&gt; (LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) &lt;-&gt; (CE: !DHCPV6_N=
EW_OPTION1, so no ORO for it) &lt;-&gt; (ISP: DHCPV6_NEW_OPTION1)<br clear=
=3D"none">&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt; Is a combine=
d DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unknown* DHCPv6 opti=
on transparent, like a DHCPv6 relay is? I think the answer is no based on w=
hat Bernie said.<br clear=3D"none">&gt; <br clear=3D"none">&gt; ___________=
_____________________<br clear=3D"none">&gt; From: Hemant Singh (shemant) &=
lt;<a shape=3D"rect" ymailto=3D"mailto:shemant@cisco.com" href=3D"mailto:sh=
emant@cisco.com">shemant@cisco.com</a>&gt;<br clear=3D"none">&gt; To: Berni=
e Volz (volz) &lt;<a shape=3D"rect" ymailto=3D"mailto:volz@cisco.com" href=
=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt; <br clear=3D"none">&gt; C=
c: Mark ZZZ Smith &lt;<a shape=3D"rect" ymailto=3D"mailto:markzzzsmith@yaho=
o.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">markzzzsmith@yahoo.com.=
au</a>&gt;; "STARK, BARBARA H" &lt;<a shape=3D"rect" ymailto=3D"mailto:bs76=
52@att.com" href=3D"mailto:bs7652@att.com">bs7652@att.com</a>&gt;; Brian Ha=
berman &lt;<a shape=3D"rect" ymailto=3D"mailto:brian@innovationslab.net" hr=
ef=3D"mailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;; "<=
a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.=
org">ipv6@ietf.org</a>" &lt;<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.o=
rg" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;; Ralph Droms (rdrom=
s) &lt;<a shape=3D"rect" ymailto=3D"mailto:rdroms@cisco.com" href=3D"mailto=
:rdroms@cisco.com">rdroms@cisco.com</a>&gt;; Ted Lemon &lt;<a shape=3D"rect=
" ymailto=3D"mailto:Ted.Lemon@nominum.com" href=3D"mailto:Ted.Lemon@nominum=
.com">Ted.Lemon@nominum.com</a>&gt; <br clear=3D"none">&gt; Sent: Friday, 3=
 April 2015, 23:28<br clear=3D"none">&gt; Subject: RE: RA Option Guidelines=
<br clear=3D"none">&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt; <br=
 clear=3D"none">&gt; Bernie,<br clear=3D"none">&gt; <br clear=3D"none">&gt;=
 Got it =E2=80=93 thanks much!&nbsp; So the CE router implementation has to=
 change to be configurable to include a new DHCPv6 option in the ORO for th=
e WAN interface.&nbsp; Once the new option is returned by the server, the C=
E uses the new option for stateless DHCPv6 services on the LAN.&nbsp; Note,=
 it is the same service provider who has configured the CE for the new DHCP=
v6 option and thus the same service provider also provisions the DHCPv6 ser=
ver to return the new option, if asked for.&nbsp; There is no need for DHCP=
v6 relay in the CE for this new option support.&nbsp; <br clear=3D"none">&g=
t; <br clear=3D"none">&gt; In summary, both Mark=E2=80=99s and Barbara=E2=
=80=99s goals are met.<br clear=3D"none">&gt; <br clear=3D"none">&gt; Thank=
s,<br clear=3D"none">&gt; <br clear=3D"none">&gt; Hemant<br clear=3D"none">=
&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt=
; From:Bernie Volz (volz) <br clear=3D"none">&gt; Sent: Friday, April 03, 2=
015 7:48 AM<br clear=3D"none">&gt; To: Hemant Singh (shemant)<br clear=3D"n=
one">&gt; Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a shape=3D=
"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@=
ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br clear=3D"none">&gt; Subjec=
t: Re: RA Option Guidelines<br clear=3D"none">&gt; <br clear=3D"none">&gt; =
All options MUST be in ORO for server to return (there are some "protocol" =
options, such as client-id and server-id that are NOT supposed to be in ORO=
). So client controls the options it gets. So #1 is not true (some servers,=
 such as CPNR, can be configured to return options the client did not reque=
st, but generally that is useless since the client will most likely ignore =
it).<br clear=3D"none">&gt; <br clear=3D"none">&gt; #2 is normal DHCP opera=
tion.<br clear=3D"none">&gt; <br clear=3D"none">&gt; Note that while I thin=
k you were discussing stateless, it is true for stateful and stateless dhcp=
.<br clear=3D"none">&gt; <br clear=3D"none">&gt; - Bernie (from iPad)<br cl=
ear=3D"none">&gt; <br clear=3D"none">&gt;&gt; On Apr 3, 2015, at 7:43 AM, H=
emant Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"mailto:shemant@cisco=
.com" href=3D"mailto:shemant@cisco.com">shemant@cisco.com</a>&gt; wrote:<br=
 clear=3D"none">&gt;&gt; Bernie,<br clear=3D"none">&gt;&gt; <br clear=3D"no=
ne">&gt;&gt; Appreciate the quick reply.&nbsp; Let me summarize the issues =
and then you can clarify.<br clear=3D"none">&gt;&gt; <br clear=3D"none">&gt=
;&gt; 1.&nbsp; &nbsp;  The CE WAN interface does not include a new option i=
n DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the server.&nbsp; =
If the server is configured to return the DHCPV6_NEW_OPTION1 to clients, th=
en will the server reply with DHCPV6_NEW_OPTION1 even when the client did n=
ot request the option in the ORO?&nbsp;  In this scenario, no code changes =
on the CE, and just the server configuration takes care of the issue.<br cl=
ear=3D"none">&gt;&gt; 2.&nbsp; &nbsp;  The CE WAN interface does include a =
new option in DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the se=
rver.&nbsp; If the server is configured to return DHCPV6_NEW_OPTION1 to cli=
ents, then will the server reply with DHCPV6_NEW_OPTION1?<br clear=3D"none"=
>&gt;&gt; <br clear=3D"none">&gt;&gt; Mark,<br clear=3D"none">&gt;&gt; <br =
clear=3D"none">&gt;&gt; Note Bernie agrees with how I and Wes Beebee (who I=
 discussed this thread with) also interpreted RFC3736.&nbsp; New options ca=
n be served by the stateless DHCPv6 server without revising RFC3736.<br cle=
ar=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt; Thanks all,<br clear=3D"no=
ne">&gt;&gt; <br clear=3D"none">&gt;&gt; Hemant<br clear=3D"none">&gt;&gt; =
<br clear=3D"none">&gt;&gt; From:Bernie Volz (volz) <br clear=3D"none">&gt;=
&gt; Sent: Friday, April 03, 2015 7:33 AM<br clear=3D"none">&gt;&gt; To: He=
mant Singh (shemant)<br clear=3D"none">&gt;&gt; Cc: Mark ZZZ Smith; STARK, =
BARBARA H; Brian Haberman; <a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.or=
g" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>; Ralph Droms (rdroms); T=
ed Lemon<br clear=3D"none">&gt;&gt; Subject: Re: RA Option Guidelines<br cl=
ear=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt; I didn't study the comple=
te thread but I am sure everyone would understand that new options should b=
e allowed to be requested. The ORO list cannot be frozen ... At the time th=
e rfc was written, that was the list. But new option documents are not requ=
ired to update RFC3736.<br clear=3D"none">&gt;&gt; <br clear=3D"none">&gt;&=
gt; There are no interop issues either as if either side (client or server)=
 doesn't know of an option, it just doesn't include or ignores it.<br clear=
=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt; - Bernie (from iPad)<br clea=
r=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; On Apr 3, 2015, at 7:09=
 AM, Hemant Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"mailto:shemant=
@cisco.com" href=3D"mailto:shemant@cisco.com">shemant@cisco.com</a>&gt; wro=
te:<br clear=3D"none">&gt;&gt;&gt; Could the DHCPv6 gurus in Ralph, Bernie,=
 and Ted please help resolve this thread for stateless DHCPv6 current vs. f=
uture options and the ORO option. <br clear=3D"none">&gt;&gt;&gt; <br clear=
=3D"none">&gt;&gt;&gt; Thanks,<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"=
none">&gt;&gt;&gt; Hemant<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none"=
>&gt;&gt;&gt; From:Mark ZZZ Smith [mailto:<a shape=3D"rect" ymailto=3D"mail=
to:markzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">mar=
kzzzsmith@yahoo.com.au</a>] <br clear=3D"none">&gt;&gt;&gt; Sent: Thursday,=
 April 02, 2015 10:19 PM<br clear=3D"none">&gt;&gt;&gt; To: Hemant Singh (s=
hemant); STARK, BARBARA H; Brian Haberman; <a shape=3D"rect" ymailto=3D"mai=
lto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br clear=
=3D"none">&gt;&gt;&gt; Subject: Re: RA Option Guidelines<br clear=3D"none">=
&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; Hi Hemant,<br clear=3D"none">&=
gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt;=
 ________________________________<br clear=3D"none">&gt;&gt;&gt; From: Hema=
nt Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"mailto:shemant@cisco.co=
m" href=3D"mailto:shemant@cisco.com">shemant@cisco.com</a>&gt;<br clear=3D"=
none">&gt;&gt;&gt; To: Mark ZZZ Smith &lt;<a shape=3D"rect" ymailto=3D"mail=
to:markzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">mar=
kzzzsmith@yahoo.com.au</a>&gt;; "STARK, BARBARA H" &lt;<a shape=3D"rect" ym=
ailto=3D"mailto:bs7652@att.com" href=3D"mailto:bs7652@att.com">bs7652@att.c=
om</a>&gt;; Brian Haberman &lt;<a shape=3D"rect" ymailto=3D"mailto:brian@in=
novationslab.net" href=3D"mailto:brian@innovationslab.net">brian@innovation=
slab.net</a>&gt;; "<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>" &lt;<a shape=3D"rect" ymailto=
=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&g=
t; <br clear=3D"none">&gt;&gt;&gt; Sent: Friday, 3 April 2015, 6:07<br clea=
r=3D"none">&gt;&gt;&gt; Subject: RE: RA Option Guidelines<br clear=3D"none"=
>&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&g=
t; <br clear=3D"none">&gt;&gt;&gt; Mark,<br clear=3D"none">&gt;&gt;&gt; <br=
 clear=3D"none">&gt;&gt;&gt; The stateless DHCPv6 server in RFC3736 allows =
for new options to be served by the stateless server.&nbsp;  Read the first=
 paragraph of section 5.3 in RFC3736.<br clear=3D"none">&gt;&gt;&gt; <br cl=
ear=3D"none">&gt;&gt;&gt; / So there are a few reasons why I wouldn't come =
to that conclusion without some very careful reading:<br clear=3D"none">&gt=
;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / - The explicitly identified set=
 of required and optional DHCPv6 options that can be supported by a statele=
ss DHCPv6 server<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;=
&gt; / - The lack of any overt discussion that this set of required and opt=
ional DHCPv6 options are a minimum, and that further DHCPv6 options could b=
e provided by a stateless DHCPv6 server if supported by the implementation,=
 are appropriate and requested by the<br clear=3D"none">&gt; client. It bei=
ng a minimum is subtly eluded to in a few sentences in the Abstract and the=
 Introduction, however I think they could easily be missed. I'd expect that=
 if this is the case, it is much clearer and obvious.<br clear=3D"none">&gt=
;&gt;&gt; / - I think text you refer to in 5.3, "Clients and servers use th=
e following options to pass configuration information to clients; note that=
 other options for configuration information may be specified in future Int=
ernet Standards:" reads to me like a later version of this RFC will specify=
 more stateless DHCPv6 server supported options. A statement such as "Other=
 additional DHCPv6 options appropriate for stateless DHCPv6 operation may b=
e supported by an implementation." would make it much clearer that the supp=
orted options were up to the implementer once the minimum had been implemen=
ted.<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / So if=
 I were implementing a stateless DHCPv6 server as per RFC3736, I'd think th=
e implementation was complete when I had implemented the options specified.=
 I wouldn't put any effort into making it also transparent to any options t=
hat weren't identified in RFC3736, as there is no text discussing that.<br =
clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; So the new opti=
ons you want to serve can be served by the CE stateless DHCPv6 server.&nbsp=
;  Now, if the service provider configures his/her DHCPv6 server to return =
new options to the CE WAN interface address acquisition, the CE uses the op=
tions on the LAN.&nbsp; See bullet L-12 of RFC 7084.&nbsp; Existing RFCs su=
pport your use case and no dhcpv6 relay is required in the CE.<br clear=3D"=
none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / I also cannot find tex=
t in RFC3315 or its updates on how to handle received options that were not=
 requested by the client in the Option Request Option. So if the CE WAN DHC=
Pv6 client doesn't request an option in its ORO to the SP's DHCPv6 server, =
I don't think it is possible for the CE to pass options it doesn't know abo=
ut onto the downstream LAN devices that do understand those DHCPv6 options.=
<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / If it is =
possible to send a DHCPv6 client "ORO type" options that it didn't request,=
 then the behaviour is still ambiguous. If the DHCPv6 client is a host, the=
n it would be quite reasonable and expected to silently ignore those receiv=
ed unknown options. However, if the DHCPv6 client is on the WAN side of a C=
E device, then those options should instead be passed to the LAN DHCPv6 ser=
ver, which presumably should know how to correctly handle options it doesn'=
t understand - in the specific CE case, remember those options in case a do=
wnstream LAN DHCPv6 client requests them. I think RFC7084 and it's ancestor=
 RFC6204 are the only RFCs which describe this combination of DHCPv6 client=
/server working together, and neither of them have discussed passing unknow=
n options from the DHCPv6 WAN client to the DHCPv6 LAN server.<br clear=3D"=
none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / Are you aware of any C=
E DHCPv6 WAN client/DHCPv6 LAN server implementations that are unknown DHCP=
v6 option transparent? Looking at RFC7084, this behaviour seems to be very =
explicitly prohibited, by limiting the LAN DHCPv6 server support to only th=
ose options described in RFC7084, or to those described in RFC3736.<br clea=
r=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / I think this leve=
l of DHCPv6 option transparency between CE LAN attached hosts and the upstr=
eam SP's DHCPv6 server(s) can only be achieved by using a DHCPv6 relay on t=
he CE LAN interface, because DHCPv6 relays are DHCPv6 option transparent. (=
A CE would still have a DHCPv6 client on its WAN interface for its own para=
meters and DHCPv6-PD prefixes).<br clear=3D"none">&gt;&gt;&gt; <br clear=3D=
"none">&gt;&gt;&gt; / Regards,<br clear=3D"none">&gt;&gt;&gt; / Mark.<br cl=
ear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none=
">&gt;&gt;&gt; Barbara,<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&=
gt;&gt;&gt; For your use case, the service provider configures the DHCPv6 s=
erver to only serve options specified in RFC 7084.&nbsp; Thus in this deplo=
yment no extra options exist to serve to the CE router LAN.<br clear=3D"non=
e">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; Both use cases can be suppo=
rted using existing RFC=E2=80=99s.<br clear=3D"none">&gt;&gt;&gt; <br clear=
=3D"none">&gt;&gt;&gt; Hemant<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"n=
one">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&g=
t;&gt; From:Mark ZZZ Smith [mailto:<a shape=3D"rect" ymailto=3D"mailto:mark=
zzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">markzzzsmi=
th@yahoo.com.au</a>] <br clear=3D"none">&gt;&gt;&gt; Sent: Tuesday, March 3=
1, 2015 9:52 PM<br clear=3D"none">&gt;&gt;&gt; To: Hemant Singh (shemant); =
STARK, BARBARA H; Brian Haberman; <a shape=3D"rect" ymailto=3D"mailto:ipv6@=
ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br clear=3D"none"=
>&gt;&gt;&gt; Subject: Re: RA Option Guidelines<br clear=3D"none">&gt;&gt;&=
gt; <br clear=3D"none">&gt;&gt;&gt; Hi Hemant,<br clear=3D"none">&gt;&gt;&g=
t; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; ________=
________________________<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">=
&gt;&gt;&gt; From:Hemant Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"m=
ailto:shemant@cisco.com" href=3D"mailto:shemant@cisco.com">shemant@cisco.co=
m</a>&gt;<br clear=3D"none">&gt;&gt;&gt; To: "STARK, BARBARA H" &lt;<a shap=
e=3D"rect" ymailto=3D"mailto:bs7652@att.com" href=3D"mailto:bs7652@att.com"=
>bs7652@att.com</a>&gt;; Mark ZZZ Smith &lt;<a shape=3D"rect" ymailto=3D"ma=
ilto:markzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">m=
arkzzzsmith@yahoo.com.au</a>&gt;; Brian Haberman &lt;<a shape=3D"rect" ymai=
lto=3D"mailto:brian@innovationslab.net" href=3D"mailto:brian@innovationslab=
.net">brian@innovationslab.net</a>&gt;; "<a shape=3D"rect" ymailto=3D"mailt=
o:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>" &lt;<a sh=
ape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org"=
>ipv6@ietf.org</a>&gt; <br clear=3D"none">&gt;&gt;&gt; Sent: Wednesday, 1 A=
pril 2015, 1:27<br clear=3D"none">&gt;&gt;&gt; Subject: RE: RA Option Guide=
lines<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; Barbar=
a,<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; Thanks fo=
r replying.&nbsp; &nbsp; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none"=
>&gt;&gt;&gt; Mark,<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&=
gt;&gt; If new DHCPv6 options are added to be supported by RFC3736, then th=
e SP includes the new option in the DHCPv6 responses to the CPE WAN.&nbsp; =
Then the CPE includes the new option to its LAN DHCPv6 clients.<br clear=3D=
"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; /&nbsp; So here is a sc=
enario.<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / As=
 an ISP, my customers have VoIP handsets that might support the OPTION_GEOL=
OCATION DHCPv6 option (I might know that a portion of them do, because they=
've bought those VoIP handsets from me). How long is it going to take for m=
e to get that option added to<br clear=3D"none">&gt; an updated RFC3736 and=
 RFC7084, to get my CPE vendor to update and release their firmware to supp=
ort that option, and test that new CPE firmware and then to deploy that new=
 firmware?<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; /=
 I think I'd be lucky if it only took 2 years.<br clear=3D"none">&gt;&gt;&g=
t; <br clear=3D"none">&gt;&gt;&gt; / A few months later I decide I want to =
provide OPTION_NEW_POSIX_TIMEZONE to my customers if their hosts request it=
. So now I have to try to get OPTION_NEW_POSIX_TIMEZONE added to the update=
d RFC3736, to get my CPE vendor to update and release their firmware<br cle=
ar=3D"none">&gt; to support that option, and test that new CPE firmware and=
 then to deploy that new firmware.<br clear=3D"none">&gt;&gt;&gt; <br clear=
=3D"none">&gt;&gt;&gt; / Now if I'm lucky I could add it to the draft for O=
PTION_GEOLOCATION, so it is still "only" 2 years to get to a point where I =
could provide those options to my customers. But what if that draft has pro=
gressed too far though the IETF publishing process? I have<br clear=3D"none=
">&gt; to create a new draft updating the to be published draft.<br clear=
=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / So, to achieve wha=
t should be a simple task of providing location or timezone information to =
customers' end hosts if they want it, we've just incurred the massive costs=
 and time delays of the IETF publishing process, vendor firmware upgrades, =
firmware testing<br clear=3D"none">&gt; and firmware deployment. Sounds lik=
e how hard I understand it was to roll out features like CLI in PSTN networ=
ks ...<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; What =
is one option you'd like the host on the LAN to include so that we can unde=
rstand your use case better?&nbsp; <br clear=3D"none">&gt;&gt;&gt; <br clea=
r=3D"none">&gt;&gt;&gt; / I'm going to make the problem much harder for you=
. I want the CPE to "support" or better, be transparent to, all current and=
 future DHCPv6 options, and I don't want to have to upgrade or ask my custo=
mers to successfully upgrade their CPE each and every time<br clear=3D"none=
">&gt;&gt;&gt; there is a new DHCPv6 option defined that might be useful to=
 me and them. I want to be able to provide service parameters to my custome=
rs hosts, directly or indirectly, without the software revision or model of=
 their CPE being the constraint.<br clear=3D"none">&gt;&gt;&gt; <br clear=
=3D"none">&gt;&gt;&gt; The SIP server is already included as one option sup=
ported by RFC3736.&nbsp; Certainly, if the SIP server support is needed in =
the RA, I am open for it since the RA already includes DNS information.<br =
clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; / I don't think=
 DNS in RAs was a good idea, and neither were SIP options when they were pr=
oposed. See that time consuming and service disrupting firmware upgrade cyc=
le for new DHCPv6 options? Same problem if you use RA options to achieve th=
e same goal. New<br clear=3D"none">&gt; firmware upgrade each time you want=
 to support a new RA option.<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"no=
ne">&gt;&gt;&gt; / Duplication between RA options and DHCPv6 options also c=
auses more problems. Which is preferred? Are they treated equally or does o=
ne take precedence over the other? As far as I'm aware, these questions hav=
en't been answered for the DHCPv6 DNS and RA DNS<br clear=3D"none">&gt; opt=
ions yet. It might be simple to come up with a simple rule for more DHCPv6 =
options are duplicated into RAs, however their might be some specific cases=
 where the RA option value should be preferred over the DHCPv6 equivalent o=
ption and vice-versa. <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&g=
t;&gt;&gt; However, I still ask the question as to how an RA received at th=
e WAN of the CPE has its options propagated to the RA on the LAN?&nbsp; At =
the time of writing RFC 6204 or RFC 7084, there is no such provision betwee=
n the RA received on the WAN and the RA issued on<br clear=3D"none">&gt; th=
e LAN of the CE router.<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&=
gt;&gt;&gt; / Use a DHCPv6 relay in the CPE. Then there isn't a problem, ne=
w DHCPv6 options that are unknown by the CPE will pass right through it tra=
nsparently. The only complication is when stateful DHCPv6 addressing is use=
d on the CPE LAN interface, and I suggested<br clear=3D"none">&gt; a hybrid=
 mode of operation for a DHCPv6 server in that draft which I think solves t=
hat problem.<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt;=
 Others,<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; Als=
o, why does one need an RA Option Guideline?&nbsp; RFC4861 specifies a TLV =
format and an option Type.&nbsp; I don't see anything else needed if I need=
 to specify a new RA option. <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"n=
one">&gt;&gt;&gt; Thanks,<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none"=
>&gt;&gt;&gt; Hemant<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;=
&gt;&gt; -----Original Message-----<br clear=3D"none">&gt;&gt;&gt; From: ST=
ARK, BARBARA H [mailto:<a shape=3D"rect" ymailto=3D"mailto:bs7652@att.com" =
href=3D"mailto:bs7652@att.com">bs7652@att.com</a>] <br clear=3D"none">&gt;&=
gt;&gt; Sent: Tuesday, March 31, 2015 9:25 AM<br clear=3D"none">&gt;&gt;&gt=
; To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a shape=3D"r=
ect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ie=
tf.org</a><br clear=3D"none">&gt;&gt;&gt; Subject: RE: RA Option Guidelines=
<br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; <br clear=
=3D"none">&gt;&gt;&gt; <br clear=3D"none">&gt;&gt;&gt; <br clear=3D"none">&=
gt;&gt;&gt; RFC 7084 already says: <br clear=3D"none">&gt;&gt;&gt; L-12:&nb=
sp; The IPv6 CE router SHOULD make available a subset of DHCPv6<br clear=3D=
"none">&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp;  options (as listed in Secti=
on 5.3 of [RFC3736]) received from<br clear=3D"none">&gt;&gt;&gt;&nbsp; &nb=
sp; &nbsp; &nbsp;  the DHCPv6 client on its WAN interface to its LAN-side D=
HCPv6<br clear=3D"none">&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp;  server.<br=
 clear=3D"none">&gt; <br clear=3D"none">&gt; ------------------------------=
--------------------------------------<br clear=3D"none">&gt; IETF IPv6 wor=
king group mailing list<br clear=3D"none">&gt; <a shape=3D"rect" ymailto=3D=
"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br c=
lear=3D"none">&gt; Administrative Requests: <a shape=3D"rect" href=3D"https=
://www.ietf.org/mailman/listinfo/ipv6" target=3D"_blank">https://www.ietf.o=
rg/mailman/listinfo/ipv6</a><br clear=3D"none">&gt; -----------------------=
---------------------------------------------</div><br><br></div> </div> </=
div>  </div></body></html>
------=_Part_32928_1181099829.1428122044583--


From nobody Sat Apr  4 02:00:11 2015
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CDD01B2A85 for <ipv6@ietfa.amsl.com>; Sat,  4 Apr 2015 02:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TiBnQ3vBTkel for <ipv6@ietfa.amsl.com>; Sat,  4 Apr 2015 02:00:08 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.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 5930F1B2A77 for <ipv6@ietf.org>; Sat,  4 Apr 2015 02:00:07 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  iface 141.3.10.81 id 1YeJvw-0008TB-Cz for <ipv6@ietf.org>; Sat, 04 Apr 2015 11:00:04 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id 170C4B0017E for <ipv6@ietf.org>; Sat,  4 Apr 2015 11:00:04 +0200 (CEST)
Message-ID: <551FA813.4040805@kit.edu>
Date: Sat, 04 Apr 2015 11:00:03 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: RA Option Guidelines
References: <5515A9A7.3080508@innovationslab.net> <281018849.2116525.1427767749309.JavaMail.yahoo@mail.yahoo.com> <75B6FA9F576969419E42BECB86CB1B8916834620@xmb-rcd-x06.cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F8C7AF@GAALPA1MSGUSRBF.ITServices.sbc.com> <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <551AF4E5.7000207@gmail.com> <551EE710.2050301@gmail.com> <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
In-Reply-To: <95018337-F7BA-48C5-81CF-3B2F8987F698@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1428138004.
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/B1880MHqV6XYuZzND2q6D_w5YiM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 09:00:10 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 03.04.2015 at 22:18 Ole Troan wrote:
>> Do we actually agree on this, or rather on a slightly expanded
>> version:
>> 
>> RA options should be limited to link-local/subnet specific
>> parameters (i.e., layer 3 parameters only) necessary for a simple
>> unmanaged network. The only exception is RFC 6106 (DNS
>> Configuration). More complex situations are better handled by
>> other configuration metods such as DHCPv6.
> 
> I agree only with this part: “RA options should be limited to
> link-local/subnet specific parameters (i.e. layer 3 parameters
> only). The only exception is RFC6106 (DNS Configuration).”
> 
> RA’s aren’t unmanaged. they certainly don’t require the network to
> be simple. there was a thread on the DHC list a while back
> appearing to reach the conclusion that DHCP should only be used to
> configure the network layer (although there are many exceptions). 
> the main difference between RA and DHCP is that one is per subnet,
> the other per host.

+1

Regards,
 Roland

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlUfqBMACgkQ1YyfLd659kdyjwCgzkWVaeaGBt3vZ01/ImUiv53y
y48AoMN3y603oXLlxvHOKvHazKvFV5uu
=hFoI
-----END PGP SIGNATURE-----


From nobody Sat Apr  4 05:05:15 2015
Return-Path: <volz@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 646B41A8889 for <ipv6@ietfa.amsl.com>; Sat,  4 Apr 2015 05:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hO2wvYXff9Ht for <ipv6@ietfa.amsl.com>; Sat,  4 Apr 2015 05:05:08 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D239D1A887C for <ipv6@ietf.org>; Sat,  4 Apr 2015 05:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=50797; q=dns/txt; s=iport; t=1428149108; x=1429358708; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=McSjklWLyJUkQrJ2h864NKjz5i10qyY7CUlZ8It1+Rk=; b=drlDeFdpMVuMsAI7kE4W7zDUUnJhCWuO8OHPplErfZUbn7PUItkwSXF1 DOpgfb1zFqqs3VxctotySwtLY4axZi8awYqZwcBEwxIGdmRDX4q+xtu8S IGPEIKKD673H2dpw1yi/iXSkpdzC/wgidqMmyr1YcxGieIsmf4MNOwVjS E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DfBwAf0h9V/40NJK1cgkVDUlzFVBkBC4Ixg0oCgR9MAQEBAQEBfoQeAQEBAwEBAQEXAQxEAwsFBwQCAQgRBAEBASABBgcnCxQJCAIEDgUJiBIDCQgNzCABAQEBAQEBAQEBAQEBAQEBAQEBAQEXiymCR4FnCRchCgYBAgSDEYEWBYFMg0QKgQSCcodbiDuBR4EdgzWCY4YfT4Jpg0giggMcgVBvAYEDgT8BAQE
X-IronPort-AV: E=Sophos;i="5.11,522,1422921600";  d="scan'208,217";a="409513017"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-2.cisco.com with ESMTP; 04 Apr 2015 12:05:06 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t34C55fp031041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 4 Apr 2015 12:05:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Sat, 4 Apr 2015 07:05:04 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: RA Option Guidelines
Thread-Topic: RA Option Guidelines
Thread-Index: AQHQaKQlnXXmv757w0ecSSL/v887950xBCKAgAUtv4CAAGHRsIAAWuGA//+45SCAARfwgIACXRswgADPJQCAAD99sIAAB4TagABWoID//62BWIAAXxoAgADdcQD//8lI5gAM4q4AAAVGCno=
Date: Sat, 4 Apr 2015 12:05:04 +0000
Message-ID: <147FEEB9-096A-4A67-A351-9B7A59D3172E@cisco.com>
References: <C9212BE0-A9D1-4AC8-8886-2B4A5CA858A0@cisco.com>, <630957669.32929.1428122044593.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <630957669.32929.1428122044593.JavaMail.yahoo@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_147FEEB9096A4A67A3519B7A59D3172Eciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/uekbbHRHK1LFFA4HZyXDP0fFdJY>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 12:05:14 -0000

--_000_147FEEB9096A4A67A3519B7A59D3172Eciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Why is thus such a big deal? The same has been the case for v4 all along an=
d has not been an issue. There are reasons to upgrade CE or the firmware pe=
riodically, i.e. security and new features. New options aren't added that f=
requently and those that have been recently are for softwire and for option=
s that your home computer, phone, or tablet doesn't generally need.

See http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xht=
ml.

- Bernie (from iPad)

On Apr 4, 2015, at 12:34 AM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mail=
to:markzzzsmith@yahoo.com.au>> wrote:

Hi Bernie,

________________________________
From: Bernie Volz (volz) <volz@cisco.com<mailto:volz@cisco.com>>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com=
.au>>
Cc: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>>; B=
rian Haberman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; =
Ted Lemon <Ted.Lemon@nominum.com<mailto:Ted.Lemon@nominum.com>>; "ipv6@ietf=
.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>; Ralph Dr=
oms (rdroms) <rdroms@cisco.com<mailto:rdroms@cisco.com>>
Sent: Saturday, 4 April 2015, 14:25
Subject: Re: RA Option Guidelines

Yes, in that situation the CE would not have requested the option from the =
ISP. You would need to update firmware on CE.

/ Thank you for confirming that.

/ Having to update firmware on the CE is the exact situation I think should=
 be avoided.

/ If CE devices have to be upgraded to deploy new applications and services=
 (and I think 'deployment' includes automated configuration of them), then =
in my opinion Internet (application) transparency has been lost.


As new options get assigned, clients & servers need to be updated to make u=
se of them.

/ If the CE device is DHCPv6 option transparent (i.e., is running a LAN DHC=
Pv6 relay), then upgrades are only required to the hosts that want to use t=
he new DHCPv6 options, which is much less disruptive than also requiring CE=
 firmware upgrades.

You could also provide some CE configuration to request and save arbitary o=
ptions, but that only is useful to expert CE users and probably has securit=
y issues.

/ Agree, not practical for typical residential users.

/ Regards,
/ Mark.

- Bernie (from iPad)



> On Apr 3, 2015, at 9:41 PM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mai=
lto:markzzzsmith@yahoo.com.au>> wrote:
>
> I don't think it is.
>
> Can this ever work, because this is the scenario I'm talking about:
>
> (LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) <-> (CE: !DHCPV6_NEW_OPTION=
1, so no ORO for it) <-> (ISP: DHCPV6_NEW_OPTION1)
>
>
> Is a combined DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unknow=
n* DHCPv6 option transparent, like a DHCPv6 relay is? I think the answer is=
 no based on what Bernie said.
>
> ________________________________
> From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com>=
>
> To: Bernie Volz (volz) <volz@cisco.com<mailto:volz@cisco.com>>
> Cc: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.c=
om.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Brian =
Haberman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ipv6=
@ietf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>; Ral=
ph Droms (rdroms) <rdroms@cisco.com<mailto:rdroms@cisco.com>>; Ted Lemon <T=
ed.Lemon@nominum.com<mailto:Ted.Lemon@nominum.com>>
> Sent: Friday, 3 April 2015, 23:28
> Subject: RE: RA Option Guidelines
>
>
>
> Bernie,
>
> Got it =96 thanks much!  So the CE router implementation has to change to=
 be configurable to include a new DHCPv6 option in the ORO for the WAN inte=
rface.  Once the new option is returned by the server, the CE uses the new =
option for stateless DHCPv6 services on the LAN.  Note, it is the same serv=
ice provider who has configured the CE for the new DHCPv6 option and thus t=
he same service provider also provisions the DHCPv6 server to return the ne=
w option, if asked for.  There is no need for DHCPv6 relay in the CE for th=
is new option support.
>
> In summary, both Mark=92s and Barbara=92s goals are met.
>
> Thanks,
>
> Hemant
>
>
>
> From:Bernie Volz (volz)
> Sent: Friday, April 03, 2015 7:48 AM
> To: Hemant Singh (shemant)
> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mailt=
o:ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
> Subject: Re: RA Option Guidelines
>
> All options MUST be in ORO for server to return (there are some "protocol=
" options, such as client-id and server-id that are NOT supposed to be in O=
RO). So client controls the options it gets. So #1 is not true (some server=
s, such as CPNR, can be configured to return options the client did not req=
uest, but generally that is useless since the client will most likely ignor=
e it).
>
> #2 is normal DHCP operation.
>
> Note that while I think you were discussing stateless, it is true for sta=
teful and stateless dhcp.
>
> - Bernie (from iPad)
>
>> On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com<ma=
ilto:shemant@cisco.com>> wrote:
>> Bernie,
>>
>> Appreciate the quick reply.  Let me summarize the issues and then you ca=
n clarify.
>>
>> 1.    The CE WAN interface does not include a new option in DHCPV6_NEW_O=
PTION1 in the ORO option of the SOLICIT to the server.  If the server is co=
nfigured to return the DHCPV6_NEW_OPTION1 to clients, then will the server =
reply with DHCPV6_NEW_OPTION1 even when the client did not request the opti=
on in the ORO?  In this scenario, no code changes on the CE, and just the s=
erver configuration takes care of the issue.
>> 2.    The CE WAN interface does include a new option in DHCPV6_NEW_OPTIO=
N1 in the ORO option of the SOLICIT to the server.  If the server is config=
ured to return DHCPV6_NEW_OPTION1 to clients, then will the server reply wi=
th DHCPV6_NEW_OPTION1?
>>
>> Mark,
>>
>> Note Bernie agrees with how I and Wes Beebee (who I discussed this threa=
d with) also interpreted RFC3736.  New options can be served by the statele=
ss DHCPv6 server without revising RFC3736.
>>
>> Thanks all,
>>
>> Hemant
>>
>> From:Bernie Volz (volz)
>> Sent: Friday, April 03, 2015 7:33 AM
>> To: Hemant Singh (shemant)
>> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org<mail=
to:ipv6@ietf.org>; Ralph Droms (rdroms); Ted Lemon
>> Subject: Re: RA Option Guidelines
>>
>> I didn't study the complete thread but I am sure everyone would understa=
nd that new options should be allowed to be requested. The ORO list cannot =
be frozen ... At the time the rfc was written, that was the list. But new o=
ption documents are not required to update RFC3736.
>>
>> There are no interop issues either as if either side (client or server) =
doesn't know of an option, it just doesn't include or ignores it.
>>
>> - Bernie (from iPad)
>>
>>> On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com<m=
ailto:shemant@cisco.com>> wrote:
>>> Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve th=
is thread for stateless DHCPv6 current vs. future options and the ORO optio=
n.
>>>
>>> Thanks,
>>>
>>> Hemant
>>>
>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au<mailto:markzzzsmi=
th@yahoo.com.au>]
>>> Sent: Thursday, April 02, 2015 10:19 PM
>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf=
.org<mailto:ipv6@ietf.org>
>>> Subject: Re: RA Option Guidelines
>>>
>>> Hi Hemant,
>>>
>>>
>>> ________________________________
>>> From: Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.co=
m>>
>>> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo=
.com.au>>; "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Bria=
n Haberman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ip=
v6@ietf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
>>> Sent: Friday, 3 April 2015, 6:07
>>> Subject: RE: RA Option Guidelines
>>>
>>>
>>>
>>> Mark,
>>>
>>> The stateless DHCPv6 server in RFC3736 allows for new options to be ser=
ved by the stateless server.  Read the first paragraph of section 5.3 in RF=
C3736.
>>>
>>> / So there are a few reasons why I wouldn't come to that conclusion wit=
hout some very careful reading:
>>>
>>> / - The explicitly identified set of required and optional DHCPv6 optio=
ns that can be supported by a stateless DHCPv6 server
>>>
>>> / - The lack of any overt discussion that this set of required and opti=
onal DHCPv6 options are a minimum, and that further DHCPv6 options could be=
 provided by a stateless DHCPv6 server if supported by the implementation, =
are appropriate and requested by the
> client. It being a minimum is subtly eluded to in a few sentences in the =
Abstract and the Introduction, however I think they could easily be missed.=
 I'd expect that if this is the case, it is much clearer and obvious.
>>> / - I think text you refer to in 5.3, "Clients and servers use the foll=
owing options to pass configuration information to clients; note that other=
 options for configuration information may be specified in future Internet =
Standards:" reads to me like a later version of this RFC will specify more =
stateless DHCPv6 server supported options. A statement such as "Other addit=
ional DHCPv6 options appropriate for stateless DHCPv6 operation may be supp=
orted by an implementation." would make it much clearer that the supported =
options were up to the implementer once the minimum had been implemented.
>>>
>>> / So if I were implementing a stateless DHCPv6 server as per RFC3736, I=
'd think the implementation was complete when I had implemented the options=
 specified. I wouldn't put any effort into making it also transparent to an=
y options that weren't identified in RFC3736, as there is no text discussin=
g that.
>>>
>>> So the new options you want to serve can be served by the CE stateless =
DHCPv6 server.  Now, if the service provider configures his/her DHCPv6 serv=
er to return new options to the CE WAN interface address acquisition, the C=
E uses the options on the LAN.  See bullet L-12 of RFC 7084.  Existing RFCs=
 support your use case and no dhcpv6 relay is required in the CE.
>>>
>>> / I also cannot find text in RFC3315 or its updates on how to handle re=
ceived options that were not requested by the client in the Option Request =
Option. So if the CE WAN DHCPv6 client doesn't request an option in its ORO=
 to the SP's DHCPv6 server, I don't think it is possible for the CE to pass=
 options it doesn't know about onto the downstream LAN devices that do unde=
rstand those DHCPv6 options.
>>>
>>> / If it is possible to send a DHCPv6 client "ORO type" options that it =
didn't request, then the behaviour is still ambiguous. If the DHCPv6 client=
 is a host, then it would be quite reasonable and expected to silently igno=
re those received unknown options. However, if the DHCPv6 client is on the =
WAN side of a CE device, then those options should instead be passed to the=
 LAN DHCPv6 server, which presumably should know how to correctly handle op=
tions it doesn't understand - in the specific CE case, remember those optio=
ns in case a downstream LAN DHCPv6 client requests them. I think RFC7084 an=
d it's ancestor RFC6204 are the only RFCs which describe this combination o=
f DHCPv6 client/server working together, and neither of them have discussed=
 passing unknown options from the DHCPv6 WAN client to the DHCPv6 LAN serve=
r.
>>>
>>> / Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implement=
ations that are unknown DHCPv6 option transparent? Looking at RFC7084, this=
 behaviour seems to be very explicitly prohibited, by limiting the LAN DHCP=
v6 server support to only those options described in RFC7084, or to those d=
escribed in RFC3736.
>>>
>>> / I think this level of DHCPv6 option transparency between CE LAN attac=
hed hosts and the upstream SP's DHCPv6 server(s) can only be achieved by us=
ing a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCPv=
6 option transparent. (A CE would still have a DHCPv6 client on its WAN int=
erface for its own parameters and DHCPv6-PD prefixes).
>>>
>>> / Regards,
>>> / Mark.
>>>
>>>
>>> Barbara,
>>>
>>> For your use case, the service provider configures the DHCPv6 server to=
 only serve options specified in RFC 7084.  Thus in this deployment no extr=
a options exist to serve to the CE router LAN.
>>>
>>> Both use cases can be supported using existing RFC=92s.
>>>
>>> Hemant
>>>
>>>
>>>
>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au<mailto:markzzzsmi=
th@yahoo.com.au>]
>>> Sent: Tuesday, March 31, 2015 9:52 PM
>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@ietf=
.org<mailto:ipv6@ietf.org>
>>> Subject: Re: RA Option Guidelines
>>>
>>> Hi Hemant,
>>>
>>>
>>> ________________________________
>>>
>>> From:Hemant Singh (shemant) <shemant@cisco.com<mailto:shemant@cisco.com=
>>
>>> To: "STARK, BARBARA H" <bs7652@att.com<mailto:bs7652@att.com>>; Mark ZZ=
Z Smith <markzzzsmith@yahoo.com.au<mailto:markzzzsmith@yahoo.com.au>>; Bria=
n Haberman <brian@innovationslab.net<mailto:brian@innovationslab.net>>; "ip=
v6@ietf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
>>> Sent: Wednesday, 1 April 2015, 1:27
>>> Subject: RE: RA Option Guidelines
>>>
>>> Barbara,
>>>
>>> Thanks for replying.
>>>
>>> Mark,
>>>
>>> If new DHCPv6 options are added to be supported by RFC3736, then the SP=
 includes the new option in the DHCPv6 responses to the CPE WAN.  Then the =
CPE includes the new option to its LAN DHCPv6 clients.
>>>
>>> /  So here is a scenario.
>>>
>>> / As an ISP, my customers have VoIP handsets that might support the OPT=
ION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, beca=
use they've bought those VoIP handsets from me). How long is it going to ta=
ke for me to get that option added to
> an updated RFC3736 and RFC7084, to get my CPE vendor to update and releas=
e their firmware to support that option, and test that new CPE firmware and=
 then to deploy that new firmware?
>>>
>>> / I think I'd be lucky if it only took 2 years.
>>>
>>> / A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZO=
NE to my customers if their hosts request it. So now I have to try to get O=
PTION_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendor=
 to update and release their firmware
> to support that option, and test that new CPE firmware and then to deploy=
 that new firmware.
>>>
>>> / Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION, =
so it is still "only" 2 years to get to a point where I could provide those=
 options to my customers. But what if that draft has progressed too far tho=
ugh the IETF publishing process? I have
> to create a new draft updating the to be published draft.
>>>
>>> / So, to achieve what should be a simple task of providing location or =
timezone information to customers' end hosts if they want it, we've just in=
curred the massive costs and time delays of the IETF publishing process, ve=
ndor firmware upgrades, firmware testing
> and firmware deployment. Sounds like how hard I understand it was to roll=
 out features like CLI in PSTN networks ...
>>>
>>> What is one option you'd like the host on the LAN to include so that we=
 can understand your use case better?
>>>
>>> / I'm going to make the problem much harder for you. I want the CPE to =
"support" or better, be transparent to, all current and future DHCPv6 optio=
ns, and I don't want to have to upgrade or ask my customers to successfully=
 upgrade their CPE each and every time
>>> there is a new DHCPv6 option defined that might be useful to me and the=
m. I want to be able to provide service parameters to my customers hosts, d=
irectly or indirectly, without the software revision or model of their CPE =
being the constraint.
>>>
>>> The SIP server is already included as one option supported by RFC3736. =
 Certainly, if the SIP server support is needed in the RA, I am open for it=
 since the RA already includes DNS information.
>>>
>>> / I don't think DNS in RAs was a good idea, and neither were SIP option=
s when they were proposed. See that time consuming and service disrupting f=
irmware upgrade cycle for new DHCPv6 options? Same problem if you use RA op=
tions to achieve the same goal. New
> firmware upgrade each time you want to support a new RA option.
>>>
>>> / Duplication between RA options and DHCPv6 options also causes more pr=
oblems. Which is preferred? Are they treated equally or does one take prece=
dence over the other? As far as I'm aware, these questions haven't been ans=
wered for the DHCPv6 DNS and RA DNS
> options yet. It might be simple to come up with a simple rule for more DH=
CPv6 options are duplicated into RAs, however their might be some specific =
cases where the RA option value should be preferred over the DHCPv6 equival=
ent option and vice-versa.
>>>
>>> However, I still ask the question as to how an RA received at the WAN o=
f the CPE has its options propagated to the RA on the LAN?  At the time of =
writing RFC 6204 or RFC 7084, there is no such provision between the RA rec=
eived on the WAN and the RA issued on
> the LAN of the CE router.
>>>
>>> / Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv6=
 options that are unknown by the CPE will pass right through it transparent=
ly. The only complication is when stateful DHCPv6 addressing is used on the=
 CPE LAN interface, and I suggested
> a hybrid mode of operation for a DHCPv6 server in that draft which I thin=
k solves that problem.
>>>
>>> Others,
>>>
>>> Also, why does one need an RA Option Guideline?  RFC4861 specifies a TL=
V format and an option Type.  I don't see anything else needed if I need to=
 specify a new RA option.
>>>
>>> Thanks,
>>>
>>> Hemant
>>>
>>> -----Original Message-----
>>> From: STARK, BARBARA H [mailto:bs7652@att.com<mailto:bs7652@att.com>]
>>> Sent: Tuesday, March 31, 2015 9:25 AM
>>> To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.o=
rg<mailto:ipv6@ietf.org>
>>> Subject: RE: RA Option Guidelines
>>>
>>>
>>>
>>>
>>> RFC 7084 already says:
>>> L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>>>        options (as listed in Section 5.3 of [RFC3736]) received from
>>>        the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>>>        server.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org<mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



--_000_147FEEB9096A4A67A3519B7A59D3172Eciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>Why is thus such a big deal? The same has been the case for v4 all alo=
ng and has not been an issue. There are reasons to upgrade CE or the firmwa=
re periodically, i.e. security and new features. New options aren't added t=
hat frequently and those that have
 been recently are for softwire and for options that your home computer, ph=
one, or tablet doesn't generally need.</div>
<div><br>
</div>
<div>See&nbsp;<a href=3D"http://www.iana.org/assignments/dhcpv6-parameters/=
dhcpv6-parameters.xhtml">http://www.iana.org/assignments/dhcpv6-parameters/=
dhcpv6-parameters.xhtml</a>.</div>
<div><br>
- Bernie (from iPad)</div>
<div><br>
On Apr 4, 2015, at 12:34 AM, Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzsm=
ith@yahoo.com.au">markzzzsmith@yahoo.com.au</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div style=3D"color:#000; background-color:#fff; font-family:Helvetica Neue=
-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Gran=
de, Sans-Serif;font-size:16px">
<div id=3D"yui_3_16_0_1_1428120409298_5500" dir=3D"ltr"><span>Hi Bernie,</s=
pan></div>
<br>
<div style=3D"font-family: Helvetica Neue-Light, Helvetica Neue Light, Helv=
etica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" =
id=3D"yui_3_16_0_1_1428120409298_4116">
<div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif; font-size: 16px;" id=3D"yui_3_16_0_1_1428120409=
298_4115">
<div dir=3D"ltr" id=3D"yui_3_16_0_1_1428120409298_4114">
<hr size=3D"1" id=3D"yui_3_16_0_1_1428120409298_5499">
<font size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_1_1428120409298_4113"><b><=
span style=3D"font-weight:bold;">From:</span></b> Bernie Volz (volz) &lt;<a=
 href=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt;<br>
<b><span style=3D"font-weight: bold;">To:</span></b> Mark ZZZ Smith &lt;<a =
href=3D"mailto:markzzzsmith@yahoo.com.au">markzzzsmith@yahoo.com.au</a>&gt;
<br>
<b><span style=3D"font-weight: bold;">Cc:</span></b> Hemant Singh (shemant)=
 &lt;<a href=3D"mailto:shemant@cisco.com">shemant@cisco.com</a>&gt;; Brian =
Haberman &lt;<a href=3D"mailto:brian@innovationslab.net">brian@innovationsl=
ab.net</a>&gt;; Ted Lemon &lt;<a href=3D"mailto:Ted.Lemon@nominum.com">Ted.=
Lemon@nominum.com</a>&gt;;
 &quot;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;; Ralph Droms (rdroms) &lt;<=
a href=3D"mailto:rdroms@cisco.com">rdroms@cisco.com</a>&gt;
<br>
<b><span style=3D"font-weight: bold;">Sent:</span></b> Saturday, 4 April 20=
15, 14:25<br>
<b><span style=3D"font-weight: bold;">Subject:</span></b> Re: RA Option Gui=
delines<br>
</font></div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>
Yes, in that situation the CE would not have requested the option from the =
ISP. You would need to update firmware on CE.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>
</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=
=3D"ltr">/ Thank you for confirming that.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>
</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=
=3D"ltr">/ Having to update firmware on the CE is the exact situation I thi=
nk should be avoided.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=
=3D"ltr"><br>
</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=
=3D"ltr">/ If CE devices have to be upgraded to deploy new applications and=
 services (and I think 'deployment' includes automated configuration of the=
m), then in my opinion Internet (application)
 transparency has been lost.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br c=
lear=3D"none">
<br clear=3D"none">
As new options get assigned, clients &amp; servers need to be updated to ma=
ke use of them.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>
</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118">/ If =
the CE device is DHCPv6 option transparent (i.e., is running a LAN DHCPv6 r=
elay), then upgrades are only required to the hosts that want to use the ne=
w DHCPv6 options, which is much less
 disruptive than also requiring CE firmware upgrades.<br clear=3D"none">
<br clear=3D"none">
You could also provide some CE configuration to request and save arbitary o=
ptions, but that only is useful to expert CE users and probably has securit=
y issues.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>
</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118" dir=
=3D"ltr">/ Agree, not practical for typical residential users.</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118"><br>
</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118">/ Reg=
ards,</div>
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428120409298_4118">/ Mar=
k.<br clear=3D"none">
<br clear=3D"none">
- Bernie (from iPad)<br clear=3D"none">
<div class=3D"qtdSeparateBR"><br>
<br>
</div>
<div class=3D"yqt6274444161" id=3D"yqtfd18973"><br clear=3D"none">
&gt; On Apr 3, 2015, at 9:41 PM, Mark ZZZ Smith &lt;<a shape=3D"rect" ymail=
to=3D"mailto:markzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.c=
om.au">markzzzsmith@yahoo.com.au</a>&gt; wrote:<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; I don't think it is.<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; Can this ever work, because this is the scenario I'm talking about:<br=
 clear=3D"none">
&gt; <br clear=3D"none">
&gt; (LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) &lt;-&gt; (CE: !DHCPV6_N=
EW_OPTION1, so no ORO for it) &lt;-&gt; (ISP: DHCPV6_NEW_OPTION1)<br clear=
=3D"none">
&gt; <br clear=3D"none">
&gt; <br clear=3D"none">
&gt; Is a combined DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unk=
nown* DHCPv6 option transparent, like a DHCPv6 relay is? I think the answer=
 is no based on what Bernie said.<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; ________________________________<br clear=3D"none">
&gt; From: Hemant Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"mailto:s=
hemant@cisco.com" href=3D"mailto:shemant@cisco.com">shemant@cisco.com</a>&g=
t;<br clear=3D"none">
&gt; To: Bernie Volz (volz) &lt;<a shape=3D"rect" ymailto=3D"mailto:volz@ci=
sco.com" href=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt;
<br clear=3D"none">
&gt; Cc: Mark ZZZ Smith &lt;<a shape=3D"rect" ymailto=3D"mailto:markzzzsmit=
h@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">markzzzsmith@yaho=
o.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a shape=3D"rect" ymailt=
o=3D"mailto:bs7652@att.com" href=3D"mailto:bs7652@att.com">bs7652@att.com</=
a>&gt;;
 Brian Haberman &lt;<a shape=3D"rect" ymailto=3D"mailto:brian@innovationsla=
b.net" href=3D"mailto:brian@innovationslab.net">brian@innovationslab.net</a=
>&gt;; &quot;<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mai=
lto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a shape=3D"rect" ymailto=3D=
"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;;
 Ralph Droms (rdroms) &lt;<a shape=3D"rect" ymailto=3D"mailto:rdroms@cisco.=
com" href=3D"mailto:rdroms@cisco.com">rdroms@cisco.com</a>&gt;; Ted Lemon &=
lt;<a shape=3D"rect" ymailto=3D"mailto:Ted.Lemon@nominum.com" href=3D"mailt=
o:Ted.Lemon@nominum.com">Ted.Lemon@nominum.com</a>&gt;
<br clear=3D"none">
&gt; Sent: Friday, 3 April 2015, 23:28<br clear=3D"none">
&gt; Subject: RE: RA Option Guidelines<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; <br clear=3D"none">
&gt; <br clear=3D"none">
&gt; Bernie,<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; Got it =96 thanks much!&nbsp; So the CE router implementation has to c=
hange to be configurable to include a new DHCPv6 option in the ORO for the =
WAN interface.&nbsp; Once the new option is returned by the server, the CE =
uses the new option for stateless DHCPv6 services
 on the LAN.&nbsp; Note, it is the same service provider who has configured=
 the CE for the new DHCPv6 option and thus the same service provider also p=
rovisions the DHCPv6 server to return the new option, if asked for.&nbsp; T=
here is no need for DHCPv6 relay in the CE
 for this new option support.&nbsp; <br clear=3D"none">
&gt; <br clear=3D"none">
&gt; In summary, both Mark=92s and Barbara=92s goals are met.<br clear=3D"n=
one">
&gt; <br clear=3D"none">
&gt; Thanks,<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; Hemant<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; <br clear=3D"none">
&gt; <br clear=3D"none">
&gt; From:Bernie Volz (volz) <br clear=3D"none">
&gt; Sent: Friday, April 03, 2015 7:48 AM<br clear=3D"none">
&gt; To: Hemant Singh (shemant)<br clear=3D"none">
&gt; Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a shape=3D"rect=
" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br clear=3D"none">
&gt; Subject: Re: RA Option Guidelines<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; All options MUST be in ORO for server to return (there are some &quot;=
protocol&quot; options, such as client-id and server-id that are NOT suppos=
ed to be in ORO). So client controls the options it gets. So #1 is not true=
 (some servers, such as CPNR, can be configured
 to return options the client did not request, but generally that is useles=
s since the client will most likely ignore it).<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; #2 is normal DHCP operation.<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; Note that while I think you were discussing stateless, it is true for =
stateful and stateless dhcp.<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; - Bernie (from iPad)<br clear=3D"none">
&gt; <br clear=3D"none">
&gt;&gt; On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) &lt;<a shape=3D=
"rect" ymailto=3D"mailto:shemant@cisco.com" href=3D"mailto:shemant@cisco.co=
m">shemant@cisco.com</a>&gt; wrote:<br clear=3D"none">
&gt;&gt; Bernie,<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; Appreciate the quick reply.&nbsp; Let me summarize the issues and =
then you can clarify.<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; 1.&nbsp; &nbsp; The CE WAN interface does not include a new option=
 in DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the server.&nbsp=
; If the server is configured to return the DHCPV6_NEW_OPTION1 to clients, =
then will the server reply with DHCPV6_NEW_OPTION1 even
 when the client did not request the option in the ORO?&nbsp; In this scena=
rio, no code changes on the CE, and just the server configuration takes car=
e of the issue.<br clear=3D"none">
&gt;&gt; 2.&nbsp; &nbsp; The CE WAN interface does include a new option in =
DHCPV6_NEW_OPTION1 in the ORO option of the SOLICIT to the server.&nbsp; If=
 the server is configured to return DHCPV6_NEW_OPTION1 to clients, then wil=
l the server reply with DHCPV6_NEW_OPTION1?<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; Mark,<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; Note Bernie agrees with how I and Wes Beebee (who I discussed this=
 thread with) also interpreted RFC3736.&nbsp; New options can be served by =
the stateless DHCPv6 server without revising RFC3736.<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; Thanks all,<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; Hemant<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; From:Bernie Volz (volz) <br clear=3D"none">
&gt;&gt; Sent: Friday, April 03, 2015 7:33 AM<br clear=3D"none">
&gt;&gt; To: Hemant Singh (shemant)<br clear=3D"none">
&gt;&gt; Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; <a shape=3D"=
rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">
ipv6@ietf.org</a>; Ralph Droms (rdroms); Ted Lemon<br clear=3D"none">
&gt;&gt; Subject: Re: RA Option Guidelines<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; I didn't study the complete thread but I am sure everyone would un=
derstand that new options should be allowed to be requested. The ORO list c=
annot be frozen ... At the time the rfc was written, that was the list. But=
 new option documents are not required
 to update RFC3736.<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; There are no interop issues either as if either side (client or se=
rver) doesn't know of an option, it just doesn't include or ignores it.<br =
clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt; - Bernie (from iPad)<br clear=3D"none">
&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) &lt;<a shap=
e=3D"rect" ymailto=3D"mailto:shemant@cisco.com" href=3D"mailto:shemant@cisc=
o.com">shemant@cisco.com</a>&gt; wrote:<br clear=3D"none">
&gt;&gt;&gt; Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help r=
esolve this thread for stateless DHCPv6 current vs. future options and the =
ORO option.
<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Thanks,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Hemant<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; From:Mark ZZZ Smith [mailto:<a shape=3D"rect" ymailto=3D"mailt=
o:markzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">mark=
zzzsmith@yahoo.com.au</a>]
<br clear=3D"none">
&gt;&gt;&gt; Sent: Thursday, April 02, 2015 10:19 PM<br clear=3D"none">
&gt;&gt;&gt; To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; =
<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf=
.org">
ipv6@ietf.org</a><br clear=3D"none">
&gt;&gt;&gt; Subject: Re: RA Option Guidelines<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Hi Hemant,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; ________________________________<br clear=3D"none">
&gt;&gt;&gt; From: Hemant Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"=
mailto:shemant@cisco.com" href=3D"mailto:shemant@cisco.com">shemant@cisco.c=
om</a>&gt;<br clear=3D"none">
&gt;&gt;&gt; To: Mark ZZZ Smith &lt;<a shape=3D"rect" ymailto=3D"mailto:mar=
kzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">markzzzsm=
ith@yahoo.com.au</a>&gt;; &quot;STARK, BARBARA H&quot; &lt;<a shape=3D"rect=
" ymailto=3D"mailto:bs7652@att.com" href=3D"mailto:bs7652@att.com">bs7652@a=
tt.com</a>&gt;;
 Brian Haberman &lt;<a shape=3D"rect" ymailto=3D"mailto:brian@innovationsla=
b.net" href=3D"mailto:brian@innovationslab.net">brian@innovationslab.net</a=
>&gt;; &quot;<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mai=
lto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a shape=3D"rect" ymailto=3D=
"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br clear=3D"none">
&gt;&gt;&gt; Sent: Friday, 3 April 2015, 6:07<br clear=3D"none">
&gt;&gt;&gt; Subject: RE: RA Option Guidelines<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Mark,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; The stateless DHCPv6 server in RFC3736 allows for new options =
to be served by the stateless server.&nbsp; Read the first paragraph of sec=
tion 5.3 in RFC3736.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / So there are a few reasons why I wouldn't come to that concl=
usion without some very careful reading:<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / - The explicitly identified set of required and optional DHC=
Pv6 options that can be supported by a stateless DHCPv6 server<br clear=3D"=
none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / - The lack of any overt discussion that this set of required=
 and optional DHCPv6 options are a minimum, and that further DHCPv6 options=
 could be provided by a stateless DHCPv6 server if supported by the impleme=
ntation, are appropriate and requested by
 the<br clear=3D"none">
&gt; client. It being a minimum is subtly eluded to in a few sentences in t=
he Abstract and the Introduction, however I think they could easily be miss=
ed. I'd expect that if this is the case, it is much clearer and obvious.<br=
 clear=3D"none">
&gt;&gt;&gt; / - I think text you refer to in 5.3, &quot;Clients and server=
s use the following options to pass configuration information to clients; n=
ote that other options for configuration information may be specified in fu=
ture Internet Standards:&quot; reads to me like a later
 version of this RFC will specify more stateless DHCPv6 server supported op=
tions. A statement such as &quot;Other additional DHCPv6 options appropriat=
e for stateless DHCPv6 operation may be supported by an implementation.&quo=
t; would make it much clearer that the supported
 options were up to the implementer once the minimum had been implemented.<=
br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / So if I were implementing a stateless DHCPv6 server as per R=
FC3736, I'd think the implementation was complete when I had implemented th=
e options specified. I wouldn't put any effort into making it also transpar=
ent to any options that weren't identified
 in RFC3736, as there is no text discussing that.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; So the new options you want to serve can be served by the CE s=
tateless DHCPv6 server.&nbsp; Now, if the service provider configures his/h=
er DHCPv6 server to return new options to the CE WAN interface address acqu=
isition, the CE uses the options on the LAN.&nbsp;
 See bullet L-12 of RFC 7084.&nbsp; Existing RFCs support your use case and=
 no dhcpv6 relay is required in the CE.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / I also cannot find text in RFC3315 or its updates on how to =
handle received options that were not requested by the client in the Option=
 Request Option. So if the CE WAN DHCPv6 client doesn't request an option i=
n its ORO to the SP's DHCPv6 server, I don't
 think it is possible for the CE to pass options it doesn't know about onto=
 the downstream LAN devices that do understand those DHCPv6 options.<br cle=
ar=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / If it is possible to send a DHCPv6 client &quot;ORO type&quo=
t; options that it didn't request, then the behaviour is still ambiguous. I=
f the DHCPv6 client is a host, then it would be quite reasonable and expect=
ed to silently ignore those received unknown options.
 However, if the DHCPv6 client is on the WAN side of a CE device, then thos=
e options should instead be passed to the LAN DHCPv6 server, which presumab=
ly should know how to correctly handle options it doesn't understand - in t=
he specific CE case, remember those
 options in case a downstream LAN DHCPv6 client requests them. I think RFC7=
084 and it's ancestor RFC6204 are the only RFCs which describe this combina=
tion of DHCPv6 client/server working together, and neither of them have dis=
cussed passing unknown options from
 the DHCPv6 WAN client to the DHCPv6 LAN server.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server =
implementations that are unknown DHCPv6 option transparent? Looking at RFC7=
084, this behaviour seems to be very explicitly prohibited, by limiting the=
 LAN DHCPv6 server support to only those
 options described in RFC7084, or to those described in RFC3736.<br clear=
=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / I think this level of DHCPv6 option transparency between CE =
LAN attached hosts and the upstream SP's DHCPv6 server(s) can only be achie=
ved by using a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays =
are DHCPv6 option transparent. (A CE would
 still have a DHCPv6 client on its WAN interface for its own parameters and=
 DHCPv6-PD prefixes).<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / Regards,<br clear=3D"none">
&gt;&gt;&gt; / Mark.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Barbara,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; For your use case, the service provider configures the DHCPv6 =
server to only serve options specified in RFC 7084.&nbsp; Thus in this depl=
oyment no extra options exist to serve to the CE router LAN.<br clear=3D"no=
ne">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Both use cases can be supported using existing RFC=92s.<br cle=
ar=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Hemant<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; From:Mark ZZZ Smith [mailto:<a shape=3D"rect" ymailto=3D"mailt=
o:markzzzsmith@yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">mark=
zzzsmith@yahoo.com.au</a>]
<br clear=3D"none">
&gt;&gt;&gt; Sent: Tuesday, March 31, 2015 9:52 PM<br clear=3D"none">
&gt;&gt;&gt; To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; =
<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf=
.org">
ipv6@ietf.org</a><br clear=3D"none">
&gt;&gt;&gt; Subject: Re: RA Option Guidelines<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Hi Hemant,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; ________________________________<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; From:Hemant Singh (shemant) &lt;<a shape=3D"rect" ymailto=3D"m=
ailto:shemant@cisco.com" href=3D"mailto:shemant@cisco.com">shemant@cisco.co=
m</a>&gt;<br clear=3D"none">
&gt;&gt;&gt; To: &quot;STARK, BARBARA H&quot; &lt;<a shape=3D"rect" ymailto=
=3D"mailto:bs7652@att.com" href=3D"mailto:bs7652@att.com">bs7652@att.com</a=
>&gt;; Mark ZZZ Smith &lt;<a shape=3D"rect" ymailto=3D"mailto:markzzzsmith@=
yahoo.com.au" href=3D"mailto:markzzzsmith@yahoo.com.au">markzzzsmith@yahoo.=
com.au</a>&gt;;
 Brian Haberman &lt;<a shape=3D"rect" ymailto=3D"mailto:brian@innovationsla=
b.net" href=3D"mailto:brian@innovationslab.net">brian@innovationslab.net</a=
>&gt;; &quot;<a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mai=
lto:ipv6@ietf.org">ipv6@ietf.org</a>&quot; &lt;<a shape=3D"rect" ymailto=3D=
"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;
<br clear=3D"none">
&gt;&gt;&gt; Sent: Wednesday, 1 April 2015, 1:27<br clear=3D"none">
&gt;&gt;&gt; Subject: RE: RA Option Guidelines<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Barbara,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Thanks for replying.&nbsp; &nbsp; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Mark,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; If new DHCPv6 options are added to be supported by RFC3736, th=
en the SP includes the new option in the DHCPv6 responses to the CPE WAN.&n=
bsp; Then the CPE includes the new option to its LAN DHCPv6 clients.<br cle=
ar=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; /&nbsp; So here is a scenario.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / As an ISP, my customers have VoIP handsets that might suppor=
t the OPTION_GEOLOCATION DHCPv6 option (I might know that a portion of them=
 do, because they've bought those VoIP handsets from me). How long is it go=
ing to take for me to get that option added
 to<br clear=3D"none">
&gt; an updated RFC3736 and RFC7084, to get my CPE vendor to update and rel=
ease their firmware to support that option, and test that new CPE firmware =
and then to deploy that new firmware?<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / I think I'd be lucky if it only took 2 years.<br clear=3D"no=
ne">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / A few months later I decide I want to provide OPTION_NEW_POS=
IX_TIMEZONE to my customers if their hosts request it. So now I have to try=
 to get OPTION_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my C=
PE vendor to update and release their firmware<br clear=3D"none">
&gt; to support that option, and test that new CPE firmware and then to dep=
loy that new firmware.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / Now if I'm lucky I could add it to the draft for OPTION_GEOL=
OCATION, so it is still &quot;only&quot; 2 years to get to a point where I =
could provide those options to my customers. But what if that draft has pro=
gressed too far though the IETF publishing process?
 I have<br clear=3D"none">
&gt; to create a new draft updating the to be published draft.<br clear=3D"=
none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / So, to achieve what should be a simple task of providing loc=
ation or timezone information to customers' end hosts if they want it, we'v=
e just incurred the massive costs and time delays of the IETF publishing pr=
ocess, vendor firmware upgrades, firmware
 testing<br clear=3D"none">
&gt; and firmware deployment. Sounds like how hard I understand it was to r=
oll out features like CLI in PSTN networks ...<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; What is one option you'd like the host on the LAN to include s=
o that we can understand your use case better?&nbsp;
<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / I'm going to make the problem much harder for you. I want th=
e CPE to &quot;support&quot; or better, be transparent to, all current and =
future DHCPv6 options, and I don't want to have to upgrade or ask my custom=
ers to successfully upgrade their CPE each and every
 time<br clear=3D"none">
&gt;&gt;&gt; there is a new DHCPv6 option defined that might be useful to m=
e and them. I want to be able to provide service parameters to my customers=
 hosts, directly or indirectly, without the software revision or model of t=
heir CPE being the constraint.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; The SIP server is already included as one option supported by =
RFC3736.&nbsp; Certainly, if the SIP server support is needed in the RA, I =
am open for it since the RA already includes DNS information.<br clear=3D"n=
one">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / I don't think DNS in RAs was a good idea, and neither were S=
IP options when they were proposed. See that time consuming and service dis=
rupting firmware upgrade cycle for new DHCPv6 options? Same problem if you =
use RA options to achieve the same goal.
 New<br clear=3D"none">
&gt; firmware upgrade each time you want to support a new RA option.<br cle=
ar=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / Duplication between RA options and DHCPv6 options also cause=
s more problems. Which is preferred? Are they treated equally or does one t=
ake precedence over the other? As far as I'm aware, these questions haven't=
 been answered for the DHCPv6 DNS and RA
 DNS<br clear=3D"none">
&gt; options yet. It might be simple to come up with a simple rule for more=
 DHCPv6 options are duplicated into RAs, however their might be some specif=
ic cases where the RA option value should be preferred over the DHCPv6 equi=
valent option and vice-versa.
<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; However, I still ask the question as to how an RA received at =
the WAN of the CPE has its options propagated to the RA on the LAN?&nbsp; A=
t the time of writing RFC 6204 or RFC 7084, there is no such provision betw=
een the RA received on the WAN and the RA issued
 on<br clear=3D"none">
&gt; the LAN of the CE router.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; / Use a DHCPv6 relay in the CPE. Then there isn't a problem, n=
ew DHCPv6 options that are unknown by the CPE will pass right through it tr=
ansparently. The only complication is when stateful DHCPv6 addressing is us=
ed on the CPE LAN interface, and I suggested<br clear=3D"none">
&gt; a hybrid mode of operation for a DHCPv6 server in that draft which I t=
hink solves that problem.<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Others,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Also, why does one need an RA Option Guideline?&nbsp; RFC4861 =
specifies a TLV format and an option Type.&nbsp; I don't see anything else =
needed if I need to specify a new RA option.
<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Thanks,<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; Hemant<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; -----Original Message-----<br clear=3D"none">
&gt;&gt;&gt; From: STARK, BARBARA H [mailto:<a shape=3D"rect" ymailto=3D"ma=
ilto:bs7652@att.com" href=3D"mailto:bs7652@att.com">bs7652@att.com</a>]
<br clear=3D"none">
&gt;&gt;&gt; Sent: Tuesday, March 31, 2015 9:25 AM<br clear=3D"none">
&gt;&gt;&gt; To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; <a=
 shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.o=
rg">
ipv6@ietf.org</a><br clear=3D"none">
&gt;&gt;&gt; Subject: RE: RA Option Guidelines<br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; <br clear=3D"none">
&gt;&gt;&gt; RFC 7084 already says: <br clear=3D"none">
&gt;&gt;&gt; L-12:&nbsp; The IPv6 CE router SHOULD make available a subset =
of DHCPv6<br clear=3D"none">
&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; options (as listed in Section 5.3 o=
f [RFC3736]) received from<br clear=3D"none">
&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; the DHCPv6 client on its WAN interf=
ace to its LAN-side DHCPv6<br clear=3D"none">
&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; server.<br clear=3D"none">
&gt; <br clear=3D"none">
&gt; --------------------------------------------------------------------<b=
r clear=3D"none">
&gt; IETF IPv6 working group mailing list<br clear=3D"none">
&gt; <a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6=
@ietf.org">ipv6@ietf.org</a><br clear=3D"none">
&gt; Administrative Requests: <a shape=3D"rect" href=3D"https://www.ietf.or=
g/mailman/listinfo/ipv6" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ipv6</a><br clear=3D"none">
&gt; --------------------------------------------------------------------</=
div>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_147FEEB9096A4A67A3519B7A59D3172Eciscocom_--


From nobody Sat Apr  4 05:26:33 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22ACF1A8890 for <ipv6@ietfa.amsl.com>; Sat,  4 Apr 2015 05:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 iEnxCrD382Wv for <ipv6@ietfa.amsl.com>; Sat,  4 Apr 2015 05:26:30 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001: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 F39E11A88E4 for <ipv6@ietf.org>; Sat,  4 Apr 2015 05:26:28 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so109278170igb.1 for <ipv6@ietf.org>; Sat, 04 Apr 2015 05:26:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=P/HW9Srfx1p8xAHWagSJGH/Pxuv5/UkqURAo5sZJq38=; b=RyklQW/FJ/aATcaTDrO10vGrIXUXdOekw5+eUEs+v4mgSCdXsFtrLo/AgVxFH0oY78 ncdnnpTsUeq8pu7u8RM4ZyWKD1D43X3z+bvytm36eA2L8zlllLtsSg3/KUDMr6PKmOtI NqAAZcc3yjNgGvmK1vxqxB9Ob2KIU4d86CnlIjmvPQNDHFbSVaCi5SjYFqzEz3oOND9d v1ajBqB209cqQtiGtnqEvNA0p/x6TkKX9VOkkqNPd5SE3JUL0qRwxsTKr49LluxF+On7 ZlMtJZsDKMgsEy/vw6++2j4yntlLymnHEdcms7cZNMPPg7XSkyS7w5UUId41GhvUxAzS QyWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=P/HW9Srfx1p8xAHWagSJGH/Pxuv5/UkqURAo5sZJq38=; b=c4qqhqScfgPS0NqLI1JsmJvrgrXkhA+4tcASfmWPBnWPAYIe/NJLK4mqTamzsb2yyI ANBPqYBl3VRqc0Er4mkDjmLK0X56HjQcD1fnO45nU2icgPncwyZbjDUZLJATF2Aj04se lFAk5zn4xOXMTC/f87YSImwp/hUKwtInLSOgTq7e1N24o3d8XQSY2YjVJ74Qd15kcNO2 +kRUfNdz3zYFtmr1OJG+zJVrIp3FFJbeKq690nif7U22XkUG+q80Qwa0tKSaPP2ywXJn fMyrhYqSRhZAljP+ImQLMhEQrHaiYeawuKq39qfG4R8z+pWJyPTLc2HfLdSCyzJ81OyO UcYw==
X-Gm-Message-State: ALoCoQmtewLDytXGrqy+mQDP0LnOunyzQyZSREIjW1Ph4v5N0HhNawgrhmXeSw3ogntam+qAEbN2
X-Received: by 10.107.130.145 with SMTP id m17mr9564673ioi.89.1428150388360; Sat, 04 Apr 2015 05:26:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Sat, 4 Apr 2015 05:26:07 -0700 (PDT)
In-Reply-To: <551EE710.2050301@gmail.com>
References: <5515A9A7.3080508@innovationslab.net> <281018849.2116525.1427767749309.JavaMail.yahoo@mail.yahoo.com> <75B6FA9F576969419E42BECB86CB1B8916834620@xmb-rcd-x06.cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F8C7AF@GAALPA1MSGUSRBF.ITServices.sbc.com> <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <551AF4E5.7000207@gmail.com> <551EE710.2050301@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 4 Apr 2015 21:26:07 +0900
Message-ID: <CAKD1Yr1WnOSB_dmF4g1=-mUKoekzpPzFA4P6H=f3pYa7F1YO9A@mail.gmail.com>
Subject: Re: RA Option Guidelines
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ed02a95b1340512e52cec
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/P1gouEJZ8uuRci9mKw91knwdqpY>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 12:26:31 -0000

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

On Sat, Apr 4, 2015 at 4:16 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Do we actually agree on this, or rather on a slightly expanded version:
>
> RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only) necessary for a simple unmanaged network.
> The only exception is RFC 6106 (DNS Configuration). More complex situations
> are better handled by other configuration metods such as DHCPv6.


No, I strongly disagree.

There are other differences between RA and DHCP. The most important one I
see is that with DHCP it is basically impossible to change things
dynamically.

Dynamically changing stateful parameters requires that the client implement
reconfigure, and even then, it requires authentication, and requires either
that the DHCP server never crashes, or that DHCPv6 failover is in use.
Dynamically changing stateless options doesn't even seem possible at all -
you have to wait until the client asks again, and the minimum time that
must pass is 10 minutes (RFC 4242).

--001a113ed02a95b1340512e52cec
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 S=
at, Apr 4, 2015 at 4:16 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=
=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter=
@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Do we ac=
tually agree on this, or rather on a slightly expanded version:<br>
<span><br>
RA options should be limited to link-local/subnet specific parameters<br>
</span>(i.e., layer 3 parameters only) necessary for a simple unmanaged net=
work.<br>
The only exception is RFC 6106 (DNS Configuration). More complex situations=
<br>
are better handled by other configuration metods such as DHCPv6.</blockquot=
e><div><br></div><div>No, I strongly disagree.</div><div><br></div><div>The=
re are other differences between RA and DHCP. The most important one I see =
is that with DHCP it is basically impossible to change things dynamically.<=
/div><div><br></div><div>Dynamically changing stateful parameters requires =
that the client implement reconfigure, and even then, it requires authentic=
ation, and requires either that the DHCP server never crashes, or that DHCP=
v6 failover is in use. Dynamically changing stateless options doesn&#39;t e=
ven seem possible at all - you have to wait until the client asks again, an=
d the minimum time that must pass is 10 minutes (RFC 4242).</div></div></di=
v></div>

--001a113ed02a95b1340512e52cec--


From nobody Mon Apr  6 15:41:12 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1231ACCDF for <ipv6@ietfa.amsl.com>; Mon,  6 Apr 2015 15:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.201
X-Spam-Level: ***
X-Spam-Status: No, score=3.201 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 NPf_-dP40rbb for <ipv6@ietfa.amsl.com>; Mon,  6 Apr 2015 15:41:08 -0700 (PDT)
Received: from nm13-vm0.bullet.mail.bf1.yahoo.com (nm13-vm0.bullet.mail.bf1.yahoo.com [98.139.213.79]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E08411ACCDA for <ipv6@ietf.org>; Mon,  6 Apr 2015 15:41:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428360067; bh=yl5rA2Z3mukwSl2TCW5kXAscX5bc4VyCtpiXVIjhu00=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=gjKNvOrGmGG90pPx/+t6CJk1akDca/v+51xrWH7fHNFLkO97sEN9XVb24dQZ4jvvumqb2LVyhqsegL+6IRHj5Ov4IVtqJ0CvH/6seCtfI0KRS0j/fg8GBVN98Iq5Q/ef0jyRgtyK4A1AsFfTALXhVMlLldpDtr13GiJ47zePWKjCThLIzXJctx5hHj7PkU0rFHOTYWbgC790BwYlwS0dbqnp4muOb4I1/4ju3jQXRYvRzYoueBIC8+tZo7OTwi3MVtvm691m4CZaoL9ShXz+L8Bd8wdb6tDSbnhChxVq+57NC/xawq+s4Tz8znRxl08OA+59evGG63lkwG5BlP0iKw==
Received: from [66.196.81.172] by nm13.bullet.mail.bf1.yahoo.com with NNFMP; 06 Apr 2015 22:41:07 -0000
Received: from [98.139.212.217] by tm18.bullet.mail.bf1.yahoo.com with NNFMP;  06 Apr 2015 22:41:07 -0000
Received: from [127.0.0.1] by omp1026.mail.bf1.yahoo.com with NNFMP; 06 Apr 2015 22:41:07 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 101967.32417.bm@omp1026.mail.bf1.yahoo.com
X-YMail-OSG: Qqy9zPQVM1mydBHtGA.B_yQpd5JGfmIGhYYJ.1HXzCEBrKRUADRgYDyHlA7uzDu r48DK2aUqi_4XpWxyG5EjAFGzfrOkgfP4Ta0OyVunxBo5T2hzV8SLmwNdsIFWgcqqzrNQ6XdFqqX R8wXhMRHWZHc7BmcvApm7c2qWczXjA_4Bere84e.G623b6pT_sbojIQDeM_OsZVDUsxZ9juxhpu3 nq7JQ5q8T_B_IXWT9kn9Xox53lA0E5rIgVaL7O8K5ut34kYLWxm4xKjt0X6MU1OCRsHOKB.7SAg8 Nque2hhDmIFgHGYydib.4S_tLW6D0lkSdjs5cxSYXsWeKFyvJ7hucZ2N.EuCXsLTlRCWgyU1Goxa sKkXJ0RSweHh8ycdXDAu73MIxmg2hVXvQV1V4zFystTbU0pICxMaRUPKW6hZx.QWbQ8qFTFIm8Zz WPnUebX6RQxjZQSvtdXgDNS3xFdWJ4ibZQC1auu0TWJ824sJqOqBfR_XrbEWVf56pKxBUAznVVh_ pLGOQp4kHfJOZ4g1n0ReYzKNEOu7qPM7A3VvN7ymtOugt9nCCH155wVBK2.T_UyrWF8WOy_99OOY GMLb_xtTgwPvvqg_UGtaELk_pR5ckZYPj4lpBZ1IZ.lhmlnbnwvFJtPl9pKCgrGi5G9.D3F_3k_N .cQiKE79I7OaCr5sk1oG99SE_FHTU6AIj.OrMvmEdZK2v1rm.ghSxIa.QalCZL3CQmrYTkWwltdQ HW5ehPrK9cgjRlV12XjILaSDgyKsBgQNP_ZpYVpyR3OkjladMgPf9dx44pxJL3pc2lt7K.3CvzC3 JeB0zNa9MD1NTFaexsk2BQx4w0CUlyd0UMMPCR6xMfXWTCsMevWLbFVGnA343pNxt8.2_GQ_qzhs RRGoTE9ZN85KEsrHNT5JLisup.CqTp1GAWu_MdhPY3f2QtPkxSqzUGeW74aQaQtdtvIzO6KS9g.S XJztxF.M5GHW4T.EZAqq0QydEgRyrpryBGkfimfCDNLpJLZkAR2skkRpsI.764DJzZQKwbS1dpvU IIrduxdoXWUmEuzUvC5lr8M5FhFFabpzzmx98zwwueTlLKFkHx7attp7IIREEUHaj7U6zVVxd4P. xwUPFNtxJxI1Bqnwi37.ic_0aZebcFbYrGnIZTd11XEye.Qu6V6QhT1Yz
Received: by 76.13.26.156; Mon, 06 Apr 2015 22:41:06 +0000 
Date: Mon, 6 Apr 2015 22:41:03 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "Bernie Volz (volz)" <volz@cisco.com>
Message-ID: <1184477004.758166.1428360063664.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <147FEEB9-096A-4A67-A351-9B7A59D3172E@cisco.com>
References: <147FEEB9-096A-4A67-A351-9B7A59D3172E@cisco.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jQFvkqjPPO_vchutetCft6V4JS0>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2015 22:41:11 -0000

Hi Bernie,

Actually, in many broadband networks IPv4 is quite different. The options y=
ou could convey to customers were limited to those that were supported by I=
PCP,


- IPv4 DNS

- Microsoft Netbios Name Servers addresses
- Mobile IPv4 address
everything else had to be manually configured by the customer, with the det=
ails provided on settings web pages such as this,


http://www.internode.on.net/support/guides/general_settings/



which is onerous and error prone, and in my opinion would be a very un-user=
 friendly practice to continue in IPv6. Cars are learning drive themselves,=
 and planes can fly themselves, so why do customers still have to cut and p=
aste ISP service setting into their applications in this day and age?



There are certainly good reasons to upgrade CPE fairly regularly, however I=
'm not confident it is happening as much as people might believe, based on =
first hand experience at fairly residential broadband ISPs in Australia bet=
ween 2005 and 2011, where the market is primarily BYO CPE, and a number of =
other presentations and articles I've seen on the topic such as these:

Black Hat USA 2014 - Network: Abuse of CPE Devices and Recommended Fixes
https://www.youtube.com/watch?v=3DJJF91GHm_7w

The Wild West by HD Moore
https://speakerdeck.com/hdm/derbycon-2012-the-wild-west


12 Million Home Routers Vulnerable to Takeover
https://threatpost.com/12-million-home-routers-vulnerable-to-takeover/10997=
0

Australia in the Carna Botnet
https://docs.google.com/file/d/0BxMgdZPXsSLBX2VXUTBXYURkNlk/edit


Security updates could be considered a more important reason to upgrade tha=
n to support new DHCP options, so if security updates aren't happening, the=
n updates to support new DHCP options are even less likely to occur.


IOW, upgrading routers to support new applications is not practical, and in=
 my understanding, also not following the Internet (Application) Transparen=
cy model as described in RFC1958 and other RFCs.=20

Regards,
Mark.










________________________________
From: Bernie Volz (volz) <volz@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>=20
Cc: Hemant Singh (shemant) <shemant@cisco.com>; Brian Haberman <brian@innov=
ationslab.net>; Ted Lemon <Ted.Lemon@nominum.com>; "ipv6@ietf.org" <ipv6@ie=
tf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>=20
Sent: Saturday, 4 April 2015, 23:05
Subject: Re: RA Option Guidelines



Why is thus such a big deal? The same has been the case for v4 all along an=
d has not been an issue. There are reasons to upgrade CE or the firmware pe=
riodically, i.e. security and new features. New options aren't added that f=
requently and those that have been recently are for softwire and for option=
s that your home computer, phone, or tablet doesn't generally need.

See http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xht=
ml.

- Bernie (from iPad)



On Apr 4, 2015, at 12:34 AM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au> wro=
te:


Hi Bernie,
>
>
>________________________________
> From: Bernie Volz (volz) <volz@cisco.com>
>To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>=20
>Cc: Hemant Singh (shemant) <shemant@cisco.com>; Brian Haberman <brian@inno=
vationslab.net>; Ted Lemon <Ted.Lemon@nominum.com>; "ipv6@ietf.org" <ipv6@i=
etf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>=20
>Sent: Saturday, 4 April 2015, 14:25
>Subject: Re: RA Option Guidelines
>
>
>Yes, in that situation the CE would not have requested the option from the=
 ISP. You would need to update firmware on CE.
>
>
>/ Thank you for confirming that.
>
>
>/ Having to update firmware on the CE is the exact situation I think shoul=
d be avoided.
>
>
>/ If CE devices have to be upgraded to deploy new applications and service=
s (and I think 'deployment' includes automated configuration of them), then=
 in my opinion Internet (application) transparency has been lost.
>
>
>As new options get assigned, clients & servers need to be updated to make =
use of them.
>
>
>/ If the CE device is DHCPv6 option transparent (i.e., is running a LAN DH=
CPv6 relay), then upgrades are only required to the hosts that want to use =
the new DHCPv6 options, which is much less disruptive than also requiring C=
E firmware upgrades.
>
>You could also provide some CE configuration to request and save arbitary =
options, but that only is useful to expert CE users and probably has securi=
ty issues.
>
>
>/ Agree, not practical for typical residential users.
>
>
>/ Regards,
>/ Mark.
>
>- Bernie (from iPad)
>
>
>
>
>
>> On Apr 3, 2015, at 9:41 PM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au> w=
rote:
>>=20
>> I don't think it is.
>>=20
>> Can this ever work, because this is the scenario I'm talking about:
>>=20
>> (LAN Host: DHCPV6_NEW_OPTION1, so ORO for it) <-> (CE: !DHCPV6_NEW_OPTIO=
N1, so no ORO for it) <-> (ISP: DHCPV6_NEW_OPTION1)
>>=20
>>=20
>> Is a combined DHCPv6 Client/DHCPv6 server, as in the CE scenario, *unkno=
wn* DHCPv6 option transparent, like a DHCPv6 relay is? I think the answer i=
s no based on what Bernie said.
>>=20
>> ________________________________
>> From: Hemant Singh (shemant) <shemant@cisco.com>
>> To: Bernie Volz (volz) <volz@cisco.com>=20
>> Cc: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs76=
52@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ip=
v6@ietf.org>; Ralph Droms (rdroms) <rdroms@cisco.com>; Ted Lemon <Ted.Lemon=
@nominum.com>=20
>> Sent: Friday, 3 April 2015, 23:28
>> Subject: RE: RA Option Guidelines
>>=20
>>=20
>>=20
>> Bernie,
>>=20
>> Got it =E2=80=93 thanks much!  So the CE router implementation has to ch=
ange to be configurable to include a new DHCPv6 option in the ORO for the W=
AN interface.  Once the new option is returned by the server, the CE uses t=
he new option for stateless DHCPv6 services
on the LAN.  Note, it is the same service provider who has configured the C=
E for the new DHCPv6 option and thus the same service provider also provisi=
ons the DHCPv6 server to return the new option, if asked for.  There is no =
need for DHCPv6 relay in the CE
for this new option support. =20
>>=20
>> In summary, both Mark=E2=80=99s and Barbara=E2=80=99s goals are met.
>>=20
>> Thanks,
>>=20
>> Hemant
>>=20
>>=20
>>=20
>> From:Bernie Volz (volz)=20
>> Sent: Friday, April 03, 2015 7:48 AM
>> To: Hemant Singh (shemant)
>> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ral=
ph Droms (rdroms); Ted Lemon
>> Subject: Re: RA Option Guidelines
>>=20
>> All options MUST be in ORO for server to return (there are some "protoco=
l" options, such as client-id and server-id that are NOT supposed to be in =
ORO). So client controls the options it gets. So #1 is not true (some serve=
rs, such as CPNR, can be configured
to return options the client did not request, but generally that is useless=
 since the client will most likely ignore it).
>>=20
>> #2 is normal DHCP operation.
>>=20
>> Note that while I think you were discussing stateless, it is true for st=
ateful and stateless dhcp.
>>=20
>> - Bernie (from iPad)
>>=20
>>> On Apr 3, 2015, at 7:43 AM, Hemant Singh (shemant) <shemant@cisco.com> =
wrote:
>>> Bernie,
>>>=20
>>> Appreciate the quick reply.  Let me summarize the issues and then you c=
an clarify.
>>>=20
>>> 1.    The CE WAN interface does not include a new option in DHCPV6_NEW_=
OPTION1 in the ORO option of the SOLICIT to the server.  If the server is c=
onfigured to return the DHCPV6_NEW_OPTION1 to clients, then will the server=
 reply with DHCPV6_NEW_OPTION1 even
when the client did not request the option in the ORO?  In this scenario, n=
o code changes on the CE, and just the server configuration takes care of t=
he issue.
>>> 2.    The CE WAN interface does include a new option in DHCPV6_NEW_OPTI=
ON1 in the ORO option of the SOLICIT to the server.  If the server is confi=
gured to return DHCPV6_NEW_OPTION1 to clients, then will the server reply w=
ith DHCPV6_NEW_OPTION1?
>>>=20
>>> Mark,
>>>=20
>>> Note Bernie agrees with how I and Wes Beebee (who I discussed this thre=
ad with) also interpreted RFC3736.  New options can be served by the statel=
ess DHCPv6 server without revising RFC3736.
>>>=20
>>> Thanks all,
>>>=20
>>> Hemant
>>>=20
>>> From:Bernie Volz (volz)=20
>>> Sent: Friday, April 03, 2015 7:33 AM
>>> To: Hemant Singh (shemant)
>>> Cc: Mark ZZZ Smith; STARK, BARBARA H; Brian Haberman; ipv6@ietf.org; Ra=
lph Droms (rdroms); Ted Lemon
>>> Subject: Re: RA Option Guidelines
>>>=20
>>> I didn't study the complete thread but I am sure everyone would underst=
and that new options should be allowed to be requested. The ORO list cannot=
 be frozen ... At the time the rfc was written, that was the list. But new =
option documents are not required
to update RFC3736.
>>>=20
>>> There are no interop issues either as if either side (client or server)=
 doesn't know of an option, it just doesn't include or ignores it.
>>>=20
>>> - Bernie (from iPad)
>>>=20
>>>> On Apr 3, 2015, at 7:09 AM, Hemant Singh (shemant) <shemant@cisco.com>=
 wrote:
>>>> Could the DHCPv6 gurus in Ralph, Bernie, and Ted please help resolve t=
his thread for stateless DHCPv6 current vs. future options and the ORO opti=
on.=20
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Hemant
>>>>=20
>>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>>> Sent: Thursday, April 02, 2015 10:19 PM
>>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@iet=
f.org
>>>> Subject: Re: RA Option Guidelines
>>>>=20
>>>> Hi Hemant,
>>>>=20
>>>>=20
>>>> ________________________________
>>>> From: Hemant Singh (shemant) <shemant@cisco.com>
>>>> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "STARK, BARBARA H" <bs=
7652@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <=
ipv6@ietf.org>=20
>>>> Sent: Friday, 3 April 2015, 6:07
>>>> Subject: RE: RA Option Guidelines
>>>>=20
>>>>=20
>>>>=20
>>>> Mark,
>>>>=20
>>>> The stateless DHCPv6 server in RFC3736 allows for new options to be se=
rved by the stateless server.  Read the first paragraph of section 5.3 in R=
FC3736.
>>>>=20
>>>> / So there are a few reasons why I wouldn't come to that conclusion wi=
thout some very careful reading:
>>>>=20
>>>> / - The explicitly identified set of required and optional DHCPv6 opti=
ons that can be supported by a stateless DHCPv6 server
>>>>=20
>>>> / - The lack of any overt discussion that this set of required and opt=
ional DHCPv6 options are a minimum, and that further DHCPv6 options could b=
e provided by a stateless DHCPv6 server if supported by the implementation,=
 are appropriate and requested by
the
>> client. It being a minimum is subtly eluded to in a few sentences in the=
 Abstract and the Introduction, however I think they could easily be missed=
. I'd expect that if this is the case, it is much clearer and obvious.
>>>> / - I think text you refer to in 5.3, "Clients and servers use the fol=
lowing options to pass configuration information to clients; note that othe=
r options for configuration information may be specified in future Internet=
 Standards:" reads to me like a later
version of this RFC will specify more stateless DHCPv6 server supported opt=
ions. A statement such as "Other additional DHCPv6 options appropriate for =
stateless DHCPv6 operation may be supported by an implementation." would ma=
ke it much clearer that the supported
options were up to the implementer once the minimum had been implemented.
>>>>=20
>>>> / So if I were implementing a stateless DHCPv6 server as per RFC3736, =
I'd think the implementation was complete when I had implemented the option=
s specified. I wouldn't put any effort into making it also transparent to a=
ny options that weren't identified
in RFC3736, as there is no text discussing that.
>>>>=20
>>>> So the new options you want to serve can be served by the CE stateless=
 DHCPv6 server.  Now, if the service provider configures his/her DHCPv6 ser=
ver to return new options to the CE WAN interface address acquisition, the =
CE uses the options on the LAN.=20
See bullet L-12 of RFC 7084.  Existing RFCs support your use case and no dh=
cpv6 relay is required in the CE.
>>>>=20
>>>> / I also cannot find text in RFC3315 or its updates on how to handle r=
eceived options that were not requested by the client in the Option Request=
 Option. So if the CE WAN DHCPv6 client doesn't request an option in its OR=
O to the SP's DHCPv6 server, I don't
think it is possible for the CE to pass options it doesn't know about onto =
the downstream LAN devices that do understand those DHCPv6 options.
>>>>=20
>>>> / If it is possible to send a DHCPv6 client "ORO type" options that it=
 didn't request, then the behaviour is still ambiguous. If the DHCPv6 clien=
t is a host, then it would be quite reasonable and expected to silently ign=
ore those received unknown options.
However, if the DHCPv6 client is on the WAN side of a CE device, then those=
 options should instead be passed to the LAN DHCPv6 server, which presumabl=
y should know how to correctly handle options it doesn't understand - in th=
e specific CE case, remember those
options in case a downstream LAN DHCPv6 client requests them. I think RFC70=
84 and it's ancestor RFC6204 are the only RFCs which describe this combinat=
ion of DHCPv6 client/server working together, and neither of them have disc=
ussed passing unknown options from
the DHCPv6 WAN client to the DHCPv6 LAN server.
>>>>=20
>>>> / Are you aware of any CE DHCPv6 WAN client/DHCPv6 LAN server implemen=
tations that are unknown DHCPv6 option transparent? Looking at RFC7084, thi=
s behaviour seems to be very explicitly prohibited, by limiting the LAN DHC=
Pv6 server support to only those
options described in RFC7084, or to those described in RFC3736.
>>>>=20
>>>> / I think this level of DHCPv6 option transparency between CE LAN atta=
ched hosts and the upstream SP's DHCPv6 server(s) can only be achieved by u=
sing a DHCPv6 relay on the CE LAN interface, because DHCPv6 relays are DHCP=
v6 option transparent. (A CE would
still have a DHCPv6 client on its WAN interface for its own parameters and =
DHCPv6-PD prefixes).
>>>>=20
>>>> / Regards,
>>>> / Mark.
>>>>=20
>>>>=20
>>>> Barbara,
>>>>=20
>>>> For your use case, the service provider configures the DHCPv6 server t=
o only serve options specified in RFC 7084.  Thus in this deployment no ext=
ra options exist to serve to the CE router LAN.
>>>>=20
>>>> Both use cases can be supported using existing RFC=E2=80=99s.
>>>>=20
>>>> Hemant
>>>>=20
>>>>=20
>>>>=20
>>>> From:Mark ZZZ Smith [mailto:markzzzsmith@yahoo.com.au]=20
>>>> Sent: Tuesday, March 31, 2015 9:52 PM
>>>> To: Hemant Singh (shemant); STARK, BARBARA H; Brian Haberman; ipv6@iet=
f.org
>>>> Subject: Re: RA Option Guidelines
>>>>=20
>>>> Hi Hemant,
>>>>=20
>>>>=20
>>>> ________________________________
>>>>=20
>>>> From:Hemant Singh (shemant) <shemant@cisco.com>
>>>> To: "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@=
yahoo.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <=
ipv6@ietf.org>=20
>>>> Sent: Wednesday, 1 April 2015, 1:27
>>>> Subject: RE: RA Option Guidelines
>>>>=20
>>>> Barbara,
>>>>=20
>>>> Thanks for replying.   =20
>>>>=20
>>>> Mark,
>>>>=20
>>>> If new DHCPv6 options are added to be supported by RFC3736, then the S=
P includes the new option in the DHCPv6 responses to the CPE WAN.  Then the=
 CPE includes the new option to its LAN DHCPv6 clients.
>>>>=20
>>>> /  So here is a scenario.
>>>>=20
>>>> / As an ISP, my customers have VoIP handsets that might support the OP=
TION_GEOLOCATION DHCPv6 option (I might know that a portion of them do, bec=
ause they've bought those VoIP handsets from me). How long is it going to t=
ake for me to get that option added
to
>> an updated RFC3736 and RFC7084, to get my CPE vendor to update and relea=
se their firmware to support that option, and test that new CPE firmware an=
d then to deploy that new firmware?
>>>>=20
>>>> / I think I'd be lucky if it only took 2 years.
>>>>=20
>>>> / A few months later I decide I want to provide OPTION_NEW_POSIX_TIMEZ=
ONE to my customers if their hosts request it. So now I have to try to get =
OPTION_NEW_POSIX_TIMEZONE added to the updated RFC3736, to get my CPE vendo=
r to update and release their firmware
>> to support that option, and test that new CPE firmware and then to deplo=
y that new firmware.
>>>>=20
>>>> / Now if I'm lucky I could add it to the draft for OPTION_GEOLOCATION,=
 so it is still "only" 2 years to get to a point where I could provide thos=
e options to my customers. But what if that draft has progressed too far th=
ough the IETF publishing process?
I have
>> to create a new draft updating the to be published draft.
>>>>=20
>>>> / So, to achieve what should be a simple task of providing location or=
 timezone information to customers' end hosts if they want it, we've just i=
ncurred the massive costs and time delays of the IETF publishing process, v=
endor firmware upgrades, firmware
testing
>> and firmware deployment. Sounds like how hard I understand it was to rol=
l out features like CLI in PSTN networks ...
>>>>=20
>>>> What is one option you'd like the host on the LAN to include so that w=
e can understand your use case better? =20
>>>>=20
>>>> / I'm going to make the problem much harder for you. I want the CPE to=
 "support" or better, be transparent to, all current and future DHCPv6 opti=
ons, and I don't want to have to upgrade or ask my customers to successfull=
y upgrade their CPE each and every
time
>>>> there is a new DHCPv6 option defined that might be useful to me and th=
em. I want to be able to provide service parameters to my customers hosts, =
directly or indirectly, without the software revision or model of their CPE=
 being the constraint.
>>>>=20
>>>> The SIP server is already included as one option supported by RFC3736.=
  Certainly, if the SIP server support is needed in the RA, I am open for i=
t since the RA already includes DNS information.
>>>>=20
>>>> / I don't think DNS in RAs was a good idea, and neither were SIP optio=
ns when they were proposed. See that time consuming and service disrupting =
firmware upgrade cycle for new DHCPv6 options? Same problem if you use RA o=
ptions to achieve the same goal.
New
>> firmware upgrade each time you want to support a new RA option.
>>>>=20
>>>> / Duplication between RA options and DHCPv6 options also causes more p=
roblems. Which is preferred? Are they treated equally or does one take prec=
edence over the other? As far as I'm aware, these questions haven't been an=
swered for the DHCPv6 DNS and RA
DNS
>> options yet. It might be simple to come up with a simple rule for more D=
HCPv6 options are duplicated into RAs, however their might be some specific=
 cases where the RA option value should be preferred over the DHCPv6 equiva=
lent option and vice-versa.=20
>>>>=20
>>>> However, I still ask the question as to how an RA received at the WAN =
of the CPE has its options propagated to the RA on the LAN?  At the time of=
 writing RFC 6204 or RFC 7084, there is no such provision between the RA re=
ceived on the WAN and the RA issued
on
>> the LAN of the CE router.
>>>>=20
>>>> / Use a DHCPv6 relay in the CPE. Then there isn't a problem, new DHCPv=
6 options that are unknown by the CPE will pass right through it transparen=
tly. The only complication is when stateful DHCPv6 addressing is used on th=
e CPE LAN interface, and I suggested
>> a hybrid mode of operation for a DHCPv6 server in that draft which I thi=
nk solves that problem.
>>>>=20
>>>> Others,
>>>>=20
>>>> Also, why does one need an RA Option Guideline?  RFC4861 specifies a T=
LV format and an option Type.  I don't see anything else needed if I need t=
o specify a new RA option.=20
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Hemant
>>>>=20
>>>> -----Original Message-----
>>>> From: STARK, BARBARA H [mailto:bs7652@att.com]=20
>>>> Sent: Tuesday, March 31, 2015 9:25 AM
>>>> To: Hemant Singh (shemant); Mark ZZZ Smith; Brian Haberman; ipv6@ietf.=
org
>>>> Subject: RE: RA Option Guidelines
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> RFC 7084 already says:=20
>>>> L-12:  The IPv6 CE router SHOULD make available a subset of DHCPv6
>>>>        options (as listed in Section 5.3 of [RFC3736]) received from
>>>>        the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
>>>>        server.
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>


From nobody Mon Apr  6 16:20:48 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F74E1B29DB for <ipv6@ietfa.amsl.com>; Mon,  6 Apr 2015 16:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.502
X-Spam-Level: 
X-Spam-Status: No, score=0.502 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 gAbyv4XouzBw for <ipv6@ietfa.amsl.com>; Mon,  6 Apr 2015 16:20:46 -0700 (PDT)
Received: from nm26-vm0.bullet.mail.bf1.yahoo.com (nm26-vm0.bullet.mail.bf1.yahoo.com [98.139.213.74]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B12BD1ACE7C for <ipv6@ietf.org>; Mon,  6 Apr 2015 16:20:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428362444; bh=yja9zS8P82DyfDJRcEirVNX8noDqZAuPKwJB3xUXM/s=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=P2Ey9WaGJVkqYTvEOcoFDba64D6noipiQyWMs9cfO4aKWdRl2LDF167oWjPlgdcoGgKHs11rSpuD++C5kza+1hr1AqCNOkTo9QTsNMpKIgMrDgtDKbJPjz1LEaZTQ15ONCTPCz5NAkwHMy4fIFrdDNGpfVY0ej++K+5veF6dhd/3HoHQoACv+7fAxyzr+2eSUAGpbBqhxOMjdLVH/ycVort13ZtculUmLm3NwmdwccIS7IQnTTQBJ7ZzLw/NUUbBzYx5zaivENEcPIcE2HZ+gcciW2KWu5aTwPd9Pl2wnIwyHrEHaB4N/BSRs1I3mKP8q823qW1fFe4M2fOE2N8mXA==
Received: from [66.196.81.170] by nm26.bullet.mail.bf1.yahoo.com with NNFMP; 06 Apr 2015 23:20:44 -0000
Received: from [98.139.212.244] by tm16.bullet.mail.bf1.yahoo.com with NNFMP;  06 Apr 2015 23:20:44 -0000
Received: from [127.0.0.1] by omp1053.mail.bf1.yahoo.com with NNFMP; 06 Apr 2015 23:20:44 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 762509.22347.bm@omp1053.mail.bf1.yahoo.com
X-YMail-OSG: ZmQOV1YVM1kGcGB4gbKHBViXQ_h5hO8Sm1dZVUu.oUFlY7RepAGiBku67q73qCD WPqP7xncHni2lL9SwK7J4lW9cYi5pc3DdsqQuKKdx8aggtJY0KeqtY4Xd34Umkr.m37jicPbTUEY BXwNAQiExMhGIO_NzBPnCV2ahyk5MTxXizTQY_IpnN7pA.U2tSLswGtrapTJbBXcg.3UtxymtKb1 9J4ZphQpoj6rsUgJ.ExzoF0UMKNLAXze96CqyI07aBqVX_my8xCvXudRq91u1tECL5KPvY0aRsmt gIgyQrvVOL5fYXogUloj7a_VvnSNGhnaoaxcMEgbFChrSU5T4fPOyQJ07yNZmdkIIw4O70wDBnYN eJxUgKI.H2BbyOLlSn3hprgP2c.v2FaaKhPwe8cBEW_78rWPGtWzuPCCobpNoUfUxJR.7TSoR2o3 r5_dxEq2oP2nhFE4b_qRyChWLc_P_kUDuOjk_Hq0vhFhJvwKHQoEtB66ac.2aZJuhqyzMxCNKcrX lUFq2U6YWg0F8HdnkLxWwa8R65Xwz8hMbpnN84s4dRlE-
Received: by 66.196.80.145; Mon, 06 Apr 2015 23:20:44 +0000 
Date: Mon, 6 Apr 2015 23:20:42 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Lorenzo Colitti <lorenzo@google.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <480425314.794654.1428362442633.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAKD1Yr1WnOSB_dmF4g1=-mUKoekzpPzFA4P6H=f3pYa7F1YO9A@mail.gmail.com>
References: <CAKD1Yr1WnOSB_dmF4g1=-mUKoekzpPzFA4P6H=f3pYa7F1YO9A@mail.gmail.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_794653_518878271.1428362442627"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9ihGf3Z6e_PSp-kYcc5j3px2Mqc>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2015 23:20:47 -0000

------=_Part_794653_518878271.1428362442627
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

So that sounds to me like a limitation in DHCPv6 that should be fixed, rather than trying to work around it with RAs.
I think the fundamental question about what to use RAs for comes to:
Do we bind/tightly couple the ability to deploy new applications to the features supported by the local router or not?

My understanding of the Internet architecture as described in RFC1958 is we should not.
      From: Lorenzo Colitti <lorenzo@google.com>
 To: Brian E Carpenter <brian.e.carpenter@gmail.com> 
Cc: Hemant Singh (shemant) <shemant@cisco.com>; "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@ietf.org> 
 Sent: Saturday, 4 April 2015, 23:26
 Subject: Re: RA Option Guidelines
   


On Sat, Apr 4, 2015 at 4:16 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

Do we actually agree on this, or rather on a slightly expanded version:

RA options should be limited to link-local/subnet specific parameters
(i.e., layer 3 parameters only) necessary for a simple unmanaged network.
The only exception is RFC 6106 (DNS Configuration). More complex situations
are better handled by other configuration metods such as DHCPv6.

No, I strongly disagree.
There are other differences between RA and DHCP. The most important one I see is that with DHCP it is basically impossible to change things dynamically.
Dynamically changing stateful parameters requires that the client implement reconfigure, and even then, it requires authentication, and requires either that the DHCP server never crashes, or that DHCPv6 failover is in use. Dynamically changing stateless options doesn't even seem possible at all - you have to wait until the client asks again, and the minimum time that must pass is 10 minutes (RFC 4242).

   
------=_Part_794653_518878271.1428362442627
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div dir=3D"ltr" id=3D"yui_3_16_=
0_1_1428362074839_3819"><span id=3D"yui_3_16_0_1_1428362074839_3818">So tha=
t sounds to me like a limitation in DHCPv6 that should be fixed, rather tha=
n trying to work around it with RAs.</span></div><div dir=3D"ltr" id=3D"yui=
_3_16_0_1_1428362074839_3817"><span><br></span></div><div dir=3D"ltr" id=3D=
"yui_3_16_0_1_1428362074839_3762"><span id=3D"yui_3_16_0_1_1428362074839_37=
66">I think the fundamental question about what to use RAs for comes to:</s=
pan></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428362074839_3762"><span><br=
></span></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428362074839_3762"><span=
 id=3D"yui_3_16_0_1_1428362074839_3791">Do we bind/tightly couple the abili=
ty to deploy new applications to the features supported by the local router=
 or not?<br></span></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428362074839_=
3762"><span><br></span></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428362074=
839_3762"><span id=3D"yui_3_16_0_1_1428362074839_3837">My understanding of =
the Internet architecture as described in RFC1958 is we should not.</span><=
/div><br>  <div style=3D"font-family: Helvetica Neue-Light, Helvetica Neue =
Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-si=
ze: 16px;" id=3D"yui_3_16_0_1_1428362074839_3739"> <div style=3D"font-famil=
y: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Ser=
if; font-size: 16px;" id=3D"yui_3_16_0_1_1428362074839_3738"> <div dir=3D"l=
tr" id=3D"yui_3_16_0_1_1428362074839_3737"> <hr size=3D"1" id=3D"yui_3_16_0=
_1_1428362074839_3761">  <font size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_1=
_1428362074839_3740"> <b id=3D"yui_3_16_0_1_1428362074839_3760"><span style=
=3D"font-weight:bold;" id=3D"yui_3_16_0_1_1428362074839_3759">From:</span><=
/b> Lorenzo Colitti &lt;lorenzo@google.com&gt;<br> <b id=3D"yui_3_16_0_1_14=
28362074839_3823"><span style=3D"font-weight: bold;" id=3D"yui_3_16_0_1_142=
8362074839_3822">To:</span></b> Brian E Carpenter &lt;brian.e.carpenter@gma=
il.com&gt; <br><b><span style=3D"font-weight: bold;">Cc:</span></b> Hemant =
Singh (shemant) &lt;shemant@cisco.com&gt;; "STARK, BARBARA H" &lt;bs7652@at=
t.com&gt;; Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt;; Brian Haberman=
 &lt;brian@innovationslab.net&gt;; "ipv6@ietf.org" &lt;ipv6@ietf.org&gt; <b=
r> <b id=3D"yui_3_16_0_1_1428362074839_3816"><span style=3D"font-weight: bo=
ld;" id=3D"yui_3_16_0_1_1428362074839_3815">Sent:</span></b> Saturday, 4 Ap=
ril 2015, 23:26<br> <b><span style=3D"font-weight: bold;">Subject:</span></=
b> Re: RA Option Guidelines<br> </font> </div> <div class=3D"y_msg_containe=
r" id=3D"yui_3_16_0_1_1428362074839_3925"><br><div id=3D"yiv0700614457"><di=
v id=3D"yui_3_16_0_1_1428362074839_3929"><div dir=3D"ltr" id=3D"yui_3_16_0_=
1_1428362074839_3928"><div class=3D"yiv0700614457gmail_extra" id=3D"yui_3_1=
6_0_1_1428362074839_3927"><div class=3D"qtdSeparateBR"><br><br></div><div c=
lass=3D"yiv0700614457yqt1735939391" id=3D"yiv0700614457yqtfd88173"><div cla=
ss=3D"yiv0700614457gmail_quote" id=3D"yui_3_16_0_1_1428362074839_3926">On S=
at, Apr 4, 2015 at 4:16 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a rel=
=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:brian.e.carpenter@gmail.com"=
 target=3D"_blank" href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carp=
enter@gmail.com</a>&gt;</span> wrote:<br clear=3D"none"><blockquote class=
=3D"yiv0700614457gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex;" id=3D"yui_3_16_0_1_1428362074839_3930">Do we ac=
tually agree on this, or rather on a slightly expanded version:<br clear=3D=
"none">
<span><br clear=3D"none">
RA options should be limited to link-local/subnet specific parameters<br cl=
ear=3D"none">
</span>(i.e., layer 3 parameters only) necessary for a simple unmanaged net=
work.<br clear=3D"none">
The only exception is RFC 6106 (DNS Configuration). More complex situations=
<br clear=3D"none">
are better handled by other configuration metods such as DHCPv6.</blockquot=
e><div id=3D"yui_3_16_0_1_1428362074839_3931"><br clear=3D"none"></div><div=
 id=3D"yui_3_16_0_1_1428362074839_3932">No, I strongly disagree.</div><div =
id=3D"yui_3_16_0_1_1428362074839_3933"><br clear=3D"none"></div><div id=3D"=
yui_3_16_0_1_1428362074839_3934">There are other differences between RA and=
 DHCP. The most important one I see is that with DHCP it is basically impos=
sible to change things dynamically.</div><div id=3D"yui_3_16_0_1_1428362074=
839_3935"><br clear=3D"none"></div><div id=3D"yui_3_16_0_1_1428362074839_39=
36">Dynamically changing stateful parameters requires that the client imple=
ment reconfigure, and even then, it requires authentication, and requires e=
ither that the DHCP server never crashes, or that DHCPv6 failover is in use=
. Dynamically changing stateless options doesn't even seem possible at all =
- you have to wait until the client asks again, and the minimum time that m=
ust pass is 10 minutes (RFC 4242).</div></div></div></div></div></div></div=
><br><br></div> </div> </div>  </div></body></html>
------=_Part_794653_518878271.1428362442627--


From nobody Mon Apr  6 17:29:40 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7328A1B2B7A for <ipv6@ietfa.amsl.com>; Mon,  6 Apr 2015 17:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 9c7z5AE0l73l for <ipv6@ietfa.amsl.com>; Mon,  6 Apr 2015 17:29:37 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001: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 9DA291B2B79 for <ipv6@ietf.org>; Mon,  6 Apr 2015 17:29:37 -0700 (PDT)
Received: by iggg4 with SMTP id g4so2412694igg.0 for <ipv6@ietf.org>; Mon, 06 Apr 2015 17:29:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KhdGCGKJ+I2TSB8OfwVenx9rc2NRUeIrVSNpjF9EI0M=; b=H4cahqsP7ke4paqUSf5UVMrPiZNQm/BKpjD0GQQh35mS8LBxNs7qdRByd2wCYrLSEg YJaPU61GaL7qjRPlzFWDlx/U0ObWul+TaIhZpunc0LysApPTpAmUM8hW6Mj0s1lVfyos tFYosKOMfdrDEdC4O20cBTBsCA2sPQbYgLRSZpar8NCxGZIXTj5nVMfvLsYQUeJNeSFg GwiO3hcyhU8rlA0kPY+c1T0SiCxpX3hkW2KEKWZOf2KLufbgt72yEy1u/i4WkBDpzzJ8 GuIJyRzvtlvG8GZAwbvaQJ6LsfE5SqYL7BQrJQWE+6QK9I3Ft3xCeVrq5FERUYIAKfXm foEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=KhdGCGKJ+I2TSB8OfwVenx9rc2NRUeIrVSNpjF9EI0M=; b=mfP3/c1+iVe0nitOAhPsJD+1/SVDcXGp7fBY/WuaLNLHSCv5Dx8p44OE5cRLFlJFnx TiPVVRobz6vVBD9ws9sjFrJas+nQwUAZDrflXt60mC74s/frP3vTf7XITI+AqMyy/FZL kjbb8g7PSELYBB5p/UKTfksmHU5P7TeJPKWlLvF+Xbt6SIYxmknwqxR3tnLKOO7L6glM OZuS5NrytLRxyKv9G5L5aiUa7RSI6WvnE+3L2h7ouruN0/cCv2mIa7fkh05gDprfv+dx 9/5/4WriP3H/uNlnzh2EYuQ9KAJCWBSG+Eb47gEZCoe7W1dI6YJR8X1SjXqmXBCSTkpO zZtg==
X-Gm-Message-State: ALoCoQmln0ffV6wscnwu9y1/x3EGObGagrrUDJvcN6BO/Shh4Hx9ocTNE5y2qzkJIxlMa1GqGz09
X-Received: by 10.50.79.197 with SMTP id l5mr1322098igx.39.1428366576815; Mon, 06 Apr 2015 17:29:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Mon, 6 Apr 2015 17:29:16 -0700 (PDT)
In-Reply-To: <480425314.794654.1428362442633.JavaMail.yahoo@mail.yahoo.com>
References: <CAKD1Yr1WnOSB_dmF4g1=-mUKoekzpPzFA4P6H=f3pYa7F1YO9A@mail.gmail.com> <480425314.794654.1428362442633.JavaMail.yahoo@mail.yahoo.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 7 Apr 2015 09:29:16 +0900
Message-ID: <CAKD1Yr16fa6tV23s6noV5F_45hJ6k0Pa01Eeg2XK_zzLUvF5rQ@mail.gmail.com>
Subject: Re: RA Option Guidelines
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Content-Type: multipart/alternative; boundary=089e013cc1686bb30105131782b0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5dGn5kEnI4nUfZFir9NhgvDYFGo>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 00:29:39 -0000

--089e013cc1686bb30105131782b0
Content-Type: text/plain; charset=UTF-8

Bear in mind that AIUI there is pretty strong consensus in the dhc working
group that DHCP should *not* be used for general application configuration,
but only for bootstrapping networking parameters.

On Tue, Apr 7, 2015 at 8:20 AM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
wrote:

> So that sounds to me like a limitation in DHCPv6 that should be fixed,
> rather than trying to work around it with RAs.
>
> I think the fundamental question about what to use RAs for comes to:
>
> Do we bind/tightly couple the ability to deploy new applications to the
> features supported by the local router or not?
>
> My understanding of the Internet architecture as described in RFC1958 is
> we should not.
>
>   ------------------------------
>  *From:* Lorenzo Colitti <lorenzo@google.com>
> *To:* Brian E Carpenter <brian.e.carpenter@gmail.com>
> *Cc:* Hemant Singh (shemant) <shemant@cisco.com>; "STARK, BARBARA H" <
> bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; Brian
> Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@ietf.org>
> *Sent:* Saturday, 4 April 2015, 23:26
> *Subject:* Re: RA Option Guidelines
>
>
>
> On Sat, Apr 4, 2015 at 4:16 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
> Do we actually agree on this, or rather on a slightly expanded version:
>
> RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only) necessary for a simple unmanaged network.
> The only exception is RFC 6106 (DNS Configuration). More complex situations
> are better handled by other configuration metods such as DHCPv6.
>
>
> No, I strongly disagree.
>
> There are other differences between RA and DHCP. The most important one I
> see is that with DHCP it is basically impossible to change things
> dynamically.
>
> Dynamically changing stateful parameters requires that the client
> implement reconfigure, and even then, it requires authentication, and
> requires either that the DHCP server never crashes, or that DHCPv6 failover
> is in use. Dynamically changing stateless options doesn't even seem
> possible at all - you have to wait until the client asks again, and the
> minimum time that must pass is 10 minutes (RFC 4242).
>
>
>

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

<div dir=3D"ltr">Bear in mind that AIUI there is pretty strong consensus in=
 the dhc working group that DHCP should *not* be used for general applicati=
on configuration, but only for bootstrapping networking parameters.</div><d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 7, 2015=
 at 8:20 AM, Mark ZZZ Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:markzzz=
smith@yahoo.com.au" target=3D"_blank">markzzzsmith@yahoo.com.au</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><div style=3D"color:#000;=
background-color:#fff;font-family:Helvetica Neue-Light,Helvetica Neue Light=
,Helvetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif;font-size:16px"><d=
iv dir=3D"ltr"><span>So that sounds to me like a limitation in DHCPv6 that =
should be fixed, rather than trying to work around it with RAs.</span></div=
><div dir=3D"ltr"><span><br></span></div><div dir=3D"ltr"><span>I think the=
 fundamental question about what to use RAs for comes to:</span></div><div =
dir=3D"ltr"><span><br></span></div><div dir=3D"ltr"><span>Do we bind/tightl=
y couple the ability to deploy new applications to the features supported b=
y the local router or not?<br></span></div><div dir=3D"ltr"><span><br></spa=
n></div><div dir=3D"ltr"><span>My understanding of the Internet architectur=
e as described in RFC1958 is we should not.</span></div><br>  <div style=3D=
"font-family:Helvetica Neue-Light,Helvetica Neue Light,Helvetica Neue,Helve=
tica,Arial,Lucida Grande,Sans-Serif;font-size:16px"> <div style=3D"font-fam=
ily:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif;f=
ont-size:16px"> <div dir=3D"ltr"> <hr size=3D"1">  <font face=3D"Arial"> <b=
><span style=3D"font-weight:bold">From:</span></b> Lorenzo Colitti &lt;<a h=
ref=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com</a>&=
gt;<span class=3D""><br> <b><span style=3D"font-weight:bold">To:</span></b>=
 Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" targe=
t=3D"_blank">brian.e.carpenter@gmail.com</a>&gt; <br></span><b><span style=
=3D"font-weight:bold">Cc:</span></b> Hemant Singh (shemant) &lt;<a href=3D"=
mailto:shemant@cisco.com" target=3D"_blank">shemant@cisco.com</a>&gt;; &quo=
t;STARK, BARBARA H&quot; &lt;<a href=3D"mailto:bs7652@att.com" target=3D"_b=
lank">bs7652@att.com</a>&gt;; Mark ZZZ Smith &lt;<a href=3D"mailto:markzzzs=
mith@yahoo.com.au" target=3D"_blank">markzzzsmith@yahoo.com.au</a>&gt;; Bri=
an Haberman &lt;<a href=3D"mailto:brian@innovationslab.net" target=3D"_blan=
k">brian@innovationslab.net</a>&gt;; &quot;<a href=3D"mailto:ipv6@ietf.org"=
 target=3D"_blank">ipv6@ietf.org</a>&quot; &lt;<a href=3D"mailto:ipv6@ietf.=
org" target=3D"_blank">ipv6@ietf.org</a>&gt; <br> <b><span style=3D"font-we=
ight:bold">Sent:</span></b> Saturday, 4 April 2015, 23:26<span class=3D""><=
br> <b><span style=3D"font-weight:bold">Subject:</span></b> Re: RA Option G=
uidelines<br> </span></font> </div> <div><br><div><div><div dir=3D"ltr"><di=
v><div><br><br></div><div><div class=3D"h5"><div><div>On Sat, Apr 4, 2015 a=
t 4:16 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a rel=3D"nofollow" shap=
e=3D"rect" href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">br=
ian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br clear=3D"none"><blockquo=
te style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Do we actually agree on this, or rather on a slightly expanded version:<br =
clear=3D"none">
<span><br clear=3D"none">
RA options should be limited to link-local/subnet specific parameters<br cl=
ear=3D"none">
</span>(i.e., layer 3 parameters only) necessary for a simple unmanaged net=
work.<br clear=3D"none">
The only exception is RFC 6106 (DNS Configuration). More complex situations=
<br clear=3D"none">
are better handled by other configuration metods such as DHCPv6.</blockquot=
e><div><br clear=3D"none"></div><div>No, I strongly disagree.</div><div><br=
 clear=3D"none"></div><div>There are other differences between RA and DHCP.=
 The most important one I see is that with DHCP it is basically impossible =
to change things dynamically.</div><div><br clear=3D"none"></div><div>Dynam=
ically changing stateful parameters requires that the client implement reco=
nfigure, and even then, it requires authentication, and requires either tha=
t the DHCP server never crashes, or that DHCPv6 failover is in use. Dynamic=
ally changing stateless options doesn&#39;t even seem possible at all - you=
 have to wait until the client asks again, and the minimum time that must p=
ass is 10 minutes (RFC 4242).</div></div></div></div></div></div></div></di=
v></div><br><br></div> </div> </div>  </div></div></blockquote></div><br></=
div>

--089e013cc1686bb30105131782b0--


From nobody Mon Apr  6 20:07:48 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C862A1AD259; Mon,  6 Apr 2015 20:07: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_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBr01221434F; Mon,  6 Apr 2015 20:07:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C888C1A6FF7; Mon,  6 Apr 2015 20:07:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Subject: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150407030724.32439.29818.idtracker@ietfa.amsl.com>
Date: Mon, 06 Apr 2015 20:07:24 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SC-Wv8HC6lJgSqCu2WKXAAQJIO8>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 03:07:47 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-6man-resilient-rs-05: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I'm piling on Barry's Comment as a Discuss, which should be easy to
discuss, but ... in this text:

3.  Configuring the use of retransmissions

   Implementations of this specification MAY provide a configuration
   option to enable or disable the use of such potentially infinite
   retransmissions.  If the implementation provides such a configuration
   option, it MUST be able to enable/disable retransmissions on a per-
   interface basis.
   
You can tell me that it's a LAN, so the transport ADs can go back to
sleep, but I was surprised that this configuration option was a MAY. 

I was also surprised that there was no guidance about the default setting
(on or off), but let's start with the MAY.

IP does get tunneled to new and exciting places ... and infinite
retransmissions are infinite ...


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Extreme nit alert:

   In general, the delay may be unacceptable in some
   scenarios.
   
would make more sense to me without the "in general".



From nobody Tue Apr  7 05:02:58 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D701B3523 for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 05:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxDdr7pPCefd for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 05:02:45 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45C931B3513 for <ipv6@ietf.org>; Tue,  7 Apr 2015 05:02:43 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t37C2eTw031763 for <ipv6@ietf.org>; Tue, 7 Apr 2015 14:02:40 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 507E9202CC2 for <ipv6@ietf.org>; Tue,  7 Apr 2015 14:03:43 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 48D4F202C7E for <ipv6@ietf.org>; Tue,  7 Apr 2015 14:03:43 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t37C2Ki0024725 for <ipv6@ietf.org>; Tue, 7 Apr 2015 14:02:40 +0200
Message-ID: <5523C74C.4050201@gmail.com>
Date: Tue, 07 Apr 2015 14:02:20 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: RA Option Guidelines
References: <5515A9A7.3080508@innovationslab.net> <281018849.2116525.1427767749309.JavaMail.yahoo@mail.yahoo.com> <75B6FA9F576969419E42BECB86CB1B8916834620@xmb-rcd-x06.cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F8C7AF@GAALPA1MSGUSRBF.ITServices.sbc.com> <75B6FA9F576969419E42BECB86CB1B89168346DA@xmb-rcd-x06.cisco.com> <551AF4E5.7000207@gmail.com> <551EE710.2050301@gmail.com>
In-Reply-To: <551EE710.2050301@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/71Asec6ypuxGksR5wqiB82g6_p0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 12:02:51 -0000

Le 03/04/2015 21:16, Brian E Carpenter a écrit :
> I'm glad y'all have got DHCPv6 sorted out. Now, as to the original
> subject of this thread: On 01/04/2015 08:26, Brian E Carpenter
> wrote:
>> On 01/04/2015 03:27, Hemant Singh (shemant) wrote: ...
>>> Also, why does one need an RA Option Guideline?  RFC4861
>>> specifies a TLV format and an option Type.   I don't see
>>> anything else needed if I need to specify a new RA option.
>>
>> Section 9 "Extensibility - Option Processing" gives some general
>> advice, too.
>>
>> The question is what do we collectively want. I liked Mark's
>> restrictive criterion "RA options should be limited to
>> link-local/subnet specific parameters (i.e., layer 3 parameters
>> only)". DHCPv6 is available as the kitchen sink protocol for other
>> stuff. I'm not sure whether we want to write this down; it seems
>> as if  one or two sentences should be added to RFC4861bis if there
>> ever is such a document.
>
> Do we actually agree on this, or rather on a slightly expanded
> version:
>
> RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only) necessary for a simple unmanaged
> network. The only exception is RFC 6106 (DNS Configuration). More
> complex situations are better handled by other configuration metods
> such as DHCPv6.

It makes sense.

But, would it be possible to tell link-local subnet of a particular
Router?  I am asking because currently it is the link-local subnet of
one particular interface, the "on-link" prefix;  and it would be good to
allow a prefix in one subnet of an interface of a router be announced on
another interface of same router as "other prefix nearby".

And still forbid one Router to read an RA and propagate its contents
further down the network.

Alex


>
> Brian
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From nobody Tue Apr  7 06:32:38 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D82011B35B3; Tue,  7 Apr 2015 06:32: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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpwIPgAgeaI6; Tue,  7 Apr 2015 06:32:34 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE0531B3595; Tue,  7 Apr 2015 06:30:56 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 8356F880E2; Tue,  7 Apr 2015 06:30:56 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id E706A13682CC; Tue,  7 Apr 2015 06:30:55 -0700 (PDT)
Message-ID: <5523DC07.3040008@innovationslab.net>
Date: Tue, 07 Apr 2015 09:30:47 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
Subject: Re: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
References: <20150407030724.32439.29818.idtracker@ietfa.amsl.com>
In-Reply-To: <20150407030724.32439.29818.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9H3jji28vX3RnAhJJrFrDEkPt0ARRN9DK"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Dq8FzyhZV9QsQTs1Sz8MSq9A6_w>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 13:32:36 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9H3jji28vX3RnAhJJrFrDEkPt0ARRN9DK
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi all,

On 4/6/15 11:07 PM, Spencer Dawkins wrote:
> Spencer Dawkins has entered the following ballot position for
> draft-ietf-6man-resilient-rs-05: Discuss
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this=

> introductory paragraph, however.)
>=20
>=20
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.htm=
l
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> I'm piling on Barry's Comment as a Discuss, which should be easy to
> discuss, but ... in this text:
>=20
> 3.  Configuring the use of retransmissions
>=20
>    Implementations of this specification MAY provide a configuration
>    option to enable or disable the use of such potentially infinite
>    retransmissions.  If the implementation provides such a configuratio=
n
>    option, it MUST be able to enable/disable retransmissions on a per-
>    interface basis.
>   =20
> You can tell me that it's a LAN, so the transport ADs can go back to
> sleep, but I was surprised that this configuration option was a MAY.=20
>=20
> I was also surprised that there was no guidance about the default setti=
ng
> (on or off), but let's start with the MAY.
>=20
> IP does get tunneled to new and exciting places ... and infinite
> retransmissions are infinite ...

I went back and re-read Barry's Comment and the resulting response and
felt unsatisfied.

Barry & Spencer, let me know if I am misinterpreting your concerns...

It appears odd to give such concrete guidance as "enable/disable
retransmissions on a per-interface basis" for a function that is
completely optional.  After some thought, I am trying to figure out why
it would be optional since typical NA/NS/RA/RS functionality is
per-interface anyway.

Given what is being described, I would think we would want to encourage
implementers to provide a configuration option rather than make it
optional.  The text could be re-written (without 2119 keywords) as such:

NEW:
Implementations of this specification are encouraged to provide a
configuration option to enable or disable potentially infinite RS
retransmissions. Providing an option to enable/disable retransmissions
on a per-interface basis allows network operators to configure RS
behavior most applicable to each connected link.

Regards,
Brian

>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> Extreme nit alert:
>=20
>    In general, the delay may be unacceptable in some
>    scenarios.
>   =20
> would make more sense to me without the "in general".
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20
>=20


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

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

iQEcBAEBCAAGBQJVI9wHAAoJEBOZRqCi7goqvBYH/2Di1yQX2M3Iy3PGRmLV81TC
4GKKgHU+20pcliOLQJ45At4YPqHqO3BANp45hWxAiDutu2OSQfc1NGV3JVDxutyM
VeElpYEm30JYO/Zlc9zcjAadScr31OZLFybtX3FHfBLR0pAN3tQWlPr7SYt717+G
39AbKdy/C/rj1GdkAX2AdJL1pDjdKLnvGgO6HA509CY1ea2N+pH8Nzts7fvxVPGV
+K/AxfCCCldZ7swtvFnbvyzZrylgnIjIkNwn2jmCm9pTGOCLPZ8AlohOTYb19lA7
n5bwpdT2oAghf76+WsbGd0SipMH2a/FzK+qvDV9yJterCiDi5gZ2OpG2YtQvl0w=
=Q+Pe
-----END PGP SIGNATURE-----

--9H3jji28vX3RnAhJJrFrDEkPt0ARRN9DK--


From nobody Tue Apr  7 08:06:48 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8751B36BA; Tue,  7 Apr 2015 08:06:47 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zXMefeFkUZPC; Tue,  7 Apr 2015 08:06:44 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::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 6E1921B36CC; Tue,  7 Apr 2015 08:06:30 -0700 (PDT)
Received: by lboc7 with SMTP id c7so44855522lbo.1; Tue, 07 Apr 2015 08:06:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tN8kfMHSu8tVogVbfxNW+GTB2ebTMW2cR/jVjlp5XNg=; b=PdbSGHFWcJDlROjT3Q4nzagWqkA+VGSbmd5TIl5ZFngRDPkun33ZHH7USyrhstZ/26 wH0HFLv41OuFWeGC8sIdCirhXd46OWU4f+9nhAmH+pH9UCz9/WslPenP7cx6lzDsIxeM EElz+qtvCBZTOfVC7NiPA7nZbEvndL5up4G1v4r1UlK46z1RUfwZPoTZAboOk9fYsaQJ J0LIJ+JXXlj70jPCQiBZDodP73xvQzq3vO8QLQKZeIiZdWthqvJdMGoWuZX5Jk5DSGnH b8H69C6X5tEEGfetv9i/hSwywSGZd2++ThCiUxpUpRadJ5Vi955BENR3wu7nADlgN0eB E2uw==
MIME-Version: 1.0
X-Received: by 10.152.27.225 with SMTP id w1mr19070274lag.77.1428419188989; Tue, 07 Apr 2015 08:06:28 -0700 (PDT)
Received: by 10.152.129.3 with HTTP; Tue, 7 Apr 2015 08:06:28 -0700 (PDT)
In-Reply-To: <5523DC07.3040008@innovationslab.net>
References: <20150407030724.32439.29818.idtracker@ietfa.amsl.com> <5523DC07.3040008@innovationslab.net>
Date: Tue, 7 Apr 2015 10:06:28 -0500
Message-ID: <CAKKJt-cBnuood4hFxymPzZf1UBZ-BK8P042TRrELMSOnsJXLyA@mail.gmail.com>
Subject: Re: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=089e0158c45859a5fe051323c2e7
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lL7wDKhUuTvRa016eZQ5VfiNmHc>
Cc: ot@cisco.com, ipv6@ietf.org, The IESG <iesg@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 15:06:47 -0000

--089e0158c45859a5fe051323c2e7
Content-Type: text/plain; charset=UTF-8

Hi, Brian,

On Tue, Apr 7, 2015 at 8:30 AM, Brian Haberman <brian@innovationslab.net>
wrote:

> Hi all,
>
> On 4/6/15 11:07 PM, Spencer Dawkins wrote:
> > Spencer Dawkins has entered the following ballot position for
> > draft-ietf-6man-resilient-rs-05: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > I'm piling on Barry's Comment as a Discuss, which should be easy to
> > discuss, but ... in this text:
> >
> > 3.  Configuring the use of retransmissions
> >
> >    Implementations of this specification MAY provide a configuration
> >    option to enable or disable the use of such potentially infinite
> >    retransmissions.  If the implementation provides such a configuration
> >    option, it MUST be able to enable/disable retransmissions on a per-
> >    interface basis.
> >
> > You can tell me that it's a LAN, so the transport ADs can go back to
> > sleep, but I was surprised that this configuration option was a MAY.
> >
> > I was also surprised that there was no guidance about the default setting
> > (on or off), but let's start with the MAY.
> >
> > IP does get tunneled to new and exciting places ... and infinite
> > retransmissions are infinite ...
>
> I went back and re-read Barry's Comment and the resulting response and
> felt unsatisfied.
>
> Barry & Spencer, let me know if I am misinterpreting your concerns...
>
> It appears odd to give such concrete guidance as "enable/disable
> retransmissions on a per-interface basis" for a function that is
> completely optional.  After some thought, I am trying to figure out why
> it would be optional since typical NA/NS/RA/RS functionality is
> per-interface anyway.
>
> Given what is being described, I would think we would want to encourage
> implementers to provide a configuration option rather than make it
> optional.  The text could be re-written (without 2119 keywords) as such:
>
> NEW:
> Implementations of this specification are encouraged to provide a
> configuration option to enable or disable potentially infinite RS
> retransmissions. Providing an option to enable/disable retransmissions
> on a per-interface basis allows network operators to configure RS
> behavior most applicable to each connected link.


So, without 2119 keywords, I'd prefer "strongly encouraged", but
"encouraged" is an improvement.

My other point was - if there's a  configuration option for this, I would
prefer that the group make a recommendation about default settings.

I'd prefer "off by default", but could be convinced that "on by default"
has benefits that outweigh the costs.

Without a recommendation, I'm visualizing a network where the option isn't
set, some devices default "on" and others default "off", and hilarity
ensues.

Again, I could be convinced that's not a problem, but wanted to ask.

I'll clear when we figure out what I'm clearing in favor of, but I'll clear
for "encouraged" or anything stronger in the text you proposed.

Thanks!

Spencer

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

<div dir=3D"ltr">Hi, Brian,<div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Tue, Apr 7, 2015 at 8:30 AM, Brian Haberman <span dir=3D"ltr">=
&lt;<a href=3D"mailto:brian@innovationslab.net" target=3D"_blank">brian@inn=
ovationslab.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">Hi =
all,<br>
<div><div class=3D"h5"><br>
On 4/6/15 11:07 PM, Spencer Dawkins wrote:<br>
&gt; Spencer Dawkins has entered the following ballot position for<br>
&gt; draft-ietf-6man-resilient-rs-05: Discuss<br>
&gt;<br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt;<br>
&gt;<br>
&gt; Please refer to <a href=3D"http://www.ietf.org/iesg/statement/discuss-=
criteria.html" target=3D"_blank">http://www.ietf.org/iesg/statement/discuss=
-criteria.html</a><br>
&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;<br>
&gt;<br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-r=
s/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-6man-resil=
ient-rs/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; DISCUSS:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt;<br>
&gt; I&#39;m piling on Barry&#39;s Comment as a Discuss, which should be ea=
sy to<br>
&gt; discuss, but ... in this text:<br>
&gt;<br>
&gt; 3.=C2=A0 Configuring the use of retransmissions<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Implementations of this specification MAY provide a confi=
guration<br>
&gt;=C2=A0 =C2=A0 option to enable or disable the use of such potentially i=
nfinite<br>
&gt;=C2=A0 =C2=A0 retransmissions.=C2=A0 If the implementation provides suc=
h a configuration<br>
&gt;=C2=A0 =C2=A0 option, it MUST be able to enable/disable retransmissions=
 on a per-<br>
&gt;=C2=A0 =C2=A0 interface basis.<br>
&gt;<br>
&gt; You can tell me that it&#39;s a LAN, so the transport ADs can go back =
to<br>
&gt; sleep, but I was surprised that this configuration option was a MAY.<b=
r>
&gt;<br>
&gt; I was also surprised that there was no guidance about the default sett=
ing<br>
&gt; (on or off), but let&#39;s start with the MAY.<br>
&gt;<br>
&gt; IP does get tunneled to new and exciting places ... and infinite<br>
&gt; retransmissions are infinite ...<br>
<br>
</div></div>I went back and re-read Barry&#39;s Comment and the resulting r=
esponse and<br>
felt unsatisfied.<br>
<br>
Barry &amp; Spencer, let me know if I am misinterpreting your concerns...<b=
r>
<br>
It appears odd to give such concrete guidance as &quot;enable/disable<br>
retransmissions on a per-interface basis&quot; for a function that is<br>
completely optional.=C2=A0 After some thought, I am trying to figure out wh=
y<br>
it would be optional since typical NA/NS/RA/RS functionality is<br>
per-interface anyway.<br>
<br>
Given what is being described, I would think we would want to encourage<br>
implementers to provide a configuration option rather than make it<br>
optional.=C2=A0 The text could be re-written (without 2119 keywords) as suc=
h:<br>
<br>
NEW:<br>
Implementations of this specification are encouraged to provide a<br>
configuration option to enable or disable potentially infinite RS<br>
retransmissions. Providing an option to enable/disable retransmissions<br>
on a per-interface basis allows network operators to configure RS<br>
behavior most applicable to each connected link.</blockquote><div><br></div=
><div>So, without 2119 keywords, I&#39;d prefer &quot;strongly encouraged&q=
uot;, but &quot;encouraged&quot; is an improvement.</div><div><br></div><di=
v>My other point was - if there&#39;s a =C2=A0configuration option for this=
, I would prefer that the group make a recommendation about default setting=
s.=C2=A0</div><div><br></div><div>I&#39;d prefer &quot;off by default&quot;=
, but could be convinced that &quot;on by default&quot; has benefits that o=
utweigh the costs.=C2=A0</div><div><br></div><div>Without a recommendation,=
 I&#39;m visualizing a network where the option isn&#39;t set, some devices=
 default &quot;on&quot; and others default &quot;off&quot;, and hilarity en=
sues.</div><div><br></div><div>Again, I could be convinced that&#39;s not a=
 problem, but wanted to ask.</div><div><br></div><div>I&#39;ll clear when w=
e figure out what I&#39;m clearing in favor of, but I&#39;ll clear for &quo=
t;encouraged&quot; or anything stronger in the text you proposed.</div><div=
><br></div><div>Thanks!</div><div><br></div><div>Spencer</div></div></div><=
/div>

--089e0158c45859a5fe051323c2e7--


From nobody Tue Apr  7 09:40:45 2015
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086E21A8ADF for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 09:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82a6wnjLYrE3 for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 09:40:42 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2BEB21A8AC7 for <6man@ietf.org>; Tue,  7 Apr 2015 09:40:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 2BAB740332; Tue,  7 Apr 2015 18:40:41 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zpk26MpeWwK7; Tue,  7 Apr 2015 18:40:38 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:548a:7232:916e:4057]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id CFF6E40182; Tue,  7 Apr 2015 18:40:38 +0200 (CEST)
Message-ID: <55240885.9060200@globis.net>
Date: Tue, 07 Apr 2015 18:40:37 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: sarikaya@ieee.org
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com>
In-Reply-To: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/odkVvgnc4m2R24an34WKLAjf23U>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 16:40:44 -0000

Behcet Sarikaya wrote:
> Hi all,
>
> I submitted Rev. 06 of SADR Overview draft. This revision contains
> changes from IETF 92, namely:
>
> -corporate VPN  scenario in Section 3 contributed by Brian Carpenter
> as discussed in our F2F meeting in Dallas with the chairs, Brian,
> Pfister and myself.
>
> -Third party next hop text in Section 5 where the third part next hop
> issue has been left out of scope.
>
> I think this draft is ready for adoption call.
> Also contributors wishing to coauthor, send me an email.
>
> Regards,
>
> Behcet
>
>
> A new version of I-D, draft-sarikaya-6man-sadr-overview-06.txt
> has been successfully submitted by Behcet Sarikaya and posted to the
> IETF repository.
>
> Name:           draft-sarikaya-6man-sadr-overview
> Revision:       06
> Title:          Source Address Dependent Routing and Source Address
> Selection for IPv6 Hosts
> Document date:  2015-03-31
> Group:          Individual Submission
> Pages:          16
> URL:
> http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-06.txt
> Status:
> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
> Htmlized:       http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-06
>
> Abstract:
>     This document presents the source address dependent routing from the
>     host perspective.  Multihomed hosts and hosts with multiple
>     interfaces are considered.  Different architectures are introduced
>     and with their help, why source address selection and next hop
>     resolution in view of source address dependent routing is needed is
>     explained.  The document concludes with an informative guidelines on
>     the different solution approaches.
>

 > If host configuration is done using router advertisement messages
    then there is a need to define new router advertisement options for
    source address dependent routing.  These options include Route Prefix
    with Source Address/Prefix Option.  Other options such as Next Hop
    Address with Route Prefix option and Next Hop Address with Source
    Address and Route Prefix option will be considered in Section 5.3

Like many others, I still don't get the need for the Next Hop Address 
option, but I guess that could be thrashed out later.

I also still wonder whether the WG really needs three drafts that have 
considerable overlap, and yet still leave considerable gaps:

We have:

https://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06
https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04
and
https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00

But I'd expect any "SADR overview" to also cover router - router 
forwarding behaviour. Not just end host - router.

And was there ever any agreement reached on which was the more beautiful 
of https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04 or 
https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00 ?

In my mind, https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00  
is a logical progression from https://tools.ietf.org/html/rfc4191

But that also leaves major gaps on how routers would interact, plus any 
potential issues at an AS-boundary e.g. updating BCP38 to filter inbound 
and outbound SADR routes.

In short: I'm still not convinced we have the right problem statement.

regards,
RayH



From nobody Tue Apr  7 10:02:23 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481F01A8AA2 for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 10:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 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, SPF_PASS=-0.001] autolearn=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 ZbvkIVugRRUd for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 10:02:16 -0700 (PDT)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::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 2ED781A8A85 for <6man@ietf.org>; Tue,  7 Apr 2015 10:02:13 -0700 (PDT)
Received: by lbbuc2 with SMTP id uc2so44164513lbb.2 for <6man@ietf.org>; Tue, 07 Apr 2015 10:02:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=+sUFedcJw8jRSn99UuUx1CCIDDKkZJTNi2BW7LHvGDs=; b=ib8/PS5/CvgXvzV6KjraMfvWE4Wb25BZ17AOJfDAMNjclzEXInqu40KdgyL3+I3cpK v0P01i0pFys0hyg6kJADeW/eA39KRY3KqBa/9tuDPDTS3+CdhHEqKfZZRiQxwdEaVMw+ bxQEMSLy0KwCW50YzpX7JGZrBFZ3VzhykYeqirRwI51X/3AAxUHYzasSTj0h5JDssvlM XJ92P9W4BKP7BYpCN3qVXSBLR1FkUoRtl3v7ifiFQXl1i8AlycFST+njeO8X4EJOedcx W6lLd/SEDM1S9gEetqgxG2uh7tH6T0vXAi5332bR/JYsfCGnyfP68GJOHWxTIFB/6FUZ kcIA==
MIME-Version: 1.0
X-Received: by 10.152.19.132 with SMTP id f4mr1108031lae.115.1428426131601; Tue, 07 Apr 2015 10:02:11 -0700 (PDT)
Received: by 10.114.59.103 with HTTP; Tue, 7 Apr 2015 10:02:11 -0700 (PDT)
In-Reply-To: <55240885.9060200@globis.net>
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com> <55240885.9060200@globis.net>
Date: Tue, 7 Apr 2015 12:02:11 -0500
Message-ID: <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ray Hunter <v6ops@globis.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tHaBN9XaYZE4LSYagnsq5ynAqG4>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 17:02:22 -0000

Hi Ray,

On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <v6ops@globis.net> wrote:
>
>
> Behcet Sarikaya wrote:
>>
>> Hi all,
>>
>> I submitted Rev. 06 of SADR Overview draft. This revision contains
>> changes from IETF 92, namely:
>>
>> -corporate VPN  scenario in Section 3 contributed by Brian Carpenter
>> as discussed in our F2F meeting in Dallas with the chairs, Brian,
>> Pfister and myself.
>>
>> -Third party next hop text in Section 5 where the third part next hop
>> issue has been left out of scope.
>>
>> I think this draft is ready for adoption call.
>> Also contributors wishing to coauthor, send me an email.
>>
>> Regards,
>>
>> Behcet
>>
>>
>> A new version of I-D, draft-sarikaya-6man-sadr-overview-06.txt
>> has been successfully submitted by Behcet Sarikaya and posted to the
>> IETF repository.
>>
>> Name:           draft-sarikaya-6man-sadr-overview
>> Revision:       06
>> Title:          Source Address Dependent Routing and Source Address
>> Selection for IPv6 Hosts
>> Document date:  2015-03-31
>> Group:          Individual Submission
>> Pages:          16
>> URL:
>>
>> http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-06.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
>> Htmlized:
>> http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-06
>>
>> Abstract:
>>     This document presents the source address dependent routing from the
>>     host perspective.  Multihomed hosts and hosts with multiple
>>     interfaces are considered.  Different architectures are introduced
>>     and with their help, why source address selection and next hop
>>     resolution in view of source address dependent routing is needed is
>>     explained.  The document concludes with an informative guidelines on
>>     the different solution approaches.
>>
>
>> If host configuration is done using router advertisement messages
>    then there is a need to define new router advertisement options for
>    source address dependent routing.  These options include Route Prefix
>    with Source Address/Prefix Option.  Other options such as Next Hop
>    Address with Route Prefix option and Next Hop Address with Source
>    Address and Route Prefix option will be considered in Section 5.3
>
> Like many others, I still don't get the need for the Next Hop Address
> option, but I guess that could be thrashed out later.

More or less. Section 5.3 makes the third party next hop work out of
scope, maybe sometime in the future someone will be able to come up
with a good use case, I believe so.

>
> I also still wonder whether the WG really needs three drafts that have
> considerable overlap, and yet still leave considerable gaps:
>

One is overview the other two are solution documents.

> We have:
>
> https://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06
> https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04
> and
> https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00
>
> But I'd expect any "SADR overview" to also cover router - router forwarding
> behaviour. Not just end host - router.

Can you offer some text?

>
> And was there ever any agreement reached on which was the more beautiful of
> https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04

This should be
draft-sarikaya-6man-sadr-ra

 we do not plan on pursuing draft-sarikaya-6man-next-hop-ra-04 any
further because of the third part next hop issue.

 or
> https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00 ?
>
> In my mind, https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00  is a
> logical progression from https://tools.ietf.org/html/rfc4191
>

The other approach is to define a new option as in
draft-sarikaya-6man-sadr-ra then we don't need an I flag. Also the
point you have below could be discussed there.

> But that also leaves major gaps on how routers would interact, plus any
> potential issues at an AS-boundary e.g. updating BCP38 to filter inbound and
> outbound SADR routes.

Currently we (Pfister and I) are discussing how to merge these two
solution documents. So I believe there will be one solution document
in the end.

>
> In short: I'm still not convinced we have the right problem statement.
>

Overview document is the one we have now after long discussions.
Of course it could be improved, the plan is to improve it as a WG draft.


> regards,
> RayH
>
>


From nobody Tue Apr  7 13:01:57 2015
Return-Path: <JuanCarlos.Zuniga@interdigital.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF971B3BBF for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 13:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.244
X-Spam-Level: 
X-Spam-Status: No, score=-1.244 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] autolearn=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 JELsyNtWAxB8 for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 13:01:54 -0700 (PDT)
Received: from smtp-in1.interdigital.com (smtp-in1.interdigital.com [64.208.228.133]) (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 75E5B1B3BBD for <ipv6@ietf.org>; Tue,  7 Apr 2015 13:01:52 -0700 (PDT)
X-ASG-Debug-ID: 1428436910-06daaa66b916a70001-WbpaHM
Received: from NISSONITE.InterDigital.com (nissonite.interdigital.com [10.2.64.252]) by smtp-in1.interdigital.com with ESMTP id HFmxkDUsTAR8w9iM (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Tue, 07 Apr 2015 16:01:50 -0400 (EDT)
X-Barracuda-Envelope-From: JuanCarlos.Zuniga@InterDigital.com
Received: from NABESITE.InterDigital.com ([fe80::4d8a:a889:67c2:f009]) by NISSONITE.InterDigital.com ([::1]) with mapi id 14.03.0210.002; Tue, 7 Apr 2015 16:01:50 -0400
From: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>
To: "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
X-ASG-Orig-Subj: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgGTuWtA
Date: Tue, 7 Apr 2015 20:01:50 +0000
Message-ID: <785DB11636645E438E2E096E1ADA47C410718A4A@NABESITE.InterDigital.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.3.2.202]
x-exclaimer-md-config: bb79a19d-f711-475c-a0f9-4d93b71c94dd
Content-Type: multipart/alternative; boundary="_000_785DB11636645E438E2E096E1ADA47C410718A4ANABESITEInterDi_"
MIME-Version: 1.0
X-Barracuda-Connect: nissonite.interdigital.com[10.2.64.252]
X-Barracuda-Start-Time: 1428436910
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: https://10.1.245.3:443/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at interdigital.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_SC0_MISMATCH_TO, HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.17646 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WZkjbDbI0goz1aBQGGmCu3UVAFI>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 20:01:55 -0000

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

QXV0aG9ycywNCg0KVGhlIFdHTEMgaGFzIGVuZGVkLiBQbGVhc2UgcHJvZHVjZSBhIG5ldyB2ZXJz
aW9uIG9mIHRoZSBkb2N1bWVudCB0YWtpbmcgaW50byBhY2NvdW50IHRoZSBjb21tZW50cyByZWNl
aXZlZCBvbiB0aGUgbGlzdHMgYW5kIHN1Ym1pdCBhIHN1bW1hcnkgb2YgdGhlIGRpZmZlcmVudCBp
c3N1ZXMgYWRkcmVzc2VkIGluIHRoaXMgbmV3IHZlcnNpb24uDQoNCkJlc3QsDQoNCkp1YW4gQ2Fy
bG9zDQooYXMgSW50LUFyZWEgV0cgY28tY2hhaXIpDQoNCkZyb206IFp1bmlnYSwgSnVhbiBDYXJs
b3MNClNlbnQ6IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDoyNyBQTQ0KVG86ICdpbnQtYXJlYUBp
ZXRmLm9yZyc7ICdpcHY2QGlldGYub3JnJw0KQ2M6ICdkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlw
djZAdG9vbHMuaWV0Zi5vcmcnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogU3Rh
cnQgb2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2DQoNCg0KRGVhciBJbnQt
QXJlYSBhbmQgNm1hbiBXR3MsDQoNCg0KDQpBdCB0aGUgSW50LUFyZWEgV0cgbWVldGluZyBpbiBE
YWxsYXMgdGhlcmUgd2VyZSBzb21lIGNvbW1lbnRzIG9uIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2Ni4gSXQgd2FzIGRlY2lkZWQgdG8gc3VibWl0IHRoZSBkb2N1bWVudCBmb3IgV0cgTGFzdCBD
YWxsIHRvIHRoZSBJbnQtQXJlYSAmIDZtYW4gV0dzIGFzIHNvb24gYXMgdGhlIGFncmVlZCBjaGFu
Z2VzIHdlcmUgbWFkZS4NCg0KDQoNClRoZSBkb2N1bWVudCBoYXMgbm93IGJlZW4gdXBkYXRlZCBh
Y2NvcmRpbmdseSwgc28gdGhpcyBlbWFpbCBzdGFydHMgYW4gSW50LUFyZWEvNm1hbiBXR3MgTGFz
dCBDYWxsIG9uOg0KDQoNCg0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1p
bnRhcmVhLWdyZS1pcHY2LTA0DQoNCg0KDQpQbGVhc2UgcmVzcG9uZCB0byB0aGlzIGVtYWlsIHRv
IHN1cHBvcnQgdGhlIGRvY3VtZW50IGFuZC9vciBzZW5kIGNvbW1lbnRzIGJ5IDIwMTUtMDQtMDYu
DQoNCg0KDQpJbiBhZGRpdGlvbiwgdG8gc2F0aXNmeSBSRkMgNjcwMiAiUHJvbW90aW5nIENvbXBs
aWFuY2Ugd2l0aCBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIChJUFIpIjoNCg0KQXJlIHlv
dSBwZXJzb25hbGx5IGF3YXJlIG9mIGFueSBJUFIgdGhhdCBhcHBsaWVzIHRvIGRyYWZ0LWlldGYt
aW50YXJlYS1ncmUtaXB2Nj8NCg0KSWYgc28sIGhhcyB0aGlzIElQUiBiZWVuIGRpc2Nsb3NlZCBp
biBjb21wbGlhbmNlIHdpdGggSUVURiBJUFIgcnVsZXM/DQoNCihTZWUgUkZDcyAzOTc5LCA0ODc5
LCAzNjY5LCBhbmQgNTM3OCBmb3IgbW9yZSBkZXRhaWxzLikNCg0KDQoNCkJlc3QsDQoNCg0KDQpK
dWFuIENhcmxvcyBadW5pZ2ENCihhcyBJbnQtQXJlYSBXRyBjby1jaGFpcikNCg0K

--_000_785DB11636645E438E2E096E1ADA47C410718A4ANABESITEInterDi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjwhLS0gVGVtcGxhdGUgZ2VuZXJhdGVkIGJ5IEV4Y2xh
aW1lciBTaWduYXR1cmUgTWFuYWdlciBFeGNoYW5nZSBFZGl0aW9uIG9uIDA0OjAxOjUwIFR1ZXNk
YXksIDcgQXByaWwgMjAxNSAtLT4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29u
dGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+
UC5JbXByaW50VW5pcXVlSUQgew0KCU1BUkdJTjogMGNtIDBjbSAwcHQNCn0NCkxJLkltcHJpbnRV
bmlxdWVJRCB7DQoJTUFSR0lOOiAwY20gMGNtIDBwdA0KfQ0KRElWLkltcHJpbnRVbmlxdWVJRCB7
DQoJTUFSR0lOOiAwY20gMGNtIDBwdA0KfQ0KVEFCTEUuSW1wcmludFVuaXF1ZUlEVGFibGUgew0K
CU1BUkdJTjogMGNtIDBjbSAwcHQNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFnZTogU2VjdGlvbjEN
Cn0NCjwvc3R5bGU+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRlbnQ9Ik1pY3Jvc29mdCBX
b3JkIDE1IChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRp
b25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAx
NSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFs
LCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgljb2xvcjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K
YTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjojOTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5N
c29QbGFpblRleHQsIGxpLk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFy
Z2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7
bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0
O30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEw
LjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2lu
OjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3Jk
U2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
ZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0t
LT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4N
CjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1s
PjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEi
IHZsaW5rPSIjOTU0RjcyIj4NCjxwPjwvcD4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+QXV0aG9ycyw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBXR0xDIGhhcyBlbmRlZC4g
UGxlYXNlIHByb2R1Y2UgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZG9jdW1lbnQgdGFraW5nIGludG8g
YWNjb3VudCB0aGUgY29tbWVudHMgcmVjZWl2ZWQgb24gdGhlIGxpc3RzIGFuZCBzdWJtaXQgYSBz
dW1tYXJ5IG9mIHRoZSBkaWZmZXJlbnQgaXNzdWVzIGFkZHJlc3NlZCBpbiB0aGlzIG5ldyB2ZXJz
aW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+QmVzdCw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkp1YW4gQ2FybG9zIDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4o
YXMgSW50LUFyZWEgV0cgY28tY2hhaXIpPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJs
dWUgMS41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFp1bmlnYSwg
SnVhbiBDYXJsb3MgPGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDoy
NyBQTTxicj4NCjxiPlRvOjwvYj4gJ2ludC1hcmVhQGlldGYub3JnJzsgJ2lwdjZAaWV0Zi5vcmcn
PGJyPg0KPGI+Q2M6PC9iPiAnZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYu
b3JnJzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gU3RhcnQg
b2YgV0dMQyBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5EZWFyIEludC1BcmVhIGFuZCA2bWFuIFdHcyw8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QXQgdGhlIEludC1BcmVhIFdHIG1lZXRpbmcgaW4g
RGFsbGFzIHRoZXJlIHdlcmUgc29tZSBjb21tZW50cyBvbiBkcmFmdC1pZXRmLWludGFyZWEtZ3Jl
LWlwdjYuIEl0IHdhcyBkZWNpZGVkIHRvIHN1Ym1pdCB0aGUgZG9jdW1lbnQgZm9yIFdHIExhc3Qg
Q2FsbCB0byB0aGUgSW50LUFyZWEgJmFtcDsgNm1hbiBXR3MgYXMgc29vbiBhcyB0aGUgYWdyZWVk
IGNoYW5nZXMgd2VyZSBtYWRlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5UaGUgZG9j
dW1lbnQgaGFzIG5vdyBiZWVuIHVwZGF0ZWQgYWNjb3JkaW5nbHksIHNvIHRoaXMgZW1haWwgc3Rh
cnRzIGFuIEludC1BcmVhLzZtYW4gV0dzIExhc3QgQ2FsbCBvbjo8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0
Zi1pbnRhcmVhLWdyZS1pcHY2LTA0Ij5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1p
ZXRmLWludGFyZWEtZ3JlLWlwdjYtMDQ8L2E+DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+UGxlYXNlIHJlc3BvbmQgdG8gdGhpcyBlbWFpbCB0byBzdXBwb3J0IHRoZSBkb2N1bWVudCBh
bmQvb3Igc2VuZCBjb21tZW50cyBieSAyMDE1LTA0LTA2LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij5JbiBhZGRpdGlvbiwgdG8gc2F0aXNmeSBSRkMgNjcwMiAmcXVvdDtQcm9tb3Rpbmcg
Q29tcGxpYW5jZSB3aXRoIEludGVsbGVjdHVhbCBQcm9wZXJ0eSBSaWdodHMgKElQUikmcXVvdDs6
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5BcmUgeW91IHBlcnNvbmFs
bHkgYXdhcmUgb2YgYW55IElQUiB0aGF0IGFwcGxpZXMgdG8gZHJhZnQtaWV0Zi1pbnRhcmVhLWdy
ZS1pcHY2PyZuYnNwOw0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5J
ZiBzbywgaGFzIHRoaXMgSVBSIGJlZW4gZGlzY2xvc2VkIGluIGNvbXBsaWFuY2Ugd2l0aCBJRVRG
IElQUiBydWxlcz88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPihTZWUg
UkZDcyAzOTc5LCA0ODc5LCAzNjY5LCBhbmQgNTM3OCBmb3IgbW9yZSBkZXRhaWxzLik8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QmVzdCw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+SnVhbiBDYXJsb3MgWnVuaWdhIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+KGFzIEludC1BcmVhIFdHIGNvLWNoYWlyKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHA+PC9wPg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_785DB11636645E438E2E096E1ADA47C410718A4ANABESITEInterDi_--


From nobody Tue Apr  7 13:26:15 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08EBF1B3C12; Tue,  7 Apr 2015 13:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IoxrXzMW-WwU; Tue,  7 Apr 2015 13:26:10 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0112.outbound.protection.outlook.com [65.55.169.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 951FF1B3C11; Tue,  7 Apr 2015 13:26:09 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.1.130.23; Tue, 7 Apr 2015 20:26:07 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Tue, 7 Apr 2015 20:26:07 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>, "draft-ietf-intarea-gre-ipv6@tools.ietf.org" <draft-ietf-intarea-gre-ipv6@tools.ietf.org>
Subject: RE: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Topic: Start of WGLC for draft-ietf-intarea-gre-ipv6
Thread-Index: AdBrHeUvMOmHRKvzSsuuWoWBg4qFNgGTuWtAAAEOeuA=
Date: Tue, 7 Apr 2015 20:26:07 +0000
Message-ID: <CO1PR05MB442581A7F90D01000C9FD37AEFD0@CO1PR05MB442.namprd05.prod.outlook.com>
References: <785DB11636645E438E2E096E1ADA47C410718A4A@NABESITE.InterDigital.com>
In-Reply-To: <785DB11636645E438E2E096E1ADA47C410718A4A@NABESITE.InterDigital.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
authentication-results: InterDigital.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB443;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(377454003)(19617315012)(2501003)(122556002)(40100003)(77156002)(86362001)(99286002)(54356999)(62966003)(76576001)(76176999)(15975445007)(102836002)(50986999)(16236675004)(19625215002)(2900100001)(92566002)(230783001)(2950100001)(19300405004)(46102003)(19580395003)(2656002)(19580405001)(87936001)(74316001)(33656002)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <CO1PR05MB4432ECBDC5348DBB65491BCAEFD0@CO1PR05MB443.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CO1PR05MB443; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB443; 
x-forefront-prvs: 0539EEBD11
Content-Type: multipart/alternative; boundary="_000_CO1PR05MB442581A7F90D01000C9FD37AEFD0CO1PR05MB442namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2015 20:26:07.3430 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB443
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KNaE8biguYnIAaMUlfkPcsteSZ4>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 20:26:12 -0000

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

Rm9sa3MsDQoNCkkgd2lsbCB0cnkgdG8gcHJvZHVjZSBhIG5ldyB2ZXJzaW9uIGJ5IENPQiB0b21v
cnJvdy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBS
b24NCg0KDQpGcm9tOiBadW5pZ2EsIEp1YW4gQ2FybG9zIFttYWlsdG86SnVhbkNhcmxvcy5adW5p
Z2FASW50ZXJEaWdpdGFsLmNvbV0NClNlbnQ6IFR1ZXNkYXksIEFwcmlsIDA3LCAyMDE1IDQ6MDIg
UE0NClRvOiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmcNCkNjOiBp
bnQtYXJlYUBpZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzsgaW50YXJlYS1jaGFpcnNAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJFOiBTdGFydCBvZiBXR0xDIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlw
djYNCg0KQXV0aG9ycywNCg0KVGhlIFdHTEMgaGFzIGVuZGVkLiBQbGVhc2UgcHJvZHVjZSBhIG5l
dyB2ZXJzaW9uIG9mIHRoZSBkb2N1bWVudCB0YWtpbmcgaW50byBhY2NvdW50IHRoZSBjb21tZW50
cyByZWNlaXZlZCBvbiB0aGUgbGlzdHMgYW5kIHN1Ym1pdCBhIHN1bW1hcnkgb2YgdGhlIGRpZmZl
cmVudCBpc3N1ZXMgYWRkcmVzc2VkIGluIHRoaXMgbmV3IHZlcnNpb24uDQoNCkJlc3QsDQoNCkp1
YW4gQ2FybG9zDQooYXMgSW50LUFyZWEgV0cgY28tY2hhaXIpDQoNCkZyb206IFp1bmlnYSwgSnVh
biBDYXJsb3MNClNlbnQ6IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDoyNyBQTQ0KVG86ICdpbnQt
YXJlYUBpZXRmLm9yZyc7ICdpcHY2QGlldGYub3JnJw0KQ2M6ICdkcmFmdC1pZXRmLWludGFyZWEt
Z3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmcnOyBpbnRhcmVhLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86
aW50YXJlYS1jaGFpcnNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBTdGFydCBvZiBXR0xDIGZvciBkcmFm
dC1pZXRmLWludGFyZWEtZ3JlLWlwdjYNCg0KDQpEZWFyIEludC1BcmVhIGFuZCA2bWFuIFdHcywN
Cg0KDQoNCkF0IHRoZSBJbnQtQXJlYSBXRyBtZWV0aW5nIGluIERhbGxhcyB0aGVyZSB3ZXJlIHNv
bWUgY29tbWVudHMgb24gZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LiBJdCB3YXMgZGVjaWRl
ZCB0byBzdWJtaXQgdGhlIGRvY3VtZW50IGZvciBXRyBMYXN0IENhbGwgdG8gdGhlIEludC1BcmVh
ICYgNm1hbiBXR3MgYXMgc29vbiBhcyB0aGUgYWdyZWVkIGNoYW5nZXMgd2VyZSBtYWRlLg0KDQoN
Cg0KVGhlIGRvY3VtZW50IGhhcyBub3cgYmVlbiB1cGRhdGVkIGFjY29yZGluZ2x5LCBzbyB0aGlz
IGVtYWlsIHN0YXJ0cyBhbiBJbnQtQXJlYS82bWFuIFdHcyBMYXN0IENhbGwgb246DQoNCg0KDQpo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYtMDQN
Cg0KDQoNClBsZWFzZSByZXNwb25kIHRvIHRoaXMgZW1haWwgdG8gc3VwcG9ydCB0aGUgZG9jdW1l
bnQgYW5kL29yIHNlbmQgY29tbWVudHMgYnkgMjAxNS0wNC0wNi4NCg0KDQoNCkluIGFkZGl0aW9u
LCB0byBzYXRpc2Z5IFJGQyA2NzAyICJQcm9tb3RpbmcgQ29tcGxpYW5jZSB3aXRoIEludGVsbGVj
dHVhbCBQcm9wZXJ0eSBSaWdodHMgKElQUikiOg0KDQpBcmUgeW91IHBlcnNvbmFsbHkgYXdhcmUg
b2YgYW55IElQUiB0aGF0IGFwcGxpZXMgdG8gZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2Pw0K
DQpJZiBzbywgaGFzIHRoaXMgSVBSIGJlZW4gZGlzY2xvc2VkIGluIGNvbXBsaWFuY2Ugd2l0aCBJ
RVRGIElQUiBydWxlcz8NCg0KKFNlZSBSRkNzIDM5NzksIDQ4NzksIDM2NjksIGFuZCA1Mzc4IGZv
ciBtb3JlIGRldGFpbHMuKQ0KDQoNCg0KQmVzdCwNCg0KDQoNCkp1YW4gQ2FybG9zIFp1bmlnYQ0K
KGFzIEludC1BcmVhIFdHIGNvLWNoYWlyKQ0KDQo=

--_000_CO1PR05MB442581A7F90D01000C9FD37AEFD0CO1PR05MB442namprd_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
OTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxp
Lk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnAuaW1wcmludHVuaXF1ZWlkLCBsaS5p
bXByaW50dW5pcXVlaWQsIGRpdi5pbXByaW50dW5pcXVlaWQNCgl7bXNvLXN0eWxlLW5hbWU6aW1w
cmludHVuaXF1ZWlkOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZv
bnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0K
c3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0IENoYXIiOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCI7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7
bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xv
cjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTIzDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5
N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9u
dC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47
DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7
cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48
IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0
PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5
b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9
IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Rm9sa3MsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5JIHdpbGwgdHJ5IHRvIHByb2R1Y2Ug
YSBuZXcgdmVyc2lvbiBieSBDT0IgdG9tb3Jyb3cuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgUm9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMu
MHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBadW5p
Z2EsIEp1YW4gQ2FybG9zIFttYWlsdG86SnVhbkNhcmxvcy5adW5pZ2FASW50ZXJEaWdpdGFsLmNv
bV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBBcHJpbCAwNywgMjAxNSA0OjAyIFBNPGJy
Pg0KPGI+VG86PC9iPiBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjZAdG9vbHMuaWV0Zi5vcmc8
YnI+DQo8Yj5DYzo8L2I+IGludC1hcmVhQGlldGYub3JnOyBpcHY2QGlldGYub3JnOyBpbnRhcmVh
LWNoYWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSRTogU3RhcnQgb2YgV0dMQyBm
b3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+QXV0aG9ycyw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZSBXR0xDIGhhcyBlbmRlZC4gUGxlYXNl
IHByb2R1Y2UgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZG9jdW1lbnQgdGFraW5nIGludG8gYWNjb3Vu
dCB0aGUgY29tbWVudHMgcmVjZWl2ZWQgb24gdGhlIGxpc3RzIGFuZCBzdWJtaXQgYSBzdW1tYXJ5
IG9mIHRoZSBkaWZmZXJlbnQgaXNzdWVzIGFkZHJlc3NlZCBpbiB0aGlzIG5ldyB2ZXJzaW9uLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+QmVzdCw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkp1YW4gQ2FybG9zIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj4oYXMgSW50
LUFyZWEgV0cgY28tY2hhaXIpPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41
cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVy
Om5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBp
biAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFp1bmlnYSwgSnVhbiBD
YXJsb3MgPGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgTWFyY2ggMzAsIDIwMTUgNDoyNyBQTTxi
cj4NCjxiPlRvOjwvYj4gJ2ludC1hcmVhQGlldGYub3JnJzsgJ2lwdjZAaWV0Zi5vcmcnPGJyPg0K
PGI+Q2M6PC9iPiAnZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2QHRvb2xzLmlldGYub3JnJzsg
PGEgaHJlZj0ibWFpbHRvOmludGFyZWEtY2hhaXJzQGlldGYub3JnIj4NCmludGFyZWEtY2hhaXJz
QGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9iPiBTdGFydCBvZiBXR0xDIGZvciBkcmFm
dC1pZXRmLWludGFyZWEtZ3JlLWlwdjY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPkRlYXIgSW50LUFyZWEgYW5kIDZtYW4gV0dzLDxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij5BdCB0aGUgSW50LUFyZWEgV0cgbWVldGluZyBpbiBEYWxsYXMgdGhlcmUgd2Vy
ZSBzb21lIGNvbW1lbnRzIG9uIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni4gSXQgd2FzIGRl
Y2lkZWQgdG8gc3VibWl0IHRoZSBkb2N1bWVudCBmb3IgV0cgTGFzdCBDYWxsIHRvIHRoZSBJbnQt
QXJlYSAmYW1wOyA2bWFuIFdHcyBhcyBzb29uIGFzIHRoZSBhZ3JlZWQgY2hhbmdlcyB3ZXJlIG1h
ZGUuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoZSBkb2N1bWVudCBoYXMgbm93IGJl
ZW4gdXBkYXRlZCBhY2NvcmRpbmdseSwgc28gdGhpcyBlbWFpbCBzdGFydHMgYW4gSW50LUFyZWEv
Nm1hbiBXR3MgTGFzdCBDYWxsIG9uOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48YSBo
cmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlw
djYtMDQiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaW50YXJlYS1ncmUt
aXB2Ni0wNDwvYT4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5QbGVhc2UgcmVzcG9u
ZCB0byB0aGlzIGVtYWlsIHRvIHN1cHBvcnQgdGhlIGRvY3VtZW50IGFuZC9vciBzZW5kIGNvbW1l
bnRzIGJ5IDIwMTUtMDQtMDYuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkluIGFkZGl0
aW9uLCB0byBzYXRpc2Z5IFJGQyA2NzAyICZxdW90O1Byb21vdGluZyBDb21wbGlhbmNlIHdpdGgg
SW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0cyAoSVBSKSZxdW90Ozo8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkFyZSB5b3UgcGVyc29uYWxseSBhd2FyZSBvZiBhbnkg
SVBSIHRoYXQgYXBwbGllcyB0byBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjY/Jm5ic3A7DQo8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPklmIHNvLCBoYXMgdGhpcyBJ
UFIgYmVlbiBkaXNjbG9zZWQgaW4gY29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzPzxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+KFNlZSBSRkNzIDM5NzksIDQ4Nzks
IDM2NjksIGFuZCA1Mzc4IGZvciBtb3JlIGRldGFpbHMuKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij5CZXN0LDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5i
c3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5KdWFuIENhcmxvcyBa
dW5pZ2EgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4oYXMgSW50LUFyZWEg
V0cgY28tY2hhaXIpPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4N
Cg==

--_000_CO1PR05MB442581A7F90D01000C9FD37AEFD0CO1PR05MB442namprd_--


From nobody Tue Apr  7 14:56:35 2015
Return-Path: <akatlas@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 862421A92EA; Tue,  7 Apr 2015 14:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.898
X-Spam-Level: 
X-Spam-Status: No, score=-101.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FH4I36P4exlr; Tue,  7 Apr 2015 14:56:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A075C1A92E3; Tue,  7 Apr 2015 14:56:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alia Atlas" <akatlas@gmail.com>
To: "The IESG" <iesg@ietf.org>
Subject: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150407215627.13544.1729.idtracker@ietfa.amsl.com>
Date: Tue, 07 Apr 2015 14:56:27 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CiyyHFCv40K6gSjjnxSIVCWgN-I>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 21:56:32 -0000

Alia Atlas has entered the following ballot position for
draft-ietf-6man-resilient-rs-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

To continue a bit on Spencer's Discuss and Barry's Comment, I'd prefer to
see a default for the configuration.  I'd assume it would be "off" to
continue to provide current behavior, but I don't really care.  
Consistency is my concern.



From nobody Tue Apr  7 16:18:40 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6791A8968 for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 16:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.802
X-Spam-Level: ***
X-Spam-Status: No, score=3.802 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 qg5n0CoUS2o9 for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 16:18:37 -0700 (PDT)
Received: from nm31-vm2.bullet.mail.bf1.yahoo.com (nm31-vm2.bullet.mail.bf1.yahoo.com [72.30.239.10]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80D171A895D for <ipv6@ietf.org>; Tue,  7 Apr 2015 16:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428448716; bh=EhAm2ZIUtxS/KceKbFhrPcpDn8Xf2i08v/SJcsxXIsM=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=txDDG8HnPxbaPs/S+eFlRtDQWdzNrDQte9nK3VXugfSmSx4bD/8q4Xx7GEzeHswFJe8cQMuNbtleIHvaMDR4jH6t2RHtBZXG2IR53afitAls1LDYvL3lk8gTwLkkxeUjPL8ZJoP2tppWO5LBiCKfVFN9v1u/V205Ty82l7sa8zKrf6pgS97ydswCoO7KkSvoT2w1kjh88GaZBAPJudgzA8HEleDl4Kpi2Y5n14rCwvIILH5KI+DsHDzZ8I5WNtpf24WsVAX2AqbPg3LUI/AJr8ACYIe2FVWTKXgtRXNnpQ3fEfm6S/tJM+BJjJsTiPPCAnXuux4J5huO042aqvdnCQ==
Received: from [98.139.170.182] by nm31.bullet.mail.bf1.yahoo.com with NNFMP;  07 Apr 2015 23:18:36 -0000
Received: from [98.139.212.209] by tm25.bullet.mail.bf1.yahoo.com with NNFMP;  07 Apr 2015 23:18:19 -0000
Received: from [127.0.0.1] by omp1018.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 23:18:19 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 570345.2532.bm@omp1018.mail.bf1.yahoo.com
X-YMail-OSG: KFP2WqoVM1kGz2uLEBQkdKchmJHU8HL3Qr8VUHyqpAS2xnKnF7mG3AyfYrSv1KG 3PyHwskhaP58sOIE8QfCwCSFzfMv2lPrD7AikLBtCHEUv4rt_qQco_97rUDLG5c1A8BQRQRjBiqq npZBrW4mkK4T5zkvEX2500FzGUTjIMzb66la9pFhfhftdccp9PJQDCya.adqeq7LnKpvUeBjzd55 AwfJZY1U2MDlxWePihOixJp5C3SLKEGQRh._fXks8AGZTj4fnWCLSDB4svOVy5HEmP482fmCExOf .vqHh6NYtfQIQByAVWUm.1xBBLm99EC.2ppvouyu5GbJu.g.Th3PIK2KAa3olvfd8AFA8kmAxvko 7TorDDIvcyNl0IckjVQXjdpykbCD48iW5Mx.6xxna8slD3VWKQ4zrS6ffssCjDtMECdCSEBKMozg VFHr2dKzJB9Iwzfd2T3SiqLZNFwNCO2HrDnYWDjInN9aEzSiCnAmOGJKDHF7MBFxltoYx_.RIfGp 6.Yh5vhTnwtRUJUoz0kYW3DTWG6LDlOfTnGWKMoLtcw--
Received: by 66.196.81.110; Tue, 07 Apr 2015 23:18:19 +0000 
Date: Tue, 7 Apr 2015 23:18:17 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Lorenzo Colitti <lorenzo@google.com>
Message-ID: <1990322011.1823999.1428448697972.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAKD1Yr16fa6tV23s6noV5F_45hJ6k0Pa01Eeg2XK_zzLUvF5rQ@mail.gmail.com>
References: <CAKD1Yr16fa6tV23s6noV5F_45hJ6k0Pa01Eeg2XK_zzLUvF5rQ@mail.gmail.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_1823998_328532286.1428448697968"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/52EcRAcvFIhmOTg1eXmxUogTQdU>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 23:18:39 -0000

------=_Part_1823998_328532286.1428448697968
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Lorenzo,


________________________________
From: Lorenzo Colitti <lorenzo@google.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au> 
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>; Hemant Singh (shemant) <shemant@cisco.com>; "STARK, BARBARA H" <bs7652@att.com>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@ietf.org> 
Sent: Tuesday, 7 April 2015, 10:29
Subject: Re: RA Option Guidelines



Bear in mind that AIUI there is pretty strong consensus in the dhc working group that DHCP should *not* be used for general application configuration, but only for bootstrapping networking parameters.


/ I'm not sure I understand their view, although if 'network parameters' has been generalised to include application parameters then it makes more sense.

/ I'm considering "network parameters" to mean only network layer/layer 3 parameters. Other parameters belong to other upper layers, and those other layers are only implemented in hosts (or the (control plane located) host component/functions of a router), so they're host oriented rather than network parameters. Going by the name, it sounds like the Dynamic Host Configuration Protocol is either the best or a likely candidate protocol to configure these transport layer+ parameters.
/ RFC5505, "Principles of Internet Host Configuration" also creates a configuration distinction between the network layer ("Internet-Layer Configuration") and the upper layers ("Higher-Layer Configuration"), and also discusses the issue of DHCPv6 learned parameters been less dynamic in "Relationship between IP Configuration and Service Discovery".
/ Regards,Mark.

On Tue, Apr 7, 2015 at 8:20 AM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au> wrote:

So that sounds to me like a limitation in DHCPv6 that should be fixed, rather than trying to work around it with RAs.
>
>
>I think the fundamental question about what to use RAs for comes to:
>
>
>Do we bind/tightly couple the ability to deploy new applications to the features supported by the local router or not?
>
>
>
>My understanding of the Internet architecture as described in RFC1958 is we should not.
>
>
>________________________________
> From: Lorenzo Colitti <lorenzo@google.com>
>To: Brian E Carpenter <brian.e.carpenter@gmail.com> 
>Cc: Hemant Singh (shemant) <shemant@cisco.com>; "STARK, BARBARA H" <bs7652@att.com>; Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; Brian Haberman <brian@innovationslab.net>; "ipv6@ietf.org" <ipv6@ietf.org> 
>Sent: Saturday, 4 April 2015, 23:26
>Subject: Re: RA Option Guidelines
> 
>
>
>
>
>
>On Sat, Apr 4, 2015 at 4:16 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
>Do we actually agree on this, or rather on a slightly expanded version:
>>
>>RA options should be limited to link-local/subnet specific parameters
>>(i.e., layer 3 parameters only) necessary for a simple unmanaged network.
>>The only exception is RFC 6106 (DNS Configuration). More complex situations
>>are better handled by other configuration metods such as DHCPv6.
>
>
>No, I strongly disagree.
>
>
>There are other differences between RA and DHCP. The most important one I see is that with DHCP it is basically impossible to change things dynamically.
>
>
>Dynamically changing stateful parameters requires that the client implement reconfigure, and even then, it requires authentication, and requires either that the DHCP server never crashes, or that DHCPv6 failover is in use. Dynamically changing stateless options doesn't even seem possible at all - you have to wait until the client asks again, and the minimum time that must pass is 10 minutes (RFC 4242).
>
>
------=_Part_1823998_328532286.1428448697968
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px">Hi Lorenzo,<br><br><br>_________=
_______________________<br>From: Lorenzo Colitti &lt;lorenzo@google.com&gt;=
<br>To: Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt; <br>Cc: Brian E Ca=
rpenter &lt;brian.e.carpenter@gmail.com&gt;; Hemant Singh (shemant) &lt;she=
mant@cisco.com&gt;; "STARK, BARBARA H" &lt;bs7652@att.com&gt;; Brian Haberm=
an &lt;brian@innovationslab.net&gt;; "ipv6@ietf.org" &lt;ipv6@ietf.org&gt; =
<br>Sent: Tuesday, 7 April 2015, 10:29<br>Subject: Re: RA Option Guidelines=
<br><br><br><br>Bear in mind that AIUI there is pretty strong consensus in =
the dhc working group that DHCP should *not* be used for general applicatio=
n configuration, but only for bootstrapping networking parameters.<br><br><=
br>/ I'm not sure I understand their view, although if 'network parameters'=
 has been generalised to include application parameters then it makes more =
sense.<br><br><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428444387939_27749">/ I'=
m considering "network parameters" to mean only network layer/layer 3 param=
eters. Other parameters belong to other upper layers, and those other layer=
s are only implemented in hosts (or the (control plane located) host compon=
ent/functions of a router), so they're host oriented rather than network pa=
rameters. Going by the name, it sounds like the Dynamic Host Configuration =
Protocol is either the best or a likely candidate protocol to configure the=
se transport layer+ parameters.</div><br><div dir=3D"ltr" id=3D"yui_3_16_0_=
1_1428444387939_27788">/ RFC5505, "Principles of Internet Host Configuratio=
n" also creates a configuration distinction between the network layer ("Int=
ernet-Layer Configuration") and the upper layers ("Higher-Layer Configurati=
on"), and also discusses the issue of DHCPv6 learned parameters been less d=
ynamic in "Relationship between IP Configuration and Service Discovery".</d=
iv><br><div id=3D"yui_3_16_0_1_1428444387939_27837">/ Regards,</div><div di=
r=3D"ltr" id=3D"yui_3_16_0_1_1428444387939_27838">Mark.</div><br><br>On Tue=
, Apr 7, 2015 at 8:20 AM, Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt; =
wrote:<br><br>So that sounds to me like a limitation in DHCPv6 that should =
be fixed, rather than trying to work around it with RAs.<br>&gt;<br>&gt;<br=
>&gt;I think the fundamental question about what to use RAs for comes to:<b=
r>&gt;<br>&gt;<br>&gt;Do we bind/tightly couple the ability to deploy new a=
pplications to the features supported by the local router or not?<br>&gt;<b=
r>&gt;<br>&gt;<br>&gt;My understanding of the Internet architecture as desc=
ribed in RFC1958 is we should not.<br>&gt;<br>&gt;<br>&gt;_________________=
_______________<br>&gt; From: Lorenzo Colitti &lt;lorenzo@google.com&gt;<br=
>&gt;To: Brian E Carpenter &lt;brian.e.carpenter@gmail.com&gt; <br>&gt;Cc: =
Hemant Singh (shemant) &lt;shemant@cisco.com&gt;; "STARK, BARBARA H" &lt;bs=
7652@att.com&gt;; Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt;; Brian H=
aberman &lt;brian@innovationslab.net&gt;; "ipv6@ietf.org" &lt;ipv6@ietf.org=
&gt; <br>&gt;Sent: Saturday, 4 April 2015, 23:26<br>&gt;Subject: Re: RA Opt=
ion Guidelines<br>&gt; <br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;On S=
at, Apr 4, 2015 at 4:16 AM, Brian E Carpenter &lt;brian.e.carpenter@gmail.c=
om&gt; wrote:<br>&gt;<br>&gt;Do we actually agree on this, or rather on a s=
lightly expanded version:<br>&gt;&gt;<br>&gt;&gt;RA options should be limit=
ed to link-local/subnet specific parameters<br>&gt;&gt;(i.e., layer 3 param=
eters only) necessary for a simple unmanaged network.<br>&gt;&gt;The only e=
xception is RFC 6106 (DNS Configuration). More complex situations<br>&gt;&g=
t;are better handled by other configuration metods such as DHCPv6.<br>&gt;<=
br>&gt;<br>&gt;No, I strongly disagree.<br>&gt;<br>&gt;<br>&gt;There are ot=
her differences between RA and DHCP. The most important one I see is that w=
ith DHCP it is basically impossible to change things dynamically.<br>&gt;<b=
r>&gt;<br>&gt;Dynamically changing stateful parameters requires that the cl=
ient implement reconfigure, and even then, it requires authentication, and =
requires either that the DHCP server never crashes, or that DHCPv6 failover=
 is in use. Dynamically changing stateless options doesn't even seem possib=
le at all - you have to wait until the client asks again, and the minimum t=
ime that must pass is 10 minutes (RFC 4242).<br>&gt;<br>&gt;</div></body></=
html>
------=_Part_1823998_328532286.1428448697968--


From nobody Tue Apr  7 16:39:55 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEE121AC40B for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 16:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.502
X-Spam-Level: 
X-Spam-Status: No, score=0.502 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 MZRN3ioBRnYe for <ipv6@ietfa.amsl.com>; Tue,  7 Apr 2015 16:39:52 -0700 (PDT)
Received: from nm41-vm8.bullet.mail.bf1.yahoo.com (nm41-vm8.bullet.mail.bf1.yahoo.com [216.109.114.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86B6B1AC41D for <ipv6@ietf.org>; Tue,  7 Apr 2015 16:39:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428449991; bh=h1vND+LVuOdNfJ1D+eNbotBhxBXsndXr0QUf+3Pckto=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=mq3UcWep5QKXR6bodtcJExDaBFU7REkk6GISHveDrf3XhqkLfX3+Y8HdZtbPhC/Hbnc3MKtNGPFMLUpMWZrbO1jymNbCUW39meU0C7oJBmCEVeHIId4JVt/4QWp67fBIJygINTHLlerXFdRDpUEA+bN7Q4fW3S3HsYvGD/JSaWgGnMGqSTTdUQ3Hw8G1+J+AB4Ubd+PL40VEzviwHRmncXWRPI7t6sPEXbw4IN/XWTw7cDmFHzA4tD9tR107npM+6wd5/tHKWBatMtrj8t0dox3i9Q5gaqKLN0EBKBCooXebpUmf0oVBfcmSf/w7eQNpJCL3nHOxwih3KInW7FLSCA==
Received: from [66.196.81.174] by nm41.bullet.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 23:39:51 -0000
Received: from [98.139.215.251] by tm20.bullet.mail.bf1.yahoo.com with NNFMP;  07 Apr 2015 23:39:51 -0000
Received: from [127.0.0.1] by omp1064.mail.bf1.yahoo.com with NNFMP; 07 Apr 2015 23:39:51 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 712318.91524.bm@omp1064.mail.bf1.yahoo.com
X-YMail-OSG: 9zX0VpoVM1lELxqeCzXDyRKisd3.mZ1cM0k2hrK4nvnlkhmCaN3oJoQHCoowalX BkNTVFhtU85IvXv3pFlIoatkKdJsPk6b6BVJbgM5jIRTccGnnMW9nXPnShyndX99.lQ510QcmDtH z4UNwdirMfePvHiO7XaGF75ravmSLRQ_BAvr1J3MDJQzMJxfJvYykKugRBMX8JIuENchgPPAPUa2 0LVyjyqYOe_FmTNgV9bGI50A5t61n20S64gLG9Tej0F0FHycQjoLYRu4TSHmljQiJkIYJpgbawJ8 MlohD5OEPmUicdzoGGDdplnuCU1aAUBACNa3711WL1IabYiAbfWBPRqM85CKGoJnf161UFbXgFIj HQxHpOBq_xGLsoDoidR1130rtveCdzfHEJajXtxvuKcTC9k2CyFxCcO36WhiXonThfA4DL.SMuBP jb4QLMVekyH6gXzFcSE4Cyf1UEmbwiq_KlhP_rrkfo9eHxWL2zp_WZPP7ZS2kBRmQlxZpDIoVFaD oY1_P3Mk_XwCNR2S44kPBNad4rHL2JQB5c9prlsG3Wu6yrHj0
Received: by 66.196.80.193; Tue, 07 Apr 2015 23:39:51 +0000 
Date: Tue, 7 Apr 2015 23:39:38 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>,  "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <1463387085.1838834.1428449978449.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <5523C74C.4050201@gmail.com>
References: <5523C74C.4050201@gmail.com>
Subject: Re: RA Option Guidelines
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_1838833_2174889.1428449978443"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qNvru-w0jbnSsjmqoWu4V7kZFXY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 23:39:55 -0000

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


      From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
 To: ipv6@ietf.org=20
 Sent: Tuesday, 7 April 2015, 22:02
 Subject: Re: RA Option Guidelines
  =20
Le 03/04/2015 21:16, Brian E Carpenter a =C3=A9crit :
> I'm glad y'all have got DHCPv6 sorted out. Now, as to the original
> subject of this thread: On 01/04/2015 08:26, Brian E Carpenter
> wrote:
>> On 01/04/2015 03:27, Hemant Singh (shemant) wrote: ...
>>> Also, why does one need an RA Option Guideline?=C2=A0 RFC4861
>>> specifies a TLV format and an option Type.=C2=A0 I don't see
>>> anything else needed if I need to specify a new RA option.
>>
>> Section 9 "Extensibility - Option Processing" gives some general
>> advice, too.
>>
>> The question is what do we collectively want. I liked Mark's
>> restrictive criterion "RA options should be limited to
>> link-local/subnet specific parameters (i.e., layer 3 parameters
>> only)". DHCPv6 is available as the kitchen sink protocol for other
>> stuff. I'm not sure whether we want to write this down; it seems
>> as if=C2=A0 one or two sentences should be added to RFC4861bis if there
>> ever is such a document.
>
> Do we actually agree on this, or rather on a slightly expanded
> version:
>
> RA options should be limited to link-local/subnet specific parameters
> (i.e., layer 3 parameters only) necessary for a simple unmanaged
> network. The only exception is RFC 6106 (DNS Configuration). More
> complex situations are better handled by other configuration metods
> such as DHCPv6.

It makes sense.

But, would it be possible to tell link-local subnet of a particular
Router?=C2=A0 I am asking because currently it is the link-local subnet of
one particular interface, the "on-link" prefix;=C2=A0 and it would be good =
to
allow a prefix in one subnet of an interface of a router be announced on
another interface of same router as "other prefix nearby".
/ I think the Route Information Option is the RA option you're looking for =
(RFC4191).

And still forbid one Router to read an RA and propagate its contents
further down the network.

/ I agree with this. With exception to the exceptional RA DNS options, all =
of the other RA option parameters are specific to the link the RA is sent o=
ver. Copying those values onto a different link doesn't make sense, because=
 those values may not be correct for the different link. In other words, li=
nk specific RA option values need to be originated (not copied) for the lin=
k the RA is sent over.
/ RFC5505, "Principles of Internet Host Configuration" discusses these topi=
cs quite comprehensively. I'd read bits of it in the past, however I didn't=
 realise comprehensive it was. Well worth a read.

/ Regards,/ Mark.

Alex




>
> Brian
>
> --------------------------------------------------------------------
>=C2=A0 IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

 =C2=A0 
------=_Part_1838833_2174889.1428449978443
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div><span></span></div><br>  <d=
iv style=3D"font-family: Helvetica Neue-Light, Helvetica Neue Light, Helvet=
ica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id=
=3D"yui_3_16_0_1_1428444387939_29339"> <div style=3D"font-family: Helvetica=
Neue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-siz=
e: 16px;" id=3D"yui_3_16_0_1_1428444387939_29338"> <div dir=3D"ltr" id=3D"y=
ui_3_16_0_1_1428444387939_29337"> <hr size=3D"1">  <font size=3D"2" face=3D=
"Arial" id=3D"yui_3_16_0_1_1428444387939_29336"> <b id=3D"yui_3_16_0_1_1428=
444387939_29335"><span style=3D"font-weight:bold;" id=3D"yui_3_16_0_1_14284=
44387939_29334">From:</span></b> Alexandru Petrescu &lt;alexandru.petrescu@=
gmail.com&gt;<br> <b><span style=3D"font-weight: bold;">To:</span></b> ipv6=
@ietf.org <br> <b><span style=3D"font-weight: bold;">Sent:</span></b> Tuesd=
ay, 7 April 2015, 22:02<br> <b><span style=3D"font-weight: bold;">Subject:<=
/span></b> Re: RA Option Guidelines<br> </font> </div> <div class=3D"y_msg_=
container" id=3D"yui_3_16_0_1_1428444387939_29340"><br>Le 03/04/2015 21:16,=
 Brian E Carpenter a =C3=A9crit :<br clear=3D"none">&gt; I'm glad y'all hav=
e got DHCPv6 sorted out. Now, as to the original<br clear=3D"none">&gt; sub=
ject of this thread: On 01/04/2015 08:26, Brian E Carpenter<br clear=3D"non=
e">&gt; wrote:<br clear=3D"none">&gt;&gt; On 01/04/2015 03:27, Hemant Singh=
 (shemant) wrote: ...<br clear=3D"none">&gt;&gt;&gt; Also, why does one nee=
d an RA Option Guideline?&nbsp; RFC4861<br clear=3D"none">&gt;&gt;&gt; spec=
ifies a TLV format and an option Type.&nbsp;  I don't see<br clear=3D"none"=
>&gt;&gt;&gt; anything else needed if I need to specify a new RA option.<br=
 clear=3D"none">&gt;&gt;<br clear=3D"none">&gt;&gt; Section 9 "Extensibilit=
y - Option Processing" gives some general<br clear=3D"none">&gt;&gt; advice=
, too.<br clear=3D"none">&gt;&gt;<br clear=3D"none">&gt;&gt; The question i=
s what do we collectively want. I liked Mark's<br clear=3D"none">&gt;&gt; r=
estrictive criterion "RA options should be limited to<br clear=3D"none">&gt=
;&gt; link-local/subnet specific parameters (i.e., layer 3 parameters<br cl=
ear=3D"none">&gt;&gt; only)". DHCPv6 is available as the kitchen sink proto=
col for other<br clear=3D"none">&gt;&gt; stuff. I'm not sure whether we wan=
t to write this down; it seems<br clear=3D"none">&gt;&gt; as if&nbsp; one o=
r two sentences should be added to RFC4861bis if there<br clear=3D"none">&g=
t;&gt; ever is such a document.<br clear=3D"none">&gt;<br clear=3D"none">&g=
t; Do we actually agree on this, or rather on a slightly expanded<br clear=
=3D"none">&gt; version:<br clear=3D"none">&gt;<br clear=3D"none">&gt; RA op=
tions should be limited to link-local/subnet specific parameters<br clear=
=3D"none">&gt; (i.e., layer 3 parameters only) necessary for a simple unman=
aged<br clear=3D"none">&gt; network. The only exception is RFC 6106 (DNS Co=
nfiguration). More<br clear=3D"none">&gt; complex situations are better han=
dled by other configuration metods<br clear=3D"none">&gt; such as DHCPv6.<b=
r clear=3D"none"><br clear=3D"none">It makes sense.<br clear=3D"none"><br c=
lear=3D"none">But, would it be possible to tell link-local subnet of a part=
icular<br clear=3D"none">Router?&nbsp; I am asking because currently it is =
the link-local subnet of<br clear=3D"none">one particular interface, the "o=
n-link" prefix;&nbsp; and it would be good to<br clear=3D"none">allow a pre=
fix in one subnet of an interface of a router be announced on<br clear=3D"n=
one">another interface of same router as "other prefix nearby".</div><div c=
lass=3D"y_msg_container" id=3D"yui_3_16_0_1_1428444387939_29340"><br></div>=
<div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428444387939_29340" dir=
=3D"ltr">/ I think the Route Information Option is the RA option you're loo=
king for (RFC4191).<br clear=3D"none"><br clear=3D"none">And still forbid o=
ne Router to read an RA and propagate its contents<br clear=3D"none">furthe=
r down the network.<br clear=3D"none"><br>/ I agree with this. With excepti=
on to the exceptional RA DNS options, all of the other RA option parameters=
 are specific to the link the RA is sent over. Copying those values onto a =
different link doesn't make sense, because those values may not be correct =
for the different link. In other words, link specific RA option values need=
 to be originated (not copied) for the link the RA is sent over.</div><div =
class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428444387939_29340" dir=3D"lt=
r"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_1_142844438793=
9_29340" dir=3D"ltr">/ RFC5505, "Principles of Internet Host Configuration"=
 discusses these topics quite comprehensively. I'd read bits of it in the p=
ast, however I didn't realise comprehensive it was. Well worth a read.<br><=
/div><div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1428444387939_29340"=
 dir=3D"ltr"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_1_14=
28444387939_29340" dir=3D"ltr">/ Regards,</div><div class=3D"y_msg_containe=
r" id=3D"yui_3_16_0_1_1428444387939_29340" dir=3D"ltr">/ Mark.</div><div cl=
ass=3D"y_msg_container" id=3D"yui_3_16_0_1_1428444387939_29340" dir=3D"ltr"=
><br><br clear=3D"none">Alex<div class=3D"qtdSeparateBR"><br><br></div><div=
 class=3D"yqt6752874108" id=3D"yqtfd37459"><br clear=3D"none"><br clear=3D"=
none"><br clear=3D"none">&gt;<br clear=3D"none">&gt; Brian</div><br clear=
=3D"none">&gt;<br clear=3D"none">&gt; -------------------------------------=
-------------------------------<br clear=3D"none">&gt;&nbsp; IETF IPv6 work=
ing group mailing list <a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" h=
ref=3D"mailto:ipv6@ietf.org" id=3D"yui_3_16_0_1_1428444387939_30098">ipv6@i=
etf.org</a> Administrative<br clear=3D"none">&gt; Requests: <a shape=3D"rec=
t" href=3D"https://www.ietf.org/mailman/listinfo/ipv6" target=3D"_blank" id=
=3D"yui_3_16_0_1_1428444387939_30099">https://www.ietf.org/mailman/listinfo=
/ipv6</a><br clear=3D"none">&gt; ------------------------------------------=
--------------------------<br clear=3D"none">&gt;<br clear=3D"none">&gt;<br=
 clear=3D"none"><br clear=3D"none"><br clear=3D"none">---------------------=
-----------------------------------------------<br clear=3D"none">IETF IPv6=
 working group mailing list<br clear=3D"none"><a shape=3D"rect" ymailto=3D"=
mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br cl=
ear=3D"none">Administrative Requests: <a shape=3D"rect" href=3D"https://www=
.ietf.org/mailman/listinfo/ipv6" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/ipv6</a><div class=3D"yqt6752874108" id=3D"yqtfd08388"><br cl=
ear=3D"none">--------------------------------------------------------------=
------</div><br><br></div> <div class=3D"" id=3D"yui_3_16_0_1_1428444387939=
_29340" dir=3D"ltr" style=3D"">&nbsp;</div></div> </div>  </div></body></ht=
ml>
------=_Part_1838833_2174889.1428449978443--


From nobody Tue Apr  7 21:15:59 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C00021B2D63; Tue,  7 Apr 2015 21:15:55 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iyj3DpzCue5U; Tue,  7 Apr 2015 21:15:54 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8A9C1B2D62; Tue,  7 Apr 2015 21:15:53 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-7b-552448d49782
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id A5.30.17241.5D844255; Tue,  7 Apr 2015 23:15:01 +0200 (CEST)
Received: from [153.88.4.126] (147.117.188.8) by smtps-am.internal.ericsson.com (147.117.188.75) with Microsoft SMTP Server (TLS) id 14.3.210.2; Wed, 8 Apr 2015 00:15:51 -0400
Message-ID: <5524AB6F.90602@ericsson.com>
Date: Wed, 8 Apr 2015 00:15:43 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
Subject: Re: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
References: <20150407030724.32439.29818.idtracker@ietfa.amsl.com> <5523DC07.3040008@innovationslab.net>
In-Reply-To: <5523DC07.3040008@innovationslab.net>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.8]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyuXSPt+5VD5VQg95GUYvdU6axWczs+cdo MePPRGaLl2ffM1ms2LWe1WLZlD3MDmweU35vZPXYOesuu8eSJT+ZPGYe/8ISwBLFZZOSmpNZ llqkb5fAldHw9A9TwRexioZbSxkbGM8KdTFyckgImEi8/3KHBcIWk7hwbz1bFyMXh5DAUUaJ +RMvMUM4mxklmg89BaviFdCU2LJ7HyuIzSKgIvG36TE7iM0GNGnDzs9MILaoQJjEtN/PWSHq BSVOznwC1isiUCXxbNkOsDizgLXE/km9QDYHh7BAmsTxgwIgYSGBdImHuzaAlXAKGEksa93B AlLCLGAv8WBrGUSnvMT2t3OYIco1Jbau+c4Kcb+ixIvjP5kmMArNQrJ4FkL3LCTdCxiZVzFy lBanluWmGxluYgQG+TEJNscdjAs+WR5iFOBgVOLhXXBSKVSINbGsuDL3EKM0B4uSOG/ZlYMh QDcmlqRmp6YWpBbFF5XmpBYfYmTi4JRqYMw5c11U6ee3NVMKn9xguP7JS77GK/bfs8K2azw9 XxTtLF0/xcRO/3rDLFRAR/d0kohcT8CUdeWNLIckkgv6HtdyPmUtOLn91vekoMy3AXuqZqp4 5To/vRT/YcWkUoN2V+aDG30rkuoC991v4os2eRv0OPiOnpRy2aQ/h93O9bAyXThtkqLho8RS nJFoqMVcVJwIAP263EdTAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EDvhQAOXT2ntmu4Cnsiifo9AEUs>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 04:15:55 -0000

Hi Brian,

On 04/07/2015 09:30 AM, Brian Haberman wrote:
> Hi all,
>
> On 4/6/15 11:07 PM, Spencer Dawkins wrote:
>> Spencer Dawkins has entered the following ballot position for
>> draft-ietf-6man-resilient-rs-05: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> I'm piling on Barry's Comment as a Discuss, which should be easy to
>> discuss, but ... in this text:
>>
>> 3.  Configuring the use of retransmissions
>>
>>     Implementations of this specification MAY provide a configuration
>>     option to enable or disable the use of such potentially infinite
>>     retransmissions.  If the implementation provides such a configuration
>>     option, it MUST be able to enable/disable retransmissions on a per-
>>     interface basis.
>>
>> You can tell me that it's a LAN, so the transport ADs can go back to
>> sleep, but I was surprised that this configuration option was a MAY.
>>
>> I was also surprised that there was no guidance about the default setting
>> (on or off), but let's start with the MAY.
>>
>> IP does get tunneled to new and exciting places ... and infinite
>> retransmissions are infinite ...
>
> I went back and re-read Barry's Comment and the resulting response and
> felt unsatisfied.
>
> Barry & Spencer, let me know if I am misinterpreting your concerns...
>
> It appears odd to give such concrete guidance as "enable/disable
> retransmissions on a per-interface basis" for a function that is
> completely optional.  After some thought, I am trying to figure out why
> it would be optional since typical NA/NS/RA/RS functionality is
> per-interface anyway.
>
> Given what is being described, I would think we would want to encourage
> implementers to provide a configuration option rather than make it
> optional.  The text could be re-written (without 2119 keywords) as such:
>
> NEW:
> Implementations of this specification are encouraged to provide a
> configuration option to enable or disable potentially infinite RS
> retransmissions. Providing an option to enable/disable retransmissions
> on a per-interface basis allows network operators to configure RS
> behavior most applicable to each connected link.

This text looks good. If this will help clarify things, I will make the 
change.

Thanks
Suresh



From nobody Tue Apr  7 21:33:28 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31E91B2DD4; Tue,  7 Apr 2015 21:33:26 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUSycHxN8hH2; Tue,  7 Apr 2015 21:33:24 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92B881B2DD3; Tue,  7 Apr 2015 21:33:23 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-56-55244cef30cd
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 8A.60.17241.FEC44255; Tue,  7 Apr 2015 23:32:31 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0210.002; Wed, 8 Apr 2015 00:33:22 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Brian Haberman <brian@innovationslab.net>
Subject: Re: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
Thread-Topic: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
Thread-Index: AQHQcOANrfnY742n90yyE1h9jceSMw==
Date: Wed, 8 Apr 2015 04:33:21 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628B6DCF1@eusaamb107.ericsson.se>
References: <20150407030724.32439.29818.idtracker@ietfa.amsl.com> <5523DC07.3040008@innovationslab.net> <CAKKJt-cBnuood4hFxymPzZf1UBZ-BK8P042TRrELMSOnsJXLyA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyuXRPlO57H5VQg7/nlSx2T5nGZjGz5x+j xYw/E5ktXp59z2SxYtd6VotlU/YwO7B5TPm9kdVj56y77B5Llvxk8ph5/AtLAEsUl01Kak5m WWqRvl0CV8aU/TUF15Qrem+vZW9gbJLuYuTkkBAwkTjVsYkFwhaTuHBvPRuILSRwlFHi+jn1 LkYuIHsZo8S836/AitiAGjbs/MwEYosIZEgs/XeMDaSIWaCXUWL67svsXYwcHMICaRLHDwpA 1KRL/Fq0kg0kLCKgJ/FirxeIySKgItH4owKkglfAV2Lj2X42iFUbGCXebt4HdgMj0D3fT60B W8UsIC5x68l8Jog7BSSW7DnPDGGLSrx8/I8VwlaU2Nc/nR2iXkdiwe5PbBC2tsSyha+ZIZYJ Spyc+YRlAqPoLCRjZyFpmYWkZRaSlgWMLKsYOUqLU8ty040MNzECo+iYBJvjDsYFnywPMQpw MCrx8C44qRQqxJpYVlyZe4hRmoNFSZy37MrBECGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M /iF7f75oZ560YPvz6//bXdTFGtfcmne5x/WZ6b8jCkemLFGWmMur7BJYnZndvPewbuVMC79T m2Rqyz4sa9D2fPmT7anrr107c4N+36s6EGGicqfOmsHrTw17+4Nn57S+e8VOTN0kZ3bRyVNQ uNbRuvmM5eTef84t3BsNjHuC/2T3pEyd+++3EktxRqKhFnNRcSIAfjGZ4YMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ntV-he81ewr2UbW7VRgHWz9jOTw>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, The IESG <iesg@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 04:33:27 -0000

Hi Spencer,=0A=
   Thanks for your comments. Please find responses inline.=0A=
=0A=
On 04/07/2015 11:07 AM, Spencer Dawkins at IETF wrote:=0A=
> Hi, Brian,=0A=
>=0A=
> On Tue, Apr 7, 2015 at 8:30 AM, Brian Haberman <brian@innovationslab.net=
=0A=
> <mailto:brian@innovationslab.net>> wrote:=0A=
>=0A=
>     Hi all,=0A=
>=0A=
>     On 4/6/15 11:07 PM, Spencer Dawkins wrote:=0A=
>      > Spencer Dawkins has entered the following ballot position for=0A=
>      > draft-ietf-6man-resilient-rs-05: Discuss=0A=
>      >=0A=
>      > When responding, please keep the subject line intact and reply to =
all=0A=
>      > email addresses included in the To and CC lines. (Feel free to=0A=
>     cut this=0A=
>      > introductory paragraph, however.)=0A=
>      >=0A=
>      >=0A=
>      > Please refer to=0A=
>     http://www.ietf.org/iesg/statement/discuss-criteria.html=0A=
>      > for more information about IESG DISCUSS and COMMENT positions.=0A=
>      >=0A=
>      >=0A=
>      > The document, along with other ballot positions, can be found here=
:=0A=
>      > http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/=0A=
>      >=0A=
>      >=0A=
>      >=0A=
>      >=0A=
>     ---------------------------------------------------------------------=
-=0A=
>      > DISCUSS:=0A=
>      >=0A=
>     ---------------------------------------------------------------------=
-=0A=
>      >=0A=
>      > I'm piling on Barry's Comment as a Discuss, which should be easy t=
o=0A=
>      > discuss, but ... in this text:=0A=
>      >=0A=
>      > 3.  Configuring the use of retransmissions=0A=
>      >=0A=
>      >    Implementations of this specification MAY provide a configurati=
on=0A=
>      >    option to enable or disable the use of such potentially infinit=
e=0A=
>      >    retransmissions.  If the implementation provides such a=0A=
>     configuration=0A=
>      >    option, it MUST be able to enable/disable retransmissions on a=
=0A=
>     per-=0A=
>      >    interface basis.=0A=
>      >=0A=
>      > You can tell me that it's a LAN, so the transport ADs can go back =
to=0A=
>      > sleep, but I was surprised that this configuration option was a MA=
Y.=0A=
>      >=0A=
>      > I was also surprised that there was no guidance about the default=
=0A=
>     setting=0A=
>      > (on or off), but let's start with the MAY.=0A=
>      >=0A=
>      > IP does get tunneled to new and exciting places ... and infinite=
=0A=
>      > retransmissions are infinite ...=0A=
>=0A=
>     I went back and re-read Barry's Comment and the resulting response an=
d=0A=
>     felt unsatisfied.=0A=
>=0A=
>     Barry & Spencer, let me know if I am misinterpreting your concerns...=
=0A=
>=0A=
>     It appears odd to give such concrete guidance as "enable/disable=0A=
>     retransmissions on a per-interface basis" for a function that is=0A=
>     completely optional.  After some thought, I am trying to figure out w=
hy=0A=
>     it would be optional since typical NA/NS/RA/RS functionality is=0A=
>     per-interface anyway.=0A=
>=0A=
>     Given what is being described, I would think we would want to encoura=
ge=0A=
>     implementers to provide a configuration option rather than make it=0A=
>     optional.  The text could be re-written (without 2119 keywords) as su=
ch:=0A=
>=0A=
>     NEW:=0A=
>     Implementations of this specification are encouraged to provide a=0A=
>     configuration option to enable or disable potentially infinite RS=0A=
>     retransmissions. Providing an option to enable/disable retransmission=
s=0A=
>     on a per-interface basis allows network operators to configure RS=0A=
>     behavior most applicable to each connected link.=0A=
>=0A=
>=0A=
> So, without 2119 keywords, I'd prefer "strongly encouraged", but=0A=
> "encouraged" is an improvement.=0A=
>=0A=
> My other point was - if there's a  configuration option for this, I=0A=
> would prefer that the group make a recommendation about default settings.=
=0A=
=0A=
Sounds good.=0A=
=0A=
>=0A=
> I'd prefer "off by default", but could be convinced that "on by default"=
=0A=
> has benefits that outweigh the costs.=0A=
=0A=
I am not exactly sure what you mean by "off by default" but the goal is =0A=
to enable persistent RS sending by default for increasing the robustness =
=0A=
for ND. If you mean that the option to disable should be "off by =0A=
default", I fully agree and can make the change right away.=0A=
=0A=
Thanks=0A=
Suresh=0A=


From nobody Tue Apr  7 21:45:54 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABA71B2E0F; Tue,  7 Apr 2015 21:45:53 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bEQ8038wDmV7; Tue,  7 Apr 2015 21:45:52 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 520BE1B2E0D; Tue,  7 Apr 2015 21:45:52 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-51-55244fdb9ec9
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 41.B0.17241.BDF44255; Tue,  7 Apr 2015 23:44:59 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0210.002; Wed, 8 Apr 2015 00:45:51 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Alia Atlas <akatlas@gmail.com>, The IESG <iesg@ietf.org>
Subject: Re: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
Thread-Topic: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
Thread-Index: AQHQcX29/lKJXclmwkq8k0z21f7QhA==
Date: Wed, 8 Apr 2015 04:45:50 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se>
References: <20150407215627.13544.1729.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyuXRPiO5tf5VQg66z+ha7p0xjs/j08BKz xYw/E5ktXp59z2SxYtd6VgdWjym/N7J67Jx1l91jyZKfTAHMUVw2Kak5mWWpRfp2CVwZUzY+ YCtYylLxcsFm9gbGzcxdjJwcEgImEv//fYCyxSQu3FvP1sXIxSEkcJRR4uORDkYIZxmjRO+6 HlaQKjagjg07PzOB2CICNhJ3Z+4FKuLgYBYolvh7yQskLCwQJfFhfwsrREm0xL17NxghbD2J lntzWUDKWQRUJL7fMwcJ8wr4Suw53cUKEhYScJC4digDJMwIdM73U2vAFjELiEvcejKfCeJM AYkle85DnSwq8fLxP1YIW1FiX/90doh6HYkFuz+xQdjaEssWvmaGWCUocXLmE5YJjKKzkIyd haRlFpKWWUhaFjCyrGLkKC1OLctNNzLcxAiMmGMSbI47GBd8sjzEKMDBqMTDu+CkUqgQa2JZ cWXuIUZpDhYlcd6yKwdDhATSE0tSs1NTC1KL4otKc1KLDzEycXBKNTBm8N7ll/ZvUvgy4evm zcKTBd8dypV+/9FtimvD/3i5s0fOrHkxrdt7glrni3OLfD0yXXd1bLzYUZuUoqgubLPvwt0M z/pt+SvOSV3ivV3BeKRJcculs+8a/9V3fDy3wTmW2zPq5PFZC7jX9rwUec759mqA0y6tBOH1 f7cwyC7T+nspye/Kxx9RSizFGYmGWsxFxYkAI12ffXkCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1hjJYpdUxfzp3P2XsNcBWsa57Bg>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 04:45:53 -0000

Hi Alia,=0A=
   Thanks for your comment.=0A=
=0A=
On 04/07/2015 05:56 PM, Alia Atlas wrote:=0A=
> To continue a bit on Spencer's Discuss and Barry's Comment, I'd prefer to=
=0A=
> see a default for the configuration.  I'd assume it would be "off" to=0A=
> continue to provide current behavior, but I don't really care.=0A=
> Consistency is my concern.=0A=
=0A=
OK. Will add a default. I have responded to Spencer and I will make the =0A=
update as soon as I get a response from him as well.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=
=0A=


From nobody Tue Apr  7 21:55:17 2015
Return-Path: <akatlas@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018CA1B3059; Tue,  7 Apr 2015 21:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dm9RfG9YGeZq; Tue,  7 Apr 2015 21:55:12 -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 A7C8B1B2E20; Tue,  7 Apr 2015 21:55:12 -0700 (PDT)
Received: by qku63 with SMTP id 63so72063884qku.3; Tue, 07 Apr 2015 21:55:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3RZ67b+N4YgfwkPgu7NplVK3uYNq2YeA28Gee2A9HBA=; b=JW3rmERU2bH+AEG6PJKVboKxi7Kx3f13FfX/POWl79l0uFiEmtgNo4+53oobiEgXwV ZDueNlN00yLBT73kJn8/hJTP02jJR5HVFKiHJuILVvLLuT/tIdvJGz8rYvNDdp4+87B6 O6kw4hapPrl0F8LzCQCPp/nquxLfYfeGeBjZex8tvnZX2ZVIoyppPYl/N9Zqzj4BnCqH IXDg16O9pvhvfWFlCKopiT1evrqEu4c6KQ/Z62+liDRrixQMz94QhT/snlCYpgttRqrf uMNEmzkeFmO/lp/VMDHzPVQdqxrQwd9xcT1zvKSxTdsBQNdnYBmgm1bB0X5W0VO5te0m mblw==
MIME-Version: 1.0
X-Received: by 10.182.60.38 with SMTP id e6mr19187774obr.57.1428468911944; Tue, 07 Apr 2015 21:55:11 -0700 (PDT)
Received: by 10.60.44.198 with HTTP; Tue, 7 Apr 2015 21:55:11 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se>
References: <20150407215627.13544.1729.idtracker@ietfa.amsl.com> <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se>
Date: Wed, 8 Apr 2015 00:55:11 -0400
Message-ID: <CAG4d1rf2uui7aA511f4ZMedmnZ+4P8UAji2zhWT4syRFNgbAqA@mail.gmail.com>
Subject: Re: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
From: Alia Atlas <akatlas@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=089e0149c5d811ba1705132f56f0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xOT2BadChWPxQ-GD7BNUilwlvpk>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, The IESG <iesg@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 04:55:14 -0000

--089e0149c5d811ba1705132f56f0
Content-Type: text/plain; charset=UTF-8

Hi Suresh,

Sounds good.  Thank you.

Alia

On Wed, Apr 8, 2015 at 12:45 AM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> Hi Alia,
>    Thanks for your comment.
>
> On 04/07/2015 05:56 PM, Alia Atlas wrote:
> > To continue a bit on Spencer's Discuss and Barry's Comment, I'd prefer to
> > see a default for the configuration.  I'd assume it would be "off" to
> > continue to provide current behavior, but I don't really care.
> > Consistency is my concern.
>
> OK. Will add a default. I have responded to Spencer and I will make the
> update as soon as I get a response from him as well.
>
> Thanks
> Suresh
>
>
>

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

<div dir=3D"ltr">Hi Suresh,<div><br></div><div>Sounds good.=C2=A0 Thank you=
.</div><div><br></div><div>Alia</div></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Wed, Apr 8, 2015 at 12:45 AM, Suresh Krishnan =
<span dir=3D"ltr">&lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" targe=
t=3D"_blank">suresh.krishnan@ericsson.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Hi Alia,<br>
=C2=A0 =C2=A0Thanks for your comment.<br>
<span class=3D""><br>
On 04/07/2015 05:56 PM, Alia Atlas wrote:<br>
&gt; To continue a bit on Spencer&#39;s Discuss and Barry&#39;s Comment, I&=
#39;d prefer to<br>
&gt; see a default for the configuration.=C2=A0 I&#39;d assume it would be =
&quot;off&quot; to<br>
&gt; continue to provide current behavior, but I don&#39;t really care.<br>
&gt; Consistency is my concern.<br>
<br>
</span>OK. Will add a default. I have responded to Spencer and I will make =
the<br>
update as soon as I get a response from him as well.<br>
<br>
Thanks<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Suresh<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--089e0149c5d811ba1705132f56f0--


From nobody Wed Apr  8 00:44:00 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67EFE1B2CE6; Wed,  8 Apr 2015 00:43:59 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvjOCWXnEZfS; Wed,  8 Apr 2015 00:43:56 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::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 5F3881B2D1F; Wed,  8 Apr 2015 00:43:03 -0700 (PDT)
Received: by laat2 with SMTP id t2so52626540laa.1; Wed, 08 Apr 2015 00:43:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7ogwj106WIaxVW/oY22z76BUbRmZtH6nSAfkr2EP5zI=; b=QOKyA9shckDzUpTWZ6IiqH0JXK1Em06MfBPt0YPBfh1XFejwo4X+qYIUhrvub8WK9Q BFoT4vn+Zx4V6shyv3+3wo6cDTxYmjTj+aRQ49ziM8cXRcc3U6clz0/rjv8wDh57mgEd qIcn4qD0DlpU1yKQZ4BYxBRgJoQ9zlNsrv6/vIsenmn/nrW5XgVB9NYpZUjNersDZW6T cL+MHpoDu5dDJuRHYt7L5A0YFre2xKOsGoVWvDj4NqtynPT+S1b0oycZS6L1iCAqgmek E01y+c2zunSXDSolJR30asUZFW+4p3SpYfMUCmQW0c6xvxVW0BKq8t305rJHkXG8R69Z bO6A==
MIME-Version: 1.0
X-Received: by 10.112.162.232 with SMTP id yd8mr21489111lbb.41.1428478981905;  Wed, 08 Apr 2015 00:43:01 -0700 (PDT)
Received: by 10.152.129.3 with HTTP; Wed, 8 Apr 2015 00:43:01 -0700 (PDT)
Received: by 10.152.129.3 with HTTP; Wed, 8 Apr 2015 00:43:01 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628B6DCF1@eusaamb107.ericsson.se>
References: <20150407030724.32439.29818.idtracker@ietfa.amsl.com> <5523DC07.3040008@innovationslab.net> <CAKKJt-cBnuood4hFxymPzZf1UBZ-BK8P042TRrELMSOnsJXLyA@mail.gmail.com> <E87B771635882B4BA20096B589152EF628B6DCF1@eusaamb107.ericsson.se>
Date: Wed, 8 Apr 2015 02:43:01 -0500
Message-ID: <CAKKJt-cY+pC+EfvE7DPSi51vS0bBQYgUQEU-hfGHZiD9wKoBaQ@mail.gmail.com>
Subject: Re: Spencer Dawkins' Discuss on draft-ietf-6man-resilient-rs-05: (with DISCUSS and COMMENT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=089e01184bba492501051331aeaa
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ApnyPJblRRpI7mQV9blLPUsPDjA>
Cc: "ot@cisco.com" <ot@cisco.com>, Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org, iesg@ietf.org, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 07:43:59 -0000

--089e01184bba492501051331aeaa
Content-Type: text/plain; charset=UTF-8

Hi, Suresh,
On Apr 7, 2015 23:33, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:
>
> Hi Spencer,
>    Thanks for your comments. Please find responses inline.
>
> On 04/07/2015 11:07 AM, Spencer Dawkins at IETF wrote:
> > Hi, Brian,
> >
> > On Tue, Apr 7, 2015 at 8:30 AM, Brian Haberman <brian@innovationslab.net
> > <mailto:brian@innovationslab.net>> wrote:
> >
> >     Hi all,
> >
> >     On 4/6/15 11:07 PM, Spencer Dawkins wrote:
> >      > Spencer Dawkins has entered the following ballot position for
> >      > draft-ietf-6man-resilient-rs-05: Discuss
> >      >
> >      > When responding, please keep the subject line intact and reply
to all
> >      > email addresses included in the To and CC lines. (Feel free to
> >     cut this
> >      > introductory paragraph, however.)
> >      >
> >      >
> >      > Please refer to
> >     http://www.ietf.org/iesg/statement/discuss-criteria.html
> >      > for more information about IESG DISCUSS and COMMENT positions.
> >      >
> >      >
> >      > The document, along with other ballot positions, can be found
here:
> >      > http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/
> >      >
> >      >
> >      >
> >      >
> >
 ----------------------------------------------------------------------
> >      > DISCUSS:
> >      >
> >
 ----------------------------------------------------------------------
> >      >
> >      > I'm piling on Barry's Comment as a Discuss, which should be easy
to
> >      > discuss, but ... in this text:
> >      >
> >      > 3.  Configuring the use of retransmissions
> >      >
> >      >    Implementations of this specification MAY provide a
configuration
> >      >    option to enable or disable the use of such potentially
infinite
> >      >    retransmissions.  If the implementation provides such a
> >     configuration
> >      >    option, it MUST be able to enable/disable retransmissions on a
> >     per-
> >      >    interface basis.
> >      >
> >      > You can tell me that it's a LAN, so the transport ADs can go
back to
> >      > sleep, but I was surprised that this configuration option was a
MAY.
> >      >
> >      > I was also surprised that there was no guidance about the default
> >     setting
> >      > (on or off), but let's start with the MAY.
> >      >
> >      > IP does get tunneled to new and exciting places ... and infinite
> >      > retransmissions are infinite ...
> >
> >     I went back and re-read Barry's Comment and the resulting response
and
> >     felt unsatisfied.
> >
> >     Barry & Spencer, let me know if I am misinterpreting your
concerns...
> >
> >     It appears odd to give such concrete guidance as "enable/disable
> >     retransmissions on a per-interface basis" for a function that is
> >     completely optional.  After some thought, I am trying to figure out
why
> >     it would be optional since typical NA/NS/RA/RS functionality is
> >     per-interface anyway.
> >
> >     Given what is being described, I would think we would want to
encourage
> >     implementers to provide a configuration option rather than make it
> >     optional.  The text could be re-written (without 2119 keywords) as
such:
> >
> >     NEW:
> >     Implementations of this specification are encouraged to provide a
> >     configuration option to enable or disable potentially infinite RS
> >     retransmissions. Providing an option to enable/disable
retransmissions
> >     on a per-interface basis allows network operators to configure RS
> >     behavior most applicable to each connected link.
> >
> >
> > So, without 2119 keywords, I'd prefer "strongly encouraged", but
> > "encouraged" is an improvement.
> >
> > My other point was - if there's a  configuration option for this, I
> > would prefer that the group make a recommendation about default
settings.
>
> Sounds good.
>
> >
> > I'd prefer "off by default", but could be convinced that "on by default"
> > has benefits that outweigh the costs.
>
> I am not exactly sure what you mean by "off by default"

I'm sorry, that really wasn't clear ("unambiguous technical text is hard"
:-)

> but the goal is
> to enable persistent RS sending by default for increasing the robustness
> for ND. If you mean that the option to disable should be "off by
> default", I fully agree and can make the change right away.

Transport guys would be genetically predisposed to prefer
disabled-by-default in the absence of any other information, but I asked,
and you're saying enabled-by-default really is the goal, so, that's fine
("we had the Discussion").

I'm more comfortable with a consistent enabled-by-default than a default
that might differ unexpectedly among the devices in a single network, so if
you're ok with enabled-by-default, I'd appreciate you making the change.

Thanks,

Spencer

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

<p dir=3D"ltr">Hi, Suresh,<br>
On Apr 7, 2015 23:33, &quot;Suresh Krishnan&quot; &lt;<a href=3D"mailto:sur=
esh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Spencer,<br>
&gt; =C2=A0 =C2=A0Thanks for your comments. Please find responses inline.<b=
r>
&gt;<br>
&gt; On 04/07/2015 11:07 AM, Spencer Dawkins at IETF wrote:<br>
&gt; &gt; Hi, Brian,<br>
&gt; &gt;<br>
&gt; &gt; On Tue, Apr 7, 2015 at 8:30 AM, Brian Haberman &lt;<a href=3D"mai=
lto:brian@innovationslab.net">brian@innovationslab.net</a><br>
&gt; &gt; &lt;mailto:<a href=3D"mailto:brian@innovationslab.net">brian@inno=
vationslab.net</a>&gt;&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0Hi all,<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0On 4/6/15 11:07 PM, Spencer Dawkins wrote:<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; Spencer Dawkins has entered the followin=
g ballot position for<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; draft-ietf-6man-resilient-rs-05: Discuss=
<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; When responding, please keep the subject=
 line intact and reply to all<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; email addresses included in the To and C=
C lines. (Feel free to<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0cut this<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; introductory paragraph, however.)<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; Please refer to<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.ietf.org/iesg/statement/=
discuss-criteria.html">http://www.ietf.org/iesg/statement/discuss-criteria.=
html</a><br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; for more information about IESG DISCUSS =
and COMMENT positions.<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; The document, along with other ballot po=
sitions, can be found here:<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; <a href=3D"http://datatracker.ietf.org/d=
oc/draft-ietf-6man-resilient-rs/">http://datatracker.ietf.org/doc/draft-iet=
f-6man-resilient-rs/</a><br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0----------------------------------------------=
------------------------<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; DISCUSS:<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0----------------------------------------------=
------------------------<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; I&#39;m piling on Barry&#39;s Comment as=
 a Discuss, which should be easy to<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; discuss, but ... in this text:<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; 3.=C2=A0 Configuring the use of retransm=
issions<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 Implementations of this spe=
cification MAY provide a configuration<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 option to enable or disable=
 the use of such potentially infinite<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 retransmissions.=C2=A0 If t=
he implementation provides such a<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0configuration<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 option, it MUST be able to =
enable/disable retransmissions on a<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0per-<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 interface basis.<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; You can tell me that it&#39;s a LAN, so =
the transport ADs can go back to<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; sleep, but I was surprised that this con=
figuration option was a MAY.<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; I was also surprised that there was no g=
uidance about the default<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0setting<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; (on or off), but let&#39;s start with th=
e MAY.<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; IP does get tunneled to new and exciting=
 places ... and infinite<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 &gt; retransmissions are infinite ...<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0I went back and re-read Barry&#39;s Comment an=
d the resulting response and<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0felt unsatisfied.<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0Barry &amp; Spencer, let me know if I am misin=
terpreting your concerns...<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0It appears odd to give such concrete guidance =
as &quot;enable/disable<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0retransmissions on a per-interface basis&quot;=
 for a function that is<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0completely optional.=C2=A0 After some thought,=
 I am trying to figure out why<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0it would be optional since typical NA/NS/RA/RS=
 functionality is<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0per-interface anyway.<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0Given what is being described, I would think w=
e would want to encourage<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0implementers to provide a configuration option=
 rather than make it<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0optional.=C2=A0 The text could be re-written (=
without 2119 keywords) as such:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0NEW:<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0Implementations of this specification are enco=
uraged to provide a<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0configuration option to enable or disable pote=
ntially infinite RS<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0retransmissions. Providing an option to enable=
/disable retransmissions<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0on a per-interface basis allows network operat=
ors to configure RS<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0behavior most applicable to each connected lin=
k.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; So, without 2119 keywords, I&#39;d prefer &quot;strongly encourag=
ed&quot;, but<br>
&gt; &gt; &quot;encouraged&quot; is an improvement.<br>
&gt; &gt;<br>
&gt; &gt; My other point was - if there&#39;s a=C2=A0 configuration option =
for this, I<br>
&gt; &gt; would prefer that the group make a recommendation about default s=
ettings.<br>
&gt;<br>
&gt; Sounds good.<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; I&#39;d prefer &quot;off by default&quot;, but could be convinced=
 that &quot;on by default&quot;<br>
&gt; &gt; has benefits that outweigh the costs.<br>
&gt;<br>
&gt; I am not exactly sure what you mean by &quot;off by default&quot; </p>
<p dir=3D"ltr">I&#39;m sorry, that really wasn&#39;t clear (&quot;unambiguo=
us technical text is hard&quot; :-)</p>
<p dir=3D"ltr">&gt; but the goal is<br>
&gt; to enable persistent RS sending by default for increasing the robustne=
ss<br>
&gt; for ND. If you mean that the option to disable should be &quot;off by<=
br>
&gt; default&quot;, I fully agree and can make the change right away.</p>
<p dir=3D"ltr">Transport guys would be genetically predisposed to prefer di=
sabled-by-default in the absence of any other information, but I asked, and=
 you&#39;re saying enabled-by-default really is the goal, so, that&#39;s fi=
ne (&quot;we had the Discussion&quot;).</p>
<p dir=3D"ltr">I&#39;m more comfortable with a consistent enabled-by-defaul=
t than a default that might differ unexpectedly among the devices in a sing=
le network, so if you&#39;re ok with enabled-by-default, I&#39;d appreciate=
 you making the change.</p>
<p dir=3D"ltr">Thanks,</p>
<p dir=3D"ltr">Spencer</p>

--089e01184bba492501051331aeaa--


From nobody Wed Apr  8 01:01:32 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 408A31B2D97; Wed,  8 Apr 2015 01:01:28 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ioorwe2FzL72; Wed,  8 Apr 2015 01:01:26 -0700 (PDT)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::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 E66A71B2D93; Wed,  8 Apr 2015 01:01:25 -0700 (PDT)
Received: by lbbuc2 with SMTP id uc2so57425538lbb.2; Wed, 08 Apr 2015 01:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wuCdhAugesv5maEB2GqUJV3DCACXVqEk7+YEFDMDJB4=; b=ZbK3IPKMp5G3JP+nPDBbJS7GIP/zbyz4uLRSjBwu++xw9AqrMndBCQUR5ZW0BpDeYX 3ZMT/IKwjolCGwLWbfYQfAC0RI9tL9GFhWiYAYdt8GYxfsXejcnxDzVG8Rvw0JIPenGc NaSs5VBqA8/H39egFeBZdZU6wMiYGpfZqv5VItOEIIJBquQ/SDDBc7GaTm3T5Z0rmXZI kc5urdRCq2nJQrhcwyZH16ScXI3cLGkC3uveCTo7p4345PgPs15i2vxB0zDHPXHnT+zO KJEa6+d7oXeFff2yg8UJrNxuZuvzSEU1sPFzFoAoUW4GyLOXmq35ni8+ppOQj4iJI5Uf Zjxw==
MIME-Version: 1.0
X-Received: by 10.152.1.194 with SMTP id 2mr21999229lao.38.1428480084361; Wed, 08 Apr 2015 01:01:24 -0700 (PDT)
Received: by 10.152.129.3 with HTTP; Wed, 8 Apr 2015 01:01:24 -0700 (PDT)
Received: by 10.152.129.3 with HTTP; Wed, 8 Apr 2015 01:01:24 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se>
References: <20150407215627.13544.1729.idtracker@ietfa.amsl.com> <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se>
Date: Wed, 8 Apr 2015 03:01:24 -0500
Message-ID: <CAKKJt-ciMU-kuuwiwiSUwDP6zsL3wu2TP7t9hEs-SYT3iPE3dQ@mail.gmail.com>
Subject: Re: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=089e013c6bccff45d3051331efec
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XxYuksPZ2WiZq2HMHad3SpC-I1c>
Cc: "ot@cisco.com" <ot@cisco.com>, ipv6@ietf.org, iesg@ietf.org, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 08:01:28 -0000

--089e013c6bccff45d3051331efec
Content-Type: text/plain; charset=UTF-8

Hi, Suresh,
On Apr 7, 2015 23:45, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
wrote:
>
> Hi Alia,
>    Thanks for your comment.
>
> On 04/07/2015 05:56 PM, Alia Atlas wrote:
> > To continue a bit on Spencer's Discuss and Barry's Comment, I'd prefer
to
> > see a default for the configuration.  I'd assume it would be "off" to
> > continue to provide current behavior, but I don't really care.
> > Consistency is my concern.
>
> OK. Will add a default. I have responded to Spencer and I will make the
> update as soon as I get a response from him as well.

I understand Alia's preference for no-change-in-behavior-by-default (Alia
is suspicious enough to be a TSV AD!), and I understand that you're trying
to change the current case so that devices no longer just stop sending for
30 minutes.

I'm happy to defer to people who have thought about this, on which way the
default goes, as long as there's a consistent default.

Spencer

> Thanks
> Suresh
>
>
>

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

<p dir=3D"ltr">Hi, Suresh,<br>
On Apr 7, 2015 23:45, &quot;Suresh Krishnan&quot; &lt;<a href=3D"mailto:sur=
esh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Alia,<br>
&gt; =C2=A0 =C2=A0Thanks for your comment.<br>
&gt;<br>
&gt; On 04/07/2015 05:56 PM, Alia Atlas wrote:<br>
&gt; &gt; To continue a bit on Spencer&#39;s Discuss and Barry&#39;s Commen=
t, I&#39;d prefer to<br>
&gt; &gt; see a default for the configuration.=C2=A0 I&#39;d assume it woul=
d be &quot;off&quot; to<br>
&gt; &gt; continue to provide current behavior, but I don&#39;t really care=
.<br>
&gt; &gt; Consistency is my concern.<br>
&gt;<br>
&gt; OK. Will add a default. I have responded to Spencer and I will make th=
e<br>
&gt; update as soon as I get a response from him as well.</p>
<p dir=3D"ltr">I understand Alia&#39;s preference for no-change-in-behavior=
-by-default (Alia is suspicious enough to be a TSV AD!), and I understand t=
hat you&#39;re trying to change the current case so that devices no longer =
just stop sending for 30 minutes.</p>
<p dir=3D"ltr">I&#39;m happy to defer to people who have thought about this=
, on which way the default goes, as long as there&#39;s a consistent defaul=
t.</p>
<p dir=3D"ltr">Spencer</p>
<p dir=3D"ltr">&gt; Thanks<br>
&gt; Suresh<br>
&gt;<br>
&gt;<br>
&gt;<br>
</p>

--089e013c6bccff45d3051331efec--


From nobody Wed Apr  8 05:37:00 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 107391A0029; Wed,  8 Apr 2015 05:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oVE7NTEiVrfT; Wed,  8 Apr 2015 05:36:56 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF4ED1A1A28; Wed,  8 Apr 2015 05:36:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-predictable-fragment-id-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408123655.17106.68920.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 05:36:55 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/r8JMB7nycSVxhwHqp6A9OqIQp20>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 12:36:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Security Implications of Predictable Fragment Identification Values
        Author          : Fernando Gont
	Filename        : draft-ietf-6man-predictable-fragment-id-05.txt
	Pages           : 16
	Date            : 2015-04-08

Abstract:
   IPv6 specifies the Fragment Header, which is employed for the
   fragmentation and reassembly mechanisms.  The Fragment Header
   contains an "Identification" field which, together with the IPv6
   Source Address and the IPv6 Destination Address of a packet,
   identifies fragments that correspond to the same original datagram,
   such that they can be reassembled together at the receiving host.
   The only requirement for setting the "Identification" value is that
   it must be different than that employed for any other fragmented
   packet sent recently with the same Source Address and Destination
   Address.  Some implementations use a simple global counter for
   setting the Identification field, thus leading to predictable values.
   This document analyzes the security implications of predictable
   Identification values, and provides implementation guidance for
   selecting the Identification field of the Fragment Header, such that
   the aforementioned security implications are mitigated.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-predictable-fragment-id/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-predictable-fragment-id-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-predictable-fragment-id-05


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/


From nobody Wed Apr  8 08:51:47 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B07E1B3394; Wed,  8 Apr 2015 08:51:45 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqTQ6tlBxbew; Wed,  8 Apr 2015 08:51:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE3F11B3348; Wed,  8 Apr 2015 08:51:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
Subject: Stephen Farrell's No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408155108.15627.15561.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 08:51:08 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/kekn31p-oZM4ihJ9teLO5vpw6nk>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 15:51:45 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-6man-resilient-rs-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


security considerations: I note that RFC 4861 has been
updated, including by RFC 5942, which specifically says it
addresses a security concern in 4861. (I didn't check the
others.) I think it'd be better to say here "beyond those
discussed in [RFC4861] and RFCs that update that" or some
such. Or point to all the relevant ones, or tell me that it
doesn't matter for this:-)



From nobody Wed Apr  8 12:19:39 2015
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5164F1B3530 for <ipv6@ietfa.amsl.com>; Wed,  8 Apr 2015 12:19:37 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k904-zXiNDAD for <ipv6@ietfa.amsl.com>; Wed,  8 Apr 2015 12:19:35 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001: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 A0C321B352D for <ipv6@ietf.org>; Wed,  8 Apr 2015 12:19:35 -0700 (PDT)
Received: by ignm3 with SMTP id m3so35408618ign.0 for <ipv6@ietf.org>; Wed, 08 Apr 2015 12:19:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:date:cc:message-id :references:to; bh=rEymAYMjldqxB+l+h9m2+2uurrOA43V3oRQwjBENodE=; b=PZmwI68NsnT0KQfA6oyOOhhV7C0xutbDKmhdAiOA/K61hwW7EMCRFURf38gEvJPcAe j4Vxv4eeehgKQeTdEr0jX6tbd1YcpnGbnFVqvDex/MXD9jBC5mYOeuMuGh54Xz0urWzr dKHAsewTqv+a/AGd+DzCl/G5nfgh8xUa/ShCqqizoMBFk4AMlagodexGVat+q9Qr3q5k 1M5bhQxX2o0X1bwp7vBsaiuwK5rT4VXsfp9y5oKBHFxKEMWhvqNkd4boP/kMyoNEYuQh KdMZfqPm6q3bbRAuwAm/uFMVsZXnKPy7/xsE8NzpmxsudVdTLEue961q+JXh83xazx9N 70/A==
X-Received: by 10.50.221.98 with SMTP id qd2mr14368466igc.37.1428520775086; Wed, 08 Apr 2015 12:19:35 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id f1sm7333297igt.14.2015.04.08.12.19.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Apr 2015 12:19:33 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C4CFFB5E-11E3-496A-96C9-20B69D069A0D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
X-Pgp-Agent: GPGMail 2.5b6
From: Bob Hinden <bob.hinden@gmail.com>
Date: Wed, 8 Apr 2015 12:19:30 -0700
Message-Id: <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7pMqQBLGHz_qqdOjeE765SmfDLU>
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 19:19:37 -0000

--Apple-Mail=_C4CFFB5E-11E3-496A-96C9-20B69D069A0D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Reminder.  Please send comments on this adoption call.

Thanks
Bob & Ole


> Begin forwarded message:
>=20
> From: Bob Hinden <bob.hinden@gmail.com>
> Subject: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
> Date: March 27, 2015 at 8:34:09 AM PDT
> Cc: 6man Chairs <6man-chairs@tools.ietf.org>
> To: IPv6 List <ipv6@ietf.org>
>=20
> This message starts a two week 6MAN Working Group Last Call on =
adopting:
>=20
>        Title           : IPv6 Neighbor Discovery Optional Unicast =
RS/RA Refresh
>        Authors         : Erik Nordmark
>                          Andrew Yourtchenko
>                          Suresh Krishnan
>        Filename        : draft-nordmark-6man-rs-refresh-01.txt
>        Pages           : 12
>        Date            : 2014-10-27
>=20
>        https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01
>=20
> as a working group document. Substantive comments and statements of =
support for adopting this document should be directed to the mailing =
list.  Editorial suggestions can be sent to the authors.  This adoption =
call will end on April 10, 2015.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=C3=B8an
>=20


--Apple-Mail=_C4CFFB5E-11E3-496A-96C9-20B69D069A0D
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

iQEcBAEBCgAGBQJVJX9DAAoJEK7rdBF357uosEgH/0QLplKh4q6kXgPXVsLQ9yO3
OL7TtRqhYgHU/Sm23quNkpFVwppAp3NXHlS7DfbOH56uIphjZhejCmiv1dOt8sup
DEGqBcZ9NJR6bN7ry80mljSbzkCUG/YG5Ce2Z/uAVusQij+/9Aw7+YC3PnSMbcH3
uWyvw6spQFyjrfRvZehQQUmykdKXM7de74r6pCjANdYVJR1UAtOD+umHHiNizOeR
UldG8I90llAvRKNCURS85ik/FLl8qzJWWD2NmDuVOcMfdSGg6rsMuy1xIWaNPf1l
L0ElBjRN3up2q71j7th/7/tgru1fIaAeR0ADukui3E3X4mCDPugT5u1A7sCVHIc=
=zatO
-----END PGP SIGNATURE-----

--Apple-Mail=_C4CFFB5E-11E3-496A-96C9-20B69D069A0D--


From nobody Wed Apr  8 17:33:33 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40CBA1A92EE for <ipv6@ietfa.amsl.com>; Wed,  8 Apr 2015 17:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.102
X-Spam-Level: *
X-Spam-Status: No, score=1.102 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 cbay01-Bt79n for <ipv6@ietfa.amsl.com>; Wed,  8 Apr 2015 17:33:31 -0700 (PDT)
Received: from nm45-vm2.bullet.mail.ne1.yahoo.com (nm45-vm2.bullet.mail.ne1.yahoo.com [98.138.121.66]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD71C1A892A for <ipv6@ietf.org>; Wed,  8 Apr 2015 17:33:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1428539610; bh=lWnHgkpjo7yvNy6z5D/1ylZylpCdoiiF8JurIKKShHU=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=l5WiaDM/Dunu0HJOxAL2OFTUMN7IMqUaPU4e++sJJu6SQoGWJKUZsmjxKSQOqAaQzoCp4dncuA9G8bOznhbo/nSCT2GgsgKjDxNq00wkLydTTT9om9F2xzjVdEV2oix9sWKVFnvx5Dw6Zc6MljWHAWkrnwR+3lDNjPOXKdhafZJHpcgBr/aM+5+m+LouMlxkB/mV0jrIYTJxvIkhmDAWEDVLnIgylU13rxqD9dXPQcnYDzssbC/fkokk8C7RX01k85JCuK+mzb5EoLUqsRgBqTpsTWQ4HpXYA2keLbc1WccgNe71+JPWwRnlimIaeaXZtO/YNCDf+GpMkJ9PYZrPOw==
Received: from [127.0.0.1] by nm45.bullet.mail.ne1.yahoo.com with NNFMP; 09 Apr 2015 00:33:30 -0000
Received: from [98.138.100.102] by nm45.bullet.mail.ne1.yahoo.com with NNFMP;  09 Apr 2015 00:30:29 -0000
Received: from [98.139.170.182] by tm101.bullet.mail.ne1.yahoo.com with NNFMP;  09 Apr 2015 00:30:29 -0000
Received: from [98.139.212.229] by tm25.bullet.mail.bf1.yahoo.com with NNFMP;  09 Apr 2015 00:30:29 -0000
Received: from [127.0.0.1] by omp1038.mail.bf1.yahoo.com with NNFMP; 09 Apr 2015 00:30:29 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 5299.25705.bm@omp1038.mail.bf1.yahoo.com
X-YMail-OSG: 3ZT4xMUVM1kZERnCaGbJG3KzcJ4p0d31EjPBjc2Dp7QlkQEXLvhe1LHG19H50iR OpxssuGxY_HX8yc8PCOe2Tt5IQS7MeBiJDcGetbp4wLad8UhJ6glCoX8QlVCLYVFH4zf.HFabAES OQog..jiUhhz2eYPAKS_BryCC3Q2kbLDbNqL.Q7WXJBfLrYTfcE8D1frqgl0A_U0N9_3RGvxU9go XukgD.OMj3bwXmTOaIg96IqeJ63biOMWA4Z9LaxqpSMMhi7i0yUjhnLxiOjdyPgg7KoOf0bDIHj6 y5dfjW1dGu5UTVOchLLN4.8BUQtS.cugAsjY_5Cwa1NtL.oVwjRosR91.eFg_5mT.t3vkJRDYC77 kodUvAmVoj6zqiweT4FnxQQR6VCr3fs5foHPWFM_uIfLB6Ks8l_xUDiRjHurVmj3SRcf0K4iaUGN qztaZJWtNM0ddo8p31QsU12o8UZb6CcY2W6byLDHN9kDcahhpgUi1awlchz4mdzWrV5V7LqAJwvT VfvmevvljG0pNW2VnG.Mt.KD1eFYyATh6AXGkpVVkhZdZmHvGTaTKBYgNq.U-
Received: by 66.196.80.125; Thu, 09 Apr 2015 00:30:28 +0000 
Date: Thu, 9 Apr 2015 00:30:27 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Message-ID: <1418596901.2922500.1428539427726.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
Subject: Re: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2922498_627364480.1428539427720"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1HfkQ5KWv3M4SUdVMtqoVl0IoJk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 00:33:32 -0000

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

Hi,
I support adoption.
Regards,Mark.
      From: Bob Hinden <bob.hinden@gmail.com>
 To: IPv6 List <ipv6@ietf.org>=20
Cc: Bob Hinden <bob.hinden@gmail.com>=20
 Sent: Thursday, 9 April 2015, 5:19
 Subject: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
  =20
Reminder.=C2=A0 Please send comments on this adoption call.

Thanks
Bob & Ole


> Begin forwarded message:
>=20
> From: Bob Hinden <bob.hinden@gmail.com>
> Subject: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
> Date: March 27, 2015 at 8:34:09 AM PDT
> Cc: 6man Chairs <6man-chairs@tools.ietf.org>
> To: IPv6 List <ipv6@ietf.org>
>=20
> This message starts a two week 6MAN Working Group Last Call on adopting:
>=20
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IPv6=
 Neighbor Discovery Optional Unicast RS/RA Refresh
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 : Erik Nord=
mark
>=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 Andrew Yourtchenko
>=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 Suresh Krishnan
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-no=
rdmark-6man-rs-refresh-01.txt
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 12
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
: 2014-10-27
>=20
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://tools.ietf.org/html/draft-nordmark-6ma=
n-rs-refresh-01
>=20
> as a working group document. Substantive comments and statements of suppo=
rt for adopting this document should be directed to the mailing list.=C2=A0=
 Editorial suggestions can be sent to the authors.=C2=A0 This adoption call=
 will end on April 10, 2015.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=C3=B8an
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


  
------=_Part_2922498_627364480.1428539427720
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div dir=3D"ltr"><span>Hi,</span=
></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428536102903_11228"><span><br><=
/span></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428536102903_11230"><span =
id=3D"yui_3_16_0_1_1428536102903_11229">I support adoption.</span></div><di=
v dir=3D"ltr"><span><br></span></div><div dir=3D"ltr"><span>Regards,</span>=
</div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1428536102903_11231"><span>Mark.<=
/span></div><br>  <div style=3D"font-family: Helvetica Neue-Light, Helvetic=
a Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; =
font-size: 16px;" id=3D"yui_3_16_0_1_1428536102903_11234"> <div style=3D"fo=
nt-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, =
Sans-Serif; font-size: 16px;" id=3D"yui_3_16_0_1_1428536102903_11233"> <div=
 dir=3D"ltr" id=3D"yui_3_16_0_1_1428536102903_11232"> <hr size=3D"1">  <fon=
t size=3D"2" face=3D"Arial"> <b><span style=3D"font-weight:bold;">From:</sp=
an></b> Bob Hinden &lt;bob.hinden@gmail.com&gt;<br> <b><span style=3D"font-=
weight: bold;">To:</span></b> IPv6 List &lt;ipv6@ietf.org&gt; <br><b><span =
style=3D"font-weight: bold;">Cc:</span></b> Bob Hinden &lt;bob.hinden@gmail=
.com&gt; <br> <b><span style=3D"font-weight: bold;">Sent:</span></b> Thursd=
ay, 9 April 2015, 5:19<br> <b><span style=3D"font-weight: bold;">Subject:</=
span></b> Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01<br>=
 </font> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_0_1_142853610=
2903_11235"><br>Reminder.&nbsp; Please send comments on this adoption call.=
<br><br>Thanks<br>Bob &amp; Ole<br><br><br>&gt; Begin forwarded message:<br=
>&gt; <br>&gt; From: Bob Hinden &lt;<a ymailto=3D"mailto:bob.hinden@gmail.c=
om" href=3D"mailto:bob.hinden@gmail.com">bob.hinden@gmail.com</a>&gt;<br>&g=
t; Subject: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01<br>&gt=
; Date: March 27, 2015 at 8:34:09 AM PDT<br>&gt; Cc: 6man Chairs &lt;<a yma=
ilto=3D"mailto:6man-chairs@tools.ietf.org" href=3D"mailto:6man-chairs@tools=
.ietf.org">6man-chairs@tools.ietf.org</a>&gt;<br>&gt; To: IPv6 List &lt;<a =
ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.or=
g</a>&gt;<br>&gt; <br>&gt; This message starts a two week 6MAN Working Grou=
p Last Call on adopting:<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; Title&=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  : IPv6 Neighbor Discovery Optional Unica=
st RS/RA Refresh<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; Authors&nbsp; &nbsp; &n=
bsp; &nbsp;  : Erik Nordmark<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Andrew Yourtchenko<br>&=
gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; Suresh Krishnan<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; Filen=
ame&nbsp; &nbsp; &nbsp; &nbsp; : draft-nordmark-6man-rs-refresh-01.txt<br>&=
gt;&nbsp; &nbsp; &nbsp; &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  : 1=
2<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; : 2014-10-27<br>&gt; <br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; <a href=3D=
"https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01" target=3D"_=
blank">https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01</a><br=
>&gt; <br>&gt; as a working group document. Substantive comments and statem=
ents of support for adopting this document should be directed to the mailin=
g list.&nbsp; Editorial suggestions can be sent to the authors.&nbsp; This =
adoption call will end on April 10, 2015.<br>&gt; <br>&gt; Regards,<br>&gt;=
 <br>&gt; Bob Hinden &amp; Ole Tr=C3=B8an<br>&gt; <br><br>-----------------=
---------------------------------------------------<br>IETF IPv6 working gr=
oup mailing list<br><a ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6=
@ietf.org">ipv6@ietf.org</a><br>Administrative Requests: <a href=3D"https:/=
/www.ietf.org/mailman/listinfo/ipv6" target=3D"_blank">https://www.ietf.org=
/mailman/listinfo/ipv6</a><br>---------------------------------------------=
-----------------------<br><br><br></div> </div> </div>  </div></body></htm=
l>
------=_Part_2922498_627364480.1428539427720--


From nobody Wed Apr  8 21:55:08 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D603C1ACE8B; Wed,  8 Apr 2015 21:55:06 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfK27jc9VY4f; Wed,  8 Apr 2015 21:55:05 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0B1D1ACE4A; Wed,  8 Apr 2015 21:52:51 -0700 (PDT)
X-AuditID: c618062d-f79686d0000030a8-b5-5525af140420
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id D1.EB.12456.41FA5255; Thu,  9 Apr 2015 00:43:32 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0210.002; Thu, 9 Apr 2015 00:52:44 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Subject: Re: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
Thread-Topic: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
Thread-Index: AQHQcX29/lKJXclmwkq8k0z21f7QhA==
Date: Thu, 9 Apr 2015 04:52:43 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628B6F3C1@eusaamb107.ericsson.se>
References: <20150407215627.13544.1729.idtracker@ietfa.amsl.com> <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se> <CAKKJt-ciMU-kuuwiwiSUwDP6zsL3wu2TP7t9hEs-SYT3iPE3dQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXRPoK7IetVQg+Xdcha7p0xjs/j08BKz xYw/E5ktXp59z2SxYtd6VotlU/YwO7B5TPm9kdVj56y77B5LlvxkCmCO4rJJSc3JLEst0rdL 4MpoWWpUsJ+7Ymb/GvYGxlbOLkZODgkBE4lli9azQthiEhfurWfrYuTiEBI4yihx8HczM4Sz jFHi9/5HTCBVbEAdG3Z+BrNFBKwltvR1gnUwC2xjlDi/9D47SEJYIEriw/4WVoiiaIl7924w Qth6Ei335rKA2CwCKhLXNv0Dq+cV8JW4v/stK8S204wSU5Z2gTUzAt30/dQasG3MAuISt57M Z4K4VUBiyZ7zzBC2qMTLx/+gflCSmPP6GjNEvY7Egt2f2CBsbYllC18zQywTlDg58wnLBEbR WUjGzkLSMgtJyywkLQsYWVYxcpQWp5blphsZbGIExtAxCTbdHYx7XloeYhTgYFTi4X2wRDVU iDWxrLgy9xCjNAeLkjjvogcHQ4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwZlkFXLDcvePx orpzZ4OOOlUI/v8x5au+UfykxAvGk2d95HHZ+0t0464PFl2TV6roZOxSnbvzmhara831/S/O +E52Whhw+FOJ+ew+7wAL/d9P689o57LLBhpcCq+v4Ja72b926kWPeVca2++0dn+7YXb16uw/ PluPTiy7NPPuj86dTwUztX5+vKPEUpyRaKjFXFScCABy/0cmggIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/s9ZOg-OCbuYRwDcJLUtN-drOSrc>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 04:55:07 -0000

Hi Alia and Spencer,=0A=
   I will specify the default in the next revision. Thanks for your =0A=
comments.=0A=
=0A=
Regards=0A=
Suresh=0A=
=0A=
On 04/08/2015 04:01 AM, Spencer Dawkins at IETF wrote:=0A=
> Hi, Suresh,=0A=
> On Apr 7, 2015 23:45, "Suresh Krishnan" <suresh.krishnan@ericsson.com=0A=
> <mailto:suresh.krishnan@ericsson.com>> wrote:=0A=
>  >=0A=
>  > Hi Alia,=0A=
>  >    Thanks for your comment.=0A=
>  >=0A=
>  > On 04/07/2015 05:56 PM, Alia Atlas wrote:=0A=
>  > > To continue a bit on Spencer's Discuss and Barry's Comment, I'd=0A=
> prefer to=0A=
>  > > see a default for the configuration.  I'd assume it would be "off" t=
o=0A=
>  > > continue to provide current behavior, but I don't really care.=0A=
>  > > Consistency is my concern.=0A=
>  >=0A=
>  > OK. Will add a default. I have responded to Spencer and I will make th=
e=0A=
>  > update as soon as I get a response from him as well.=0A=
>=0A=
> I understand Alia's preference for no-change-in-behavior-by-default=0A=
> (Alia is suspicious enough to be a TSV AD!), and I understand that=0A=
> you're trying to change the current case so that devices no longer just=
=0A=
> stop sending for 30 minutes.=0A=
>=0A=
> I'm happy to defer to people who have thought about this, on which way=0A=
> the default goes, as long as there's a consistent default.=0A=
>=0A=
> Spencer=0A=
>=0A=
>  > Thanks=0A=
>  > Suresh=0A=
>  >=0A=
>  >=0A=
>  >=0A=
>=0A=
=0A=


From nobody Wed Apr  8 21:59:17 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039A71ACED3; Wed,  8 Apr 2015 21:59:16 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhIZIUy77czI; Wed,  8 Apr 2015 21:59:14 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 449FC1ACEBE; Wed,  8 Apr 2015 21:58:05 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-9d-5525a42b1d30
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id CE.6D.17241.B24A5255; Wed,  8 Apr 2015 23:56:59 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0210.002; Thu, 9 Apr 2015 00:58:03 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
Thread-Topic: Stephen Farrell's No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
Thread-Index: AQHQchQYPW9Jzjp110CQbqz3eZfFSQ==
Date: Thu, 9 Apr 2015 04:58:02 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628B6F404@eusaamb107.ericsson.se>
References: <20150408155108.15627.15561.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXSPn672EtVQgwW/xC12T5nGZjHjz0Rm i5dn3zNZrNi1ntVi+t5r7A6sHlN+b2T1WNt9lc1jyZKfTAHMUVw2Kak5mWWpRfp2CVwZPbsv sBVM4qjoXHqKvYHxEVsXIweHhICJxKq1kl2MnECmmMSFe+uBwlwcQgJHGSV+LpnCApIQEljG KDFpAVgRG1D9hp2fmUBsEQFPiYd9p1hA5jALFEv8veQFEhYWSJBY/+gbC0RJosTPpzOgyvUk 1q34AraWRUBF4tZZVZAwr4CvxItHS5ggNjlKrNwxiR3EZgQ65/upNWBxZgFxiVtP5jNBnCkg sWTPeWYIW1Ti5eN/rBC2ksTH3/PZIep1JBbs/sQGYWtLLFv4mhlil6DEyZlPWCYwis5CMnYW kpZZSFpmIWlZwMiyipGjtDi1LDfdyHATIzBejkmwOe5gXPDJ8hCjAAejEg9vQrBKqBBrYllx Ze4hRmkOFiVx3rIrB0OEBNITS1KzU1MLUovii0pzUosPMTJxcEo1MMrK8Ec2nwiz/njOWv7D H0erW/P5H15YkVA0c+7zqa/vnX+3ecmsedwOKic3vwyaxdQyYbnQ5YNbZDZsN1OZ0r+dda/C n0nTp92b/7Bif2T990i9feIvzYI8lJ5f3b62w/HXyY5I65lema82n1np0BSesFhWmuvgsUrV 1p/Z+XMmfNt2dXqicoCtEktxRqKhFnNRcSIAswX3q3gCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hdgNKARi3azvAr9KPpzIBR028Dc>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 04:59:16 -0000

Hi Stephen,=0A=
   Thanks for your comment.=0A=
=0A=
On 04/08/2015 11:53 AM, Stephen Farrell wrote:=0A=
> ----------------------------------------------------------------------=0A=
> COMMENT:=0A=
> ----------------------------------------------------------------------=0A=
>=0A=
>=0A=
> security considerations: I note that RFC 4861 has been=0A=
> updated, including by RFC 5942, which specifically says it=0A=
> addresses a security concern in 4861. (I didn't check the=0A=
> others.) I think it'd be better to say here "beyond those=0A=
> discussed in [RFC4861] and RFCs that update that" or some=0A=
> such. Or point to all the relevant ones, or tell me that it=0A=
> doesn't matter for this:-)=0A=
=0A=
Makes sense. Even though the security concerns from RFC5942 do not =0A=
directly apply to the mechanism proposed in this document, there are =0A=
other security updates to RFC4861 in the pipeline in 6man that may =0A=
apply. Will include this phrase in the next rev.=0A=
=0A=
Regards=0A=
Suresh=0A=
=0A=
=0A=


From nobody Wed Apr  8 22:54:06 2015
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 879881B2CB7; Wed,  8 Apr 2015 22:54:05 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AqlQKudmEtZS; Wed,  8 Apr 2015 22:54:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5911B2CB2; Wed,  8 Apr 2015 22:54:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Joel Jaeggli" <joelja@bogus.com>
To: "The IESG" <iesg@ietf.org>
Subject: Joel Jaeggli's No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150409055404.13839.70876.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 22:54:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/aIDhagrf8YN_ny6DxXF5BwwHp1o>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 05:54:05 -0000

Joel Jaeggli has entered the following ballot position for
draft-ietf-6man-resilient-rs-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I can live with it.

It doesn't really dwell on costs to devices from the potential for
devices on very large but unrouted adhoc networks to spend resources
soliciting routers essentially forever.



From nobody Thu Apr  9 01:52:42 2015
Return-Path: <db3546@att.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D036F1B369E; Wed,  8 Apr 2015 14:16: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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8YRte0hqEM_N; Wed,  8 Apr 2015 14:16:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C691B3697; Wed,  8 Apr 2015 14:16:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Deborah Brungard" <db3546@att.com>
To: "The IESG" <iesg@ietf.org>
Subject: Deborah Brungard's No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408211606.8335.80540.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 14:16:06 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xXLpL_vKdIB2IjQJcLZjwi6qfDc>
X-Mailman-Approved-At: Thu, 09 Apr 2015 01:52:41 -0700
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 21:16:08 -0000

Deborah Brungard has entered the following ballot position for
draft-ietf-6man-resilient-rs-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Similar to Barry's comment, I would expect some operators' would prefer a
system-wide default also be supported vs. per interface granularity.



From nobody Thu Apr  9 02:49:22 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6DBE1B2D44; Thu,  9 Apr 2015 02:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXzlFbTM-Wwj; Thu,  9 Apr 2015 02:49:15 -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 38FFE1B2D40; Thu,  9 Apr 2015 02:49:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 15CF6BEEE; Thu,  9 Apr 2015 10:49:13 +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 mMYg95uCYJH2; Thu,  9 Apr 2015 10:49:12 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.18.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DF910BE57; Thu,  9 Apr 2015 10:49:11 +0100 (IST)
Message-ID: <55264B17.4020707@cs.tcd.ie>
Date: Thu, 09 Apr 2015 10:49:11 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, The IESG <iesg@ietf.org>
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
References: <20150408155108.15627.15561.idtracker@ietfa.amsl.com> <E87B771635882B4BA20096B589152EF628B6F404@eusaamb107.ericsson.se>
In-Reply-To: <E87B771635882B4BA20096B589152EF628B6F404@eusaamb107.ericsson.se>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3y2fjYU_QjIeJUClmGugRC5OdaA>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 09:49:18 -0000

That seems fine, thanks,
S

On 09/04/15 05:58, Suresh Krishnan wrote:
> Hi Stephen,
>    Thanks for your comment.
> 
> On 04/08/2015 11:53 AM, Stephen Farrell wrote:
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>>
>> security considerations: I note that RFC 4861 has been
>> updated, including by RFC 5942, which specifically says it
>> addresses a security concern in 4861. (I didn't check the
>> others.) I think it'd be better to say here "beyond those
>> discussed in [RFC4861] and RFCs that update that" or some
>> such. Or point to all the relevant ones, or tell me that it
>> doesn't matter for this:-)
> 
> Makes sense. Even though the security concerns from RFC5942 do not 
> directly apply to the mechanism proposed in this document, there are 
> other security updates to RFC4861 in the pipeline in 6man that may 
> apply. Will include this phrase in the next rev.
> 
> Regards
> Suresh
> 
> 


From nobody Thu Apr  9 04:08:04 2015
Return-Path: <jari.arkko@piuha.net>
X-Original-To: expand-draft-ietf-6man-resilient-rs.all@virtual.ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 5E0281B33B4; Thu,  9 Apr 2015 04:06:32 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-6man-resilient-rs.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-6man-resilient-rs.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 383371B3361; Thu,  9 Apr 2015 04:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SyugautnMYyF; Thu,  9 Apr 2015 04:06:30 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFFB1B33DC; Thu,  9 Apr 2015 04:06:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E00462CC6F; Thu,  9 Apr 2015 14:06:29 +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 KHxFJ2lxBe4m; Thu,  9 Apr 2015 14:06:29 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 300862CC5D; Thu,  9 Apr 2015 14:06:29 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_D9A48D24-8233-4DA8-876D-6041E0058E2E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Gen-ART telechat review of draft-ietf-6man-resilient-rs-05
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <551D917A.3040400@gmail.com>
Date: Thu, 9 Apr 2015 14:06:27 +0300
Message-Id: <5729BFE3-AB68-4636-99A1-18997D56ED55@piuha.net>
References: <551D917A.3040400@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/iNrC_7bOZpMHNhB9d25Wgr5hKzc>
X-Mailman-Approved-At: Thu, 09 Apr 2015 04:08:03 -0700
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-6man-resilient-rs.all@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 11:06:32 -0000

--Apple-Mail=_D9A48D24-8233-4DA8-876D-6041E0058E2E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks for the review and new versions!

Jari

On 02 Apr 2015, at 21:59, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-6man-resilient-rs-05.txt.txt
> Reviewer: Brian Carpenter
> Review Date: 2015-04-03
> IETF LC End Date: 2015-02-16
> IESG Telechat date: 2015-04-09
>=20
> Summary: Ready
> --------
>=20
> Comment: Thanks for taking care of my Last Call comments
> --------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_D9A48D24-8233-4DA8-876D-6041E0058E2E
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

iQIcBAEBCgAGBQJVJl0zAAoJEM80gCTQU46qrB8QAIH7jxPeybcSyZk2q7O+12Sm
CVk5VyJfsNmut6JRkhWxBfhrqbhK8pKRzKhiTxMzXAwtIAiIVw5lW+FcpOxM5krC
N1e8bjPOoSLWMd6T1RfZ33A9CvhWSHdJJrsmJyF5L48hAmXiCMEbl4bte2IYUJjQ
oCWSmV/KiH93RLtSzWYtJR3aeiI0xD8a/n3ci+XbGouw+5Xmr0WrJQRy6wJBmqHZ
+uIW/EORDBSiH6X0l5Kr9Lvrr7KBMdKOYEf+483DUCZH9YStnSfxfF50TWsVnMo7
8AXJTTILfGPj+Jj/tjeJPVKafQrxrT1Sp+AuRNS4SEmYG0bq3s1VbuG0d0PbdaRE
yp85RJk8bRfw7dLan0q+HwexdI9j7HFoQVwOmAIOTag7c90JG0o++uikKp/jVgV/
Iyfk4JIXCbt3AHDCL1FTGV3sFD0K3JftvVefItcW8+FpZOS18pVexNtrfhanynxK
k0jqCYwbt7IwrvgCQ++bL/QMUyvqKgMbxHYzpDnyx6QiqOBvfCbPSDsXkEeiDR7l
Q/ena9W1x4/9u8VMWt55hKwdeCXVb3JrqC82oN4glh6TTtc247FZ+9zWjq9NrcUb
gpDjhIFE9kjJ5o6sE0ocVB1NnIsMeFqEF2/8z7bcyfTsw/mIk6YLfnpqBuDb1LzC
nSGXmjeSdTFONt38wz4B
=V/wk
-----END PGP SIGNATURE-----

--Apple-Mail=_D9A48D24-8233-4DA8-876D-6041E0058E2E--


From nobody Thu Apr  9 06:51:01 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41BF1A1A9E; Thu,  9 Apr 2015 06:50:58 -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_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CH36neXQSgGc; Thu,  9 Apr 2015 06:50:57 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A22ED1A1A8A; Thu,  9 Apr 2015 06:50:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Subject: Spencer Dawkins' Yes on draft-ietf-6man-resilient-rs-05: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150409135057.13211.34274.idtracker@ietfa.amsl.com>
Date: Thu, 09 Apr 2015 06:50:57 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/W3dx1eLXIQ4az-pSgrqwRaZG0XA>
Cc: ot@cisco.com, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 13:50:59 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-6man-resilient-rs-05: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for working through my discuss (and Alia's comment), which was


---

I'm piling on Barry's Comment as a Discuss, which should be easy to
discuss, but ... in this text:

3.  Configuring the use of retransmissions

   Implementations of this specification MAY provide a configuration
   option to enable or disable the use of such potentially infinite
   retransmissions.  If the implementation provides such a configuration
   option, it MUST be able to enable/disable retransmissions on a per-
   interface basis.
   
You can tell me that it's a LAN, so the transport ADs can go back to
sleep, but I was surprised that this configuration option was a MAY. 

I was also surprised that there was no guidance about the default setting
(on or off), but let's start with the MAY.

IP does get tunneled to new and exciting places ... and infinite
retransmissions are infinite ...

---

Extreme nit alert:

   In general, the delay may be unacceptable in some
   scenarios.
   
would make more sense to me without the "in general".



From nobody Thu Apr  9 06:52:08 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5511A1A8A; Thu,  9 Apr 2015 06:52:05 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deR3granhdca; Thu,  9 Apr 2015 06:52:03 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::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 3CEF71A1A88; Thu,  9 Apr 2015 06:52:03 -0700 (PDT)
Received: by lbcga7 with SMTP id ga7so41955656lbc.1; Thu, 09 Apr 2015 06:52:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cdf75to/e7dCoT73VQlD4SUMMqaprTv3HD6lYEEA/h8=; b=tBCcaD946LobpgvLxMTbcW7eD07PwRbxx1IxqOC56t3KlZFlb9RgTGKd7AtIOJf41/ jO0T0Jp8heEtjxGyXK4jhfUwsVyH45K/5rtemsV0AO1bkVqmsclm8F/gB4GA0D8icU8L 5829QimVMXS0tWCIk0kRTJaQhv7n6jUTp1d1BYln31Ikjp0nEN6Cb0m4qLQyfKMp8iIB mWBiz7LAZ1Rb+rsPc/nik2nav/2WfOD5Nigt9lhrMRK/4NCR3XwsJFR9VLzUssSsCPxl mbEMJ+x3/5WWIG/ns4StTmO8bC3+FfmTZ2i+Y7WRoAZq1ozMayCsQd1SeTIjdoW+vEZ3 CJdA==
MIME-Version: 1.0
X-Received: by 10.152.206.75 with SMTP id lm11mr4717897lac.41.1428587521656; Thu, 09 Apr 2015 06:52:01 -0700 (PDT)
Received: by 10.152.129.3 with HTTP; Thu, 9 Apr 2015 06:52:01 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628B6F3C1@eusaamb107.ericsson.se>
References: <20150407215627.13544.1729.idtracker@ietfa.amsl.com> <E87B771635882B4BA20096B589152EF628B6DD58@eusaamb107.ericsson.se> <CAKKJt-ciMU-kuuwiwiSUwDP6zsL3wu2TP7t9hEs-SYT3iPE3dQ@mail.gmail.com> <E87B771635882B4BA20096B589152EF628B6F3C1@eusaamb107.ericsson.se>
Date: Thu, 9 Apr 2015 08:52:01 -0500
Message-ID: <CAKKJt-cVVYaR9yx-H4i8v3DhRKDP9HZfAByB4aSRhGr0PiY4Zg@mail.gmail.com>
Subject: Re: Alia Atlas' No Objection on draft-ietf-6man-resilient-rs-05: (with COMMENT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=001a1133bdc6c24b4305134af38e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oi9FHJ12J7bWCKilH9OWg-ryvUE>
Cc: "ot@cisco.com" <ot@cisco.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 13:52:05 -0000

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

Hi, Suresh,

On Wed, Apr 8, 2015 at 11:52 PM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> Hi Alia and Spencer,
>    I will specify the default in the next revision. Thanks for your
> comments.
>

Oh, thank YOU.

I cleared based on the IOU revision.

Spencer


>
> Regards
> Suresh
>
> On 04/08/2015 04:01 AM, Spencer Dawkins at IETF wrote:
> > Hi, Suresh,
> > On Apr 7, 2015 23:45, "Suresh Krishnan" <suresh.krishnan@ericsson.com
> > <mailto:suresh.krishnan@ericsson.com>> wrote:
> >  >
> >  > Hi Alia,
> >  >    Thanks for your comment.
> >  >
> >  > On 04/07/2015 05:56 PM, Alia Atlas wrote:
> >  > > To continue a bit on Spencer's Discuss and Barry's Comment, I'd
> > prefer to
> >  > > see a default for the configuration.  I'd assume it would be "off"
> to
> >  > > continue to provide current behavior, but I don't really care.
> >  > > Consistency is my concern.
> >  >
> >  > OK. Will add a default. I have responded to Spencer and I will make
> the
> >  > update as soon as I get a response from him as well.
> >
> > I understand Alia's preference for no-change-in-behavior-by-default
> > (Alia is suspicious enough to be a TSV AD!), and I understand that
> > you're trying to change the current case so that devices no longer just
> > stop sending for 30 minutes.
> >
> > I'm happy to defer to people who have thought about this, on which way
> > the default goes, as long as there's a consistent default.
> >
> > Spencer
> >
> >  > Thanks
> >  > Suresh
> >  >
> >  >
> >  >
> >
>
>

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

<div dir=3D"ltr">Hi, Suresh,<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Wed, Apr 8, 2015 at 11:52 PM, Suresh Krishnan <span dir=3D"lt=
r">&lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" target=3D"_blank">su=
resh.krishnan@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">Hi Alia and Spencer,<br>
=C2=A0 =C2=A0I will specify the default in the next revision. Thanks for yo=
ur<br>
comments.<br></blockquote><div><br></div><div>Oh, thank YOU.</div><div><br>=
</div><div>I cleared based on the IOU revision.</div><div><br></div><div>Sp=
encer</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Suresh<br>
</font></span><span class=3D"im HOEnZb"><br>
On 04/08/2015 04:01 AM, Spencer Dawkins at IETF wrote:<br>
&gt; Hi, Suresh,<br>
&gt; On Apr 7, 2015 23:45, &quot;Suresh Krishnan&quot; &lt;<a href=3D"mailt=
o:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a><br>
</span><div class=3D"HOEnZb"><div class=3D"h5">&gt; &lt;mailto:<a href=3D"m=
ailto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a>&gt;&gt=
; wrote:<br>
&gt;=C2=A0 &gt;<br>
&gt;=C2=A0 &gt; Hi Alia,<br>
&gt;=C2=A0 &gt;=C2=A0 =C2=A0 Thanks for your comment.<br>
&gt;=C2=A0 &gt;<br>
&gt;=C2=A0 &gt; On 04/07/2015 05:56 PM, Alia Atlas wrote:<br>
&gt;=C2=A0 &gt; &gt; To continue a bit on Spencer&#39;s Discuss and Barry&#=
39;s Comment, I&#39;d<br>
&gt; prefer to<br>
&gt;=C2=A0 &gt; &gt; see a default for the configuration.=C2=A0 I&#39;d ass=
ume it would be &quot;off&quot; to<br>
&gt;=C2=A0 &gt; &gt; continue to provide current behavior, but I don&#39;t =
really care.<br>
&gt;=C2=A0 &gt; &gt; Consistency is my concern.<br>
&gt;=C2=A0 &gt;<br>
&gt;=C2=A0 &gt; OK. Will add a default. I have responded to Spencer and I w=
ill make the<br>
&gt;=C2=A0 &gt; update as soon as I get a response from him as well.<br>
&gt;<br>
&gt; I understand Alia&#39;s preference for no-change-in-behavior-by-defaul=
t<br>
&gt; (Alia is suspicious enough to be a TSV AD!), and I understand that<br>
&gt; you&#39;re trying to change the current case so that devices no longer=
 just<br>
&gt; stop sending for 30 minutes.<br>
&gt;<br>
&gt; I&#39;m happy to defer to people who have thought about this, on which=
 way<br>
&gt; the default goes, as long as there&#39;s a consistent default.<br>
&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt;=C2=A0 &gt; Thanks<br>
&gt;=C2=A0 &gt; Suresh<br>
&gt;=C2=A0 &gt;<br>
&gt;=C2=A0 &gt;<br>
&gt;=C2=A0 &gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a1133bdc6c24b4305134af38e--


From nobody Thu Apr  9 09:15:25 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C9B1B2E69 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 09:15:20 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x7Z25qVWCbbv for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 09:15:18 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 C988C1B2E66 for <ipv6@ietf.org>; Thu,  9 Apr 2015 09:15:18 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t39GFCUO014667 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Apr 2015 09:15:14 -0700
Message-ID: <5526A58F.7040403@acm.org>
Date: Thu, 09 Apr 2015 09:15:11 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: Re: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
In-Reply-To: <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVZI6QVvkYTQ/6oQKHsuO+f0r/kC9NgnTsjkoodiLJ+8DFD46LTUf6b2HUtOmmeJ8gdhM5ML4sRjPNSdtIRAsH22
X-Sonic-ID: C;tOtzmdPe5BGARNBwQIsAyQ== M;ItqxmtPe5BGARNBwQIsAyQ==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1oDGaGxDIKcNtUx9kxb3d4ZMdsY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 16:15:20 -0000

Thanks for the reminder.

I support this draft (kind of obvious since I asked for the adoption call).

The reason for why I think this is important is that we should avoid any 
(further) fragmentation of ND for different types of networks and hosts, 
and instead provide different options at deployment.

Regards,
    Erik

On 4/8/15 12:19 PM, Bob Hinden wrote:
> Reminder.  Please send comments on this adoption call.
>
> Thanks
> Bob & Ole
>
>
>> Begin forwarded message:
>>
>> From: Bob Hinden <bob.hinden@gmail.com>
>> Subject: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
>> Date: March 27, 2015 at 8:34:09 AM PDT
>> Cc: 6man Chairs <6man-chairs@tools.ietf.org>
>> To: IPv6 List <ipv6@ietf.org>
>>
>> This message starts a two week 6MAN Working Group Last Call on adopting:
>>
>>         Title           : IPv6 Neighbor Discovery Optional Unicast RS/RA Refresh
>>         Authors         : Erik Nordmark
>>                           Andrew Yourtchenko
>>                           Suresh Krishnan
>>         Filename        : draft-nordmark-6man-rs-refresh-01.txt
>>         Pages           : 12
>>         Date            : 2014-10-27
>>
>>         https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01
>>
>> as a working group document. Substantive comments and statements of support for adopting this document should be directed to the mailing list.  Editorial suggestions can be sent to the authors.  This adoption call will end on April 10, 2015.
>>
>> Regards,
>>
>> Bob Hinden & Ole Trøan
>>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Thu Apr  9 10:57:46 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEC31B300B; Thu,  9 Apr 2015 10:57:45 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mw3GhTTirUvB; Thu,  9 Apr 2015 10:57:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEBF1B3017; Thu,  9 Apr 2015 10:57:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <6man-chairs@ietf.org>, <ipv6@ietf.org>, <ot@cisco.com>
Subject: ID Tracker State Update Notice: <draft-ietf-6man-resilient-rs-05.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150409175740.23462.49804.idtracker@ietfa.amsl.com>
Date: Thu, 09 Apr 2015 10:57:40 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EbOe4FAFUwuQYYUZG1yHfct1KKE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 17:57:45 -0000

IESG state changed to Approved-announcement to be sent::Revised I-D Needed from IESG Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/


From nobody Thu Apr  9 11:33:04 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93C571A87E1 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 11:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 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, SPF_PASS=-0.001] autolearn=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 rS6W8YxAA1Y1 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 11:33:01 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::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 8DEDD1A87C2 for <ipv6@ietf.org>; Thu,  9 Apr 2015 11:33:00 -0700 (PDT)
Received: by lagv1 with SMTP id v1so96134614lag.3 for <ipv6@ietf.org>; Thu, 09 Apr 2015 11:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=JLjlZaDm0d7QcLe0RSskuUkDAS2WXeG4+7SVrXGB9ME=; b=iJuQPlGv+F2YEdTK5flt55IweKnoiQbTzMean7uD9+l52IGWTQpthkAO14aVWrWA/j EZZLatTH5J7FeFejxhOMrRuZNZrVB/9HStXge0H6rSjj+h5uWxuWdAwVuxDTTGjUkm28 lmo1CmfZpNg7ws7YRBCjBXDoVaQ+8JazhdEU/e56Fdq3Xokqg9DSQx3ZSDyMtdJllJBU 2EDEv87RRXVJe1PsB6CEBqJ2NX2APLd4R6ys4Hdhq6WZDzW/kTB57jlUGdZTRKy0xGby Ao15XMpKw/GsKirhubVuAi5c31D1NzC4pFmcT8KR8JlFr2W/gxvXXnzTpgU8ROg5c/e4 m/Wg==
MIME-Version: 1.0
X-Received: by 10.112.93.72 with SMTP id cs8mr25180134lbb.15.1428604379061; Thu, 09 Apr 2015 11:32:59 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Thu, 9 Apr 2015 11:32:58 -0700 (PDT)
In-Reply-To: <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
Date: Thu, 9 Apr 2015 13:32:59 -0500
Message-ID: <CAC8QAcfRX+WMBwR4SQYMCKnZ2+Q4qKHAXa5XtoYAnf+CxG7NbQ@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ERex3-hHetXB-SHRYgqWhue7lck>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 18:33:02 -0000

I also support adoption.

Regards,

Behcet

On Wed, Apr 8, 2015 at 2:19 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> Reminder.  Please send comments on this adoption call.
>
> Thanks
> Bob & Ole
>
>
>> Begin forwarded message:
>>
>> From: Bob Hinden <bob.hinden@gmail.com>
>> Subject: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
>> Date: March 27, 2015 at 8:34:09 AM PDT
>> Cc: 6man Chairs <6man-chairs@tools.ietf.org>
>> To: IPv6 List <ipv6@ietf.org>
>>
>> This message starts a two week 6MAN Working Group Last Call on adopting:
>>
>>        Title           : IPv6 Neighbor Discovery Optional Unicast RS/RA =
Refresh
>>        Authors         : Erik Nordmark
>>                          Andrew Yourtchenko
>>                          Suresh Krishnan
>>        Filename        : draft-nordmark-6man-rs-refresh-01.txt
>>        Pages           : 12
>>        Date            : 2014-10-27
>>
>>        https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01
>>
>> as a working group document. Substantive comments and statements of supp=
ort for adopting this document should be directed to the mailing list.  Edi=
torial suggestions can be sent to the authors.  This adoption call will end=
 on April 10, 2015.
>>
>> Regards,
>>
>> Bob Hinden & Ole Tr=C3=B8an
>>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Thu Apr  9 13:51:22 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 127481B3261 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 13:51:21 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6eu_Rz5L2-v for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 13:51:18 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::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 501141B324F for <6man@ietf.org>; Thu,  9 Apr 2015 13:51:16 -0700 (PDT)
Received: by pabtp1 with SMTP id tp1so55463885pab.2 for <6man@ietf.org>; Thu, 09 Apr 2015 13:51:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CXFGn68pV7g2QMj6IkqF77u5diJjN3ad2fIyR5KtgLE=; b=dw43/lKRqC8Q56W7YPpL+ezo31A9BhzN1VvJeeinAklIe0H9+kkqcnzPK2JMx6tPo8 bPzszOnTsJ0wbJoNy2Cxx2ZoIpPL+IfdOmjVj2/Cb/gbr3cdXOTapN/VTdwxEbEPNabh aWUzPIR88WAOy4vre7RkrhE/YDlIAghIy/AiRRz3X0+IMSeWx7/WrFhDG23gB7NjxmSF hc4IwmTIWrm/HGGrbVjrvYQCl/xRQuELD8ObT5PgrqZKMeFVZOFiCqar1Egk/FNCnI17 Vv9TL2Q9yRMqO3hm4xeXzXHSJRYlV5fypPGp/SqT+1ccXjfgpUoI/DHw4vbidjaTifi1 JP/Q==
X-Received: by 10.70.5.225 with SMTP id v1mr59220400pdv.103.1428612676045; Thu, 09 Apr 2015 13:51:16 -0700 (PDT)
Received: from ?IPv6:2406:e007:65de:1:28cc:dc4c:9703:6781? ([2406:e007:65de:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id fs16sm10168643pdb.12.2015.04.09.13.51.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 13:51:14 -0700 (PDT)
Message-ID: <5526E648.4020004@gmail.com>
Date: Fri, 10 Apr 2015 08:51:20 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: sarikaya@ieee.org, Ray Hunter <v6ops@globis.net>
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com> <55240885.9060200@globis.net> <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com>
In-Reply-To: <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vO8hDalQ6mcljBVDYpzG13IG11w>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 20:51:21 -0000

On 08/04/2015 05:02, Behcet Sarikaya wrote:
> Hi Ray,
> 
> On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <v6ops@globis.net> wrote:

...
>> But I'd expect any "SADR overview" to also cover router - router forwarding
>> behaviour. Not just end host - router.
> 
> Can you offer some text?

At the moment that's covered by draft-baker-rtgwg-src-dst-routing-use-cases.
IMHO the separation into host and router drafts is reasonable, so that
each draft fits mainly into a single WG.

    Brian


From nobody Thu Apr  9 14:03:22 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C29E1B3308; Thu,  9 Apr 2015 14:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSkK4TW0yPZL; Thu,  9 Apr 2015 14:03:16 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0797.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::797]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 139CB1B3300; Thu,  9 Apr 2015 14:03:07 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.1.130.23; Thu, 9 Apr 2015 21:02:49 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Thu, 9 Apr 2015 21:02:49 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQcwfSHRL6IJKFxUecEJirrd5rvJ1FKqxw
Date: Thu, 9 Apr 2015 21:02:49 +0000
Message-ID: <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com>
In-Reply-To: <20150409205737.10780.29197.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB442;
x-microsoft-antispam-prvs: <CO1PR05MB442CC523D2FECBA1CEA4D89AEFB0@CO1PR05MB442.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(51704005)(13464003)(377424004)(2900100001)(19580395003)(450100001)(2950100001)(19580405001)(92566002)(62966003)(50986999)(87936001)(86362001)(46102003)(2501003)(76576001)(107886001)(33656002)(122556002)(1720100001)(15975445007)(54356999)(74316001)(106116001)(77156002)(102836002)(76176999)(66066001)(2656002)(99286002)(2420400003)(230783001)(40100003); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CO1PR05MB442; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB442; 
x-forefront-prvs: 0541031FF6
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Apr 2015 21:02:49.1193 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB442
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/atqYgKo0QSWtXACe5702NnPuzBo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 21:03:19 -0000

Rm9sa3MsDQoNCkkgaGF2ZSB1cGRhdGVkIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni4gUGxl
YXNlIHRlbGwgbWUgaWYgSSBoYXZlIGFkZHJlc3NlZCBhbGwgb2YgeW91ciBjb21tZW50cy4NCg0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSb24NCg0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4gU2VudDogVGh1cnNk
YXksIEFwcmlsIDA5LCAyMDE1IDQ6NTggUE0NCj4gVG86IFJvbmFsZCBCb25pY2E7IFN1cmVzaCBL
cmlzaG5hbjsgU3VyZXNoIEtyaXNobmFuOyBDYXJsb3MgUGlnbmF0YXJvOw0KPiBSb25hbGQgQm9u
aWNhOyBDYXJsb3MgUGlnbmF0YXJvDQo+IFN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlv
biBmb3IgZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2LTA1LnR4dA0KPiANCj4gDQo+IEEgbmV3
IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYtMDUudHh0DQo+IGhh
cyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgUm9uIEJvbmljYSBhbmQgcG9zdGVkIHRv
IHRoZSBJRVRGDQo+IHJlcG9zaXRvcnkuDQo+IA0KPiBOYW1lOgkJZHJhZnQtaWV0Zi1pbnRhcmVh
LWdyZS1pcHY2DQo+IFJldmlzaW9uOgkwNQ0KPiBUaXRsZToJCUlQdjYgU3VwcG9ydCBmb3IgR2Vu
ZXJpYyBSb3V0aW5nIEVuY2Fwc3VsYXRpb24gKEdSRSkNCj4gRG9jdW1lbnQgZGF0ZToJMjAxNS0w
NC0xMA0KPiBHcm91cDoJCWludGFyZWENCj4gUGFnZXM6CQk4DQo+IFVSTDogICAgICAgICAgICBo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLWludGFyZWEtZ3Jl
LWlwdjYtDQo+IDA1LnR4dA0KPiBTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2Lw0KPiBIdG1saXplZDogICAg
ICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pbnRhcmVhLWdyZS1pcHY2
LTA1DQo+IERpZmY6ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1k
cmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYtMDUNCj4gDQo+IEFic3RyYWN0Og0KPiAgICBHZW5l
cmljIFJvdXRpbmcgRW5jYXBzdWxhdGlvbiAoR1JFKSBjYW4gYmUgdXNlZCB0byBjYXJyeSBhbnkg
bmV0d29yay0NCj4gICAgbGF5ZXIgcGF5bG9hZCBwcm90b2NvbCBvdmVyIGFueSBuZXR3b3JrLWxh
eWVyIGRlbGl2ZXJ5IHByb3RvY29sLiAgR1JFDQo+ICAgIHByb2NlZHVyZXMgYXJlIHNwZWNpZmll
ZCBmb3IgSVB2NCwgdXNlZCBhcyBlaXRoZXIgdGhlIHBheWxvYWQgb3INCj4gICAgZGVsaXZlcnkg
cHJvdG9jb2wuICBIb3dldmVyLCBHUkUgcHJvY2VkdXJlcyBhcmUgbm90IHNwZWNpZmllZCBmb3IN
Cj4gICAgSVB2Ni4NCj4gDQo+ICAgIFRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIEdSRSBwcm9jZWR1
cmVzIGZvciBJUHY2LCB1c2VkIGFzIGVpdGhlciB0aGUNCj4gICAgcGF5bG9hZCBvciBkZWxpdmVy
eSBwcm90b2NvbC4gIEl0IHVwZGF0ZXMgdGhlIEdSRSBzcGVjaWZpY2F0aW9uLCBSRkMNCj4gICAg
Mjc4NC4NCj4gDQo+IA0KPiANCj4gDQo+IA0KPiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtl
IGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+IHVudGls
IHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0
Zi5vcmcuDQo+IA0KPiBUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=


From nobody Thu Apr  9 14:26:42 2015
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD6D1B3355 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 14:26:40 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzKhsMaLnYfq for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 14:26:38 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::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 5F82F1B3357 for <ipv6@ietf.org>; Thu,  9 Apr 2015 14:26:37 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fernando@gont.com.ar>) id 1YgJy6-0006B3-QR; Thu, 09 Apr 2015 23:26:35 +0200
Message-ID: <5526C50D.4030906@gont.com.ar>
Date: Thu, 09 Apr 2015 15:29:33 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: Re: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
In-Reply-To: <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HEQNKqYmN_oIZ3ZThzLlSziqehw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 21:26:40 -0000

On 04/08/2015 04:19 PM, Bob Hinden wrote:
> Reminder.  Please send comments on this adoption call.

I support adoption of this document as a 6man wg item.

I will send a detailed review asap -- hopefully this weekend.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Thu Apr  9 15:26:46 2015
Return-Path: <lucy.yong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B6E91B3297; Thu,  9 Apr 2015 14:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ir5mgLFUliBl; Thu,  9 Apr 2015 14:14:54 -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 3BDBD1B327A; Thu,  9 Apr 2015 14:14:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUR23682; Thu, 09 Apr 2015 21:14:51 +0000 (GMT)
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Apr 2015 22:14:51 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml705-chm ([10.193.5.142]) with mapi id 14.03.0158.001; Thu, 9 Apr 2015 14:14:38 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQcwfSHRL6IJKFxUecEJirrd5rvJ1FKqxwgAACbyA=
Date: Thu, 9 Apr 2015 21:14:38 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.144.23]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2uGG_Wd6s99S9eOswUBK8LMmuAU>
X-Mailman-Approved-At: Thu, 09 Apr 2015 15:26:43 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 21:14:56 -0000

Hi Ron,

Security considerations should state that IPsec [RFC4301] can be used to pr=
ovide payload security and privacy over an IP network where the security is=
 a concern.

Thanks,
Lucy=20

-----Original Message-----
From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald Bonic=
a
Sent: Thursday, April 09, 2015 4:03 PM
To: int-area@ietf.org; ipv6@ietf.org
Subject: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre=
-ipv6-05.txt

Folks,

I have updated draft-ietf-intarea-gre-ipv6. Please tell me if I have addres=
sed all of your comments.

                                                  Ron


> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, April 09, 2015 4:58 PM
> To: Ronald Bonica; Suresh Krishnan; Suresh Krishnan; Carlos Pignataro;=20
> Ronald Bonica; Carlos Pignataro
> Subject: New Version Notification for=20
> draft-ietf-intarea-gre-ipv6-05.txt
>=20
>=20
> A new version of I-D, draft-ietf-intarea-gre-ipv6-05.txt
> has been successfully submitted by Ron Bonica and posted to the IETF=20
> repository.
>=20
> Name:		draft-ietf-intarea-gre-ipv6
> Revision:	05
> Title:		IPv6 Support for Generic Routing Encapsulation (GRE)
> Document date:	2015-04-10
> Group:		intarea
> Pages:		8
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-intarea-gr=
e-ipv6-
> 05.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-intarea-gre-i=
pv6/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-intarea-gre-ipv6-05
> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-intarea-gre=
-ipv6-05
>=20
> Abstract:
>    Generic Routing Encapsulation (GRE) can be used to carry any network-
>    layer payload protocol over any network-layer delivery protocol.  GRE
>    procedures are specified for IPv4, used as either the payload or
>    delivery protocol.  However, GRE procedures are not specified for
>    IPv6.
>=20
>    This document specifies GRE procedures for IPv6, used as either the
>    payload or delivery protocol.  It updates the GRE specification, RFC
>    2784.
>=20
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> The IETF Secretariat

_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area


From nobody Thu Apr  9 19:35:08 2015
Return-Path: <liushucheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AB01A90D7 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 19:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2XneFn_45W6 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 19:35: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 A839D1A90D4 for <ipv6@ietf.org>; Thu,  9 Apr 2015 19:35:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRF76850; Fri, 10 Apr 2015 02:35:02 +0000 (GMT)
Received: from SZXEMA411-HUB.china.huawei.com (10.82.72.70) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Apr 2015 03:35:02 +0100
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.195]) by szxema411-hub.china.huawei.com ([10.82.72.70]) with mapi id 14.03.0158.001; Fri, 10 Apr 2015 10:34:58 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: Erik Nordmark <nordmark@acm.org>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Topic: Fwd: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Index: AQHQaKOBwD18hvMcUU+SJG8ivd+zeZ1DkK+lgADYooCAATLb0A==
Date: Fri, 10 Apr 2015 02:34:57 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB600CBE26@SZXEMA509-MBS.china.huawei.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com> <5526A58F.7040403@acm.org>
In-Reply-To: <5526A58F.7040403@acm.org>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.78.105]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/F0IDcWBQIn9OROIoS7L2T26GBlQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 02:35:07 -0000

I support the adoption of this draft, and also second the reason Erik poste=
d.

Regards,
Will (Shucheng LIU)

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Erik Nordmark
> Sent: Friday, April 10, 2015 12:15 AM
> To: Bob Hinden; IPv6 List
> Subject: Re: Fwd: 6MAN WG Adoption Call:
> draft-nordmark-6man-rs-refresh-01
>=20
>=20
> Thanks for the reminder.
>=20
> I support this draft (kind of obvious since I asked for the adoption call=
).
>=20
> The reason for why I think this is important is that we should avoid any
> (further) fragmentation of ND for different types of networks and hosts, =
and
> instead provide different options at deployment.
>=20
> Regards,
>     Erik
>=20
> On 4/8/15 12:19 PM, Bob Hinden wrote:
> > Reminder.  Please send comments on this adoption call.
> >
> > Thanks
> > Bob & Ole
> >
> >
> >> Begin forwarded message:
> >>
> >> From: Bob Hinden <bob.hinden@gmail.com>
> >> Subject: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
> >> Date: March 27, 2015 at 8:34:09 AM PDT
> >> Cc: 6man Chairs <6man-chairs@tools.ietf.org>
> >> To: IPv6 List <ipv6@ietf.org>
> >>
> >> This message starts a two week 6MAN Working Group Last Call on adoptin=
g:
> >>
> >>         Title           : IPv6 Neighbor Discovery Optional Unicast
> RS/RA Refresh
> >>         Authors         : Erik Nordmark
> >>                           Andrew Yourtchenko
> >>                           Suresh Krishnan
> >>         Filename        : draft-nordmark-6man-rs-refresh-01.txt
> >>         Pages           : 12
> >>         Date            : 2014-10-27
> >>
> >>         https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01
> >>
> >> as a working group document. Substantive comments and statements of
> support for adopting this document should be directed to the mailing list=
.
> Editorial suggestions can be sent to the authors.  This adoption call wil=
l end on
> April 10, 2015.
> >>
> >> Regards,
> >>
> >> Bob Hinden & Ole Tr=F8an
> >>
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Thu Apr  9 20:44:03 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC111AC42A; Thu,  9 Apr 2015 20:44: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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80HhoEe-iWc0; Thu,  9 Apr 2015 20:44:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 704321AC417; Thu,  9 Apr 2015 20:44:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-resilient-rs-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150410034400.31567.18832.idtracker@ietfa.amsl.com>
Date: Thu, 09 Apr 2015 20:44:00 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WAMiQQ31YQ31MHtIcsKmqCnomas>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 03:44:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Packet loss resiliency for Router Solicitations
        Authors         : Suresh Krishnan
                          Dmitry Anipko
                          Dave Thaler
	Filename        : draft-ietf-6man-resilient-rs-06.txt
	Pages           : 6
	Date            : 2015-04-09

Abstract:
   When an interface on a host is initialized, the host transmits Router
   Solicitations in order to minimize the amount of time it needs to
   wait until the next unsolicited multicast Router Advertisement is
   received.  In certain scenarios, these router solicitations
   transmitted by the host might be lost.  This document specifies a
   mechanism for hosts to cope with the loss of the initial Router
   Solicitations.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-resilient-rs-06


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/


From nobody Thu Apr  9 20:44:06 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF1F1AC42D; Thu,  9 Apr 2015 20:44:03 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HL0FgcpDueV1; Thu,  9 Apr 2015 20:44:02 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB821AC426; Thu,  9 Apr 2015 20:44:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <6man-chairs@ietf.org>, <ipv6@ietf.org>, <ot@cisco.com>, <brian@innovationslab.net>
Subject: New Version Notification - draft-ietf-6man-resilient-rs-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150410034401.31567.36954.idtracker@ietfa.amsl.com>
Date: Thu, 09 Apr 2015 20:44:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hXyr6F4QTIeciKsWlwK-0Kgb4Kk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 03:44:03 -0000

A new version (-06) has been submitted for draft-ietf-6man-resilient-rs:
http://www.ietf.org/internet-drafts/draft-ietf-6man-resilient-rs-06.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-resilient-rs-06

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.

IETF Secretariat.


From nobody Thu Apr  9 23:15:51 2015
Return-Path: <ot@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83A2A1ACE67 for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 23:15:49 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T560g-aelklP for <ipv6@ietfa.amsl.com>; Thu,  9 Apr 2015 23:15:48 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B212B1ACE65 for <6man@ietf.org>; Thu,  9 Apr 2015 23:15:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1499; q=dns/txt; s=iport; t=1428646547; x=1429856147; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=P4RfvStorqrrvpEsujWB5KD5dfQNiWNqUYbyt72Xmcs=; b=F0cMJuDrT9Cedq7a8X5e2Ed3mLLhuX7Y1S8ZH2QIcZBU2HACaaJR6AK9 oRPiZJhJZ4hJ2zPQJK0TnpvaWdWR9Bl5liF8eSE82Xx++6IsqHYWoc1al W0kTdT0YCke7hFn5HMurQ7tCbbT8wgWXAzNsXxnZcz2dczcJhdYXBwbeQ E=;
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D5AwBfaSdV/xbLJq1cgmaEacE5CYdPAoF+FAEBAQEBAQF9hCABAQQjVAIQC0ICAlcGiD0Bt2WWVQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLK4R8B4JoL4EWAQSScYgelGUig3GDMAEBAQ
X-IronPort-AV: E=Sophos;i="5.11,555,1422921600";  d="asc'?scan'208";a="424443569"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 10 Apr 2015 06:15:46 +0000
Received: from gomlefisk.localdomain (ssh-ams-2.cisco.com [144.254.73.146]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t3A6Fjbd031764 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Apr 2015 06:15:45 GMT
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 958D94292149; Fri, 10 Apr 2015 08:15:47 +0200 (CEST)
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D050FF68-02FA-48AE-B274-09CD54AA590A"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <ot@cisco.com>
In-Reply-To: <5526E648.4020004@gmail.com>
Date: Fri, 10 Apr 2015 08:15:46 +0200
Message-Id: <F48F50DA-4257-48E7-B34D-A0543EA3E50D@cisco.com>
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com> <55240885.9060200@globis.net> <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com> <5526E648.4020004@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oKVpcdFpLIZMMlr4VxtwctAkCVs>
Cc: Ray Hunter <v6ops@globis.net>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 06:15:49 -0000

--Apple-Mail=_D050FF68-02FA-48AE-B274-09CD54AA590A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> ...
>>> But I'd expect any "SADR overview" to also cover router - router =
forwarding
>>> behaviour. Not just end host - router.
>>=20
>> Can you offer some text?
>=20
> At the moment that's covered by =
draft-baker-rtgwg-src-dst-routing-use-cases.
> IMHO the separation into host and router drafts is reasonable, so that
> each draft fits mainly into a single WG.

fully agree. SADR might not be the best name for the host portion.
perhaps something like "IPv6 Multi-homed host gaps=E2=80=9D?

Ole

--Apple-Mail=_D050FF68-02FA-48AE-B274-09CD54AA590A
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

iQEcBAEBCgAGBQJVJ2qTAAoJEP0up8EdT99J1+8H/15ljugv57VUKK/J77rKkdKd
IK3k6uX2Crbnv9Gx48BYJ/xVE7dpxp1JYrxy3k3OcpoAdef1k9l11QUMBzcfq1Ge
uve2asiIvg5LzTu/kp/ySq5JOLeh+AnGA1o1nf2XoHiY+HWtj9zKFatTFr4jKQVJ
TDiRzreqNM68Sc8WEsOHH05YkF4BZqO+pITX/fRPw5SW1S52IjjXb61r3REFzDH9
WPIGANTJkWkZLDcdn9vAR2pcTvPZ8B9zXafUFJoT1roeala3Z3StY0wM4qgxPq0c
lOVh3Y8yAYtMrv+xFYThtkilkWAB1WSzntC+4N9b79q+rY6WYbmxz1iJj3oEpz8=
=/5jS
-----END PGP SIGNATURE-----

--Apple-Mail=_D050FF68-02FA-48AE-B274-09CD54AA590A--


From nobody Fri Apr 10 03:39:16 2015
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04451B2BD4 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 03:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUi5BPcC-TAL for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 03:39:12 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 82A111B2BD6 for <6man@ietf.org>; Fri, 10 Apr 2015 03:39:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B6615402D6; Fri, 10 Apr 2015 12:39:11 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zm9XMqW45hN8; Fri, 10 Apr 2015 12:39:08 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:8831:c50:63b9:f10f]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 95A7740189; Fri, 10 Apr 2015 12:39:08 +0200 (CEST)
Message-ID: <5527A84B.8090201@globis.net>
Date: Fri, 10 Apr 2015 12:39:07 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com> <55240885.9060200@globis.net> <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com> <5526E648.4020004@gmail.com> <F48F50DA-4257-48E7-B34D-A0543EA3E50D@cisco.com>
In-Reply-To: <F48F50DA-4257-48E7-B34D-A0543EA3E50D@cisco.com>
Content-Type: multipart/alternative; boundary="------------080804010609060405050705"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fqtamREiDXqjI6sVP_d3offN_Zs>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 10:39:15 -0000

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



> Ole Troan <mailto:ot@cisco.com>
> 10 April 2015 08:15
>
> fully agree. SADR might not be the best name for the host portion.
> perhaps something like "IPv6 Multi-homed host gaps”?
>
> Ole
> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 9 April 2015 22:51
> On 08/04/2015 05:02, Behcet Sarikaya wrote:
>> Hi Ray,
>>
>> On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter<v6ops@globis.net>  wrote:
>
> ...
>>> But I'd expect any "SADR overview" to also cover router - router forwarding
>>> behaviour. Not just end host - router.
>> Can you offer some text?
>
> At the moment that's covered by draft-baker-rtgwg-src-dst-routing-use-cases.
> IMHO the separation into host and router drafts is reasonable, so that
> each draft fits mainly into a single WG.
>
>      Brian
> Behcet Sarikaya <mailto:sarikaya2012@gmail.com>
> 7 April 2015 19:02
> Hi Ray,
>
> On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter<v6ops@globis.net>  wrote:
>> Behcet Sarikaya wrote:
>>> Hi all,
>>>
>>> I submitted Rev. 06 of SADR Overview draft. This revision contains
>>> changes from IETF 92, namely:
>>>
>>> -corporate VPN  scenario in Section 3 contributed by Brian Carpenter
>>> as discussed in our F2F meeting in Dallas with the chairs, Brian,
>>> Pfister and myself.
>>>
>>> -Third party next hop text in Section 5 where the third part next hop
>>> issue has been left out of scope.
>>>
>>> I think this draft is ready for adoption call.
>>> Also contributors wishing to coauthor, send me an email.
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>>
>>> A new version of I-D, draft-sarikaya-6man-sadr-overview-06.txt
>>> has been successfully submitted by Behcet Sarikaya and posted to the
>>> IETF repository.
>>>
>>> Name:           draft-sarikaya-6man-sadr-overview
>>> Revision:       06
>>> Title:          Source Address Dependent Routing and Source Address
>>> Selection for IPv6 Hosts
>>> Document date:  2015-03-31
>>> Group:          Individual Submission
>>> Pages:          16
>>> URL:
>>>
>>> http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-06.txt
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
>>> Htmlized:
>>> http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06
>>> Diff:
>>> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-06
>>>
>>> Abstract:
>>>      This document presents the source address dependent routing from the
>>>      host perspective.  Multihomed hosts and hosts with multiple
>>>      interfaces are considered.  Different architectures are introduced
>>>      and with their help, why source address selection and next hop
>>>      resolution in view of source address dependent routing is needed is
>>>      explained.  The document concludes with an informative guidelines on
>>>      the different solution approaches.
>>>
>>> If host configuration is done using router advertisement messages
>>     then there is a need to define new router advertisement options for
>>     source address dependent routing.  These options include Route Prefix
>>     with Source Address/Prefix Option.  Other options such as Next Hop
>>     Address with Route Prefix option and Next Hop Address with Source
>>     Address and Route Prefix option will be considered in Section 5.3
>>
>> Like many others, I still don't get the need for the Next Hop Address
>> option, but I guess that could be thrashed out later.
>
> More or less. Section 5.3 makes the third party next hop work out of
> scope, maybe sometime in the future someone will be able to come up
> with a good use case, I believe so.
>
>> I also still wonder whether the WG really needs three drafts that have
>> considerable overlap, and yet still leave considerable gaps:
>>
>
> One is overview the other two are solution documents.
>
>> We have:
>>
>> https://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06
>> https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04
>> and
>> https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00
>>
>> But I'd expect any "SADR overview" to also cover router - router forwarding
>> behaviour. Not just end host - router.
>
> Can you offer some text?
>
>> And was there ever any agreement reached on which was the more beautiful of
>> https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04
>
> This should be
> draft-sarikaya-6man-sadr-ra
>
>   we do not plan on pursuing draft-sarikaya-6man-next-hop-ra-04 any
> further because of the third part next hop issue.
>
>   or
>> https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00 ?
>>
>> In my mind, https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00  is a
>> logical progression from https://tools.ietf.org/html/rfc4191
>>
>
> The other approach is to define a new option as in
> draft-sarikaya-6man-sadr-ra then we don't need an I flag. Also the
> point you have below could be discussed there.
>
>> But that also leaves major gaps on how routers would interact, plus any
>> potential issues at an AS-boundary e.g. updating BCP38 to filter inbound and
>> outbound SADR routes.
>
> Currently we (Pfister and I) are discussing how to merge these two
> solution documents. So I believe there will be one solution document
> in the end.
>
>> In short: I'm still not convinced we have the right problem statement.
>>
>
> Overview document is the one we have now after long discussions.
> Of course it could be improved, the plan is to improve it as a WG draft.
>
>
>> regards,
>> RayH
>>
>>
>>
>
Both of your comments make sense to me: host portion covered in this WG 
and changing the title.

What about other considerations then?

Such as potentially extending ICMP redirects to include source address 
specific applicability?

I know this has been discussed, but it isn't included in any problem 
statement yet AFAICS.

regards
RayH

--------------080804010609060405050705
Content-Type: multipart/related;
 boundary="------------050202080801060904000005"


--------------050202080801060904000005
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"><br>
<br>
<blockquote style="border: 0px none;" 
cite="mid:F48F50DA-4257-48E7-B34D-A0543EA3E50D@cisco.com" type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px"> 	<div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="ot@cisco.com" photoname="Ole Troan" 
src="cid:part1.02070109.08020207@globis.net" 
name="compose-unknown-contact.jpg" height="25px" width="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
   	<a moz-do-not-send="true" href="mailto:ot@cisco.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Ole Troan</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">10 April 2015 
08:15</span></font></div></div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div><!----><br>fully agree. 
SADR might not be the best name for the host portion.<br>perhaps 
something like "IPv6 Multi-homed host gaps”?<br><br>Ole<br></div></div>
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px"> 	<div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="brian.e.carpenter@gmail.com" photoname="Brian E 
Carpenter" src="cid:part1.02070109.08020207@globis.net" 
name="compose-unknown-contact.jpg" height="25px" width="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
   	<a moz-do-not-send="true" href="mailto:brian.e.carpenter@gmail.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Brian E Carpenter</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">9 April 2015 
22:51</span></font></div></div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><pre wrap="">On 08/04/2015 05:02, Behcet Sarikaya wrote:
</pre><blockquote type="cite"><pre wrap="">Hi Ray,

On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <a class="moz-txt-link-rfc2396E" href="mailto:v6ops@globis.net">&lt;v6ops@globis.net&gt;</a> wrote:
</pre></blockquote><pre wrap=""><!---->
...
</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">But I'd expect any "SADR overview" to also cover router - router forwarding
behaviour. Not just end host - router.
</pre></blockquote><pre wrap="">Can you offer some text?
</pre></blockquote><pre wrap=""><!---->
At the moment that's covered by draft-baker-rtgwg-src-dst-routing-use-cases.
IMHO the separation into host and router drafts is reasonable, so that
each draft fits mainly into a single WG.

    Brian
</pre></div>
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px"> 	<div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="sarikaya2012@gmail.com" photoname="Behcet Sarikaya" 
src="cid:part1.02070109.08020207@globis.net" 
name="compose-unknown-contact.jpg" height="25px" width="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
   	<a moz-do-not-send="true" href="mailto:sarikaya2012@gmail.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Behcet Sarikaya</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">7 April 2015 
19:02</span></font></div></div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><pre wrap="">Hi Ray,

On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <a class="moz-txt-link-rfc2396E" href="mailto:v6ops@globis.net">&lt;v6ops@globis.net&gt;</a> wrote:
</pre><blockquote type="cite"><pre wrap="">Behcet Sarikaya wrote:
</pre><blockquote type="cite"><pre wrap="">Hi all,

I submitted Rev. 06 of SADR Overview draft. This revision contains
changes from IETF 92, namely:

-corporate VPN  scenario in Section 3 contributed by Brian Carpenter
as discussed in our F2F meeting in Dallas with the chairs, Brian,
Pfister and myself.

-Third party next hop text in Section 5 where the third part next hop
issue has been left out of scope.

I think this draft is ready for adoption call.
Also contributors wishing to coauthor, send me an email.

Regards,

Behcet


A new version of I-D, draft-sarikaya-6man-sadr-overview-06.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-sarikaya-6man-sadr-overview
Revision:       06
Title:          Source Address Dependent Routing and Source Address
Selection for IPv6 Hosts
Document date:  2015-03-31
Group:          Individual Submission
Pages:          16
URL:

<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-06.txt">http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-06.txt</a>
Status:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/">https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/</a>
Htmlized:
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06">http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06</a>
Diff:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-06">http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-06</a>

Abstract:
    This document presents the source address dependent routing from the
    host perspective.  Multihomed hosts and hosts with multiple
    interfaces are considered.  Different architectures are introduced
    and with their help, why source address selection and next hop
    resolution in view of source address dependent routing is needed is
    explained.  The document concludes with an informative guidelines on
    the different solution approaches.

</pre></blockquote><blockquote type="cite"><pre wrap="">If host configuration is done using router advertisement messages
</pre></blockquote><pre wrap="">   then there is a need to define new router advertisement options for
   source address dependent routing.  These options include Route Prefix
   with Source Address/Prefix Option.  Other options such as Next Hop
   Address with Route Prefix option and Next Hop Address with Source
   Address and Route Prefix option will be considered in Section 5.3

Like many others, I still don't get the need for the Next Hop Address
option, but I guess that could be thrashed out later.
</pre></blockquote><pre wrap=""><!---->
More or less. Section 5.3 makes the third party next hop work out of
scope, maybe sometime in the future someone will be able to come up
with a good use case, I believe so.

</pre><blockquote type="cite"><pre wrap="">I also still wonder whether the WG really needs three drafts that have
considerable overlap, and yet still leave considerable gaps:

</pre></blockquote><pre wrap=""><!---->
One is overview the other two are solution documents.

</pre><blockquote type="cite"><pre wrap="">We have:

<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06">https://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-06</a>
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04">https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04</a>
and
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00">https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00</a>

But I'd expect any "SADR overview" to also cover router - router forwarding
behaviour. Not just end host - router.
</pre></blockquote><pre wrap=""><!---->
Can you offer some text?

</pre><blockquote type="cite"><pre wrap="">And was there ever any agreement reached on which was the more beautiful of
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04">https://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-04</a>
</pre></blockquote><pre wrap=""><!---->
This should be
draft-sarikaya-6man-sadr-ra

 we do not plan on pursuing draft-sarikaya-6man-next-hop-ra-04 any
further because of the third part next hop issue.

 or
</pre><blockquote type="cite"><pre wrap=""><a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00">https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00</a> ?

In my mind, <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00">https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00</a>  is a
logical progression from <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc4191">https://tools.ietf.org/html/rfc4191</a>

</pre></blockquote><pre wrap=""><!---->
The other approach is to define a new option as in
draft-sarikaya-6man-sadr-ra then we don't need an I flag. Also the
point you have below could be discussed there.

</pre><blockquote type="cite"><pre wrap="">But that also leaves major gaps on how routers would interact, plus any
potential issues at an AS-boundary e.g. updating BCP38 to filter inbound and
outbound SADR routes.
</pre></blockquote><pre wrap=""><!---->
Currently we (Pfister and I) are discussing how to merge these two
solution documents. So I believe there will be one solution document
in the end.

</pre><blockquote type="cite"><pre wrap="">In short: I'm still not convinced we have the right problem statement.

</pre></blockquote><pre wrap=""><!---->
Overview document is the one we have now after long discussions.
Of course it could be improved, the plan is to improve it as a WG draft.


</pre><blockquote type="cite"><pre wrap="">regards,
RayH



</pre></blockquote></div>
  <br>
</blockquote>
Both of your comments make sense to me: host portion covered in this WG 
and changing the title.<br>
<br>
What about other considerations then?<br>
<br>
Such as potentially extending ICMP redirects to include source address 
specific applicability?<br>
<br>
I know this has been discussed, but it isn't included in any problem 
statement yet AFAICS.<br>
<br>
regards<br>
RayH<br>
</body></html>

--------------050202080801060904000005
Content-Type: image/jpeg; x-apple-mail-type=stationery;
 name="compose-unknown-contact.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.02070109.08020207@globis.net>
Content-Disposition: inline;
 filename="compose-unknown-contact.jpg"

/9j/4AAQSkZJRgABAQEARwBHAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEC
AQEBAQEBAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/2wBDAQEBAQEBAQICAgICAgIC
AgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/wAAR
CAAZABkDAREAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAABgcICQr/xAA0EAABAwMCAgUK
BwAAAAAAAAACAQMEBQYRABITIQcUMUF2CBUXIjI2N0JRtVRWkZOV0dL/xAAYAQEAAwEAAAAA
AAAAAAAAAAADAAEEAv/EACQRAAICAAQGAwAAAAAAAAAAAAABAhEDMrHREyExM0FxgfDx/9oA
DAMBAAIRAxEAPwDuEt+gW/ULet6oVC3rfqNQqFv0OfPn1GhUqfOmzZtKZlS5UqZMaNwzNwiJ
VIl7eXLCaZIGwBl3TY8epPx2+jy2ZNPjvkwc9uhW8j7nCPhvOsQliYIeS7cvCpp8o50qwrC4
v3lsNSDbdmTEhvs2tahxpfV3WnmbbozJEw/gwdadbYExVRXKEKoSdvJcaOSqxE7/AAiX0gXx
+a69/JSf9alIlste0VzaNpeFrcT9KKymotyiaZ0KRCnzacoE7Kjzn4gi2KqUh3jqDHDHv4mR
UfruTWlMzlVUKIVNp9GguEJnAh0+IZjyAiisgyRDnu5azS8miKqjOTVkKqS/psG37fo1Fbab
eg25b8eZPeFJBBJSjMG5HjMeyihnaauZwe4OGiju13GAcpOwBeN+U8/IkGbsiS8b7ryogmbz
hbyc9REROfZhERO5ETShjPtvpGqTUyLErytS4siSwx5x2tRH4hPOI0DkjZtaJtFxuVEbIUUi
yeNujlBUJGbJN6nM/Cyf2Hf60YgjvKA+NPSP4gT7axpcPtr51YWJnYn9dnAQWl722p4ot37y
zqnlfp6FrqbwawG8/9k=
--------------050202080801060904000005--

--------------080804010609060405050705--


From nobody Fri Apr 10 06:21:51 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5EB1B354E; Fri, 10 Apr 2015 06:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dR32VSit0G0T; Fri, 10 Apr 2015 06:21:45 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0755.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:755]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C3051B3544; Fri, 10 Apr 2015 06:21:45 -0700 (PDT)
Received: from CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) by CO1PR05MB521.namprd05.prod.outlook.com (10.141.72.13) with Microsoft SMTP Server (TLS) id 15.1.130.23; Fri, 10 Apr 2015 13:21:25 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) with Microsoft SMTP Server (TLS) id 15.1.130.23; Fri, 10 Apr 2015 13:21:25 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Fri, 10 Apr 2015 13:21:24 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>,  "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQcwrDp9dxYEBnxUmM6NRkqzG+ep1GOwxA
Date: Fri, 10 Apr 2015 13:21:23 +0000
Message-ID: <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm>
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB444; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB521; 
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(164054003)(51704005)(377454003)(377424004)(13464003)(74316001)(107886001)(19580395003)(19580405001)(46102003)(2656002)(54356999)(50986999)(76176999)(106116001)(2900100001)(86362001)(2950100001)(92566002)(33656002)(230783001)(15975445007)(87936001)(2201001)(99286002)(40100003)(62966003)(66066001)(76576001)(2501003)(1720100001)(122556002)(102836002)(2420400003)(77156002); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB444; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <CO1PR05MB44445A69990E7FB9E5C539CAEFA0@CO1PR05MB444.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CO1PR05MB444; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB444; 
x-forefront-prvs: 054231DC40
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2015 13:21:23.8050 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB444
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zCLvWhfvOpMKyzW7YRDWcaf-KoA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 13:21:48 -0000

Hi Lucy,

MPLS over GRE [RFC 4023] has exactly the same security issues as IPv6 over =
GRE. Fortunately, RFC 4023 has an extensive Security Considerations section=
 that references IPSec. So, the current document references RFC 4023 and ge=
ts IPSec through one layer of indirection.

                                                                           =
           Ron


> -----Original Message-----
> From: Lucy yong [mailto:lucy.yong@huawei.com]
> Sent: Thursday, April 09, 2015 5:15 PM
> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intar=
ea-
> gre-ipv6-05.txt
>=20
> Hi Ron,
>=20
> Security considerations should state that IPsec [RFC4301] can be used to
> provide payload security and privacy over an IP network where the securit=
y is
> a concern.
>=20
> Thanks,
> Lucy
>=20
> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald
> Bonica
> Sent: Thursday, April 09, 2015 4:03 PM
> To: int-area@ietf.org; ipv6@ietf.org
> Subject: [Int-area] FW: New Version Notification for draft-ietf-intarea-g=
re-
> ipv6-05.txt
>=20
> Folks,
>=20
> I have updated draft-ietf-intarea-gre-ipv6. Please tell me if I have addr=
essed
> all of your comments.
>=20
>                                                   Ron
>=20
>=20
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: Thursday, April 09, 2015 4:58 PM
> > To: Ronald Bonica; Suresh Krishnan; Suresh Krishnan; Carlos Pignataro;
> > Ronald Bonica; Carlos Pignataro
> > Subject: New Version Notification for
> > draft-ietf-intarea-gre-ipv6-05.txt
> >
> >
> > A new version of I-D, draft-ietf-intarea-gre-ipv6-05.txt
> > has been successfully submitted by Ron Bonica and posted to the IETF
> > repository.
> >
> > Name:		draft-ietf-intarea-gre-ipv6
> > Revision:	05
> > Title:		IPv6 Support for Generic Routing Encapsulation (GRE)
> > Document date:	2015-04-10
> > Group:		intarea
> > Pages:		8
> > URL:            http://www.ietf.org/internet-drafts/draft-ietf-intarea-=
gre-ipv6-
> > 05.txt
> > Status:         https://datatracker.ietf.org/doc/draft-ietf-intarea-gre=
-ipv6/
> > Htmlized:       http://tools.ietf.org/html/draft-ietf-intarea-gre-ipv6-=
05
> > Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-intarea-g=
re-ipv6-05
> >
> > Abstract:
> >    Generic Routing Encapsulation (GRE) can be used to carry any network=
-
> >    layer payload protocol over any network-layer delivery protocol.  GR=
E
> >    procedures are specified for IPv4, used as either the payload or
> >    delivery protocol.  However, GRE procedures are not specified for
> >    IPv6.
> >
> >    This document specifies GRE procedures for IPv6, used as either the
> >    payload or delivery protocol.  It updates the GRE specification, RFC
> >    2784.
> >
> >
> >
> >
> >
> > 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.i=
etf.org.
> >
> > The IETF Secretariat
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Fri Apr 10 09:37:08 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D801ACDD9 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 09:37:03 -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, SPF_PASS=-0.001] autolearn=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 o8wzzONGIQ49 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 09:37:01 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::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 D19801ACEE3 for <6man@ietf.org>; Fri, 10 Apr 2015 09:37:00 -0700 (PDT)
Received: by lbbqq2 with SMTP id qq2so17697281lbb.3 for <6man@ietf.org>; Fri, 10 Apr 2015 09:36:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ICu6ksUAue12EPpRRk/PEcjI4kH7FCBm96AcJrO1jgw=; b=iz5tKCgsOr5JJgSpl4aIjD2gqikqCY6NkDFF8bQOWutOMuT1++TK9wwkTQ8B+543QO ItITouFBE2XWzNx9xS3dCJHJZDkNeH2YftYHDkMn0RUxzIcmSTC2KaHpANmHn+NqSx2K fu0KvslGPXY4DaTPqLESl2F3suMkP/2gkL2st20NtO/fXvwJ2LJmKNVtoNqbUyjdQUP9 EcR4TkOpm3iCOi55nip0AIJ04W5QHqfWOHoCoKMwFJo2ytjUu+XTkXYORYu8SSMMr+YD rwhs0TaoqbHVx3eWk3C1g1ogBLxZad4EBuPbCsEXFjm3Nyd4yRaIDYxpmPggJcTPOcFn er+w==
MIME-Version: 1.0
X-Received: by 10.152.121.72 with SMTP id li8mr2100230lab.11.1428683819352; Fri, 10 Apr 2015 09:36:59 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Fri, 10 Apr 2015 09:36:59 -0700 (PDT)
In-Reply-To: <5527A84B.8090201@globis.net>
References: <CAC8QAceCoBx8VCgLq5tJ8JUGtVCPP+PXC0gxmhpRpmrp0MXqPw@mail.gmail.com> <55240885.9060200@globis.net> <CAC8QAcddWTb-w_3Q29sq0GpUOcqyOPjDRd1a0Uk3zY0ivzohNg@mail.gmail.com> <5526E648.4020004@gmail.com> <F48F50DA-4257-48E7-B34D-A0543EA3E50D@cisco.com> <5527A84B.8090201@globis.net>
Date: Fri, 10 Apr 2015 11:36:59 -0500
Message-ID: <CAC8QAceRxLOhkZDMrXEu0MJURWm-Jc07J9nAcrPXzNOALHzzeA@mail.gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-06.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ray Hunter <v6ops@globis.net>
Content-Type: multipart/related; boundary=089e01176b3b8ca3250513615f46
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6eW6juQtntxCpOYHMspHK1OxynY>
Cc: Ole Troan <ot@cisco.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:37:04 -0000

--089e01176b3b8ca3250513615f46
Content-Type: multipart/alternative; boundary=089e01176b3b8ca31f0513615f45

--089e01176b3b8ca31f0513615f45
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ray, all,

On Fri, Apr 10, 2015 at 5:39 AM, Ray Hunter <v6ops@globis.net> wrote:

>
>
>   Ole Troan <ot@cisco.com>
>  10 April 2015 08:15
>
> fully agree. SADR might not be the best name for the host portion.
> perhaps something like "IPv6 Multi-homed host gaps=E2=80=9D?
>
> Isn't this limiting the host gaps, possibly the future ones to source
address selection?
Otherwise I am OK.


> Ole
>   Brian E Carpenter <brian.e.carpenter@gmail.com>
>  9 April 2015 22:51
>
> On 08/04/2015 05:02, Behcet Sarikaya wrote:
>
> Hi Ray,
>
> On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <v6ops@globis.net> <v6ops@glo=
bis.net> wrote:
>
> ...
>
> But I'd expect any "SADR overview" to also cover router - router forwardi=
ng
> behaviour. Not just end host - router.
>
> Can you offer some text?
>
>
> At the moment that's covered by draft-baker-rtgwg-src-dst-routing-use-cas=
es.
> IMHO the separation into host and router drafts is reasonable, so that
> each draft fits mainly into a single WG.
>
>
I agree.

snipped some text here.

> This should be
> draft-sarikaya-6man-sadr-ra
>
>  we do not plan on pursuing draft-sarikaya-6man-next-hop-ra-04 any
> further because of the third part next hop issue.
>
>  or
>
> https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00 ?
>
> In my mind, https://tools.ietf.org/html/draft-pfister-6man-sadr-ra-00  is=
 a
> logical progression from https://tools.ietf.org/html/rfc4191
>
> The other approach is to define a new option as in
> draft-sarikaya-6man-sadr-ra then we don't need an I flag.
>
> Snipped some text.

> Currently we (Pfister and I) are discussing how to merge these two
> solution documents. So I believe there will be one solution document
> in the end.
>
>
We need more feedback on the above choices for solution approaches.


>
>  Both of your comments make sense to me: host portion covered in this WG
> and changing the title.
>
> What about other considerations then?
>
> Such as potentially extending ICMP redirects to include source address
> specific applicability?
>
> I know this has been discussed, but it isn't included in any problem
> statement yet AFAICS.
>
> regards
> RayH
>
Regards,

Behcet

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

<div dir=3D"ltr">Hi Ray, all,<div class=3D"gmail_extra"><br></div><div clas=
s=3D"gmail_quote">On Fri, Apr 10, 2015 at 5:39 AM, Ray Hunter <span dir=3D"=
ltr">&lt;<a href=3D"mailto:v6ops@globis.net" target=3D"_blank">v6ops@globis=
.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);=
border-left-width:1px;border-left-style:solid">

<div text=3D"#000000" bgcolor=3D"#FFFFFF"><br>
<br>
<blockquote style=3D"border:0px currentColor" type=3D"cite">
  <div style=3D"margin:30px 25px 10px"><div style=3D"width:100%;padding-top=
:5px;border-top-color:rgb(237,238,240);border-top-width:1px;border-top-styl=
e:solid;display:table"> 	<div style=3D"padding-right:6px;vertical-align:mid=
dle;display:table-cell"><img name=3D"14ca2e981cdb8817_compose-unknown-conta=
ct.jpg" width=3D"25" height=3D"25" src=3D"cid:part1.02070109.08020207@globi=
s.net"></div>   <div style=3D"width:100%;vertical-align:middle;display:tabl=
e-cell;white-space:nowrap">
   	<a style=3D"color:rgb(115,127,146)!important;padding-right:6px;font-wei=
ght:bold;text-decoration:none!important" href=3D"mailto:ot@cisco.com" targe=
t=3D"_blank">Ole Troan</a></div>   <div style=3D"vertical-align:middle;disp=
lay:table-cell;white-space:nowrap">  =20
  <font color=3D"#9fa2a5"><span style=3D"padding-left:6px">10 April 2015=20
08:15</span></font></div></div></div><span>
  <div style=3D"color:rgb(136,136,136);margin-right:24px;margin-left:24px">=
<div><br>fully agree.=20
SADR might not be the best name for the host portion.<br>perhaps=20
something like &quot;IPv6 Multi-homed host gaps=E2=80=9D?<br><br></div></di=
v></span></blockquote></div></blockquote><div>Isn&#39;t this limiting the h=
ost gaps, possibly the=C2=A0future ones to source address=C2=A0selection?</=
div><div>Otherwise I am OK.</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-col=
or:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div tex=
t=3D"#000000" bgcolor=3D"#FFFFFF"><blockquote style=3D"border:0px currentCo=
lor" type=3D"cite"><span><div style=3D"color:rgb(136,136,136);margin-right:=
24px;margin-left:24px"><div>Ole<br></div></div>
  </span><div style=3D"margin:30px 25px 10px"><div style=3D"width:100%;padd=
ing-top:5px;border-top-color:rgb(237,238,240);border-top-width:1px;border-t=
op-style:solid;display:table"> 	<div style=3D"padding-right:6px;vertical-al=
ign:middle;display:table-cell"><img name=3D"14ca2e981cdb8817_compose-unknow=
n-contact.jpg" width=3D"25" height=3D"25" src=3D"cid:part1.02070109.0802020=
7@globis.net"></div>   <div style=3D"width:100%;vertical-align:middle;displ=
ay:table-cell;white-space:nowrap">
   	<a style=3D"color:rgb(115,127,146)!important;padding-right:6px;font-wei=
ght:bold;text-decoration:none!important" href=3D"mailto:brian.e.carpenter@g=
mail.com" target=3D"_blank">Brian E Carpenter</a></div>   <div style=3D"ver=
tical-align:middle;display:table-cell;white-space:nowrap">  =20
  <font color=3D"#9fa2a5"><span style=3D"padding-left:6px">9 April 2015=20
22:51</span></font></div></div></div>
  <div style=3D"color:rgb(136,136,136);margin-right:24px;margin-left:24px">=
<span><pre>On 08/04/2015 05:02, Behcet Sarikaya wrote:
</pre><blockquote type=3D"cite"><pre>Hi Ray,

On Tue, Apr 7, 2015 at 11:40 AM, Ray Hunter <a href=3D"mailto:v6ops@globis.=
net" target=3D"_blank">&lt;v6ops@globis.net&gt;</a> wrote:
</pre></blockquote></span><span><pre>...
</pre><blockquote type=3D"cite"><blockquote type=3D"cite"><pre>But I&#39;d =
expect any &quot;SADR overview&quot; to also cover router - router forwardi=
ng
behaviour. Not just end host - router.
</pre></blockquote><pre>Can you offer some text?
</pre></blockquote></span><pre><span>
At the moment that&#39;s covered by draft-baker-rtgwg-src-dst-</span>routin=
g-use-cases.
IMHO the separation into host and router drafts is reasonable, so that
each draft fits mainly into a single WG.
</pre></div></blockquote></div></blockquote><div>=C2=A0</div><div>I agree.<=
/div><div>=C2=A0</div><span><div>snipped some text here. </div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;bo=
rder-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:so=
lid"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><blockquote style=3D"border:=
0px currentColor" type=3D"cite"><div style=3D"color:rgb(136,136,136);margin=
-right:24px;margin-left:24px"><pre>This should be
draft-sarikaya-6man-sadr-ra

 we do not plan on pursuing draft-sarikaya-6man-next-hop-ra-04 any
further because of the third part next hop issue.

 or
</pre><blockquote type=3D"cite"><pre><a href=3D"https://tools.ietf.org/html=
/draft-pfister-6man-sadr-ra-00" target=3D"_blank">https://tools.ietf.org/ht=
ml/draft-pfister-6man-sadr-ra-00</a> ?

In my mind, <a href=3D"https://tools.ietf.org/html/draft-pfister-6man-sadr-=
ra-00" target=3D"_blank">https://tools.ietf.org/html/draft-pfister-6man-sad=
r-ra-00</a>  is a
logical progression from <a href=3D"https://tools.ietf.org/html/rfc4191" ta=
rget=3D"_blank">https://tools.ietf.org/html/rfc4191</a>
</pre></blockquote><pre>The other approach is to define a new option as in
draft-sarikaya-6man-sadr-ra then we don&#39;t need an I flag.</pre></div></=
blockquote></div></blockquote><div>Snipped some text.</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border=
-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"=
><div text=3D"#000000" bgcolor=3D"#FFFFFF"><blockquote style=3D"border:0px =
currentColor" type=3D"cite"><div style=3D"color:rgb(136,136,136);margin-rig=
ht:24px;margin-left:24px"><pre>Currently we (Pfister and I) are discussing =
how to merge these two
solution documents. So I believe there will be one solution document
in the end.
</pre></div></blockquote></div></blockquote><div>=C2=A0</div><div>We need m=
ore feedback on the above choices for solution approaches.</div><div>=C2=A0=
</div></span><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width=
:1px;border-left-style:solid"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><bl=
ockquote style=3D"border:0px currentColor" type=3D"cite"><div style=3D"colo=
r:rgb(136,136,136);margin-right:24px;margin-left:24px"></div>
  <br>
</blockquote>
Both of your comments make sense to me: host portion covered in this WG=20
and changing the title.<br>
<br>
What about other considerations then?<br>
<br>
Such as potentially extending ICMP redirects to include source address=20
specific applicability?<br>
<br>
I know this has been discussed, but it isn&#39;t included in any problem=20
statement yet AFAICS.<br>
<br>
regards<br>
RayH<br>
</div>
</blockquote></div><div class=3D"gmail_extra">Regards,</div><div class=3D"g=
mail_extra">=C2=A0</div><div class=3D"gmail_extra">Behcet<br></div></div>

--089e01176b3b8ca31f0513615f45--
--089e01176b3b8ca3250513615f46
Content-Type: image/jpeg; x-apple-mail-type=stationery; name="compose-unknown-contact.jpg"
Content-Disposition: inline; filename="compose-unknown-contact.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.02070109.08020207@globis.net>
X-Attachment-Id: 7a182a8fc661b75d_0.1.1

/9j/4AAQSkZJRgABAQEARwBHAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQECAQEB
AQEBAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/2wBDAQEBAQEBAQICAgICAgICAgICAgIC
AgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/wAARCAAZABkDAREA
AhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAABgcICQr/xAA0EAABAwMCAgUKBwAAAAAAAAACAQME
BQYRABITIQcUMUF2CBUXIjI2N0JRtVRWkZOV0dL/xAAYAQEAAwEAAAAAAAAAAAAAAAADAAEEAv/E
ACQRAAICAAQGAwAAAAAAAAAAAAABAhEDMrHREyExM0FxgfDx/9oADAMBAAIRAxEAPwDuEt+gW/UL
et6oVC3rfqNQqFv0OfPn1GhUqfOmzZtKZlS5UqZMaNwzNwiJVIl7eXLCaZIGwBl3TY8epPx2+jy2
ZNPjvkwc9uhW8j7nCPhvOsQliYIeS7cvCpp8o50qwrC4v3lsNSDbdmTEhvs2tahxpfV3WnmbbozJ
Ew/gwdadbYExVRXKEKoSdvJcaOSqxE7/AAiX0gXx+a69/JSf9alIlste0VzaNpeFrcT9KKymotyi
aZ0KRCnzacoE7Kjzn4gi2KqUh3jqDHDHv4mRUfruTWlMzlVUKIVNp9GguEJnAh0+IZjyAiisgyRD
nu5azS8miKqjOTVkKqS/psG37fo1Fbabeg25b8eZPeFJBBJSjMG5HjMeyihnaauZwe4OGiju13GA
cpOwBeN+U8/IkGbsiS8b7ryogmbzhbyc9REROfZhERO5ETShjPtvpGqTUyLErytS4siSwx5x2tRH
4hPOI0DkjZtaJtFxuVEbIUUiyeNujlBUJGbJN6nM/Cyf2Hf60YgjvKA+NPSP4gT7axpcPtr51YWJ
nYn9dnAQWl722p4ot37yzqnlfp6FrqbwawG8/9k=
--089e01176b3b8ca3250513615f46--


From nobody Fri Apr 10 09:57:28 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BAD1AD36F for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 09:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 Pad2pIhhLCZF for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 09:57:25 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001: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 772DA1A1EF6 for <ipv6@ietf.org>; Fri, 10 Apr 2015 09:57:25 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so2812483igb.0 for <ipv6@ietf.org>; Fri, 10 Apr 2015 09:57:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fgc0nvJIP8gAW5/b2OZL2Y2ttX5KgSPAC3zKMlzieEw=; b=a57355LS4bdt0M0c+8+JBrLupoXGS8WXNMaXrit7xahUfdMgEVBfvYM3XkUAAlVQ54 IP+hZ8bRMM6Mrcpflhjs3ZBjfd1F7gKMxMmgeIBczp1ReAC0Q+/mf09cxoEO0YKEZqz0 GxESE7k3G9HQLE03KjxSTXvV4aKBSl6+c9KYb7xaYWwfRYaW2+dp887Z1lua1Dt+6p2f st9s+ZO49cU8ZfJZi9DUJPxfXUOka1ukwjpIl25NCsK+Rs65YrcOLigmBjd8F0Fb4Peu IGD13Ebae977lsTHJyd5NELrM2GfVRriBnHBhv0nxbWNp0+vXL/lvi2gbfyTX7d24d54 k1dw==
MIME-Version: 1.0
X-Received: by 10.50.254.99 with SMTP id ah3mr29991012igd.12.1428685044944; Fri, 10 Apr 2015 09:57:24 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Fri, 10 Apr 2015 09:57:24 -0700 (PDT)
In-Reply-To: <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com>
Date: Fri, 10 Apr 2015 09:57:24 -0700
X-Google-Sender-Auth: ub8ytPtP3XAWoWujdcGAhj3-Pg0
Message-ID: <CAJE_bqdh8aUzmF7UkBgicMNAM_YHBLQ5DYyuimbu9EY=d6T0Sg@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/k8gNogIbqaD35XzIvV9Pja3cVo4>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:57:27 -0000

At Wed, 8 Apr 2015 12:19:30 -0700,
Bob Hinden <bob.hinden@gmail.com> wrote:

> > This message starts a two week 6MAN Working Group Last Call on adopting:
> >        Filename        : draft-nordmark-6man-rs-refresh-01.txt
> >        https://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01
> >
> > as a working group document. Substantive comments and statements
> > of support for adopting this document should be directed to the
> > mailing list.  Editorial suggestions can be sent to the authors.
> > This adoption call will end on April 10, 2015.

I think it's worth discussing so I support the adoption.  But I have
one higher level question: did we agree that we need some enhancements
to ND to address the concern of multicast overhead?  It's quite
possible that I missed something in previous discussions, but I
thought there was not a clear consensus for the need for protocol
level changes while we generally saw potential issues in this area.

On the draft itself, I have a few minor comments:

- Section 5:
   Refresh Time:  16-bit unsigned integer.  Units is seconds.  The all-
                  ones value (65535) means infinite.

What should the host do if this is 0?  Should it just keep sending
RSes? (I'm joking).

- Section 7: remove 'section'.
   [...]  Note that section
   Section 9 says that routers SHOULD report such inconsistencies to
   system management.

- Section 8.2: s/be be/may be/ (?)

   [...]  That be be performed at deployment time (e.g., only
   hosts which are known to support RTO are configured with the layer 2
   security keys), or the routers detect any RSs which do not include

- Section 8.3: remove '.' before 'Note':

   .  Note that such new information is not likely to reach sleeping
   hosts until those hosts refresh by sending a RS.

--
JINMEI, Tatuya


From nobody Fri Apr 10 11:52:21 2015
Return-Path: <farmer@umn.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFBD31A0125 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 11:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXuUa9MESkrL for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 11:52:18 -0700 (PDT)
Received: from vs-a.tc.umn.edu (vs-a.tc.umn.edu [134.84.119.220]) by ietfa.amsl.com (Postfix) with ESMTP id DB7611A0040 for <ipv6@ietf.org>; Fri, 10 Apr 2015 11:52:17 -0700 (PDT)
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by vs-a.tc.umn.edu (UMN smtpd) with ESMTP for <ipv6@ietf.org>; Fri, 10 Apr 2015 13:52:16 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f182.google.com [209.85.223.182] #+LO+TS+TR
X-Umn-Classification: local
Received: by iejt8 with SMTP id t8so24647044iej.2 for <ipv6@ietf.org>; Fri, 10 Apr 2015 11:52:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bgSHpm+ELmZx6veZn2pPcB5MBEwzxYSGWcl3G/lSo4A=; b=NzHtxArdAP2iP5HIbC/PKjPG2dkuHJwdWDQna9ttosa+mnK7KtjT74WFcq1ovQnu5N qHwa1MEujTXhfunsh7C5MC3bPph2EnDzQ5RUeoHznlDvCvmhQAOG6KX78BFz7tMQ6WBs 5YHahW3He+X104fAFa5lAJ3/2Twh8BGreuz4Y=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=bgSHpm+ELmZx6veZn2pPcB5MBEwzxYSGWcl3G/lSo4A=; b=fyUCZB6NZgGyGGav+S3Kna8mW6Jv4i0+Qmnb+o8B1jWMYGEwbCFyB9g3l31ukCRbaN iL7mTfNVXiIYYHzi3X/BfNhs9depeGtE/JjkwyNmPGmrD2lReN7XpJblcVQiKJU5qGhG d4Rdo7EF8giA7ThysDbigZakprPb13ahU5YW2knIeOq2iVedh7w47A4bYALAQlr2Lq+8 jtOhpdYPQkW2MBgc9DP9sTi3vlt10M9bAXSIBNhbA6Kx3TEONkZGZ8DjAcu3F9SLiiF+ uXLYtgP/Sfg9sypPBm7oztbss8hh3kaMMOlXlWeKQHhvQf87WfuTkg2Pno586dcwpiP7 5m8w==
X-Gm-Message-State: ALoCoQlYKQ41iTt8lRtihgcYTrZRQoJr0bhmFFO/EErMh47DAlzNJvxd4i5EnFFNtiJqof91rUxSjFrM0mUw29ezy+DYM66GrKUZAZS0fASV2frg0m5qHJLM3AZWr4M5HSf4M2APekd3
X-Received: by 10.51.17.40 with SMTP id gb8mr375005igd.44.1428691936091; Fri, 10 Apr 2015 11:52:16 -0700 (PDT)
X-Received: by 10.51.17.40 with SMTP id gb8mr374971igd.44.1428691935761; Fri, 10 Apr 2015 11:52:15 -0700 (PDT)
Received: from x-160-94-246-22.uofm-secure.wireless.umn.edu ([2607:ea00:104:2000:8460:f194:7c3a:cdb1]) by mx.google.com with ESMTPSA id i80sm1623925iod.6.2015.04.10.11.52.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Apr 2015 11:52:14 -0700 (PDT)
Message-ID: <55281BDB.1040804@umn.edu>
Date: Fri, 10 Apr 2015 13:52:11 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5n5YIiMwY0YMy1EhOQGsrmC-b88>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 18:52:20 -0000

I agree with Lucy, I'd like to see a direct reference to IPsec. How 
about something like what Lucy had and then reference RFC 4023 for a 
more extensive discussion.

    IPsec [RFC4301] can be used to provide payload security and privacy
    over an IP network where security is a concern, the Security
    Considerations section of MPLS in GRE [RFC4023] discusses this more
    extensively and applies equally to the current specification.  Beyond
    that, the current specification introduces no security
    considerations beyond those mentioned in RFC 2784.

I'd like to see general security references for IPv6 and tunnels 
included as well, maybe something like the following as a second paragraph.

   More generically, security considerations for IPv6 are discussed in
   [RFC4942], operational security for IPv6 is discussed in
   [I-D.ietf-opsec-v6], and security concerns for tunnels in general are
   discussed in [RFC6169].

Thanks

On 4/10/15 08:21 , Ronald Bonica wrote:
> Hi Lucy,
>
> MPLS over GRE [RFC 4023] has exactly the same security issues as IPv6 over GRE. Fortunately, RFC 4023 has an extensive Security Considerations section that references IPSec. So, the current document references RFC 4023 and gets IPSec through one layer of indirection.
>
>                                                                                        Ron
>
>
>> -----Original Message-----
>> From: Lucy yong [mailto:lucy.yong@huawei.com]
>> Sent: Thursday, April 09, 2015 5:15 PM
>> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
>> Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-
>> gre-ipv6-05.txt
>>
>> Hi Ron,
>>
>> Security considerations should state that IPsec [RFC4301] can be used to
>> provide payload security and privacy over an IP network where the security is
>> a concern.
>>
>> Thanks,
>> Lucy
>>
>> -----Original Message-----
>> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald
>> Bonica
>> Sent: Thursday, April 09, 2015 4:03 PM
>> To: int-area@ietf.org; ipv6@ietf.org
>> Subject: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-
>> ipv6-05.txt
>>
>> Folks,
>>
>> I have updated draft-ietf-intarea-gre-ipv6. Please tell me if I have addressed
>> all of your comments.
>>
>>                                                    Ron
>>
>>
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Thursday, April 09, 2015 4:58 PM
>>> To: Ronald Bonica; Suresh Krishnan; Suresh Krishnan; Carlos Pignataro;
>>> Ronald Bonica; Carlos Pignataro
>>> Subject: New Version Notification for
>>> draft-ietf-intarea-gre-ipv6-05.txt
>>>
>>>
>>> A new version of I-D, draft-ietf-intarea-gre-ipv6-05.txt
>>> has been successfully submitted by Ron Bonica and posted to the IETF
>>> repository.
>>>
>>> Name:		draft-ietf-intarea-gre-ipv6
>>> Revision:	05
>>> Title:		IPv6 Support for Generic Routing Encapsulation (GRE)
>>> Document date:	2015-04-10
>>> Group:		intarea
>>> Pages:		8
>>> URL:            http://www.ietf.org/internet-drafts/draft-ietf-intarea-gre-ipv6-
>>> 05.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-intarea-gre-ipv6/
>>> Htmlized:       http://tools.ietf.org/html/draft-ietf-intarea-gre-ipv6-05
>>> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-gre-ipv6-05
>>>
>>> Abstract:
>>>     Generic Routing Encapsulation (GRE) can be used to carry any network-
>>>     layer payload protocol over any network-layer delivery protocol.  GRE
>>>     procedures are specified for IPv4, used as either the payload or
>>>     delivery protocol.  However, GRE procedures are not specified for
>>>     IPv6.
>>>
>>>     This document specifies GRE procedures for IPv6, used as either the
>>>     payload or delivery protocol.  It updates the GRE specification, RFC
>>>     2784.
>>>
>>>
>>>
>>>
>>>
>>> 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
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Fri Apr 10 14:56:36 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577291B2D72; Fri, 10 Apr 2015 14:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qaPqu9o0MjG6; Fri, 10 Apr 2015 14:56:32 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0742.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::742]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9A551B2D6C; Fri, 10 Apr 2015 14:56:31 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.1.130.23; Fri, 10 Apr 2015 21:56:12 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Fri, 10 Apr 2015 21:56:11 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: David Farmer <farmer@umn.edu>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQc795MeXvxGLYck68SuOpfDNlq51Gyn2A
Date: Fri, 10 Apr 2015 21:56:11 +0000
Message-ID: <CO1PR05MB4423075D15159BCD8D08028AEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55281BDB.1040804@umn.edu>
In-Reply-To: <55281BDB.1040804@umn.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.13]
authentication-results: umn.edu; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB441;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(51704005)(13464003)(24454002)(479174004)(377424004)(164054003)(252514010)(40100003)(2420400003)(99286002)(1720100001)(50986999)(230783001)(92566002)(2201001)(54356999)(15975445007)(102836002)(122556002)(2900100001)(74316001)(77156002)(62966003)(46102003)(2501003)(33656002)(86362001)(93886004)(76176999)(19580405001)(19580395003)(66066001)(2656002)(2171001)(2950100001)(106116001)(87936001)(107886001)(76576001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <CO1PR05MB4412BA2D4C08853DC7D2BE2AEFA0@CO1PR05MB441.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CO1PR05MB441; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB441; 
x-forefront-prvs: 054231DC40
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2015 21:56:11.4205 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB441
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/p8KrNTMQ_ZW9sjQqbDcCWZstBUs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 21:56:34 -0000

David,

Works for me. I will spin a new version that includes this text.

                                                    Ron


> -----Original Message-----
> From: David Farmer [mailto:farmer@umn.edu]
> Sent: Friday, April 10, 2015 2:52 PM
> To: Ronald Bonica; Lucy yong; int-area@ietf.org; ipv6@ietf.org
> Cc: David Farmer
> Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intar=
ea-
> gre-ipv6-05.txt
>=20
> I agree with Lucy, I'd like to see a direct reference to IPsec. How about
> something like what Lucy had and then reference RFC 4023 for a more
> extensive discussion.
>=20
>     IPsec [RFC4301] can be used to provide payload security and privacy
>     over an IP network where security is a concern, the Security
>     Considerations section of MPLS in GRE [RFC4023] discusses this more
>     extensively and applies equally to the current specification.  Beyond
>     that, the current specification introduces no security
>     considerations beyond those mentioned in RFC 2784.
>=20
> I'd like to see general security references for IPv6 and tunnels included=
 as
> well, maybe something like the following as a second paragraph.
>=20
>    More generically, security considerations for IPv6 are discussed in
>    [RFC4942], operational security for IPv6 is discussed in
>    [I-D.ietf-opsec-v6], and security concerns for tunnels in general are
>    discussed in [RFC6169].
>=20
> Thanks
>=20
> On 4/10/15 08:21 , Ronald Bonica wrote:
> > Hi Lucy,
> >
> > MPLS over GRE [RFC 4023] has exactly the same security issues as IPv6 o=
ver
> GRE. Fortunately, RFC 4023 has an extensive Security Considerations secti=
on
> that references IPSec. So, the current document references RFC 4023 and
> gets IPSec through one layer of indirection.
> >
> >
> > Ron
> >
> >
> >> -----Original Message-----
> >> From: Lucy yong [mailto:lucy.yong@huawei.com]
> >> Sent: Thursday, April 09, 2015 5:15 PM
> >> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> >> Subject: RE: [Int-area] FW: New Version Notification for
> >> draft-ietf-intarea- gre-ipv6-05.txt
> >>
> >> Hi Ron,
> >>
> >> Security considerations should state that IPsec [RFC4301] can be used
> >> to provide payload security and privacy over an IP network where the
> >> security is a concern.
> >>
> >> Thanks,
> >> Lucy
> >>
> >> -----Original Message-----
> >> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald
> >> Bonica
> >> Sent: Thursday, April 09, 2015 4:03 PM
> >> To: int-area@ietf.org; ipv6@ietf.org
> >> Subject: [Int-area] FW: New Version Notification for
> >> draft-ietf-intarea-gre- ipv6-05.txt
> >>
> >> Folks,
> >>
> >> I have updated draft-ietf-intarea-gre-ipv6. Please tell me if I have
> >> addressed all of your comments.
> >>
> >>                                                    Ron
> >>
> >>
> >>> -----Original Message-----
> >>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >>> Sent: Thursday, April 09, 2015 4:58 PM
> >>> To: Ronald Bonica; Suresh Krishnan; Suresh Krishnan; Carlos
> >>> Pignataro; Ronald Bonica; Carlos Pignataro
> >>> Subject: New Version Notification for
> >>> draft-ietf-intarea-gre-ipv6-05.txt
> >>>
> >>>
> >>> A new version of I-D, draft-ietf-intarea-gre-ipv6-05.txt
> >>> has been successfully submitted by Ron Bonica and posted to the IETF
> >>> repository.
> >>>
> >>> Name:		draft-ietf-intarea-gre-ipv6
> >>> Revision:	05
> >>> Title:		IPv6 Support for Generic Routing Encapsulation (GRE)
> >>> Document date:	2015-04-10
> >>> Group:		intarea
> >>> Pages:		8
> >>> URL:            http://www.ietf.org/internet-drafts/draft-ietf-intare=
a-gre-
> ipv6-
> >>> 05.txt
> >>> Status:         https://datatracker.ietf.org/doc/draft-ietf-intarea-g=
re-ipv6/
> >>> Htmlized:       http://tools.ietf.org/html/draft-ietf-intarea-gre-ipv=
6-05
> >>> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-intarea=
-gre-ipv6-05
> >>>
> >>> Abstract:
> >>>     Generic Routing Encapsulation (GRE) can be used to carry any
> network-
> >>>     layer payload protocol over any network-layer delivery protocol. =
 GRE
> >>>     procedures are specified for IPv4, used as either the payload or
> >>>     delivery protocol.  However, GRE procedures are not specified for
> >>>     IPv6.
> >>>
> >>>     This document specifies GRE procedures for IPv6, used as either t=
he
> >>>     payload or delivery protocol.  It updates the GRE specification, =
RFC
> >>>     2784.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 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
> >>
> >> _______________________________________________
> >> Int-area mailing list
> >> Int-area@ietf.org
> >> https://www.ietf.org/mailman/listinfo/int-area
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>=20
>=20
> --
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> David Farmer               Email: farmer@umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE     Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From nobody Fri Apr 10 15:24:43 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E92E1B2DCB; Fri, 10 Apr 2015 15:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-Nn-bgSdFKv; Fri, 10 Apr 2015 15:24:40 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0124.outbound.protection.outlook.com [65.55.169.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99C2E1B2DC9; Fri, 10 Apr 2015 15:24:39 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.1.130.23; Fri, 10 Apr 2015 22:24:37 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Fri, 10 Apr 2015 22:24:37 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: David Farmer <farmer@umn.edu>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQc795MeXvxGLYck68SuOpfDNlq51G0K1w
Date: Fri, 10 Apr 2015 22:24:36 +0000
Message-ID: <CO1PR05MB4426AB890F76C434BBF03DEAEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55281BDB.1040804@umn.edu>
In-Reply-To: <55281BDB.1040804@umn.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.13]
authentication-results: umn.edu; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB442;
x-microsoft-antispam-prvs: <CO1PR05MB442E5C1E73F526B0D9791F0AEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(24454002)(377424004)(479174004)(164054003)(377454003)(252514010)(13464003)(51704005)(77156002)(106116001)(74316001)(2656002)(230783001)(66066001)(102836002)(15975445007)(33656002)(1720100001)(54356999)(122556002)(2201001)(76176999)(2420400003)(99286002)(40100003)(19580395003)(92566002)(19580405001)(2950100001)(93886004)(2900100001)(46102003)(86362001)(2171001)(76576001)(107886001)(62966003)(50986999)(87936001)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CO1PR05MB442; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB442; 
x-forefront-prvs: 054231DC40
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2015 22:24:36.9070 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB442
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xLGZzttq2KBGRPPigs13lu0YQ-M>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 22:24:42 -0000

David, Lucy,

Having thought about it a little more, would you mind if I crafted the text=
 as follows:

The security section of [RFC 4023] identifies threats encountered when MPLS=
 is deliver over GRE. These threats apply equally to any GRE payload that i=
s delivered over GRE. As stated in RFC 4023, these threats can be mitigated=
 by authenticating and/or encrypting the delivery packet using IPSec [RFC 4=
301] procedures. When the payload is IPv6, they can also be mitigated by au=
thenticating and/or encrypting the payload using IPSec. Beyond that, the cu=
rrent specification introduces no security considerations beyond those ment=
ioned in RFC 2784.

More generically, security considerations for IPv6 are discussed in  [RFC49=
42], operational security for IPv6 is discussed in [I-D.ietf-opsec-v6], and=
 security concerns for tunnels in general are  discussed in [RFC6169].


                                                                          R=
on


> -----Original Message-----
> From: David Farmer [mailto:farmer@umn.edu]
> Sent: Friday, April 10, 2015 2:52 PM
> To: Ronald Bonica; Lucy yong; int-area@ietf.org; ipv6@ietf.org
> Cc: David Farmer
> Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intar=
ea-
> gre-ipv6-05.txt
>=20
> I agree with Lucy, I'd like to see a direct reference to IPsec. How about
> something like what Lucy had and then reference RFC 4023 for a more
> extensive discussion.
>=20
>     IPsec [RFC4301] can be used to provide payload security and privacy
>     over an IP network where security is a concern, the Security
>     Considerations section of MPLS in GRE [RFC4023] discusses this more
>     extensively and applies equally to the current specification.  Beyond
>     that, the current specification introduces no security
>     considerations beyond those mentioned in RFC 2784.
>=20
> I'd like to see general security references for IPv6 and tunnels included=
 as
> well, maybe something like the following as a second paragraph.
>=20
>    More generically, security considerations for IPv6 are discussed in
>    [RFC4942], operational security for IPv6 is discussed in
>    [I-D.ietf-opsec-v6], and security concerns for tunnels in general are
>    discussed in [RFC6169].
>=20
> Thanks
>=20
> On 4/10/15 08:21 , Ronald Bonica wrote:
> > Hi Lucy,
> >
> > MPLS over GRE [RFC 4023] has exactly the same security issues as IPv6 o=
ver
> GRE. Fortunately, RFC 4023 has an extensive Security Considerations secti=
on
> that references IPSec. So, the current document references RFC 4023 and
> gets IPSec through one layer of indirection.
> >
> >
> > Ron
> >
> >
> >> -----Original Message-----
> >> From: Lucy yong [mailto:lucy.yong@huawei.com]
> >> Sent: Thursday, April 09, 2015 5:15 PM
> >> To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
> >> Subject: RE: [Int-area] FW: New Version Notification for
> >> draft-ietf-intarea- gre-ipv6-05.txt
> >>
> >> Hi Ron,
> >>
> >> Security considerations should state that IPsec [RFC4301] can be used
> >> to provide payload security and privacy over an IP network where the
> >> security is a concern.
> >>
> >> Thanks,
> >> Lucy
> >>
> >> -----Original Message-----
> >> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald
> >> Bonica
> >> Sent: Thursday, April 09, 2015 4:03 PM
> >> To: int-area@ietf.org; ipv6@ietf.org
> >> Subject: [Int-area] FW: New Version Notification for
> >> draft-ietf-intarea-gre- ipv6-05.txt
> >>
> >> Folks,
> >>
> >> I have updated draft-ietf-intarea-gre-ipv6. Please tell me if I have
> >> addressed all of your comments.
> >>
> >>                                                    Ron
> >>
> >>
> >>> -----Original Message-----
> >>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >>> Sent: Thursday, April 09, 2015 4:58 PM
> >>> To: Ronald Bonica; Suresh Krishnan; Suresh Krishnan; Carlos
> >>> Pignataro; Ronald Bonica; Carlos Pignataro
> >>> Subject: New Version Notification for
> >>> draft-ietf-intarea-gre-ipv6-05.txt
> >>>
> >>>
> >>> A new version of I-D, draft-ietf-intarea-gre-ipv6-05.txt
> >>> has been successfully submitted by Ron Bonica and posted to the IETF
> >>> repository.
> >>>
> >>> Name:		draft-ietf-intarea-gre-ipv6
> >>> Revision:	05
> >>> Title:		IPv6 Support for Generic Routing Encapsulation (GRE)
> >>> Document date:	2015-04-10
> >>> Group:		intarea
> >>> Pages:		8
> >>> URL:            http://www.ietf.org/internet-drafts/draft-ietf-intare=
a-gre-
> ipv6-
> >>> 05.txt
> >>> Status:         https://datatracker.ietf.org/doc/draft-ietf-intarea-g=
re-ipv6/
> >>> Htmlized:       http://tools.ietf.org/html/draft-ietf-intarea-gre-ipv=
6-05
> >>> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-intarea=
-gre-ipv6-05
> >>>
> >>> Abstract:
> >>>     Generic Routing Encapsulation (GRE) can be used to carry any
> network-
> >>>     layer payload protocol over any network-layer delivery protocol. =
 GRE
> >>>     procedures are specified for IPv4, used as either the payload or
> >>>     delivery protocol.  However, GRE procedures are not specified for
> >>>     IPv6.
> >>>
> >>>     This document specifies GRE procedures for IPv6, used as either t=
he
> >>>     payload or delivery protocol.  It updates the GRE specification, =
RFC
> >>>     2784.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 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
> >>
> >> _______________________________________________
> >> Int-area mailing list
> >> Int-area@ietf.org
> >> https://www.ietf.org/mailman/listinfo/int-area
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>=20
>=20
> --
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> David Farmer               Email: farmer@umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE     Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From nobody Fri Apr 10 16:26:07 2015
Return-Path: <farmer@umn.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 164AE1B2E69 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 16:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DYqIMbQtLmfX for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 16:25:59 -0700 (PDT)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.119.20]) by ietfa.amsl.com (Postfix) with ESMTP id BB7981B2E67 for <ipv6@ietf.org>; Fri, 10 Apr 2015 16:25:59 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <ipv6@ietf.org>; Fri, 10 Apr 2015 18:25:58 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f172.google.com [209.85.223.172] #+LO+TS+TR
X-Umn-Classification: local
Received: by iedfl3 with SMTP id fl3so32939490ied.1 for <ipv6@ietf.org>; Fri, 10 Apr 2015 16:25:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zR5V31NRz43XEZd1gcZQy6ICucXka2HAyY7d73/Mw9E=; b=UMz6JMVhnS55pHGwiYXqpA5oEvWBLIeMx2MGkpw34ufkNzJLaroqmEe1q92LKbhcnj jwXUVSTCuvlzUp35UlCeUq77LF5+2DqOQ+zibSp6NnNIaol694SnmTZ6MRAkk7OlVtGa Rh5eBsnq5n60qa7P+vDisqifB+zfKenPcbqYc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=zR5V31NRz43XEZd1gcZQy6ICucXka2HAyY7d73/Mw9E=; b=YHvxB2P6YzCIFA1H1SDfLrnKZ7HY92mzlwNX/DolrKivshuCWFNZ59mPE9BdEHyP1Q yjJA6hTKYeWkAUEyj89JPL3R1O6oE7LM86KOpBOXnnYcxzCWN2td9q0hxF+8s2YwdiXE Piu5GbdW9drf89dMZoCHTvsDbmrw4fGAxPc2l1+yI4kh3a3GOXwTwYEiQDrkgZwRQxlC hAF5DSI9RtO/VwangKd++0h6pYbRFotloei8TjRWLg0Q6Psp7LqW9JF0xLsCCjK6Ds7W dJ+elu0krZrg9P39GTxRyu4F8qexLWDx7Pct6O1avNZqP8qdRTMLu+EvUE9kE6m1gayV Orqg==
X-Gm-Message-State: ALoCoQnysLjiNkVDe7j70vzA/+8rcLZZ3DAVn8TPbHdINfH19fgGcXAOKNFubA0LAQstPQZMurHqv5l3vA/o+38Zu4x3SEqE+yj6EclmgxHrV1YTV65PSnOnJH/9cYJPnqHCWByGOcw+
X-Received: by 10.42.113.134 with SMTP id c6mr6682853icq.17.1428708358225; Fri, 10 Apr 2015 16:25:58 -0700 (PDT)
X-Received: by 10.42.113.134 with SMTP id c6mr6682838icq.17.1428708358056; Fri, 10 Apr 2015 16:25:58 -0700 (PDT)
Received: from x-128-101-233-117.uofm-secure.wireless.umn.edu ([2607:ea00:104:2000:8475:ae36:2dc5:425d]) by mx.google.com with ESMTPSA id j126sm183723ioe.22.2015.04.10.16.25.55 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Apr 2015 16:25:56 -0700 (PDT)
Message-ID: <55285BFF.2040903@umn.edu>
Date: Fri, 10 Apr 2015 18:25:51 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55281BDB.1040804@umn.edu> <CO1PR05MB4426AB890F76C434BBF03DEAEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4426AB890F76C434BBF03DEAEFA0@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DnalglZbrzX0zb5m7oessaiEVuQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 23:26:04 -0000

Sure, that works, but few nits;

- The first "GRE" in in the second sentence seems redundant, I'd suggest 
just removing it.

- Except for applying to IPv6, the fourth sentence says almost the same 
thing as the third sentence.  I'd suggest adding ", including IPv6" to 
the second sentence, and remove the fourth sentence all together.

- The double use of the word "beyond" in the last sentence seems 
redundant as well.  Maybe substitute, "Otherwise," for "Beyond that," at 
the beginning of the sentence.

Putting those together you get;

The security section of [RFC 4023] identifies threats encountered when 
MPLS is deliver over GRE. These threats apply equally to any payload 
that is delivered over GRE, including IPv6. As stated in RFC 4023, these 
threats can be mitigated by authenticating and/or encrypting the 
delivery packet using IPSec [RFC 4301] procedures. Otherwise, the 
current specification introduces no security considerations beyond those 
mentioned in RFC 2784.

More generically, security considerations for IPv6 are discussed in 
[RFC4942], operational security for IPv6 is discussed in 
[I-D.ietf-opsec-v6], and security concerns for tunnels in general are 
discussed in [RFC6169].

On 4/10/15 17:24 , Ronald Bonica wrote:
> David, Lucy,
>
> Having thought about it a little more, would you mind if I crafted the text as follows:
>
> The security section of [RFC 4023] identifies threats encountered when MPLS is deliver over GRE. These threats apply equally to any GRE payload that is delivered over GRE. As stated in RFC 4023, these threats can be mitigated by authenticating and/or encrypting the delivery packet using IPSec [RFC 4301] procedures. When the payload is IPv6, they can also be mitigated by authenticating and/or encrypting the payload using IPSec. Beyond that, the current specification introduces no security considerations beyond those mentioned in RFC 2784.
>
> More generically, security considerations for IPv6 are discussed in  [RFC4942], operational security for IPv6 is discussed in [I-D.ietf-opsec-v6], and security concerns for tunnels in general are  discussed in [RFC6169].
>
>
>                                                                            Ron


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Fri Apr 10 17:30:47 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7BA1A8996; Fri, 10 Apr 2015 17:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k08UTfP-KybJ; Fri, 10 Apr 2015 17:30:43 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0130.outbound.protection.outlook.com [207.46.100.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 2B2411A8742; Fri, 10 Apr 2015 17:30:42 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.1.130.23; Sat, 11 Apr 2015 00:30:41 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Sat, 11 Apr 2015 00:30:41 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: David Farmer <farmer@umn.edu>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQc795MeXvxGLYck68SuOpfDNlq51G0K1wgAATMYCAAA1p4A==
Date: Sat, 11 Apr 2015 00:30:41 +0000
Message-ID: <CO1PR05MB4421C79D81A2B90F313A5A9AEF90@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55281BDB.1040804@umn.edu> <CO1PR05MB4426AB890F76C434BBF03DEAEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55285BFF.2040903@umn.edu>
In-Reply-To: <55285BFF.2040903@umn.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.13]
authentication-results: umn.edu; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB442;
x-microsoft-antispam-prvs: <CO1PR05MB442DFA3162768E3458DDB34AEF90@CO1PR05MB442.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(24454002)(479174004)(377454003)(252514010)(13464003)(51704005)(77156002)(106116001)(230783001)(66066001)(2656002)(102836002)(33656002)(74316001)(54356999)(2201001)(122556002)(76176999)(99286002)(40100003)(19580395003)(92566002)(19580405001)(2950100001)(93886004)(2900100001)(46102003)(86362001)(2171001)(76576001)(107886001)(62966003)(50986999)(87936001)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CO1PR05MB442; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB442; 
x-forefront-prvs: 05437568AA
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2015 00:30:41.2936 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB442
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TQpnjGVXMjCJpzkJujMFaSwmIJY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 00:30:45 -0000

> -----Original Message-----
> From: David Farmer [mailto:farmer@umn.edu]
> Sent: Friday, April 10, 2015 7:26 PM
> To: Ronald Bonica; Lucy yong; int-area@ietf.org; ipv6@ietf.org
> Cc: David Farmer
> Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intar=
ea-
> gre-ipv6-05.txt
>=20
> Sure, that works, but few nits;
>=20
> - The first "GRE" in in the second sentence seems redundant, I'd suggest =
just
> removing it.
[RPB]=20

Yikes! That was certainly redundant! I will remove it.

>=20
> - Except for applying to IPv6, the fourth sentence says almost the same t=
hing
> as the third sentence.  I'd suggest adding ", including IPv6" to the seco=
nd
> sentence, and remove the fourth sentence all together.
[RPB]=20

I don't agree. In the third sentence, the GRE ingress and GRE egress nodes =
execute IPSec procedures. They encrypt and/or authenticate the GRE delivery=
 header. (That's all you can do when the payload is MPLS).  In the fourth s=
entence, the payload originator and payload destination execute IPSec proce=
dures. They encrypt and/or authenticate the payload packet. This is an opti=
on when the payload is IPv6.=20

In the first case, the=20
>=20
> - The double use of the word "beyond" in the last sentence seems
> redundant as well.  Maybe substitute, "Otherwise," for "Beyond that," at =
the
> beginning of the sentence.
[RPB]=20

Agree.


                     Ron

>=20
> Putting those together you get;
>=20
> The security section of [RFC 4023] identifies threats encountered when MP=
LS
> is deliver over GRE. These threats apply equally to any payload that is
> delivered over GRE, including IPv6. As stated in RFC 4023, these threats =
can
> be mitigated by authenticating and/or encrypting the delivery packet usin=
g
> IPSec [RFC 4301] procedures. Otherwise, the current specification introdu=
ces
> no security considerations beyond those mentioned in RFC 2784.
>=20
> More generically, security considerations for IPv6 are discussed in [RFC4=
942],
> operational security for IPv6 is discussed in [I-D.ietf-opsec-v6], and se=
curity
> concerns for tunnels in general are discussed in [RFC6169].
>=20
> On 4/10/15 17:24 , Ronald Bonica wrote:
> > David, Lucy,
> >
> > Having thought about it a little more, would you mind if I crafted the =
text as
> follows:
> >
> > The security section of [RFC 4023] identifies threats encountered when
> MPLS is deliver over GRE. These threats apply equally to any GRE payload
> that is delivered over GRE. As stated in RFC 4023, these threats can be
> mitigated by authenticating and/or encrypting the delivery packet using
> IPSec [RFC 4301] procedures. When the payload is IPv6, they can also be
> mitigated by authenticating and/or encrypting the payload using IPSec.
> Beyond that, the current specification introduces no security considerati=
ons
> beyond those mentioned in RFC 2784.
> >
> > More generically, security considerations for IPv6 are discussed in
> [RFC4942], operational security for IPv6 is discussed in [I-D.ietf-opsec-=
v6],
> and security concerns for tunnels in general are  discussed in [RFC6169].
> >
> >
> >
> > Ron
>=20
>=20
> --
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> David Farmer               Email: farmer@umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE     Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From nobody Fri Apr 10 18:37:49 2015
Return-Path: <farmer@umn.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9AB01AC423 for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 18:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ni_bcm3aUZWh for <ipv6@ietfa.amsl.com>; Fri, 10 Apr 2015 18:37:46 -0700 (PDT)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.119.20]) by ietfa.amsl.com (Postfix) with ESMTP id 617AB1AC41C for <ipv6@ietf.org>; Fri, 10 Apr 2015 18:37:46 -0700 (PDT)
Received: from mail-ig0-f175.google.com (mail-ig0-f175.google.com [209.85.213.175]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <ipv6@ietf.org>; Fri, 10 Apr 2015 20:37:45 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ig0-f175.google.com [209.85.213.175] #+LO+TS+TR
X-Umn-Classification: local
Received: by igbqf9 with SMTP id qf9so11044558igb.1 for <ipv6@ietf.org>; Fri, 10 Apr 2015 18:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/UtbCKxIPfS3S90+Gi0jtmC36AHO4s7RUz2XN9RwdxQ=; b=j09uOBWfvcqkOcCmipZ5pM2CgBexUncmCY/GToEScH4fZi6zNBoKlMUGoFxYqPUzax dOa3uvXdHAbnGcy2A1n6ptD0ZYo5Iw9ZHFECym8yu2Tk9f9hAYZPMh2hAm7qPRzE6W+i NhO6mrtP82/MvghBKlKV3T8Fypz+Aq+wxe1Sk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=/UtbCKxIPfS3S90+Gi0jtmC36AHO4s7RUz2XN9RwdxQ=; b=EPDBBxSfS1Z2XGZ0X+4r34+Dobt52O1TbznaUvdpKFyHMZ3haTx4PD+bYP7zaa9Fsk 5Pk/cmBsdLww+3qXSO/Kl3HGn8VPt5kebWbf2wIGEfpATfnY/zU8/f0e+qcvYbCRh+H5 Y0Ai37EH9rp6vOA1I9/TJKwKk6fsejdj31ybZ0JQ/MRwH6RxS60dX6GUTk1Y7XVGPnJg 5KfE+ow2sAMCK5UcGVL6WRdP1ABcmC6gWsDD2idYDYlbonOn22Hwz3Pw3eyCgsTWzvNl AxiPfpAxZacl6uQYAl9hRWp1HwB0GTZe0jmPFG6hgwHR3O1GET4cWDLbUV9DppyAmi6L ZWxA==
X-Gm-Message-State: ALoCoQmfJasiNzsBgxxnbpZFZsXaLsljC73qHEy3lAWC1httyfj+4rig/GmTXGsSdPUFWJDh0EgdNbCtdAWSCo7L44FPwR8iubtRuGkgfxx6oJ9sej2HDtJ6zy636eshJgj8eji9xzza
X-Received: by 10.50.79.229 with SMTP id m5mr2184750igx.23.1428716264754; Fri, 10 Apr 2015 18:37:44 -0700 (PDT)
X-Received: by 10.50.79.229 with SMTP id m5mr2184726igx.23.1428716264314; Fri, 10 Apr 2015 18:37:44 -0700 (PDT)
Received: from oit201651646.local ([2601:2:5b00:a9f:b024:8bbc:9164:c351]) by mx.google.com with ESMTPSA id lp7sm925536igb.20.2015.04.10.18.37.41 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Apr 2015 18:37:42 -0700 (PDT)
Message-ID: <55287AE2.8050304@umn.edu>
Date: Fri, 10 Apr 2015 20:37:38 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55281BDB.1040804@umn.edu> <CO1PR05MB4426AB890F76C434BBF03DEAEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55285BFF.2040903@umn.edu> <CO1PR05MB4421C79D81A2B90F313A5A9AEF90@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4421C79D81A2B90F313A5A9AEF90@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qyT1-eKat3ajx-vDgtq8GhhK7cI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 01:37:48 -0000

On 4/10/15 19:30 , Ronald Bonica wrote:

>> - Except for applying to IPv6, the fourth sentence says almost the same thing
>> as the third sentence.  I'd suggest adding ", including IPv6" to the second
>> sentence, and remove the fourth sentence all together.
> [RPB]
>
> I don't agree. In the third sentence, the GRE ingress and GRE egress nodes execute IPSec procedures. They encrypt and/or authenticate the GRE delivery header. (That's all you can do when the payload is MPLS).  In the fourth sentence, the payload originator and payload destination execute IPSec procedures. They encrypt and/or authenticate the payload packet. This is an option when the payload is IPv6.

Ok, I missed that distinction the first time, I might not be the only 
one that misses it. How can that distinction be highlighted a little 
more?  Maybe something like the following:

Alternatively when the payload is IPv6, these threats can also be 
mitigated by authenticating and/or encrypting the payload using IPSec, 
instead of the delivery packet.





-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Fri Apr 10 18:41:28 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C10421B2EA6; Fri, 10 Apr 2015 18:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7y4Kl2m2tWd; Fri, 10 Apr 2015 18:41:23 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0797.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::797]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CD171B2CE1; Fri, 10 Apr 2015 18:41:22 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.1.130.23; Sat, 11 Apr 2015 01:41:03 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Sat, 11 Apr 2015 01:41:03 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: David Farmer <farmer@umn.edu>, Lucy yong <lucy.yong@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-05.txt
Thread-Index: AQHQc795MeXvxGLYck68SuOpfDNlq51G0K1wgAATMYCAAA1p4IAAF2kAgAAA2+A=
Date: Sat, 11 Apr 2015 01:41:02 +0000
Message-ID: <CO1PR05MB442D34E028DB0FD7BB6C7E9AEF90@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150409205737.10780.29197.idtracker@ietfa.amsl.com> <CO1PR05MB44234C6DEF4BE6593ABC6C0AEFB0@CO1PR05MB442.namprd05.prod.outlook.com> <2691CE0099834E4A9C5044EEC662BB9D5715802F@dfweml701-chm> <CO1PR05MB4429D2A048A36DF703D6DF5AEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55281BDB.1040804@umn.edu> <CO1PR05MB4426AB890F76C434BBF03DEAEFA0@CO1PR05MB442.namprd05.prod.outlook.com> <55285BFF.2040903@umn.edu> <CO1PR05MB4421C79D81A2B90F313A5A9AEF90@CO1PR05MB442.namprd05.prod.outlook.com> <55287AE2.8050304@umn.edu>
In-Reply-To: <55287AE2.8050304@umn.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.13]
authentication-results: umn.edu; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB441;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(479174004)(252514010)(377454003)(24454002)(51704005)(13464003)(76176999)(19580405001)(19580395003)(66066001)(46102003)(33656002)(86362001)(93886004)(2501003)(87936001)(106116001)(2950100001)(107886001)(76576001)(2656002)(2171001)(99286002)(50986999)(40100003)(74316001)(2900100001)(102836002)(122556002)(62966003)(77156002)(2201001)(92566002)(230783001)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <CO1PR05MB4416CA88172759840EE16A8AEF90@CO1PR05MB441.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CO1PR05MB441; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB441; 
x-forefront-prvs: 05437568AA
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2015 01:41:02.8560 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB441
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fHWPsRK0Ci-uvYo5SrcdLdwc7G8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 01:41:24 -0000

Works for me. I will spin a new version and post it in a few minutes.

                                      Ron


> -----Original Message-----
> From: David Farmer [mailto:farmer@umn.edu]
> Sent: Friday, April 10, 2015 9:38 PM
> To: Ronald Bonica; Lucy yong; int-area@ietf.org; ipv6@ietf.org
> Cc: David Farmer
> Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intar=
ea-
> gre-ipv6-05.txt
>=20
> On 4/10/15 19:30 , Ronald Bonica wrote:
>=20
> >> - Except for applying to IPv6, the fourth sentence says almost the
> >> same thing as the third sentence.  I'd suggest adding ", including
> >> IPv6" to the second sentence, and remove the fourth sentence all
> together.
> > [RPB]
> >
> > I don't agree. In the third sentence, the GRE ingress and GRE egress no=
des
> execute IPSec procedures. They encrypt and/or authenticate the GRE
> delivery header. (That's all you can do when the payload is MPLS).  In th=
e
> fourth sentence, the payload originator and payload destination execute
> IPSec procedures. They encrypt and/or authenticate the payload packet. Th=
is
> is an option when the payload is IPv6.
>=20
> Ok, I missed that distinction the first time, I might not be the only one=
 that
> misses it. How can that distinction be highlighted a little more?  Maybe
> something like the following:
>=20
> Alternatively when the payload is IPv6, these threats can also be mitigat=
ed by
> authenticating and/or encrypting the payload using IPSec, instead of the
> delivery packet.
>=20
>=20
>=20
>=20
>=20
> --
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> David Farmer               Email: farmer@umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE     Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From nobody Fri Apr 10 18:45:42 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2171B2F1C; Fri, 10 Apr 2015 18:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tMG87iilOGc; Fri, 10 Apr 2015 18:45:38 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0786.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::786]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D3E41B2F0F; Fri, 10 Apr 2015 18:45:38 -0700 (PDT)
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.1.130.23; Sat, 11 Apr 2015 01:45:17 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Sat, 11 Apr 2015 01:45:17 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: FW: New Version Notification for draft-ietf-intarea-gre-ipv6-06.txt
Thread-Topic: New Version Notification for draft-ietf-intarea-gre-ipv6-06.txt
Thread-Index: AQHQc/kAF00w+FoQ/UGi9PVoOkID1J1HCkwQ
Date: Sat, 11 Apr 2015 01:45:16 +0000
Message-ID: <CO1PR05MB442EAF7CCD2493EA5B159ECAEF90@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150411014404.22246.15898.idtracker@ietfa.amsl.com>
In-Reply-To: <20150411014404.22246.15898.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.13]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB443;
x-microsoft-antispam-prvs: <CO1PR05MB443392527BE968A2D2F3487AEF90@CO1PR05MB443.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377424004)(13464003)(69234005)(377454003)(51704005)(74316001)(76576001)(2501003)(107886001)(15975445007)(102836002)(19580405001)(19580395003)(99286002)(62966003)(77156002)(106116001)(2420400003)(40100003)(66066001)(1720100001)(122556002)(450100001)(46102003)(230783001)(92566002)(87936001)(2950100001)(54356999)(86362001)(2656002)(50986999)(33656002)(76176999)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CO1PR05MB443; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB443; 
x-forefront-prvs: 05437568AA
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2015 01:45:16.0623 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB443
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/faJW4C_07HU15g-l_NhrCeETgV0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 01:45:40 -0000

DQpGWUkNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddDQo+IFNlbnQ6
IEZyaWRheSwgQXByaWwgMTAsIDIwMTUgOTo0NCBQTQ0KPiBUbzogUm9uYWxkIEJvbmljYTsgU3Vy
ZXNoIEtyaXNobmFuOyBTdXJlc2ggS3Jpc2huYW47IENhcmxvcyBQaWduYXRhcm87DQo+IFJvbmFs
ZCBCb25pY2E7IENhcmxvcyBQaWduYXRhcm8NCj4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZp
Y2F0aW9uIGZvciBkcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYtMDYudHh0DQo+IA0KPiANCj4g
QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni0wNi50eHQN
Cj4gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBSb24gQm9uaWNhIGFuZCBwb3N0
ZWQgdG8gdGhlIElFVEYNCj4gcmVwb3NpdG9yeS4NCj4gDQo+IE5hbWU6CQlkcmFmdC1pZXRmLWlu
dGFyZWEtZ3JlLWlwdjYNCj4gUmV2aXNpb246CTA2DQo+IFRpdGxlOgkJSVB2NiBTdXBwb3J0IGZv
ciBHZW5lcmljIFJvdXRpbmcgRW5jYXBzdWxhdGlvbiAoR1JFKQ0KPiBEb2N1bWVudCBkYXRlOgky
MDE1LTA0LTExDQo+IEdyb3VwOgkJaW50YXJlYQ0KPiBQYWdlczoJCTgNCj4gVVJMOiAgICAgICAg
ICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtaW50YXJl
YS1ncmUtaXB2Ni0NCj4gMDYudHh0DQo+IFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWludGFyZWEtZ3JlLWlwdjYvDQo+IEh0bWxpemVk
OiAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWludGFyZWEtZ3Jl
LWlwdjYtMDYNCj4gRGlmZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91
cmwyPWRyYWZ0LWlldGYtaW50YXJlYS1ncmUtaXB2Ni0wNg0KPiANCj4gQWJzdHJhY3Q6DQo+ICAg
IEdlbmVyaWMgUm91dGluZyBFbmNhcHN1bGF0aW9uIChHUkUpIGNhbiBiZSB1c2VkIHRvIGNhcnJ5
IGFueSBuZXR3b3JrLQ0KPiAgICBsYXllciBwYXlsb2FkIHByb3RvY29sIG92ZXIgYW55IG5ldHdv
cmstbGF5ZXIgZGVsaXZlcnkgcHJvdG9jb2wuICBHUkUNCj4gICAgcHJvY2VkdXJlcyBhcmUgc3Bl
Y2lmaWVkIGZvciBJUHY0LCB1c2VkIGFzIGVpdGhlciB0aGUgcGF5bG9hZCBvcg0KPiAgICBkZWxp
dmVyeSBwcm90b2NvbC4gIEhvd2V2ZXIsIEdSRSBwcm9jZWR1cmVzIGFyZSBub3Qgc3BlY2lmaWVk
IGZvcg0KPiAgICBJUHY2Lg0KPiANCj4gICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgR1JFIHBy
b2NlZHVyZXMgZm9yIElQdjYsIHVzZWQgYXMgZWl0aGVyIHRoZQ0KPiAgICBwYXlsb2FkIG9yIGRl
bGl2ZXJ5IHByb3RvY29sLiAgSXQgdXBkYXRlcyB0aGUgR1JFIHNwZWNpZmljYXRpb24sIFJGQw0K
PiAgICAyNzg0Lg0KPiANCj4gDQo+IA0KPiANCj4gDQo+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5
IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCj4g
dW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29s
cy5pZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Sat Apr 11 10:15:16 2015
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F091A802D for <ipv6@ietfa.amsl.com>; Sat, 11 Apr 2015 10:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.811
X-Spam-Level: 
X-Spam-Status: No, score=-11.811 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SofG6Nz_faay for <ipv6@ietfa.amsl.com>; Sat, 11 Apr 2015 10:15:13 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE9DB1A7D85 for <ipv6@ietf.org>; Sat, 11 Apr 2015 10:15:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1664; q=dns/txt; s=iport; t=1428772513; x=1429982113; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=2B6ZQJk/8YjGocn1WwFj0dEGH4TnoQpL/nUY9wrLNoc=; b=P941C8P4lffAFNU0l12UD3TxoRTzOC+wQIOKkPFzZe3+kWKqrljhagPm 5PFN6eSBuv+FkkB8/SwlkALlR7f7hU3Go1q4PV7Z/M/yERVVL0ziEME8E OAIziqShwiniCu7jPk/pbAybQwdwuNxj3Ut7bXf3NS+pSl1+Tr0K9UtwE A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A/BQAiVSlV/4cNJK1cgwxSXAWDEMMmhgECHIEVTAEBAQEBAX6EHwEBAQQjEToLDAQCAQgRBAEBAwIGHQMCAgIwFAEICAIEAQ0FCIgiDbZLljkBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIEhigqESxYbBwaCYi+BFgWRDIN5mwIig29vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.11,562,1422921600"; d="scan'208";a="407934714"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP; 11 Apr 2015 17:15:13 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t3BHFCC1001659 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 11 Apr 2015 17:15:12 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Sat, 11 Apr 2015 12:15:12 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Topic: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Index: AQHQaKOAKqvfH3IQjk2pNXw/o2k3AJ1II2oA
Date: Sat, 11 Apr 2015 17:15:11 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B891683D5A4@xmb-rcd-x06.cisco.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
In-Reply-To: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.253.223]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jBtTCgk6Y3ou5j5WYGzED6zpsH0>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 17:15:16 -0000

SSAgc3VwcG9ydCB0aGlzIGRvY3VtZW50J3MgYWRvcHRpb24gYnkgNm1hbi4gIE1pbm9yIGVkaXRz
IGFyZSBpbmNsdWRlZCBiZWxvdy4NCg0KU2VjdGlvbiA1DQoNCnMvYSBvcHRpb24vYW4gb3B0aW9u
Lw0KDQpTZWN0aW9uIDcuMiBhbmQgb3RoZXIgcGxhY2VzDQoNCnMvZXRjL2V0Yy4vDQoNCnMvY2Fu
IG5vdC9jYW5ub3QvDQoNCkhlbWFudA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG
cm9tOiBpcHY2IFttYWlsdG86aXB2Ni1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQm9i
IEhpbmRlbg0KU2VudDogRnJpZGF5LCBNYXJjaCAyNywgMjAxNSAxMTozNCBBTQ0KVG86IElQdjYg
TGlzdA0KQ2M6IDZtYW4gQ2hhaXJzDQpTdWJqZWN0OiA2TUFOIFdHIEFkb3B0aW9uIENhbGw6IGRy
YWZ0LW5vcmRtYXJrLTZtYW4tcnMtcmVmcmVzaC0wMQ0KDQpUaGlzIG1lc3NhZ2Ugc3RhcnRzIGEg
dHdvIHdlZWsgNk1BTiBXb3JraW5nIEdyb3VwIExhc3QgQ2FsbCBvbiBhZG9wdGluZzoNCg0KICAg
ICAgICBUaXRsZSAgICAgICAgICAgOiBJUHY2IE5laWdoYm9yIERpc2NvdmVyeSBPcHRpb25hbCBV
bmljYXN0IFJTL1JBIFJlZnJlc2gNCiAgICAgICAgQXV0aG9ycyAgICAgICAgIDogRXJpayBOb3Jk
bWFyaw0KICAgICAgICAgICAgICAgICAgICAgICAgICBBbmRyZXcgWW91cnRjaGVua28NCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgU3VyZXNoIEtyaXNobmFuDQogICAgICAgIEZpbGVuYW1lICAg
ICAgICA6IGRyYWZ0LW5vcmRtYXJrLTZtYW4tcnMtcmVmcmVzaC0wMS50eHQNCiAgICAgICAgUGFn
ZXMgICAgICAgICAgIDogMTINCiAgICAgICAgRGF0ZSAgICAgICAgICAgIDogMjAxNC0xMC0yNw0K
DQogICAgICAgIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ub3JkbWFyay02bWFu
LXJzLXJlZnJlc2gtMDENCg0KYXMgYSB3b3JraW5nIGdyb3VwIGRvY3VtZW50LiBTdWJzdGFudGl2
ZSBjb21tZW50cyBhbmQgc3RhdGVtZW50cyBvZiBzdXBwb3J0IGZvciBhZG9wdGluZyB0aGlzIGRv
Y3VtZW50IHNob3VsZCBiZSBkaXJlY3RlZCB0byB0aGUgbWFpbGluZyBsaXN0LiAgRWRpdG9yaWFs
IHN1Z2dlc3Rpb25zIGNhbiBiZSBzZW50IHRvIHRoZSBhdXRob3JzLiAgVGhpcyBhZG9wdGlvbiBj
YWxsIHdpbGwgZW5kIG9uIEFwcmlsIDEwLCAyMDE1Lg0KDQpSZWdhcmRzLA0KDQpCb2IgSGluZGVu
ICYgT2xlIFRyw7hhbg0KDQo=


From nobody Sun Apr 12 21:17:25 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C271ACD5F for <ipv6@ietfa.amsl.com>; Sun, 12 Apr 2015 21:17:24 -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=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afteHCmhHFpY for <ipv6@ietfa.amsl.com>; Sun, 12 Apr 2015 21:17:23 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::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 097A81ACD6A for <ipv6@ietf.org>; Sun, 12 Apr 2015 21:17:23 -0700 (PDT)
Received: by pddn5 with SMTP id n5so93633373pdd.2 for <ipv6@ietf.org>; Sun, 12 Apr 2015 21:17:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zPWmQ3CLXB4w+pTgy1Sn+41qoOipxrA/ViFZ9ZD3iZs=; b=ydpo6y7AfHS+uIMiKyF9nJFjn8d6o2uzkC9E0VbzsW7xzxPBfag6u0ty3RHOXKoPTm /pcc8EYlXbvODBHYZ593icGWih7UZrhZ6XacmMGK7dJSClvQ1uFfZ5w3hJamVZIWEK07 t4P8qpBQhJdrOO1sCsv9XcBCnzrL1Z2nv1y+zJoXwFBey1flFEFyuFKsZrjLMQRJQst6 ECH5UbREXvY+5HF/ckX5royEodf9I/68XMTjawYc8TNel1/fJfVjnYVVUG6qCxKWDIw7 fhiogXFmnZmBYVlRo+OmETTHptx4VpAB7hb+IEM3pjBu5Rtv+TPmkHT6qdJzAHGUH/fi W/mw==
X-Received: by 10.70.101.200 with SMTP id fi8mr22991468pdb.161.1428898642704;  Sun, 12 Apr 2015 21:17:22 -0700 (PDT)
Received: from ?IPv6:2406:e007:695b:1:28cc:dc4c:9703:6781? ([2406:e007:695b:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id tg14sm5746282pac.15.2015.04.12.21.17.19 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Apr 2015 21:17:21 -0700 (PDT)
Message-ID: <552B434D.6080201@gmail.com>
Date: Mon, 13 Apr 2015 16:17:17 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>,  Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: IPv6 as a Standard?
References: <201503302354.t2UNsMwV067446@givry.fdupont.fr> <4FFB4718-271C-4E8A-BA15-E6E38C88485A@employees.org>
In-Reply-To: <4FFB4718-271C-4E8A-BA15-E6E38C88485A@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DUC75Qyso8ZRJs0SLplmbiYEbFU>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 04:17:24 -0000

On 04/04/2015 09:54, Ole Troan wrote:
>>>> IPv6 is 20 year old (cf my next message) so it is time to launch the=

>>>> process to make it a (full) Standard!
>>>
>>> Age is not the question - does it meet the criteria in RFC 6410?
>>> I think the answer is yes, but the questions about errata and unused
>>> features have to be answered.
>>>
>>> And there is a practical problem caused by "Updated by RFC5095, RFC57=
22,
>>> RFC5871, RFC6437, RFC6564, RFC6935, RFC6946, RFC7045, RFC7112". There=
's
>>> no way 2460 can be promoted as-is.
>>
>> =3D> I believe the answer is in your second sentence, i.e., errata and=

>> unused features are in the updating RFCs. So:
>> (1) 2 implementations: no issue
>> (2) errata: to be done (*)
>> (3) unused feature: to be done (*)
>> (4) IPR: none
>> So we have to produce a "consolidated" version of RFC 2460 merging mos=
t
>> of the updating RFCs (what I marked with (*)). The token is in the han=
ds
>> of the WG chairs=E2=80=A6
>=20
> Bob and I had a look at sub-set of the IPv6 core RFCs that are at draft=
 standard during IETF week.
> at least for 2460 the errata do not look to be an issue. nor are we awa=
re of any unused features.
>=20
> RFC6410 says nothing about =E2=80=9CUpdated by=E2=80=9D RFCs, and we ha=
ve asked our AD to get a clarification from the IESG.
> in case we are required to incorporate the "Updated by=E2=80=9D RFCs, a=
s opposed to promote the document as-is, it might require a more thorough=
 discussion. I did a first pass at incorporating the changes suggested in=
 those RFCs, and it turns out that a couple of them are not just simple e=
ditorial changes. likewise we need to consider if it is wise to publish t=
he IPv6 specification under a new RFC number.

I've been thinking about this from time to time, and I conclude that RFC =
2460
has been updated by so many RFCs that it would be very misleading to prom=
ote it
as-is. It may be that the correct solution is a lot of work, unfortunatel=
y.

    Brian


From nobody Mon Apr 13 03:01:37 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BE01B30C5; Mon, 13 Apr 2015 03:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.11
X-Spam-Level: 
X-Spam-Status: No, score=-13.11 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 602Dx9Xg9uNG; Mon, 13 Apr 2015 03:01:33 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90CC31B30C7; Mon, 13 Apr 2015 03:01:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1663; q=dns/txt; s=iport; t=1428919292; x=1430128892; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to; bh=v/+EypcDFLsmHsL4EYmjLa/xdv3kqBTNdnyyBS+Uypg=; b=do+Ji4NqB+1tuhnf+G542JCtldICzoq4vWjz8yiu+wD/uJq14s0urJ2B 9FrYvTzgpTzaxZxuExBBCnru1nw2otIdkJgzk9gYcHmFfzTAKBc0QYJZZ s0D3V0mGg2g7SuGXInqgdtCPrSvieFODIYjZrFzEHn9dX6jr8os8mSZyi Q=;
X-IronPort-AV: E=Sophos;i="5.11,569,1422921600";  d="scan'208,217";a="425157990"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 13 Apr 2015 10:01:30 +0000
Received: from [10.55.98.187] (ams-stbryant-88110.cisco.com [10.55.98.187]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t3DA1UVp015768; Mon, 13 Apr 2015 10:01:30 GMT
Message-ID: <552B93FA.4040606@cisco.com>
Date: Mon, 13 Apr 2015 11:01:30 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-06.txt
References: <20150411014404.22246.15898.idtracker@ietfa.amsl.com> <CO1PR05MB442EAF7CCD2493EA5B159ECAEF90@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB442EAF7CCD2493EA5B159ECAEF90@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------080705030903020701030509"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/88qQ1nq2zRnZqsbCYq-aRojjIUM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 10:01:34 -0000

This is a multi-part message in MIME format.
--------------080705030903020701030509
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit


Ron

The text

GRE over IPv6 is  deployable only in environments where the network 
operator
deems the  risk associated with behavior c) to be acceptable.

really cries out for some form of RFC2119 language such as:

GRE over IPv6 is MUST NOT be deployed other than where the
network operator deems the  risk associated with behavior c) to be
acceptable.

or something similar.

- Stewart

--------------080705030903020701030509
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <meta http-equiv="content-type" content="text/html;
      charset=windows-1252">
    <br>
    Ron<br>
    <br>
    The text<br>
    <br>
    GRE over IPv6 is  deployable only in environments where the network
    operator <br>
    deems the  risk associated with behavior c) to be acceptable.<br>
    <br>
    really cries out for some form of RFC2119 language such as:<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=windows-1252">
    GRE over IPv6 is MUST NOT be deployed other than where the <br>
    network operator deems the  risk associated with behavior c) to be <br>
    acceptable.<br>
    <br>
    or something similar.<br>
    <br>
    - Stewart<br>
  </body>
</html>

--------------080705030903020701030509--


From nobody Mon Apr 13 04:16:34 2015
Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDB5D1A9071; Mon, 13 Apr 2015 04:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PqFIFie2DDBW; Mon, 13 Apr 2015 04:16:30 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0131.outbound.protection.outlook.com [207.46.100.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81BC81A9068; Mon, 13 Apr 2015 04:16:30 -0700 (PDT)
Received: from CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) by CO1PR05MB523.namprd05.prod.outlook.com (10.141.72.18) with Microsoft SMTP Server (TLS) id 15.1.136.25; Mon, 13 Apr 2015 11:16:29 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) with Microsoft SMTP Server (TLS) id 15.1.130.23; Mon, 13 Apr 2015 11:16:28 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.220]) with mapi id 15.01.0130.020; Mon, 13 Apr 2015 11:16:28 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-06.txt
Thread-Topic: [Int-area] FW: New Version Notification for draft-ietf-intarea-gre-ipv6-06.txt
Thread-Index: AQHQc/kAF00w+FoQ/UGi9PVoOkID1J1HCkwQgAOvYgCAABTNkA==
Date: Mon, 13 Apr 2015 11:16:28 +0000
Message-ID: <CO1PR05MB4428A66797CCD7C2A1E5A3CAEE70@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20150411014404.22246.15898.idtracker@ietfa.amsl.com> <CO1PR05MB442EAF7CCD2493EA5B159ECAEF90@CO1PR05MB442.namprd05.prod.outlook.com> <552B93FA.4040606@cisco.com>
In-Reply-To: <552B93FA.4040606@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.10]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rbonica@juniper.net; 
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB444; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB523; 
x-microsoft-antispam-prvs: <CO1PR05MB444CE882C8FA112D13893DCAEE70@CO1PR05MB444.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(189002)(199003)(81156005)(46102003)(74316001)(19300405004)(230783001)(97736003)(16236675004)(99286002)(2501003)(40100003)(122556002)(19625215002)(33656002)(101416001)(2950100001)(92566002)(2900100001)(19580395003)(19580405001)(77156002)(62966003)(68736005)(2420400003)(102836002)(15975445007)(86362001)(87936001)(2656002)(2201001)(54356999)(76176999)(50986999)(107886001)(106116001)(106356001)(105586002)(76576001)(64706001)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB444; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CO1PR05MB444; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB444; 
x-forefront-prvs: 0545EFAC9A
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: multipart/alternative; boundary="_000_CO1PR05MB4428A66797CCD7C2A1E5A3CAEE70CO1PR05MB442namprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2015 11:16:28.1175 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB444
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0uORJ04cCZEdQ5iTw6O21eQqEIM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 11:16:32 -0000

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

Stuart,

Works for me. I just made the change and posted a new version of the draft.

                                Ron


From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Monday, April 13, 2015 6:02 AM
To: Ronald Bonica; int-area@ietf.org; ipv6@ietf.org
Subject: Re: [Int-area] FW: New Version Notification for draft-ietf-intarea=
-gre-ipv6-06.txt


Ron

The text

GRE over IPv6 is  deployable only in environments where the network operato=
r
deems the  risk associated with behavior c) to be acceptable.

really cries out for some form of RFC2119 language such as:

GRE over IPv6 is MUST NOT be deployed other than where the
network operator deems the  risk associated with behavior c) to be
acceptable.

or something similar.

- Stewart

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;
	color:black;}
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:#1F497D;}
.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=3D"white" lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Stuart,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">Works for me. I just made the change =
and posted a new version of the draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><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=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif;color:windowtext">From:</span></b><span style=3D"=
font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:windowtex=
t"> Stewart Bryant [mailto:stbryant@cisco.com]
<br>
<b>Sent:</b> Monday, April 13, 2015 6:02 AM<br>
<b>To:</b> Ronald Bonica; int-area@ietf.org; ipv6@ietf.org<br>
<b>Subject:</b> Re: [Int-area] FW: New Version Notification for draft-ietf-=
intarea-gre-ipv6-06.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><br>
Ron<br>
<br>
The text<br>
<br>
GRE over IPv6 is&nbsp; deployable only in environments where the network op=
erator <br>
deems the&nbsp; risk associated with behavior c) to be acceptable.<br>
<br>
really cries out for some form of RFC2119 language such as:<br>
<br>
GRE over IPv6 is MUST NOT be deployed other than where the <br>
network operator deems the&nbsp; risk associated with behavior c) to be <br=
>
acceptable.<br>
<br>
or something similar.<br>
<br>
- Stewart<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_CO1PR05MB4428A66797CCD7C2A1E5A3CAEE70CO1PR05MB442namprd_--


From nobody Mon Apr 13 11:06:42 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8B81AD35D; Mon, 13 Apr 2015 11:06: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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q6RXA-16Ajap; Mon, 13 Apr 2015 11:06:40 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2126F1AD0CC; Mon, 13 Apr 2015 11:06:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <6man-chairs@ietf.org>, <ipv6@ietf.org>, <ot@cisco.com>
Subject: ID Tracker State Update Notice: <draft-ietf-6man-resilient-rs-06.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150413180640.22801.51840.idtracker@ietfa.amsl.com>
Date: Mon, 13 Apr 2015 11:06:40 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/eTFk3Vv5nUPkJopYguwLkQz75Vo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 18:06:41 -0000

IESG has approved the document and state has been changed to Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/


From nobody Mon Apr 13 11:06:48 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3E71AD151; Mon, 13 Apr 2015 11:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xX7HatXcir3r; Mon, 13 Apr 2015 11:06:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A98A1AD2D5; Mon, 13 Apr 2015 11:06:40 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Protocol Action: 'Packet loss resiliency for Router Solicitations' to Proposed Standard (draft-ietf-6man-resilient-rs-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150413180640.22801.60585.idtracker@ietfa.amsl.com>
Date: Mon, 13 Apr 2015 11:06:40 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hJJjH8BsE-pgZZGNvlpk8bDObkw>
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 18:06:43 -0000

The IESG has approved the following document:
- 'Packet loss resiliency for Router Solicitations'
  (draft-ietf-6man-resilient-rs-06.txt) as Proposed Standard

This document is the product of the IPv6 Maintenance Working Group.

The IESG contact persons are Brian Haberman and Terry Manderson.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/





Technical Summary

   When an interface on a host is initialized, the host transmits
   Router Solicitations in order to minimize the amount of time it
   needs to wait until the next unsolicited multicast Router
   Advertisement is received. In certain scenarios, router
   solicitations transmitted by the host might be lost. This document
   specifies a mechanism for hosts to cope with the loss of the
   initial Router Solicitations.

Working Group Summary

   The initial revision of this work was published in July 2012. There
   is a strong consensus that this solves a real problem.

Document Quality

  The 6man working group appoints reviewers for all documents being
  advanced to the IESG. This document has been reviewed in detail by
  6man reviewers, and it has had extensive discussion on the mailing
  list.
  
Personnel

  Document Shepherd: Ole Troan
  Responsible Area Director: Brian Haberman


From nobody Mon Apr 13 12:05:38 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8578B1B31B1; Mon, 13 Apr 2015 12:05:37 -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, TVD_SPACE_RATIO=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N975sSJDGnQK; Mon, 13 Apr 2015 12:05:36 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF391B3184; Mon, 13 Apr 2015 12:05:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <6man-chairs@ietf.org>, <ipv6@ietf.org>, <ot@cisco.com>
Subject: ID Tracker State Update Notice: <draft-ietf-6man-resilient-rs-06.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150413190526.32303.52442.idtracker@ietfa.amsl.com>
Date: Mon, 13 Apr 2015 12:05:26 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/nS999sYrmlDK2MZqHhcY4kbLp8o>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 19:05:37 -0000

IANA action state changed to No IC
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/


From nobody Tue Apr 14 09:05:20 2015
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59C6D1B2E23 for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 09:05:18 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KKRFVQGDwVTE for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 09:05:13 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C2491B2E1B for <ipv6@ietf.org>; Tue, 14 Apr 2015 09:02:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1812; q=dns/txt; s=iport; t=1429027345; x=1430236945; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=MmUQHhUq0ZWDKz4Qoe1QopB2mpIZpcuK5S0g0AXIRr8=; b=PLu5OjaOhk7gOtr19eOH5my2Cq4SJyhCxMxI2vsfpywg+HCWUnEO/eNV 7C+802Lc7GucmE2gJ/8fzPOPiEXOsgnV3pYYdADHzLpn8UT3ahL976Phu 6504kUqvszB8oDWIcVYPjcOPpqKiTzqSamPbyjFhbSM/m7bMUsvJwluoG 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BeBAAfOS1V/5RdJa1cgwxSXAWDEMFvZgmBToYBAhyBKTgUAQEBAQEBAX2EHwEBAQQjEToLDAQCAQgRBAEBAwIGHQMCAgIwFAEICAIEAQ0FCIgiDbVylX4BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIEhigqESzEHBoJiL4EWBZEOg3mGGZRrIoNvb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,576,1422921600"; d="scan'208";a="141099755"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-1.cisco.com with ESMTP; 14 Apr 2015 16:02:24 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t3EG2N8x026595 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Apr 2015 16:02:23 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.140]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Tue, 14 Apr 2015 11:02:23 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Topic: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Index: AQHQaKOEVZA6wXDokUWTePgaTrbfBp1Mxehw
Date: Tue, 14 Apr 2015 16:02:22 +0000
Deferred-Delivery: Tue, 14 Apr 2015 16:02:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD849DCD999@xmb-rcd-x01.cisco.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
In-Reply-To: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.192.57]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WYRnGHovR7KpTqfuT1q5Gpp_2sk>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 16:05:18 -0000

RGVhciBhbGw6DQoNClRoaXMgZG9jdW1lbnRzIGNvbnRyaWJ1dGVzIHRvIHRoZSByZWR1Y3Rpb24g
b2YgbXVsdGljYXN0IG5vaXNlLCB3aGljaCBpcyBjcml0aWNhbCBpbiBtYW55IGVudmlyb25tZW50
cyBhcyBkaXNjdXNzZWQgaW4gdGhlIGludHJvLg0KVGhlIGRvY3VtZW50IGlzIGFscmVhZHkgc291
bmQgd2l0aCBhIGNsZWFybHkgZGVmaW5lZCBiZWhhdmlvci4gSSBzdXBwb3J0IHRoZSBhZG9wdGlv
bi4NCg0KQ2hlZXJzLA0KDQpQYXNjYWwNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
PiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Yg
Qm9iIEhpbmRlbg0KPiBTZW50OiB2ZW5kcmVkaSAyNyBtYXJzIDIwMTUgMTY6MzQNCj4gVG86IElQ
djYgTGlzdA0KPiBDYzogNm1hbiBDaGFpcnMNCj4gU3ViamVjdDogNk1BTiBXRyBBZG9wdGlvbiBD
YWxsOiBkcmFmdC1ub3JkbWFyay02bWFuLXJzLXJlZnJlc2gtMDENCj4gDQo+IFRoaXMgbWVzc2Fn
ZSBzdGFydHMgYSB0d28gd2VlayA2TUFOIFdvcmtpbmcgR3JvdXAgTGFzdCBDYWxsIG9uIGFkb3B0
aW5nOg0KPiANCj4gICAgICAgICBUaXRsZSAgICAgICAgICAgOiBJUHY2IE5laWdoYm9yIERpc2Nv
dmVyeSBPcHRpb25hbCBVbmljYXN0IFJTL1JBIFJlZnJlc2gNCj4gICAgICAgICBBdXRob3JzICAg
ICAgICAgOiBFcmlrIE5vcmRtYXJrDQo+ICAgICAgICAgICAgICAgICAgICAgICAgICAgQW5kcmV3
IFlvdXJ0Y2hlbmtvDQo+ICAgICAgICAgICAgICAgICAgICAgICAgICAgU3VyZXNoIEtyaXNobmFu
DQo+ICAgICAgICAgRmlsZW5hbWUgICAgICAgIDogZHJhZnQtbm9yZG1hcmstNm1hbi1ycy1yZWZy
ZXNoLTAxLnR4dA0KPiAgICAgICAgIFBhZ2VzICAgICAgICAgICA6IDEyDQo+ICAgICAgICAgRGF0
ZSAgICAgICAgICAgIDogMjAxNC0xMC0yNw0KPiANCj4gICAgICAgICBodHRwczovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtbm9yZG1hcmstNm1hbi1ycy1yZWZyZXNoLTAxDQo+IA0KPiBhcyBh
IHdvcmtpbmcgZ3JvdXAgZG9jdW1lbnQuIFN1YnN0YW50aXZlIGNvbW1lbnRzIGFuZCBzdGF0ZW1l
bnRzIG9mIHN1cHBvcnQNCj4gZm9yIGFkb3B0aW5nIHRoaXMgZG9jdW1lbnQgc2hvdWxkIGJlIGRp
cmVjdGVkIHRvIHRoZSBtYWlsaW5nIGxpc3QuICBFZGl0b3JpYWwNCj4gc3VnZ2VzdGlvbnMgY2Fu
IGJlIHNlbnQgdG8gdGhlIGF1dGhvcnMuICBUaGlzIGFkb3B0aW9uIGNhbGwgd2lsbCBlbmQgb24g
QXByaWwgMTAsDQo+IDIwMTUuDQo+IA0KPiBSZWdhcmRzLA0KPiANCj4gQm9iIEhpbmRlbiAmIE9s
ZSBUcsO4YW4NCg0K


From nobody Tue Apr 14 09:17:47 2015
Return-Path: <hosnieh.rafiee@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D421B2E01 for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 09:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dnbwTAb2suYk for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 09:17:44 -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 DCAFB1B2D8A for <ipv6@ietf.org>; Tue, 14 Apr 2015 09:17:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUV54226; Tue, 14 Apr 2015 16:17:42 +0000 (GMT)
Received: from LHREML504-MBS.china.huawei.com ([10.125.30.107]) by lhreml402-hub.china.huawei.com ([10.201.5.241]) with mapi id 14.03.0158.001; Tue, 14 Apr 2015 17:17:39 +0100
From: Hosnieh Rafiee <hosnieh.rafiee@huawei.com>
To: IPv6 List <ipv6@ietf.org>
Subject: RE: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Topic: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Index: AQHQaKOEVZA6wXDokUWTePgaTrbfBp1MxehwgAAFmtA=
Date: Tue, 14 Apr 2015 16:17:37 +0000
Message-ID: <814D0BFB77D95844A01CA29B44CBF8A701527777@lhreml504-mbs>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <E045AECD98228444A58C61C200AE1BD849DCD999@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD849DCD999@xmb-rcd-x01.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.82.219]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vHK1ewDBsF3pLCX_neCM7st-jDA>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 16:17:45 -0000

DQorMQ0KDQpJIHN1cHBvcnQgdGhlIGFkb3B0aW9uIG9mIHRoaXMgZG9jdW1lbnQuDQoNCkhvc25p
ZWgNCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlwdjYgW21haWx0
bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBQYXNjYWwgVGh1YmVydA0KPiAo
cHRodWJlcnQpDQo+IFNlbnQ6IFR1ZXNkYXksIEFwcmlsIDE0LCAyMDE1IDY6MDIgUE0NCj4gVG86
IEJvYiBIaW5kZW47IElQdjYgTGlzdA0KPiBDYzogNm1hbiBDaGFpcnMNCj4gU3ViamVjdDogUkU6
IDZNQU4gV0cgQWRvcHRpb24gQ2FsbDogZHJhZnQtbm9yZG1hcmstNm1hbi1ycy1yZWZyZXNoLTAx
DQo+IA0KPiBEZWFyIGFsbDoNCj4gDQo+IFRoaXMgZG9jdW1lbnRzIGNvbnRyaWJ1dGVzIHRvIHRo
ZSByZWR1Y3Rpb24gb2YgbXVsdGljYXN0IG5vaXNlLCB3aGljaA0KPiBpcyBjcml0aWNhbCBpbiBt
YW55IGVudmlyb25tZW50cyBhcyBkaXNjdXNzZWQgaW4gdGhlIGludHJvLg0KPiBUaGUgZG9jdW1l
bnQgaXMgYWxyZWFkeSBzb3VuZCB3aXRoIGEgY2xlYXJseSBkZWZpbmVkIGJlaGF2aW9yLiBJDQo+
IHN1cHBvcnQgdGhlIGFkb3B0aW9uLg0KPiANCj4gQ2hlZXJzLA0KPiANCj4gUGFzY2FsDQo+IA0K
PiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJvbTogaXB2NiBbbWFpbHRvOmlw
djYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEJvYiBIaW5kZW4NCj4gPiBTZW50OiB2
ZW5kcmVkaSAyNyBtYXJzIDIwMTUgMTY6MzQNCj4gPiBUbzogSVB2NiBMaXN0DQo+ID4gQ2M6IDZt
YW4gQ2hhaXJzDQo+ID4gU3ViamVjdDogNk1BTiBXRyBBZG9wdGlvbiBDYWxsOiBkcmFmdC1ub3Jk
bWFyay02bWFuLXJzLXJlZnJlc2gtMDENCj4gPg0KPiA+IFRoaXMgbWVzc2FnZSBzdGFydHMgYSB0
d28gd2VlayA2TUFOIFdvcmtpbmcgR3JvdXAgTGFzdCBDYWxsIG9uDQo+IGFkb3B0aW5nOg0KPiA+
DQo+ID4gICAgICAgICBUaXRsZSAgICAgICAgICAgOiBJUHY2IE5laWdoYm9yIERpc2NvdmVyeSBP
cHRpb25hbCBVbmljYXN0DQo+IFJTL1JBIFJlZnJlc2gNCj4gPiAgICAgICAgIEF1dGhvcnMgICAg
ICAgICA6IEVyaWsgTm9yZG1hcmsNCj4gPiAgICAgICAgICAgICAgICAgICAgICAgICAgIEFuZHJl
dyBZb3VydGNoZW5rbw0KPiA+ICAgICAgICAgICAgICAgICAgICAgICAgICAgU3VyZXNoIEtyaXNo
bmFuDQo+ID4gICAgICAgICBGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1ub3JkbWFyay02bWFuLXJz
LXJlZnJlc2gtMDEudHh0DQo+ID4gICAgICAgICBQYWdlcyAgICAgICAgICAgOiAxMg0KPiA+ICAg
ICAgICAgRGF0ZSAgICAgICAgICAgIDogMjAxNC0xMC0yNw0KPiA+DQo+ID4gICAgICAgICBodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbm9yZG1hcmstNm1hbi1ycy1yZWZyZXNoLTAx
DQo+ID4NCj4gPiBhcyBhIHdvcmtpbmcgZ3JvdXAgZG9jdW1lbnQuIFN1YnN0YW50aXZlIGNvbW1l
bnRzIGFuZCBzdGF0ZW1lbnRzIG9mDQo+ID4gc3VwcG9ydCBmb3IgYWRvcHRpbmcgdGhpcyBkb2N1
bWVudCBzaG91bGQgYmUgZGlyZWN0ZWQgdG8gdGhlIG1haWxpbmcNCj4gPiBsaXN0LiAgRWRpdG9y
aWFsIHN1Z2dlc3Rpb25zIGNhbiBiZSBzZW50IHRvIHRoZSBhdXRob3JzLiAgVGhpcw0KPiA+IGFk
b3B0aW9uIGNhbGwgd2lsbCBlbmQgb24gQXByaWwgMTAsIDIwMTUuDQo+ID4NCj4gPiBSZWdhcmRz
LA0KPiA+DQo+ID4gQm9iIEhpbmRlbiAmIE9sZSBUcsO4YW4NCj4gDQo+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+
IElFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdA0KPiBpcHY2QGlldGYub3JnDQo+
IEFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2lwdjYNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg==


From nobody Tue Apr 14 11:16:06 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A9A1A802A; Tue, 14 Apr 2015 11:16:04 -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, TVD_SPACE_RATIO=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6C5yZncSJdAA; Tue, 14 Apr 2015 11:16:03 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B171A6F7A; Tue, 14 Apr 2015 11:16:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <6man-chairs@ietf.org>, <ipv6@ietf.org>, <ot@cisco.com>
Subject: ID Tracker State Update Notice: <draft-ietf-6man-resilient-rs-06.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150414181603.10766.50093.idtracker@ietfa.amsl.com>
Date: Tue, 14 Apr 2015 11:16:03 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7WWj_nTJb0nDg_LL02VpS4PBk5s>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 18:16:04 -0000

IESG state changed to RFC Ed Queue from Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/


From nobody Tue Apr 14 12:56:38 2015
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E0A1A1A54 for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 12:56:37 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djroMTisbicc for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 12:56:36 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001: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 595711A1A1D for <ipv6@ietf.org>; Tue, 14 Apr 2015 12:56:36 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so24166970igb.0 for <ipv6@ietf.org>; Tue, 14 Apr 2015 12:56:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:date:message-id:cc:to:mime-version;  bh=BOaAklb13wVJw+G3MoNMc2wBqUrFIl2cx6cPDZCpUQ4=; b=ScSZUf1b6GQ6Er+qJYzImlDOEDCbXNRPQPnNWFeGqQQ3HlhOdr7tB/AChZIBu1ctRM iGiaRkhXRmvtI7jMsE+5uAKkglq/At5sSdzbEQFcrRtrc8/J+jpWyfsdHZYKL1OztJtW BlkPR9Z3pldJIeGr+znsLz+rDNiNi7Iabzddy4kui+fY4jjvHKBFAgYhAhBKSJNWqj8+ fD2BC6cvJiZa3/L3R4Zmtu/1eiv9yxwrz4xYjBgSCTKKDXqAUWKKSHP48iCvmMQB8CrX 6Po83+Tzhs2O7t+s4vHsjA2meD0Ibt6YINyzDjC3Qe2OJK2H2EXq87A8HZQE5m0k+dyy ZlIQ==
X-Received: by 10.51.17.7 with SMTP id ga7mr26354845igd.42.1429041395748; Tue, 14 Apr 2015 12:56:35 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id i80sm1033624iod.6.2015.04.14.12.56.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Apr 2015 12:56:35 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
X-Pgp-Agent: GPGMail 2.5b6
Content-Type: multipart/signed; boundary="Apple-Mail=_62A65ADD-AB26-41F6-B9E8-4EA417A118D4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN IETF92 Minutes
Date: Tue, 14 Apr 2015 12:56:32 -0700
Message-Id: <8C3D0A50-A649-42D7-8192-F5F88685DA00@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ifUX0OUbJ2iTWLXnkjQpiGIbyC4>
Cc: Ole Jacobsen <olejacobsen@me.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 19:56:38 -0000

--Apple-Mail=_62A65ADD-AB26-41F6-B9E8-4EA417A118D4
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

The minutes for the 6MAN session at IETF92 can be found at:

  https://www.ietf.org/proceedings/92/minutes/minutes-92-6man

Many thanks to Erik Kline for taking the minutes.

Thanks,
Bob & Ole



--Apple-Mail=_62A65ADD-AB26-41F6-B9E8-4EA417A118D4
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

iQEcBAEBCgAGBQJVLXDwAAoJEK7rdBF357uoJwoIAJS/cYZ0eP7V7qEbDmKBk9zN
yI7P5CJHqXw0XBnbM2GvyxRHQhJJX85KotofnL2pIR3XJLl9N0fHXwnWmgXE821E
2S7RYVa/NoRMKRbWAZR9c/HaObuICxcIHqmBWUQYjtWSs9uzUO4mM3ptPJSGH540
N/nrWZlR0n8A8+Gz8ikNdXuW2Ceq/QI9uJjsobBmVLxa4rgKPzB3yEDtbPuxfHVh
HwEJgbezC7uy2Y9sDAi8w6WuobLkmP5xrhzbjWyjZoRl71CvqhxQ8V1ag7BWBKGi
C/vxdcTPuW2RxvBsrpvgrURyIsL4vBxImcFauqar+xJ68R2IWofHMzWeyXB2AJY=
=UiCQ
-----END PGP SIGNATURE-----

--Apple-Mail=_62A65ADD-AB26-41F6-B9E8-4EA417A118D4--


From nobody Tue Apr 14 14:13:48 2015
Return-Path: <olejacobsen@me.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9391B2A08 for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 13:24: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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBewKOJi3jTM for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 13:24:27 -0700 (PDT)
Received: from st11p00mm-asmtp003.mac.com (st11p00mm-asmtpout003.mac.com [17.172.81.2]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07A9E1B29FE for <ipv6@ietf.org>; Tue, 14 Apr 2015 13:24:27 -0700 (PDT)
Received: from 173-11-110-132-sfba.hfc.comcastbusiness.net (173-11-110-132-SFBA.hfc.comcastbusiness.net [173.11.110.132]) by st11p00mm-asmtp003.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NMT00KUQCOJBW30@st11p00mm-asmtp003.mac.com> for ipv6@ietf.org; Tue, 14 Apr 2015 20:24:26 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-04-14_06:2015-04-14,2015-04-14,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=3 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1504140170
Date: Tue, 14 Apr 2015 13:24:21 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN IETF92 Minutes
In-reply-to: <8C3D0A50-A649-42D7-8192-F5F88685DA00@gmail.com>
Message-id: <alpine.OSX.2.01.1504141321560.3843@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <8C3D0A50-A649-42D7-8192-F5F88685DA00@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/QQ2QuQz4In7k2wgjm3KLlWKJ_8Y>
X-Mailman-Approved-At: Tue, 14 Apr 2015 14:13:46 -0700
Cc: Ole Jacobsen <olejacobsen@me.com>, IPv6 List <ipv6@ietf.org>, Ole Troan <ot@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 20:24:31 -0000

Bob,

As you know, I am morally opposed to IPv6 and I object strongly
to having my name associated with this protocol in any shape or
form!

OK, that was a joke, but you probably meant to copy "the other
Ole" [copied here] :-)

Cheers,

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
UK Cell: +44 7805 977889
docomo: (090) 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com
E-mail: ole@protocoljournal.org
Skype: organdemo



On Tue, 14 Apr 2015, Bob Hinden wrote:

> The minutes for the 6MAN session at IETF92 can be found at:
> 
>   https://www.ietf.org/proceedings/92/minutes/minutes-92-6man
> 
> Many thanks to Erik Kline for taking the minutes.
> 
> Thanks,
> Bob & Ole
> 
> 
> 


From nobody Tue Apr 14 14:59:40 2015
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFEF81A6FCB for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 14:59:38 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6xeLwZX8m_Y for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 14:59:36 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001: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 C9BC51A6F3C for <ipv6@ietf.org>; Tue, 14 Apr 2015 14:59:36 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so26865516igb.1 for <ipv6@ietf.org>; Tue, 14 Apr 2015 14:59:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=tmtvT1MNR0Chl+PLnGFfHwrh8CYM12nDFnJh5tbrtzg=; b=JVHVAnOPp7xjPaorpPQ9zPZst8Yw/6Qf9dQms4dCOGv9VZazXc35O+Npdu50wfsmH6 XInh225qkZd3Elo0H+wVLY3bK7Ed8nh52xMs3vrPqBYbte25ruZDzSYRZP+PcRxtp23a mGiPLgqIXujqeVi/Th4JOICE9PuVIMKgyE3+/W5ACaWpxE/9XIMlpEmxvYXQTcQNdnDX etCmem7CfAYv1c12Wll8m7mr45quzMRttvfR2s2DOWfZfbe/QqSSNqZZLXUP5WR8fUUn 7YWC6/R6/ZIWHqgFHPQy6EJbhnu2yFczlBLZvKG/6BprqPHKI3Tki8KMGa1UsRH4TdMM FY0Q==
X-Received: by 10.107.26.207 with SMTP id a198mr31502310ioa.5.1429048776247; Tue, 14 Apr 2015 14:59:36 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id 16sm1205001ion.20.2015.04.14.14.59.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Apr 2015 14:59:35 -0700 (PDT)
Subject: Re: 6MAN IETF92 Minutes
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3E84DD71-CD9D-4321-A3FA-A84442EF0A1C"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <alpine.OSX.2.01.1504141321560.3843@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Tue, 14 Apr 2015 14:59:32 -0700
Message-Id: <C23104D2-397C-4EAF-99E8-3F4B71408CF9@gmail.com>
References: <8C3D0A50-A649-42D7-8192-F5F88685DA00@gmail.com> <alpine.OSX.2.01.1504141321560.3843@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0dTfdMZIWk0DxnFIc7JD5LX5cXA>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, =?utf-8?Q?Ole_Tr=C3=B8an?= <ot@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 21:59:38 -0000

--Apple-Mail=_3E84DD71-CD9D-4321-A3FA-A84442EF0A1C
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Ole,

Yes, my mistake.  :-(

Bob

> On Apr 14, 2015, at 1:24 PM, Ole Jacobsen <olejacobsen@me.com> wrote:
> 
> 
> Bob,
> 
> As you know, I am morally opposed to IPv6 and I object strongly
> to having my name associated with this protocol in any shape or
> form!
> 
> OK, that was a joke, but you probably meant to copy "the other
> Ole" [copied here] :-)
> 
> Cheers,
> 
> Ole
> 
> 
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office:  +1 415-550-9433
> Cell:    +1 415-370-4628
> UK Cell: +44 7805 977889
> docomo: (090) 3337-9311
> Web: protocoljournal.org
> E-mail: olejacobsen@me.com
> E-mail: ole@protocoljournal.org
> Skype: organdemo
> 
> 
> 
> On Tue, 14 Apr 2015, Bob Hinden wrote:
> 
>> The minutes for the 6MAN session at IETF92 can be found at:
>> 
>>  https://www.ietf.org/proceedings/92/minutes/minutes-92-6man
>> 
>> Many thanks to Erik Kline for taking the minutes.
>> 
>> Thanks,
>> Bob & Ole
>> 
>> 
>> 


--Apple-Mail=_3E84DD71-CD9D-4321-A3FA-A84442EF0A1C
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

iQEcBAEBCgAGBQJVLY3EAAoJEK7rdBF357uorioH/RNdYu1Ur0QnamsTc2rFtHu0
FW59udzFMW+YxC5yZYYtlqz9vAvyUGvJrT93bUEJEneg1hQHNNsjPePDCoBAGrf3
JRjAWfqtcqW1qPe27ep/DnEHvIfOUfhzH5tT+YdyFmAqPJ25Vc1OXGEjroLsqCJW
thkRS4CC3DWxATMuroYwLx15QFd9Pu2wN6nCDqj200hEomwEiE1HJDxPDshCIj6P
wVT5JtfhuVUEzdtkHz8f6vyA88m9dERS9XH8j0Ci8ioCWf9RqQV6xTMyz8i3c/Jd
id5E3DmlBZ+m5l2RANINnuRQpexh4pK3siHgmX6GzC0THeaeTNy/1rKxyMZtUKo=
=cwee
-----END PGP SIGNATURE-----

--Apple-Mail=_3E84DD71-CD9D-4321-A3FA-A84442EF0A1C--


From nobody Tue Apr 14 15:02:06 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD47F1A7D80 for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 15:02:04 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WcNdtYdmI-Me for <ipv6@ietfa.amsl.com>; Tue, 14 Apr 2015 15:01:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 119F21A7D85 for <ipv6@ietf.org>; Tue, 14 Apr 2015 15:01:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <ipv6@ietf.org>
Subject: Milestones changed for 6man WG
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150414220157.9558.41537.idtracker@ietfa.amsl.com>
Date: Tue, 14 Apr 2015 15:01:57 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/e9VYGA8zxvO6eFKfF1Ry-YIdr-I>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 22:02:04 -0000

Changed milestone "Plan for advancing core IPv6 core specifications to
Internet Standard", set due date to July 2015 from July 2014.

URL: http://datatracker.ietf.org/wg/6man/charter/


From nobody Wed Apr 15 03:55:41 2015
Return-Path: <loganaden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3281A1EF1 for <ipv6@ietfa.amsl.com>; Wed, 15 Apr 2015 03:55:39 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAi8KiS-ws9l for <ipv6@ietfa.amsl.com>; Wed, 15 Apr 2015 03:55:37 -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 84DB91A1EEE for <ipv6@ietf.org>; Wed, 15 Apr 2015 03:55:37 -0700 (PDT)
Received: by oica37 with SMTP id a37so16930486oic.0 for <ipv6@ietf.org>; Wed, 15 Apr 2015 03:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VQOukNGLRUvFdtQzKu6/reY54El6n3WkVDxM+J3NBgA=; b=FKZMrP8t2dvwoqwLPg8cDKAC1UWsQF2bfbhRrF2KTS4FJxTzbTBEs2UgxL6ihX3+/A ewxTTSHogBzdiwFW553++Z0+xNu6MgJ46RrEUCzSTq+MF1HJUR8Ejjgami3yqEgBY42h iqBkbfiNQNzIJV1Obc67YniQtXC0ou/o/if6VbK98E+3nLvlztlnNvnW0rajXJCHYVHG Ak5HhQBK2O+upfZkcSis393Gn86mPqTY19MkEMP1kItC7l1yA3Q6/HcO+X8zS85YRnes bRryXpfNMV0W7jtkl9Bksw9r09M2gcPqMnVu7Gwz34iIDfAbp5r1byt1iRFI3G8y/onJ zMJA==
MIME-Version: 1.0
X-Received: by 10.50.79.134 with SMTP id j6mr7559228igx.33.1429095336985; Wed, 15 Apr 2015 03:55:36 -0700 (PDT)
Received: by 10.50.25.231 with HTTP; Wed, 15 Apr 2015 03:55:36 -0700 (PDT)
In-Reply-To: <8C3D0A50-A649-42D7-8192-F5F88685DA00@gmail.com>
References: <8C3D0A50-A649-42D7-8192-F5F88685DA00@gmail.com>
Date: Wed, 15 Apr 2015 14:55:36 +0400
Message-ID: <CAOp4FwT-t+Tae=n2SB_o5mFJBbNFm2RNNfiBnpJBN9Tjm0F8pA@mail.gmail.com>
Subject: Re: 6MAN IETF92 Minutes
From: Loganaden Velvindron <loganaden@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sBlSPodqfZpZp1qNsh4FIAcemcA>
Cc: Ole Jacobsen <olejacobsen@me.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 10:55:39 -0000

On Tue, Apr 14, 2015 at 11:56 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> The minutes for the 6MAN session at IETF92 can be found at:
>
>   https://www.ietf.org/proceedings/92/minutes/minutes-92-6man
>
> Many thanks to Erik Kline for taking the minutes.
>
> Thanks,
> Bob & Ole
>
>

Thank you for taking the time to post the minutes, and thanks to the
team which is uploading the sessions on youtube.



>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 
This message is strictly personal and the opinions expressed do not
represent those of my employers, either past or present.


From nobody Wed Apr 15 15:53:25 2015
Return-Path: <jon.cronin@hp.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC7931AC3A1 for <ipv6@ietfa.amsl.com>; Wed, 15 Apr 2015 15:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.08
X-Spam-Level: 
X-Spam-Status: No, score=-1.08 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_MED=-2.3, TVD_SPACE_RATIO=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EbtvaYWSA_lc for <ipv6@ietfa.amsl.com>; Wed, 15 Apr 2015 15:53:22 -0700 (PDT)
Received: from g9t5008.houston.hp.com (g9t5008.houston.hp.com [15.240.92.66]) (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 73A3A1ABD3A for <ipv6@ietf.org>; Wed, 15 Apr 2015 15:53:22 -0700 (PDT)
Received: from G4W6310.americas.hpqcorp.net (g4w6310.houston.hp.com [16.210.26.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g9t5008.houston.hp.com (Postfix) with ESMTPS id 5DA74824 for <ipv6@ietf.org>; Wed, 15 Apr 2015 22:53:21 +0000 (UTC)
Received: from G4W6303.americas.hpqcorp.net (16.210.26.228) by G4W6310.americas.hpqcorp.net (16.210.26.217) with Microsoft SMTP Server (TLS) id 14.3.169.1; Wed, 15 Apr 2015 22:51:10 +0000
Received: from G9W0721.americas.hpqcorp.net ([169.254.2.185]) by G4W6303.americas.hpqcorp.net ([16.210.26.228]) with mapi id 14.03.0169.001; Wed, 15 Apr 2015 22:51:10 +0000
From: "Cronin, Jon" <jon.cronin@hp.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: unsubscribe
Thread-Topic: unsubscribe
Thread-Index: AdB3zqRfO6nOlCI1SmSPoy8P+0OfdQ==
Date: Wed, 15 Apr 2015 22:51:09 +0000
Message-ID: <0B874456FB46054F8B16F61EA0B8A56423A76362@G9W0721.americas.hpqcorp.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [16.210.48.14]
Content-Type: multipart/alternative; boundary="_000_0B874456FB46054F8B16F61EA0B8A56423A76362G9W0721americas_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pxlFPdDqDO8lUXvCiFWmAyTyjMI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 22:53:24 -0000

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

unsubscribe


--_000_0B874456FB46054F8B16F61EA0B8A56423A76362G9W0721americas_
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:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Franklin Gothic Book";
	panose-1:2 11 5 3 2 1 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Franklin Gothic Book",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Franklin Gothic Boo=
k&quot;,sans-serif">unsubscribe</span><span style=3D"font-family:&quot;Fran=
klin Gothic Book&quot;,sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_0B874456FB46054F8B16F61EA0B8A56423A76362G9W0721americas_--


From nobody Thu Apr 16 17:52:59 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A39F1A7009 for <ipv6@ietfa.amsl.com>; Thu, 16 Apr 2015 17:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.202
X-Spam-Level: ***
X-Spam-Status: No, score=3.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 NnWHwHE8Tfii for <ipv6@ietfa.amsl.com>; Thu, 16 Apr 2015 17:52:53 -0700 (PDT)
Received: from nm40-vm4.bullet.mail.bf1.yahoo.com (nm40-vm4.bullet.mail.bf1.yahoo.com [72.30.239.212]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8825A1A700C for <6man@ietf.org>; Thu, 16 Apr 2015 17:52:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1429231972; bh=XMWkvDg/anoDVFhSsOaMJZQJes32pF7eUwRa1/iN8oY=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=dxPg8mqYt+lEhKXEotuL36OXfkP2iq4ladayKP9NLsKmTX4elfzAgqUnPpppeZ3Ra50OnWCLAck5CGBEokqsRlaVjbvdJEkWxL2gti3AF8JLGzc2f1w5PCBtvY+bbwUA3XYBvNmlG/SnYv5WAVoY3W7fX5OE1vKi3uwT12Jj8rzjsufslhNnefan9JJwC/IOYLJZWxKuZtCxofnJnH23xY6eiQzRjdbvXPO2OYcSjQnYre2F/ROKoGcT2b50vI+6+47KkMeaAGk0AxebmKlveFKwtbg3Qbm6Vc3qa9djSSwFvZNrInc/LfeqJkgz2mxnhdznZ7A94Zpf1/7Vr8/ENg==
Received: from [98.139.214.32] by nm40.bullet.mail.bf1.yahoo.com with NNFMP; 17 Apr 2015 00:52:52 -0000
Received: from [98.139.215.251] by tm15.bullet.mail.bf1.yahoo.com with NNFMP;  17 Apr 2015 00:52:52 -0000
Received: from [127.0.0.1] by omp1064.mail.bf1.yahoo.com with NNFMP; 17 Apr 2015 00:52:52 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 743535.25283.bm@omp1064.mail.bf1.yahoo.com
X-YMail-OSG: 3otH1I8VM1nrFoMoA_OhniwQOOnxuNXkEH9Rf4YeXllj8wGb8m9nrBUJgdQZrPS 7v1Pax8umyaD4ITAD62bDgbsv.rzGxzGYA5d_LpW_yqjhzPfIjOa3hPJ4NOiQeGbNkHEEeVcChYu 7PwjDESzrVE1bdywCV667BA8V._Kc13hfPWW43eWoeD2lP0BB4WG9rpdDgPDr2MhYIhCyfEDTfsO MSXsfLVY5I4qqJL9zA_GJ.fTwyaYYwTvSWc1dV6fJ2AJypOZSxvyyUOvz9VP6md39EkcptmD0Vn_ hH5fiNppgGRHGezx2Kd11YpArfEehzj16ahMVVCJggcTCibLYLzVkwj4bEmLRaDPNzSIHxCFVNnk GVWHm5U9RBqh58s2af9pMXmq4Hx6OkCS7Qk5.9kMOYAJOeu7xWUGMWkPh_qmxw.0JYkzrsmrvyUL ZlGb.8O6o_8JeEvtclCz_69agnn31qIrlDllAHoqXvW2tGUmLb.3.pww9750RrEuRnezn6mISrXB K0YV99koSvxFYOIQvv6apQmYwM025ZwmUUWpYrwkF5mY-
Received: by 76.13.27.69; Fri, 17 Apr 2015 00:52:52 +0000 
Date: Fri, 17 Apr 2015 00:52:51 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "fgont@si6networks.com" <fgont@si6networks.com>,  "pavlix@pavlix.net" <pavlix@pavlix.net>,  "liushucheng@huawei.com" <liushucheng@huawei.com>
Message-ID: <922402387.5845419.1429231971293.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1059223520.4994623.1429165351434.JavaMail.yahoo@mail.yahoo.com>
References: <1059223520.4994623.1429165351434.JavaMail.yahoo@mail.yahoo.com>
Subject: Re: Some thoughts/comments on draft-gont-6man-slaac-dns-config-issues-01
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_5845418_1122128710.1429231971286"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pSBFziWKVKxjcpAXW413s7MIKnY>
Cc: "6man@ietf.org" <6man@ietf.org>, "marka@isc.org" <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 00:52:58 -0000

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

Fernando suggested I should have also CC'd 6man for further discussion/comm=
ents.
      From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
 To: "fgont@si6networks.com" <fgont@si6networks.com>; "pavlix@pavlix.net" <=
pavlix@pavlix.net>; "liushucheng@huawei.com" <liushucheng@huawei.com>=20
Cc: "marka@isc.org" <marka@isc.org>=20
 Sent: Thursday, 16 April 2015, 16:22
 Subject: Some thoughts/comments on draft-gont-6man-slaac-dns-config-issues=
-01
  =20
Hi,

CC'ing Mark Andrews, because he is one of the DNS experts I'm aware of, so =
it would be good to get his input.

I'm having a read though, here are some thoughts/comments I have on it. Pay=
 attention to or disregard at will!



1.=C2=A0 Introduction~~~~~~~~~~~~~~~

Regarding this discussion:

"The recommended bounds (MaxRtrAdvInterval <=3D
Lifetime <=3D 2*MaxRtrAdvInterval) have been found to be too short for
scenarios in which some Router Advertisement messages may be lost.
In such scenarios, hosts may fail to receive unsolicited Router
Advertisements and therefore fail to refresh the expiration time of
the DNS-related information previously learned through the RDNSS and
DNSSL options), thus eventually discarding the aforementioned DNS-
related information prematurely."


I think the more important thing to point out is that, as per RFC4861, Rout=
er Lifetime,

"The Router Lifetime applies only to
the router's usefulness as a default router; it
does not apply to information contained in other
message fields or options."

and,=20

"Options that need time limits for their information include their own
lifetime fields."

which means that option lifetime values are or should be independent of the=
 Router Lifetime value and its upper or lower value constants (e.g MaxRtrAd=
vInterval)
=20
In other words, state that the RDNSS and DNSSL lifetimes should have never =
been derived or limited to the RAs Router Lifetime value, and also observe =
that what has been specified in RFC6106 has caused the issues mentioned.


2.=C2=A0 Changing the Semantics of the 'Lifetime' field of RDNSS and DNSSL =
options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~


I'd suggest adding (enclosed in **s)

"o=C2=A0 The 'Lifetime' field indicates the amount of time during which the
aforementioned DNS-related information is expected to be stable.
A node is NOT required to discard the DNS-related information once
the Lifetime expires. ** The RDNSS and DNSSL Lifetime field values are now =
completely independent of the RA's Router Lifetime field value. ***"

to make this independence very clear.

I think it would also be worth pointing out, perhaps as a second paragraph =
to this point, that the DNS resolver in the client will take actions to dea=
l with unreachable DNS servers, in the case where the DNS information hasn'=
t been discarded despite the RDNSS option lifetime having expired. In other=
 words, the RDNSS lifetime value is not the absolute indication of whether =
a DNS server is useful or not, and the resolver will determine that by acti=
vely attempting to use the DNS server. Perhaps that means that the text sho=
uld be changed to=20
"A node is SHOULD NOT discard the DNS-related information once the Lifetime=
 expires."? (which I suppose almost makes the RDNSS option lifetime value r=
edundant?!)





"o=C2=A0 If a host has already gathered a sufficient number of RDNSS
addresses (or DNS search domain names), and additional data is
received while the existing entries have not yet expired, the
received RDNSS addresses (or DNS search domain names) SHOULD be
ignored."

I don't think the same rule for RDNSS can be also applied to the DNSSL opti=
ons.

In the case of RDNSS, the assumption would be that all of the DNS servers s=
upplied in the RDNSS option can provide equivalent DNS resolution service. =
For example, ignoring 2 out of 5 should not cause any issues, because the r=
emaining 3 should provide equivalent service to the ignored 2.

However, for DNSSL, I think ignoring some of them might cause failures, bec=
ause the options are not providing equivalent values. For example, say DNSS=
L:example.com and DNSSL:example.org were accepted, but DNSSL:example.net wa=
s ignored. If 'www' was looked up, and 'www.example.net' was the only entry=
 that should have matched, ignoring DNSSL:example.net would cause a lookup =
of 'www' to fail to match on 'www.example.net'. I think the resolver would =
then do a root lookup of 'www.' and that would either fail too or return so=
mething not intended.



"o=C2=A0 If a host receives new RDNSS addresses (or DNS search domain
names), and some of the existing entries have expired, the newly-
learned information SHOULD be used to replace the expired entries."
I think similar to above applies, different newer DNSSL option values aren'=
t replacements for older, expired DNSSL option values. Expired DNSSL option=
s should probably be thrown away when they expire.




"o=C2=A0 A host SHOULD flush configured DNS-related information when it has
any reason to believe that its network connectivity has changed in
some relevant way (e.g., there has been a "link change event").
When that happens, the host MAY send a Router Solicitation message
to re-learn the corresponding DNS-related information."

Perhaps another signal to trigger this could be repeated failed attempts by=
 the DNS resolver to use the majority or probably all of the existing DNS s=
erver IPv6 addresses?




3.=C2=A0 Changing the Default Values of the 'Lifetime' field of RDNSS and D=
NSSL options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~~~~~

Firstly, this is probably also a section where pointing out that the DNS re=
solver will make its own liveness tests/attempts to overcome the sorts of p=
acket loss mentioned.

Regarding this,

"
[RFC6106] is hereby updated as follows:

The default value of AdvRDNSSLifetime and AdvDNSSLLifetime MUST be
at least 10*MaxRtrAdvInterval so that the probability of hosts
receiving unsolicited Router Advertisements is increased."



I'm in two minds. On the one hand, I like the idea of having an automated d=
efault that is relative to the perceived level of packet loss that might oc=
cur. On the other hand, as before, Router Lifetime and its upper and lower =
limits are not general "whole of RA" lifetime constraints or RA robustness =
parameters.

Perhaps the middle ground would be to define a specific constant and then n=
ote that it is the 10 times the value of MaxRtrAdvInterval,=C2=A0 specified=
 in RFC4861. This would allow the specific constant to be changed at a late=
r time if necessary, or allow the operator to change the value, without bei=
ng constrained to it being 10*MaxRtrAdvInterval (that is, if it is defined =
as a formula, then in code it probably wouldn't be made an independently se=
ttable parameter, it'd just be calculated based on the current value of Max=
RtrAdvInterval).



4.=C2=A0 Use of Router Solicitations for active Probing~~~~~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I don't think the RDNSS and DNSSL RFC should have said anything about this,=
 as more generally, the problem is one of RA robustness, independent of wha=
t particular options are in the RA. Theoretically, different RA options cou=
ld define their own RA robustness methods that could end up being incompati=
ble with each other.

So perhaps it might be better to say that RA robustness is not specific to =
RDNSS and DNSSL options, and refer to a more general mechanism, if it exist=
s (?), regarding triggering RSes to seek new option values (hmm, I don't re=
member reading anything specific about it, but perhaps that means that RA o=
ption lifetimes are always greater than the unsolicited RA interval to ensu=
re option lifetimes are always refreshed before they expire?)



5.=C2=A0 Sanitize the received RDNSS/DNSSL 'Lifetime' Values~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As per above and other RA options, a constant upper limit would be better.




Regards,
Mark.


  
------=_Part_5845418_1122128710.1429231971286
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div id=3D"yui_3_16_0_1_14292300=
71708_12383" dir=3D"ltr"><span id=3D"yui_3_16_0_1_1429230071708_12582">Fern=
ando suggested I should have also CC'd 6man for further discussion/comments=
.</span></div><br>  <div style=3D"font-family: Helvetica Neue-Light, Helvet=
ica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif=
; font-size: 16px;" id=3D"yui_3_16_0_1_1429230071708_12573"> <div style=3D"=
font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande=
, Sans-Serif; font-size: 16px;" id=3D"yui_3_16_0_1_1429230071708_12572"> <d=
iv dir=3D"ltr" id=3D"yui_3_16_0_1_1429230071708_12571"> <hr size=3D"1" id=
=3D"yui_3_16_0_1_1429230071708_12576">  <font size=3D"2" face=3D"Arial" id=
=3D"yui_3_16_0_1_1429230071708_12574"> <b><span style=3D"font-weight:bold;"=
>From:</span></b> Mark ZZZ Smith &lt;markzzzsmith@yahoo.com.au&gt;<br> <b><=
span style=3D"font-weight: bold;">To:</span></b> "fgont@si6networks.com" &l=
t;fgont@si6networks.com&gt;; "pavlix@pavlix.net" &lt;pavlix@pavlix.net&gt;;=
 "liushucheng@huawei.com" &lt;liushucheng@huawei.com&gt; <br><b><span style=
=3D"font-weight: bold;">Cc:</span></b> "marka@isc.org" &lt;marka@isc.org&gt=
; <br> <b><span style=3D"font-weight: bold;">Sent:</span></b> Thursday, 16 =
April 2015, 16:22<br> <b><span style=3D"font-weight: bold;">Subject:</span>=
</b> Some thoughts/comments on draft-gont-6man-slaac-dns-config-issues-01<b=
r> </font> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1429230=
071708_12575"><br>Hi,<br><br>CC'ing Mark Andrews, because he is one of the =
DNS experts I'm aware of, so it would be good to get his input.<br><br>I'm =
having a read though, here are some thoughts/comments I have on it. Pay att=
ention to or disregard at will!<br><br><br><br>1.&nbsp; Introduction~~~~~~~=
~~~~~~~~<br><br>Regarding this discussion:<br><br>"The recommended bounds (=
MaxRtrAdvInterval &lt;=3D<br>Lifetime &lt;=3D 2*MaxRtrAdvInterval) have bee=
n found to be too short for<br>scenarios in which some Router Advertisement=
 messages may be lost.<br>In such scenarios, hosts may fail to receive unso=
licited Router<br>Advertisements and therefore fail to refresh the expirati=
on time of<br>the DNS-related information previously learned through the RD=
NSS and<br>DNSSL options), thus eventually discarding the aforementioned DN=
S-<br>related information prematurely."<br><br><br>I think the more importa=
nt thing to point out is that, as per RFC4861, Router Lifetime,<br><br>"The=
 Router Lifetime applies only to<br>the router's usefulness as a default ro=
uter; it<br>does not apply to information contained in other<br>message fie=
lds or options."<br><br>and, <br><br>"Options that need time limits for the=
ir information include their own<br>lifetime fields."<br><br>which means th=
at option lifetime values are or should be independent of the Router Lifeti=
me value and its upper or lower value constants (e.g MaxRtrAdvInterval)<br>=
 <br>In other words, state that the RDNSS and DNSSL lifetimes should have n=
ever been derived or limited to the RAs Router Lifetime value, and also obs=
erve that what has been specified in RFC6106 has caused the issues mentione=
d.<br><br><br>2.&nbsp; Changing the Semantics of the 'Lifetime' field of RD=
NSS and DNSSL options<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br><br>I'd suggest adding (enclosed in **s)<=
br><br>"o&nbsp; The 'Lifetime' field indicates the amount of time during wh=
ich the<br>aforementioned DNS-related information is expected to be stable.=
<br>A node is NOT required to discard the DNS-related information once<br>t=
he Lifetime expires. ** The RDNSS and DNSSL Lifetime field values are now c=
ompletely independent of the RA's Router Lifetime field value. ***"<br><br>=
to make this independence very clear.<br><br>I think it would also be worth=
 pointing out, perhaps as a second paragraph to this point, that the DNS re=
solver in the client will take actions to deal with unreachable DNS servers=
, in the case where the DNS information hasn't been discarded despite the R=
DNSS option lifetime having expired. In other words, the RDNSS lifetime val=
ue is not the absolute indication of whether a DNS server is useful or not,=
 and the resolver will determine that by actively attempting to use the DNS=
 server. Perhaps that means that the text should be changed to <br>"A node =
is SHOULD NOT discard the DNS-related information once the Lifetime expires=
."? (which I suppose almost makes the RDNSS option lifetime value redundant=
?!)<br><br><br><br><br><br>"o&nbsp; If a host has already gathered a suffic=
ient number of RDNSS<br>addresses (or DNS search domain names), and additio=
nal data is<br>received while the existing entries have not yet expired, th=
e<br>received RDNSS addresses (or DNS search domain names) SHOULD be<br>ign=
ored."<br><br>I don't think the same rule for RDNSS can be also applied to =
the DNSSL options.<br><br>In the case of RDNSS, the assumption would be tha=
t all of the DNS servers supplied in the RDNSS option can provide equivalen=
t DNS resolution service. For example, ignoring 2 out of 5 should not cause=
 any issues, because the remaining 3 should provide equivalent service to t=
he ignored 2.<br><br>However, for DNSSL, I think ignoring some of them migh=
t cause failures, because the options are not providing equivalent values. =
For example, say DNSSL:example.com and DNSSL:example.org were accepted, but=
 DNSSL:example.net was ignored. If 'www' was looked up, and 'www.example.ne=
t' was the only entry that should have matched, ignoring DNSSL:example.net =
would cause a lookup of 'www' to fail to match on 'www.example.net'. I thin=
k the resolver would then do a root lookup of 'www.' and that would either =
fail too or return something not intended.<br><br><br><br>"o&nbsp; If a hos=
t receives new RDNSS addresses (or DNS search domain<br>names), and some of=
 the existing entries have expired, the newly-<br>learned information SHOUL=
D be used to replace the expired entries."<br>I think similar to above appl=
ies, different newer DNSSL option values aren't replacements for older, exp=
ired DNSSL option values. Expired DNSSL options should probably be thrown a=
way when they expire.<br><br><br><br><br>"o&nbsp; A host SHOULD flush confi=
gured DNS-related information when it has<br>any reason to believe that its=
 network connectivity has changed in<br>some relevant way (e.g., there has =
been a "link change event").<br>When that happens, the host MAY send a Rout=
er Solicitation message<br>to re-learn the corresponding DNS-related inform=
ation."<br><br>Perhaps another signal to trigger this could be repeated fai=
led attempts by the DNS resolver to use the majority or probably all of the=
 existing DNS server IPv6 addresses?<br><br><br><br><br>3.&nbsp; Changing t=
he Default Values of the 'Lifetime' field of RDNSS and DNSSL options<br>~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~~<br><br>Firstly, this is probably also a section where pointing out that=
 the DNS resolver will make its own liveness tests/attempts to overcome the=
 sorts of packet loss mentioned.<br><br>Regarding this,<br><br>"<br>[RFC610=
6] is hereby updated as follows:<br><br>The default value of AdvRDNSSLifeti=
me and AdvDNSSLLifetime MUST be<br>at least 10*MaxRtrAdvInterval so that th=
e probability of hosts<br>receiving unsolicited Router Advertisements is in=
creased."<br><br><br><br>I'm in two minds. On the one hand, I like the idea=
 of having an automated default that is relative to the perceived level of =
packet loss that might occur. On the other hand, as before, Router Lifetime=
 and its upper and lower limits are not general "whole of RA" lifetime cons=
traints or RA robustness parameters.<br><br>Perhaps the middle ground would=
 be to define a specific constant and then note that it is the 10 times the=
 value of MaxRtrAdvInterval,&nbsp; specified in RFC4861. This would allow t=
he specific constant to be changed at a later time if necessary, or allow t=
he operator to change the value, without being constrained to it being 10*M=
axRtrAdvInterval (that is, if it is defined as a formula, then in code it p=
robably wouldn't be made an independently settable parameter, it'd just be =
calculated based on the current value of MaxRtrAdvInterval).<br><br><br><br=
>4.&nbsp; Use of Router Solicitations for active Probing~~~~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br>I don't think the RDNSS and DNSSL RFC=
 should have said anything about this, as more generally, the problem is on=
e of RA robustness, independent of what particular options are in the RA. T=
heoretically, different RA options could define their own RA robustness met=
hods that could end up being incompatible with each other.<br><br>So perhap=
s it might be better to say that RA robustness is not specific to RDNSS and=
 DNSSL options, and refer to a more general mechanism, if it exists (?), re=
garding triggering RSes to seek new option values (hmm, I don't remember re=
ading anything specific about it, but perhaps that means that RA option lif=
etimes are always greater than the unsolicited RA interval to ensure option=
 lifetimes are always refreshed before they expire?)<br><br><br><br>5.&nbsp=
; Sanitize the received RDNSS/DNSSL 'Lifetime' Values~~~~~~~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br>As per above and other RA options, =
a constant upper limit would be better.<br><br><br><br><br>Regards,<br>Mark=
.<br><br><br></div> </div> </div>  </div></body></html>
------=_Part_5845418_1122128710.1429231971286--


From nobody Thu Apr 16 23:09:43 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E571ACEAB for <ipv6@ietfa.amsl.com>; Thu, 16 Apr 2015 23:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 LkX6TWggPkCm for <ipv6@ietfa.amsl.com>; Thu, 16 Apr 2015 23:09:40 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::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 E94EC1ACEA6 for <ipv6@ietf.org>; Thu, 16 Apr 2015 23:09:39 -0700 (PDT)
Received: by obfe9 with SMTP id e9so61840245obf.1 for <ipv6@ietf.org>; Thu, 16 Apr 2015 23:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=gdeLXpXdoYfPFcxzGkGdfxugRITX4AUyczj4lyiiqzQ=; b=h60vfxeTEHa8jUuBE+oXkR3ynTxYf2oFgZ8m/RHe51mCs4WoL6cnKcWUEnY4DauPs0 OZz3hqm6yhXPdVG9uEGZe7ll7OZM/+vYT+ym+WCLSNrUqEX/QKll/jdOoY8L5bqPjt5Q baG6egU8SHIYOEWuqOA75Fmcydk15zD+/uUvg5/k81d4UFaMQjDhV9V4zW7nxRkE6uGy mXHO6IcBGGdUM/9nWCFZLXcb/7AZINFLPbNPPiAUdnullJt2YmyNbQLlcwsRUjuPL91u 20OeLxeQuuvN9/ihut7olu4xFpk8ABpyRwipTgaCqUf5eAH97O95ZJvyFqsM5JF5wjU/ p3FA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=gdeLXpXdoYfPFcxzGkGdfxugRITX4AUyczj4lyiiqzQ=; b=NATsWUCnlu/xYWO5ZaBjO8x2VUwCjrIW+zYAZjXmLEg2pNJIrMPLGO5DAWBD9nhgs2 MqvpJKduXdJViF+Bw2IyaWQl4OsqeurbU097ORwRUfDtF0D1qXgBHb9qu4VQ1FD4+uT0 OH1gw4cVL33jCpq6SLtb19s56RyQG25r93JQsfyzirzqUDUzh4Hsb6y6xtiT1fiFLlmO o3FaQPq4lOcROlVBgBO0fc9b2PEkNm6LXKPUaKRjV5ceNKEgQyWwQ9ctPliBiz/02efJ lp++vUA1VQY5q/WfhsoKHRkCE4Ri2OdZ4eYsY3qA9DUk8MfeJRSA+/Rg/8enygqRtfUf JZ2g==
X-Gm-Message-State: ALoCoQl/EUI76EdWxbAElvnmWIojbTdPCs05iqFvpOj1ZDnGJ2Mu/i8U8mr6J3W2djv2TXbp8t5q
X-Received: by 10.50.4.97 with SMTP id j1mr832918igj.46.1429250978530; Thu, 16 Apr 2015 23:09:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Thu, 16 Apr 2015 23:09:18 -0700 (PDT)
In-Reply-To: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 17 Apr 2015 15:09:18 +0900
Message-ID: <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2cd4edef80e0513e56cc7
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Rnukw5VPRaml9mCtLGOvtd3pIh4>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 06:09:42 -0000

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

On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <bob.hinden@gmail.com> wrote:

>         Title           : IPv6 Neighbor Discovery Optional Unicast RS/RA
> Refresh
>         Authors         : Erik Nordmark
>                           Andrew Yourtchenko
>                           Suresh Krishnan
>

I oppose adoption of the document as it stands.

I believe that document cannot meet its stated goal of "allow the operator
to choose whether unicast RS refresh is more efficient than periodic
multicast RAs, while preserving the timely and scalable reconfiguration
capabilities that a periodic RA model provides" in the presence of legacy
hosts that do not support this specification.

The reason is as follows: as noted in section 8.2, in the presence of hosts
that do not support this specification, routers must send periodic Router
Advertisements, otherwise the "timely and scalable reconfiguration
capabilities" cannot be maintained. This mode provides no power savings
over the status quo.

The document says that the network can operate in a mode where multicast
RAs are suppressed if it is known that all hosts on the link support the
specification. However:

   1. It is impossible to know with certainty when a legacy node has joined
   the network. If a legacy host's three initial Router Solicitations are
   missed, then that host will never again send an RA, and will never get IPv6
   connectivity unless it disconnects and reconnects. In contrast, today the
   node will get IPv6 connectivity as soon as it receives a periodic RA.
   2. In general, it is impossible to know when a legacy node has
   disconnected from the network. On some link layers this might be possible
   by relying on layer 2 information (e.g., wifi association state), but that
   requires that the router also be the layer 2 access point.
   3. This mode provides no benefit unless *all* the nodes on the network
   support the specification. Given that currently 0% of nodes support it, it
   can be expected that the vast majority of networks, where the operator does
   not tightly control the details of the IPv6 implementations in the clients,
   will see no benefit.


I would support adoption on condition that if the goal cannot be met, we
either abandon the work, or we qualify it with an applicability statement
that says that unicast RS refresh should only be used in special-purpose
networks where the operator controls both the devices and the network.

Also note: the above makes the document of limited use, but not harmful.
However, I think it's harmful, because it will cause operators and device
vendors who are familiar with IPv4 and its client-initiated, pull
configuration model (i.e., DHCP) to assume that periodic RAs are not
necessary, and therefore not implement them, because things "will work"
without them. I've been asked many times, "Why do we have to listen to RAs
anyway? Can't we just wake up and refresh the information we need? That
would be easier."

Over time, relying on this mechanism will cause IPv6 to lose the "timely
and scalable reconfiguration capabilities" provided by periodic RAs that
we're trying to preserve, because the lack of those capabilities will not
cause visible problems. That model works today in IPv4, but we should bear
in mind that in IPv4 there are lots of things that we're forced to do to do
because we can't announce network configuration updates to hosts in a
timely manner. For example, we have to use VRRP because it's impossible to
change the default gateway. Sometimes we use NAT because it's impossible to
renumber. And so on.

Cheers,
Lorenzo

--001a11c2cd4edef80e0513e56cc7
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 S=
at, Mar 28, 2015 at 12:34 AM, Bob Hinden <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:bob.hinden@gmail.com" target=3D"_blank">bob.hinden@gmail.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IPv6 Neighbor Discovery Optional Unicas=
t RS/RA Refresh<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Erik=
 Nordmark<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 Andrew Yourtchenko<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 Suresh Krishnan<br></blockquote><div><br></div><div>I opp=
ose adoption of the document as it stands.</div><div><br></div><div>I belie=
ve that document cannot meet its stated goal of &quot;allow the operator to=
 choose whether unicast RS refresh is more efficient than periodic multicas=
t RAs, while preserving the timely and scalable reconfiguration capabilitie=
s that a periodic RA model provides&quot; in the presence of legacy hosts t=
hat do not support this specification.</div><div><br></div><div>The reason =
is as follows: as noted in section 8.2, in the presence of hosts that do no=
t support this specification, routers must send periodic Router Advertiseme=
nts, otherwise the &quot;timely and scalable reconfiguration capabilities&q=
uot; cannot be maintained. This mode provides no power savings over the sta=
tus quo.</div><div><br></div><div>The document says that the network can op=
erate in a mode where multicast RAs are suppressed if it is known that all =
hosts on the link support the specification. However:</div><div><ol><li>It =
is impossible to know with certainty when a legacy node has joined the netw=
ork. If a legacy host&#39;s three initial Router Solicitations are missed, =
then that host will never again send an RA, and will never get IPv6 connect=
ivity unless it disconnects and reconnects. In contrast, today the node wil=
l get IPv6 connectivity as soon as it receives a periodic RA.</li><li>In ge=
neral, it is impossible to know when a legacy node has disconnected from th=
e network. On some link layers this might be possible by relying on layer 2=
 information (e.g., wifi association state), but that requires that the rou=
ter also be the layer 2 access point.</li><li>This mode provides no benefit=
 unless *all* the nodes on the network support the specification. Given tha=
t currently 0% of nodes support it, it can be expected that the vast majori=
ty of networks, where the operator does not tightly control the details of =
the IPv6 implementations in the clients, will see no benefit.</li></ol><div=
><br></div><div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-se=
rif;font-size:small;font-style:normal;font-variant:normal;font-weight:norma=
l;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px=
;text-transform:none;white-space:normal;word-spacing:0px;background-color:r=
gb(255,255,255)"><div style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:small;font-style:normal;font-variant:normal;font-weight:norm=
al;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0p=
x;text-transform:none;white-space:normal;word-spacing:0px;background-color:=
rgb(255,255,255)"><span style=3D"color:rgb(34,34,34);font-family:arial,sans=
-serif;font-size:small;font-style:normal;font-variant:normal;font-weight:no=
rmal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:=
0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;disp=
lay:inline!important;background-color:rgb(255,255,255)">I would support ado=
ption on condition that if the goal cannot be met, we either abandon the wo=
rk, or we qualify it with an applicability statement that says that unicast=
 RS refresh should only be used in special-purpose networks where the opera=
tor controls both the devices and the network.</span></div></div><br></div>=
<div>Also note: the above makes the document of limited use, but not harmfu=
l. However, I think it&#39;s harmful, because it will cause operators and d=
evice vendors who are familiar with IPv4 and its client-initiated, pull con=
figuration model (i.e., DHCP) to assume that periodic RAs are not necessary=
, and therefore not implement them, because things &quot;will work&quot; wi=
thout them. I&#39;ve been asked many times, &quot;Why do we have to listen =
to RAs anyway? Can&#39;t we just wake up and refresh the information we nee=
d? That would be easier.&quot;<br></div><div><br class=3D"">Over time, rely=
ing on this mechanism will cause IPv6 to lose the &quot;timely and scalable=
 reconfiguration capabilities&quot; provided by periodic RAs that we&#39;re=
 trying to preserve, because the lack of those capabilities will not cause =
visible problems. That model works today in IPv4, but we should bear in min=
d that in IPv4 there are lots of things that we&#39;re forced to do to do b=
ecause we can&#39;t announce network configuration updates to hosts in a ti=
mely manner. For example, we have to use VRRP because it&#39;s impossible t=
o change the default gateway. Sometimes we use NAT because it&#39;s impossi=
ble to renumber. And so on.</div><div><br></div></div><div><div style=3D"co=
lor:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:n=
ormal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-hei=
ght:normal;text-align:start;text-indent:0px;text-transform:none;white-space=
:normal;word-spacing:0px;background-color:rgb(255,255,255)">Cheers,<br></di=
v></div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter=
-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-tr=
ansform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,2=
55,255)"><span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;fo=
nt-size:small;font-style:normal;font-variant:normal;font-weight:normal;lett=
er-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-=
transform:none;white-space:normal;word-spacing:0px;float:none;display:inlin=
e!important;background-color:rgb(255,255,255)">Lorenzo</span></div></div></=
div></div>

--001a11c2cd4edef80e0513e56cc7--


From nobody Fri Apr 17 02:03:06 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4134C1A6F5D for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 02:03:04 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDbgIibXZi3F for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 02:03:02 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C2D1A1A8A for <ipv6@ietf.org>; Fri, 17 Apr 2015 02:03:01 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 77575264272; Fri, 17 Apr 2015 11:02:59 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.41]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 4D07327C1CF; Fri, 17 Apr 2015 11:02:59 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM31.corporate.adroot.infra.ftgroup ([fe80::2cc9:4bac:7b7d:229d%19]) with mapi id 14.03.0224.002; Fri, 17 Apr 2015 11:02:59 +0200
From: <mohamed.boucadair@orange.com>
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Topic: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Index: AQHQaKOBjX187Wxu20mUlVCmvwvlnJ1RCRqw
Date: Fri, 17 Apr 2015 09:02:57 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330052FFDC7@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
In-Reply-To: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.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.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.4.17.74219
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/dXL8kcp4fFY9Btemd0NxI6IPNsc>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 09:03:04 -0000

RGVhciBjaGFpcnMsIA0KDQpJIHN1cHBvcnQgdGhlIGFkb3B0aW9uIG9mIHRoaXMgZHJhZnQuIA0K
DQpDaGVlcnMsDQpNZWQNCg0KPiAtLS0tLU1lc3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGXCoDog
aXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gRGUgbGEgcGFydCBkZSBCb2IgSGlu
ZGVuDQo+IEVudm95w6nCoDogdmVuZHJlZGkgMjcgbWFycyAyMDE1IDE2OjM0DQo+IMOAwqA6IElQ
djYgTGlzdA0KPiBDY8KgOiA2bWFuIENoYWlycw0KPiBPYmpldMKgOiA2TUFOIFdHIEFkb3B0aW9u
IENhbGw6IGRyYWZ0LW5vcmRtYXJrLTZtYW4tcnMtcmVmcmVzaC0wMQ0KPiANCj4gVGhpcyBtZXNz
YWdlIHN0YXJ0cyBhIHR3byB3ZWVrIDZNQU4gV29ya2luZyBHcm91cCBMYXN0IENhbGwgb24gYWRv
cHRpbmc6DQo+IA0KPiAgICAgICAgIFRpdGxlICAgICAgICAgICA6IElQdjYgTmVpZ2hib3IgRGlz
Y292ZXJ5IE9wdGlvbmFsIFVuaWNhc3QgUlMvUkENCj4gUmVmcmVzaA0KPiAgICAgICAgIEF1dGhv
cnMgICAgICAgICA6IEVyaWsgTm9yZG1hcmsNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICBB
bmRyZXcgWW91cnRjaGVua28NCj4gICAgICAgICAgICAgICAgICAgICAgICAgICBTdXJlc2ggS3Jp
c2huYW4NCj4gICAgICAgICBGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1ub3JkbWFyay02bWFuLXJz
LXJlZnJlc2gtMDEudHh0DQo+ICAgICAgICAgUGFnZXMgICAgICAgICAgIDogMTINCj4gICAgICAg
ICBEYXRlICAgICAgICAgICAgOiAyMDE0LTEwLTI3DQo+IA0KPiAgICAgICAgIGh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ub3JkbWFyay02bWFuLXJzLXJlZnJlc2gtMDENCj4gDQo+
IGFzIGEgd29ya2luZyBncm91cCBkb2N1bWVudC4gU3Vic3RhbnRpdmUgY29tbWVudHMgYW5kIHN0
YXRlbWVudHMgb2YNCj4gc3VwcG9ydCBmb3IgYWRvcHRpbmcgdGhpcyBkb2N1bWVudCBzaG91bGQg
YmUgZGlyZWN0ZWQgdG8gdGhlIG1haWxpbmcgbGlzdC4NCj4gRWRpdG9yaWFsIHN1Z2dlc3Rpb25z
IGNhbiBiZSBzZW50IHRvIHRoZSBhdXRob3JzLiAgVGhpcyBhZG9wdGlvbiBjYWxsIHdpbGwNCj4g
ZW5kIG9uIEFwcmlsIDEwLCAyMDE1Lg0KPiANCj4gUmVnYXJkcywNCj4gDQo+IEJvYiBIaW5kZW4g
JiBPbGUgVHLDuGFuDQoNCg==


From nobody Fri Apr 17 05:00:21 2015
Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C67A1B2B63 for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 05:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z06lRefOiHcL for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 05:00:17 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 604361B2B62 for <ipv6@ietf.org>; Fri, 17 Apr 2015 05:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13875; q=dns/txt; s=iport; t=1429272017; x=1430481617; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=P9LTM+FCbGV3mbxMuO20l6dSWws3Bd7YiXwyBFGq1e0=; b=GppuDWTySGL4EIntHmnrV5rUEz7CrK9JyOXv+7bA5W2sS8HPNRAJXMXj ruOBJ0ayUUDeb8uIWN8nj78mjB/bqK6Il+kf7ju9lt1gdTaQfOTr4zfdh Xd17UfMvZNJGx1iBlwU/n96ClZHTUAFoKwz0TlTwbLXqBje5KZWSOz3SI M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BWBAAg9TBV/4cNJK1TCoMMUlzGGAmBRQEJhgMCgVU4FAEBAQEBAQF9hCEBAQQBAQFrCxACAQg/ByEGCxQRAgQOBYgWAxENwl4NhS4BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIspgkeBWAQKSwQHgxeBFgWGK4p3iFCBTo5IhkIig29vgQKBQQEBAQ
X-IronPort-AV: E=Sophos;i="5.11,594,1422921600";  d="scan'208,217";a="142025896"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-8.cisco.com with ESMTP; 17 Apr 2015 12:00:16 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t3HC0GQS002521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 17 Apr 2015 12:00:16 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.251]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Fri, 17 Apr 2015 07:00:16 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Topic: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Thread-Index: AQHQeNUhMoMfdK0xCkavs9R66E3ZdZ1RGneI
Date: Fri, 17 Apr 2015 12:00:15 +0000
Message-ID: <07C8DB50-E741-4D81-BB43-6FE7DB258C06@cisco.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>, <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
In-Reply-To: <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_07C8DB50E7414D81BB436FE7DB258C06ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cc7XBwS9gUMHugVD7m5rcv8bRvM>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 12:00:20 -0000

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

Hi Lorenzo,


  1.  It is impossible to know with certainty when a legacy node has joined=
 the network. If a legacy host's three initial

The absence of RS-flag in RS should enable the router to identify the prese=
nce of one or more legacy nodes on the network segment.


  1.  Router Solicitations are missed, then that host will never again send=
 an RA

Ummm..you mean, router, not the host above !! :)


3. I agree, and such a scenario is well expected during the initial roll ou=
t. But that shouldn't dilute the long term benefit of this proposal, IMO.

Cheers,
Rajiv

On Apr 17, 2015, at 2:09 AM, Lorenzo Colitti <lorenzo@google.com<mailto:lor=
enzo@google.com>> wrote:

On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <bob.hinden@gmail.com<mailto:b=
ob.hinden@gmail.com>> wrote:
        Title           : IPv6 Neighbor Discovery Optional Unicast RS/RA Re=
fresh
        Authors         : Erik Nordmark
                          Andrew Yourtchenko
                          Suresh Krishnan

I oppose adoption of the document as it stands.

I believe that document cannot meet its stated goal of "allow the operator =
to choose whether unicast RS refresh is more efficient than periodic multic=
ast RAs, while preserving the timely and scalable reconfiguration capabilit=
ies that a periodic RA model provides" in the presence of legacy hosts that=
 do not support this specification.

The reason is as follows: as noted in section 8.2, in the presence of hosts=
 that do not support this specification, routers must send periodic Router =
Advertisements, otherwise the "timely and scalable reconfiguration capabili=
ties" cannot be maintained. This mode provides no power savings over the st=
atus quo.

The document says that the network can operate in a mode where multicast RA=
s are suppressed if it is known that all hosts on the link support the spec=
ification. However:

  1.  It is impossible to know with certainty when a legacy node has joined=
 the network. If a legacy host's three initial Router Solicitations are mis=
sed, then that host will never again send an RA, and will never get IPv6 co=
nnectivity unless it disconnects and reconnects. In contrast, today the nod=
e will get IPv6 connectivity as soon as it receives a periodic RA.
  2.  In general, it is impossible to know when a legacy node has disconnec=
ted from the network. On some link layers this might be possible by relying=
 on layer 2 information (e.g., wifi association state), but that requires t=
hat the router also be the layer 2 access point.
  3.  This mode provides no benefit unless *all* the nodes on the network s=
upport the specification. Given that currently 0% of nodes support it, it c=
an be expected that the vast majority of networks, where the operator does =
not tightly control the details of the IPv6 implementations in the clients,=
 will see no benefit.

I would support adoption on condition that if the goal cannot be met, we ei=
ther abandon the work, or we qualify it with an applicability statement tha=
t says that unicast RS refresh should only be used in special-purpose netwo=
rks where the operator controls both the devices and the network.

Also note: the above makes the document of limited use, but not harmful. Ho=
wever, I think it's harmful, because it will cause operators and device ven=
dors who are familiar with IPv4 and its client-initiated, pull configuratio=
n model (i.e., DHCP) to assume that periodic RAs are not necessary, and the=
refore not implement them, because things "will work" without them. I've be=
en asked many times, "Why do we have to listen to RAs anyway? Can't we just=
 wake up and refresh the information we need? That would be easier."

Over time, relying on this mechanism will cause IPv6 to lose the "timely an=
d scalable reconfiguration capabilities" provided by periodic RAs that we'r=
e trying to preserve, because the lack of those capabilities will not cause=
 visible problems. That model works today in IPv4, but we should bear in mi=
nd that in IPv4 there are lots of things that we're forced to do to do beca=
use we can't announce network configuration updates to hosts in a timely ma=
nner. For example, we have to use VRRP because it's impossible to change th=
e default gateway. Sometimes we use NAT because it's impossible to renumber=
. And so on.

Cheers,
Lorenzo
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Hi Lorenzo,</div>
<div><br>
</div>
<div>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<ol>
<li><font color=3D"#000000"><span style=3D"background-color: rgba(255, 255,=
 255, 0);">It is impossible to know with certainty when a legacy node has j=
oined the network. If a legacy host's three initial&nbsp;</span></font></li=
></ol>
</div>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>The absence of RS-flag in RS should enable the router to identify the =
presence of one or more legacy nodes on the network segment.&nbsp;<br>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<ol>
<li><font color=3D"#000000"><span style=3D"background-color: rgba(255, 255,=
 255, 0);">Router Solicitations are missed, then that host will never again=
 send an RA</span></font></li></ol>
</div>
</div>
</div>
</blockquote>
<div>Ummm..you mean, router, not the host above !! :)</div>
<div><br>
</div>
<div><br>
</div>
<div>3. I agree, and such a scenario is well expected during the initial ro=
ll out. But that shouldn't dilute the long term benefit of this proposal, I=
MO.&nbsp;</div>
<br>
Cheers,
<div>Rajiv</div>
</div>
<div><br>
On Apr 17, 2015, at 2:09 AM, Lorenzo Colitti &lt;<a href=3D"mailto:lorenzo@=
google.com">lorenzo@google.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <sp=
an dir=3D"ltr">
&lt;<a href=3D"mailto:bob.hinden@gmail.com" target=3D"_blank">bob.hinden@gm=
ail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
&nbsp; &nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:=
 IPv6 Neighbor Discovery Optional Unicast RS/RA Refresh<br>
&nbsp; &nbsp; &nbsp; &nbsp; Authors&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Erik=
 Nordmark<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; Andrew Yourtchenko<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; Suresh Krishnan<br>
</blockquote>
<div><br>
</div>
<div>I oppose adoption of the document as it stands.</div>
<div><br>
</div>
<div>I believe that document cannot meet its stated goal of &quot;allow the=
 operator to choose whether unicast RS refresh is more efficient than perio=
dic multicast RAs, while preserving the timely and scalable reconfiguration=
 capabilities that a periodic RA model
 provides&quot; in the presence of legacy hosts that do not support this sp=
ecification.</div>
<div><br>
</div>
<div>The reason is as follows: as noted in section 8.2, in the presence of =
hosts that do not support this specification, routers must send periodic Ro=
uter Advertisements, otherwise the &quot;timely and scalable reconfiguratio=
n capabilities&quot; cannot be maintained.
 This mode provides no power savings over the status quo.</div>
<div><br>
</div>
<div>The document says that the network can operate in a mode where multica=
st RAs are suppressed if it is known that all hosts on the link support the=
 specification. However:</div>
<div>
<ol>
<li>It is impossible to know with certainty when a legacy node has joined t=
he network. If a legacy host's three initial Router Solicitations are misse=
d, then that host will never again send an RA, and will never get IPv6 conn=
ectivity unless it disconnects and
 reconnects. In contrast, today the node will get IPv6 connectivity as soon=
 as it receives a periodic RA.</li><li>In general, it is impossible to know=
 when a legacy node has disconnected from the network. On some link layers =
this might be possible by relying on layer 2 information (e.g., wifi associ=
ation state), but that requires that the router also be the layer 2
 access point.</li><li>This mode provides no benefit unless *all* the nodes=
 on the network support the specification. Given that currently 0% of nodes=
 support it, it can be expected that the vast majority of networks, where t=
he operator does not tightly control the details of
 the IPv6 implementations in the clients, will see no benefit.</li></ol>
<div><br>
</div>
<div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing=
:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"=
>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing=
:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"=
>
<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:s=
mall;font-style:normal;font-variant:normal;font-weight:normal;letter-spacin=
g:normal;line-height:normal;text-align:start;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;float:none;display:inline!importa=
nt;background-color:rgb(255,255,255)">I
 would support adoption on condition that if the goal cannot be met, we eit=
her abandon the work, or we qualify it with an applicability statement that=
 says that unicast RS refresh should only be used in special-purpose networ=
ks where the operator controls both
 the devices and the network.</span></div>
</div>
<br>
</div>
<div>Also note: the above makes the document of limited use, but not harmfu=
l. However, I think it's harmful, because it will cause operators and devic=
e vendors who are familiar with IPv4 and its client-initiated, pull configu=
ration model (i.e., DHCP) to assume
 that periodic RAs are not necessary, and therefore not implement them, bec=
ause things &quot;will work&quot; without them. I've been asked many times,=
 &quot;Why do we have to listen to RAs anyway? Can't we just wake up and re=
fresh the information we need? That would be easier.&quot;<br>
</div>
<div><br class=3D"">
Over time, relying on this mechanism will cause IPv6 to lose the &quot;time=
ly and scalable reconfiguration capabilities&quot; provided by periodic RAs=
 that we're trying to preserve, because the lack of those capabilities will=
 not cause visible problems. That model works
 today in IPv4, but we should bear in mind that in IPv4 there are lots of t=
hings that we're forced to do to do because we can't announce network confi=
guration updates to hosts in a timely manner. For example, we have to use V=
RRP because it's impossible to change
 the default gateway. Sometimes we use NAT because it's impossible to renum=
ber. And so on.</div>
<div><br>
</div>
</div>
<div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing=
:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"=
>
Cheers,<br>
</div>
</div>
<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing=
:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"=
>
<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:s=
mall;font-style:normal;font-variant:normal;font-weight:normal;letter-spacin=
g:normal;line-height:normal;text-align:start;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;float:none;display:inline!importa=
nt;background-color:rgb(255,255,255)">Lorenzo</span></div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>----------------------------------------------------------------=
----</span><br>
<span>IETF IPv6 working group mailing list</span><br>
<span><a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a></span><br>
<span>Administrative Requests: <a href=3D"https://www.ietf.org/mailman/list=
info/ipv6">
https://www.ietf.org/mailman/listinfo/ipv6</a></span><br>
<span>--------------------------------------------------------------------<=
/span><br>
</div>
</blockquote>
</body>
</html>

--_000_07C8DB50E7414D81BB436FE7DB258C06ciscocom_--


From nobody Fri Apr 17 10:36:44 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7CD61A9089 for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 10:36:42 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F_jcVqV7gzUW for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 10:36:41 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 760101A9091 for <ipv6@ietf.org>; Fri, 17 Apr 2015 10:36:41 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3HHab8G021494 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Apr 2015 10:36:37 -0700
Message-ID: <553144A5.3040608@acm.org>
Date: Fri, 17 Apr 2015 10:36:37 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
In-Reply-To: <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVaZfWDGxkQ9PBCLvkRhfvhjmezGBIMP57rEjgM7rxWsQetvMAUugNkPS9K2IVZ2PwXXSTmisJrABX9OxuLLh9Ws
X-Sonic-ID: C;KrKSTCjl5BGYK7O3ym/e/Q== M;JMuiTCjl5BGYK7O3ym/e/Q==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5Rl6YRnVH8N057gbd5Eb1N9vkS4>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 17:36:43 -0000

[Sorry for the duplicate - corrected the from address]

On 4/16/15 11:09 PM, Lorenzo Colitti wrote:
> On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <bob.hinden@gmail.com 
> <mailto:bob.hinden@gmail.com>> wrote:
>
>           Title           : IPv6 Neighbor Discovery Optional Unicast
>     RS/RA Refresh
>             Authors         : Erik Nordmark
>                               Andrew Yourtchenko
>                               Suresh Krishnan
>
>
> I oppose adoption of the document as it stands.
>
> I believe that document cannot meet its stated goal of "allow the 
> operator to choose whether unicast RS refresh is more efficient than 
> periodic multicast RAs, while preserving the timely and scalable 
> reconfiguration capabilities that a periodic RA model provides" in the 
> presence of legacy hosts that do not support this specification.
>
> The reason is as follows: as noted in section 8.2, in the presence of 
> hosts that do not support this specification, routers must send 
> periodic Router Advertisements, otherwise the "timely and scalable 
> reconfiguration capabilities" cannot be maintained. This mode provides 
> no power savings over the status quo.
Lorenzo,

I think you must be making some unstated assumptions in coming to that 
conclusion, because it does not match my conclusion.

This specification allows a host to go to sleep and turn of its radio, 
which includes not being awoken by any multicast RA, and when it wakes 
up it can send a RS to refresh the information that might have changed 
while it was asleep. That provides power savings for that host.


>
> The document says that the network can operate in a mode where 
> multicast RAs are suppressed if it is known that all hosts on the link 
> support the specification. However:
>
>  1. It is impossible to know with certainty when a legacy node has
>     joined the network. If a legacy host's three initial Router
>     Solicitations are missed, then that host will never again send an
>     RA, and will never get IPv6 connectivity unless it disconnects and
>     reconnects. In contrast, today the node will get IPv6 connectivity
>     as soon as it receives a periodic RA.
>

As I pointed out in some earlier email, a host which is subject to 
packet loss so that the initial RAs are lost does not see any useful 
service. Your "as soon as" is currently as bad as 30 minutes (and 
separate discussions about MaxRtrAdvInterval might increase this to 6 
hours). I don't know which host will wait for that long. Thus I don't 
think you can claim that legacy hosts work under such packet loss 
conditions.

Regards,
     Erik

>  1. In general, it is impossible to know when a legacy node has
>     disconnected from the network. On some link layers this might be
>     possible by relying on layer 2 information (e.g., wifi association
>     state), but that requires that the router also be the layer 2
>     access point.
>  2. This mode provides no benefit unless *all* the nodes on the
>     network support the specification. Given that currently 0% of
>     nodes support it, it can be expected that the vast majority of
>     networks, where the operator does not tightly control the details
>     of the IPv6 implementations in the clients, will see no benefit.
>
>
> I would support adoption on condition that if the goal cannot be met, 
> we either abandon the work, or we qualify it with an applicability 
> statement that says that unicast RS refresh should only be used in 
> special-purpose networks where the operator controls both the devices 
> and the network.
>
> Also note: the above makes the document of limited use, but not 
> harmful. However, I think it's harmful, because it will cause 
> operators and device vendors who are familiar with IPv4 and its 
> client-initiated, pull configuration model (i.e., DHCP) to assume that 
> periodic RAs are not necessary, and therefore not implement them, 
> because things "will work" without them. I've been asked many times, 
> "Why do we have to listen to RAs anyway? Can't we just wake up and 
> refresh the information we need? That would be easier."
>
> Over time, relying on this mechanism will cause IPv6 to lose the 
> "timely and scalable reconfiguration capabilities" provided by 
> periodic RAs that we're trying to preserve, because the lack of those 
> capabilities will not cause visible problems. That model works today 
> in IPv4, but we should bear in mind that in IPv4 there are lots of 
> things that we're forced to do to do because we can't announce network 
> configuration updates to hosts in a timely manner. For example, we 
> have to use VRRP because it's impossible to change the default 
> gateway. Sometimes we use NAT because it's impossible to renumber. And 
> so on.
>
> Cheers,
> Lorenzo
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Apr 17 10:53:12 2015
Return-Path: <nordmark@sonic.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55B31A904F for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 10:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ptwF26ypcsGH for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 10:34:11 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 D3DA41A904D for <ipv6@ietf.org>; Fri, 17 Apr 2015 10:34:11 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3HHY6Ya015813 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Apr 2015 10:34:06 -0700
Message-ID: <5531440E.5060102@sonic.net>
Date: Fri, 17 Apr 2015 10:34:06 -0700
From: Erik Nordmark <nordmark@sonic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
In-Reply-To: <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbYAI+IPu5C52qrICpO8fjZ2UBWYP74O7hzWh/pPycIPRwcg/bTLOp2pp3zyeGd/LMUy3zEtOpjuGcV7CPYBKhL
X-Sonic-ID: C;0rnO8ifl5BGInc/lyiZxWA== M;XGXk8ifl5BGInc/lyiZxWA==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EktnuIhk6LipoPy-ULH_4Z_myFA>
X-Mailman-Approved-At: Fri, 17 Apr 2015 10:53:10 -0700
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 17:34:13 -0000

On 4/16/15 11:09 PM, Lorenzo Colitti wrote:
> On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <bob.hinden@gmail.com 
> <mailto:bob.hinden@gmail.com>> wrote:
>
>           Title           : IPv6 Neighbor Discovery Optional Unicast
>     RS/RA Refresh
>             Authors         : Erik Nordmark
>                               Andrew Yourtchenko
>                               Suresh Krishnan
>
>
> I oppose adoption of the document as it stands.
>
> I believe that document cannot meet its stated goal of "allow the 
> operator to choose whether unicast RS refresh is more efficient than 
> periodic multicast RAs, while preserving the timely and scalable 
> reconfiguration capabilities that a periodic RA model provides" in the 
> presence of legacy hosts that do not support this specification.
>
> The reason is as follows: as noted in section 8.2, in the presence of 
> hosts that do not support this specification, routers must send 
> periodic Router Advertisements, otherwise the "timely and scalable 
> reconfiguration capabilities" cannot be maintained. This mode provides 
> no power savings over the status quo.
Lorenzo,

I think you must be making some unstated assumptions in coming to that 
conclusion, because it does not match my conclusion.

This specification allows a host to go to sleep and turn of its radio, 
which includes not being awoken by any multicast RA, and when it wakes 
up it can send a RS to refresh the information that might have changed 
while it was asleep. That provides power savings for that host.


>
> The document says that the network can operate in a mode where 
> multicast RAs are suppressed if it is known that all hosts on the link 
> support the specification. However:
>
>  1. It is impossible to know with certainty when a legacy node has
>     joined the network. If a legacy host's three initial Router
>     Solicitations are missed, then that host will never again send an
>     RA, and will never get IPv6 connectivity unless it disconnects and
>     reconnects. In contrast, today the node will get IPv6 connectivity
>     as soon as it receives a periodic RA.
>

As I pointed out in some earlier email, a host which is subject to 
packet loss so that the initial RAs are lost does not see any useful 
service. Your "as soon as" is currently as bad as 30 minutes (and 
separate discussions about MaxRtrAdvInterval might increase this to 6 
hours). I don't know which host will wait for that long. Thus I don't 
think you can claim that legacy hosts work under such packet loss 
conditions.

Regards,
     Erik

>  1. In general, it is impossible to know when a legacy node has
>     disconnected from the network. On some link layers this might be
>     possible by relying on layer 2 information (e.g., wifi association
>     state), but that requires that the router also be the layer 2
>     access point.
>  2. This mode provides no benefit unless *all* the nodes on the
>     network support the specification. Given that currently 0% of
>     nodes support it, it can be expected that the vast majority of
>     networks, where the operator does not tightly control the details
>     of the IPv6 implementations in the clients, will see no benefit.
>
>
> I would support adoption on condition that if the goal cannot be met, 
> we either abandon the work, or we qualify it with an applicability 
> statement that says that unicast RS refresh should only be used in 
> special-purpose networks where the operator controls both the devices 
> and the network.
>
> Also note: the above makes the document of limited use, but not 
> harmful. However, I think it's harmful, because it will cause 
> operators and device vendors who are familiar with IPv4 and its 
> client-initiated, pull configuration model (i.e., DHCP) to assume that 
> periodic RAs are not necessary, and therefore not implement them, 
> because things "will work" without them. I've been asked many times, 
> "Why do we have to listen to RAs anyway? Can't we just wake up and 
> refresh the information we need? That would be easier."
>
> Over time, relying on this mechanism will cause IPv6 to lose the 
> "timely and scalable reconfiguration capabilities" provided by 
> periodic RAs that we're trying to preserve, because the lack of those 
> capabilities will not cause visible problems. That model works today 
> in IPv4, but we should bear in mind that in IPv4 there are lots of 
> things that we're forced to do to do because we can't announce network 
> configuration updates to hosts in a timely manner. For example, we 
> have to use VRRP because it's impossible to change the default 
> gateway. Sometimes we use NAT because it's impossible to renumber. And 
> so on.
>
> Cheers,
> Lorenzo
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Apr 17 16:08:07 2015
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3F01B30D3 for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 16:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WmAJSWcVr4pr for <ipv6@ietfa.amsl.com>; Fri, 17 Apr 2015 16:08:01 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1572F1B30D2 for <6man@ietf.org>; Fri, 17 Apr 2015 16:08:01 -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)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id B2A9C1FCAB8 for <6man@ietf.org>; Fri, 17 Apr 2015 23:07:57 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 22867160058 for <6man@ietf.org>; Fri, 17 Apr 2015 23:08:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id EF305160083 for <6man@ietf.org>; Fri, 17 Apr 2015 23:08: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 YDW6ZjoXSwvh for <6man@ietf.org>; Fri, 17 Apr 2015 23:08:00 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 7252F160058 for <6man@ietf.org>; Fri, 17 Apr 2015 23:08:00 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 072B52D31138 for <6man@ietf.org>; Sat, 18 Apr 2015 08:38:24 +1000 (EST)
To: 6man@ietf.org
From: Mark Andrews <marka@isc.org>
Subject: Re: Some thoughts/comments on draft-gont-6man-slaac-dns-config-issues-01
Date: Sat, 18 Apr 2015 08:38:23 +1000
Message-Id: <20150417223824.072B52D31138@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-S6xYCVUtODpNo4scO3xoE1Cd4Q>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 23:08:05 -0000

------- Forwarded Message

To: Fernando Gont <fgont@si6networks.com>
Cc: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>,
    "pavlix@pavlix.net" <pavlix@pavlix.net>,
    "liushucheng@huawei.com" <liushucheng@huawei.com>
From: Mark Andrews <marka@isc.org>
References: <1059223520.4994623.1429165351434.JavaMail.yahoo@mail.yahoo.com> <55304CD4.7040902@si6networks.com>
Subject: Re: Some thoughts/comments on draft-gont-6man-slaac-dns-config-issues-01
In-reply-to: Your message of "Thu, 16 Apr 2015 20:59:16 -0300."
             <55304CD4.7040902@si6networks.com>
Date: Fri, 17 Apr 2015 10:33:48 +1000


On DNS server lifetimes there are several senarios to consider
depending upon which servers are being advertised.

1. Servers that are the embeded in the router or are proxied
	by the router.
2. Servers that are internal to the network but are not the
	router.
3. Servers that are external to the network and have a restricted
	client population (think ISP limited to its address
	ranges).
4. Servers that are external and don't have a restricted
	client population (think Google's public recursive
	servers).
5. a mixture of the above.

For 2 and 4 lifetime is totally independent of router lifetime.

For 1 and 3 the servers are only good as long as the router is up
and if you have a alternate exit route it would be better to not
use nameservers advertised by the router.  This is also a common
senario in homes.

That said I would just have the node update the servers based on a
merge of the available servers (if there are multiple routers) /
new set of servers and not remove them when the router goes down.

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

------- End of Forwarded Message


From nobody Sun Apr 19 02:36:39 2015
Return-Path: <loganaden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F971A0015 for <ipv6@ietfa.amsl.com>; Sun, 19 Apr 2015 02:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.199
X-Spam-Level: 
X-Spam-Status: No, score=0.199 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 ybGlc2x7t5VJ for <ipv6@ietfa.amsl.com>; Sun, 19 Apr 2015 02:36:36 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001: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 AC0CD1A0006 for <ipv6@ietf.org>; Sun, 19 Apr 2015 02:36:36 -0700 (PDT)
Received: by iget9 with SMTP id t9so49387988ige.1 for <ipv6@ietf.org>; Sun, 19 Apr 2015 02:36:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=lgZe8esIvMJoA/ZVtrsMUAW889a7e3+P0AW1VHj99YA=; b=N8N84RtimNVEqm/xcXHIyyHiuLR2PmRMfHc5p866ji6bqKDzbVKv19KMcdHlEX3840 CqUCF0IomJz5IsWHmyZLieTE+cfr1Smb62zw8ryLFfzviDPjP/d3C9LUmdbgMk1+Ngtq o6gNgaLf05rtOPVibugE+FwAnCtjwDoBSUpmGIzVeJgv88b0ILjzSzKw1lHFMFG9OzYJ 0Na4FrexdDO9ZT+VVnypZaujz72bFasObpatkZvrgHnUBH0A2xS+QiX/gYQoq4p19sv3 dZ7q5MSjv7GQQYkqAh4tuAprVjtAjOp5BCftxETQjq9kwzM1s7dEB15k8pfuHRdBozdx rECQ==
MIME-Version: 1.0
X-Received: by 10.107.160.202 with SMTP id j193mr4971956ioe.43.1429436196199;  Sun, 19 Apr 2015 02:36:36 -0700 (PDT)
Received: by 10.50.25.231 with HTTP; Sun, 19 Apr 2015 02:36:36 -0700 (PDT)
In-Reply-To: <CAJE_bqfsPvhwqj15O+_Cm07ZkD0vXFPuk4R-Rexr28FZdYbknQ@mail.gmail.com>
References: <CAOp4FwQ5M2iPpZTMN-f-RmuZ1-+KVCBfkpg1WNjhc2trZH3NOg@mail.gmail.com> <D13B670F.5C518%hesham@elevatemobile.com> <CAOp4FwQ+VPYygwL2qY7NWT6hPw+d1=rm1_rSBA4ir3CnegCsSw@mail.gmail.com> <55155589.3030503@gmail.com> <CAOp4FwTi2MTNq+e0ogy65-ZO+BbJwNKa1PzV-MLV2XmxKrSKqQ@mail.gmail.com> <9F34D3EE-E628-4727-A863-544E44114D53@gmail.com> <CAJE_bqe9kj1wfGAwDR0yYd2Dx8dS2bdAKzFhBDe2UFDc73kLCw@mail.gmail.com> <CAOp4FwR7pPoz7KcKAWcOnReNgmrbbM+HJTniQ_-QWmcA7L3jtQ@mail.gmail.com> <CAJE_bqfsPvhwqj15O+_Cm07ZkD0vXFPuk4R-Rexr28FZdYbknQ@mail.gmail.com>
Date: Sun, 19 Apr 2015 09:36:36 +0000
Message-ID: <CAOp4FwRh79kq0SX4V5sZbdyT5FZ16qzeqEZs7Cb5TJwqAe7rDQ@mail.gmail.com>
Subject: Re: Updating RFC 4861
From: Loganaden Velvindron <loganaden@gmail.com>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4OfZ709pFpLllIaWp9N1lPrgTDQ>
Cc: Bob Hinden <bob.hinden@gmail.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Apr 2015 09:36:38 -0000

On Mon, Mar 30, 2015 at 4:50 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinm=
ei@wide.ad.jp> wrote:
> At Fri, 27 Mar 2015 15:43:30 +0000,
> Loganaden Velvindron <loganaden@gmail.com> wrote:
>
>> > I'm not sure if we want to include a specific validation on the
>> > received value of Cur Hop Limit in the protocol specification.  I've
>> > assumed that the general sense is that an on-link attacker can
>> > generally perform various evil things (whose severity vary) and we
>> > address a specific threat in the base protocol spec only when it's
>> > considered to be too severe.  An example of this is the "too short a
>> > valid lifetime attack".  In that sense, sending too small a Cur Hop
>> > Limit value looks quite minor to me.
>>
>> It is possible to cause a denial of service attack on a link-local
>> interface. A patch has been queued for inclusion in Linux:
>>
>> http://www.spinics.net/lists/netdev/msg322361.html
>>
>> I think that since we have running code, and and upcoming CVE, we
>> might want the standard to reflect what's currently happening in
>> production operating systems.
>
> The "denial of service attack" in this case is to make a certain set
> of off-link destinations unreachable, right?  If I were an attacker, I
> could achieve that goal by sending RAs with valid routers's source
> addresses and with the router lifetime being 0.  So, again personally,
> I'm not really convinced whether we need this "defense" in the first
> place - if we really want to avoid this class of "attacks" (which are
> annoying but relatively minor and can only be done by an on-link
> attacker - although I can imagine some cases where it can really
> matter), I'd rather rely on a more comprehensive measure such as SEND
> or RA guard, depending on requirement details (whether it has to work
> perfectly even if hard to deploy, or we need something reasonably
> workable and deployable).  And so I personally don't buy then argument
> that we need to tweak the protocol just because some implementors
> wanted to do something deviant.

Up to now, we have FreeBSD, Linux and also Illumnos who have all
implemented that tweak.


>
> --
> JINMEI, Tatuya


From nobody Mon Apr 20 06:54:52 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53251B2BB3 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 06:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 lwRkGqDSjQmN for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 06:54:49 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001: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 7CC9D1B2BB2 for <ipv6@ietf.org>; Mon, 20 Apr 2015 06:54:49 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so59465001igb.1 for <ipv6@ietf.org>; Mon, 20 Apr 2015 06:54:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qFm5nCs5YVcZyJ/UWMFnaktAF8GBP1OaH0+M+PWdDqI=; b=oVu62qPgRvGG1dHtuHKuQRNwxlrROsNRuagNCf9e7yCyXKB+c2bEURE7pfZvqKubyS b0ss5JGY9lN84CdAOTtcWmZI4ECWT4VquhFTGnBdZTLi2u90VpvI6EWH9x0HuhqOmaYG ArswnjXiqiZH6WjvZve/ndpLPCYjIpw5FIoVr6Ro/caAQmIgz8d9K7dxf6p/DqOBdbe5 tPTGbqEQ9IfZlm0bBY9qba6m2KXnV3bWFK1bEYK6swxhVoSZ140YLFfwCiDHpFAi1V/s xe7oUK6wBvzxMHONFN0JjGpxqc2kY3BVHMGVa7mKWi4aslfEcpL1cGwC7GpIjoRHrLsu +QqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=qFm5nCs5YVcZyJ/UWMFnaktAF8GBP1OaH0+M+PWdDqI=; b=RDvuzLX1orpjCOQ9Sq296lwXl/FGCIvY4F+pPgRYa9P6+gxZrPw04K0yg4Xy19TMVo HbK66mlWERUITNy7r0EjGgPW7TrSnoMTJyRf2OQGmTfC7U4spK1sy2HTXya+QHcJjE8A 7lLiDW6t1XavWFiTpU28S5ZvQzBGfotEdPsmM6L2Cz5QCpvJRySzBo4Xs6qHXRA9urg8 eDULC3LxBWxnNas6/WvBBb7PXowgzhsfPIHH0UeAbCk8PPlQbMopjS3B1f/5IdT+nGpX Hv0mXslFruiIR+4IkDfrylj+Cmf2bFsIgkgDhQ2w6k9fRtq5Glfb7ExqZ4rqty8GDRoO e+1Q==
X-Gm-Message-State: ALoCoQmGAOgoOidnsbyd7A/VZ8uxQGtIrb9joE2LYhS3zCyyDQee5jOtFfz8rhwAZPL9f8E+jfhP
X-Received: by 10.50.4.97 with SMTP id j1mr20976505igj.46.1429538088848; Mon, 20 Apr 2015 06:54:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Mon, 20 Apr 2015 06:54:28 -0700 (PDT)
In-Reply-To: <5531440E.5060102@sonic.net>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 20 Apr 2015 22:54:28 +0900
Message-ID: <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Erik Nordmark <nordmark@sonic.net>
Content-Type: multipart/alternative; boundary=001a11c2cd4efac6b205142845cc
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/F_9YmjXbvv2J78_G67iPc6OuSuY>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Apr 2015 13:54:51 -0000

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

On Sat, Apr 18, 2015 at 2:34 AM, Erik Nordmark <nordmark@sonic.net> wrote:

> The reason is as follows: as noted in section 8.2, in the presence of
>> hosts that do not support this specification, routers must send periodic
>> Router Advertisements, otherwise the "timely and scalable reconfiguration
>> capabilities" cannot be maintained. This mode provides no power savings
>> over the status quo.
>>
> Lorenzo,
>
> I think you must be making some unstated assumptions in coming to that
> conclusion, because it does not match my conclusion.
>
> This specification allows a host to go to sleep and turn of its radio,
> which includes not being awoken by any multicast RA, and when it wakes up
> it can send a RS to refresh the information that might have changed while
> it was asleep. That provides power savings for that host.
>

But then the "timely and scalable reconfiguration capabilities" cannot be
maintained. The network can't tell that host about any new information,
because that host won't receive it. The host will only receive it when it
wakes up next.


> The document says that the network can operate in a mode where multicast
>> RAs are suppressed if it is known that all hosts on the link support the
>> specification. However:
>>
>>  1. It is impossible to know with certainty when a legacy node has
>>     joined the network. If a legacy host's three initial Router
>>     Solicitations are missed, then that host will never again send an
>>     RA, and will never get IPv6 connectivity unless it disconnects and
>>     reconnects. In contrast, today the node will get IPv6 connectivity
>>     as soon as it receives a periodic RA.
>>
>>
> As I pointed out in some earlier email, a host which is subject to packet
> loss so that the initial RAs are lost does not see any useful service. Your
> "as soon as" is currently as bad as 30 minutes (and separate discussions
> about MaxRtrAdvInterval might increase this to 6 hours). I don't know which
> host will wait for that long. Thus I don't think you can claim that legacy
> hosts work under such packet loss conditions.
>

It depends how frequent the RAs are. In general purpose networks, they
might be more frequent. Also, any node joining may cause a solicited
multicast RA. Depending on the application, "after 10 minutes" may be a lot
better than "never".

What about points #2 and #3?

--001a11c2cd4efac6b205142845cc
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 S=
at, Apr 18, 2015 at 2:34 AM, Erik Nordmark <span dir=3D"ltr">&lt;<a href=3D=
"mailto:nordmark@sonic.net" target=3D"_blank">nordmark@sonic.net</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex"><span class=3D""><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">The reaso=
n is as follows: as noted in section 8.2, in the presence of hosts that do =
not support this specification, routers must send periodic Router Advertise=
ments, otherwise the &quot;timely and scalable reconfiguration capabilities=
&quot; cannot be maintained. This mode provides no power savings over the s=
tatus quo.<br>
</blockquote></span>
Lorenzo,<br>
<br>
I think you must be making some unstated assumptions in coming to that conc=
lusion, because it does not match my conclusion.<br>
<br>
This specification allows a host to go to sleep and turn of its radio, whic=
h includes not being awoken by any multicast RA, and when it wakes up it ca=
n send a RS to refresh the information that might have changed while it was=
 asleep. That provides power savings for that host.<br></blockquote><div><b=
r></div><div>But then the &quot;timely and scalable reconfiguration capabil=
ities&quot; cannot be maintained. The network can&#39;t tell that host abou=
t any new information, because that host won&#39;t receive it. The host wil=
l only receive it when it wakes up next.</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:so=
lid;padding-left:1ex"><span class=3D"">
The document says that the network can operate in a mode where multicast RA=
s are suppressed if it is known that all hosts on the link support the spec=
ification. However:<br>
<br></span>
=C2=A01. It is impossible to know with certainty when a legacy node has<spa=
n class=3D""><br>
=C2=A0 =C2=A0 joined the network. If a legacy host&#39;s three initial Rout=
er<br>
=C2=A0 =C2=A0 Solicitations are missed, then that host will never again sen=
d an<br>
=C2=A0 =C2=A0 RA, and will never get IPv6 connectivity unless it disconnect=
s and<br>
=C2=A0 =C2=A0 reconnects. In contrast, today the node will get IPv6 connect=
ivity<br>
=C2=A0 =C2=A0 as soon as it receives a periodic RA.<br>
<br>
</span></blockquote>
<br>
As I pointed out in some earlier email, a host which is subject to packet l=
oss so that the initial RAs are lost does not see any useful service. Your =
&quot;as soon as&quot; is currently as bad as 30 minutes (and separate disc=
ussions about MaxRtrAdvInterval might increase this to 6 hours). I don&#39;=
t know which host will wait for that long. Thus I don&#39;t think you can c=
laim that legacy hosts work under such packet loss conditions.<br></blockqu=
ote><div><br></div><div>It depends how frequent the RAs are. In general pur=
pose networks, they might be more frequent. Also, any node joining may caus=
e a solicited multicast RA. Depending on the application, &quot;after 10 mi=
nutes&quot; may be a lot better than &quot;never&quot;.</div><div><br></div=
><div>What about points #2 and #3?</div></div></div></div>

--001a11c2cd4efac6b205142845cc--


From nobody Mon Apr 20 10:42:00 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1CA1B2C71 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 10:41:59 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u7nS2BZXG66D for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 10:41:58 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 4044F1B2C6C for <ipv6@ietf.org>; Mon, 20 Apr 2015 10:41:58 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3KHfqCJ021298 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 20 Apr 2015 10:41:53 -0700
Message-ID: <55353A60.1030701@acm.org>
Date: Mon, 20 Apr 2015 10:41:52 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com>
In-Reply-To: <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVajVdPKl+FMrlQapneY4gAlRHB3RS49sDQzIfmEJpqZV2IzpEhdQub5gzuZSs+12HXNIDmTNVtdkvj2E31o/kzC
X-Sonic-ID: C;5ICJh4Tn5BG/h8/lyiZxWA== M;rtY7iITn5BG/h8/lyiZxWA==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_pTAnihh1RsXBP5Xe4N0Ql7V0vA>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Apr 2015 17:41:59 -0000

On 4/20/15 6:54 AM, Lorenzo Colitti wrote:
> But then the "timely and scalable reconfiguration capabilities" cannot 
> be maintained. The network can't tell that host about any new 
> information, because that host won't receive it. The host will only 
> receive it when it wakes up next.
The host will take no action on any state until it wakes up. "timely" 
implies that hosts do not take any actions on stale state, and with RS 
refresh they would not. Hence it is very "timely".

Note that without RS refresh hosts can take action on stale state if the 
packet loss experienced by the RAs is such that they miss e.g., the RAs 
that set the preferred lifetime for a prefix to zero, or set the default 
router lifetime to zero. Thus RFC 4861 operates in a probabilistic mode 
- which made sense when all networks were wires and one could assume the 
packet loss were independent events. Walking out of range of a radio 
does not result in independent events.

Thus using RS refresh makes the "timely" work better than in RFC 4861.

> It depends how frequent the RAs are. In general purpose networks, they 
> might be more frequent. Also, any node joining may cause a solicited 
> multicast RA. Depending on the application, "after 10 minutes" may be 
> a lot better than "never".
For the network deployments where frequency of RAs is a concern, the 
desire seems to be to increase the time.
If you read e.g. section 5.1 in 
draft-yourtchenko-colitti-nd-reduce-multicast you'll see that.
Those are also the networks where resilient-RS makes sense.

>
> What about points #2 and #3?
I think this email thread should about WG adoption and not WG last call 
or even about WG discussion.
Are you arguing that all your points in the draft need to be addressed 
to your satisfaction before it can even become a WG draft?
That isn't how an IETF working group is supposed to operate.


FWIW your #2 was a statement of fact, but not clear how it is relevant 
to the discussion. Seems to be related to your assumption that any 
multicast RA makes this null and void, which is incorrect.
#3 was AFAICT a restatement of your conclusion based on some unstated 
assumptions. I already tried to guess at that unstated assumption in my 
first respond and I responded based on that. Was my guess wrong? Did I 
you make some other unstated assumptions?

Regards,
    Erik




From nobody Mon Apr 20 13:59:49 2015
Return-Path: <warren@kumari.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7565E1B31AF for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 13:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDUf29LFUVit for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 13:59:46 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.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 E6CB11B31B9 for <ipv6@ietf.org>; Mon, 20 Apr 2015 13:59:43 -0700 (PDT)
Received: by widdi4 with SMTP id di4so115049629wid.0 for <ipv6@ietf.org>; Mon, 20 Apr 2015 13:59:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XUfU3EEwRSrfOnUrp8OBcQ68edEE0krkMLrE7lWocX8=; b=g/2bfDbgXlg2hfX+Qkr1IjYF/3ATtH7M1DeFI91URFCgyvmE/OPCXAS6gviai/PO7m lKSNyIarB5TZHd4gwriUoN+HMYLdcZhV+vmYioXynQ0q4EGt0wEVl7g7jujHI9+1hbHb Ml3NAMT/+bGmsOsPK0L9i8sdEoFIf8TxZn7zgM9wwVtxsECT+iRE/D9h56E28cUxyLT9 3XBlHDUKJJlHgpU4c5SdlTqWmMYkkn4wK6HtDXruEz46h6LIvYQUru0NJsf6lAyV0KBv o7BVrMlC7C28V3GNZ7gDLBueJrlrIVfnuC0uRMA/TwbqEsY9nlcX3l2fMnhtbz0uxEID VRPA==
X-Gm-Message-State: ALoCoQkwEE6VXY1rZNeOLocRs7TsN46/ntonMu62EdDDwEbYQRwmseaSnCe/6ehOTWpyPFYBk3Rv
MIME-Version: 1.0
X-Received: by 10.194.104.201 with SMTP id gg9mr33692672wjb.113.1429563582662;  Mon, 20 Apr 2015 13:59:42 -0700 (PDT)
Received: by 10.194.47.36 with HTTP; Mon, 20 Apr 2015 13:59:42 -0700 (PDT)
In-Reply-To: <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com>
Date: Mon, 20 Apr 2015 16:59:42 -0400
Message-ID: <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
From: Warren Kumari <warren@kumari.net>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/s9peYwfpeKfMqd2qxY5k1l06oMY>
Cc: draft-wkumari-dhc-capport.shepherd@ietf.org, olafur@cloudflare.com, Paul Ebersman <ebersman-ietf@dragon.net>, draft-wkumari-dhc-capport.ad@ietf.org, draft-wkumari-dhc-capport@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>, Steve Sheng <steve.sheng@icann.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Apr 2015 20:59:47 -0000

So, I'm having a hard time trying to convert these comments into
actual text that I can put in the document. If people have anything
specific that they would like incorporated, please send text.

The purpose of this document is simply to inform the client that it is
behind a CP **and how to reach that CaptivePortal**.
A client connecting to a new network has to assume that there may be a
CP present, and perform probing to try and find the CP. Providing the
client with an explicit signal and location allows the client to get
connected faster.

I do not think that the *network* needs to (or should) keep track of
the state of the client; it feels like a layer violation, and adds
much complexity. Many networks with captive portals are small networks
like coffee shops, doctor's offices, or similar, and so have very
limited networking devices. So, keeping this as simple and
non-resource intensive is a definite goal. For example, many homes'
CPE contain CP functionality, for example for guest networks. As we
have often seen, the quality of home CPE is far from stellar and so
keeping the functionality simple and easy to implement would be good.

The captive portal needs some state because it acts as a gatekeeper,
and the client needs *some* state because it establishes a TCP
connection and does the login dance. There is a mailing list to
discuss the larger set of interactions around captive portals, and I
suspect we will probably end up with a protocol between the client and
the CP that provides information to the client such as how long it's
access is valid for, etc.

So, again, this document is not trying to address the whole CP
interaction, instead it is simply a "Dude, there is a CP at $location,
you will have to talk to it before you can reach the Internet"...

On Fri, Mar 27, 2015 at 3:55 PM, Warren Kumari <warren@kumari.net> wrote:
> Hi all,
>
> Just quickly wanted to say thanks for the comments --  I haven't done
> anything useful with them yet, but will address them after the meeting
> is all done, I've gotten home, etc...
>
> W
>
>
> On Fri, Mar 27, 2015 at 8:43 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> Le 27/03/2015 08:12, Dan L=C3=BCdtke a =C3=A9crit :
>>>
>>>
>>>>>
>>>>>>
>>>>>> Why would there be two routers on the same Client subnet in the
>>>>>> first place?
>>>>>
>>>>>
>>>>> So the clients can be multi-homed.
>>>>
>>>>
>>>> Ok, so each router would advertise a different prefix.
>>>>
>>>> In a similar way, two DHCP Relays (software present in each Router)
>>>> would be in charge of two different prefixes, distinction visible
>>>> in DHCP Server's conf file.
>>>>
>>>
>>> Only if both routers are from the same provider or administrative
>>> domain, right?
>>
>>
>> Right.
>>
>> I think two non-DHCP-Relay Routers too will need to be from the same
>> provider or same administrative domain in order to advertise two
>> different prefixes on the same link.  The reason of that necessity is
>> that they must make sure only one of them claims (RA) to be a default
>> router, otherwise they will fool the Client with two default routes (a
>> Client uses only one default route).  That can be achieved only if they
>> are administered by a single entity, be that an ISP or a sysadmin.
>>
>>> Not sure what the direction is you want to got there, but I remember
>>> it was about =E2=80=9Cthe full picture=E2=80=9D.
>>
>>
>> I am trying to say that the full picture of a network can easily include
>> a DHCP server(s), as much as a well-administered set of Routers sending =
RAs.
>>
>> This full picture would be needed when conceiving how the portal
>> notification should be given to a client.
>>
>> Suggesting not to set DHCP out of it.
>>
>> Alex
>>
>>
>>
>>>
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
> --
> 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



--=20
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 Apr 20 14:15:48 2015
Return-Path: <jared@puck.nether.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414771B31F3; Mon, 20 Apr 2015 14:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level: 
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m69YyZuztWH3; Mon, 20 Apr 2015 14:15:45 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF7D1A1B17; Mon, 20 Apr 2015 14:15:45 -0700 (PDT)
Received: from [IPv6:2601:4:f02:6c00:a5ff:8760:91d5:f203] (unknown [IPv6:2601:4:f02:6c00:a5ff:8760:91d5:f203]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 95A835406A0; Mon, 20 Apr 2015 17:15:44 -0400 (EDT)
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: text/plain; charset=utf-8
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com>
Date: Mon, 20 Apr 2015 17:15:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0F55735-AC24-4509-807C-0C567002AA33@puck.nether.net>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/u9ovMtXpVNcHwqekgwmQdRkJ4_g>
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, draft-wkumari-dhc-capport.shepherd@ietf.org, olafur@cloudflare.com, Paul Ebersman <ebersman-ietf@dragon.net>, Steve Sheng <steve.sheng@icann.org>, draft-wkumari-dhc-capport@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>, draft-wkumari-dhc-capport.ad@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Apr 2015 21:15:47 -0000

with the HTTPS everywhere movement, a method such as this needs to be
simple and widely available.  Today we see interception of tcp/80 as
part of a natural browser <-> server interaction to drive the user
to the authentication portal.

Allowing a DHCP option to specify one is behind a CP, allows =
authentication
to occur regardless of the end-site the user is attempting to interact =
with.

Information such as duration SHOULD be communicated via the duration of
lease.  Things such as multiple DHCP servers should not be in such a
document as it increases the complexity of response without adding =
value.
If one has multiple DHCP servers giving out different portals without
further communication between them, of course things will break.  It=E2=80=
=99s
not incumbent to document all the ways a network can poorly perform, but
we are defining how it should perform well, leaving the implementation
details of clustering, etc.. should be left to the implementing network.

- Jared

=20
> On Apr 20, 2015, at 4:59 PM, Warren Kumari <warren@kumari.net> wrote:
>=20
> So, I'm having a hard time trying to convert these comments into
> actual text that I can put in the document. If people have anything
> specific that they would like incorporated, please send text.
>=20
> The purpose of this document is simply to inform the client that it is
> behind a CP **and how to reach that CaptivePortal**.
> A client connecting to a new network has to assume that there may be a
> CP present, and perform probing to try and find the CP. Providing the
> client with an explicit signal and location allows the client to get
> connected faster.
>=20
> I do not think that the *network* needs to (or should) keep track of
> the state of the client; it feels like a layer violation, and adds
> much complexity. Many networks with captive portals are small networks
> like coffee shops, doctor's offices, or similar, and so have very
> limited networking devices. So, keeping this as simple and
> non-resource intensive is a definite goal. For example, many homes'
> CPE contain CP functionality, for example for guest networks. As we
> have often seen, the quality of home CPE is far from stellar and so
> keeping the functionality simple and easy to implement would be good.
>=20
> The captive portal needs some state because it acts as a gatekeeper,
> and the client needs *some* state because it establishes a TCP
> connection and does the login dance. There is a mailing list to
> discuss the larger set of interactions around captive portals, and I
> suspect we will probably end up with a protocol between the client and
> the CP that provides information to the client such as how long it's
> access is valid for, etc.
>=20
> So, again, this document is not trying to address the whole CP
> interaction, instead it is simply a "Dude, there is a CP at $location,
> you will have to talk to it before you can reach the Internet"...
>=20
> On Fri, Mar 27, 2015 at 3:55 PM, Warren Kumari <warren@kumari.net> =
wrote:
>> Hi all,
>>=20
>> Just quickly wanted to say thanks for the comments --  I haven't done
>> anything useful with them yet, but will address them after the =
meeting
>> is all done, I've gotten home, etc...
>>=20
>> W
>>=20
>>=20
>> On Fri, Mar 27, 2015 at 8:43 AM, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> wrote:
>>> Le 27/03/2015 08:12, Dan L=C3=BCdtke a =C3=A9crit :
>>>>=20
>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> Why would there be two routers on the same Client subnet in the
>>>>>>> first place?
>>>>>>=20
>>>>>>=20
>>>>>> So the clients can be multi-homed.
>>>>>=20
>>>>>=20
>>>>> Ok, so each router would advertise a different prefix.
>>>>>=20
>>>>> In a similar way, two DHCP Relays (software present in each =
Router)
>>>>> would be in charge of two different prefixes, distinction visible
>>>>> in DHCP Server's conf file.
>>>>>=20
>>>>=20
>>>> Only if both routers are from the same provider or administrative
>>>> domain, right?
>>>=20
>>>=20
>>> Right.
>>>=20
>>> I think two non-DHCP-Relay Routers too will need to be from the same
>>> provider or same administrative domain in order to advertise two
>>> different prefixes on the same link.  The reason of that necessity =
is
>>> that they must make sure only one of them claims (RA) to be a =
default
>>> router, otherwise they will fool the Client with two default routes =
(a
>>> Client uses only one default route).  That can be achieved only if =
they
>>> are administered by a single entity, be that an ISP or a sysadmin.
>>>=20
>>>> Not sure what the direction is you want to got there, but I =
remember
>>>> it was about =E2=80=9Cthe full picture=E2=80=9D.
>>>=20
>>>=20
>>> I am trying to say that the full picture of a network can easily =
include
>>> a DHCP server(s), as much as a well-administered set of Routers =
sending RAs.
>>>=20
>>> This full picture would be needed when conceiving how the portal
>>> notification should be given to a client.
>>>=20
>>> Suggesting not to set DHCP out of it.
>>>=20
>>> Alex
>>>=20
>>>=20
>>>=20
>>>>=20
>>>>=20
>>>> Dan
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>>=20
>> --
>> 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
>=20
>=20
>=20
> --=20
> 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
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Mon Apr 20 17:16:31 2015
Return-Path: <farmer@umn.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D4B11B359B for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 17:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcyhfZaTIN_4 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 17:16:29 -0700 (PDT)
Received: from vs-a.tc.umn.edu (vs-a.tc.umn.edu [134.84.119.220]) by ietfa.amsl.com (Postfix) with ESMTP id 577DC1B3598 for <ipv6@ietf.org>; Mon, 20 Apr 2015 17:16:29 -0700 (PDT)
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by vs-a.tc.umn.edu (UMN smtpd) with ESMTP for <ipv6@ietf.org>; Mon, 20 Apr 2015 19:16:23 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f182.google.com [209.85.223.182] #+LO+TS+TR
X-Umn-Classification: local
Received: by iebrs15 with SMTP id rs15so2422293ieb.3 for <ipv6@ietf.org>; Mon, 20 Apr 2015 17:16:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=uN2K6O+HUrMbVKiVQCzjCm75tJjLXoJtSDC7DWWUExY=; b=p/BKAZMYJ3LbeE38L+GYYPHwrSE3tMvfaE0YD3aGCEfDXT+fYHnYR9fz+QdOi4h8zd nhqqNcHStjPfYe4CNerSXy/rUjTG0wiLjGMu+CCsBQt4Twn5oQtcXvINVmQtLXIhle50 bvCSCK/r4az29myxlaKELz/rH1sCkWtGMsh0E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=uN2K6O+HUrMbVKiVQCzjCm75tJjLXoJtSDC7DWWUExY=; b=E07LU8re/E9t6lJn3fcMsaXqAndtUEZ+iPe6WT/BioBGOwjT+WYEDkS/r6GpaHJtU0 LNR5aA91+E/YBVDO0MiyjsrGcIB0J7Ne2IrfUsHzcIfTakDoGzw7ItDdD6nmYIMd8qFo natX/cf8WKkejWlHPO+oxTeDRxjm7UvKh7qsM6ksizEVSY44Hed/iLm+KZLoMWey+4nQ 4yRdK5+H0PctT+Tf79JEVpjmdYbNaWcvc7KThp5lrLcSSHglXIayzcgCiFktVOC8ZglV afBqyvWmUUo2lFbArP8kHJ4ujKeCuD0Xoma89l+dFqsJ91Dse937fv0kbcSFvs9F5qlE PheQ==
X-Gm-Message-State: ALoCoQn59g2gP0tZ4lUQYoGkdq7fmSVrS3ZR1yKGzDwpwGBlLTPDXXDEICdb81KYulUPU/+AogS4aECX1NqoSMRAgnkY1D294rkXmVcqcNoZ/aya2XJew8XkYHfKn9BFMbIU0G9o0xea
X-Received: by 10.107.37.132 with SMTP id l126mr25130443iol.42.1429575382896;  Mon, 20 Apr 2015 17:16:22 -0700 (PDT)
X-Received: by 10.107.37.132 with SMTP id l126mr25130435iol.42.1429575382711;  Mon, 20 Apr 2015 17:16:22 -0700 (PDT)
Received: from x-134-84-51-149.uofm-secure.wireless.umn.edu ([2607:ea00:104:2000:b4e7:6fac:d3e7:47d2]) by mx.google.com with ESMTPSA id k16sm7145823igf.19.2015.04.20.17.16.19 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Apr 2015 17:16:21 -0700 (PDT)
Message-ID: <553596D2.80304@umn.edu>
Date: Mon, 20 Apr 2015 19:16:18 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com>
In-Reply-To: <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bwV43oSiQ6uiqsEwNkNc6oJkAAQ>
Cc: draft-wkumari-dhc-capport.ad@ietf.org, draft-wkumari-dhc-capport@ietf.org, draft-wkumari-dhc-capport.shepherd@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 00:16:30 -0000

On 4/20/15 15:59 , Warren Kumari wrote:
...
> The purpose of this document is simply to inform the client that it is
> behind a CP **and how to reach that CaptivePortal**.
> A client connecting to a new network has to assume that there may be a
> CP present, and perform probing to try and find the CP. Providing the
> client with an explicit signal and location allows the client to get
> connected faster.

I don't know if this has been discussed already, but I think the ability 
to provide an explicit signal there is NO CP would also be useful, as 
well an primary intent of an explicit signal there is a CP.  Countering 
the assumption that a client needs to test for a CP.

...
> So, again, this document is not trying to address the whole CP
> interaction, instead it is simply a "Dude, there is a CP at $location,
> you will have to talk to it before you can reach the Internet"...

And I'd like to also see an option for "Dude, your all set to talk to 
the Internet", there is no need to probe for a captive portal.  There 
still maybe reasons to check and see if you are really connected to the 
Internet, things do break from time to time, but there SHOULD NOT be a 
CP in the way.


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Mon Apr 20 18:21:52 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 204C51A01A8 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 18:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 IMSMx39o6D0W for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 18:21:49 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::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 37E1A1A01A5 for <ipv6@ietf.org>; Mon, 20 Apr 2015 18:21:49 -0700 (PDT)
Received: by iecrt8 with SMTP id rt8so3339113iec.0 for <ipv6@ietf.org>; Mon, 20 Apr 2015 18:21:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zDw3fDib3/wkcOoR23clgoRjLEYvTEwSdLKceqioyB0=; b=Ujw0XlCnDiCEtaIfu4g4eXQYuXbE4DQs/bLpxQHl+KE2b1IhtEKZncxThDWweUG/o4 bdtrKZ8iyAl9oTErIydMAvqj7YQzmM0rJCMU+/Pk57c6yQZY3wRY6SdbYdB1uM3XlgZ8 CoHJIG4TzOjw9q6xSKSYkI+pcCIaiwxQbM+LgI1al0lx0tbXKaXvv+B/GwRWhi/6uD+w b2gnuVv/dLTTvAeQNF9kGV0nQoDFTS3MVG72UvunKZUK/yGFPQoBm2jTJFT+nh4b3sxx zeuWzWiuAfn0GxJiPzw4uKEssIGfavvX5URAyM5QW8WOXu2WkG9XD5gdwKY/jfjlvOeU c96g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=zDw3fDib3/wkcOoR23clgoRjLEYvTEwSdLKceqioyB0=; b=PnSw1pHc0gngXUuNXGt8Vrju9QAki6pJb6NGGI7l7UkRoK1eb6lQN0xDfkliL0VeSA EjrpwYVvj2ku+uvNNdAF9CYBFFLFw3EU6G4okrfzEWCuXRBLKa5V2piV3wfbEbZetlip VgBAvXN5UnhsMDG3p1tuphFc9AAo7Kdko5hUddZgfeGrDfMIvFgdRfTd5qAqa8du5AEH fv1mOfUOywrVP0lZoUbb0+CVJCa91ET4nGqI790GftMGwrDVR8rem7Q/G1DR4tS6EKI2 YDT1yM1QzQj6JEn+fry0NaDhWZCfw4urtQhYtIeM6A33aKq7/449piMlt+A5nvpMnHBm rHgA==
X-Gm-Message-State: ALoCoQl+8WJr6pAR9QRpsxFrGEFFOPZHc0d3s4ZEl0z+JyirKovKj9MIz/G0HOTeNw2xmf2c5bgL
X-Received: by 10.107.8.7 with SMTP id 7mr14096311ioi.87.1429579308682; Mon, 20 Apr 2015 18:21:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Mon, 20 Apr 2015 18:21:28 -0700 (PDT)
In-Reply-To: <55353A60.1030701@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 21 Apr 2015 10:21:28 +0900
Message-ID: <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Erik Nordmark <nordmark@acm.org>
Content-Type: multipart/alternative; boundary=001a113ecc44df7250051431de3a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yWvFgJ7JK0YQ2GKPY8--nifdLeA>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 01:21:51 -0000

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

On Tue, Apr 21, 2015 at 2:41 AM, Erik Nordmark <nordmark@acm.org> wrote:

> On 4/20/15 6:54 AM, Lorenzo Colitti wrote:
>
>> But then the "timely and scalable reconfiguration capabilities" cannot be
>> maintained. The network can't tell that host about any new information,
>> because that host won't receive it. The host will only receive it when it
>> wakes up next.
>>
> The host will take no action on any state until it wakes up. "timely"
> implies that hosts do not take any actions on stale state, and with RS
> refresh they would not. Hence it is very "timely".
>
> Note that without RS refresh hosts can take action on stale state if the
> packet loss experienced by the RAs is such that they miss e.g., the RAs
> that set the preferred lifetime for a prefix to zero, or set the default
> router lifetime to zero. Thus RFC 4861 operates in a probabilistic mode -
> which made sense when all networks were wires and one could assume the
> packet loss were independent events. Walking out of range of a radio does
> not result in independent events.
>
> Thus using RS refresh makes the "timely" work better than in RFC 4861.


Wait - are you arguing that soliciting information when the refresh timer
expires, or when the node wakes up, is more "timely" than the network just
sending an RA and having the node receive it? That doesn't make sense.

If what you're saying is that the sleeping node is going to ignore RAs
anyway, then you don't need an RS refresh option for the node to send an RS
and receive an RA when it wakes up. That's already possible.

If what you're saying is that the node won't receive the RA due to general
packet loss, then that can happen even for a solicited RA.

It depends how frequent the RAs are. In general purpose networks, they
>> might be more frequent. Also, any node joining may cause a solicited
>> multicast RA. Depending on the application, "after 10 minutes" may be a lot
>> better than "never".
>>
> For the network deployments where frequency of RAs is a concern, the
> desire seems to be to increase the time.
> If you read e.g. section 5.1 in
> draft-yourtchenko-colitti-nd-reduce-multicast you'll see that.
>

The document says that if you want to reduce multicast, you can increase
the RA interval. Personally, I don't think that makes sense, because one RA
every half hour is a tiny amount of traffic, which is trivial on any
general-purpose network.


>> What about points #2 and #3?
>>
> I think this email thread should about WG adoption and not WG last call or
> even about WG discussion.
> Are you arguing that all your points in the draft need to be addressed to
> your satisfaction before it can even become a WG draft?
> That isn't how an IETF working group is supposed to operate.
>

No. I am worried that this document cannot meet its goals, and even if it
does not, after adoption we will be unable to abandon it and instead ship
something that does not meet its goals.

Perhaps the issue here is that we don't agree on a problem statement, or
more accurately, what we're trying to accomplish with this drafts.

FWIW your #2 was a statement of fact, but not clear how it is relevant to
> the discussion. Seems to be related to your assumption that any multicast
> RA makes this null and void, which is incorrect.
>

It is relevant to the discussion because the draft proposes a mode where
periodic multicast RAs are suppressed. My point #2 observes that it's not
possible to exit that mode because there is no way to know whether legacy
hosts have left the network.

#3 was AFAICT a restatement of your conclusion based on some unstated
> assumptions. I already tried to guess at that unstated assumption in my
> first respond and I responded based on that. Was my guess wrong? Did I you
> make some other unstated assumptions?
>

My assumption is that in order to allow nodes to be updated dynamically,
hosts will still need to listen to periodic RAs. If you're saying that
that's now optional, then that's quite a change to the existing specs, and
that statement should be made very very clear in the draft.

--001a113ecc44df7250051431de3a
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 T=
ue, Apr 21, 2015 at 2:41 AM, Erik Nordmark <span dir=3D"ltr">&lt;<a href=3D=
"mailto:nordmark@acm.org" target=3D"_blank">nordmark@acm.org</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex"><span class=3D"">On 4/20/15 6:54 AM, Lorenzo Co=
litti wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
But then the &quot;timely and scalable reconfiguration capabilities&quot; c=
annot be maintained. The network can&#39;t tell that host about any new inf=
ormation, because that host won&#39;t receive it. The host will only receiv=
e it when it wakes up next.<br>
</blockquote></span>
The host will take no action on any state until it wakes up. &quot;timely&q=
uot; implies that hosts do not take any actions on stale state, and with RS=
 refresh they would not. Hence it is very &quot;timely&quot;.<br>
<br>
Note that without RS refresh hosts can take action on stale state if the pa=
cket loss experienced by the RAs is such that they miss e.g., the RAs that =
set the preferred lifetime for a prefix to zero, or set the default router =
lifetime to zero. Thus RFC 4861 operates in a probabilistic mode - which ma=
de sense when all networks were wires and one could assume the packet loss =
were independent events. Walking out of range of a radio does not result in=
 independent events.<br>
<br>
Thus using RS refresh makes the &quot;timely&quot; work better than in RFC =
4861.</blockquote><div><br></div><div>Wait - are you arguing that solicitin=
g information when the refresh timer expires, or when the node wakes up, is=
 more &quot;timely&quot; than the network just sending an RA and having the=
 node receive it? That doesn&#39;t make sense.</div><div><br></div><div><di=
v>If what you&#39;re saying is that the sleeping node is going to ignore RA=
s anyway, then you don&#39;t need an RS refresh option for the node to send=
 an RS and receive an RA when it wakes up. That&#39;s already possible.</di=
v></div><div><br></div><div>If what you&#39;re saying is that the node won&=
#39;t receive the RA due to general packet loss, then that can happen even =
for a solicited RA.</div><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex"><span class=3D""><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa=
dding-left:1ex">It depends how frequent the RAs are. In general purpose net=
works, they might be more frequent. Also, any node joining may cause a soli=
cited multicast RA. Depending on the application, &quot;after 10 minutes&qu=
ot; may be a lot better than &quot;never&quot;.<br>
</blockquote></span>
For the network deployments where frequency of RAs is a concern, the desire=
 seems to be to increase the time.<br>
If you read e.g. section 5.1 in draft-yourtchenko-colitti-nd-reduce-multica=
st you&#39;ll see that.<br></blockquote><div><br></div><div>The document sa=
ys that if you want to reduce multicast, you can increase the RA interval. =
Personally, I don&#39;t think that makes sense, because one RA every half h=
our is a tiny amount of traffic, which is trivial on any general-purpose ne=
twork.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex"><span class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
What about points #2 and #3?<br>
</blockquote></span>
I think this email thread should about WG adoption and not WG last call or =
even about WG discussion.<br>
Are you arguing that all your points in the draft need to be addressed to y=
our satisfaction before it can even become a WG draft?<br>
That isn&#39;t how an IETF working group is supposed to operate.<br></block=
quote><div><br></div><div>No. I am worried that this document cannot meet i=
ts goals, and even if it does not, after adoption we will be unable to aban=
don it and instead ship something that does not meet its goals.</div><div><=
br></div><div>Perhaps the issue here is that we don&#39;t agree on a proble=
m statement, or more accurately, what we&#39;re trying to accomplish with t=
his drafts.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">FWIW your #2 was a stateme=
nt of fact, but not clear how it is relevant to the discussion. Seems to be=
 related to your assumption that any multicast RA makes this null and void,=
 which is incorrect.<br></blockquote><div><br></div><div>It is relevant to =
the discussion because the draft proposes a mode where periodic multicast R=
As are suppressed. My point #2 observes that it&#39;s not possible to exit =
that mode because there is no way to know whether legacy hosts have left th=
e network.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204=
,204);border-left-style:solid;padding-left:1ex">
#3 was AFAICT a restatement of your conclusion based on some unstated assum=
ptions. I already tried to guess at that unstated assumption in my first re=
spond and I responded based on that. Was my guess wrong? Did I you make som=
e other unstated assumptions?<br></blockquote><div><br></div><div>My assump=
tion is that in order to allow nodes to be updated dynamically, hosts will =
still need to listen to periodic RAs. If you&#39;re saying that that&#39;s =
now optional, then that&#39;s quite a change to the existing specs, and tha=
t statement should be made very very clear in the draft.</div></div></div><=
/div>

--001a113ecc44df7250051431de3a--


From nobody Mon Apr 20 18:35:38 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7EB71A1B21 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 18:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 EbN1tFOPHzKu for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 18:35:36 -0700 (PDT)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001: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 7AD0F1A1B15 for <ipv6@ietf.org>; Mon, 20 Apr 2015 18:35:36 -0700 (PDT)
Received: by igbpi8 with SMTP id pi8so77027506igb.0 for <ipv6@ietf.org>; Mon, 20 Apr 2015 18:35:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=U5kkivtD/4DIhih1LcT5pnmD9ZI7oVu1t3U04QcVEjM=; b=FTh1/u+hmcJLWb/B5powo9sUlkeyxRjyf5ShZC9NR4MOAC6251qWL9iONPhpf/pvEN JQx/Z8BqgEtctJI+cKp4lZLjTZcxmQI6pRhkAr8dKVfY1XaInfpGu1Xh89i01XISGK3X 5ZW5kk+KtIV3L/TBG8zBCQLXUH7Um+JiQc0nRZglup2Gx63DKJEtGIV9FZ5E+un/o/8L o/S4EGR/G+8N6ZCuoI4WSWZx8hYqrCpDez/zqjyTO6oyLYeTNofF47kotriGh9KVtGNr UXfatQ9xDfnLH3JQeVd9yyi+GZgxjrd8qbT5Ye3kPmwqh4CVIMxIDgiPaP+Hlb477mdJ jibQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=U5kkivtD/4DIhih1LcT5pnmD9ZI7oVu1t3U04QcVEjM=; b=XU/Otj6xUSgQ3SYk+VbKWMFnEQyFayLHaCCIqPykbWCxRW79G2s5ok+eMGKIl7SaSd kXeeAwjAGHqwVYaPI5TO2yVjj9jvUdSqAE7qEYzFtEH4mboos9eKOq+9YaUSr3wh26GH mFYW0OXcesWHZI26P2CmRG637P82tGbaXoW2Pgt2scsyJr3G19s8gM8uPOYQGIHe8gqI Evw32t/zCnq91qByj3FF4UlALPKO8q8QWVN0XOU6quz/xR3mOCripGD1D211FfIgmjYA dbIGMWdlfVnEPFhnLOBoq2R2t2JgMdbLDj1IP0KQXF9YgHa95XwL233gdMADST7puBob FaBQ==
X-Gm-Message-State: ALoCoQnSx909f6trfp0tcr4QPhedzjifIihIsII69zJxVesS7VM0Qshjd762nTkvnUotilxNbOj4
X-Received: by 10.50.50.209 with SMTP id e17mr24652705igo.37.1429580135984; Mon, 20 Apr 2015 18:35:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Mon, 20 Apr 2015 18:35:15 -0700 (PDT)
In-Reply-To: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 21 Apr 2015 10:35:15 +0900
Message-ID: <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdca97c2f1e5505143210d2
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/f1za3zEtfJajkcozzbR2AHo3pTQ>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 01:35:37 -0000

--047d7bdca97c2f1e5505143210d2
Content-Type: text/plain; charset=UTF-8

On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <bob.hinden@gmail.com> wrote:

>         Title           : IPv6 Neighbor Discovery Optional Unicast RS/RA
> Refresh
>

All,

I think the root of my objections to this draft is that it proposes what is
in effect a substantial change to the current configuration model in IPv6
networks without saying so explicitly.

Currently, we have an easy-to understand, easy-to-reason-about model:
periodic RAs periodically notify everyone on link of the current
configuration information, and nodes that don't want to wait for such
periodic configuration information can solicit said information by sending
a request.

With this document, it's not clear what model is proposed.

It seems to me that this document is proposing a model where there are no
periodic RAs being sent. That's something that can be proposed, but if so,
we need to carefully evaluate the implications to the architecture, and how
switching to such a model affects the properties of the model we currently
have. We also need to make sure we understand how that model works for
hosts that a) don't support either resilient RS or this draft, b) support
resilient RS but not this draft.

If I am incorrect and the document is not proposing such a model, then it
should not mention this as a possibility. But then we need to understand
where the power savings are.

Cheers,
Lorenzo

--047d7bdca97c2f1e5505143210d2
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 S=
at, Mar 28, 2015 at 12:34 AM, Bob Hinden <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:bob.hinden@gmail.com" target=3D"_blank">bob.hinden@gmail.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IPv6 Neighbor Discovery Op=
tional Unicast RS/RA Refresh<br></blockquote><div><br></div><div>All,</div>=
<div><br></div><div>I think the root of my objections to this draft is that=
 it proposes what is in effect a substantial change to the current configur=
ation model in IPv6 networks without saying so explicitly.</div><div><br></=
div><div>Currently, we have an easy-to understand, easy-to-reason-about mod=
el: periodic RAs periodically notify everyone on link of the current config=
uration information, and nodes that don&#39;t want to wait for such periodi=
c configuration information can solicit said information by sending a reque=
st.</div><div><br></div><div>With this document, it&#39;s not clear what mo=
del is proposed.</div><div><br></div><div>It seems to me that this document=
 is proposing a model where there are no periodic RAs being sent. That&#39;=
s something that can be proposed, but if so, we need to carefully evaluate =
the implications to the architecture, and how switching to such a model aff=
ects the properties of the model we currently have. We also need to make su=
re we understand how that model works for hosts that a) don&#39;t support e=
ither resilient RS or this draft, b) support resilient RS but not this draf=
t.</div><div><br></div><div>If I am incorrect and the document is not propo=
sing such a model, then it should not mention this as a possibility. But th=
en we need to understand where the power savings are.</div><div><br></div><=
div>Cheers,</div><div>Lorenzo</div></div></div></div>

--047d7bdca97c2f1e5505143210d2--


From nobody Mon Apr 20 18:44:55 2015
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD581A1EFC; Mon, 20 Apr 2015 18:44:54 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3PkANNSD9ww; Mon, 20 Apr 2015 18:44:52 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0728.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::728]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FBED1A1DE1; Mon, 20 Apr 2015 18:44:52 -0700 (PDT)
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) by DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) with Microsoft SMTP Server (TLS) id 15.1.136.25; Tue, 21 Apr 2015 01:44:33 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) by DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) with mapi id 15.01.0136.026; Tue, 21 Apr 2015 01:44:33 +0000
From: Christian Huitema <huitema@microsoft.com>
To: David Farmer <farmer@umn.edu>, Warren Kumari <warren@kumari.net>
Subject: RE: RA extension review requested for draft-wkumari-dhc-capport
Thread-Topic: RA extension review requested for draft-wkumari-dhc-capport
Thread-Index: AQHQe6z3HBCQisVfYU+hXV2XWofiIJ1WmWwAgAAX24A=
Date: Tue, 21 Apr 2015 01:44:33 +0000
Message-ID: <DM2PR0301MB065519EB1CFF67886A3AFA33A8EF0@DM2PR0301MB0655.namprd03.prod.outlook.com>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com> <553596D2.80304@umn.edu>
In-Reply-To: <553596D2.80304@umn.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: umn.edu; dkim=none (message not signed) header.d=none; 
x-originating-ip: [131.107.174.254]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0655;
x-o365ent-eop-header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
x-microsoft-antispam-prvs: <DM2PR0301MB065528EB49805D06174F62DBA8EF0@DM2PR0301MB0655.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(24454002)(66066001)(76576001)(54356999)(93886004)(33656002)(106116001)(5001770100001)(62966003)(92566002)(46102003)(74316001)(50986999)(86362001)(2950100001)(2900100001)(122556002)(77156002)(102836002)(230783001)(2656002)(87936001)(76176999)(2171001)(40100003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0655; H:DM2PR0301MB0655.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:DM2PR0301MB0655; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0655; 
x-forefront-prvs: 0553CBB77A
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Apr 2015 01:44:33.0292 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0655
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AWqtq0rMzIuTv-tViY8Rak85xr8>
Cc: "draft-wkumari-dhc-capport.ad@ietf.org" <draft-wkumari-dhc-capport.ad@ietf.org>, "draft-wkumari-dhc-capport.shepherd@ietf.org" <draft-wkumari-dhc-capport.shepherd@ietf.org>, "draft-wkumari-dhc-capport@ietf.org" <draft-wkumari-dhc-capport@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 01:44:54 -0000

On Monday, April 20, 2015, at 5:16 PM, David Farmer wrote:
> ...=20
> I don't know if this has been discussed already, but I think the ability =
to provide
> an explicit signal there is NO CP would also be useful, as well an primar=
y intent of
> an explicit signal there is a CP.  Countering the assumption that a clien=
t needs to
> test for a CP.

+1

Of course, that won't work on day 1. In the absence of information, the cli=
ent will have to go on testing for CP. But still, that makes the eventual o=
utcome better.

-- Christian Huitema



From nobody Mon Apr 20 21:36:41 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A69C81A90E6 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 21:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DdEj7qAoee4g for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 21:36:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9C81A90D2 for <ipv6@ietf.org>; Mon, 20 Apr 2015 21:36:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4C9DB180092; Mon, 20 Apr 2015 21:35:27 -0700 (PDT)
To: gorry@erg.abdn.ac.uk, magnus.westerlund@ericsson.com, brian@innovationslab.net, terry.manderson@icann.org, bob.hinden@gmail.com, otroan@employees.org
Subject: [Technical Errata Reported] RFC6936 (4341)
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150421043527.4C9DB180092@rfc-editor.org>
Date: Mon, 20 Apr 2015 21:35:27 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lADzy8fHK4NtH7aBz9MyUhH1VSQ>
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 04:36:39 -0000

The following errata report has been submitted for RFC6936,
"Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341

--------------------------------------
Type: Technical
Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>

Section: 1.3.5

Original Text
-------------
The ingress of a tunnel seeking to provide good
entropy in the flow label field would therefore need to create a
random flow label value and keep corresponding state so that all
packets that were associated with a flow would be consistently given
the same flow label.  Although possible, this complexity may not be
desirable in a tunnel ingress.

Corrected Text
--------------
The ingress of a tunnel seeking to provide good
entropy in the flow label field would therefore need to create a
pseudo-random flow label value using a stateless method
as described in [RFC6438] so that all
packets that were associated with a flow would be consistently given
the same flow label.

Notes
-----
It is incorrect that a stateful method is needed, and presumably that
was the complexity judged undesirable. Also, we shouldn't say "random"
when we mean "pseudo-random."

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6936 (draft-ietf-6man-udpzero-12)
--------------------------------------
Title               : Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums
Publication Date    : April 2013
Author(s)           : G. Fairhurst, M. Westerlund
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Mon Apr 20 21:47:11 2015
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970881B2CA2 for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 21:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2nz7sYWiild for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 21:47:09 -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 2EC791A9085 for <ipv6@ietf.org>; Mon, 20 Apr 2015 21:47:09 -0700 (PDT)
Received: from mb-aye.local (c-98-248-47-249.hsd1.ca.comcast.net [98.248.47.249]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id t3L4kZ5k027863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Apr 2015 04:46:35 GMT (envelope-from joelja@bogus.com)
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
To: RFC Errata System <rfc-editor@rfc-editor.org>, gorry@erg.abdn.ac.uk, magnus.westerlund@ericsson.com, brian@innovationslab.net, terry.manderson@icann.org, bob.hinden@gmail.com, otroan@employees.org
references: <20150421043527.4C9DB180092@rfc-editor.org>
From: joel jaeggli <joelja@bogus.com>
message-id: <5535D626.6020405@bogus.com>
Date: Mon, 20 Apr 2015 21:46:30 -0700
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0
mime-version: 1.0
in-reply-to: <20150421043527.4C9DB180092@rfc-editor.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9KbbCa6H9wJcPMEntLg943IciKRCCi2BG"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jUR23fJNnCx-6BZjvUIOLSXxelA>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 04:47:10 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9KbbCa6H9wJcPMEntLg943IciKRCCi2BG
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

anyone care to comment?

joel

On 4/20/15 9:35 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC6936,
> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Ch=
ecksums".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D6936&eid=3D4341
>=20
> --------------------------------------
> Type: Technical
> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>=20
> Section: 1.3.5
>=20
> Original Text
> -------------
> The ingress of a tunnel seeking to provide good
> entropy in the flow label field would therefore need to create a
> random flow label value and keep corresponding state so that all
> packets that were associated with a flow would be consistently given
> the same flow label.  Although possible, this complexity may not be
> desirable in a tunnel ingress.
>=20
> Corrected Text
> --------------
> The ingress of a tunnel seeking to provide good
> entropy in the flow label field would therefore need to create a
> pseudo-random flow label value using a stateless method
> as described in [RFC6438] so that all
> packets that were associated with a flow would be consistently given
> the same flow label.
>=20
> Notes
> -----
> It is incorrect that a stateful method is needed, and presumably that
> was the complexity judged undesirable. Also, we shouldn't say "random"
> when we mean "pseudo-random."
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC6936 (draft-ietf-6man-udpzero-12)
> --------------------------------------
> Title               : Applicability Statement for the Use of IPv6 UDP D=
atagrams with Zero Checksums
> Publication Date    : April 2013
> Author(s)           : G. Fairhurst, M. Westerlund
> Category            : PROPOSED STANDARD
> Source              : IPv6 Maintenance
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20



--9KbbCa6H9wJcPMEntLg943IciKRCCi2BG
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.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlU11iYACgkQ8AA1q7Z/VrLjvwCfaxZZuzmXIdEcnnjJHXM6PvgP
pwoAnR/G8DQurWJvsx4btaXXw2O34RBl
=o2Cg
-----END PGP SIGNATURE-----

--9KbbCa6H9wJcPMEntLg943IciKRCCi2BG--


From nobody Mon Apr 20 23:10:59 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55AA21B343B for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 23:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 SDZN4ZXpdo4d for <ipv6@ietfa.amsl.com>; Mon, 20 Apr 2015 23:10:57 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001: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 E4FE61B32EA for <ipv6@ietf.org>; Mon, 20 Apr 2015 23:10:50 -0700 (PDT)
Received: by igbpi8 with SMTP id pi8so79885765igb.0 for <ipv6@ietf.org>; Mon, 20 Apr 2015 23:10:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/Tp44SwAXwB9O2EdYxM2cQUAPp9i4soFfNOd5nPouTo=; b=GkVFLR+QgaJJm92nk460Cu1K4uhcmdHn5496trBcVdEsog0TK5wd6SQdQwpTK1v2y0 8wlympxcwI35n1YSF78YZrNLNiiJpuyYYEemmMNA3wfpy1iTgdGYfTg6jVS0Zgp58oEi bKccmk08BkY8js/wKf+9iLQT2njY9BTvKSmgCXrlohRvw5cvfnFqSBxJmjHQe3xlzRJu 9nfyGaNiXylEc1A9TxBRZlASysReU9VsbnrqUP2y/1VLVqGNs6jBJOMwBkbPGpnjtSqz A9LcndWL5SFdLdjhhrShzU66dIupgo3mxrirUKu2bEpgSruXpxytU9HFpNFHCDz+KFJ+ k2uA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=/Tp44SwAXwB9O2EdYxM2cQUAPp9i4soFfNOd5nPouTo=; b=Keg1wlA9qVYajz7MyRMJUaF3KrxAWNc3/rVeirwBzjXJp9lmnaAxeFtH2ArT71O14F G5RrkJZ1CkC7JJlv3VOcTCQUqhweXm9UMowz4PkmY5UrXm/MCgNNktvujaWAOkkikt4i t5weY277uJKjiBXUbqmj0iA82STtGG25mEBySzUf9MUnWEqMV66qujFAA5Hyovg0Hylz xBlu27dTQexhc+PQNO7GAQlvbTebhVcUmpl1E58ubFltP5DfMYPAHCmlC13JYzhFdAqL yL2v1WUPr5dTB77z0lyLXGonkdGJUajUTaaUC21GQqGDRpt6VNoYkP/0L48eTa0t57Vs K2xQ==
X-Gm-Message-State: ALoCoQmphxY9mY0tVeqD96gRmRRTNNJa8lIqJJCJoijTLjSg7OLMcWEO0y+MU4kE6tR17dhKpSPE
X-Received: by 10.50.50.209 with SMTP id e17mr25690651igo.37.1429596650347; Mon, 20 Apr 2015 23:10:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Mon, 20 Apr 2015 23:10:29 -0700 (PDT)
In-Reply-To: <553596D2.80304@umn.edu>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com> <553596D2.80304@umn.edu>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 21 Apr 2015 15:10:29 +0900
Message-ID: <CAKD1Yr1TcwHxFx_8u_w802wLUZhevwqTsA0P7743gV41CRsM4Q@mail.gmail.com>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary=047d7bdca97c8456b3051435e849
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/T4cZfovMijezbu-k2SWkiGhgh2k>
Cc: draft-wkumari-dhc-capport.ad@ietf.org, draft-wkumari-dhc-capport@ietf.org, draft-wkumari-dhc-capport.shepherd@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 06:10:58 -0000

--047d7bdca97c8456b3051435e849
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 21, 2015 at 9:16 AM, David Farmer <farmer@umn.edu> wrote:

> I don't know if this has been discussed already, but I think the ability
>> to provide an explicit signal there is NO CP would also be useful, as well
>> an primary intent of an explicit signal there is a CP.  Countering the
>> assumption that a client needs to test for a CP.
>>
>
Yeah, because people won't ever the "no captive portal" signal if there's a
captive portal, will they?

http://www.cadinc.com/why-your-apple-ios-7-device-wont-connect-to-the-wifi-network
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01010101.html

--047d7bdca97c8456b3051435e849
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 T=
ue, Apr 21, 2015 at 9:16 AM, David Farmer <span dir=3D"ltr">&lt;<a href=3D"=
mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex"><span class=3D""><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex">I don&#39;t know i=
f this has been discussed already, but I think the ability to provide an ex=
plicit signal there is NO CP would also be useful, as well an primary inten=
t of an explicit signal there is a CP.=C2=A0 Countering the assumption that=
 a client needs to test for a CP.<br></blockquote></span></blockquote><div>=
<br></div><div>Yeah, because people won&#39;t ever the &quot;no captive por=
tal&quot; signal if there&#39;s a captive portal, will they?</div><div><br>=
</div><div><a href=3D"http://www.cadinc.com/why-your-apple-ios-7-device-won=
t-connect-to-the-wifi-network">http://www.cadinc.com/why-your-apple-ios-7-d=
evice-wont-connect-to-the-wifi-network</a><br></div><div><a href=3D"http://=
www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/=
consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01010101.html"=
>http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration=
/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_010101=
01.html</a><br></div></div></div></div>

--047d7bdca97c8456b3051435e849--


From nobody Tue Apr 21 00:21:58 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 512B81B36B6 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 00:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNklNJg3R2qj for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 00:21:55 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75FE61B36B0 for <ipv6@ietf.org>; Tue, 21 Apr 2015 00:21:55 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id E6C9360E7; Tue, 21 Apr 2015 00:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=ctsKxyFtaB/H5mfRDpiyVRU5EiY=; b= sFMJJIErCc/zNEcoKeXNTNrsO6qVfUuNk+DgbOftm13llnOMLGBv7IA1M91GJeEL EEPzemURehfPYdIM1AcAdKnNkIj3X81u1Nqkhr+8faPiH0oKaAhXfmKvaLh5Nyou NRao0lKrLbMHUnZCc0hDcTnDu1SbSltETGt2f4jJL/A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=mpqNUxzHRruk2qOEjgpZR0y8h7 iR/GAJHkwML/rPrWJFyn7APwbIolA/bhVzrgDBuhaT+k1WwxIFnjxlHfknmt8hmH mdYaDAEHDTwcAI96VTwUaVOk5OLJh0vlw34Uygmz9ikLMou99snIIs6jgQXGkw2c KYXYvxDSW0xQfg7eE=
Received: from gomlefisk.localdomain (unknown [173.38.220.51]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id F3E2E6088; Tue, 21 Apr 2015 00:21:52 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 23EFE42F0C44; Tue, 21 Apr 2015 09:20:57 +0200 (CEST)
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_431B07D7-080E-452B-BD71-01F176C10C3F"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <5535D626.6020405@bogus.com>
Date: Tue, 21 Apr 2015 09:20:56 +0200
Message-Id: <AA38B090-9281-4F94-B26E-AF5CF560D485@employees.org>
References: <20150421043527.4C9DB180092@rfc-editor.org> <5535D626.6020405@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/i5CqMJmJDeQYMrbIJ9EnYdhzoQY>
Cc: gorry@erg.abdn.ac.uk, Brian Haberman <brian@innovationslab.net>, 6man WG <ipv6@ietf.org>, 6MAN WG <bob.hinden@gmail.com>, terry.manderson@icann.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 07:21:57 -0000

--Apple-Mail=_431B07D7-080E-452B-BD71-01F176C10C3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

> anyone care to comment?

I believe the corrected text in the errata is correct.

http://www.ietf.org/iesg/statement/errata-processing.html
	=95 Only errors that could cause implementation or deployment =
problems or significant confusion should be Verified.

if the current text led implementors to dismiss setting the flow label =
because of the wrong assumption that per flow state was needed at tunnel =
ingress, then I think that=92s confusing and would also make flow label =
ECMP deployments problematic.

following that logic the errata should be verified.

cheers,
Ole

>=20
> On 4/20/15 9:35 PM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6936,
>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero =
Checksums".
>>=20
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3D6936&eid=3D4341
>>=20
>> --------------------------------------
>> Type: Technical
>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>=20
>> Section: 1.3.5
>>=20
>> Original Text
>> -------------
>> The ingress of a tunnel seeking to provide good
>> entropy in the flow label field would therefore need to create a
>> random flow label value and keep corresponding state so that all
>> packets that were associated with a flow would be consistently given
>> the same flow label.  Although possible, this complexity may not be
>> desirable in a tunnel ingress.
>>=20
>> Corrected Text
>> --------------
>> The ingress of a tunnel seeking to provide good
>> entropy in the flow label field would therefore need to create a
>> pseudo-random flow label value using a stateless method
>> as described in [RFC6438] so that all
>> packets that were associated with a flow would be consistently given
>> the same flow label.
>>=20
>> Notes
>> -----
>> It is incorrect that a stateful method is needed, and presumably that
>> was the complexity judged undesirable. Also, we shouldn't say =
"random"
>> when we mean "pseudo-random."
>>=20
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>=20
>> --------------------------------------
>> RFC6936 (draft-ietf-6man-udpzero-12)
>> --------------------------------------
>> Title               : Applicability Statement for the Use of IPv6 UDP =
Datagrams with Zero Checksums
>> Publication Date    : April 2013
>> Author(s)           : G. Fairhurst, M. Westerlund
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party     : IESG
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>=20
>=20
>=20


--Apple-Mail=_431B07D7-080E-452B-BD71-01F176C10C3F
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

iQEcBAEBCgAGBQJVNfpYAAoJEFuJXizso86gr7gIAIGJPJl78ruYh04ieCfAoQXU
w0qIIJNV9Ozk1zswVEkXqhin8LY7aUWSM5teWckkjo5UibErcEVGoX4OZ7RGXOf7
5rhSau4BY+OgFdBf9pf9tBF7+y1kwH6rjGoi2mwn6R9GkFdk5INwK69IMQ3O78KC
TsNQHALb6s8R08NOj+HFLN4+fesSjSYcux/FJfWWA5t7wdcABQRHh1k08lTtL2qS
DK+u7cZ95g1oT6RZ3+h5zGbzxfnpgaiHUBX2s4rqMjQnXXp4F/97ceXe7XtFJlLL
ctrdinvWKm8cbJUU7zp89c6rWILKzRwQ02Et9y+GwI/UNwKE0RZtGTgvMuZMDg4=
=AT3o
-----END PGP SIGNATURE-----

--Apple-Mail=_431B07D7-080E-452B-BD71-01F176C10C3F--


From nobody Tue Apr 21 00:47:17 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA36C1A890D for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 00:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.502
X-Spam-Level: 
X-Spam-Status: No, score=0.502 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HK_RANDOM_REPLYTO=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 AxRTmmBbZ9xD for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 00:47:13 -0700 (PDT)
Received: from nm21.bullet.mail.bf1.yahoo.com (nm21.bullet.mail.bf1.yahoo.com [98.139.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AF981A8955 for <ipv6@ietf.org>; Tue, 21 Apr 2015 00:47:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1429602432; bh=GG1VQq1ghvtkUBAtXeiDTHa7sl4ZTkFJ5Tct1Z/oJMU=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=KmwALKG/sw5IPWi8+rkLj4hVj1TaXOD3JaeWTEhdrPI79F/Lj2Kf8MKI/iSqHQgOv5+2LI3vHBSlRDZfwbqj6ySaNRdDZ+/SVuQK19TqibaV1RlqzbsGpJyVmDKo7qLen8hftG4X7WPLb0vUpqh+JK9tY1jTtTk0uJfNh4OvRNh7j9ur1bfVfkfCxGdkHKjKA8K2VhFRUtStbv+8xg10l0wEvk4JFDMw/0cEtgYkvlICBSYxV1CC+0TtX6Vi8noQ+Qs68OVyC3ECygqul2nxCvRYUcj3fw3SSvWV8k5hdXZkEAhnLONE1FSzhtIpT0WA0MMWJd21xw/sDGPnfFJCKA==
Received: from [98.139.214.32] by nm21.bullet.mail.bf1.yahoo.com with NNFMP; 21 Apr 2015 07:47:12 -0000
Received: from [98.139.212.248] by tm15.bullet.mail.bf1.yahoo.com with NNFMP;  21 Apr 2015 07:47:12 -0000
Received: from [127.0.0.1] by omp1057.mail.bf1.yahoo.com with NNFMP; 21 Apr 2015 07:47:12 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 776984.93688.bm@omp1057.mail.bf1.yahoo.com
X-YMail-OSG: QWCnl70VM1nACNe3CK6s1v7cgCTW8HpHUb7I89xPeSZQMyVK0QoBXYfflTo51fz _VGxvmSn3.cMVH3mCZH_HyVAE0MiG2XIaJ75FiS3MBzIg9DexaKTZF0EQbabvGNycykionLnRnYO CSzjqTYwTJaf0juN6vja.5HdG.138FmqMQQ6qC9PfiOPASsR4CGjlc7dsGhp0NwixERUJ90_g3F6 6JEhRb1yqxOJhOyNbrqc9ygmt45AlAgx4Qv4Mb_3FPOBe3fHOh0q.gBXJUSc.lfWQsli.YUlmQD9 EkCl_w5.7.Pa.e5WOsM_pDa7tdThmKUl3GlVS5pvrKEDGQHDWTWBLPnSSvfUios.H2xvxbEX3.Ot AN2uLB4WwkmVee7_w41Jan_eqf6HoXcjZhCVe1ZnU9r5Y5Pv3UN8cdgjsrxe4PiWS46.34J0kbCu X8rT.My1imdv1.zq6VFZBWNIrZO_uDlU1P45UUDM5iySM60rnCl7TUCMV2X77qTHIFsUKolwyOkE NUiwvUtmtVwSh2VRkh5Qqq9L1qq9nLjZMLbWR4WpVGqheVEjK1A--
Received: by 76.13.26.142; Tue, 21 Apr 2015 07:47:12 +0000 
Date: Tue, 21 Apr 2015 07:47:04 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: joel jaeggli <joelja@bogus.com>,  RFC Errata System <rfc-editor@rfc-editor.org>,  "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>,  "magnus.westerlund@ericsson.com" <magnus.westerlund@ericsson.com>,  "brian@innovationslab.net" <brian@innovationslab.net>,  "terry.manderson@icann.org" <terry.manderson@icann.org>,  "bob.hinden@gmail.com" <bob.hinden@gmail.com>,  "otroan@employees.org" <otroan@employees.org>
Message-ID: <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <5535D626.6020405@bogus.com>
References: <5535D626.6020405@bogus.com>
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_1217668_895093635.1429602424840"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/N3INV4laj30Az0R4UxzUsn7Vs9I>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 07:47:15 -0000

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

I agree with Brian's update, I think stateless LB is better.
(Strangely and coincidently, my OpenWRT router reported I received one toda=
y:
[ =C2=A0422.320000] IPv6: udp checksum is 0

)


Regards,Mark.
      From: joel jaeggli <joelja@bogus.com>
 To: RFC Errata System <rfc-editor@rfc-editor.org>; gorry@erg.abdn.ac.uk; m=
agnus.westerlund@ericsson.com; brian@innovationslab.net; terry.manderson@ic=
ann.org; bob.hinden@gmail.com; otroan@employees.org=20
Cc: ipv6@ietf.org=20
 Sent: Tuesday, 21 April 2015, 14:46
 Subject: Re: [Technical Errata Reported] RFC6936 (4341)
  =20
anyone care to comment?

joel



On 4/20/15 9:35 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC6936,
> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Chec=
ksums".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D6936&eid=3D4341
>=20
> --------------------------------------
> Type: Technical
> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>=20
> Section: 1.3.5
>=20
> Original Text
> -------------
> The ingress of a tunnel seeking to provide good
> entropy in the flow label field would therefore need to create a
> random flow label value and keep corresponding state so that all
> packets that were associated with a flow would be consistently given
> the same flow label.=C2=A0 Although possible, this complexity may not be
> desirable in a tunnel ingress.
>=20
> Corrected Text
> --------------
> The ingress of a tunnel seeking to provide good
> entropy in the flow label field would therefore need to create a
> pseudo-random flow label value using a stateless method
> as described in [RFC6438] so that all
> packets that were associated with a flow would be consistently given
> the same flow label.
>=20
> Notes
> -----
> It is incorrect that a stateful method is needed, and presumably that
> was the complexity judged undesirable. Also, we shouldn't say "random"
> when we mean "pseudo-random."
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC6936 (draft-ietf-6man-udpzero-12)
> --------------------------------------
> Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Applicability Sta=
tement for the Use of IPv6 UDP Datagrams with Zero Checksums
> Publication Date=C2=A0 =C2=A0 : April 2013
> Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : G. Fairhurst, M. Westerlund
> Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED STANDARD
> Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IPv6 Maintenance
> Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Internet
> Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF
> Verifying Party=C2=A0 =C2=A0 : IESG
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


  
------=_Part_1217668_895093635.1429602424840
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div dir=3D"ltr" id=3D"yui_3_16_=
0_1_1429576897795_59831">I agree with Brian's update, I think stateless LB =
is better.</div><div id=3D"yui_3_16_0_1_1429576897795_59863"><br></div><div=
 dir=3D"ltr" id=3D"yui_3_16_0_1_1429576897795_59833">(Strangely and coincid=
ently, my OpenWRT router reported I received one today:</div><div dir=3D"lt=
r" id=3D"yui_3_16_0_1_1429576897795_59833"><br></div><div dir=3D"ltr" id=3D=
"yui_3_16_0_1_1429576897795_59833" class=3D"" style=3D"">[ &nbsp;422.320000=
] IPv6: udp checksum is 0<br class=3D"" style=3D""></div><div dir=3D"ltr" i=
d=3D"yui_3_16_0_1_1429576897795_59833" class=3D"" style=3D""><br></div><div=
 dir=3D"ltr" id=3D"yui_3_16_0_1_1429576897795_59833" class=3D"" style=3D"">=
)</div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1429576897795_59833" class=3D"" =
style=3D""><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1429576897795_5983=
3" class=3D"" style=3D""><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_1_1429=
576897795_59833" class=3D"" style=3D""><br></div><div dir=3D"ltr" id=3D"yui=
_3_16_0_1_1429576897795_59833" class=3D"" style=3D"">Regards,</div><div dir=
=3D"ltr" id=3D"yui_3_16_0_1_1429576897795_59833" class=3D"" style=3D"">Mark=
.</div><div id=3D"yui_3_16_0_1_1429576897795_59832"><br></div>  <div style=
=3D"font-family: Helvetica Neue-Light, Helvetica Neue Light, Helvetica Neue=
, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id=3D"yui_=
3_16_0_1_1429576897795_59837"> <div style=3D"font-family: HelveticaNeue, He=
lvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;=
" id=3D"yui_3_16_0_1_1429576897795_59836"> <div dir=3D"ltr" id=3D"yui_3_16_=
0_1_1429576897795_59835"> <hr size=3D"1" id=3D"yui_3_16_0_1_1429576897795_5=
9838">  <font size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_1_1429576897795_59=
862"> <b id=3D"yui_3_16_0_1_1429576897795_60000"><span style=3D"font-weight=
:bold;" id=3D"yui_3_16_0_1_1429576897795_59999">From:</span></b> joel jaegg=
li &lt;joelja@bogus.com&gt;<br> <b><span style=3D"font-weight: bold;">To:</=
span></b> RFC Errata System &lt;rfc-editor@rfc-editor.org&gt;; gorry@erg.ab=
dn.ac.uk; magnus.westerlund@ericsson.com; brian@innovationslab.net; terry.m=
anderson@icann.org; bob.hinden@gmail.com; otroan@employees.org <br><b id=3D=
"yui_3_16_0_1_1429576897795_62911"><span style=3D"font-weight: bold;" id=3D=
"yui_3_16_0_1_1429576897795_62910">Cc:</span></b> ipv6@ietf.org <br> <b><sp=
an style=3D"font-weight: bold;">Sent:</span></b> Tuesday, 21 April 2015, 14=
:46<br> <b><span style=3D"font-weight: bold;">Subject:</span></b> Re: [Tech=
nical Errata Reported] RFC6936 (4341)<br> </font> </div> <div class=3D"y_ms=
g_container" id=3D"yui_3_16_0_1_1429576897795_59839"><br>anyone care to com=
ment?<br clear=3D"none"><br clear=3D"none">joel<br clear=3D"none"><div clas=
s=3D"qtdSeparateBR"><br><br></div><div class=3D"yqt1311882056" id=3D"yqtfd9=
2595"><br clear=3D"none">On 4/20/15 9:35 PM, RFC Errata System wrote:<br cl=
ear=3D"none">&gt; The following errata report has been submitted for RFC693=
6,<br clear=3D"none">&gt; "Applicability Statement for the Use of IPv6 UDP =
Datagrams with Zero Checksums".<br clear=3D"none">&gt; <br clear=3D"none">&=
gt; --------------------------------------<br clear=3D"none">&gt; You may r=
eview the report below and at:<br clear=3D"none">&gt; <a shape=3D"rect" hre=
f=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D6936&amp;eid=3D4341"=
 target=3D"_blank" id=3D"yui_3_16_0_1_1429576897795_62969">http://www.rfc-e=
ditor.org/errata_search.php?rfc=3D6936&amp;eid=3D4341</a><br clear=3D"none"=
>&gt; <br clear=3D"none">&gt; --------------------------------------<br cle=
ar=3D"none">&gt; Type: Technical<br clear=3D"none">&gt; Reported by: Brian =
Carpenter &lt;<a shape=3D"rect" ymailto=3D"mailto:brian.e.carpenter@gmail.c=
om" href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com=
</a>&gt;<br clear=3D"none">&gt; <br clear=3D"none">&gt; Section: 1.3.5<br c=
lear=3D"none">&gt; <br clear=3D"none">&gt; Original Text<br clear=3D"none">=
&gt; -------------<br clear=3D"none">&gt; The ingress of a tunnel seeking t=
o provide good<br clear=3D"none">&gt; entropy in the flow label field would=
 therefore need to create a<br clear=3D"none">&gt; random flow label value =
and keep corresponding state so that all<br clear=3D"none">&gt; packets tha=
t were associated with a flow would be consistently given<br clear=3D"none"=
>&gt; the same flow label.&nbsp; Although possible, this complexity may not=
 be<br clear=3D"none">&gt; desirable in a tunnel ingress.<br clear=3D"none"=
>&gt; <br clear=3D"none">&gt; Corrected Text<br clear=3D"none">&gt; -------=
-------<br clear=3D"none">&gt; The ingress of a tunnel seeking to provide g=
ood<br clear=3D"none">&gt; entropy in the flow label field would therefore =
need to create a<br clear=3D"none">&gt; pseudo-random flow label value usin=
g a stateless method<br clear=3D"none">&gt; as described in [RFC6438] so th=
at all<br clear=3D"none">&gt; packets that were associated with a flow woul=
d be consistently given<br clear=3D"none">&gt; the same flow label.<br clea=
r=3D"none">&gt; <br clear=3D"none">&gt; Notes<br clear=3D"none">&gt; -----<=
br clear=3D"none">&gt; It is incorrect that a stateful method is needed, an=
d presumably that<br clear=3D"none">&gt; was the complexity judged undesira=
ble. Also, we shouldn't say "random"<br clear=3D"none">&gt; when we mean "p=
seudo-random."<br clear=3D"none">&gt; <br clear=3D"none">&gt; Instructions:=
<br clear=3D"none">&gt; -------------<br clear=3D"none">&gt; This erratum i=
s currently posted as "Reported". If necessary, please<br clear=3D"none">&g=
t; use "Reply All" to discuss whether it should be verified or<br clear=3D"=
none">&gt; rejected. When a decision is reached, the verifying party (IESG)=
<br clear=3D"none">&gt; can log in to change the status and edit the report=
, if necessary. <br clear=3D"none">&gt; <br clear=3D"none">&gt; -----------=
---------------------------<br clear=3D"none">&gt; RFC6936 (draft-ietf-6man=
-udpzero-12)<br clear=3D"none">&gt; --------------------------------------<=
br clear=3D"none">&gt; Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
;  : Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Ch=
ecksums<br clear=3D"none">&gt; Publication Date&nbsp; &nbsp; : April 2013<b=
r clear=3D"none">&gt; Author(s)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  : G. Fai=
rhurst, M. Westerlund<br clear=3D"none">&gt; Category&nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; : PROPOSED STANDARD<br clear=3D"none">&gt; Source&nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : IPv6 Maintenance<br clear=3D"n=
one">&gt; Area&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Int=
ernet<br clear=3D"none">&gt; Stream&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; : IETF<br clear=3D"none">&gt; Verifying Party&nbsp; &nbsp;  : IESG=
<br clear=3D"none">&gt; <br clear=3D"none">&gt; ---------------------------=
-----------------------------------------<br clear=3D"none">&gt; IETF IPv6 =
working group mailing list<br clear=3D"none">&gt; <a shape=3D"rect" ymailto=
=3D"mailto:ipv6@ietf.org" href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><b=
r clear=3D"none">&gt; Administrative Requests: <a shape=3D"rect" href=3D"ht=
tps://www.ietf.org/mailman/listinfo/ipv6" target=3D"_blank">https://www.iet=
f.org/mailman/listinfo/ipv6</a><br clear=3D"none">&gt; --------------------=
------------------------------------------------<br clear=3D"none">&gt; <br=
 clear=3D"none"><br clear=3D"none"></div><br><div class=3D"yqt1311882056" i=
d=3D"yqtfd08347">----------------------------------------------------------=
----------<br clear=3D"none">IETF IPv6 working group mailing list<br clear=
=3D"none"><a shape=3D"rect" ymailto=3D"mailto:ipv6@ietf.org" href=3D"mailto=
:ipv6@ietf.org">ipv6@ietf.org</a><br clear=3D"none">Administrative Requests=
: <a shape=3D"rect" href=3D"https://www.ietf.org/mailman/listinfo/ipv6" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br clear=3D"n=
one">--------------------------------------------------------------------<b=
r clear=3D"none"></div><br><br></div> </div> </div>  </div></body></html>
------=_Part_1217668_895093635.1429602424840--


From nobody Tue Apr 21 01:25:52 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B56E1B3741 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 01:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.311
X-Spam-Level: 
X-Spam-Status: No, score=-1.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 40lvdDnh2y5j for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 01:10:39 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id A62471AC3C2 for <ipv6@ietf.org>; Tue, 21 Apr 2015 01:10:39 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 1F59A1B002F2; Tue, 21 Apr 2015 09:10:44 +0100 (BST)
Received: from 130.243.28.208 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Tue, 21 Apr 2015 09:09:58 +0100
Message-ID: <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk>
In-Reply-To: <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com>
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com>
Date: Tue, 21 Apr 2015 09:09:58 +0100
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
From: gorry@erg.abdn.ac.uk
To: "Mark ZZZ Smith" <markzzzsmith@yahoo.com.au>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HpMuxjd8e_q5sPa_pfwhQS5q1hY>
X-Mailman-Approved-At: Tue, 21 Apr 2015 01:25:50 -0700
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 08:10:41 -0000

I agree with this update. I think it is a useful correction.

Gorry

> I agree with Brian's update, I think stateless LB is better.
> (Strangely and coincidently, my OpenWRT router reported I received one
> today:
> [  422.320000] IPv6: udp checksum is 0
>
> )
>
>
> Regards,Mark.
>       From: joel jaeggli <joelja@bogus.com>
>  To: RFC Errata System <rfc-editor@rfc-editor.org>; gorry@erg.abdn.ac.uk;
> magnus.westerlund@ericsson.com; brian@innovationslab.net;
> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org
> Cc: ipv6@ietf.org
>  Sent: Tuesday, 21 April 2015, 14:46
>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>
> anyone care to comment?
>
> joel
>
>
>
> On 4/20/15 9:35 PM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6936,
>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero
>> Checksums".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>
>> Section: 1.3.5
>>
>> Original Text
>> -------------
>> The ingress of a tunnel seeking to provide good
>> entropy in the flow label field would therefore need to create a
>> random flow label value and keep corresponding state so that all
>> packets that were associated with a flow would be consistently given
>> the same flow label.  Although possible, this complexity may not be
>> desirable in a tunnel ingress.
>>
>> Corrected Text
>> --------------
>> The ingress of a tunnel seeking to provide good
>> entropy in the flow label field would therefore need to create a
>> pseudo-random flow label value using a stateless method
>> as described in [RFC6438] so that all
>> packets that were associated with a flow would be consistently given
>> the same flow label.
>>
>> Notes
>> -----
>> It is incorrect that a stateful method is needed, and presumably that
>> was the complexity judged undesirable. Also, we shouldn't say "random"
>> when we mean "pseudo-random."
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC6936 (draft-ietf-6man-udpzero-12)
>> --------------------------------------
>> Title              : Applicability Statement for the Use of IPv6
>> UDP Datagrams with Zero Checksums
>> Publication Date    : April 2013
>> Author(s)          : G. Fairhurst, M. Westerlund
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party    : IESG
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>


From nobody Tue Apr 21 01:45:20 2015
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D15B61B37C8 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 01:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFZp1upj5l9G for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 01:45:18 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13A5C1B37CE for <ipv6@ietf.org>; Tue, 21 Apr 2015 01:45:15 -0700 (PDT)
X-AuditID: c1b4fb3a-f79146d0000070a3-87-55360e191e86
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 46.92.28835.91E06355; Tue, 21 Apr 2015 10:45:14 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.92) with Microsoft SMTP Server id 14.3.210.2; Tue, 21 Apr 2015 10:45:13 +0200
Message-ID: <55360E18.2000008@ericsson.com>
Date: Tue, 21 Apr 2015 10:45:12 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: <gorry@erg.abdn.ac.uk>, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk>
In-Reply-To: <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyM+Jvja4Un1mowfa5XBZb3+9js5jZ84/R 4nXbbEaLl2ffM1m8OrWG0eL0hKtsFpPbVrBZNO3/ymbRevQmqwOnx9kjCxg9Dh77yOjR8/kF k8fOWXfZPQ5fuM/isWTJTyaPmce/sHg0tB1j9fh+4ApTAGcUl01Kak5mWWqRvl0CV8alnpfs BXOUKt7vns7SwPhNuouRk0NCwETi899zTBC2mMSFe+vZuhi5OIQEjjJKzF+xmgXCWc4oMend ERaQKl4BbYkfnxYzgtgsAqoSvXM2sYLYbAIWEjd/NLKB2KICURITvx6CqheUODnzCZgtIuAm cWxtIxPIUGaB00wSvyY1gDULC5hLTD69gxVi2zJGid9fDoN1cAq4Syz+8Q7sPmYBA4kji+aw QtjyEs1bZzOD2EJAFzU0dbBOYBSchWThLCQts5C0LGBkXsUoWpxaXJybbmSkl1qUmVxcnJ+n l5dasokRGEEHt/y22sF48LnjIUYBDkYlHl6F9aahQqyJZcWVuYcYpTlYlMR57YwPhQgJpCeW pGanphakFsUXleakFh9iZOLglGpgXKHaPmuLC1vyW47nypduhEVcCq+ILphWEPaE9Zj8y8f9 a37MKp/8zbnDJzx2wqf87z3rzY3mu+31fPfzfe6p9lTDA2b1CSISO6qfBWSn/Hn+vMvZeUeh 95wL5zPkbUvFln1r5P8T2rROwfV5yIWCTo1Nb6fWFy04Xr0+Vr7ndIJJVNymlwaBSizFGYmG WsxFxYkAWajYqoECAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TTNscL0Nt1g3dPVtGVQZLodJbis>
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 08:45:20 -0000

I also support approving this Errata.

Cheers

Magnus

gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
> I agree with this update. I think it is a useful correction.
> 
> Gorry
> 
>> I agree with Brian's update, I think stateless LB is better.
>> (Strangely and coincidently, my OpenWRT router reported I received one
>> today:
>> [ Â 422.320000] IPv6: udp checksum is 0
>>
>> )
>>
>>
>> Regards,Mark.
>>       From: joel jaeggli <joelja@bogus.com>
>>  To: RFC Errata System <rfc-editor@rfc-editor.org>; gorry@erg.abdn.ac.uk;
>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org
>> Cc: ipv6@ietf.org
>>  Sent: Tuesday, 21 April 2015, 14:46
>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>
>> anyone care to comment?
>>
>> joel
>>
>>
>>
>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC6936,
>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero
>>> Checksums".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>
>>> Section: 1.3.5
>>>
>>> Original Text
>>> -------------
>>> The ingress of a tunnel seeking to provide good
>>> entropy in the flow label field would therefore need to create a
>>> random flow label value and keep corresponding state so that all
>>> packets that were associated with a flow would be consistently given
>>> the same flow label.Â  Although possible, this complexity may not be
>>> desirable in a tunnel ingress.
>>>
>>> Corrected Text
>>> --------------
>>> The ingress of a tunnel seeking to provide good
>>> entropy in the flow label field would therefore need to create a
>>> pseudo-random flow label value using a stateless method
>>> as described in [RFC6438] so that all
>>> packets that were associated with a flow would be consistently given
>>> the same flow label.
>>>
>>> Notes
>>> -----
>>> It is incorrect that a stateful method is needed, and presumably that
>>> was the complexity judged undesirable. Also, we shouldn't say "random"
>>> when we mean "pseudo-random."
>>>
>>> Instructions:
>>> -------------
>>> This erratum is currently posted as "Reported". If necessary, please
>>> use "Reply All" to discuss whether it should be verified or
>>> rejected. When a decision is reached, the verifying party (IESG)
>>> can log in to change the status and edit the report, if necessary.
>>>
>>> --------------------------------------
>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>> --------------------------------------
>>> TitleÂ  Â  Â  Â  Â  Â  Â  : Applicability Statement for the Use of IPv6
>>> UDP Datagrams with Zero Checksums
>>> Publication DateÂ  Â  : April 2013
>>> Author(s)Â  Â  Â  Â  Â  : G. Fairhurst, M. Westerlund
>>> CategoryÂ  Â  Â  Â  Â  Â  : PROPOSED STANDARD
>>> SourceÂ  Â  Â  Â  Â  Â  Â  : IPv6 Maintenance
>>> AreaÂ  Â  Â  Â  Â  Â  Â  Â  : Internet
>>> StreamÂ  Â  Â  Â  Â  Â  Â  : IETF
>>> Verifying PartyÂ  Â  : IESG
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>>
>>
> 
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue Apr 21 05:07:54 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 767441AC40E for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 05:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6] autolearn=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 F0sJEk1f7Yfx for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 05:07:52 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0F1C1AC40F for <ipv6@ietf.org>; Tue, 21 Apr 2015 05:07:46 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id A43E9880F3; Tue, 21 Apr 2015 05:07:46 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id BA59A136832A; Tue, 21 Apr 2015 05:07:45 -0700 (PDT)
Message-ID: <55363D89.2070001@innovationslab.net>
Date: Tue, 21 Apr 2015 08:07:37 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,  gorry@erg.abdn.ac.uk, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com>
In-Reply-To: <55360E18.2000008@ericsson.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tRhMeiNiaONImLI0GrWR2lxmQfSMQbwRK"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/d3Dy23OVcs3_bHn8Ick_HaMrmxQ>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 12:07:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tRhMeiNiaONImLI0GrWR2lxmQfSMQbwRK
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi all,
     While I agree with the sentiment that the proposed updated text is
more appropriate, we are on a slippery slope as to this being errata.
This is a technical change and not fixing an error.  Can someone point
to a discussion where a reference to 6438 and stateless methods occurred
and there was consensus to put that in 1.3.5?

     If not, this seems more like a new draft to obsolete 6936.

Regards,
Brian

On 4/21/15 4:45 AM, Magnus Westerlund wrote:
> I also support approving this Errata.
>=20
> Cheers
>=20
> Magnus
>=20
> gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
>> I agree with this update. I think it is a useful correction.
>>
>> Gorry
>>
>>> I agree with Brian's update, I think stateless LB is better.
>>> (Strangely and coincidently, my OpenWRT router reported I received on=
e
>>> today:
>>> [ =C2 422.320000] IPv6: udp checksum is 0
>>>
>>> )
>>>
>>>
>>> Regards,Mark.
>>>       From: joel jaeggli <joelja@bogus.com>
>>>  To: RFC Errata System <rfc-editor@rfc-editor.org>; gorry@erg.abdn.ac=
=2Euk;
>>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org=

>>> Cc: ipv6@ietf.org
>>>  Sent: Tuesday, 21 April 2015, 14:46
>>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>>
>>> anyone care to comment?
>>>
>>> joel
>>>
>>>
>>>
>>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>>> The following errata report has been submitted for RFC6936,
>>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero=

>>>> Checksums".
>>>>
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> http://www.rfc-editor.org/errata_search.php?rfc=3D6936&eid=3D4341
>>>>
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>>
>>>> Section: 1.3.5
>>>>
>>>> Original Text
>>>> -------------
>>>> The ingress of a tunnel seeking to provide good
>>>> entropy in the flow label field would therefore need to create a
>>>> random flow label value and keep corresponding state so that all
>>>> packets that were associated with a flow would be consistently given=

>>>> the same flow label.=C2  Although possible, this complexity may not =
be
>>>> desirable in a tunnel ingress.
>>>>
>>>> Corrected Text
>>>> --------------
>>>> The ingress of a tunnel seeking to provide good
>>>> entropy in the flow label field would therefore need to create a
>>>> pseudo-random flow label value using a stateless method
>>>> as described in [RFC6438] so that all
>>>> packets that were associated with a flow would be consistently given=

>>>> the same flow label.
>>>>
>>>> Notes
>>>> -----
>>>> It is incorrect that a stateful method is needed, and presumably tha=
t
>>>> was the complexity judged undesirable. Also, we shouldn't say "rando=
m"
>>>> when we mean "pseudo-random."
>>>>
>>>> Instructions:
>>>> -------------
>>>> This erratum is currently posted as "Reported". If necessary, please=

>>>> use "Reply All" to discuss whether it should be verified or
>>>> rejected. When a decision is reached, the verifying party (IESG)
>>>> can log in to change the status and edit the report, if necessary.
>>>>
>>>> --------------------------------------
>>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>>> --------------------------------------
>>>> Title=C2  =C2  =C2  =C2  =C2  =C2  =C2  : Applicability Statement fo=
r the Use of IPv6
>>>> UDP Datagrams with Zero Checksums
>>>> Publication Date=C2  =C2  : April 2013
>>>> Author(s)=C2  =C2  =C2  =C2  =C2  : G. Fairhurst, M. Westerlund
>>>> Category=C2  =C2  =C2  =C2  =C2  =C2  : PROPOSED STANDARD
>>>> Source=C2  =C2  =C2  =C2  =C2  =C2  =C2  : IPv6 Maintenance
>>>> Area=C2  =C2  =C2  =C2  =C2  =C2  =C2  =C2  : Internet
>>>> Stream=C2  =C2  =C2  =C2  =C2  =C2  =C2  : IETF
>>>> Verifying Party=C2  =C2  : IESG
>>>>
>>>> --------------------------------------------------------------------=

>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------=

>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>
>>
>>
>=20
>=20


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

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

iQEcBAEBCAAGBQJVNj2KAAoJEBOZRqCi7goqG8cH/1mFmOnuaygU4iW4s5pAFkJv
HnzKZgz+7dnibl7qN2HtlbEdl+sBh4/MAaIlaEvh7iRB+lqk8koSwqYiuA9XV6IG
bowQBJ7X0qrHHmzhzqi+8BZFlSfMy5rS26WNRgrSNXMnW37ZUdJFGU84sYbjWa45
t6qWMrsGhgWOdpwdmHYTnAhan7Lhh2w5DH+2w6rJcnVNmgFM5ZfdXog+oc0XT/9X
lW0Hh+sCmuPOt8Li66zsszKrTPG3AK5TN1eAhUXDeBXXVhyj/K2Vd2mVtaiwIHxt
uK2focu0IMTbyp0nvbfggxwYlacq/fwZ4oodRnB1sa7CRwcUN4sgtLQT2FQUb4M=
=COVI
-----END PGP SIGNATURE-----

--tRhMeiNiaONImLI0GrWR2lxmQfSMQbwRK--


From nobody Tue Apr 21 05:37:04 2015
Return-Path: <warren@kumari.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0D841ACD09 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 05:37:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdLPsxJOVdUq for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 05:37:02 -0700 (PDT)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (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 C60CE1ACD0D for <ipv6@ietf.org>; Tue, 21 Apr 2015 05:36:59 -0700 (PDT)
Received: by wiun10 with SMTP id n10so19775140wiu.1 for <ipv6@ietf.org>; Tue, 21 Apr 2015 05:36:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TQonzysYQPumsFtWHMFUecmyrEQXZXpHM05bwhf+9a4=; b=BsL0R3eRHeVhond2hkKLZLtNnFBjLCisRC4t7RhuvNLg3OrWJJXT+59meHeN5ARFkZ 9fdOTN8DwVZRbvaVrkjMGbYnS9kpEI45rwr0qQoeWTsLK3zsQCsPxZjukgER0ZS257+G VJQto5SazNtDiK+hCc2QcxjZlqLyVNiLOo8KwiwnsRE5O9ZsXXlBsmRz398qxRfNqed3 1cIDPjla/C9Gd3UbTnERiZvUQ0etYac1SV54ODeapiIjbCyfKMTL8ghMryvGckQy8zbW zSjbzPsczUpazfbfrrG6XLXZVjGK5YYo+6jMU0ogiSG0m4mMw5ZUsrQGtlQ8n6tCrISj StSg==
X-Gm-Message-State: ALoCoQmolb03OAyCYva4v7E5xfwjjgl7F906M9gb0DUpk3GV6HrIOMgECvFHWE/E/vlezGS+rcHv
MIME-Version: 1.0
X-Received: by 10.194.60.67 with SMTP id f3mr40883796wjr.28.1429619818465; Tue, 21 Apr 2015 05:36:58 -0700 (PDT)
Received: by 10.194.47.36 with HTTP; Tue, 21 Apr 2015 05:36:58 -0700 (PDT)
In-Reply-To: <CAKD1Yr1TcwHxFx_8u_w802wLUZhevwqTsA0P7743gV41CRsM4Q@mail.gmail.com>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com> <553596D2.80304@umn.edu> <CAKD1Yr1TcwHxFx_8u_w802wLUZhevwqTsA0P7743gV41CRsM4Q@mail.gmail.com>
Date: Tue, 21 Apr 2015 08:36:58 -0400
Message-ID: <CAHw9_iL8vSB1p37tJua+Roag_JmwFy2HywG48yOZtJFoYOD0QA@mail.gmail.com>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
From: Warren Kumari <warren@kumari.net>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8oTSkSasb80dhzPlo5_IFk2EvAI>
Cc: draft-wkumari-dhc-capport.ad@ietf.org, draft-wkumari-dhc-capport@ietf.org, draft-wkumari-dhc-capport.shepherd@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 12:37:04 -0000

On Tue, Apr 21, 2015 at 2:10 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Tue, Apr 21, 2015 at 9:16 AM, David Farmer <farmer@umn.edu> wrote:
>>>
>>> I don't know if this has been discussed already, but I think the ability
>>> to provide an explicit signal there is NO CP would also be useful, as well
>>> an primary intent of an explicit signal there is a CP.  Countering the
>>> assumption that a client needs to test for a CP.
>
>
> Yeah, because people won't ever the "no captive portal" signal if there's a
> captive portal, will they?
>
> http://www.cadinc.com/why-your-apple-ios-7-device-wont-connect-to-the-wifi-network
> http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01010101.html


Yeah, unfortunately Lorenzo is right -- there is an incentive for
networks who have a CP to claim that they do not, and so providing an
explicit "there is no CP here" signal seems like it may be a bad idea.

For the foreseeable future, and possibly for ever, clients will still
need to perform captive portal probing. Having the network inform the
client that it is behind a captive portal, and how it contact it is an
*optimization* - it allows the client to reach the CP faster / more
reliably, but does not, unfortunately, remove the need to probe.

W


-- 
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 Tue Apr 21 06:25:07 2015
Return-Path: <warren@kumari.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46DA41A1B00 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 06:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zDGzCWMsYqIN for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 06:25:04 -0700 (PDT)
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) (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 699551A1AFC for <ipv6@ietf.org>; Tue, 21 Apr 2015 06:24:59 -0700 (PDT)
Received: by wizk4 with SMTP id k4so139218939wiz.1 for <ipv6@ietf.org>; Tue, 21 Apr 2015 06:24:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9tQREwZwZ2quWODs2clO+1v4EvKkjnvLpbzi40ajPZE=; b=OVtaGFtcHHYpA/RIeJa2pu0aNCUMKI1AReBkF9kyZUTT/vPDBNORkC1vWLoCbrEtof 7M+5kpHIaUD74TLJGxut0TISaf5gxIudhj7dv0WkJiwcvFmja/tDxjcCzQQTAoUGP/+g fNpxPp/V1VwVCd0CSWCj3KhB7Hvn9+xMcQCVwFdV3ZWwyJgZyTQEhpmqw3UIR7aGGtGa 77k447d1hacvvQeCjeh52B+XHShnrGqkM8dSJr6ehprT6aw0Erp+jGiYZj+MLZRceinB 7xpP5KTvd3YnXeFIBhu8wA7JBRh/PSda2X0kdbpNvKwew/x604gr0lzLqn8WP8V6gntG eEYw==
X-Gm-Message-State: ALoCoQm23bmIqdq5GmL34evEv/Vf9pokMDs7Vj6iphGEwvnAU70eMjXd4tQLqdbQ59RmyhPfZq/A
MIME-Version: 1.0
X-Received: by 10.194.83.105 with SMTP id p9mr34724073wjy.117.1429622697909; Tue, 21 Apr 2015 06:24:57 -0700 (PDT)
Received: by 10.194.47.36 with HTTP; Tue, 21 Apr 2015 06:24:57 -0700 (PDT)
In-Reply-To: <D0F55735-AC24-4509-807C-0C567002AA33@puck.nether.net>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com> <D0F55735-AC24-4509-807C-0C567002AA33@puck.nether.net>
Date: Tue, 21 Apr 2015 09:24:57 -0400
Message-ID: <CAHw9_iK1j6qu2Ph_Hw+tiJZXQZvgnz77N_0oMZbTRJvuFeqmLQ@mail.gmail.com>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
From: Warren Kumari <warren@kumari.net>
To: Jared Mauch <jared@puck.nether.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oCI8crsvMN9dzOfXyoxNHWMf-Y4>
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, draft-wkumari-dhc-capport.shepherd@ietf.org, olafur@cloudflare.com, Paul Ebersman <ebersman-ietf@dragon.net>, Steve Sheng <steve.sheng@icann.org>, draft-wkumari-dhc-capport@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>, draft-wkumari-dhc-capport.ad@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 13:25:06 -0000

On Mon, Apr 20, 2015 at 5:15 PM, Jared Mauch <jared@puck.nether.net> wrote:
> with the HTTPS everywhere movement, a method such as this needs to be
> simple and widely available.  Today we see interception of tcp/80 as
> part of a natural browser <-> server interaction to drive the user
> to the authentication portal.
>
> Allowing a DHCP option to specify one is behind a CP, allows authenticati=
on
> to occur regardless of the end-site the user is attempting to interact wi=
th.
>
> Information such as duration SHOULD be communicated via the duration of
> lease.

I've heard this suggestion a few times (and I almost added a TTL to
the option), but it turns out this won't work - I guess I should add a
note to the document explaining why.

At many venues (for example, hotels), you can purchase different
amounts of time -- 1h for $2.95, 3h for $4.95, 1d for $15.95 or a week
for $<all the money in your wallet>.
The DHCP server doesn't know (actually, no-one knows) how much you
will purchase until you do :-)
You *could* possibly design something where the CP informs the DHCP
server after you have purchased, so that next time you connect you can
be told, but this seems overly complex.

There is a captive portal mailing list (and we may hold a BoF in
Prague) where we are discussing a captive portal interaction protocol.
Basically, you will discover the CP (using the DHCP/RA option, or
through probing), and the CP will include something like a
/.well-known/ URL, a WISPr Redirect, <something> that will allow the
client to come back and poll the CP itself for status - things like
remaining time, where to go to re-authenticate, etc. Basically the
stuff in the current doc just says:
"There is a CP. It live at <foo>",  and there will (eventually!) be a
better way of getting more info....



>  Things such as multiple DHCP servers should not be in such a
> document as it increases the complexity of response without adding value.
> If one has multiple DHCP servers giving out different portals without
> further communication between them, of course things will break.  It=E2=
=80=99s
> not incumbent to document all the ways a network can poorly perform, but
> we are defining how it should perform well, leaving the implementation
> details of clustering, etc.. should be left to the implementing network.

Yah. There are many ways to screw yourself, trying to enumerate all of
them leads to failure (and gives people ideas!)

At one point I tried to explain what a client should do it it gets CP
information via multiple means (e.g: RA and DHCPv4). This got tricky
(and was somewhat arbitrary). Eventually Ted Lemon suggested:

"In order to support multiple "classes" of clients (e.g: IPv4 only,
   IPv6 only with DHCPv6([RFC3315]), IPv6 only with RA) the captive
   portal can provide the URI via multiple methods (IPv4 DHCP, IPv6
   DHCP, IPv6 RA).  The captive portal operator should ensure that the
   URIs handed out are equivalent to reduce the chance of operational
   problems. "

This seems very similar to the above....

W


>
> - Jared
>
>
>> On Apr 20, 2015, at 4:59 PM, Warren Kumari <warren@kumari.net> wrote:
>>
>> So, I'm having a hard time trying to convert these comments into
>> actual text that I can put in the document. If people have anything
>> specific that they would like incorporated, please send text.
>>
>> The purpose of this document is simply to inform the client that it is
>> behind a CP **and how to reach that CaptivePortal**.
>> A client connecting to a new network has to assume that there may be a
>> CP present, and perform probing to try and find the CP. Providing the
>> client with an explicit signal and location allows the client to get
>> connected faster.
>>
>> I do not think that the *network* needs to (or should) keep track of
>> the state of the client; it feels like a layer violation, and adds
>> much complexity. Many networks with captive portals are small networks
>> like coffee shops, doctor's offices, or similar, and so have very
>> limited networking devices. So, keeping this as simple and
>> non-resource intensive is a definite goal. For example, many homes'
>> CPE contain CP functionality, for example for guest networks. As we
>> have often seen, the quality of home CPE is far from stellar and so
>> keeping the functionality simple and easy to implement would be good.
>>
>> The captive portal needs some state because it acts as a gatekeeper,
>> and the client needs *some* state because it establishes a TCP
>> connection and does the login dance. There is a mailing list to
>> discuss the larger set of interactions around captive portals, and I
>> suspect we will probably end up with a protocol between the client and
>> the CP that provides information to the client such as how long it's
>> access is valid for, etc.
>>
>> So, again, this document is not trying to address the whole CP
>> interaction, instead it is simply a "Dude, there is a CP at $location,
>> you will have to talk to it before you can reach the Internet"...
>>
>> On Fri, Mar 27, 2015 at 3:55 PM, Warren Kumari <warren@kumari.net> wrote=
:
>>> Hi all,
>>>
>>> Just quickly wanted to say thanks for the comments --  I haven't done
>>> anything useful with them yet, but will address them after the meeting
>>> is all done, I've gotten home, etc...
>>>
>>> W
>>>
>>>
>>> On Fri, Mar 27, 2015 at 8:43 AM, Alexandru Petrescu
>>> <alexandru.petrescu@gmail.com> wrote:
>>>> Le 27/03/2015 08:12, Dan L=C3=BCdtke a =C3=A9crit :
>>>>>
>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Why would there be two routers on the same Client subnet in the
>>>>>>>> first place?
>>>>>>>
>>>>>>>
>>>>>>> So the clients can be multi-homed.
>>>>>>
>>>>>>
>>>>>> Ok, so each router would advertise a different prefix.
>>>>>>
>>>>>> In a similar way, two DHCP Relays (software present in each Router)
>>>>>> would be in charge of two different prefixes, distinction visible
>>>>>> in DHCP Server's conf file.
>>>>>>
>>>>>
>>>>> Only if both routers are from the same provider or administrative
>>>>> domain, right?
>>>>
>>>>
>>>> Right.
>>>>
>>>> I think two non-DHCP-Relay Routers too will need to be from the same
>>>> provider or same administrative domain in order to advertise two
>>>> different prefixes on the same link.  The reason of that necessity is
>>>> that they must make sure only one of them claims (RA) to be a default
>>>> router, otherwise they will fool the Client with two default routes (a
>>>> Client uses only one default route).  That can be achieved only if the=
y
>>>> are administered by a single entity, be that an ISP or a sysadmin.
>>>>
>>>>> Not sure what the direction is you want to got there, but I remember
>>>>> it was about =E2=80=9Cthe full picture=E2=80=9D.
>>>>
>>>>
>>>> I am trying to say that the full picture of a network can easily inclu=
de
>>>> a DHCP server(s), as much as a well-administered set of Routers sendin=
g RAs.
>>>>
>>>> This full picture would be needed when conceiving how the portal
>>>> notification should be given to a client.
>>>>
>>>> Suggesting not to set DHCP out of it.
>>>>
>>>> Alex
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> 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
>>
>>
>>
>> --
>> 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
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>



--=20
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 Tue Apr 21 07:42:37 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0D61A891F for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 07:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 uRv6MTsFXHfr for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 07:42:35 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::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 48B111ACDA9 for <ipv6@ietf.org>; Tue, 21 Apr 2015 07:42:35 -0700 (PDT)
Received: by iecrt8 with SMTP id rt8so15239989iec.0 for <ipv6@ietf.org>; Tue, 21 Apr 2015 07:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=k2KMjeAnaN1cRAaIf0eerYFfUyoNZMXVNGKAs+Fz6iE=; b=JveZ18/6eLliOPRXmvBD0UqkE/C9BGceVbat705wxzt1DEKhvVytQeMQYg1T72xn2S 4VRAUPlAEQZnbT8pckWzixXehVniBwBNoy5X/XQ75WWq+GCz+792cJfBj3gXkjIrs/76 Jbu39ndV+HI/4ah9EycWFZiGy2PqW0lwhz9PrNt+DilSBiVxBkGs7VHb3iMDEf4Yqso3 Gqsz3174ONomhxVWzprbsnuwoFIZvuD2iOQOlxEJgt8Nklw8xr/GeuV7OtvepP6Zc3tP mEo2GTKoxD6IpjDygxcoshTYogAu9uCvKWulVxw6sAb++Ep7vakCRqmp6oGezS9APiXX hWKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=k2KMjeAnaN1cRAaIf0eerYFfUyoNZMXVNGKAs+Fz6iE=; b=LBkjA6JIvaTQ5DmYOPtiJoiKP/eRhEY8bKjAtA4KDmGglOP16KyMB0ISebCyzFKIOH XG7f1oMXsTofNydXmMOOuOMhSkIBnFP8NtWu0ItXfSYtCbKJ2TCd6YcdeylOK45hpQDq zDcCIVD6bcJ4sxCFD/9aXXkZN3XpItK3Y3IGuO/+xHUBGODMgZO6l/+BoTCWIKuFgJa6 ga0mP3btbasTM4nzm5m2WknCue3TjpbYVMxeow0dNlBKAM/YAP4jZy1/VvFr6R4YHutS 8PvEyGWtH89DDxrXcjw/TgzRLt9ewD48OxWrohejdebvMN901yLnRFfzscRW60J8CLQa jo2Q==
X-Gm-Message-State: ALoCoQkUOm2linhHFmhGvlc3t7fkvvlZ29aJuoRzWcknS09+tCkoXAfABbcAWxcbZz5XVEX/kO2r
X-Received: by 10.42.207.206 with SMTP id fz14mr3874457icb.34.1429627354793; Tue, 21 Apr 2015 07:42:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Tue, 21 Apr 2015 07:42:14 -0700 (PDT)
In-Reply-To: <CAHw9_iK1j6qu2Ph_Hw+tiJZXQZvgnz77N_0oMZbTRJvuFeqmLQ@mail.gmail.com>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com> <D0F55735-AC24-4509-807C-0C567002AA33@puck.nether.net> <CAHw9_iK1j6qu2Ph_Hw+tiJZXQZvgnz77N_0oMZbTRJvuFeqmLQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 21 Apr 2015 23:42:14 +0900
Message-ID: <CAKD1Yr3gOz2fC0=T2W16sN2XkY7bWY62J2dxCH2e-jiSrRAPig@mail.gmail.com>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=20cf30426df6a4eabd05143d0e10
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yDnQxHKfj5eWIvCZM6lEvQ5NdT0>
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, draft-wkumari-dhc-capport.shepherd@ietf.org, olafur@cloudflare.com, Paul Ebersman <ebersman-ietf@dragon.net>, draft-wkumari-dhc-capport.ad@ietf.org, draft-wkumari-dhc-capport@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>, Steve Sheng <steve.sheng@icann.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 14:42:36 -0000

--20cf30426df6a4eabd05143d0e10
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 21, 2015 at 10:24 PM, Warren Kumari <warren@kumari.net> wrote:

> You *could* possibly design something where the CP informs the DHCP
> server after you have purchased, so that next time you connect you can
> be told, but this seems overly complex.
>

If you're using RAs, you can just include that in the RA option. RAs are
dynamic.

--20cf30426df6a4eabd05143d0e10
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 T=
ue, Apr 21, 2015 at 10:24 PM, Warren Kumari <span dir=3D"ltr">&lt;<a href=
=3D"mailto:warren@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">You *could* possibly design =
something where the CP informs the DHCP<br>
server after you have purchased, so that next time you connect you can<br>
be told, but this seems overly complex.<br></blockquote><div><br></div><div=
>If you&#39;re using RAs, you can just include that in the RA option. RAs a=
re dynamic.</div></div></div></div>

--20cf30426df6a4eabd05143d0e10--


From nobody Tue Apr 21 08:01:35 2015
Return-Path: <warren@kumari.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D190E1ACDAD for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 08:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bX185Z1_BFuo for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 08:01:33 -0700 (PDT)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) (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 0AB9B1ACDEC for <ipv6@ietf.org>; Tue, 21 Apr 2015 08:01:21 -0700 (PDT)
Received: by wgin8 with SMTP id n8so216229040wgi.0 for <ipv6@ietf.org>; Tue, 21 Apr 2015 08:01:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XT3TFd+/iThh9PDZPoVU0KYJz3oUlr9xkeZ7gSgmbmo=; b=jld8JTSGw/+v9L3K0yuNwtQV9AFsRpUuHXkVxLLsOdNRs0TerF9k0GC3vy6HMJXHwv 2sZQw1ckfmHKtq5S2WGAPTVtpIEIvtpTZkt3AkAKo8DBZpUKIOQBom7ZIEBONM0lEi72 xthicFNZIA61SQRanovutn414Di28pEfkE894daiDjMXTIfFmUGgsHbtje/HCGHhyoQ3 tUIazu9D3BRyYMypLLuNnjqIFSpyutovoQz6z5EJgRbyfkeYnH1Wp/pJfZ83D9O9mHsA SRl3OirXB1Z5HNw0fb9d5t/Y/rnAGQmqzr6K3G3N0m+HOszenQi/SRsw0190hIUm0t9V GD7g==
X-Gm-Message-State: ALoCoQkHTw6w1yRu08u2lJPMycngkO74aiIMw4TdSMRtI99cyHBtIMHY+2yna/Gxdx5VCZ1T1uu6
MIME-Version: 1.0
X-Received: by 10.180.83.130 with SMTP id q2mr6460188wiy.89.1429628479677; Tue, 21 Apr 2015 08:01:19 -0700 (PDT)
Received: by 10.194.47.36 with HTTP; Tue, 21 Apr 2015 08:01:19 -0700 (PDT)
In-Reply-To: <CAKD1Yr3gOz2fC0=T2W16sN2XkY7bWY62J2dxCH2e-jiSrRAPig@mail.gmail.com>
References: <DC4904FE-D5C5-4A6A-898F-840032757F94@nominum.com> <55104EF9.7060409@gmail.com> <A72A5029-AA09-4AA2-A288-7DFD383C571A@danrl.de> <55133B1A.3020904@gmail.com> <FB0234A3-C472-488D-9C33-F5C5A7EAA147@danrl.de> <CAKD1Yr039=F_mn7no94UQeTP4y=Z-WvNjznQCx6mKWhUKwhu8A@mail.gmail.com> <55148F1F.8050806@gmail.com> <1B266F12-DDDF-4358-97E3-DBB4ABE161A9@nominum.com> <551553CD.9020902@gmail.com> <F22C8F0E-94A8-4FD8-90F2-5AF4634A2FA5@danrl.de> <5515563A.5060509@gmail.com> <D6F83A1F-BC9D-4C68-A8D8-4CF8A7A27A25@danrl.de> <55155E6B.5070705@gmail.com> <CAHw9_i+_cGTsdeM_RomuUWHKpFAVqM6GZunav19h9sAbzBexAw@mail.gmail.com> <CAHw9_iJHP6fKE6T9qc2fiLZPbwpkU1tdJ3FHUginu09in371MA@mail.gmail.com> <D0F55735-AC24-4509-807C-0C567002AA33@puck.nether.net> <CAHw9_iK1j6qu2Ph_Hw+tiJZXQZvgnz77N_0oMZbTRJvuFeqmLQ@mail.gmail.com> <CAKD1Yr3gOz2fC0=T2W16sN2XkY7bWY62J2dxCH2e-jiSrRAPig@mail.gmail.com>
Date: Tue, 21 Apr 2015 11:01:19 -0400
Message-ID: <CAHw9_iKXCn2HBQrP4xPeuRfBhuW4TPwJX9oM15xbC_5W+XUc3g@mail.gmail.com>
Subject: Re: RA extension review requested for draft-wkumari-dhc-capport
From: Warren Kumari <warren@kumari.net>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/mzn1eM4gsWD7hf6m-muTpSLeEfg>
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, draft-wkumari-dhc-capport.shepherd@ietf.org, olafur@cloudflare.com, Paul Ebersman <ebersman-ietf@dragon.net>, draft-wkumari-dhc-capport.ad@ietf.org, draft-wkumari-dhc-capport@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>, Steve Sheng <steve.sheng@icann.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 15:01:34 -0000

On Tue, Apr 21, 2015 at 10:42 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Tue, Apr 21, 2015 at 10:24 PM, Warren Kumari <warren@kumari.net> wrote:
>>
>> You *could* possibly design something where the CP informs the DHCP
>> server after you have purchased, so that next time you connect you can
>> be told, but this seems overly complex.
>
>
> If you're using RAs, you can just include that in the RA option. RAs are
> dynamic.

Yeah, you *could*, but it seems to me to have the same issue - it
would be fairly complex, especially if the CP is not the device
generating the RA...

Also, what, multicast with one TTL for folk joining the network, and
then unicast to specific clients who have joined their unique time
remaining?

The CP functionality of often baked into CPE (for example, my
neighbor's Linksys has a "guest network" with CP functionality. It
only barely kinda works at the moment, and the v6 functionality is
similarly wonky -- getting it to send different RAs to different
clients seems like a bridge too far...

W


-- 
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 Tue Apr 21 08:21:48 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3971ACDBB for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 08:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.611
X-Spam-Level: 
X-Spam-Status: No, score=-3.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZuZRw5Nj73dw for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 08:07:32 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id DD4491ACDA0 for <ipv6@ietf.org>; Tue, 21 Apr 2015 08:07:31 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id B0C6B1B001D2; Tue, 21 Apr 2015 16:07:32 +0100 (BST)
Received: from 130.243.28.20 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Tue, 21 Apr 2015 16:06:46 +0100
Message-ID: <d2dd9fb3b6a9586783dbe2067d729ffe.squirrel@erg.abdn.ac.uk>
In-Reply-To: <55363D89.2070001@innovationslab.net>
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net>
Date: Tue, 21 Apr 2015 16:06:46 +0100
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
From: gorry@erg.abdn.ac.uk
To: "Brian Haberman" <brian@innovationslab.net>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rmQ_kt_nKe5XxgAO4L3ScXNLz2w>
X-Mailman-Approved-At: Tue, 21 Apr 2015 08:21:46 -0700
Cc: gorry@erg.abdn.ac.uk, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 15:07:34 -0000

I'll read the surrounding para's carefully and get back.

Gorry

> Hi all,
>      While I agree with the sentiment that the proposed updated text is
> more appropriate, we are on a slippery slope as to this being errata.
> This is a technical change and not fixing an error.  Can someone point
> to a discussion where a reference to 6438 and stateless methods occurred
> and there was consensus to put that in 1.3.5?
>
>      If not, this seems more like a new draft to obsolete 6936.
>
> Regards,
> Brian
>
> On 4/21/15 4:45 AM, Magnus Westerlund wrote:
>> I also support approving this Errata.
>>
>> Cheers
>>
>> Magnus
>>
>> gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
>>> I agree with this update. I think it is a useful correction.
>>>
>>> Gorry
>>>
>>>> I agree with Brian's update, I think stateless LB is better.
>>>> (Strangely and coincidently, my OpenWRT router reported I received one
>>>> today:
>>>> [ Â 422.320000] IPv6: udp checksum is 0
>>>>
>>>> )
>>>>
>>>>
>>>> Regards,Mark.
>>>>       From: joel jaeggli <joelja@bogus.com>
>>>>  To: RFC Errata System <rfc-editor@rfc-editor.org>;
>>>> gorry@erg.abdn.ac.uk;
>>>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>>>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org
>>>> Cc: ipv6@ietf.org
>>>>  Sent: Tuesday, 21 April 2015, 14:46
>>>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>>>
>>>> anyone care to comment?
>>>>
>>>> joel
>>>>
>>>>
>>>>
>>>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>>>> The following errata report has been submitted for RFC6936,
>>>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero
>>>>> Checksums".
>>>>>
>>>>> --------------------------------------
>>>>> You may review the report below and at:
>>>>> http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341
>>>>>
>>>>> --------------------------------------
>>>>> Type: Technical
>>>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>>>
>>>>> Section: 1.3.5
>>>>>
>>>>> Original Text
>>>>> -------------
>>>>> The ingress of a tunnel seeking to provide good
>>>>> entropy in the flow label field would therefore need to create a
>>>>> random flow label value and keep corresponding state so that all
>>>>> packets that were associated with a flow would be consistently given
>>>>> the same flow label.Â  Although possible, this complexity may not be
>>>>> desirable in a tunnel ingress.
>>>>>
>>>>> Corrected Text
>>>>> --------------
>>>>> The ingress of a tunnel seeking to provide good
>>>>> entropy in the flow label field would therefore need to create a
>>>>> pseudo-random flow label value using a stateless method
>>>>> as described in [RFC6438] so that all
>>>>> packets that were associated with a flow would be consistently given
>>>>> the same flow label.
>>>>>
>>>>> Notes
>>>>> -----
>>>>> It is incorrect that a stateful method is needed, and presumably that
>>>>> was the complexity judged undesirable. Also, we shouldn't say
>>>>> "random"
>>>>> when we mean "pseudo-random."
>>>>>
>>>>> Instructions:
>>>>> -------------
>>>>> This erratum is currently posted as "Reported". If necessary, please
>>>>> use "Reply All" to discuss whether it should be verified or
>>>>> rejected. When a decision is reached, the verifying party (IESG)
>>>>> can log in to change the status and edit the report, if necessary.
>>>>>
>>>>> --------------------------------------
>>>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>>>> --------------------------------------
>>>>> TitleÂ  Â  Â  Â  Â  Â  Â  : Applicability Statement for the Use of
>>>>> IPv6
>>>>> UDP Datagrams with Zero Checksums
>>>>> Publication DateÂ  Â  : April 2013
>>>>> Author(s)Â  Â  Â  Â  Â  : G. Fairhurst, M. Westerlund
>>>>> CategoryÂ  Â  Â  Â  Â  Â  : PROPOSED STANDARD
>>>>> SourceÂ  Â  Â  Â  Â  Â  Â  : IPv6 Maintenance
>>>>> AreaÂ  Â  Â  Â  Â  Â  Â  Â  : Internet
>>>>> StreamÂ  Â  Â  Â  Â  Â  Â  : IETF
>>>>> Verifying PartyÂ  Â  : IESG
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>



From nobody Tue Apr 21 09:47:52 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDEEA1B29C6 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 09:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 hhcI6yhNgc6h for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 09:47:49 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::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 0551A1B29D3 for <ipv6@ietf.org>; Tue, 21 Apr 2015 09:44:52 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so18188742ieb.3 for <ipv6@ietf.org>; Tue, 21 Apr 2015 09:44:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tCx+zdLqBYOhz99EQtxTrzEsoOmcfdH1+7euiujIsHM=; b=dRHGtr8s/WvOV9X5JDrTKNiU7U1qbrb8WoiJG3JOY84p1XAnopodL6CyrerkbkZOKy m7jbCVhSwPlPNesWQVnKSBySIsAgdDawJbIIzEzhwfr9Myl1Nx9r4UmVp4YzoAvevOHF x2G7WzoUirt+SxziTI6eykL5FKtdemgtxXLtFNjuipjTjSKMkIG90onEF1c+GWEtc2vA gruiBX7ODLt5GAcFgT+QJX8ZKrl6XnMMdWAWPdKxsSAXbarRtpfRC4OAgQC8Nvfuq7le 8pxMnI7CmZdY3CtnkOlTAlXLvy1Zw8OiLS5oRYyi1NkzbdiGj1On6ELNZGUwnzsYhvit TxAw==
MIME-Version: 1.0
X-Received: by 10.43.163.71 with SMTP id mn7mr4431759icc.72.1429634692421; Tue, 21 Apr 2015 09:44:52 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.50.80 with HTTP; Tue, 21 Apr 2015 09:44:52 -0700 (PDT)
In-Reply-To: <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>
Date: Tue, 21 Apr 2015 09:44:52 -0700
X-Google-Sender-Auth: 5piLhAc0dXI5g7A8YoBR0IK-Iek
Message-ID: <CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/OW6IxpCCtr5UGcJS9E5wpwtxsZ4>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 16:47:51 -0000

At Tue, 21 Apr 2015 10:35:15 +0900,
Lorenzo Colitti <lorenzo@google.com> wrote:

> I think the root of my objections to this draft is that it proposes what is
> in effect a substantial change to the current configuration model in IPv6
> networks without saying so explicitly.
[...]
> If I am incorrect and the document is not proposing such a model, then it
> should not mention this as a possibility. But then we need to understand
> where the power savings are.

I'm not sure if these points are too critical to adopt the document,
but I guess it may be related to the higher-level question that I
asked in response to this call:
http://www.ietf.org/mail-archive/web/ipv6/current/msg22411.html
(and that hasn't been answered).

I was not sure if we had agreed on sufficient need for making
non-trivial (if not substantial) changes to a core part of the
protocol.  If what Lorenzo was trying to say is a different form of
what I tried to ask, I tend to agree with part of his argument.
Although I'm not necessarily opposed to adopting the document just
because of that, I think it's reasonable to request clarifying the
problem statement and expected goal.

--
JINMEI, Tatuya


From nobody Tue Apr 21 10:02:27 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 358AA1B2850 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 10:02:26 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTp3dYkq0qMf for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 10:02:24 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 9F2FC1AD379 for <ipv6@ietf.org>; Tue, 21 Apr 2015 10:02:24 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3LH2Goc001936 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Apr 2015 10:02:16 -0700
Message-ID: <55368297.6080006@acm.org>
Date: Tue, 21 Apr 2015 10:02:15 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com>
In-Reply-To: <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVZYsvAMZjn2Da5uyqxf+RZNBaM8t93oTG48bzz/p5HCLtDjMNNZjWI8gAQRpMMwneTTTTXUVHlwh/eUzx+MDYXQ
X-Sonic-ID: C;SsGQKUjo5BG3N+VSju/ZCg== M;ZmiqKUjo5BG3N+VSju/ZCg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gnT6TdwEhIVrFHEWmUZK_L9XUvk>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 17:02:26 -0000

On 4/20/15 6:21 PM, Lorenzo Colitti wrote:
> On Tue, Apr 21, 2015 at 2:41 AM, Erik Nordmark <nordmark@acm.org 
> <mailto:nordmark@acm.org>> wrote:
>
>     On 4/20/15 6:54 AM, Lorenzo Colitti wrote:
>
>         But then the "timely and scalable reconfiguration
>         capabilities" cannot be maintained. The network can't tell
>         that host about any new information, because that host won't
>         receive it. The host will only receive it when it wakes up next.
>
>     The host will take no action on any state until it wakes up.
>     "timely" implies that hosts do not take any actions on stale
>     state, and with RS refresh they would not. Hence it is very "timely".
>
>     Note that without RS refresh hosts can take action on stale state
>     if the packet loss experienced by the RAs is such that they miss
>     e.g., the RAs that set the preferred lifetime for a prefix to
>     zero, or set the default router lifetime to zero. Thus RFC 4861
>     operates in a probabilistic mode - which made sense when all
>     networks were wires and one could assume the packet loss were
>     independent events. Walking out of range of a radio does not
>     result in independent events.
>
>     Thus using RS refresh makes the "timely" work better than in RFC 4861.
>
>
> Wait - are you arguing that soliciting information when the refresh 
> timer expires, or when the node wakes up, is more "timely" than the 
> network just sending an RA and having the node receive it? That 
> doesn't make sense.
No, that wasn't what I said. I'll repeat. (But perhaps it is better for 
me to explain this over the phone instead of bothering the whole list?)
1. If there is no packet loss then the RS refresh is as timely as the 
host waking up to receive the unsolicited RAs. This is because the host 
will not use any of the state from the RA until it is time for it to 
wake up.
2. In the presence of packet loss things are more complex, but it is 
clear that unsolicited RAs do not provide any time guarantees. One can 
only make a probabilistic argument (assuming independent event packet 
loss) of how likely it is for a host to have received the information 
after N RAs have been sent. RS refresh provides has a lower expected 
delay; the host will retransmit the RS (following resilient-RS 
retransmissions) until it gets an RA. With unsolicited RAs the host 
would be waiting up to 15 minutes (or 6 hours with a larger maxra) for a 
the next unsolicited RA. With RS refresh it would send a new RS after a 
second. If the host implementations don't act on the state until RS 
refresh has succeeded (or the host has detected it has moved to a 
different link and received the RAs for that link), then the amount of 
time during which the host operates on stale state becomes zero. But in 
practice a host might act on the, potentially stale, state after the 
first RS refresh.

Hence for hosts sleeping on a schedule
   if we don't care about packet loss, then unsolicited and refresh are 
the same.
   if we care about packet loss, then refresh has a lower average delay.

>
> If what you're saying is that the sleeping node is going to ignore RAs 
> anyway, then you don't need an RS refresh option for the node to send 
> an RS and receive an RA when it wakes up. That's already possible.
There is no RFC which suggests or recommends sending a RS after wakeup. 
RFC 4861 is very prescriptive on when RS can and can not be sent.


>
> If what you're saying is that the node won't receive the RA due to 
> general packet loss, then that can happen even for a solicited RA.
See above.

>
>         It depends how frequent the RAs are. In general purpose
>         networks, they might be more frequent. Also, any node joining
>         may cause a solicited multicast RA. Depending on the
>         application, "after 10 minutes" may be a lot better than "never".
>
>     For the network deployments where frequency of RAs is a concern,
>     the desire seems to be to increase the time.
>     If you read e.g. section 5.1 in
>     draft-yourtchenko-colitti-nd-reduce-multicast you'll see that.
>
>
> The document says that if you want to reduce multicast, you can 
> increase the RA interval. Personally, I don't think that makes sense, 
> because one RA every half hour is a tiny amount of traffic, which is 
> trivial on any general-purpose network.

IPv6 needs to apply to a large range of network technologies, just like 
IPv4 does.
I think that is the fundamental disconnect here.

>
>
>         What about points #2 and #3?
>
>     I think this email thread should about WG adoption and not WG last
>     call or even about WG discussion.
>     Are you arguing that all your points in the draft need to be
>     addressed to your satisfaction before it can even become a WG draft?
>     That isn't how an IETF working group is supposed to operate.
>
>
> No. I am worried that this document cannot meet its goals, and even if 
> it does not, after adoption we will be unable to abandon it and 
> instead ship something that does not meet its goals.
>
> Perhaps the issue here is that we don't agree on a problem statement, 
> or more accurately, what we're trying to accomplish with this drafts.

You've said that for > 2 years now, but never provided any useful 
suggestions.

AFAICT you are in the rough here. But up to the WG chairs to decide.

Regards,
    Erik

>
>     FWIW your #2 was a statement of fact, but not clear how it is
>     relevant to the discussion. Seems to be related to your assumption
>     that any multicast RA makes this null and void, which is incorrect.
>
>
> It is relevant to the discussion because the draft proposes a mode 
> where periodic multicast RAs are suppressed. My point #2 observes that 
> it's not possible to exit that mode because there is no way to know 
> whether legacy hosts have left the network.
>
>     #3 was AFAICT a restatement of your conclusion based on some
>     unstated assumptions. I already tried to guess at that unstated
>     assumption in my first respond and I responded based on that. Was
>     my guess wrong? Did I you make some other unstated assumptions?
>
>
> My assumption is that in order to allow nodes to be updated 
> dynamically, hosts will still need to listen to periodic RAs. If 
> you're saying that that's now optional, then that's quite a change to 
> the existing specs, and that statement should be made very very clear 
> in the draft.


From nobody Tue Apr 21 10:10:56 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36D4C1A0041 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 10:10:54 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FM_H1VAVNIwF for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 10:10:52 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 DAC0D1A0045 for <ipv6@ietf.org>; Tue, 21 Apr 2015 10:10:48 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3LHAhl9025921 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Apr 2015 10:10:43 -0700
Message-ID: <55368493.7090306@acm.org>
Date: Tue, 21 Apr 2015 10:10:43 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>
In-Reply-To: <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVaqGRyorhUhEF0K78OpwrKS9sQSOAZWXV45xmveYsdNs7cTepzeCrRMhUMJL/OthcZPBrD/JpCIxSxCyVl0XGdG
X-Sonic-ID: C;jvnLV0no5BGqNYY+Bvepxg== M;dNHgV0no5BGqNYY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/W__xRylNjG9pEfiDVhHDozkos4U>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 17:10:54 -0000

On 4/20/15 6:35 PM, Lorenzo Colitti wrote:
> On Sat, Mar 28, 2015 at 12:34 AM, Bob Hinden <bob.hinden@gmail.com 
> <mailto:bob.hinden@gmail.com>> wrote:
>
>     Title           : IPv6 Neighbor Discovery Optional Unicast RS/RA
>     Refresh
>
>
> All,
>
> I think the root of my objections to this draft is that it proposes 
> what is in effect a substantial change to the current configuration 
> model in IPv6 networks without saying so explicitly.
>
> Currently, we have an easy-to understand, easy-to-reason-about model: 
> periodic RAs periodically notify everyone on link of the current 
> configuration information, and nodes that don't want to wait for such 
> periodic configuration information can solicit said information by 
> sending a request.

Lorenzo,
which RFC states "nodes that don't want to wait for such periodic 
configuration information can solicit said information by sending a 
request"?
AFAIK that isn't allowed. If you do that you would be violating this 
MUST in RFC 4861:
    Once the host sends a Router Solicitation, and receives a valid
    Router Advertisement with a non-zero Router Lifetime, the host MUST
    desist from sending additional solicitations on that interface, until
    the next time one of the above events occurs.

>
> With this document, it's not clear what model is proposed.
AFAICT the document is clear on what it is proposing. If others find it 
unclear we can definitely add some wording.

You seem to disagree with the change in the model? Or perhaps you don't 
since the paragraph above seems to say that that the model already 
allows for "pull" by sending RSes? Even though that is not allowed in 
RFC 4861!!

So I'm confused by your statements.

Regards,
     Erik

>
> It seems to me that this document is proposing a model where there are 
> no periodic RAs being sent. That's something that can be proposed, but 
> if so, we need to carefully evaluate the implications to the 
> architecture, and how switching to such a model affects the properties 
> of the model we currently have. We also need to make sure we 
> understand how that model works for hosts that a) don't support either 
> resilient RS or this draft, b) support resilient RS but not this draft.
>
> If I am incorrect and the document is not proposing such a model, then 
> it should not mention this as a possibility. But then we need to 
> understand where the power savings are.
>
> Cheers,
> Lorenzo
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Tue Apr 21 10:23:26 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E06251A1BDF for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 10:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.634
X-Spam-Level: 
X-Spam-Status: No, score=-1.634 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 xi8iC792PGZM for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 10:23:23 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 238D51A1BCB for <ipv6@ietf.org>; Tue, 21 Apr 2015 10:23:23 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3LHNISI012941 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Apr 2015 10:23:18 -0700
Message-ID: <55368786.5000507@acm.org>
Date: Tue, 21 Apr 2015 10:23:18 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com> <CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com>
In-Reply-To: <CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030307010809080901050805"
X-Sonic-CAuth: UmFuZG9tSVZxC1RD9OPjKv1DQRw5bV/S15ldnw6uZWC79d969E6mUODVct/Kz+c/Vom4G/m+uuqQ+yEO5Tiadj+ab5TXyUbe
X-Sonic-ID: C;oPDMGUvo5BGwqIY+Bvepxg== M;yh/nGUvo5BGwqIY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1cGdJGosyNpEvLKigAv6l_M5IM4>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 17:23:25 -0000

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

On 4/21/15 9:44 AM, 神明達哉 wrote:
> At Tue, 21 Apr 2015 10:35:15 +0900,
> Lorenzo Colitti <lorenzo@google.com> wrote:
>
>> I think the root of my objections to this draft is that it proposes what is
>> in effect a substantial change to the current configuration model in IPv6
>> networks without saying so explicitly.
> [...]
>> If I am incorrect and the document is not proposing such a model, then it
>> should not mention this as a possibility. But then we need to understand
>> where the power savings are.
> I'm not sure if these points are too critical to adopt the document,
> but I guess it may be related to the higher-level question that I
> asked in response to this call:
> http://www.ietf.org/mail-archive/web/ipv6/current/msg22411.html
> (and that hasn't been answered).
Jinmei,

Your email had some editorial corrections, which will be applied.

The question seemed to be addressed to the WG and not the authors, which 
is a sad excuse for not responding.
Your question was:

I think it's worth discussing so I support the adoption.  But I have
one higher level question: did we agree that we need some enhancements
to ND to address the concern of multicast overhead?  It's quite
possible that I missed something in previous discussions, but I
thought there was not a clear consensus for the need for protocol
level changes while we generally saw potential issues in this area.


It is up to the WG chairs to gauge consensus, and I don't think there 
has been any explicit call on whether we need work to reduce ND 
multicast in general. (There are various techniques which can already be 
used such as setting O=0 to avoid multicast NS from hosts, and adjust 
timers, etc).

My personal take is that we don't need any open-ended protocol work 
here, but it would useful to have some (v6ops?) documents with 
operational recommendations e.g. for WiFi networks. Others have 
expressed concerns that for WiFI vendors are busy implementing various 
forms of filtering of multicast, and it isn't clear to what extent those 
solutions/hacks (depending on your point of view) will cause problems in 
the future. Hence some recommendations would be helpful.

One separate output of the efficient-nd design team is that we need to 
ask the WG whether there is interest in improving DAD, but that is more 
about DAD robustness than efficiency. I had that question on the slides 
in Dallas, but the question wasn't asked of the room. Bob and Ole 
suggested we do that question on the mailing list.

>
> I was not sure if we had agreed on sufficient need for making
> non-trivial (if not substantial) changes to a core part of the
> protocol.  If what Lorenzo was trying to say is a different form of
> what I tried to ask, I tend to agree with part of his argument.
> Although I'm not necessarily opposed to adopting the document just
> because of that, I think it's reasonable to request clarifying the
> problem statement and expected goal.

Please send text on what you would want to see as (part of) PS and goals.

Thanks,
    Erik

>
> --
> JINMEI, Tatuya
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


--------------030307010809080901050805
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">
    <div class="moz-cite-prefix">On 4/21/15 9:44 AM, 神明達哉 wrote:<br>
    </div>
    <blockquote
cite="mid:CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com"
      type="cite">
      <pre wrap="">At Tue, 21 Apr 2015 10:35:15 +0900,
Lorenzo Colitti <a class="moz-txt-link-rfc2396E" href="mailto:lorenzo@google.com">&lt;lorenzo@google.com&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">I think the root of my objections to this draft is that it proposes what is
in effect a substantial change to the current configuration model in IPv6
networks without saying so explicitly.
</pre>
      </blockquote>
      <pre wrap="">[...]
</pre>
      <blockquote type="cite">
        <pre wrap="">If I am incorrect and the document is not proposing such a model, then it
should not mention this as a possibility. But then we need to understand
where the power savings are.
</pre>
      </blockquote>
      <pre wrap="">
I'm not sure if these points are too critical to adopt the document,
but I guess it may be related to the higher-level question that I
asked in response to this call:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/ipv6/current/msg22411.html">http://www.ietf.org/mail-archive/web/ipv6/current/msg22411.html</a>
(and that hasn't been answered).</pre>
    </blockquote>
    Jinmei,<br>
    <br>
    Your email had some editorial corrections, which will be applied.<br>
    <br>
    The question seemed to be addressed to the WG and not the authors,
    which is a sad excuse for not responding.<br>
    Your question was:<br>
    <meta charset="utf-8">
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">I think it's worth discussing so I support the adoption.  But I have
one higher level question: did we agree that we need some enhancements
to ND to address the concern of multicast overhead?  It's quite
possible that I missed something in previous discussions, but I
thought there was not a clear consensus for the need for protocol
level changes while we generally saw potential issues in this area.
</pre>
    <br class="Apple-interchange-newline">
    It is up to the WG chairs to gauge consensus, and I don't think
    there has been any explicit call on whether we need work to reduce
    ND multicast in general. (There are various techniques which can
    already be used such as setting O=0 to avoid multicast NS from
    hosts, and adjust timers, etc). <br>
    <br>
    My personal take is that we don't need any open-ended protocol work
    here, but it would useful to have some (v6ops?) documents with
    operational recommendations e.g. for WiFi networks. Others have
    expressed concerns that for WiFI vendors are busy implementing
    various forms of filtering of multicast, and it isn't clear to what
    extent those solutions/hacks (depending on your point of view) will
    cause problems in the future. Hence some recommendations would be
    helpful.<br>
    <br>
    One separate output of the efficient-nd design team is that we need
    to ask the WG whether there is interest in improving DAD, but that
    is more about DAD robustness than efficiency. I had that question on
    the slides in Dallas, but the question wasn't asked of the room. Bob
    and Ole suggested we do that question on the mailing list.<br>
    <br>
    <blockquote
cite="mid:CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com"
      type="cite">
      <pre wrap="">

I was not sure if we had agreed on sufficient need for making
non-trivial (if not substantial) changes to a core part of the
protocol.  If what Lorenzo was trying to say is a different form of
what I tried to ask, I tend to agree with part of his argument.
Although I'm not necessarily opposed to adopting the document just
because of that, I think it's reasonable to request clarifying the
problem statement and expected goal.</pre>
    </blockquote>
    <br>
    Please send text on what you would want to see as (part of) PS and
    goals.<br>
    <br>
    Thanks,<br>
       Erik<br>
    <br>
    <blockquote
cite="mid:CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com"
      type="cite">
      <pre wrap="">

--
JINMEI, Tatuya

--------------------------------------------------------------------
IETF IPv6 working group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>
Administrative Requests: <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a>
--------------------------------------------------------------------

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030307010809080901050805--


From nobody Tue Apr 21 11:21:23 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 666BD1A0084 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 11:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.635
X-Spam-Level: 
X-Spam-Status: No, score=-1.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 rjrGf9gkU4k8 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 11:21:21 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 0B59B1A8838 for <ipv6@ietf.org>; Tue, 21 Apr 2015 11:21:21 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3LILH0R004261 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Apr 2015 11:21:17 -0700
Message-ID: <5536951D.60102@acm.org>
Date: Tue, 21 Apr 2015 11:21:17 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com> <CAJE_bqdh8aUzmF7UkBgicMNAM_YHBLQ5DYyuimbu9EY=d6T0Sg@mail.gmail.com>
In-Reply-To: <CAJE_bqdh8aUzmF7UkBgicMNAM_YHBLQ5DYyuimbu9EY=d6T0Sg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVaWPCJtPtcuklmSnf9fFRtZJXqm2WmsaEokdldBQ29x0yeW2baPS0DlfpvP1tDWGO+j9p8W9fVP5V0RDASLMyqN
X-Sonic-ID: C;oibSM1Po5BGq34Y+Bvepxg== M;fAXnM1Po5BGq34Y+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/S-BWnRSPadvwOS8RMmZuOMP8Cao>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 18:21:22 -0000

Jinmei,

Thanks for your comments.
Responses below.

On 4/10/15 9:57 AM, 神明達哉 wrote:
>
>
> On the draft itself, I have a few minor comments:
>
> - Section 5:
>     Refresh Time:  16-bit unsigned integer.  Units is seconds.  The all-
>                    ones value (65535) means infinite.
>
> What should the host do if this is 0?  Should it just keep sending
> RSes? (I'm joking).
Good catch. I'm inclined to just make zero be reserved, and state that 
hosts should ignore an RTO if the Refresh Time is zero - i.e. treat the 
RA as if the RTO was not present.
Is that sufficient?

We could pick some arbitrary number (10 seconds?) and say that it is a 
lower bound, but I don't know how to pick such a number.

>
> - Section 7: remove 'section'.
>     [...]  Note that section
>     Section 9 says that routers SHOULD report such inconsistencies to
>     system management.
Fixed.

>
> - Section 8.2: s/be be/may be/ (?)
>
>     [...]  That be be performed at deployment time (e.g., only
>     hosts which are known to support RTO are configured with the layer 2
>     security keys), or the routers detect any RSs which do not include
I think "could be" is better since it avoids potential confusion with 
uppercase MAY.
>
> - Section 8.3: remove '.' before 'Note':
>
>     .  Note that such new information is not likely to reach sleeping
>     hosts until those hosts refresh by sending a RS.
Fixed.

Thanks,
    Erik

>
> --
> JINMEI, Tatuya
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Tue Apr 21 11:51:19 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72271A8931 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 11:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 mJMH44ycPWYD for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001: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 A9C6A1A1B3E for <ipv6@ietf.org>; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
Received: by iget9 with SMTP id t9so90918500ige.1 for <ipv6@ietf.org>; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=D1RjKc20ktana1M3Cwu9XQTCs6cgdiG697R2w+xodcw=; b=PVMAI1HxuaWuvFxIiaZYpqt2uYPjwsrz+nQacba0JO124GOJC0NQ4zgeWJ116qNmqD /5ehvJvKaqNWpZXMGfM5f8JblPmK6Sw+660UFlyOrKZmwCmCC12Ri8UTZD6URWLL9s3a PqKhHi77VEtIpGU0ojPFHjo7nGYTH7tb0g6fwBZiby/zJXyfxwR3qWNGdxb/kEWagOzM pIzdEajGrI7VpmFxOTt1ufKCxRNfQI568Y0OI2Rj8WGhiEjavoQfmUEnjbHtdxOztobG 05ALTwOdpt3ruQK/aSOQqhH66eN4hsLOX//mGP+YpiBxgfVWawb1e9/fwewMxk1/8okJ QDEw==
MIME-Version: 1.0
X-Received: by 10.42.128.84 with SMTP id l20mr5316216ics.21.1429642276213; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.50.80 with HTTP; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
In-Reply-To: <5536951D.60102@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com> <CAJE_bqdh8aUzmF7UkBgicMNAM_YHBLQ5DYyuimbu9EY=d6T0Sg@mail.gmail.com> <5536951D.60102@acm.org>
Date: Tue, 21 Apr 2015 11:51:16 -0700
X-Google-Sender-Auth: TsYcYv3m8cJMhfIvpilUdgDE4ds
Message-ID: <CAJE_bqdDYFVuBSB6OVSpiOo1CW8PM+ajzcAuqo78gnP82pn3xw@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Erik Nordmark <nordmark@acm.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TCygcBsmQL7kQL9dyJX3Tpmzmys>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 18:51:17 -0000

At Tue, 21 Apr 2015 11:21:17 -0700,
Erik Nordmark <nordmark@acm.org> wrote:

> > - Section 5:
> >     Refresh Time:  16-bit unsigned integer.  Units is seconds.  The all-
> >                    ones value (65535) means infinite.
> >
> > What should the host do if this is 0?  Should it just keep sending
> > RSes? (I'm joking).
> Good catch. I'm inclined to just make zero be reserved, and state that
> hosts should ignore an RTO if the Refresh Time is zero - i.e. treat the
> RA as if the RTO was not present.
> Is that sufficient?

I think so.

> We could pick some arbitrary number (10 seconds?) and say that it is a
> lower bound, but I don't know how to pick such a number.

Some more conservative lower bound may also help, but I don't know how
to pick one either.  It's probably enough if you add a note that care
should be taken if this field is set to some small value so it won't
cause unexpected RS storm.

> > - Section 8.2: s/be be/may be/ (?)
> >
> >     [...]  That be be performed at deployment time (e.g., only
> >     hosts which are known to support RTO are configured with the layer 2
> >     security keys), or the routers detect any RSs which do not include
> I think "could be" is better since it avoids potential confusion with
> uppercase MAY.

I'm fine with 'could be'.

--
JINMEI, Tatuya


From nobody Tue Apr 21 17:17:15 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD8F1B2F32 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 17:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001] autolearn=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 gIjFqXus-SmY for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 17:17:12 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::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 935AA1B2F31 for <ipv6@ietf.org>; Tue, 21 Apr 2015 17:17:12 -0700 (PDT)
Received: by pacyx8 with SMTP id yx8so255942797pac.1 for <ipv6@ietf.org>; Tue, 21 Apr 2015 17:17:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QRg7DhReF7zXIu4nBXgmFSwoZ4ndHkGpKU8SMG3GPAk=; b=bx1bMnyPIQTIOlxVzLdjRZH0ArpVrBtltT0mzJyb+EbPKpNAL4jtZKPXU5KUt5X6dV /YPDohJ+g6I2NYKx868rw8wzl+xrbK7PfiHX3TT7lodyJMDVMBPRwNhkzI+Z+QpkKs32 O2ssGBpJk/ac7ZYnU9r4kR/NlWVjEjOOPBaPNiE7gM/UlO5QYvHztR9fUXjxvfsbfHvp 39OBaO1PPCPuVE9lyeZvL+m1uJDx07TciuzmlQjsnt4kde3VoeQmvMeFJa48SIhVJhAz HOd2vMnV+SMNcixOqFD0D0ZDnHMd6QMRTWQZLlLsjJtTnJ84FUFL7YGSiDVkPzKIZdZI ZFug==
X-Received: by 10.70.45.79 with SMTP id k15mr42460873pdm.78.1429661832225; Tue, 21 Apr 2015 17:17:12 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by mx.google.com with ESMTPSA id wh6sm3099487pbc.96.2015.04.21.17.17.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Apr 2015 17:17:11 -0700 (PDT)
Message-ID: <5536E887.7090806@gmail.com>
Date: Wed, 22 Apr 2015 12:17:11 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>,  Magnus Westerlund <magnus.westerlund@ericsson.com>, gorry@erg.abdn.ac.uk, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net>
In-Reply-To: <55363D89.2070001@innovationslab.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/MKkSHqASAoAy8WiUB8DM5qNB8io>
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "terry.manderson@icann.org" <terry.manderson@icann.org>, "ipv6@ietf.org" <ipv6@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 00:17:14 -0000

On 22/04/2015 00:07, Brian Haberman wrote:
> Hi all,
>      While I agree with the sentiment that the proposed updated text is=

> more appropriate, we are on a slippery slope as to this being errata.
> This is a technical change and not fixing an error.  Can someone point
> to a discussion where a reference to 6438 and stateless methods occurre=
d
> and there was consensus to put that in 1.3.5?
>=20
>      If not, this seems more like a new draft to obsolete 6936.

Good point. How about "hold for document update" to resolve the
open errata report?

Mea culpa, because I didn't ever review that part of
draft-ietf-6man-udpzero.

    Brian C

> Regards,
> Brian
>=20
> On 4/21/15 4:45 AM, Magnus Westerlund wrote:
>> I also support approving this Errata.
>>
>> Cheers
>>
>> Magnus
>>
>> gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
>>> I agree with this update. I think it is a useful correction.
>>>
>>> Gorry
>>>
>>>> I agree with Brian's update, I think stateless LB is better.
>>>> (Strangely and coincidently, my OpenWRT router reported I received o=
ne
>>>> today:
>>>> [ =C3=82 422.320000] IPv6: udp checksum is 0
>>>>
>>>> )
>>>>
>>>>
>>>> Regards,Mark.
>>>>       From: joel jaeggli <joelja@bogus.com>
>>>>  To: RFC Errata System <rfc-editor@rfc-editor.org>; gorry@erg.abdn.a=
c.uk;
>>>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>>>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.or=
g
>>>> Cc: ipv6@ietf.org
>>>>  Sent: Tuesday, 21 April 2015, 14:46
>>>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>>>
>>>> anyone care to comment?
>>>>
>>>> joel
>>>>
>>>>
>>>>
>>>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>>>> The following errata report has been submitted for RFC6936,
>>>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zer=
o
>>>>> Checksums".
>>>>>
>>>>> --------------------------------------
>>>>> You may review the report below and at:
>>>>> http://www.rfc-editor.org/errata_search.php?rfc=3D6936&eid=3D4341
>>>>>
>>>>> --------------------------------------
>>>>> Type: Technical
>>>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>>>
>>>>> Section: 1.3.5
>>>>>
>>>>> Original Text
>>>>> -------------
>>>>> The ingress of a tunnel seeking to provide good
>>>>> entropy in the flow label field would therefore need to create a
>>>>> random flow label value and keep corresponding state so that all
>>>>> packets that were associated with a flow would be consistently give=
n
>>>>> the same flow label.=C3=82  Although possible, this complexity may =
not be
>>>>> desirable in a tunnel ingress.
>>>>>
>>>>> Corrected Text
>>>>> --------------
>>>>> The ingress of a tunnel seeking to provide good
>>>>> entropy in the flow label field would therefore need to create a
>>>>> pseudo-random flow label value using a stateless method
>>>>> as described in [RFC6438] so that all
>>>>> packets that were associated with a flow would be consistently give=
n
>>>>> the same flow label.
>>>>>
>>>>> Notes
>>>>> -----
>>>>> It is incorrect that a stateful method is needed, and presumably th=
at
>>>>> was the complexity judged undesirable. Also, we shouldn't say "rand=
om"
>>>>> when we mean "pseudo-random."
>>>>>
>>>>> Instructions:
>>>>> -------------
>>>>> This erratum is currently posted as "Reported". If necessary, pleas=
e
>>>>> use "Reply All" to discuss whether it should be verified or
>>>>> rejected. When a decision is reached, the verifying party (IESG)
>>>>> can log in to change the status and edit the report, if necessary.
>>>>>
>>>>> --------------------------------------
>>>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>>>> --------------------------------------
>>>>> Title=C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  : Appl=
icability Statement for the Use of IPv6
>>>>> UDP Datagrams with Zero Checksums
>>>>> Publication Date=C3=82  =C3=82  : April 2013
>>>>> Author(s)=C3=82  =C3=82  =C3=82  =C3=82  =C3=82  : G. Fairhurst, M.=
 Westerlund
>>>>> Category=C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  : PROPOSED =
STANDARD
>>>>> Source=C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  : IPv=
6 Maintenance
>>>>> Area=C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82 =
 : Internet
>>>>> Stream=C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  =C3=82  : IET=
F
>>>>> Verifying Party=C3=82  =C3=82  : IESG
>>>>>
>>>>> -------------------------------------------------------------------=
-
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6=

>>>>> -------------------------------------------------------------------=
-
>>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------=

>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------=

>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Wed Apr 22 00:38:58 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD851B3303 for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 00:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unLIM49OQqux for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 00:38:55 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 860321B32FF for <ipv6@ietf.org>; Wed, 22 Apr 2015 00:38:50 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 42C29613E; Wed, 22 Apr 2015 00:38:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=yuXHM6xrfAsrbiPAsYujILDm1RA=; b= kYWMbmrdpuYqc5e7LQa/9lL5LN3iuLHej/FTxFe+/z3yUvMDGm/EziKUsHokF1Ra MO/4yizHHy0mrPzpggmXb74yUoNQL/l72s1JtSV7rc6Xc2kIw9zecNxcx45Jpwwy cNvneX7zZikWvXATJTcyHusDntHgZmAc1uDYTemtdXQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=DR9X1Madd0o/TX7f9MwfxnSchZ gFPbz9aU7KdNfOPFl5Rru4MDZUaIGT7jVmL+Gy6PSutjH/gxF3q7JvoZtAgB72uI j5m6WBH3F86uTlb44wuJopGm0fUX4J/8CaShPha3dvBbguhvmLAFpGupNd5sz8XB sbSW/N5PLlHFighVc=
Received: from gomlefisk.localdomain (unknown [173.38.220.50]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id EC57160CC; Wed, 22 Apr 2015 00:38:48 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 31FAB430627B; Wed, 22 Apr 2015 09:38:46 +0200 (CEST)
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F8CF4D24-3084-4090-9729-F03959B51B20"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <55363D89.2070001@innovationslab.net>
Date: Wed, 22 Apr 2015 09:38:45 +0200
Message-Id: <F32F3D44-F1E3-426F-AB6F-C4AEDCCBF81A@employees.org>
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HwGPpo2W5clGsybtl-q2dzs_6S8>
Cc: gorry@erg.abdn.ac.uk, 6man WG <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 07:38:57 -0000

--Apple-Mail=_F8CF4D24-3084-4090-9729-F03959B51B20
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Brian,

>     While I agree with the sentiment that the proposed updated text is
> more appropriate, we are on a slippery slope as to this being errata.
> This is a technical change and not fixing an error.  Can someone point
> to a discussion where a reference to 6438 and stateless methods =
occurred
> and there was consensus to put that in 1.3.5?
>=20
>     If not, this seems more like a new draft to obsolete 6936.

I do see your point of view. technical errata are always going to be a =
judgement call.
I think we also need to consider the alternatives. the cost and energy =
required to re-issue a new document is quite high. the risk of not =
accepting this as an errata, is that the issue will be dropped and =
forgotten.

looking at:
http://www.ietf.org/iesg/statement/errata-processing.html

the important point here is if this issue creates "deployment problems =
or significant confusion=94.

I think it might do that.

with regards to the issue if this changes consensus or not. the IETF =
published RFC6438 prior to this document, with consensus that there are =
stateless methods calculating the flow label. it is an error in 6936 =
requiring a stateful method. I see no indication anywhere that the =
intention of 6936 was to change the 6438 consensus.

cheers,
Ole

--Apple-Mail=_F8CF4D24-3084-4090-9729-F03959B51B20
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

iQEcBAEBCgAGBQJVN1AFAAoJEFuJXizso86gVq8H/RRHhCRWhymbF0w18fRZ3lvT
dGL7mQG5y/B2rMWw0IT23De1yORojuISLuyoHHnl2byTtQ//S7zpcFN5Xu96CjFX
GBsVozLUWxzSpr92zyrMeVAKIBbPXcEISoyoRQohaFfuKlqYSa0ozxZCK5AguYAG
X1pjmS0/pIb5J9ro8RAwklqDSJXRFCCmfgXwpgqsYv9TzU/vCYeMc2GuHJJ/vxJ9
sfKMZ2EyNO4tVtJuS4BVmdLQ+dzqaaOwMefzs0nLVe30HGjTmvPagNIlqkB1LSZ+
JW+UBpQu+F+XvoJKPXlGWklJ6OkqNmAibIqVPDQK17DkkvXjbSeVrKcsJ0QAzDQ=
=SuaK
-----END PGP SIGNATURE-----

--Apple-Mail=_F8CF4D24-3084-4090-9729-F03959B51B20--


From nobody Wed Apr 22 01:24:59 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F34EE1B32F4 for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 00:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.611
X-Spam-Level: 
X-Spam-Status: No, score=-3.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P_HgxodVzqWv for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 00:45:44 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id CAC371B3315 for <ipv6@ietf.org>; Wed, 22 Apr 2015 00:45:41 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 563AA1B0028A; Wed, 22 Apr 2015 08:45:15 +0100 (BST)
Received: from 130.243.28.162 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Wed, 22 Apr 2015 08:44:58 +0100
Message-ID: <a9940d969da03d4550e330934fd4b61c.squirrel@erg.abdn.ac.uk>
In-Reply-To: <5536E887.7090806@gmail.com>
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net> <5536E887.7090806@gmail.com>
Date: Wed, 22 Apr 2015 08:44:58 +0100
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
From: gorry@erg.abdn.ac.uk
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wMMVJShj7hfMsw9AgRrKAz9H5dY>
X-Mailman-Approved-At: Wed, 22 Apr 2015 01:24:58 -0700
Cc: gorry@erg.abdn.ac.uk, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "terry.manderson@icann.org" <terry.manderson@icann.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 07:45:47 -0000

I wish to change my opinion also (SORRY): I prefer to hold.

To be clear:

* "random" was indeed intended to mean "pseudorandom".

* RFC6936 references ECMP [RFC6438 ] flow marking - seeking to say this
was desirable, but not always practical at present. This was written in
parallel with RFC6438.

* RFC6936 only used a stateful ECMP example. It would have been better to
also mention stateless mapping, there is no reason why this was not
included.

However - I do not think the Errata would change the meaning, and the
clarification is not "clear". Simply changing a couple of words confuses
the meaning of the surrounding paragraphs

Gorry

> On 22/04/2015 00:07, Brian Haberman wrote:
>> Hi all,
>>      While I agree with the sentiment that the proposed updated text is
>> more appropriate, we are on a slippery slope as to this being errata.
>> This is a technical change and not fixing an error.  Can someone point
>> to a discussion where a reference to 6438 and stateless methods occurred
>> and there was consensus to put that in 1.3.5?
>>
>>      If not, this seems more like a new draft to obsolete 6936.
>
> Good point. How about "hold for document update" to resolve the
> open errata report?
>
> Mea culpa, because I didn't ever review that part of
> draft-ietf-6man-udpzero.
>
>     Brian C
>
>> Regards,
>> Brian
>>
>> On 4/21/15 4:45 AM, Magnus Westerlund wrote:
>>> I also support approving this Errata.
>>>
>>> Cheers
>>>
>>> Magnus
>>>
>>> gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
>>>> I agree with this update. I think it is a useful correction.
>>>>
>>>> Gorry
>>>>
>>>>> I agree with Brian's update, I think stateless LB is better.
>>>>> (Strangely and coincidently, my OpenWRT router reported I received
>>>>> one
>>>>> today:
>>>>> [ Â 422.320000] IPv6: udp checksum is 0
>>>>>
>>>>> )
>>>>>
>>>>>
>>>>> Regards,Mark.
>>>>>       From: joel jaeggli <joelja@bogus.com>
>>>>>  To: RFC Errata System <rfc-editor@rfc-editor.org>;
>>>>> gorry@erg.abdn.ac.uk;
>>>>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>>>>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org
>>>>> Cc: ipv6@ietf.org
>>>>>  Sent: Tuesday, 21 April 2015, 14:46
>>>>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>>>>
>>>>> anyone care to comment?
>>>>>
>>>>> joel
>>>>>
>>>>>
>>>>>
>>>>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>>>>> The following errata report has been submitted for RFC6936,
>>>>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero
>>>>>> Checksums".
>>>>>>
>>>>>> --------------------------------------
>>>>>> You may review the report below and at:
>>>>>> http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341
>>>>>>
>>>>>> --------------------------------------
>>>>>> Type: Technical
>>>>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>>>>
>>>>>> Section: 1.3.5
>>>>>>
>>>>>> Original Text
>>>>>> -------------
>>>>>> The ingress of a tunnel seeking to provide good
>>>>>> entropy in the flow label field would therefore need to create a
>>>>>> random flow label value and keep corresponding state so that all
>>>>>> packets that were associated with a flow would be consistently given
>>>>>> the same flow label.Â  Although possible, this complexity may not
>>>>>> be
>>>>>> desirable in a tunnel ingress.
>>>>>>
>>>>>> Corrected Text
>>>>>> --------------
>>>>>> The ingress of a tunnel seeking to provide good
>>>>>> entropy in the flow label field would therefore need to create a
>>>>>> pseudo-random flow label value using a stateless method
>>>>>> as described in [RFC6438] so that all
>>>>>> packets that were associated with a flow would be consistently given
>>>>>> the same flow label.
>>>>>>
>>>>>> Notes
>>>>>> -----
>>>>>> It is incorrect that a stateful method is needed, and presumably
>>>>>> that
>>>>>> was the complexity judged undesirable. Also, we shouldn't say
>>>>>> "random"
>>>>>> when we mean "pseudo-random."
>>>>>>
>>>>>> Instructions:
>>>>>> -------------
>>>>>> This erratum is currently posted as "Reported". If necessary, please
>>>>>> use "Reply All" to discuss whether it should be verified or
>>>>>> rejected. When a decision is reached, the verifying party (IESG)
>>>>>> can log in to change the status and edit the report, if necessary.
>>>>>>
>>>>>> --------------------------------------
>>>>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>>>>> --------------------------------------
>>>>>> TitleÂ  Â  Â  Â  Â  Â  Â  : Applicability Statement for the
>>>>>> Use of IPv6
>>>>>> UDP Datagrams with Zero Checksums
>>>>>> Publication DateÂ  Â  : April 2013
>>>>>> Author(s)Â  Â  Â  Â  Â  : G. Fairhurst, M. Westerlund
>>>>>> CategoryÂ  Â  Â  Â  Â  Â  : PROPOSED STANDARD
>>>>>> SourceÂ  Â  Â  Â  Â  Â  Â  : IPv6 Maintenance
>>>>>> AreaÂ  Â  Â  Â  Â  Â  Â  Â  : Internet
>>>>>> StreamÂ  Â  Â  Â  Â  Â  Â  : IETF
>>>>>> Verifying PartyÂ  Â  : IESG
>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list
>>>>>> ipv6@ietf.org
>>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>


From nobody Wed Apr 22 01:25:00 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BFB1B3320 for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 00:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.311
X-Spam-Level: 
X-Spam-Status: No, score=-1.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 jIs633CThVyw for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 00:45:49 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 152B81B331D for <ipv6@ietf.org>; Wed, 22 Apr 2015 00:45:49 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 84EF11B00401; Wed, 22 Apr 2015 08:45:54 +0100 (BST)
Received: from 130.243.28.162 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Wed, 22 Apr 2015 08:45:07 +0100
Message-ID: <1b12bb1e46aad7c5cdf5a10d2c2c85bb.squirrel@erg.abdn.ac.uk>
In-Reply-To: <5536E887.7090806@gmail.com>
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net> <5536E887.7090806@gmail.com>
Date: Wed, 22 Apr 2015 08:45:07 +0100
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
From: gorry@erg.abdn.ac.uk
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/boKxK2ChEYPdRy-gATadRDxB8E4>
X-Mailman-Approved-At: Wed, 22 Apr 2015 01:24:58 -0700
Cc: gorry@erg.abdn.ac.uk, Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "terry.manderson@icann.org" <terry.manderson@icann.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 07:45:50 -0000

I wish to change my opinion also (SORRY): I prefer to hold.

To be clear:

* "random" was indeed intended to mean "pseudorandom".

* RFC6936 references ECMP [RFC6438 ] flow marking - seeking to say this
was desirable, but not always practical at present. This was written in
parallel with RFC6438.

* RFC6936 only used a stateful ECMP example. It would have been better to
also mention stateless mapping, there is no reason why this was not
included.

However - I do not think the Errata would change the meaning, and the
clarification is not "clear". Simply changing a couple of words confuses
the meaning of the surrounding paragraphs

Gorry

> On 22/04/2015 00:07, Brian Haberman wrote:
>> Hi all,
>>      While I agree with the sentiment that the proposed updated text is
>> more appropriate, we are on a slippery slope as to this being errata.
>> This is a technical change and not fixing an error.  Can someone point
>> to a discussion where a reference to 6438 and stateless methods occurred
>> and there was consensus to put that in 1.3.5?
>>
>>      If not, this seems more like a new draft to obsolete 6936.
>
> Good point. How about "hold for document update" to resolve the
> open errata report?
>
> Mea culpa, because I didn't ever review that part of
> draft-ietf-6man-udpzero.
>
>     Brian C
>
>> Regards,
>> Brian
>>
>> On 4/21/15 4:45 AM, Magnus Westerlund wrote:
>>> I also support approving this Errata.
>>>
>>> Cheers
>>>
>>> Magnus
>>>
>>> gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
>>>> I agree with this update. I think it is a useful correction.
>>>>
>>>> Gorry
>>>>
>>>>> I agree with Brian's update, I think stateless LB is better.
>>>>> (Strangely and coincidently, my OpenWRT router reported I received
>>>>> one
>>>>> today:
>>>>> [ Â 422.320000] IPv6: udp checksum is 0
>>>>>
>>>>> )
>>>>>
>>>>>
>>>>> Regards,Mark.
>>>>>       From: joel jaeggli <joelja@bogus.com>
>>>>>  To: RFC Errata System <rfc-editor@rfc-editor.org>;
>>>>> gorry@erg.abdn.ac.uk;
>>>>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>>>>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org
>>>>> Cc: ipv6@ietf.org
>>>>>  Sent: Tuesday, 21 April 2015, 14:46
>>>>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>>>>
>>>>> anyone care to comment?
>>>>>
>>>>> joel
>>>>>
>>>>>
>>>>>
>>>>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>>>>> The following errata report has been submitted for RFC6936,
>>>>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero
>>>>>> Checksums".
>>>>>>
>>>>>> --------------------------------------
>>>>>> You may review the report below and at:
>>>>>> http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341
>>>>>>
>>>>>> --------------------------------------
>>>>>> Type: Technical
>>>>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>>>>
>>>>>> Section: 1.3.5
>>>>>>
>>>>>> Original Text
>>>>>> -------------
>>>>>> The ingress of a tunnel seeking to provide good
>>>>>> entropy in the flow label field would therefore need to create a
>>>>>> random flow label value and keep corresponding state so that all
>>>>>> packets that were associated with a flow would be consistently given
>>>>>> the same flow label.Â  Although possible, this complexity may not
>>>>>> be
>>>>>> desirable in a tunnel ingress.
>>>>>>
>>>>>> Corrected Text
>>>>>> --------------
>>>>>> The ingress of a tunnel seeking to provide good
>>>>>> entropy in the flow label field would therefore need to create a
>>>>>> pseudo-random flow label value using a stateless method
>>>>>> as described in [RFC6438] so that all
>>>>>> packets that were associated with a flow would be consistently given
>>>>>> the same flow label.
>>>>>>
>>>>>> Notes
>>>>>> -----
>>>>>> It is incorrect that a stateful method is needed, and presumably
>>>>>> that
>>>>>> was the complexity judged undesirable. Also, we shouldn't say
>>>>>> "random"
>>>>>> when we mean "pseudo-random."
>>>>>>
>>>>>> Instructions:
>>>>>> -------------
>>>>>> This erratum is currently posted as "Reported". If necessary, please
>>>>>> use "Reply All" to discuss whether it should be verified or
>>>>>> rejected. When a decision is reached, the verifying party (IESG)
>>>>>> can log in to change the status and edit the report, if necessary.
>>>>>>
>>>>>> --------------------------------------
>>>>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>>>>> --------------------------------------
>>>>>> TitleÂ  Â  Â  Â  Â  Â  Â  : Applicability Statement for the
>>>>>> Use of IPv6
>>>>>> UDP Datagrams with Zero Checksums
>>>>>> Publication DateÂ  Â  : April 2013
>>>>>> Author(s)Â  Â  Â  Â  Â  : G. Fairhurst, M. Westerlund
>>>>>> CategoryÂ  Â  Â  Â  Â  Â  : PROPOSED STANDARD
>>>>>> SourceÂ  Â  Â  Â  Â  Â  Â  : IPv6 Maintenance
>>>>>> AreaÂ  Â  Â  Â  Â  Â  Â  Â  : Internet
>>>>>> StreamÂ  Â  Â  Â  Â  Â  Â  : IETF
>>>>>> Verifying PartyÂ  Â  : IESG
>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list
>>>>>> ipv6@ietf.org
>>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>


From nobody Wed Apr 22 05:09:34 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4940A1A92AC for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 05:09:31 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mfZNRFHhriZr for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 05:09:29 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 643641B3508 for <ipv6@ietf.org>; Wed, 22 Apr 2015 05:09:29 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 28B18880EA; Wed, 22 Apr 2015 05:09:29 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 411BE13682B0; Wed, 22 Apr 2015 05:09:28 -0700 (PDT)
Message-ID: <55378F71.2070906@innovationslab.net>
Date: Wed, 22 Apr 2015 08:09:21 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net> <F32F3D44-F1E3-426F-AB6F-C4AEDCCBF81A@employees.org>
In-Reply-To: <F32F3D44-F1E3-426F-AB6F-C4AEDCCBF81A@employees.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AO2kpUputdNVejnRe93i72OxOUTCbjaEg"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WKkZG0dTWBb4p_J3sXpIavXcUB0>
Cc: gorry@erg.abdn.ac.uk, 6man WG <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 12:09:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AO2kpUputdNVejnRe93i72OxOUTCbjaEg
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Ole,

On 4/22/15 3:38 AM, Ole Troan wrote:
> Brian,
>=20
>> While I agree with the sentiment that the proposed updated text is=20
>> more appropriate, we are on a slippery slope as to this being
>> errata. This is a technical change and not fixing an error.  Can
>> someone point to a discussion where a reference to 6438 and
>> stateless methods occurred and there was consensus to put that in
>> 1.3.5?
>>=20
>> If not, this seems more like a new draft to obsolete 6936.
>=20
> I do see your point of view. technical errata are always going to be
> a judgement call. I think we also need to consider the alternatives.
> the cost and energy required to re-issue a new document is quite
> high. the risk of not accepting this as an errata, is that the issue
> will be dropped and forgotten.
>=20
> looking at:=20
> http://www.ietf.org/iesg/statement/errata-processing.html
>=20
> the important point here is if this issue creates "deployment
> problems or significant confusion=94.
>=20
> I think it might do that.

I am not sure I agree.  The text in 1.3.5 is nebulous, but it does not
require a stateful method.  It says that corresponding state is kept.
If there is no corresponding state, an implementation is still
conforming to 1.3.5.

>=20
> with regards to the issue if this changes consensus or not. the IETF
> published RFC6438 prior to this document, with consensus that there
> are stateless methods calculating the flow label. it is an error in
> 6936 requiring a stateful method. I see no indication anywhere that
> the intention of 6936 was to change the 6438 consensus.

Can you point to the text that requires a stateful method?  I tend to
agree with Brian & Gorry that the text is not crisp, but that HFDU is
appropriate.  I would rather see a new RFC that cleans this up so that
consensus is clear.

Regards,
Brian



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

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

iQEcBAEBCAAGBQJVN492AAoJEBOZRqCi7goqqHsIAMCiPe7zn6RGNIM4g7RGzBIE
fMvxUIMVlTmi00qgxApakVbYzFVFTF16oUJ/xbrzPHBUqZ+mFgBIhzR3kJFVacZP
r4/7XsZFatOSNTlF4DE3VEHheLXQ6d3njXwGpCS8G6iDyuzq5xkX7jCO3tuKuUYK
JdgpmEMwI+orOBXvplQ150zuCOyQfPa621MiFEjp7+pDcmhvQdKzOKVsWc6GZMP8
COjVKbVpTryU5+w6knifMvfum9FBuqHT749ASN5p9rQ+NLf/ZZSHv3N4tOW1WOdX
JpF62cNg3LKZZLxgp3n2TxHdlxj5lNR2OA2qnfbsNVdeXzP3s7bINWUMmTwTZu8=
=Fbpc
-----END PGP SIGNATURE-----

--AO2kpUputdNVejnRe93i72OxOUTCbjaEg--


From nobody Wed Apr 22 05:30:14 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56A61B355D for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 05:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJmKCtQjeN-k for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 05:30:11 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C70DD1B355C for <ipv6@ietf.org>; Wed, 22 Apr 2015 05:30:10 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 35C2C61A9; Wed, 22 Apr 2015 05:30:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=ixigUDbmZKYy8t11YASOCBPI3x8=; b= occNO+n4xtHcgMwQVy5oNJx8oqMuxzJzgCW4nxDeN5LBbVcf5ZW88UAJwVvMsoHr kWBszRA4l6IXRTwCg/pgtNT2LvvSX7/wvXoxV0G9uKB7pFdpw1KW/QpSi8mK2c2M 13H2M4xZzWkiWXg7MysZvep9v+qQ/fCdEpZSbeaszVI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=SClJuoQkuriDv2kI9zWmyKo2Y/ 5SiWs3X8QrYKNqpMWe6z1O4tcVB+i2kQ8H4cJl+uNmRiMYbEjPX5My5vjpBdneys 03sOGlJLz1qQG4Ot/4gpJpUW8froRYq2V7T+VOx0qPa//VHxOhWcI4xEBNfBFCYq Ntdsx+5QCLSiD+418=
Received: from gomlefisk.localdomain (unknown [173.38.220.33]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 9F6B2619E; Wed, 22 Apr 2015 05:30:07 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 6BD59430D6D6; Wed, 22 Apr 2015 14:30:05 +0200 (CEST)
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F553DD14-E7E2-4A2B-8126-FC0C7A928909"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <55378F71.2070906@innovationslab.net>
Date: Wed, 22 Apr 2015 14:30:04 +0200
Message-Id: <38C94D05-FD5E-4E73-BFC3-407EB493D8DB@employees.org>
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com> <55363D89.2070001@innovationslab.net> <F32F3D44-F1E3-426F-AB6F-C4AEDCCBF81A@employees.org> <55378F71.2070906@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DoN7HvitQOATXndea01pD8foBrU>
Cc: gorry@erg.abdn.ac.uk, 6man WG <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 12:30:13 -0000

--Apple-Mail=_F553DD14-E7E2-4A2B-8126-FC0C7A928909
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Brian,

>>> While I agree with the sentiment that the proposed updated text is
>>> more appropriate, we are on a slippery slope as to this being
>>> errata. This is a technical change and not fixing an error.  Can
>>> someone point to a discussion where a reference to 6438 and
>>> stateless methods occurred and there was consensus to put that in
>>> 1.3.5?
>>>=20
>>> If not, this seems more like a new draft to obsolete 6936.
>>=20
>> I do see your point of view. technical errata are always going to be
>> a judgement call. I think we also need to consider the alternatives.
>> the cost and energy required to re-issue a new document is quite
>> high. the risk of not accepting this as an errata, is that the issue
>> will be dropped and forgotten.
>>=20
>> looking at:
>> http://www.ietf.org/iesg/statement/errata-processing.html
>>=20
>> the important point here is if this issue creates "deployment
>> problems or significant confusion=94.
>>=20
>> I think it might do that.
>=20
> I am not sure I agree.  The text in 1.3.5 is nebulous, but it does not
> require a stateful method.  It says that corresponding state is kept.
> If there is no corresponding state, an implementation is still
> conforming to 1.3.5.

I read =93corresponding state=94 implying stateful, but oh well.

>> with regards to the issue if this changes consensus or not. the IETF
>> published RFC6438 prior to this document, with consensus that there
>> are stateless methods calculating the flow label. it is an error in
>> 6936 requiring a stateful method. I see no indication anywhere that
>> the intention of 6936 was to change the 6438 consensus.
>=20
> Can you point to the text that requires a stateful method?  I tend to
> agree with Brian & Gorry that the text is not crisp, but that HFDU is
> appropriate.  I would rather see a new RFC that cleans this up so that
> consensus is clear.

my take is that it isn=92t worth the cost to re-issue a new RFC. I will =
not stop anyone having the energy though.
as long as it isn=92t reject I can live with HFDU.

cheers,
Ole

cheers,
Ole

--Apple-Mail=_F553DD14-E7E2-4A2B-8126-FC0C7A928909
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

iQEcBAEBCgAGBQJVN5RNAAoJEFuJXizso86gH08H/jgaTwunkwCHTpdVK3A27wc7
DDoNbdj4QYFkltZgWdQft9dkyV6AQi5fLUuPaTNjltZ2HEWwf5sdRJlHA80vdh4E
ti9si0ubPj8wzIpuwIIEmOZpgonTxF1PsrF/e+EvoDVQLbjwPf29+xiarmQKHjcE
jHPcCIqiCXcNXszTpRAkAtuyGV6U6WKtO1RNHJx24Aon0Z1CUfIs0laBWFhHgJRA
W/hJp9TX1jTLUH73clEO04GwWBk4LwCePdhvDcPOpnroPHQclzHUwXXk3/8a6nZR
t7F1h7rTFxdF6SFjRhFeDR9ZMJazn60srl8z7LfrUfYiVqdFaztQaMhwr+0BMFM=
=Xove
-----END PGP SIGNATURE-----

--Apple-Mail=_F553DD14-E7E2-4A2B-8126-FC0C7A928909--


From nobody Wed Apr 22 07:21:29 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5211A92FE for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 07:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Kjz_wHgrDCF1 for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 07:21:26 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001: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 827481AC411 for <ipv6@ietf.org>; Wed, 22 Apr 2015 07:19:57 -0700 (PDT)
Received: by igbyr2 with SMTP id yr2so114849606igb.0 for <ipv6@ietf.org>; Wed, 22 Apr 2015 07:19:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=027P1yDFJYrlaDog9qWGuDnvGRytcyf5EHyZqENLqxc=; b=KGMXl3KYKmr4lYS/DEyx4y4dr+ZaozZ+9vJDf8r1msaGJutDWMPTiVzV19Gs/2NidS 9cTI/DcLdTryfFYH3/SEFXHRGCjPt2Lxkpo7Q48hxxl1+M8WGU4l7ZkKFVj4gEkjpNR8 xK5REvvUmZ/781rSugfiGchHKrjTIRzuyriUOx2RvJ0G/wqM3NKVbXSHLIH9mX0rlk3k r/B5arGDuI29+DF1ZvZvfU1Ow8WyqnWrKMdLj2Wo+x0l/DVU2mKo7SduMo7XYKSjrdSe 7G+5oC6aT5ES9nAuR2O6nqtyaEAn4uSp1Pvc7OtU9Tczl+bgUoPQ+ODaEQ1aohWazW3q HNAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=027P1yDFJYrlaDog9qWGuDnvGRytcyf5EHyZqENLqxc=; b=IfEwu5McbBgHGCHchtw397wHG/hMTJU6ufe/e5aPZKA83eFuCU7Pzlsq6/DpO+5hez i33lbDWJHBNO/TqY4DfoaRtAUnjSheNDQxKmpPmBLRzFnTVcUaz1br51c76xk9bQjX0w kho/Slsd+9vyico7/BKfxmArFfEmzm+BU8an12UrpznlEOhn12A6oEarZNU2ys+nQJcL WiYsVpgm6dyzl7aeCoRWWm4ytK0viMue/4fC8pReRretbKv3i4inna/mHRmL9bJ9bDSh gyog7Wx8+0wqh/u75t61fGnJLPuKSCppJ8azNSDyZPUeJQOBuocjZ5Ms68+Ln2YiuGYZ qhxg==
X-Gm-Message-State: ALoCoQnpLJLW5Lc1PPPc7oDdxVCxPV6UPzbYt6YPC5ce1GC5PSkcUIXMY1lt5mv4i8AbS165PYK2
X-Received: by 10.107.8.7 with SMTP id 7mr24907930ioi.87.1429712396969; Wed, 22 Apr 2015 07:19:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 22 Apr 2015 07:19:36 -0700 (PDT)
In-Reply-To: <55368297.6080006@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com> <55368297.6080006@acm.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Apr 2015 23:19:36 +0900
Message-ID: <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Erik Nordmark <nordmark@acm.org>
Content-Type: multipart/alternative; boundary=001a113ecc448dc950051450db39
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XqlBVITB9-jUn0hmV6Dm-9G9nN8>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 14:21:28 -0000

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

On Wed, Apr 22, 2015 at 2:02 AM, Erik Nordmark <nordmark@acm.org> wrote:

> With unsolicited RAs the host would be waiting up to 15 minutes (or 6
> hours with a larger maxra) for a the next unsolicited RA. With RS refresh
> it would send a new RS after a second.


Oh, I see what you mean now. But I think you are assuming that unmodified
hosts will simply ignore periodic multicast RAs, and then not send an RS
when they wake up. That sort of behaviour is a violation of the standard
(because the host is not processing the multicast RAs) and is guaranteed to
cause breakage.

Also: I'd argue that nothing stops a node from sending RSes using the
resilient RS retransmit algorithm when it wakes up (see below). You don't
need any of this document for a host to be able to do that.


> If what you're saying is that the sleeping node is going to ignore RAs
>> anyway, then you don't need an RS refresh option for the node to send an RS
>> and receive an RA when it wakes up. That's already possible.
>>
> There is no RFC which suggests or recommends sending a RS after wakeup.
> RFC 4861 is very prescriptive on when RS can and can not be sent.


RFC 4861 says a host can send an RA when it "re-attaches to a link after
being detached for some time". I'd argue that's the case here. The host is
in effect disconnected, because it's asleep and not processing multicast RA
(and maybe not even unicast packets). If you think hosts might not do that
because it's not clearly allowed by the standard, then fine, let's clarify
the standard. But we don't need to change the semantics.


> The document says that if you want to reduce multicast, you can increase
>> the RA interval. Personally, I don't think that makes sense, because one RA
>> every half hour is a tiny amount of traffic, which is trivial on any
>> general-purpose network.
>>
>
> IPv6 needs to apply to a large range of network technologies, just like
> IPv4 does.
> I think that is the fundamental disconnect here.


IPv4 applies to a large range of network technologies not because of the
standards, but because implementations are, let's say, "creative". For
example: ARP is a broadcast packet, right? In how many networks is ARP
*actually* a broadcast that goes to everybody? I'd argue that there is no
large wireless network where ARP is actually broadcast - because if there
were, that network would fall over. :-)


>     Are you arguing that all your points in the draft need to be
>>     addressed to your satisfaction before it can even become a WG draft?
>>     That isn't how an IETF working group is supposed to operate.
>>
>> No. I am worried that this document cannot meet its goals, and even if it
>> does not, after adoption we will be unable to abandon it and instead ship
>> something that does not meet its goals.
>>
>> Perhaps the issue here is that we don't agree on a problem statement, or
>> more accurately, what we're trying to accomplish with this drafts.
>>
>
> You've said that for > 2 years now, but never provided any useful
> suggestions.
>

But it's impossible for me, or anyone else, to provide a useful suggestion
without a problem statement.

This document proposes a solution. I don't like this solution because I
think it is not useful except if limited cases, and in some cases it is
harmful, and I think that on balance, the harm outweighs the good. So I
ask: "Why do we need this? What justifies a change to the IPv6
configuration model, such that we're changing it from a pure push model to
a hybrid push/pull model and possibly to a pull-only model? Why are we not
carefully considering the reasons for making the change, and instead only
documenting the change without asking ourselves why?"

Suppose for the sake of argument that your draft isn't actually solving any
real problem. There would be no suggestion anyone could possibly make other
than "please describe the problems that need to be solved, and let's design
a solution together". And I don't think "I waited two years and there were
no useful suggestions, so we should adopt this solution" is an argument
that makes sense.

Assuming it has actually been two years, then in those two years I can
recall the following use cases:

1. Mobile network paging channel excessive usage. I think the numbers in
that argument were dubious, because in any mobile network today the vast
majority of devices is sending packets *way* more often than one every half
an hour. But even supposing they weren't, that problem can be fixed by
increasing the maximum RA interval and/or piggybacking RAs onto unicast
traffic, and/or sending an RA to the node opportunistically right after the
node sends a packet and thus has the channel grant.

2. Excessive multicast use on wifi. Most of this problem problem can be
solved by sending solicited RAs unicast. RA isn't really a high-order
contributor to this problem anyway - bonjour is much worse, and so is ARP.

3. Low-battery nodes. Here you can construct an argument that justifies
anything: all you need to do is posit the existence of a node whose
constraints make it a poor fit for the periodic RA model, and then decide
to optimize for that node. For example, you can posit a node that is
super-constrained, whose battery has to last years of sending one packet
per day, but cannot disconnect because it needs to receive unicast packets
on someone else's schedule instead of the natural option for a constrained
device of *disconnecting* and only polling periodically. Even here, though
- why are these devices not using special link layers? For example, 802.11
in particular is terrible at power consumption for this sort of device.
It's a high-speed technology intended to provide XXX megabit speeds, not
optimizing low power. Why are we trying to use it?

I have repeatedly suggested: let's look at the *real* harm in these cases,
and let's see how far we can go without changing the protocol. But I think
you've just kept coming back with suggestions on how to fix the protocol
without first discussing how and how much it's broken.

--001a113ecc448dc950051450db39
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 W=
ed, Apr 22, 2015 at 2:02 AM, Erik Nordmark <span dir=3D"ltr">&lt;<a href=3D=
"mailto:nordmark@acm.org" target=3D"_blank">nordmark@acm.org</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex">With unsolicited RAs the host would be waiting =
up to 15 minutes (or 6 hours with a larger maxra) for a the next unsolicite=
d RA. With RS refresh it would send a new RS after a second.</blockquote><d=
iv><br></div><div>Oh, I see what you mean now. But I think you are assuming=
 that unmodified hosts will simply ignore periodic multicast RAs, and then =
not send an RS when they wake up. That sort of behaviour is a violation of =
the standard (because the host is not processing the multicast RAs) and is =
guaranteed to cause breakage.</div><div><br></div><div>Also: I&#39;d argue =
that nothing stops a node from sending RSes using the resilient RS retransm=
it algorithm when it wakes up (see below). You don&#39;t need any of this d=
ocument for a host to be able to do that.</div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:=
1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left=
:1ex"><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bo=
rder-left-style:solid;padding-left:1ex">If what you&#39;re saying is that t=
he sleeping node is going to ignore RAs anyway, then you don&#39;t need an =
RS refresh option for the node to send an RS and receive an RA when it wake=
s up. That&#39;s already possible.<br>
</blockquote></span>
There is no RFC which suggests or recommends sending a RS after wakeup. RFC=
 4861 is very prescriptive on when RS can and can not be sent.</blockquote>=
<div><br></div><div>RFC 4861 says a host can send an RA when it &quot;re-at=
taches to a link after being detached for some time&quot;. I&#39;d argue th=
at&#39;s the case here. The host is in effect disconnected, because it&#39;=
s asleep and not processing multicast RA (and maybe not even unicast packet=
s). If you think hosts might not do that because it&#39;s not clearly allow=
ed by the standard, then fine, let&#39;s clarify the standard. But we don&#=
39;t need to change the semantics.</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">=
<span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex">The document says that if you want to red=
uce multicast, you can increase the RA interval. Personally, I don&#39;t th=
ink that makes sense, because one RA every half hour is a tiny amount of tr=
affic, which is trivial on any general-purpose network.<br>
</blockquote>
<br></span>
IPv6 needs to apply to a large range of network technologies, just like IPv=
4 does.<br>
I think that is the fundamental disconnect here.</blockquote><div><br></div=
><div>IPv4 applies to a large range of network technologies not because of =
the standards, but because implementations are, let&#39;s say, &quot;creati=
ve&quot;. For example: ARP is a broadcast packet, right? In how many networ=
ks is ARP *actually* a broadcast that goes to everybody? I&#39;d argue that=
 there is no large wireless network where ARP is actually broadcast - becau=
se if there were, that network would fall over. :-)</div><div>=C2=A0<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:soli=
d;padding-left:1ex"><span class=3D""><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(2=
04,204,204);border-left-style:solid;padding-left:1ex">=C2=A0 =C2=A0 Are you=
 arguing that all your points in the draft need to be<br>
=C2=A0 =C2=A0 addressed to your satisfaction before it can even become a WG=
 draft?<br>
=C2=A0 =C2=A0 That isn&#39;t how an IETF working group is supposed to opera=
te.<br>
<br>
No. I am worried that this document cannot meet its goals, and even if it d=
oes not, after adoption we will be unable to abandon it and instead ship so=
mething that does not meet its goals.<br>
<br>
Perhaps the issue here is that we don&#39;t agree on a problem statement, o=
r more accurately, what we&#39;re trying to accomplish with this drafts.<br=
>
</blockquote>
<br></span>
You&#39;ve said that for &gt; 2 years now, but never provided any useful su=
ggestions.<br></blockquote><div><br></div><div>But it&#39;s impossible for =
me, or anyone else, to provide a useful suggestion without a problem statem=
ent.</div><div><br></div><div>This document proposes a solution. I don&#39;=
t like this solution because I think it is not useful except if limited cas=
es, and in some cases it is harmful, and I think that on balance, the harm =
outweighs the good. So I ask: &quot;Why do we need this? What justifies a c=
hange to the IPv6 configuration model, such that we&#39;re changing it from=
 a pure push model to a hybrid push/pull model and possibly to a pull-only =
model? Why are we not carefully considering the reasons for making the chan=
ge, and instead only documenting the change without asking ourselves why?&q=
uot;</div><div><br></div><div>Suppose for the sake of argument that your dr=
aft isn&#39;t actually solving any real problem. There would be no suggesti=
on anyone could possibly make other than &quot;please describe the problems=
 that need to be solved, and let&#39;s design a solution together&quot;. An=
d I don&#39;t think &quot;I waited two years and there were no useful sugge=
stions, so we should adopt this solution&quot; is an argument that makes se=
nse.<br></div><div><br></div><div>Assuming it has actually been two years, =
then in those two years I can recall the following use cases:<br></div><div=
><br></div><div>1. Mobile network paging channel excessive usage. I think t=
he numbers in that argument were dubious, because in any mobile network tod=
ay the vast majority of devices is sending packets *way* more often than on=
e every half an hour. But even supposing they weren&#39;t, that problem can=
 be fixed by increasing the maximum RA interval and/or piggybacking RAs ont=
o unicast traffic, and/or sending an RA to the node opportunistically right=
 after the node sends a packet and thus has the channel grant.</div><div><b=
r></div><div>2. Excessive multicast use on wifi. Most of this problem probl=
em can be solved by sending solicited RAs unicast. RA isn&#39;t really a hi=
gh-order contributor to this problem anyway - bonjour is much worse, and so=
 is ARP.</div><div><br></div><div>3. Low-battery nodes. Here you can constr=
uct an argument that justifies anything: all you need to do is posit the ex=
istence of a node whose constraints make it a poor fit for the periodic RA =
model, and then decide to optimize for that node. For example, you can posi=
t a node that is super-constrained, whose battery has to last years of send=
ing one packet per day, but cannot disconnect because it needs to receive u=
nicast packets on someone else&#39;s schedule instead of the natural option=
 for a constrained device of *disconnecting* and only polling periodically.=
 Even here, though - why are these devices not using special link layers? F=
or example, 802.11 in particular is terrible at power consumption for this =
sort of device. It&#39;s a high-speed technology intended to provide XXX me=
gabit speeds, not optimizing low power. Why are we trying to use it?</div><=
div><br></div><div>I have repeatedly suggested: let&#39;s look at the *real=
* harm in these cases, and let&#39;s see how far we can go without changing=
 the protocol. But I think you&#39;ve just kept coming back with suggestion=
s on how to fix the protocol without first discussing how and how much it&#=
39;s broken.</div></div></div></div>

--001a113ecc448dc950051450db39--


From nobody Wed Apr 22 07:27:41 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6ED1A1F04 for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 07:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 LSrdAs60q_eG for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 07:27:38 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001: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 D16E81AC3C2 for <ipv6@ietf.org>; Wed, 22 Apr 2015 07:27:37 -0700 (PDT)
Received: by igbyr2 with SMTP id yr2so115081782igb.0 for <ipv6@ietf.org>; Wed, 22 Apr 2015 07:27:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9jKVpCIL8PshKHCoAP+kUfokdTE3Eqm8r979AJOQ0Fc=; b=fEf/I4WigxFjjGtlFfTaiCC29MVq1zM+qpp2zQFOqtGkhQljZ/5eW78Q9Ua07PxLO7 0ah4Y/U/hQsnBSRrjFoHXPWJ7HRevj4S5MGj2u+OXLVafeBtYdltIaWO+qITI9KOBDvx fXp9dsxqNiV0vifAIMvSxsKoxGd6KoqLU2c1ROhvFZL0J+jNnOooV4eh5EK9ZUuCxi+R wpZkuZwQWNVG9oZzknTHTD7wkT3R5Rfp4+13bpIi8BSJCRoT0pTA1NXyd0S7Hb1fVbhM ALfYEQ5LBlKl0bdQ97kMvvD3DfXAyyGRIrDv/GW3o5oxPFWXVX+8LanT1DB8jIX6JUyf 9ETw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9jKVpCIL8PshKHCoAP+kUfokdTE3Eqm8r979AJOQ0Fc=; b=FEHHLjcprVMvd0vLd2sBbjwEvORD2B2KhIspNjnImu3lxNUNA1mqWFIiS9bHL00vlZ ZIlCQUCZc71G4g1cMVAg+XXAf2bRuFKJ8lzMs4DSwV9XS7UC8+EETW10UCmBVwEZRaz5 38TyaTbSs7rhJ+eRsPKevPZVb0tTn6cRsAJh4RiAMprvCH3n0VuIxtnr+6N2ZiryWeqR t/BNTvT5bqIBoyrprjcdAYjjYHiizHAs5bZOKM7zie3WuBJ7gYpmbQfQsV4CXKvuQw8U ADGpppGkOppKeSrf7EPVB8S6nVDpGiG6FiOTfsOfFxRIo9Ms6F0DP2pe9HPXDaqWrfNY FpiA==
X-Gm-Message-State: ALoCoQmmIO6QC5xr/6Drnu5gAkIchefNsDesuLyosL8B6iwkasE3ojYO4YS/HNAjArC88Fqeqd8D
X-Received: by 10.50.221.98 with SMTP id qd2mr4837001igc.37.1429712857310; Wed, 22 Apr 2015 07:27:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 22 Apr 2015 07:27:16 -0700 (PDT)
In-Reply-To: <55368493.7090306@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com> <55368493.7090306@acm.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Apr 2015 23:27:16 +0900
Message-ID: <CAKD1Yr2GB+PYSNCXhJkAThi7q3ztik=_e=+F_CyqQZR=nu1Ktg@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Erik Nordmark <nordmark@acm.org>
Content-Type: multipart/alternative; boundary=001a11347f20fdd9a0051450f66d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xnAUyG4GA8wvTdzDVo03xVqu2yY>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 14:27:39 -0000

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

On Wed, Apr 22, 2015 at 2:10 AM, Erik Nordmark <nordmark@acm.org> wrote:

> I think the root of my objections to this draft is that it proposes what
>> is in effect a substantial change to the current configuration model in
>> IPv6 networks without saying so explicitly.
>>
>> Currently, we have an easy-to understand, easy-to-reason-about model:
>> periodic RAs periodically notify everyone on link of the current
>> configuration information, and nodes that don't want to wait for such
>> periodic configuration information can solicit said information by sending
>> a request.
>>
>
> Lorenzo,
> which RFC states "nodes that don't want to wait for such periodic
> configuration information can solicit said information by sending a
> request"?
> AFAIK that isn't allowed. If you do that you would be violating this MUST
> in RFC 4861:
>    Once the host sends a Router Solicitation, and receives a valid
>    Router Advertisement with a non-zero Router Lifetime, the host MUST
>    desist from sending additional solicitations on that interface, until
>    the next time one of the above events occurs.


As I said in my other reply, I think the event that occurs here is "The
host re-attaches to a link after being detached for some time." To me, if
you can't receive packets, you're arguably not attached.

I agree that this is interpretation is not particularly clear, but it's
also something that can be clarified without substantially changing the
semantics.

With this document, it's not clear what model is proposed.
>>
> AFAICT the document is clear on what it is proposing. If others find it
> unclear we can definitely add some wording.
>
> You seem to disagree with the change in the model? Or perhaps you don't
> since the paragraph above seems to say that that the model already allows
> for "pull" by sending RSes? Even though that is not allowed in RFC 4861!!
>

I disagree with changing the model in such a way that push configuration
becomes optional (either through explicit design, or de facto, over time,
due to sloppy / buggy implementations or developers / network operators
used to IPv4-style pull configuration).

Today, a node cannot rely only on periodic refresh without losing
information, unless it's prepared to engage in a relatively heavyweight
process of sending multicast RS and waiting for RA (or doing DNA). This
document will change that.

--001a11347f20fdd9a0051450f66d
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 W=
ed, Apr 22, 2015 at 2:10 AM, Erik Nordmark <span dir=3D"ltr">&lt;<a href=3D=
"mailto:nordmark@acm.org" target=3D"_blank">nordmark@acm.org</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex"><span class=3D""><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-col=
or:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I think the r=
oot of my objections to this draft is that it proposes what is in effect a =
substantial change to the current configuration model in IPv6 networks with=
out saying so explicitly.<br>
<br>
Currently, we have an easy-to understand, easy-to-reason-about model: perio=
dic RAs periodically notify everyone on link of the current configuration i=
nformation, and nodes that don&#39;t want to wait for such periodic configu=
ration information can solicit said information by sending a request.<br>
</blockquote>
<br></span>
Lorenzo,<br>
which RFC states &quot;nodes that don&#39;t want to wait for such periodic =
configuration information can solicit said information by sending a request=
&quot;?<br>
AFAIK that isn&#39;t allowed. If you do that you would be violating this MU=
ST in RFC 4861:<br>
=C2=A0 =C2=A0Once the host sends a Router Solicitation, and receives a vali=
d<br>
=C2=A0 =C2=A0Router Advertisement with a non-zero Router Lifetime, the host=
 MUST<br>
=C2=A0 =C2=A0desist from sending additional solicitations on that interface=
, until<br>
=C2=A0 =C2=A0the next time one of the above events occurs.</blockquote><div=
><br></div><div>As I said in my other reply, I think the event that occurs =
here is &quot;The host re-attaches to a link after being detached for some =
time.&quot; To me, if you can&#39;t receive packets, you&#39;re arguably no=
t attached.</div><div><br></div><div>I agree that this is interpretation is=
 not particularly clear, but it&#39;s also something that can be clarified =
without substantially changing the semantics.</div><div><br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-le=
ft:1ex"><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);=
border-left-style:solid;padding-left:1ex">With this document, it&#39;s not =
clear what model is proposed.<br>
</blockquote></span>
AFAICT the document is clear on what it is proposing. If others find it unc=
lear we can definitely add some wording.<br>
<br>
You seem to disagree with the change in the model? Or perhaps you don&#39;t=
 since the paragraph above seems to say that that the model already allows =
for &quot;pull&quot; by sending RSes? Even though that is not allowed in RF=
C 4861!!<br></blockquote><div><br></div><div>I disagree with changing the m=
odel in such a way that push configuration becomes optional (either through=
 explicit design, or de facto, over time, due to sloppy / buggy implementat=
ions or developers / network operators used to IPv4-style pull configuratio=
n).</div><div><br></div><div>Today, a node cannot rely only on periodic ref=
resh without losing information, unless it&#39;s prepared to engage in a re=
latively heavyweight process of sending multicast RS and waiting for RA (or=
 doing DNA). This document will change that.</div></div></div></div>

--001a11347f20fdd9a0051450f66d--


From nobody Wed Apr 22 08:28:09 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48DAB1A90E8; Wed, 22 Apr 2015 08:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JwQDgp0siN64; Wed, 22 Apr 2015 08:28:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0EFAC1A9028; Wed, 22 Apr 2015 08:28:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C9D19180208; Wed, 22 Apr 2015 08:27:02 -0700 (PDT)
To: brian.e.carpenter@gmail.com, gorry@erg.abdn.ac.uk, magnus.westerlund@ericsson.com
Subject: [Errata Held for Document Update] RFC6936 (4341)
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150422152702.C9D19180208@rfc-editor.org>
Date: Wed, 22 Apr 2015 08:27:02 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1USSwKNLwn1LtDxeYbyMhv6XzMw>
Cc: brian@innovationslab.net, ipv6@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 15:28:04 -0000

The following errata report has been held for document update 
for RFC6936, "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
Date Reported: 2015-04-20
Held by: Brian Haberman (IESG)

Section: 1.3.5

Original Text
-------------
The ingress of a tunnel seeking to provide good
entropy in the flow label field would therefore need to create a
random flow label value and keep corresponding state so that all
packets that were associated with a flow would be consistently given
the same flow label.  Although possible, this complexity may not be
desirable in a tunnel ingress.

Corrected Text
--------------
The ingress of a tunnel seeking to provide good
entropy in the flow label field would therefore need to create a
pseudo-random flow label value using a stateless method
as described in [RFC6438] so that all
packets that were associated with a flow would be consistently given
the same flow label.

Notes
-----
It is incorrect that a stateful method is needed, and presumably that
was the complexity judged undesirable. Also, we shouldn't say "random"
when we mean "pseudo-random."

--------------------------------------
RFC6936 (draft-ietf-6man-udpzero-12)
--------------------------------------
Title               : Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums
Publication Date    : April 2013
Author(s)           : G. Fairhurst, M. Westerlund
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 22 09:14:43 2015
Return-Path: <dennis.c.ferguson@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0AD1B373A for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 09:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_yf33ly0MYd for <ipv6@ietfa.amsl.com>; Wed, 22 Apr 2015 09:14:40 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::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 809501B3738 for <ipv6@ietf.org>; Wed, 22 Apr 2015 09:14:35 -0700 (PDT)
Received: by pdbqd1 with SMTP id qd1so278498330pdb.2 for <ipv6@ietf.org>; Wed, 22 Apr 2015 09:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=2uLdasJGhEeY7iBp1K5El3DK3imHeArqrOIrLq1W4Mg=; b=LizKq7ER5bCatBO9uYsfPa936gIob2Ngwpl8fZ7FXL91NGZVO5g2P5od+k5IEEO6fv ePF8vngMMxIsAw/vvXUMCwtu8KkzBdcOQghEZyU/PuijrEJSbaDK6LUacdGWERP9mYNV mPrzQATPeUdordF7OXA79+3LX0x5D4thofV8oVSpkbar0jEkaCGd5Lzey41MNnOUFpfu uPKMqe6kjh0n5R+5GlZCFg2x57gS0xoMJU8ANRKq4kH4d1/zktcVhgEevF9TP8wO3mnX j/nrup77Non10z6mFCWFHN3R+k5wQrW4HIuo08+kkfAeyjPsVACSEC40BAbSFJfc75Sr x0yw==
X-Received: by 10.70.93.36 with SMTP id cr4mr47738223pdb.68.1429719275235; Wed, 22 Apr 2015 09:14:35 -0700 (PDT)
Received: from [192.168.43.113] (mbb0436d0.tmodns.net. [208.54.4.187]) by mx.google.com with ESMTPSA id yy2sm5483039pbb.6.2015.04.22.09.14.32 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Apr 2015 09:14:33 -0700 (PDT)
From: Dennis Ferguson <dennis.c.ferguson@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Distinction between ICMP unreachable codes 0 and 6?
Message-Id: <C898DE9C-E530-4A14-8CE7-A80BDE040C2D@gmail.com>
Date: Wed, 22 Apr 2015 09:14:30 -0700
To: ipv6@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/BBkrGswImsZzYwHNfDwDjahwT4o>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 16:14:42 -0000

After many years I've found a reason to read RFC4443 with an eye for the
minutia and I can't quite figure out the intended distinction between =
ICMP
unreachable codes 0 and 6 from the text.  The definitions are

   Code           0 - No route to destination
                  [...]
                  6 - Reject route to destination

About code 0 it says this:

   If the reason for the failure to deliver is lack of a matching entry
   in the forwarding node's routing table, the Code field is set to 0.
   (This error can occur only in nodes that do not hold a "default
   route" in their routing tables.)

It says this about code 6

   If the reason for the failure to deliver is that the route to the
   destination is a reject route, the Code field is set to 6.  This may
   occur if the router has been configured to reject all the traffic for
   a specific prefix.

   Codes 5 and 6 are more informative subsets of code 1.

where code 1 is "administrative prohibition".

I have an implementation where the forwarding table always has a default
route (i.e. with a prefix of length 0), so every route lookup finds a
matching entry in the "forwarding node's routing table" but sometimes =
the
matching entry is what it would call a "reject route" in SNMP.  This =
seems
like a mere internal implementation quirk which should have no effect on
the ICMP errors it emits yet the text above, which is written in terms =
of
internal implementation mechanisms like "reject route" rather than the
semantics the error is intended to convey, seems to quite explicitly say
otherwise.

The related issue is that I think the parenthetical comment in the
code 0 description is incorrect, in that lack of a default route is not
the only way a router can determine it has no matching route to a =
destination.
A router which does a route aggregation, that is which originates a =
shorter
prefix summary route into routing while suppressing the advertisement of =
some
or all of the more specific matching prefixes it has routes to, is =
almost
always advertising reachability for destinations it knows it cannot =
reach and
must arrange its forwarding lookup so that destinations matching the =
aggregate
prefix it conjured up never match routes less specific than the =
aggregate.
I believe the unreachable code the router sends in this case should be =
the
same whether the router also has a default route or not and independent =
of
how the internal forwarding lookup is arranged to produce the error.
Moreover, when viewed this way a router with no default route (or a =
"reject"
default route) which originates a zero-length prefix into routing while
suppressing the advertisement of some or all more specific prefixes it =
has
routes for is in fact performing the extreme version of same aggregation
operation.  The error being reported, that it has no more specific route
to a destination matching the summary prefix, has the same meaning in
either case, I don't see why the length of the summary prefix should =
change
the error code it sends and in any case the error being reported is not
an "administrative prohibition" even if the internal implementation of
this involves something that is called a "reject route" when reported
via the forwarding MIB.  Ignoring routing transients, routers being
sent traffic for destinations they have no route to reach are always
the (perhaps implicit or static) origin of an aggregated summary prefix,
but the summary prefix is not necessarily a default route.

So I'm assuming that code 0 was intended to report the general case of
a router having no route to reach a destination, while code 6 is =
supposed to
be used to report the RFC4193 ULA border patrol error for which it seems
to have been invented.  If this is true then I think the code 0 =
description
would be better if it just repeated "no route to destination" without =
opining
about how that is determined, since it is more complicated than the =
comment in
the parentheses, while the code 6 specification would better avoid the =
term
"reject route" in favour of describing the circumstance that should =
cause
the code 6 error to be sent (given the definition of code 5, =
"Destination
address failed ingress/egress policy" might work).  As far as I can find
the only definition of "reject route" we had prior to RFC4193 and the
above is the route type in the RFC4292 forwarding table MIB and its
ancestors, which says this:

               reject(2) refers to a route that, if matched, discards
               the message as unreachable and returns a notification
               (e.g., ICMP error) to the message sender.  This is used
               in some protocols as a means of correctly aggregating
               routes.

Here matching a reject route results in a non-specific notification =
being
sent.  To know which notification it causes to be sent would require =
knowing
why the reject route is there, which the MIB doesn't represent and the =
existence
of the reject route by itself doesn't tell you.  The code 6 definition =
seems
to instead define the "why" to be the reject route itself, assigns =
semantics
to the "reject route" error (administrative prohibition) inconsistent =
with an
original reason reject routes were and are used, and appears to have the =
odd
consequence that the choice of representing my forwarding table as =
having no
default route or a reject default route should effect the unreachable =
code
sent for errors involving that even though this has no effect on the =
nature
of the error being reported or anything else.

It is, however, quite possible (and certainly wouldn't be the first =
time)
that I'm misunderstanding the utility of this, or that the reasons this =
is
fine were all hashed out before when I wasn't paying attention.  If so I
apologize, but I would appreciate it if someone could explain it to me.

Thanks,
Dennis Ferguson=


From nobody Thu Apr 23 11:33:12 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A364E1B3179 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 11:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 bcp6q0MnitY3 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 11:33:09 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::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 9C18A1B3183 for <ipv6@ietf.org>; Thu, 23 Apr 2015 11:32:53 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so67481720ieb.3 for <ipv6@ietf.org>; Thu, 23 Apr 2015 11:32:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=gIxYp8s9J88GTt7kerLrE5DVxxDneCr8t1sKRptzRnI=; b=oq/xxZ6Gs/ESf2NjxTotSlwOw07OboqvkwlVbi/SJSbf5vunrqzFfH1TJip+CRcblw 1Al38ZGGqzN/LKb6TDKJ64i62Zft96GTzBRSnkREZr3056t5EklIMLE/rVcI8sSnVrT8 HbXq78XyYH0KSwgezqWNRAze2T48jElWiRi0jImGkzlO/e5RPPpESljdtiZerypvTCWw PSfArpn12vwyOiNHaJkzMIjVjGXi2wRr1d77J+fnABhlcmOURedZcKkmDL/hGjlqJl/j rPt13I2ZZW+msf8C8fMcv7L5+Au3x0+ozmvNksFdg2sr2R4OcDpH0nS1U14X9DiwKY0M 5uBQ==
MIME-Version: 1.0
X-Received: by 10.43.163.71 with SMTP id mn7mr5232216icc.72.1429813973143; Thu, 23 Apr 2015 11:32:53 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.50.80 with HTTP; Thu, 23 Apr 2015 11:32:53 -0700 (PDT)
In-Reply-To: <55368786.5000507@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com> <CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com> <55368786.5000507@acm.org>
Date: Thu, 23 Apr 2015 11:32:53 -0700
X-Google-Sender-Auth: Vuv2Bkapn4qdKpHLtHDODYeU76E
Message-ID: <CAJE_bqciFNkukedq6pFYUHVvdh02GEYWEA0Wdb3dFcySz_K4NQ@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Erik Nordmark <nordmark@acm.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/e9J--fR1KNZ6RWxpUHEo58V5DSU>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 18:33:10 -0000

At Tue, 21 Apr 2015 10:23:18 -0700,
Erik Nordmark <nordmark@acm.org> wrote:

> > I was not sure if we had agreed on sufficient need for making
> > non-trivial (if not substantial) changes to a core part of the
> > protocol.  If what Lorenzo was trying to say is a different form of
> > what I tried to ask, I tend to agree with part of his argument.
> > Although I'm not necessarily opposed to adopting the document just
> > because of that, I think it's reasonable to request clarifying the
> > problem statement and expected goal.
>
> Please send text on what you would want to see as (part of) PS and goals.

It was very vague and abstract level of thought when I wrote this, so
I wouldn't have been able to propose any specific text.  But I guess
Lorenzo seemed to answer the request pretty well in his later message:
http://www.ietf.org/mail-archive/web/ipv6/current/msg22477.html

--
JINMEI, Tatuya


From nobody Thu Apr 23 14:55:31 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE781A6F13 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 14:55:31 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yK6aX9-Vu3KT for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 14:55:29 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 CC23C1B2A54 for <ipv6@ietf.org>; Thu, 23 Apr 2015 14:55:23 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3NLtFVO010368 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Apr 2015 14:55:15 -0700
Message-ID: <55396A43.8060605@acm.org>
Date: Thu, 23 Apr 2015 14:55:15 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com> <55368493.7090306@acm.org> <CAKD1Yr2GB+PYSNCXhJkAThi7q3ztik=_e=+F_CyqQZR=nu1Ktg@mail.gmail.com>
In-Reply-To: <CAKD1Yr2GB+PYSNCXhJkAThi7q3ztik=_e=+F_CyqQZR=nu1Ktg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVYzeCHvQVd6fnDredPZmtTkj7qtByDCP6szrnPkeRjOeE7su+hTIjZFpa1hqlrMy6qKF7Gh9KbVONNFeyjnZiV4
X-Sonic-ID: C;8iNybAPq5BGWYIY+Bvepxg== M;aF+JbAPq5BGWYIY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KoqNdN8A29FPWVOUWs1T_uuduxE>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 21:55:31 -0000

On 4/22/15 7:27 AM, Lorenzo Colitti wrote:
> On Wed, Apr 22, 2015 at 2:10 AM, Erik Nordmark <nordmark@acm.org 
> <mailto:nordmark@acm.org>> wrote:
>
>         I think the root of my objections to this draft is that it
>         proposes what is in effect a substantial change to the current
>         configuration model in IPv6 networks without saying so explicitly.
>
>         Currently, we have an easy-to understand, easy-to-reason-about
>         model: periodic RAs periodically notify everyone on link of
>         the current configuration information, and nodes that don't
>         want to wait for such periodic configuration information can
>         solicit said information by sending a request.
>
>
>     Lorenzo,
>     which RFC states "nodes that don't want to wait for such periodic
>     configuration information can solicit said information by sending
>     a request"?
>     AFAIK that isn't allowed. If you do that you would be violating
>     this MUST in RFC 4861:
>        Once the host sends a Router Solicitation, and receives a valid
>        Router Advertisement with a non-zero Router Lifetime, the host MUST
>        desist from sending additional solicitations on that interface,
>     until
>        the next time one of the above events occurs.
>
>
> As I said in my other reply, I think the event that occurs here is 
> "The host re-attaches to a link after being detached for some time." 
> To me, if you can't receive packets, you're arguably not attached.

Lorenzo,

If you re-read your own text above you'll find that is says "nodes that 
don't want to wait for such periodic ..." and I was responding to that 
statement
because it seems incorrect. So I think you need some more work on your 
description of existing model that you you claim is easy to understand 
and easy to reason about, since you don't seem to be able to describe it 
correctly.

If you want to fold in DNA aspects (re-attaching to a link - possibly 
the same or different) as you are trying to, then I suspect your model 
description will need more work. Might be better to write an internet 
draft instead of doing this back and forth over email. That would also 
ensure that we can get a permanent record of the model.

But might not be as easy to understand and reason about as you claim.

Regards,
    Erik


>
> I agree that this is interpretation is not particularly clear, but 
> it's also something that can be clarified without substantially 
> changing the semantics.
>
>         With this document, it's not clear what model is proposed.
>
>     AFAICT the document is clear on what it is proposing. If others
>     find it unclear we can definitely add some wording.
>
>     You seem to disagree with the change in the model? Or perhaps you
>     don't since the paragraph above seems to say that that the model
>     already allows for "pull" by sending RSes? Even though that is not
>     allowed in RFC 4861!!
>
>
> I disagree with changing the model in such a way that push 
> configuration becomes optional (either through explicit design, or de 
> facto, over time, due to sloppy / buggy implementations or developers 
> / network operators used to IPv4-style pull configuration).
>
> Today, a node cannot rely only on periodic refresh without losing 
> information, unless it's prepared to engage in a relatively 
> heavyweight process of sending multicast RS and waiting for RA (or 
> doing DNA). This document will change that.


From nobody Thu Apr 23 14:56:58 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E58F11B34AF for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 14:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.635
X-Spam-Level: 
X-Spam-Status: No, score=-1.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 xGU2S2sfPvXH for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 14:56:55 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 F03051A8A66 for <ipv6@ietf.org>; Thu, 23 Apr 2015 14:56:40 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3NLucoX016230 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Apr 2015 14:56:38 -0700
Message-ID: <55396A96.70702@acm.org>
Date: Thu, 23 Apr 2015 14:56:38 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>	<CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>	<CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com>	<55368786.5000507@acm.org> <CAJE_bqciFNkukedq6pFYUHVvdh02GEYWEA0Wdb3dFcySz_K4NQ@mail.gmail.com>
In-Reply-To: <CAJE_bqciFNkukedq6pFYUHVvdh02GEYWEA0Wdb3dFcySz_K4NQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVbtupfE5a2/ZamPWoWC6arJPzqQgXe5xijVL2Ccp2J+S4eLbv/6CFOgqStRFj9jVivQXHOz7vAx4dj1nvetMCBn
X-Sonic-ID: C;WobznQPq5BGKdOVSju/ZCg== M;ZpAPngPq5BGKdOVSju/ZCg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2hxv5vCiOTtaDXQsOupODMALfNQ>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 21:56:57 -0000

On 4/23/15 11:32 AM, 神明達哉 wrote:
> At Tue, 21 Apr 2015 10:23:18 -0700,
> Erik Nordmark <nordmark@acm.org> wrote:
>
>>> I was not sure if we had agreed on sufficient need for making
>>> non-trivial (if not substantial) changes to a core part of the
>>> protocol.  If what Lorenzo was trying to say is a different form of
>>> what I tried to ask, I tend to agree with part of his argument.
>>> Although I'm not necessarily opposed to adopting the document just
>>> because of that, I think it's reasonable to request clarifying the
>>> problem statement and expected goal.
>> Please send text on what you would want to see as (part of) PS and 
>> goals.
> It was very vague and abstract level of thought when I wrote this, so
> I wouldn't have been able to propose any specific text.  But I guess
> Lorenzo seemed to answer the request pretty well in his later message:
> http://www.ietf.org/mail-archive/web/ipv6/current/msg22477.html

Jinmei,

That email doesn't have any useful text which can be included in the 
document as a problem statement. To quote:
"1. Mobile network paging channel excessive usage. I think the numbers 
in that argument were dubious, because in any mobile network today the 
vast majority of devices is sending packets *way* more often than one 
every half an hour. But even supposing they weren't, that problem can be 
fixed by increasing the maximum RA interval and/or piggybacking RAs onto 
unicast traffic, and/or sending an RA to the node opportunistically 
right after the node sends a packet and thus has the channel grant.

2. Excessive multicast use on wifi. Most of this problem problem can be 
solved by sending solicited RAs unicast. RA isn't really a high-order 
contributor to this problem anyway - bonjour is much worse, and so is ARP.

3. Low-battery nodes. Here you can construct an argument that justifies 
anything: all you need to do is posit the existence of a node whose 
constraints make it a poor fit for the periodic RA model, and then 
decide to optimize for that node. For example, you can posit a node that 
is super-constrained, whose battery has to last years of sending one 
packet per day, but cannot disconnect because it needs to receive 
unicast packets on someone else's schedule instead of the natural option 
for a constrained device of *disconnecting* and only polling 
periodically. Even here, though - why are these devices not using 
special link layers? For example, 802.11 in particular is terrible at 
power consumption for this sort of device. It's a high-speed technology 
intended to provide XXX megabit speeds, not optimizing low power. Why 
are we trying to use it?"


That is mostly Lorenzo's personal views about different potential 
problems, and isn't something I can cut and paste into the document as a 
PS, which is really what "send text" means.


Note that the document already has a goals section. If you disagree with 
it, then please suggest edits, additions, removals.

Thanks,
    Erik

>
> -- 
> JINMEI, Tatuya
>


From nobody Thu Apr 23 15:18:22 2015
Return-Path: <nordmark@sonic.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DA41A6F13 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 14:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.31
X-Spam-Level: 
X-Spam-Status: No, score=-2.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7PV9fOgPIN1k for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 14:55:28 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 A348A1A8833 for <ipv6@ietf.org>; Thu, 23 Apr 2015 14:55:09 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3NLt4Yv014090 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Apr 2015 14:55:04 -0700
Message-ID: <55396A38.1050107@sonic.net>
Date: Thu, 23 Apr 2015 14:55:04 -0700
From: Erik Nordmark <nordmark@sonic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Erik Nordmark <nordmark@acm.org>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com>	<CAKD1Yr1c80-04CgQKCdGCZPeRgT_M_oeRzzZUnSCVKsaS9kqug@mail.gmail.com>	<CAJE_bqfdw_wQRNYept1h8s8a_gj2NOYcqWsGpsFztZbr-B_UEg@mail.gmail.com>	<55368786.5000507@acm.org> <CAJE_bqciFNkukedq6pFYUHVvdh02GEYWEA0Wdb3dFcySz_K4NQ@mail.gmail.com>
In-Reply-To: <CAJE_bqciFNkukedq6pFYUHVvdh02GEYWEA0Wdb3dFcySz_K4NQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVbEaPP9FR26zX6LWwJP3ltBibG6sM1uT0czoTOKYItYCu7JJVCZ9xaQd8FHdDJHEZ0VVMUiXJfJw9yOWZPA32rW
X-Sonic-ID: C;6uo2ZgPq5BGMHOVSju/ZCg== M;lPlBZgPq5BGMHOVSju/ZCg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/S2lqG5ADTgrjIsdyTTYtpymMAhI>
X-Mailman-Approved-At: Thu, 23 Apr 2015 15:18:21 -0700
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 21:55:30 -0000

On 4/23/15 11:32 AM, 神明達哉 wrote:
> At Tue, 21 Apr 2015 10:23:18 -0700,
> Erik Nordmark <nordmark@acm.org> wrote:
>
>>> I was not sure if we had agreed on sufficient need for making
>>> non-trivial (if not substantial) changes to a core part of the
>>> protocol.  If what Lorenzo was trying to say is a different form of
>>> what I tried to ask, I tend to agree with part of his argument.
>>> Although I'm not necessarily opposed to adopting the document just
>>> because of that, I think it's reasonable to request clarifying the
>>> problem statement and expected goal.
>> Please send text on what you would want to see as (part of) PS and goals.
> It was very vague and abstract level of thought when I wrote this, so
> I wouldn't have been able to propose any specific text.  But I guess
> Lorenzo seemed to answer the request pretty well in his later message:
> http://www.ietf.org/mail-archive/web/ipv6/current/msg22477.html

Jinmei,

That email doesn't have any useful text which can be included in the 
document as a problem statement. To quote:
"1. Mobile network paging channel excessive usage. I think the numbers 
in that argument were dubious, because in any mobile network today the 
vast majority of devices is sending packets *way* more often than one 
every half an hour. But even supposing they weren't, that problem can be 
fixed by increasing the maximum RA interval and/or piggybacking RAs onto 
unicast traffic, and/or sending an RA to the node opportunistically 
right after the node sends a packet and thus has the channel grant.

2. Excessive multicast use on wifi. Most of this problem problem can be 
solved by sending solicited RAs unicast. RA isn't really a high-order 
contributor to this problem anyway - bonjour is much worse, and so is ARP.

3. Low-battery nodes. Here you can construct an argument that justifies 
anything: all you need to do is posit the existence of a node whose 
constraints make it a poor fit for the periodic RA model, and then 
decide to optimize for that node. For example, you can posit a node that 
is super-constrained, whose battery has to last years of sending one 
packet per day, but cannot disconnect because it needs to receive 
unicast packets on someone else's schedule instead of the natural option 
for a constrained device of *disconnecting* and only polling 
periodically. Even here, though - why are these devices not using 
special link layers? For example, 802.11 in particular is terrible at 
power consumption for this sort of device. It's a high-speed technology 
intended to provide XXX megabit speeds, not optimizing low power. Why 
are we trying to use it?"


That is mostly Lorenzo's personal views about different potential 
problems, and isn't something I can cut and paste into the document as a 
PS, which is really what "send text" means.


Note that the document already has a goals section. If you disagree with 
it, then please suggest edits, additions, removals.

Thanks,
    Erik

>
> --
> JINMEI, Tatuya
>


From nobody Thu Apr 23 15:47:39 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0080B1A8A11 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 15:47:38 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSEVsKj3Ydon for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 15:47:37 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 C3EFC1A8A4F for <ipv6@ietf.org>; Thu, 23 Apr 2015 15:47:23 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3NMlJO7017804 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Apr 2015 15:47:19 -0700
Message-ID: <55397677.2040107@acm.org>
Date: Thu, 23 Apr 2015 15:47:19 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Erik Nordmark <nordmark@acm.org>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com> <55368297.6080006@acm.org> <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com>
In-Reply-To: <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbOfBhaO4qY7SASqfMeqOSwNjPvcxC0GGmcSWFOjwSYdNaVWreDtGyQ935KDfRdXvQc38pbQdXKqY40V/bwa4ec
X-Sonic-ID: C;hBzMsgrq5BGgZIY+Bvepxg== M;ZgXjsgrq5BGgZIY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1xicvC2kflvrSm1eR9DEnVb2hl0>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 22:47:38 -0000

On 4/22/15 7:19 AM, Lorenzo Colitti wrote:
>
>         Perhaps the issue here is that we don't agree on a problem
>         statement, or more accurately, what we're trying to accomplish
>         with this drafts.
>
>
>     You've said that for > 2 years now, but never provided any useful
>     suggestions.
>
>
> But it's impossible for me, or anyone else, to provide a useful 
> suggestion without a problem statement.
Lorenzo,

I hope you are seeing that you are going in circles. You ask for a 
problem statement, and when I point you at one (such as the Goals 
section in this draft), you say it is insufficient for what you think it 
should say. When I ask what you want it to include you say it is 
impossible for you to help since an acceptable (to you) problem 
statement isn't written yet.


I think the fundamental difference in opinion between you and me on this 
subject is that you don't care of communities that work on hosts that 
sleep on schedule end up doing whatever they want to IPv6 Neighbor 
Discovery (at least you have said at the mike that you don't care about 
those types of devices - and that they can go to some other WG). Thus 
time and again you dismiss any arguments relating to such hosts. Such an 
attitude is likely to cause fragmentation of the protocols and 
implementations for IPv6.

I really really really want to avoid fragmenting IPv6 and ND into 
different protocols for different types of devices. I think such 
fragmentation is harmful to IPv6 and its application across a large set 
of networks and devices - many of which do not yet use IP technology.

I hope there are others in the IPv6 working group that care about 
avoiding fragmentation while applying IPv6 to different IoT devices and 
other constrained devices, and the call for WG adoption of this draft 
seem to already have half a dozen supporters. That is promising to those 
of us that want to avoid fragmentation.

Regards,
    Erik



From nobody Thu Apr 23 19:28:50 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A12D1B2B46 for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 19:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 HnY9d0Dh4S-P for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 19:28:47 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001: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 C0C661B2B20 for <ipv6@ietf.org>; Thu, 23 Apr 2015 19:28:35 -0700 (PDT)
Received: by igbhj9 with SMTP id hj9so4600792igb.1 for <ipv6@ietf.org>; Thu, 23 Apr 2015 19:28:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=yiUxutJdczKFDYYBfzYQgqiahFnUUJczS2dw8W8kIds=; b=RssmficFWsWl9rwdKZ/crEXiotoOlr0GbLVc5tR/DAKojvgjwVMdpV769usNCEVkbD iNnll0qYHXxkjIStDUElra9CIdH5xbeZaSlUY/8lBnAnJIOaCdksfYqOsvtyMgGtxpBa 7mdfInKoteTW12o2WWTQBS41NDvnQa5M04PLhSD60+AQwAPLy4BpO+fQ9p2hkOUEw1dR jPKn8M3eyqendYb5qiuzP1TAWM5bA6CH490ypFj+gG+LxsiFsVdEA2mv1HiWVnKZb9L/ 45Yp1pvXWVEPVqpd6pBOmEGj8dGT8d4DFuFFJ/9OZyMN2QEt5qzDL6nmVsGWo3/eMMIL DVBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=yiUxutJdczKFDYYBfzYQgqiahFnUUJczS2dw8W8kIds=; b=PnchZDZfNbLKEfJNZN5PWSB/9F2qEvIv6LGXebmwTyb1iNP7+Vlowt3BDfcMdf6wTj T0bYB5rF7wGsHn0rMprIlpvBQhy1sYEc0GX0CfMACgKE3y+vZE7pBHy+bEEdwKXFvN+9 Y+d3B4iYyBsGccSSCmOWIZ/3+F7ogOLiPxn0+4znkh7xzjOrEImT1ShBvxQ3HF5aCajE VcZ38TCDQ+eY7BpNOOj0EqzYaEsGsgA7S5BqRpRgK7vLyobzaRhHNUdR6Nbl+JKZ/fOq r03q/OhOLitqvtS0SkeR0+q1e4Tzu5oZs3LMG9cW8TO5glSm4bhCBTDUjZw/J78qPjk9 SS1Q==
X-Gm-Message-State: ALoCoQnW9/0btfk9INlYaWZH75BLGgSRU+sRraUmKXZYHFdVFLLYW8JEQB06U6q1KDw1KVpjISTG
X-Received: by 10.107.33.21 with SMTP id h21mr8189107ioh.1.1429842515238; Thu, 23 Apr 2015 19:28:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Thu, 23 Apr 2015 19:28:14 -0700 (PDT)
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 24 Apr 2015 11:28:14 +0900
Message-ID: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com>
Subject: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=001a1140408c34c98005146f275d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/YYSzKqsLt1rggrrKZPiRLkMGUk0>
Cc: Erik Nordmark <nordmark@acm.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 02:28:49 -0000

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

Hi,

in the context of looking at the RS refresh draft, I looked at the
assertion in draft-garneij-6man-nd-m2m-issues-00 , which is cited as one of
the use cases. IIUC the issue boils down to: in a network with a large
number of completely silent devices, the periodic RA, which is sent on
average every 1575 seconds, ends up being the dominating factor in paging
channel usage.

I think there is an easy way to fix this: raise the maximum RA lifetime and
the maximum RA interval as proposed by draft-krishnan-6man-maxra-01. That
will lower the paging cost by a factor of 12x (21845 / 1800). If a that is
not sufficient, then the cost can further be lowered by ensuring that the
entity that deals with the mobile node's IP traffic (in 3GPP networks, the
GGSN or the PGW) sends RAs opportunistically, bundling them with any other
packets that it needs to send the device. If the device receives at least
one packet in every 21845-second interval, then the extra paging cost goes
down to zero. Even if the device never receives *any* packets (though that
seems really unlikely: how does it know if it is reporting correctly, and
that its controller is still receiving its traffic? The internet does not
have zero loss), the RAs can still be sent opportunistically when the
device *sends* a packet. The PGW will see the device send the packet and
can opportunistically send the RA, knowing that the device will be in a
high power state for a little while after sending the packet.

Also, I think we should carefully consider the impact of the problem. This
is very much a contrived worst-case scenario. If the network is a general
purpose network, such as a commercial LTE network, the paging cost will in
general be much higher, because that network also provides service to
devices such as phones and tables that are orders of magnitude more chatty
(due to users wanting to use the connection they paid for). So in general,
commercial networks will not be optimized for this sort of usage. It's true
that it's possible to optimize for M2M devices, and ensure that those
devices use as few resources as possible, but in a general-purpose network,
there's likely no point in doing that because the chattier devices are
causing most of the cost anyway (Amdahl's law).

Also note that the impact is on *paging channel* usage, not *power* usage.
I'm not an expert, but AIUI in current radio technologies such as LTE, for
a node that only sends a short burst of data every 12 hours, power is
likely dominated by the cost of staying attached to the network, listening
to the paging group, dealing with location area updates, etc. rather than
sending the packets. If you care about power, the right strategy is to
disconnect from the network completely, and only reconnect when you have
something to transmit.

Cheers,
Lorenzo

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

<div dir=3D"ltr">Hi,<div><br></div><div>in the context of looking at the RS=
 refresh draft, I looked at the assertion in=C2=A0draft-garneij-6man-nd-m2m=
-issues-00 , which is cited as one of the use cases. IIUC the issue boils d=
own to: in a network with a large number of completely silent devices, the =
periodic RA, which is sent on average every 1575 seconds, ends up being the=
 dominating factor in paging channel usage.</div><div><br></div><div>I thin=
k there is an easy way to fix this: raise the maximum RA lifetime and the m=
aximum RA interval as proposed by=C2=A0draft-krishnan-6man-maxra-01. That w=
ill lower the paging cost by a factor of 12x (21845 / 1800). If a that is n=
ot sufficient, then the cost can further be lowered by ensuring that the en=
tity that deals with the mobile node&#39;s IP traffic (in 3GPP networks, th=
e GGSN or the PGW) sends RAs opportunistically, bundling them with any othe=
r packets that it needs to send the device. If the device receives at least=
 one packet in every 21845-second interval, then the extra paging cost goes=
 down to zero. Even if the device never receives *any* packets (though that=
 seems really unlikely: how does it know if it is reporting correctly, and =
that its controller is still receiving its traffic? The internet does not h=
ave zero loss), the RAs can still be sent opportunistically when the device=
 *sends* a packet. The PGW will see the device send the packet and can oppo=
rtunistically send the RA, knowing that the device will be in a high power =
state for a little while after sending the packet.<br></div><div><br></div>=
<div>Also, I think we should carefully consider the impact of the problem. =
This is very much a contrived worst-case scenario. If the network is a gene=
ral purpose network, such as a commercial LTE network, the paging cost will=
 in general be much higher, because that network also provides service to d=
evices such as phones and tables that are orders of magnitude more chatty (=
due to users wanting to use the connection they paid for). So in general, c=
ommercial networks will not be optimized for this sort of usage. It&#39;s t=
rue that it&#39;s possible to optimize for M2M devices, and ensure that tho=
se devices use as few resources as possible, but in a general-purpose netwo=
rk, there&#39;s likely no point in doing that because the chattier devices =
are causing most of the cost anyway (Amdahl&#39;s law).<br></div><div><br><=
/div><div>Also note that the impact is on *paging channel* usage, not *powe=
r* usage. I&#39;m not an expert, but AIUI in current radio technologies suc=
h as LTE, for a node that only sends a short burst of data every 12 hours, =
power is likely dominated by the cost of staying attached to the network, l=
istening to the paging group, dealing with location area updates, etc. rath=
er than sending the packets. If you care about power, the right strategy is=
 to disconnect from the network completely, and only reconnect when you hav=
e something to transmit.<br></div><div><br></div><div>Cheers,</div><div>Lor=
enzo</div></div>

--001a1140408c34c98005146f275d--


From nobody Thu Apr 23 22:44:05 2015
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA50C1A1EFC for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 19:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 QzLmXTRlF0Qm for <ipv6@ietfa.amsl.com>; Thu, 23 Apr 2015 19:48:37 -0700 (PDT)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::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 5A7041A0235 for <ipv6@ietf.org>; Thu, 23 Apr 2015 19:48:37 -0700 (PDT)
Received: by qgej70 with SMTP id j70so17294279qge.2 for <ipv6@ietf.org>; Thu, 23 Apr 2015 19:48:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=21hBdE6OJpvr0ob0988gysgDYV1Y2FjONqKThuLHfqk=; b=WoSGZzS2wmU/p2mZx55rbF/TcggoQ22RRFcP8UfsdmDiExF7b6sNjdgNDX9JiapQwl 9EctNtTI82IhGe//r9+EzM8OIoK6oirbqWh0H3t4ACbXqmUFLCUUB75wUgfHMHddCMS3 akZ4i463Vz9bwXPVlYuUE3H4i3HAQxBimH6Hut5t1jzPRbVqjuLb0mAd38ZAGIw0pLg7 /jGrv6s7maW+I412gHhS/cUrVxs11EmLLKxYoqrs790Ft4YFe5ChXiU60M3QqvSSiRAm wySJugjAWmh+SbbHeRUivgo0RIVpUvGx1a2uM+WFb/bUPfvhjg76hAEssiOgea5UMnAQ OKNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=21hBdE6OJpvr0ob0988gysgDYV1Y2FjONqKThuLHfqk=; b=IY1Mbhw56ylvybiAj33RwdNiDs2UrPCBr0BMpIpjyIgEqXMUPtK5NP51GMESBIkRXz EThfZg+knF7Zzch6GQHZcwlYIaGl3sb0ViHaxLx8F3jiFvSL31yRk/K9Dy/bk5z5YAWt yA66vjTdbK/HfkGovqzMZbgID8gY/3Gs2hxh8HRRc8C3FaL4PZ+EXrNkmITH7XYEGGry ZFBde8WnAkXKa8NF2vHWtP0vz2H3H/du9NQY7lX9IDAEVnBpKxAZiBTNy8SkC62QlY6n A9jc5O4Jx641v17zCaaLWiRRt0c0OS7GDhAD/4/kBwjqh58L4KK4U3fnf2qCDOGZ96ii 2f4Q==
X-Gm-Message-State: ALoCoQkM6zfN4ZrqtRGui3jpWzaog+m3uywTIVtZ4SIV1b6VtH2hEnv/9LpH9Us7dU45RnrQ2/VT
X-Received: by 10.140.164.65 with SMTP id k62mr4549498qhk.61.1429843716578; Thu, 23 Apr 2015 19:48:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.208.6 with HTTP; Thu, 23 Apr 2015 19:48:16 -0700 (PDT)
In-Reply-To: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Fri, 24 Apr 2015 11:48:16 +0900
Message-ID: <CAAedzxp+VjvOiSdw1Qv9Uhad2+vd+QxB2-iv6Vv_BLXne47zBw@mail.gmail.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sMNrzLNLOElpHiFio7B89Kad9Sk>
X-Mailman-Approved-At: Thu, 23 Apr 2015 22:44:04 -0700
Cc: Erik Nordmark <nordmark@acm.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 02:48:38 -0000

Agreed.

Three additional points:

    [1] draft-krishnan-6man-maxra-01, Section 3, paragraph 1: +1.

    [2] draft-krishnan-6man-maxra-01, Section 3, paragraph 2: I think
it should be struck from that document and not be construed as
recommended here.

    [3] I would support a document that describes "opportunistic RAs".  :-)

On Fri, Apr 24, 2015 at 11:28 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> Hi,
>
> in the context of looking at the RS refresh draft, I looked at the assertion
> in draft-garneij-6man-nd-m2m-issues-00 , which is cited as one of the use
> cases. IIUC the issue boils down to: in a network with a large number of
> completely silent devices, the periodic RA, which is sent on average every
> 1575 seconds, ends up being the dominating factor in paging channel usage.
>
> I think there is an easy way to fix this: raise the maximum RA lifetime and
> the maximum RA interval as proposed by draft-krishnan-6man-maxra-01. That
> will lower the paging cost by a factor of 12x (21845 / 1800). If a that is
> not sufficient, then the cost can further be lowered by ensuring that the
> entity that deals with the mobile node's IP traffic (in 3GPP networks, the
> GGSN or the PGW) sends RAs opportunistically, bundling them with any other
> packets that it needs to send the device. If the device receives at least
> one packet in every 21845-second interval, then the extra paging cost goes
> down to zero. Even if the device never receives *any* packets (though that
> seems really unlikely: how does it know if it is reporting correctly, and
> that its controller is still receiving its traffic? The internet does not
> have zero loss), the RAs can still be sent opportunistically when the device
> *sends* a packet. The PGW will see the device send the packet and can
> opportunistically send the RA, knowing that the device will be in a high
> power state for a little while after sending the packet.
>
> Also, I think we should carefully consider the impact of the problem. This
> is very much a contrived worst-case scenario. If the network is a general
> purpose network, such as a commercial LTE network, the paging cost will in
> general be much higher, because that network also provides service to
> devices such as phones and tables that are orders of magnitude more chatty
> (due to users wanting to use the connection they paid for). So in general,
> commercial networks will not be optimized for this sort of usage. It's true
> that it's possible to optimize for M2M devices, and ensure that those
> devices use as few resources as possible, but in a general-purpose network,
> there's likely no point in doing that because the chattier devices are
> causing most of the cost anyway (Amdahl's law).
>
> Also note that the impact is on *paging channel* usage, not *power* usage.
> I'm not an expert, but AIUI in current radio technologies such as LTE, for a
> node that only sends a short burst of data every 12 hours, power is likely
> dominated by the cost of staying attached to the network, listening to the
> paging group, dealing with location area updates, etc. rather than sending
> the packets. If you care about power, the right strategy is to disconnect
> from the network completely, and only reconnect when you have something to
> transmit.
>
> Cheers,
> Lorenzo
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Fri Apr 24 15:21:12 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90B411A86DD; Fri, 24 Apr 2015 15:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJhwUNGWvLtc; Fri, 24 Apr 2015 15:21:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7981A8AAD; Fri, 24 Apr 2015 15:20:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 56AAD180208; Fri, 24 Apr 2015 15:19:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7527 on Enhanced Duplicate Address Detection
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150424221941.56AAD180208@rfc-editor.org>
Date: Fri, 24 Apr 2015 15:19:41 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/JenpRaecgTUGvmmSm4oqe2SvOn0>
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 22:21:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7527

        Title:      Enhanced Duplicate Address Detection 
        Author:     R. Asati, H. Singh,
                    W. Beebee, C. Pignataro,
                    E. Dart, W. George
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    rajiva@cisco.com, 
                    shemant@cisco.com, 
                    wbeebee@cisco.com,
                    cpignata@cisco.com, 
                    dart@es.net,
                    wesley.george@twcable.com
        Pages:      11
        Characters: 24528
        Updates:    RFC 4429, RFC 4861, RFC 4862

        I-D Tag:    draft-ietf-6man-enhanced-dad-15.txt

        URL:        https://www.rfc-editor.org/info/rfc7527

IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
discussed in Appendix A of RFC 4862.  That specification mentions a
hardware-assisted mechanism to detect looped back DAD messages.  If
hardware cannot suppress looped back DAD messages, a software
solution is required.  Several service provider communities have
expressed a need for automated detection of looped back Neighbor
Discovery (ND) messages used by DAD.  This document includes
mitigation techniques and outlines the Enhanced DAD algorithm to
automate the detection of looped back IPv6 ND messages used by DAD.
For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
self-heal after a loopback is placed and removed.  Further, for
certain access networks, this document automates resolving a specific
duplicate address conflict.  This document updates RFCs 4429, 4861,
and 4862.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Apr 27 09:55:52 2015
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB60C1A8720 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 08:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.789
X-Spam-Level: 
X-Spam-Status: No, score=-0.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_36=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 obU6quZ75Z2o for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 08:28:13 -0700 (PDT)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::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 E0B051A8706 for <ipv6@ietf.org>; Mon, 27 Apr 2015 08:28:12 -0700 (PDT)
Received: by qgdy78 with SMTP id y78so50946839qgd.0 for <ipv6@ietf.org>; Mon, 27 Apr 2015 08:28:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LlO0U7eK2hueT0aQei27gkL1k9Zw9KemrVmCcMzuTxk=; b=GRFnps/h6I4lclAWFH79ZY5a7j+ML+avaD0xhDNiKgrMp3mJKpX2dPZtBL8fun7c14 FznyuXwPQ0s2mgGZb9Grtbfj09k0rsnjNdWIJLcwtHuZb1d714wyMPahWSzP90vNkUvZ w6/B6L4wfCVNDKBJ2/5hgt8fNXnCZbai0qtUSQvMeKpOYw6Hj58NDmeVt8GVcDp4OQOL BNAy2r+PM3OEJFQf5maIAKACfC4+CQT2850TaAolWdpvxLZ1PJ57seoJdqd3cpr0AJDN ggaPZgry4geVToLiW65G9t2fVNTe4A/PuOwjFoQnyiIF/RKoQXO/BqMFWjUa3Hi9AHyM 5atA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=LlO0U7eK2hueT0aQei27gkL1k9Zw9KemrVmCcMzuTxk=; b=Elx64GIwgHCnp6pQEHSIT3Duk5Tqf2aRbZFSr6T2cNxuJzYrXhk1sF1oEn4DY307kX uBIKD+KwNN4vkWzmyFQESOKJTTh3IMLsqyLETl0G2Sa2Ma/rMmyIiE5PnjDoCfxikmgZ WZvUiV2UUdw0ztPcvIxONnODU5Ln68OOh8FvI0WSCf2Gt2O08r6B8hWZQEOxkr1y1wUu hRk3qsJ13t4HBSwJqqGbmXRl1lM+UFyEeHIoEuWb79ik33zbDCrSe4SSk4034FPwIUJV RUmJcgcMf9o6hNEsSt0wImh8ST0LvhG0ZEVld3xk8sxJj3lpaGc6Qc7ACukR0TvoBqgM h9yg==
X-Gm-Message-State: ALoCoQkmnZLWPZJxzuWUs02vtxRCOoTZ7advFhnpOyiqt0MbqOD7mz8RkdSpQdjlRDU1ylHHY2Jr
X-Received: by 10.140.100.200 with SMTP id s66mr7783556qge.1.1430148492104; Mon, 27 Apr 2015 08:28:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.208.6 with HTTP; Mon, 27 Apr 2015 08:27:51 -0700 (PDT)
In-Reply-To: <55397677.2040107@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com> <55368297.6080006@acm.org> <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com> <55397677.2040107@acm.org>
From: Erik Kline <ek@google.com>
Date: Tue, 28 Apr 2015 00:27:51 +0900
Message-ID: <CAAedzxrdwzPgvQYmxNJ9EMNc1QjM7eOx90oBprydvAMiHh3iJA@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
To: Erik Nordmark <nordmark@acm.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_2QjoYnruHx17svVmYW3p0MK9wo>
X-Mailman-Approved-At: Mon, 27 Apr 2015 09:55:51 -0700
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 15:28:14 -0000

A question comes to mind: what might the operational guidance be for
setting the refresh timer value in the RA?

Observation: it almost certainly shouldn't be /longer/ than the router
lifetime, even if the prefix lifetimes are infinite.

Reasonable stab in the dark: refresh timer value in the RA should be
in the neighborhood of some fraction (1/2, 2/3) * min(router lifetime,
prefix lifetimes...).

If that turns out to be the case, then the host can compute this timer
value for itself, sleep on its own schedule, and wake up whenever it
wants and send a unicast RS.  At that point this isn't a protocol
change but rather an operational document.  [1]

At the very least, this is a simple enough experiment to perform for
people writing the code on the affected devices (doesn't require
router vendor code changes).  Has anybody done this and measured the
outcome?

-Erik the Lesser


[1]  Note that the node MUST to be ready to basically re-attach from
scratch in the event that the router has gone (I swapped my IoT device
access point for a new model, and it got a new prefix too, while
everyone listening was asleep, for example).  So guessing a wrong
timer value must be non-fatal for the node.  At worst it won't be
"optimal" but i'm curious to know what the impact of deviation from
"optimal" would really be in these networks, given that nodes are all
going to go for the longest possible timer value.


From nobody Mon Apr 27 11:26:37 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B97151A90E5 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 11:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.711
X-Spam-Level: 
X-Spam-Status: No, score=-3.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nonYZaP2cSKj for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 11:26:34 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56B2D1A90D5 for <ipv6@ietf.org>; Mon, 27 Apr 2015 11:26:33 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 881CA6175; Mon, 27 Apr 2015 11:26:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=0Maq+0Wd7HF8JxP3BiRDefIksUE=; b= L5eKwPBmAEr91zGs2GztnBiCWDBkynhXNuq4HMIwNYQotEaQS75r7BoYWDS3DMsQ E5mkNWRijpVIVRtWhj7dUpVUlcxLWz1JhVsiq9h9HYZohAA/LcOWCxusaYbDguz3 6WqLMzzwaKPzpsJEm5+hBdv8xFMjBFnMP84pD1qsQxg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=S5ARrpUJ6u2V1xhtmMIjOF54e1 RbnudxJFy07ekPdYMsmgmbDFrDtJaovfLEeJ6hTIiw/EcsO9KcTASv+6PYIak4Nr HlnCYhVtGJKZWnpuSrhWko6m2G6QrdOCdDE1MnOFXI0/nIDfOQPNApF7o1+wZU3y sEKEgmSqMqiFNWDOg=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 24DC66087; Mon, 27 Apr 2015 11:26:32 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 9B88E4383EBA; Mon, 27 Apr 2015 20:26:20 +0200 (CEST)
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_77C5F497-CD27-426F-9F3F-22D659F73A80"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAAedzxrdwzPgvQYmxNJ9EMNc1QjM7eOx90oBprydvAMiHh3iJA@mail.gmail.com>
Date: Mon, 27 Apr 2015 20:26:19 +0200
Message-Id: <DA6BA6AC-2DEC-4866-AE41-3102337DD5B5@employees.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com> <55368297.6080006@acm.org> <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com> <55397677.2040107@acm.org> <CAAedzxrdwzPgvQYmxNJ9EMNc1QjM7eOx90oBprydvAMiHh3iJA@mail.gmail.com>
To: Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/OPMaKhzMM3SGM2evW4OmF8Tjdjs>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Erik Nordmark <nordmark@acm.org>, Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 18:26:35 -0000

--Apple-Mail=_77C5F497-CD27-426F-9F3F-22D659F73A80
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Erik,

> A question comes to mind: what might the operational guidance be for
> setting the refresh timer value in the RA?
>=20
> Observation: it almost certainly shouldn't be /longer/ than the router
> lifetime, even if the prefix lifetimes are infinite.

indeed.

> Reasonable stab in the dark: refresh timer value in the RA should be
> in the neighborhood of some fraction (1/2, 2/3) * min(router lifetime,
> prefix lifetimes...).
>=20
> If that turns out to be the case, then the host can compute this timer
> value for itself, sleep on its own schedule, and wake up whenever it
> wants and send a unicast RS.  At that point this isn't a protocol
> change but rather an operational document.  [1]
>=20
> At the very least, this is a simple enough experiment to perform for
> people writing the code on the affected devices (doesn't require
> router vendor code changes).  Has anybody done this and measured the
> outcome?

I think this was briefly discussed on the mailing list. the short-coming =
with this scheme would be the lack of explicit information from the =
network to the host and from the host to the network that this is =
supported.

it would at least be a lot harder for the network to identify and deal =
with legacy hosts without explicit notification of support.

cheers,
Ole


--Apple-Mail=_77C5F497-CD27-426F-9F3F-22D659F73A80
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

iQEcBAEBCgAGBQJVPn9MAAoJEFuJXizso86ggjQH/RX7PIzO7cdWiVKzLOgL6ASw
DmhmYYiXyXiL52oJmWe5FEPpNZuM0uBMhh2aBVbHYp+xHEeR4X/pnpCEdgkREG8a
hyMhIG5usS/mOCbM0UeCJ3SBnrEOZHLuXh7hbAk+eZ73F+hhtzY2bN7y6ZWIGwc7
mh+XjV53vr+0wWpYSVBy6b6gwkLFg0klBlT9FR/vQ76ymWQynv2nnsqR2dC7JCgA
Tu+XLZVM1W5ZFKfhzGm8G+HOvFFe2pqWZcmv8Ytv0ybeG4lpf3qcX/ax8NMFfnUJ
oRs20J4JwW9/tSs9m+AvR11CFxxxW420oxxqziXtq4dlwuokcaf2FTgKGHqnBJc=
=hYGl
-----END PGP SIGNATURE-----

--Apple-Mail=_77C5F497-CD27-426F-9F3F-22D659F73A80--


From nobody Mon Apr 27 11:35:42 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85B721A90F1; Mon, 27 Apr 2015 11:35: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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhJH4P3LSSOg; Mon, 27 Apr 2015 11:35:40 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 73A5C1A90FB; Mon, 27 Apr 2015 11:35:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150427183539.11133.94565.idtracker@ietfa.amsl.com>
Date: Mon, 27 Apr 2015 11:35:39 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fgKtWGUpBdbRb0HaGBzTM9FGgj0>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 18:35:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Privacy Considerations for IPv6 Address Generation Mechanisms
        Authors         : Alissa Cooper
                          Fernando Gont
                          Dave Thaler
	Filename        : draft-ietf-6man-ipv6-address-generation-privacy-05.txt
	Pages           : 16
	Date            : 2015-04-27

Abstract:
   This document discusses privacy and security considerations for
   several IPv6 address generation mechanisms, both standardized and
   non-standardized.  It evaluates how different mechanisms mitigate
   different threats and the trade-offs that implementors, developers,
   and users face in choosing different addresses or address generation
   mechanisms.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-address-generation-privacy/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-ipv6-address-generation-privacy-05

A diff from the previous version is available at:
https:https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ipv6-address-generation-privacy-05


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/


From nobody Mon Apr 27 12:44:15 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708751A1A4F for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 12:44: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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xA_mlGFozkI for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 12:44:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::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 B42881A1A0C for <ipv6@ietf.org>; Mon, 27 Apr 2015 12:44:10 -0700 (PDT)
Received: from [186.134.1.16] (helo=[192.168.123.128]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Ymowm-0001V1-0q; Mon, 27 Apr 2015 21:44:07 +0200
Message-ID: <553E8108.1000202@si6networks.com>
Date: Mon, 27 Apr 2015 15:33:44 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>,  draft-ietf-6man-ipv6-address-generation-privacy@tools.ietf.org
Subject: Re: Chair's review: draft-ietf-6man-ipv6-address-generation-privacy
References: <573BE2D3-0B0D-435F-A1A1-6755B9BEC256@employees.org>
In-Reply-To: <573BE2D3-0B0D-435F-A1A1-6755B9BEC256@employees.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/e3wKxiU72A1-5vk4otXr65fTb0Y>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 19:44:14 -0000

Hi, Ole,

On 03/06/2015 05:51 PM, Ole Troan wrote:
> Issue #1: The reference to RFC2462 in the Introduction; is that meant
> as a "historical" reference, then it should point to RFC1971,
> otherwise it should be updated to RFC4862.

You're right. Changed!



> Issue #2: With regards to the use of "network" in several places,
> e.g "An address that does not vary over time within the same
> network."
> 
> Suggest s/network/IPv6 link/ A "network" can be a larger piece of
> topology where addresses would change.

Good point. Change applied!



> Issue #3 (nit): Title: 3 . Weaknesses in IEEE-identifier-based IIDs 
> It might be more general to replace IEEE-identifier-based IIDs with
> "Constant IIDs" which you define in the terminology session? Or
> define it?

The current text is more specific. IEEE-identifier-based IIDs allow for
device (hardware)-specific attacks, while other constant IIDs don't.



> Issue #4 - section 3.1: CURRENT: As with other identifiers, an IPv6
> address can be used to correlate the activities of a host for at
> least as long as the lifetime of the address.  The correlation made
> possible by IEEE-identifier-based IIDs is of particular concern
> because MAC addresses are much more permanent than, say, DHCP leases.
> MAC addresses tend to last roughly the lifetime of a device's network
> interface, allowing correlation on the order of years, compared to
> days for DHCP.
> 
> ItÂs our understanding that DHCP doesnÂt change addresses when the
> lease expires, it just does a renew.  This means that a DHCP provided
> address could last for a long time and have many of the correlation
> problems that IEEE MAC based addresses have.  Further, we think that
> even for a node that leave a link and comes back later, it may be
> given the same IP address (if available) as it had before because the
> DHCP server remembered it MAC address.  We think the text in the
> draft overstates the differences and implies that DHCP addresses are
> much better in this regard.

Fixed. Changed to:
"   As with other identifiers, an IPv6 address can be used to correlate
   the activities of a host for at least as long as the lifetime of the
   address.  The correlation made possible by IEEE-identifier-based IIDs
   is of particular concern since they last roughly for the lifetime of
   a device's network interface, allowing correlation on the order of
   years."

(discussing DHCPv6 here was rather off-topic)




> Issue #5 - section 3.2:
> 
> OLD: Even if the host does not respond, the first hop router will
> usually respond with an ICMP Address Unreachable when the host is not
> present, and be silent when the host is present.
> 
> NEW: Even if the host does not respond, the first hop router will
> usually respond with an ICMPv6 Destination Unreachable message when
> the host is not present, and be silent when the host is present.

Fixed as:

"Even if the host  does not respond, the first hop router will usually
respond with an  ICMP Destination Unreachable/Address Unreachable (type
1, code 3) when the host is not present, and be silent  when the host is
present."


> Issue #6 - section 3.3: OLD: This erases much of the protection
> against address scanning that the larger IPv6 address space was
> supposed to provide as compared to IPv4.
> 
> NEW: This erases some of the protection against address scanning that
> the larger IPv6 address space could provide as compared to IPv4.
> 
> As far as we remember, the IPv6 was not designed specifically to
> protect against scanning attacks, it was a by product of the design. 
> ÂErases much of the protectionÂ seems overstated and we suggest
> replacing ÂmuchÂ with ÂsomeÂ.

We've changed it to:
"This erases much of the protection against address scanning that the
larger IPv6 address space could provide as compared to IPv4."

(IEEE-derived IIDs can reduce the initial 2**64  search space to 2**24
-- that's "much").




> Issue #7- section 4: OLD: The idea was for temporary addresses to be
> used for outgoing connections (e.g., web browsing) while maintaining
> the ability to use a stable address when more address stability is 
> desired (e.g., in DNS advertisements).
> 
> NEW: The idea was for temporary addresses to be used for outgoing
> connections (e.g., web browsing) while maintaining the ability to use
> a stable address when more address stability is desired (e.g.,
> published in DNS).

Changed to:
"They use IIDs that are randomly generated and change daily by default.
The idea was for temporary addresses to be  used for outgoing
connections (e.g., web browsing) while maintaining the ability to use
a stable address when more address stability is desired (e.g., for IPv6
addresses published in the DNS)."



> Issue #8 - section 5.2: s/MAC-derived suffixes/IEEE-identifier-based
> IIDs

Fixed!


> Issue #9 - section 5.3: There is nothing actionable here, we suggest
> this section is removed.

This section notes that some IIDs (like CGAs) might be challenging to
implement for non-technical reasons. We've kept this section. But please
let us know if you strongly feel about this change. (If so, hopefully we
could remove it as part of IETF LC).



> Issue #10 - References: The references section may need more review.
> There are very few references that this document depends on. For the
> Normative references it might be prudent to move obsoleted document
> references out of the normative secion. RFC1972, RFC2462, RFC3041,
> RFC3484. RFC3314 and RFC6265 may also go in the Informative section.

You're right. Fixed!

Thanks so much!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492








From nobody Mon Apr 27 12:44:33 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9B561A1B24 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 12:44:32 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmkN2e6Qp-8V for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 12:44:31 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::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 795DF1A1EF5 for <ipv6@ietf.org>; Mon, 27 Apr 2015 12:44:25 -0700 (PDT)
Received: from [186.134.1.16] (helo=[192.168.123.128]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Ymox5-0001VI-Oa; Mon, 27 Apr 2015 21:44:24 +0200
Message-ID: <553E848B.4070006@si6networks.com>
Date: Mon, 27 Apr 2015 15:48:43 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>,  Ole Troan <otroan@employees.org>, "draft-ietf-6man-ipv6-address-generation-privacy@tools.ietf.org" <draft-ietf-6man-ipv6-address-generation-privacy@tools.ietf.org>
Subject: Re: Chair's review: draft-ietf-6man-ipv6-address-generation-privacy
References: <573BE2D3-0B0D-435F-A1A1-6755B9BEC256@employees.org> <1520786418.400995.1425891445550.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1520786418.400995.1425891445550.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/H5e3rK90gvLOJZ5lM-RtckmXBVc>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 19:44:32 -0000

On 03/09/2015 05:57 AM, Mark ZZZ Smith wrote:
> 
> Issue #4 - section 3.1:
> CURRENT:
>   As with other identifiers, an IPv6 address can be used to correlate
>   the activities of a host for at least as long as the lifetime of the
>   address.  The correlation made possible by IEEE-identifier-based IIDs
>   is of particular concern because MAC addresses are much more
>   permanent than, say, DHCP leases.  MAC addresses tend to last roughly
>   the lifetime of a device's network interface, allowing correlation on
>   the order of years, compared to days for DHCP.
> 
> It’s our understanding that DHCP doesn’t change addresses when the lease expires, it just does a renew.  This means that a DHCP provided address could last for a long time and have many of the correlation problems that IEEE MAC based addresses have.  Further, we think that even for a node that leave a link and comes back later, it may be given the same IP address (if available) as it had before because the DHCP server remembered it MAC address.  We think the text in the draft overstates the differences and implies that DHCP addresses are much better in this regard.
> 
> / Actually, looking at the DHCPv6 text in the draft, it is probably necessary to state that DHCPv6 address selection is influenced by whether the client requests an IA_NA (Identity association for non-temporary addresses) or an IA_TA (
> Identity association for temporary addresses) (discussed in section 12. of RFC3315)

We've fixed this section, and have also added some related text (as the
one you've suggested) to the DHCPv6 section.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Apr 27 15:22:04 2015
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B34281A9123 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 15:22:02 -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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFDEnCedv-5k for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 15:22:01 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32D3F1A9111 for <ipv6@ietf.org>; Mon, 27 Apr 2015 15:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=961; q=dns/txt; s=iport; t=1430173321; x=1431382921; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=0k+axN50hRLcAOqz/QJIoPvOAp5vHBWs/+KVuJf4s24=; b=akMM6qVOk+bufti0ARPgWVth1WyBCtEbCMc638Wo7K9jE7w/IEkDsQn8 wo43fCIjFebF4wQxU8iP6gBx/lZVNv4FXVBhIsxt5KYZ++yN5/E6//UPu 6x7tE9BM2aQFxIXV2pe5ccMvYlX+WtvjQ8BHKeFFe1/Xw0PlGgujMGOf2 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByBADstT5V/4kNJK1cgwxTXAXFVGYJgVSGAgKBNTgUAQEBAQEBAYEKhCABAQEEOj8MBAIBCBEEAQELFAkHIREUBwEBBQMCBA4FCBKHfQMRDcIHDYU0AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4s4gk2CBzEHBoMRgRYFkVWEAVqECoFVgSGNaoZVI2CBWIE8b4FEgQABAQE
X-IronPort-AV: E=Sophos;i="5.11,660,1422921600"; d="scan'208";a="144999885"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-7.cisco.com with ESMTP; 27 Apr 2015 22:22:00 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t3RMM0Sd002677 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Apr 2015 22:22:00 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.245]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Mon, 27 Apr 2015 17:22:00 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: IPv6 List <ipv6@ietf.org>
Subject: FW: ETSI standard on "IPv6-based Industrial Internet leveraging 6TiSCH Technology"
Thread-Topic: ETSI standard on "IPv6-based Industrial Internet leveraging 6TiSCH Technology"
Thread-Index: AQHQgTY4t7hAl7fyQmCCLbiV1HYTH51hbZew
Date: Mon, 27 Apr 2015 22:21:17 +0000
Deferred-Delivery: Mon, 27 Apr 2015 22:22:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD849E10949@xmb-rcd-x01.cisco.com>
References: <FBE572D8-1DCF-4122-809B-D85EAA5C6BAD@cisco.com> <41C59F3B-EBA9-4428-82B8-30491118D837@gmail.com>
In-Reply-To: <41C59F3B-EBA9-4428-82B8-30491118D837@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.154.176.254]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vXUjXhZc5LRnZiWJLRMIvEsFf6k>
Cc: Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 22:22:02 -0000

Dear all:

Ralph from the IAB was kind enough to inform the IAB and the IESG at the IE=
TF on our behalf.

He also indicated me that " The usual way would be to submit the Liaison St=
atement from ETSI to the IETF at https://datatracker.ietf.org/liaison/add/?=
incoming ".

The IETF will know be waiting for us to post the statement following the li=
nk above.=09

Cheers,

Pascal


-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: lundi 27 avril 2015 15:05
To: IAB; IESG
Cc: Fred Baker (fred); Pascal Thubert (pthubert)
Subject: Fwd: ETSI standard on "IPv6-based Industrial Internet leveraging 6=
TiSCH Technology"

FYI - ETSI has formed a new ISG called IP6.  We can expect a liaison statem=
ent soon from ETSI regarding this new area of work.

You can find an announcement here: http://www.telecompaper.com/news/etsi-gr=
oup-starts-work-on-ipv6-integration-and-deployment--1079043

- Ralph



From nobody Mon Apr 27 17:55:31 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B27D1ACDD9; Mon, 27 Apr 2015 17:55:30 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJN5ZILcQQwR; Mon, 27 Apr 2015 17:55:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 180881ACDD3; Mon, 27 Apr 2015 17:55:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150428005529.16774.5976.idtracker@ietfa.amsl.com>
Date: Mon, 27 Apr 2015 17:55:29 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/aE1vjNIudiE1GY8jl-jrxmZga3Y>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 00:55:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Deprecating the Generation of IPv6 Atomic Fragments
        Authors         : Fernando Gont
                          Will(Shucheng) Liu
                          Tore Anderson
	Filename        : draft-ietf-6man-deprecate-atomfrag-generation-01.txt
	Pages           : 17
	Date            : 2015-04-27

Abstract:
   The core IPv6 specification requires that when a host receives an
   ICMPv6 "Packet Too Big" message reporting a "Next-Hop MTU" smaller
   than 1280, the host includes a Fragment Header in all subsequent
   packets sent to that destination, without reducing the assumed Path-
   MTU.  The simplicity with which ICMPv6 "Packet Too Big" messages can
   be forged, coupled with the widespread filtering of IPv6 fragments,
   results in an attack vector that can be leveraged for Denial of
   Service purposes.  This document briefly discusses the aforementioned
   attack vector, and formally updates RFC2460 such that generation of
   IPv6 atomic fragments is deprecated, thus eliminating the
   aforementioned attack vector.  Additionally, it formally updates
   RFC6145 such that the Stateless IP/ICMP Translation Algorithm (SIIT)
   does not rely on the generation of IPv6 atomic fragments, thus
   improving the robustness of the protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-deprecate-atomfrag-generation/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-generation-01

A diff from the previous version is available at:
https:https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-deprecate-atomfrag-generation-01


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/


From nobody Mon Apr 27 18:01:30 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF28F1ACDD7 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 18:01:29 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mIq1ll_QjYBS for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 18:01:27 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::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 434531ACDD3 for <ipv6@ietf.org>; Mon, 27 Apr 2015 18:01:27 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Ymttp-0003X6-L1; Tue, 28 Apr 2015 03:01:21 +0200
Message-ID: <553EDBDC.6020108@si6networks.com>
Date: Mon, 27 Apr 2015 22:01:16 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com>
In-Reply-To: <20150428005529.16774.5976.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_POvgJ7EZ0N3Fb-pf2qp7juzzpo>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 01:01:29 -0000

Folks,

We've rev'ed the aforementioned I-D with minor clarifications requested
by implementers:
<https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-generation-01>

We think the current version of the I-D is ready for WGLC.

Thoughts?

Thanks!

Best regards,
Fernando




On 04/27/2015 09:55 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 IPv6 Maintenance Working Group of the IETF.
> 
>         Title           : Deprecating the Generation of IPv6 Atomic Fragments
>         Authors         : Fernando Gont
>                           Will(Shucheng) Liu
>                           Tore Anderson
> 	Filename        : draft-ietf-6man-deprecate-atomfrag-generation-01.txt
> 	Pages           : 17
> 	Date            : 2015-04-27
> 
> Abstract:
>    The core IPv6 specification requires that when a host receives an
>    ICMPv6 "Packet Too Big" message reporting a "Next-Hop MTU" smaller
>    than 1280, the host includes a Fragment Header in all subsequent
>    packets sent to that destination, without reducing the assumed Path-
>    MTU.  The simplicity with which ICMPv6 "Packet Too Big" messages can
>    be forged, coupled with the widespread filtering of IPv6 fragments,
>    results in an attack vector that can be leveraged for Denial of
>    Service purposes.  This document briefly discusses the aforementioned
>    attack vector, and formally updates RFC2460 such that generation of
>    IPv6 atomic fragments is deprecated, thus eliminating the
>    aforementioned attack vector.  Additionally, it formally updates
>    RFC6145 such that the Stateless IP/ICMP Translation Algorithm (SIIT)
>    does not rely on the generation of IPv6 atomic fragments, thus
>    improving the robustness of the protocol.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-deprecate-atomfrag-generation/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-generation-01
> 
> A diff from the previous version is available at:
> https:https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-deprecate-atomfrag-generation-01
> 
> 
> 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/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Apr 27 19:11:54 2015
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E09C1ACDDA for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 19:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nq6qqXP5nhbr for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 19:11:52 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD5291ACE15 for <ipv6@ietf.org>; Mon, 27 Apr 2015 19:11:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1803; q=dns/txt; s=iport; t=1430187112; x=1431396712; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PXSf4QTTW4tihUhGEmrhwTPIvwBfkv1WsHphQfaWp7k=; b=FroaNIHFhlmlE9LxbYwZavNQFJeUExBWIZcsSxIRQ8YvrBHyS4WuxsKw BoW//3BTX5/RBeEQVoRzhaVpicUmInhJyNvWNqMv83rMZKU4EZaASGC1M MH2BIwfcHy4jRlMFfJApLKTaq3DgPE7XG/2JkosooD8kcOPW4v9N5qzna o=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BABQCg6z5V/4sNJK1cgwxTXAXGWoFUhgICgTI5EwEBAQEBAQGBCoQgAQEBAwF5BQsCAQgOCiMLMiUCBA4FDogVCA3HBgEBAQEBAQEBAQEBAQEBAQEBAQEBARMEiziFBQeDF4EWBZFVgXKBN1iGOIEihjiOByOCOIE8b4FEgQABAQE
X-IronPort-AV: E=Sophos;i="5.11,661,1422921600";  d="asc'?scan'208";a="145106602"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-4.cisco.com with ESMTP; 28 Apr 2015 02:11:51 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t3S2BpQq024880 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Apr 2015 02:11:51 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.172]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Mon, 27 Apr 2015 21:11:50 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Topic: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Index: AQHQgU7liPOJOD1i1UeQA2xTungMaZ1iAo4A
Date: Tue, 28 Apr 2015 02:11:49 +0000
Message-ID: <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com>
In-Reply-To: <553EDBDC.6020108@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_0B5B7A8B-E4EC-4919-A7FF-81E3FC6DBCEE"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EipiqYx4P7WGUkzTxMTBZ3aZceA>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 02:11:53 -0000

--Apple-Mail=_0B5B7A8B-E4EC-4919-A7FF-81E3FC6DBCEE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Apr 27, 2015, at 6:01 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> We've rev'ed the aforementioned I-D with minor clarifications =
requested
> by implementers:
> =
<https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-generation=
-01>
>=20
> We think the current version of the I-D is ready for WGLC.

The ID contains three essential parts: why the recommendations, a =
relatively minor change to RFC 2460, and some deep surgery on RFC 6145. =
Let me as a question on that last, if you would.

Have those proposed changes been vetted with the implementors you =
mentioned?

If this is the consensus of the working group, I personally would be in =
favor of churning 6145 rather than making future implementors read two =
documents in parallel. I would want to do that in 6man.

--Apple-Mail=_0B5B7A8B-E4EC-4919-A7FF-81E3FC6DBCEE
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 - http://gpgtools.org

iQEVAwUBVT7sY59ieig10VPpAQK8oQf/d4DkCQ9JUmpS6LMvFc28eiXpANV874MK
UXEextyLoLgJpDBfnyHDYXYTDWC+trHmf22bldb0AvR91JU+BIv1JIDv/s0RWdBZ
QItf0YUfT3Ie+DtPalsbsx4GzdI+e6dLx+KdPqKgcUWw3ZAIFzZ2Dj+wg0AB1II1
s7dhrhK+vnQDSFMfGGtGt0AxidOwJGZxC7r33waWm+7Wjrzxxm9BqlgyCcJldL7u
2dJUpNFG9zrNvFzm9dkRh7xLtKjbvb4rA9N3hWATKQPuX9I9CZnXdaJFV1FuiCae
XH2AWKDCoR+P8DT5az2hdJNm9PPCGVjUh/O1yBpsSnSDBjKmX2VZAg==
=GJ89
-----END PGP SIGNATURE-----

--Apple-Mail=_0B5B7A8B-E4EC-4919-A7FF-81E3FC6DBCEE--


From nobody Mon Apr 27 20:12:18 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD8521ACE2F for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:12:16 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id He1rpBKSiw0r for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:12:15 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D13AE1A8A71 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:12:14 -0700 (PDT)
X-AuditID: c618062d-f79a96d000007fb1-dd-553ea30b5c4b
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 1E.56.32689.B03AE355; Mon, 27 Apr 2015 22:58:51 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0210.002; Mon, 27 Apr 2015 23:12:12 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
Thread-Topic: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
Thread-Index: AQHQfjZfpTLcU5Ill0aU7Vdq4Mzggw==
Date: Tue, 28 Apr 2015 03:12:12 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628BC16D0@eusaamb107.ericsson.se>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOLMWRmVeSWpSXmKPExsUyuXSPny73YrtQg7WzNCw+dhxltXh59j2T xfrT7xgt+qfuZHJg8bh8xdtj56y77B4LNpV6LFnykymAJYrLJiU1J7MstUjfLoErY1NnD1vB LdmKezMXsTcw/hXvYuTkkBAwkXh/fRUrhC0mceHeerYuRi4OIYGjjBJrDmxngXCWM0q8nLuD CaSKDahjw87PYLaIQJDE7ld72UBsZoFgiRXf+8DiwgI+En1XNjND1PhKzHzxlxXC1pN49H06 WJxFQFVi5ee1jCA2L1DN+p172UFsIYEAiQ0nboPZjEAXfT+1hglivrjErSfzmSAuFZBYsuc8 M4QtKvHy8T+oD5QkPv6ezw5RryOxYPcnqNu0JZYtfM0MsUtQ4uTMJywTGEVnIRk7C0nLLCQt s5C0LGBkWcXIUVqcWpabbmSwiREYM8ck2HR3MO55aXmIUYCDUYmH90G8bagQa2JZcWXuIUZp DhYlcd5FDw6GCAmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamDs2/rJmUvuQpXP/INLzk3bZ6bd uVLSX33qiQB9G5EDguy3KlMnnC286n+qQVQhYt/9D8X/eIoa7AurlSKYHr7Rb3W/rjhjrvGc f4Hbt3hazrK2Wh27cMpl+a3/3vM0vp+dXrZK45TUBwGxOM3NL/fr5p1ZIdbzd1OQZObVV/Ly tbL94pO5n8kosRRnJBpqMRcVJwIAekUuMHoCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6s3GUWoCcfjw0uz3s7kMOhG5uxI>
Cc: Erik Nordmark <nordmark@acm.org>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 03:12:16 -0000

Hi Lorenzo,=0A=
   Thanks for your comments. Please find responses inline.=0A=
=0A=
On 04/23/2015 10:28 PM, Lorenzo Colitti wrote:=0A=
> Hi,=0A=
>=0A=
> in the context of looking at the RS refresh draft, I looked at the=0A=
> assertion in draft-garneij-6man-nd-m2m-issues-00 , which is cited as one=
=0A=
> of the use cases. IIUC the issue boils down to: in a network with a=0A=
> large number of completely silent devices, the periodic RA, which is=0A=
> sent on average every 1575 seconds, ends up being the dominating factor=
=0A=
> in paging channel usage.=0A=
>=0A=
> I think there is an easy way to fix this: raise the maximum RA lifetime=
=0A=
> and the maximum RA interval as proposed by draft-krishnan-6man-maxra-01.=
=0A=
=0A=
Sounds good.=0A=
=0A=
> That will lower the paging cost by a factor of 12x (21845 / 1800). If a=
=0A=
> that is not sufficient, then the cost can further be lowered by ensuring=
=0A=
> that the entity that deals with the mobile node's IP traffic (in 3GPP=0A=
> networks, the GGSN or the PGW) sends RAs opportunistically, bundling=0A=
> them with any other packets that it needs to send the device. If the=0A=
> device receives at least one packet in every 21845-second interval, then=
=0A=
> the extra paging cost goes down to zero. Even if the device never=0A=
> receives *any* packets (though that seems really unlikely: how does it=0A=
> know if it is reporting correctly, and that its controller is still=0A=
> receiving its traffic? The internet does not have zero loss), the RAs=0A=
> can still be sent opportunistically when the device *sends* a packet.=0A=
> The PGW will see the device send the packet and can opportunistically=0A=
> send the RA, knowing that the device will be in a high power state for a=
=0A=
> little while after sending the packet.=0A=
>=0A=
> Also, I think we should carefully consider the impact of the problem.=0A=
> This is very much a contrived worst-case scenario. If the network is a=0A=
> general purpose network, such as a commercial LTE network, the paging=0A=
> cost will in general be much higher, because that network also provides=
=0A=
> service to devices such as phones and tables that are orders of=0A=
> magnitude more chatty (due to users wanting to use the connection they=0A=
> paid for). So in general, commercial networks will not be optimized for=
=0A=
> this sort of usage. It's true that it's possible to optimize for M2M=0A=
> devices, and ensure that those devices use as few resources as possible,=
=0A=
> but in a general-purpose network, there's likely no point in doing that=
=0A=
> because the chattier devices are causing most of the cost anyway=0A=
> (Amdahl's law).=0A=
>=0A=
> Also note that the impact is on *paging channel* usage, not *power*=0A=
> usage. I'm not an expert, but AIUI in current radio technologies such as=
=0A=
> LTE, for a node that only sends a short burst of data every 12 hours,=0A=
> power is likely dominated by the cost of staying attached to the=0A=
> network, listening to the paging group, dealing with location area=0A=
> updates, etc. rather than sending the packets. If you care about power,=
=0A=
> the right strategy is to disconnect from the network completely, and=0A=
> only reconnect when you have something to transmit.=0A=
=0A=
You are only considering the effect on the UE and not on the network =0A=
itself. The network will be impacted either way. Frequent attaches and =0A=
detaches also increase the signaling load on the network. And the amount =
=0A=
of signaling needed to attach probably does not help with the power =0A=
efficiency of the UE either (This needs to be addressed anyway for M2M =0A=
and is not an IETF problem :-)).=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Mon Apr 27 20:17:04 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786E61ACE35 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 IHe51swhPF-K for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:17:02 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::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 5CC1C1ACE2F for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:17:02 -0700 (PDT)
Received: by iecrt8 with SMTP id rt8so9141502iec.0 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:17:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=193bAqklBOGgLLQgd4hJRuZcTnFcTHB+xWHFIzbP7dQ=; b=al61uQkNEDVJztv0MDUu7V1ZsYOb1j7hSpU9+RpqKuTx4eEEJIRq6Hk8+/+jH7oDeP wYwGd3Cg0DRnLsCngAqZJXq1JVKLtqxn35NBePn7TTeBCTYeEi1eqXu0+Nvu8z5yDUPn uW/39qcghBRsCn2PRfLFn1430BQ6T0HPrMX/VDwLHPdx4lga39HdLm5PKWzlLkNW6oXf 6seQciETVscIpUrKkE5IIRMkc9oiRH2vH5vrG9g/WD+8kZkXQ6KulHqUNhdP5RSom4W8 Tqi0C9sTrfWHWUQQN+M5/Kz1yoLKsk2urFrw7UDEbKuIUguOmhcI/C1Fava+5G4uVkbB O6pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=193bAqklBOGgLLQgd4hJRuZcTnFcTHB+xWHFIzbP7dQ=; b=V/nH9jMNln8zQEcZiIibIJ/BQCzpCEaBrDU0gj9RpHHDbclBYaDp6YBoUpBT8/vzdo k3D2C6GfbVjp2fKNPnwV/81gymKaBTxoeqzHg+2498kapYonEcNoIZW1EmK67koH9KoS apDc8eExrL9F1utNDqM4cqAvCp/Pg9A5bpbHRNaO9MP+6apvFv/Tbuh3SK60UeCxGIDE IUQBGu25dtsS9wSpsDXfZpCsbEUIItmvPr+f9diMFbLoazltypSX6xw/LTzYMeFzy7d7 hhQ9QdQVpENd9f+lWGgVV4teI/aPGfNp489MmM4+Irv3+45d6cR0qPZied8BevnAxmdA 4a0w==
X-Gm-Message-State: ALoCoQmUVFDlsKwGaa2tIMLDKqOg70+CqGcJE75Khm/2tvoZk3QgHrmI8honJePbqieo7fO26krV
X-Received: by 10.42.207.206 with SMTP id fz14mr15956792icb.34.1430191021848;  Mon, 27 Apr 2015 20:17:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Mon, 27 Apr 2015 20:16:41 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628BC16D0@eusaamb107.ericsson.se>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com> <E87B771635882B4BA20096B589152EF628BC16D0@eusaamb107.ericsson.se>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 28 Apr 2015 12:16:41 +0900
Message-ID: <CAKD1Yr1pCE7HUj=i5m709+Cc54yUdoS1K05+1-GBSpYqb8OZ+g@mail.gmail.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=20cf30426df6d1b3c00514c04b70
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Rhw1pyFoqSHDvogJex3Eup9xRhQ>
Cc: Erik Nordmark <nordmark@acm.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 03:17:03 -0000

--20cf30426df6d1b3c00514c04b70
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 28, 2015 at 12:12 PM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> > Also note that the impact is on *paging channel* usage, not *power*
> > usage. I'm not an expert, but AIUI in current radio technologies such as
> > LTE, for a node that only sends a short burst of data every 12 hours,
> > power is likely dominated by the cost of staying attached to the
> > network, listening to the paging group, dealing with location area
> > updates, etc. rather than sending the packets. If you care about power,
> > the right strategy is to disconnect from the network completely, and
> > only reconnect when you have something to transmit.
>
> You are only considering the effect on the UE and not on the network
> itself. The network will be impacted either way. Frequent attaches and
> detaches also increase the signaling load on the network. And the amount
> of signaling needed to attach probably does not help with the power
> efficiency of the UE either (This needs to be addressed anyway for M2M
> and is not an IETF problem :-)).
>

Right, it will be impacted either way. You're trading off location update
cost vs. attach cost vs. paging channel cost. However, I think it's
important to note that sending RAs opportunistically will remove most of
the extra cost.

--20cf30426df6d1b3c00514c04b70
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 T=
ue, Apr 28, 2015 at 12:12 PM, Suresh Krishnan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:suresh.krishnan@ericsson.com" target=3D"_blank">suresh.krishnan@=
ericsson.com</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><=
div class=3D"h5">&gt; Also note that the impact is on *paging channel* usag=
e, not *power*<br>
&gt; usage. I&#39;m not an expert, but AIUI in current radio technologies s=
uch as<br>
&gt; LTE, for a node that only sends a short burst of data every 12 hours,<=
br>
&gt; power is likely dominated by the cost of staying attached to the<br>
&gt; network, listening to the paging group, dealing with location area<br>
&gt; updates, etc. rather than sending the packets. If you care about power=
,<br>
&gt; the right strategy is to disconnect from the network completely, and<b=
r>
&gt; only reconnect when you have something to transmit.<br>
<br>
</div></div>You are only considering the effect on the UE and not on the ne=
twork<br>
itself. The network will be impacted either way. Frequent attaches and<br>
detaches also increase the signaling load on the network. And the amount<br=
>
of signaling needed to attach probably does not help with the power<br>
efficiency of the UE either (This needs to be addressed anyway for M2M<br>
and is not an IETF problem :-)).<br></blockquote><div><br></div><div>Right,=
 it will be impacted either way. You&#39;re trading off location update cos=
t vs. attach cost vs. paging channel cost. However, I think it&#39;s import=
ant to note that sending RAs opportunistically will remove most of the extr=
a cost.</div></div></div></div>

--20cf30426df6d1b3c00514c04b70--


From nobody Mon Apr 27 20:19:09 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DF01ACE2F for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:19:09 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBUsNDBbjk4e for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:19:08 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 071241ACE3C for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:19:07 -0700 (PDT)
X-AuditID: c6180641-f79086d000001909-88-553e98816039
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E0.98.06409.1889E355; Mon, 27 Apr 2015 22:13:53 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0210.002; Mon, 27 Apr 2015 23:19:06 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Erik Kline <ek@google.com>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
Thread-Topic: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
Thread-Index: AQHQfjZfpTLcU5Ill0aU7Vdq4Mzggw==
Date: Tue, 28 Apr 2015 03:19:06 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628BC1751@eusaamb107.ericsson.se>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com> <CAAedzxp+VjvOiSdw1Qv9Uhad2+vd+QxB2-iv6Vv_BLXne47zBw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyuXSPt27jDLtQgxO9Khafb89jt/jYcZTV 4uXZ90wW60+/Y7Ton7qTyYHV4/IVb4+ds+6yeyzYVOqxZMlPpgCWKC6blNSczLLUIn27BK6M hm+H2Qu2sFYc3zCFsYFxDUsXIyeHhICJxN9709ggbDGJC/fWA9lcHEICRxkl5q/oYYRwljNK /Dv9nRWkig2oY8POz0wgtoiAi0TXmq9g3cwC1RIzrvxjB7GFBXwk+q5sZoao8ZWY+eIvK4St J/Ho+3SwOIuAqsTMN/vA4rxANQd3HGaHWDadUWLf+QawoYxAJ30/tYYJYoG4xK0n85kgThWQ WLLnPDOELSrx8vE/VghbSeLj7/nsEPU6Egt2f4I6Tlti2cLXzBDLBCVOznzCMoFRdBaSsbOQ tMxC0jILScsCRpZVjBylxalluelGhpsYgfFzTILNcQfjgk+WhxgFOBiVeHgVKu1ChVgTy4or cw8xSnOwKInzll05GCIkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMUY8R/fFqst9i/RzZ8k5 LuDKzzvkzS8U6Tp55ZW790wiu7Q39v89/SGXs/7r5ncdLbfPu3TU1zC97MlSmpsn0RtToHFC UGEj16pH994eutEqOi1UdEE158YwW94QFzOm3cobDlr03Xn0wOPhbXaVlHdZX6zb+h9YT2SW /8cgvP3tkoJdlW8mK7EUZyQaajEXFScCAM4yQQ+AAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NxXTzkr-Tx0tU2DP7d9CRg5byhE>
Cc: Erik Nordmark <nordmark@acm.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 03:19:09 -0000

Hi Erik,=0A=
   Thanks for your comments. Please find responses inline.=0A=
=0A=
On 04/23/2015 10:48 PM, Erik Kline wrote:=0A=
> Agreed.=0A=
>=0A=
> Three additional points:=0A=
>=0A=
>      [1] draft-krishnan-6man-maxra-01, Section 3, paragraph 1: +1.=0A=
=0A=
Sounds good.=0A=
=0A=
>=0A=
>      [2] draft-krishnan-6man-maxra-01, Section 3, paragraph 2: I think=0A=
> it should be struck from that document and not be construed as=0A=
> recommended here.=0A=
=0A=
I would like to understand your reasons a bit. Is this because you think =
=0A=
multicast RAs are absolutely needed or because sending RAs only when =0A=
solicited is bad?=0A=
=0A=
Thanks=0A=
Suresh=0A=


From nobody Mon Apr 27 20:27:23 2015
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7367C1ACE37 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:27:22 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6BAIKpQlkVE for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:27:21 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D2151A1B30 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:27:21 -0700 (PDT)
X-AuditID: c618062d-f79a96d000007fb1-1e-553ea69572d9
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id F5.B6.32689.596AE355; Mon, 27 Apr 2015 23:13:58 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0210.002; Mon, 27 Apr 2015 23:27:19 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
Thread-Topic: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
Thread-Index: AQHQfjZfpTLcU5Ill0aU7Vdq4Mzggw==
Date: Tue, 28 Apr 2015 03:27:19 +0000
Message-ID: <E87B771635882B4BA20096B589152EF628BC17B1@eusaamb107.ericsson.se>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com> <E87B771635882B4BA20096B589152EF628BC16D0@eusaamb107.ericsson.se> <CAKD1Yr1pCE7HUj=i5m709+Cc54yUdoS1K05+1-GBSpYqb8OZ+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyuXRPgu60ZXahBrePMVl87DjKavHy7Hsm i/Wn3zFa9E/dyeTA4nH5irfHzll32T0WbCr1WLLkJ1MASxSXTUpqTmZZapG+XQJXxoI/wQVf +St+7FzB1sC4jKeLkZNDQsBE4uTxFcwQtpjEhXvr2UBsIYGjjBLX1hR0MXIB2csZJR73XQUr YgNq2LDzMxOILSKgIfFg3XEmkCJmgc2MErfWHmQESQgL+Ej0XdnMDFHkKzHzxV9WCFtP4tH3 6WBxFgFVidn7e8BsXqCansXLmSA232aUaHicDmIzAl30/dQasDizgLjErSfzmSAuFZBYsuc8 1NWiEi8f/2OFsJUkPv6ezw5RryOxYPcnNghbW2LZwtdQuwQlTs58wjKBUXQWkrGzkLTMQtIy C0nLAkaWVYwcpcWpZbnpRgabGIERc0yCTXcH456XlocYBTgYlXh4H8TbhgqxJpYVV+YeYpTm YFES51304GCIkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsYQuf1LNZQuxyiducLvoXUjjCNC jye4/F9k2kyGT6UX5FYpPL604uexZ2EuSR4nG6MfXtzyfdHkpWeiQp9H7NG+sOpdnt8+yS+T 19x4mK6y/vfWR6sXq3HNKtCe9zNygfGCX1tc7FlfX7r4tIOPr675YPHbgIfVfJVWK/fu8mXO mLUswWNmHNdjJZbijERDLeai4kQAjjVSa3kCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jzlHOA4XF2PjFa8b-aPv-NIuycQ>
Cc: Erik Nordmark <nordmark@acm.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 03:27:22 -0000

Hi Lorenzo,=0A=
=0A=
On 04/27/2015 11:17 PM, Lorenzo Colitti wrote:=0A=
> On Tue, Apr 28, 2015 at 12:12 PM, Suresh Krishnan=0A=
> <suresh.krishnan@ericsson.com <mailto:suresh.krishnan@ericsson.com>> wrot=
e:=0A=
>=0A=
>      > Also note that the impact is on *paging channel* usage, not *power=
*=0A=
>      > usage. I'm not an expert, but AIUI in current radio technologies=
=0A=
>     such as=0A=
>      > LTE, for a node that only sends a short burst of data every 12 hou=
rs,=0A=
>      > power is likely dominated by the cost of staying attached to the=
=0A=
>      > network, listening to the paging group, dealing with location area=
=0A=
>      > updates, etc. rather than sending the packets. If you care about=
=0A=
>     power,=0A=
>      > the right strategy is to disconnect from the network completely, a=
nd=0A=
>      > only reconnect when you have something to transmit.=0A=
>=0A=
>     You are only considering the effect on the UE and not on the network=
=0A=
>     itself. The network will be impacted either way. Frequent attaches an=
d=0A=
>     detaches also increase the signaling load on the network. And the amo=
unt=0A=
>     of signaling needed to attach probably does not help with the power=
=0A=
>     efficiency of the UE either (This needs to be addressed anyway for M2=
M=0A=
>     and is not an IETF problem :-)).=0A=
>=0A=
>=0A=
> Right, it will be impacted either way. You're trading off location=0A=
> update cost vs. attach cost vs. paging channel cost. However, I think=0A=
> it's important to note that sending RAs opportunistically will remove=0A=
> most of the extra cost.=0A=
=0A=
Yep. I will try to run some numbers for the attach-when-needed scenario =0A=
as well to see what the tradeoffs are. I need to do a bit of literature =0A=
review to figure out if the network nodes sending the RAs are aware of =0A=
the duty cycles of the M2M devices (maybe Fredrik or Samita can chime in =
=0A=
right away).=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Mon Apr 27 20:30:24 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C801ACE56 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 MQRs_TEIpdNU for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:30:10 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001: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 2FE041ACE53 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:30:10 -0700 (PDT)
Received: by iget9 with SMTP id t9so80887971ige.1 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:30:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9ZVdppL3Tq69yExShjBiPUJ6udpzm4Iqco/a25ATaVU=; b=PqmfFJ7M8zdbmHZOlo5jkieUrHirbMBCEZjrRwqDqiboLYInh17tOai3JLa8Y6KaX4 z+5N7N9pEVbn/uGc8BFUJQDWojs29+gCJJX4+wtALhw2qjhXqxYxKCc3ZeZj4znsn/aP 4aAzP1AwzQjrT2WvedyvnIqheMQ39upQm/YVMPVEpYQ3subcj4/BTFQfxywSWks11Rbv R+RWyY0XXZDk7Ahf7WzaTo48kK+DiaB19kQoBAb9QsVd1rho4ha050zVDOtpzigA9aKY 0o0B2AmxOyh7zkHEdpv7L8rVrHOn9HceObatmMFGgd7+02+zxLtVa/rUyEAEo5IihWaf P/GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9ZVdppL3Tq69yExShjBiPUJ6udpzm4Iqco/a25ATaVU=; b=NW3fF7gtt9nk8AGbzBcGIksaDpeIlgSNnnCxdU9AL/fcjtKN2bbjhKxRO96sGpNHeD M7fFz/KXzSfYzuGtE+02yewe042BuaxUEAUJNTjs4J3n5A40URa75cmsZSWbRyERdwz/ oycX2e3XnIT6iHXD9SSPSkAhwvNV+YBGKbXgjeG9XZ9TRwkPPWD0GxKqZgU/tMoK66xt GoSOGK4eO1+rpOlNJud4drpIsYpj1sMTajqlOlW4FvMpQQjlT2j2aQYytXoupVdc19Ty B9EAJ7hUmZMpfBkQnLNOUbsCV73yNkUmHrxys+dTLyLpOeSExK3Jtogx5uK+BHdUc1DX 6stQ==
X-Gm-Message-State: ALoCoQkFAiO7qWrJlj4kDPFsLq71AYdGQ2GGTZbroMDEklTTWBSmA2INOaKX9SfzFmrvNGUwjqMb
X-Received: by 10.107.33.21 with SMTP id h21mr18353079ioh.1.1430191809409; Mon, 27 Apr 2015 20:30:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Mon, 27 Apr 2015 20:29:48 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628BC17B1@eusaamb107.ericsson.se>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com> <E87B771635882B4BA20096B589152EF628BC16D0@eusaamb107.ericsson.se> <CAKD1Yr1pCE7HUj=i5m709+Cc54yUdoS1K05+1-GBSpYqb8OZ+g@mail.gmail.com> <E87B771635882B4BA20096B589152EF628BC17B1@eusaamb107.ericsson.se>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 28 Apr 2015 12:29:48 +0900
Message-ID: <CAKD1Yr1DtjRFYEib8DUk7wpR_2p=Fhk0d1_Gi1w308HGui4osA@mail.gmail.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=001a1140408cc2f24d0514c07a57
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/38IBMqySNrVksZ2HIBYdCcqx3n4>
Cc: Erik Nordmark <nordmark@acm.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, Fredrik Garneij <fredrik.garneij@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 03:30:11 -0000

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

On Tue, Apr 28, 2015 at 12:27 PM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> > Right, it will be impacted either way. You're trading off location
> > update cost vs. attach cost vs. paging channel cost. However, I think
> > it's important to note that sending RAs opportunistically will remove
> > most of the extra cost.
>
> Yep. I will try to run some numbers for the attach-when-needed scenario
> as well to see what the tradeoffs are. I need to do a bit of literature
> review to figure out if the network nodes sending the RAs are aware of
> the duty cycles of the M2M devices (maybe Fredrik or Samita can chime in
> right away).
>

They don't need to be though, right? As the first-hop router of every node
in the network, they know when those nodes emit packets, and when they
receive packets. They can then ensure that they send packets in time for
those nodes to receive them before they go back to sleep.

--001a1140408cc2f24d0514c07a57
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 T=
ue, Apr 28, 2015 at 12:27 PM, Suresh Krishnan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:suresh.krishnan@ericsson.com" target=3D"_blank">suresh.krishnan@=
ericsson.com</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><=
div class=3D"h5">&gt; Right, it will be impacted either way. You&#39;re tra=
ding off location<br>
&gt; update cost vs. attach cost vs. paging channel cost. However, I think<=
br>
&gt; it&#39;s important to note that sending RAs opportunistically will rem=
ove<br>
&gt; most of the extra cost.<br>
<br>
</div></div>Yep. I will try to run some numbers for the attach-when-needed =
scenario<br>
as well to see what the tradeoffs are. I need to do a bit of literature<br>
review to figure out if the network nodes sending the RAs are aware of<br>
the duty cycles of the M2M devices (maybe Fredrik or Samita can chime in<br=
>
right away).<br></blockquote><div><br></div><div>They don&#39;t need to be =
though, right? As the first-hop router of every node in the network, they k=
now when those nodes emit packets, and when they receive packets. They can =
then ensure that they send packets in time for those nodes to receive them =
before they go back to sleep.</div></div></div></div>

--001a1140408cc2f24d0514c07a57--


From nobody Mon Apr 27 22:18:59 2015
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5E81A002F for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 22:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2g7rPVWL40Ui for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 22:18:54 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54FDF1A000F for <ipv6@ietf.org>; Mon, 27 Apr 2015 22:18:54 -0700 (PDT)
Received: from [2a02:c0:2:4:6666:17:0:1001] (port=50075 helo=echo.ms.redpill-linpro.com) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <tore@fud.no>) id 1Ymxuu-0003DS-Vd; Tue, 28 Apr 2015 07:18:44 +0200
Date: Tue, 28 Apr 2015 07:18:03 +0200
From: Tore Anderson <tore@fud.no>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Message-ID: <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com>
In-Reply-To: <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zkBz8aJEcNox-TWDxQ89S9PUaQg>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, jool@nic.mx, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 05:18:58 -0000

Hi Fred,

* "Fred Baker (fred)" <fred@cisco.com>

> > On Apr 27, 2015, at 6:01 PM, Fernando Gont <fgont@si6networks.com> wrot=
e:
> >=20
> > We've rev'ed the aforementioned I-D with minor clarifications requested
> > by implementers:
> > <https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-generat=
ion-01>
> >=20
> > We think the current version of the I-D is ready for WGLC.
>=20
> The ID contains three essential parts: why the recommendations, a
> relatively minor change to RFC 2460, and some deep surgery on RFC
> 6145. Let me as a question on that last, if you would.
>=20
> Have those proposed changes been vetted with the implementors you
> mentioned?

I believe so. Quoting from <http://jool.mx/usr-flags-atomic.html>:

=C2=ABLet it be known that we fully condone the deprecation of atomic
fragments=C2=BB

I'm adding the implementors in question to the CC list, so they may
elaborate on their position if they so desire.

Tore


From nobody Mon Apr 27 22:57:50 2015
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A6B71A00FD for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 22:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCEHv2uSx-Mg for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 22:57:47 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 545221A0086 for <ipv6@ietf.org>; Mon, 27 Apr 2015 22:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1249; q=dns/txt; s=iport; t=1430200667; x=1431410267; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DPidkhI0ZazQY52bidMegD/EF9sHzjZ+iP5W6cIXBc0=; b=gm7llF6KmyOpABXmD2nHQrjf4C9dt783TLS9Dc4/dZJigv6t34VSdF1w ncq6pWCHv+YJC0M/G5QUKAvhofjl/yjLbjJwBEWBHRuGWqcwvK+uLReXo YKHziXOt7+w+kepelnkk78maoqVSNEZ1gVLoP1Wzex/4igEkhd/le6WGA 4=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BABQCHID9V/4sNJK1cgwyBNIMVyzkCgTZMAQEBAQEBgQuEIQEBBCNWEAIBCDsHAgIyJQIEDhOIHbJMlAgBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiziFBQeCaC+BFgWRVYFygTeHEIEikG+DUCOCOIE8gjOBAAEBAQ
X-IronPort-AV: E=Sophos;i="5.11,662,1422921600";  d="asc'?scan'208";a="412184935"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-9.cisco.com with ESMTP; 28 Apr 2015 05:57:46 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t3S5vkU0009389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Apr 2015 05:57:46 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.172]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Tue, 28 Apr 2015 00:57:46 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Tore Anderson <tore@fud.no>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Topic: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Index: AQHQgU7liPOJOD1i1UeQA2xTungMaZ1iAo4AgAA0DICAAAsXAA==
Date: Tue, 28 Apr 2015 05:57:46 +0000
Message-ID: <CBB02F0C-939D-4812-9D53-EB381637BBDC@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com>
In-Reply-To: <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_EF469304-A332-4A9F-8A5C-B93AD2E074A4"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/T9xuWdMpQgClZb0qFxCnCgCDtgs>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, "jool@nic.mx" <jool@nic.mx>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 05:57:48 -0000

--Apple-Mail=_EF469304-A332-4A9F-8A5C-B93AD2E074A4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

BTW, if we rev 6145 for this, we should include your favorite rev, and =
there is an erratum to sort out. I=E2=80=99d like to do it all in one =
swell foop in one working group. I=E2=80=99ll take advice on where; the =
obvious place (behave) doesn=E2=80=99t exist any more.

--Apple-Mail=_EF469304-A332-4A9F-8A5C-B93AD2E074A4
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 - http://gpgtools.org

iQEVAwUBVT8hWJ9ieig10VPpAQKcawf9HnrKuUrvGFI3DdLsGqlQPSyOg5H6Up7H
9w9S4TuuDdGqz4tkyMzHrAqykAuwTL0KOFPmFus0PUrjbOg7kBTnOqrSvaoRxUjr
AgkmjfBTBhG1y5m/zxUZMbTCS917Wt64jsu+owp24FKl3sLe52BWJuN/aKZ9aPUV
f71ny9Ow3Z+nnEnUY17t96AKVytL3Sm1av4h7C7lYK/fh2QBmHP4Ioyp1zIsRHkO
yGWjMaVXU4xHMGJmEpnZPZYpHOQ7PiAKK1YgSKjk0zpp8+11ShDrEpWhjmIqVexu
shemTPG2nkbvb8/yFWmVGE3D14I5skeisTxzDQrKljeXyOwOE/3d+w==
=pQ6A
-----END PGP SIGNATURE-----

--Apple-Mail=_EF469304-A332-4A9F-8A5C-B93AD2E074A4--


From nobody Mon Apr 27 23:42:52 2015
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169951A0371 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 23:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kpSbo2ezYtV5 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 23:42:49 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FB031A0354 for <ipv6@ietf.org>; Mon, 27 Apr 2015 23:42:49 -0700 (PDT)
Received: from [2a02:c0:2:4:6666:17:0:1001] (port=50626 helo=echo.ms.redpill-linpro.com) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <tore@fud.no>) id 1YmzE3-0005rK-LD; Tue, 28 Apr 2015 08:42:35 +0200
Date: Tue, 28 Apr 2015 08:41:54 +0200
From: Tore Anderson <tore@fud.no>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Message-ID: <20150428084154.74320042@echo.ms.redpill-linpro.com>
In-Reply-To: <CBB02F0C-939D-4812-9D53-EB381637BBDC@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com> <CBB02F0C-939D-4812-9D53-EB381637BBDC@cisco.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fhXYhq24xIXmKPjJB254RSw3gLo>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>, "jool@nic.mx" <jool@nic.mx>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 06:42:50 -0000

* "Fred Baker (fred)" <fred@cisco.com>

> BTW, if we rev 6145 for this, we should include your favorite rev,
> and there is an erratum to sort out. I=E2=80=99d like to do it all in one
> swell foop in one working group. I=E2=80=99ll take advice on where; the
> obvious place (behave) doesn=E2=80=99t exist any more.

I'll gladly roll draft-anderson-v6ops-siit-eam into a 6145bis.

Being somewhat of an IETF newbie, I don't have any strong opinions on
the venue and will follow where you lead... That said, I was faced with
the same question when determining where to submit the siit-eam stuff,
and here is my thoughts on the matter:

- When I spoke to Ole about the SIIT-DC/EAM stuff a while back I was
  told that 6man was not appropriate.

- A 6145bis is bordering on being out of scope for v6ops' charter. I
  guess it depends on whether or not you understand =C2=ABspecifying any
  protocols or transition mechanisms=C2=BB to also mean =C2=ABupdating alre=
ady
  specified protocols or transition mechanisms=C2=BB. That said, there is
  precedent for doing 6145 updates in v6ops though; cf. RFC 6791 (and
  also the soon-to-be-uploaded draft-ietf-v6ops-siit-eam). Furthermore,
  when considering that the updates is largely caused by operational
  experience, v6ops does sound like an OK fit.

- Sunset4 may be appropriate, as facilitating the disablement of IPv4
  in (parts of) the network is perhaps the most important use case for
  SIIT. However there's no fitting work item listed in the sunset4
  charter as far as I can see.

If there are other potential candidates, I'm not familiar with them.

Tore


From nobody Mon Apr 27 23:44:54 2015
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9693C1ACE59 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 1XRmvYrWY749 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 20:53:07 -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 A5CF31ACE56 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:53:07 -0700 (PDT)
Received: by qkhg7 with SMTP id g7so73703540qkh.2 for <ipv6@ietf.org>; Mon, 27 Apr 2015 20:53:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=udcZeerRYJ1L0iqUBrnKsTGkn6FI63GugVaStC66Zcg=; b=A9drBEZ59gO76+dn2tptCXh4JLsF8WYAsqXMOwqd+X9Zb4+JNMJ8w5FVRz8z8v6fIF 0cKOMcasGcFesXOhQxLdnVpR9LwXGYbIHoriVMKzYl40tWi1IaBQp7eYdwShmJqHhyEe 2Tjqwd4RnITaaGgtMOe111msrOKNhDaD18y+kgevsLhfjfRBEiQ1vBPWyfIkKGkVWRDh IqMZ6kFvcH0yk9RpRBAFKaJf+Yxr7uYcug8mt8ip7DZX5Qmee2EvsE5bWOGKZ/Oq4jrX 7bQCPkAak6RDXPJo/MsLwmrKBcuWLIX65nDtOmXQWByEWXfM5AOB/T4/JegRnd2KUNd+ xTOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=udcZeerRYJ1L0iqUBrnKsTGkn6FI63GugVaStC66Zcg=; b=bq54Cr9j4Kr/2pZYP+PPfCb+1kgOImr7RrvlI3rOLjuB10BGYc44/9Cf/cdXLtfEG6 tnW7p+mgnZWRxWigeL3+jG+NdmoXsGG2y/cJbEQJ7sjdS/gMlmY95XmnHijUNkHCYFud uKSnoqfDjVw/jVS1PjBSr5VoAKCeROupvad2R0vEGsXMUUw3zXrkPk4vBaCw1xS03X0r 8ndmZpxX/w65i7Su8KJMT+TyZxMTEtng/94qnATShcAfAP2Zg2vI3cYFdke730W6H0n8 e5/yMNzMvczvE3+2l+iAOTENKle9d3JzGNF4S3xkM25r3vNrS504bcDDG0bo8+0S16ZL kc7g==
X-Gm-Message-State: ALoCoQnfxiDPvfEmMCgTDYyS54AkvPkEo+gNKOQctdEA9LnMhVTqbexYJgQoMUNIbE9CPYK5KkFm
X-Received: by 10.140.30.166 with SMTP id d35mr9796068qgd.85.1430193186963; Mon, 27 Apr 2015 20:53:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.208.6 with HTTP; Mon, 27 Apr 2015 20:52:46 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF628BC1751@eusaamb107.ericsson.se>
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com> <CAAedzxp+VjvOiSdw1Qv9Uhad2+vd+QxB2-iv6Vv_BLXne47zBw@mail.gmail.com> <E87B771635882B4BA20096B589152EF628BC1751@eusaamb107.ericsson.se>
From: Erik Kline <ek@google.com>
Date: Tue, 28 Apr 2015 12:52:46 +0900
Message-ID: <CAAedzxrbeWM641BznYh_RSqHuxAugHiDySXzD70KZFo1Hf5d9w@mail.gmail.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/R2aPlHGLxz47BFVDqizEQv03pNI>
X-Mailman-Approved-At: Mon, 27 Apr 2015 23:44:54 -0700
Cc: Erik Nordmark <nordmark@acm.org>, Fredrik Garneij <fredrik.garneij@gmail.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 03:53:08 -0000

>>      [2] draft-krishnan-6man-maxra-01, Section 3, paragraph 2: I think
>> it should be struck from that document and not be construed as
>> recommended here.
>
> I would like to understand your reasons a bit. Is this because you think
> multicast RAs are absolutely needed or because sending RAs only when
> solicited is bad?

Sending unicast RAs whenever solicited: +1.

Sending opportunistic unicast RAs whenever the router has other
packets to deliver anyway: +1.  (Yes, this is not currently documented
anywhere.)

Overall I'm concerned about the propensity for everything to be
increasingly static.  Soon we'll hear: a billion clients polling via
unicast RS is putting too much load on the infrastructure to generate
the correct RAs.  And then we'll copy'n'paste DHCPv6 Squelch into RS
Squelch--either that or infinite RAs.

I don't want us to lose the *operational* ability to reconfigure,
despite the fact the protocol will continue to nominally support it.


From nobody Mon Apr 27 23:46:17 2015
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEBA1A0372 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 23:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llOkSFC55dk1 for <ipv6@ietfa.amsl.com>; Mon, 27 Apr 2015 23:46:14 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A29CE1A0371 for <ipv6@ietf.org>; Mon, 27 Apr 2015 23:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1357; q=dns/txt; s=iport; t=1430203575; x=1431413175; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=l9AGev0zQSImy0Y/HTNShyqbRnS2z+4GUKySpN3S28c=; b=Lp3SxyYWpakohdgx2mK1G+sk5QVNqV34OhIu2Q1N6CFWOzYw4aQ0xJ02 MtHEUlhtBtPuUB6Lm/ydSiKnk/eYYhcWpvFUpREMK5ihjFVFurgg+zSe7 kxi0FnFTL7Y/vEfuTrFvSFaTpnLpzarE7mjcJrAupwAfI94THzu1cKSsi U=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B8BABSLD9V/4QNJK1cgwyBLwXGewmHVgKBLzgUAQEBAQEBAYEKhCABAQEDAXkFCwIBCBgjCzIlAgQOBQ6IFQjGTwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLOIUFB4MXgRYBBJFVgXKBN4cQlWEjgWVTgTxvgUSBAAEBAQ
X-IronPort-AV: E=Sophos;i="5.11,662,1422921600";  d="asc'?scan'208";a="145153293"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-4.cisco.com with ESMTP; 28 Apr 2015 06:46:14 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t3S6kD2C016812 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Apr 2015 06:46:13 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.172]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Tue, 28 Apr 2015 01:46:13 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Tore Anderson <tore@fud.no>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Topic: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Index: AQHQgU7liPOJOD1i1UeQA2xTungMaZ1iAo4AgAA0DICAAAsXAIAADFcAgAABMoA=
Date: Tue, 28 Apr 2015 06:46:13 +0000
Message-ID: <41275F44-F36C-438A-A957-8FB2B216CE81@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com> <CBB02F0C-939D-4812-9D53-EB381637BBDC@cisco.com> <20150428084154.74320042@echo.ms.redpill-linpro.com>
In-Reply-To: <20150428084154.74320042@echo.ms.redpill-linpro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_B626E173-30D2-4DDF-A145-841962DFFEC1"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5FtNOoHAWHu3FIZanXBNPHRD_cc>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>, "jool@nic.mx" <jool@nic.mx>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 06:46:16 -0000

--Apple-Mail=_B626E173-30D2-4DDF-A145-841962DFFEC1
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On Apr 27, 2015, at 11:41 PM, Tore Anderson <tore@fud.no> wrote:
> 
> - Sunset4 may be appropriate, as facilitating the disablement of IPv4
>  in (parts of) the network is perhaps the most important use case for
>  SIIT. However there's no fitting work item listed in the sunset4
>  charter as far as I can see.

We can talk with Marc and Wes about that. Yes, it may be appropriate.

--Apple-Mail=_B626E173-30D2-4DDF-A145-841962DFFEC1
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 - http://gpgtools.org

iQEVAwUBVT8ss59ieig10VPpAQLJEwf/ZaLG482H3tFlAG0OW1VFLZMAbjMFLp8n
vBJBoPgQ+eovVkfgIgtG2Tt3flvpZ/aSQQMApIqXwpYy0NwNO8tudixfk9B5vd1r
HPtJ4kphQVlrGzJPHxW4IhFvGHm+wGqPTKfKfAPnGVt+VNMNci3WXxYdvfhV1Hcm
A7KS96xs+SpX5sEagt3FPcxefht2a4Uexr9QfpkvA/+GQYpN4sAS2cGYvtBzV9ly
iD4dJYtjXvD2xljkcwvQzBRelDrgl+mwYjcmhqHotKaE7ygnT04pW0JtXTreFmXp
nU5z2ctN6kjui4fzYl5wh2XA9rU/154Vxhl2A4Z1xN0Z4ASnab4vlQ==
=klk1
-----END PGP SIGNATURE-----

--Apple-Mail=_B626E173-30D2-4DDF-A145-841962DFFEC1--


From nobody Tue Apr 28 08:23:35 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADFD51A87A8 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 08:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.335
X-Spam-Level: 
X-Spam-Status: No, score=-1.335 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 qCUKpNauCrUI for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 08:23:32 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 998971A8794 for <ipv6@ietf.org>; Tue, 28 Apr 2015 08:23:30 -0700 (PDT)
Received: from [10.0.0.162] (74-61-144-53.sfo.clearwire-wmx.net [74.61.144.53] (may be forged)) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3SFNMwu013319 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Apr 2015 08:23:24 -0700
Message-ID: <553FA5EB.1050208@acm.org>
Date: Tue, 28 Apr 2015 08:23:23 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Erik Kline <ek@google.com>, Erik Nordmark <nordmark@acm.org>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <CAKD1Yr3o7pTOeGsRy7wcWpmEcLRcf+Yvis587Msj9qb0PGEeVg@mail.gmail.com> <5531440E.5060102@sonic.net> <CAKD1Yr3bdARtNdigrAfT3ku5cpihP_Tn6ox4VKLvULU8sSrG8A@mail.gmail.com> <55353A60.1030701@acm.org> <CAKD1Yr19w1Uy=3VSpNua3qJ-bb1yz_zCW4L8k0FV9YJAgvOtXw@mail.gmail.com> <55368297.6080006@acm.org> <CAKD1Yr1oy4TkKvFfF05V6KsyE2xsEACNqtuhLqnbgunW2hbcdA@mail.gmail.com> <55397677.2040107@acm.org> <CAAedzxrdwzPgvQYmxNJ9EMNc1QjM7eOx90oBprydvAMiHh3iJA@mail.gmail.com>
In-Reply-To: <CAAedzxrdwzPgvQYmxNJ9EMNc1QjM7eOx90oBprydvAMiHh3iJA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVaE9WYG0g5qB5xkR9cFgsVUOVCAaS/KRejn0TggDc4olD2RXNVKt+nAIDtWL+MZ5gBKugErWeJ0uQs3yehC3SJg
X-Sonic-ID: C;AqEPgrrt5BGPGoY+Bvepxg== M;+GmRgrrt5BGPGoY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lgM9iax4HHZTB5GKFBmZlU_BMjw>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 15:23:33 -0000

On 4/27/15 8:27 AM, Erik Kline wrote:
> A question comes to mind: what might the operational guidance be for
> setting the refresh timer value in the RA?
>
> Observation: it almost certainly shouldn't be /longer/ than the router
> lifetime, even if the prefix lifetimes are infinite.
>
> Reasonable stab in the dark: refresh timer value in the RA should be
> in the neighborhood of some fraction (1/2, 2/3) * min(router lifetime,
> prefix lifetimes...).
>
> If that turns out to be the case, then the host can compute this timer
> value for itself, sleep on its own schedule, and wake up whenever it
> wants and send a unicast RS.  At that point this isn't a protocol
> change but rather an operational document.  [1]
>
> At the very least, this is a simple enough experiment to perform for
> people writing the code on the affected devices (doesn't require
> router vendor code changes).  Has anybody done this and measured the
> outcome?
Erik,
the above wouldn't work because a RFC 4861 compliant router can delay 
sending the solicited RA (and multicast it) hence the host would have to 
wait for seconds with (at least) the radio powered on when it otherwise 
would have gone back to sleep after a few milliseconds.

That RA delay is why rs-refresh says that routers which implement the 
specification should unicast the solicited RAs immediately. Furthermore, 
the RTO option indicates to the hosts that the routers are in fact 
implementing rs-refresh which includes the immediate RA response.

That should all be covered in the document; I don't know if you've read 
it and understood it. I'd welcome suggestions for how to make this more 
clear if it turns out that it is not.

As an aside, you seem to think that a protocol specification is merely 
about packet formats. However, protocol specifications include 
behaviors, protocol constants, default values, statements about what is 
mandatory to implement etc.
The behaviors might be things that are conditionally mandatory or 
recommended i.e., of the form "if you implement option foo, then you 
SHOULD use binary exponential backoff for the retransmit timer."

Do you have any technical issues for the WG not pursuing this work?
Any non-technical reasons why not?
Please provide sufficient detail so that the WG can properly evaluate 
your concerns.

Thanks,
    Erik


>
> -Erik the Lesser
>
>
> [1]  Note that the node MUST to be ready to basically re-attach from
> scratch in the event that the router has gone (I swapped my IoT device
> access point for a new model, and it got a new prefix too, while
> everyone listening was asleep, for example).  So guessing a wrong
> timer value must be non-fatal for the node.  At worst it won't be
> "optimal" but i'm curious to know what the impact of deviation from
> "optimal" would really be in these networks, given that nodes are all
> going to go for the longest possible timer value.
>


From nobody Tue Apr 28 08:35:36 2015
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7571A87A1 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 08:35:34 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTtNIXXVw6bx for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 08:35:33 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.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 8A1D31A8792 for <ipv6@ietf.org>; Tue, 28 Apr 2015 08:35:33 -0700 (PDT)
Received: from [10.0.0.162] (74-61-144-53.sfo.clearwire-wmx.net [74.61.144.53] (may be forged)) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t3SFZMJQ027264 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Apr 2015 08:35:24 -0700
Message-ID: <553FA8B9.2040906@acm.org>
Date: Tue, 28 Apr 2015 08:35:21 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Erik Kline <ek@google.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Comments on the analysis in draft-garneij-6man-nd-m2m-issues-00
References: <CAKD1Yr1eKYgpniW+BoFsfZ08igj5ct4gf3ntLH_arWzu-z9hmg@mail.gmail.com> <CAAedzxp+VjvOiSdw1Qv9Uhad2+vd+QxB2-iv6Vv_BLXne47zBw@mail.gmail.com> <E87B771635882B4BA20096B589152EF628BC1751@eusaamb107.ericsson.se> <CAAedzxrbeWM641BznYh_RSqHuxAugHiDySXzD70KZFo1Hf5d9w@mail.gmail.com>
In-Reply-To: <CAAedzxrbeWM641BznYh_RSqHuxAugHiDySXzD70KZFo1Hf5d9w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbVIh/WWK1UuOqAeIo4AiVoNMPECON9CzSnbyymU4IXLqJ/w8Ks8xgrVpzYY2TgmDMgeAn0v+IhWC/2ed4Gm34i
X-Sonic-ID: C;ilo4L7zt5BGDjYY+Bvepxg== M;nP0dMLzt5BGDjYY+Bvepxg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/N6LaKzkSU_txpSwxb5f_H28U2t8>
Cc: Erik Nordmark <nordmark@acm.org>, Fredrik Garneij <fredrik.garneij@gmail.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 15:35:34 -0000

On 4/27/15 8:52 PM, Erik Kline wrote:

>> I would like to understand your reasons a bit. Is this because you think
>> multicast RAs are absolutely needed or because sending RAs only when
>> solicited is bad?
> Sending unicast RAs whenever solicited: +1.
>
> Sending opportunistic unicast RAs whenever the router has other
> packets to deliver anyway: +1.  (Yes, this is not currently documented
> anywhere.)
>
> Overall I'm concerned about the propensity for everything to be
> increasingly static.
Erik,

I don't understand how sending a RS to get an RA results in more static 
configuration than what RFC 4861 has.
RFC 4861 allows for prefix lifetimes to be infinite (which FWIW I think 
was a mistake). Whether the information is pushed or pulled has no 
impact on NUD being able to switch from an unreachable router to a 
reachable one.

You've pointed out that in rs-refresh we shouldn't allow an infinite 
refresh time, and I think that would be an improvement over RFC 4861. 
But even without that fix I don't see how rs-refresh would be more 
static than 4861.

What am I missing?

>    Soon we'll hear: a billion clients polling via
> unicast RS is putting too much load on the infrastructure to generate
> the correct RAs.  And then we'll copy'n'paste DHCPv6 Squelch into RS
> Squelch--either that or infinite RAs.
>
> I don't want us to lose the *operational* ability to reconfigure,
> despite the fact the protocol will continue to nominally support it.
>
Can you give an example where rs-refresh would not be able to 
reconfigure the hosts?
Are you assuming that implementations for some reason are more likely to 
have bugs relating to rs-refresh then they do for 4861? Or some other 
unstated assumptions?

Thanks,
    Erik



From nobody Tue Apr 28 09:00:18 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E65FF1AD074 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 09:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 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, SPF_PASS=-0.001] autolearn=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 y6qrUiQ4VojP for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 09:00:16 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::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 AC0A81AD09B for <6man@ietf.org>; Tue, 28 Apr 2015 08:59:48 -0700 (PDT)
Received: by lbbuc2 with SMTP id uc2so110848806lbb.2 for <6man@ietf.org>; Tue, 28 Apr 2015 08:59:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; bh=GxWrXBuoEJaWK+SWRQn/jfsDUPWUSW/5Hx5Pl8zyg34=; b=g84CWm9OFj2En9XoPlFm1jC8bK7JSZIm2WNLLllY+KGuKoorM5DodmA5XnA5KNf+bd CGgZ349zCyU0byVPYdqbp/i7l9nf8TFwVDWSuU4ayk4r3ZNrFhJRuUTkyFCPe2gNN8mB irWiKkJfLfyWNnSXo6outL01PLV1mHANcDqUmWG5vhlbdJzkFHpHN4DPl6pTmHVK0Bso A4p52VsU7nUUcIB9DdEnDCkE4ELNxt1N3gOXK5TvvVb2ToaS7PBl9drqaL0eEjg6wN7x oBBBcfZQ9dZX9KaDCaX05nWpaEk3uyhaSa7HtjXz4AiaPbQLOGtfTYbQ5R2rHZEAUCGh G1Qg==
MIME-Version: 1.0
X-Received: by 10.112.189.102 with SMTP id gh6mr14946123lbc.115.1430236787198;  Tue, 28 Apr 2015 08:59:47 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Tue, 28 Apr 2015 08:59:47 -0700 (PDT)
Date: Tue, 28 Apr 2015 10:59:47 -0500
Message-ID: <CAC8QAcekusSKK6oeZwGyuNtcs2jGkGqVkPsgnqguYQYPAOFV1Q@mail.gmail.com>
Subject: New Version Notification for draft-sarikaya-6man-ra-guidelines-00.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tqoDggAhC5Bx6l_aCQe7eclz-RU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 16:00:17 -0000

 Hi all,

Dan and I submitted Rev. 00 of RA Guidelines draft, as below.
Please read and comment.

Regards,

Behcet

A new version of I-D, draft-sarikaya-6man-ra-guidelines-00.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-sarikaya-6man-ra-guidelines
Revision:       00
Title:          Guidelines for New Router Advertisement Options
Document date:  2015-04-28
Group:          Individual Submission
Pages:          10
URL:
https://www.ietf.org/internet-drafts/draft-sarikaya-6man-ra-guidelines-00.txt
Status:
https://datatracker.ietf.org/doc/draft-sarikaya-6man-ra-guidelines/
Htmlized:       https://tools.ietf.org/html/draft-sarikaya-6man-ra-guidelines-00


Abstract:
   This document defines simple rules to follow when defining new router
   advertisement options.


From nobody Tue Apr 28 10:07:57 2015
Return-Path: <ydahhrk@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1411A8A13 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 10:07:55 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e34ZwI9BpZqI for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 10:07:53 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::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 6F8031A89B4 for <ipv6@ietf.org>; Tue, 28 Apr 2015 10:07:53 -0700 (PDT)
Received: by lbbuc2 with SMTP id uc2so935606lbb.2 for <ipv6@ietf.org>; Tue, 28 Apr 2015 10:07:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d41E3B6TsdHOi4FQIiRtKNYfm/1XHs8BVIJqQkuMsWg=; b=Sjb5FT68pDRNwqt/WBvAZ5ERUO0I9Z9VZ/j5u1bhKM+U/po70mUVK8abD7bThWpWXu HrsBdvBlZ66U9n1u9f3Ya9B/i8FNeBI8fod8e29Q2ht1LF5LYfNFhXPbvX/kZhREKK+O PL7loS9Q7H+/cQ+gxjoN65EkD5F5kG6vPkJCUEVn8TlIy5Q4Z3VQ5RyRuL7ZGM4em/2d Mlo+jQ9kEbXRiZp0dMCVxSKoQQSFGorIxhMwLcEzY+O2SWMtxovctpj3Tg9pCEmjYkN5 b+DGBlPk9fz7XqPqIg8Ubypt8iLGkkJ9X1Y71xpWtMhbdQCDSTiDYQkvRYnBX7D4s9lZ LqSg==
MIME-Version: 1.0
X-Received: by 10.112.234.163 with SMTP id uf3mr15656888lbc.9.1430240871999; Tue, 28 Apr 2015 10:07:51 -0700 (PDT)
Received: by 10.112.26.111 with HTTP; Tue, 28 Apr 2015 10:07:51 -0700 (PDT)
In-Reply-To: <41275F44-F36C-438A-A957-8FB2B216CE81@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com> <CBB02F0C-939D-4812-9D53-EB381637BBDC@cisco.com> <20150428084154.74320042@echo.ms.redpill-linpro.com> <41275F44-F36C-438A-A957-8FB2B216CE81@cisco.com>
Date: Tue, 28 Apr 2015 12:07:51 -0500
Message-ID: <CAA0dE=XZ=qN+hGYk2tdwhsqryRaWQjZ6wDfBarHEOP=sQ47Zmg@mail.gmail.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
From: Alberto Leiva <ydahhrk@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/QQ2mxX28-PhSY0B_G6kQJcnifqg>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, Tore Anderson <tore@fud.no>, "jool@nic.mx" <jool@nic.mx>, Fernando Gont <fgont@si6networks.com>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 17:07:55 -0000

> I'm adding the implementors in question to the CC list, so they may elaborate on their position if they so desire.

There is one minor thing I did not mention in that documentation. It
does seem minor, but I'll include it here for completeness sake.

I feel there's some degree of carelessness toward atomic fragments in
Linux's network stack. They are a minor paragraph in RFC 2460, easy to
overlook, and the idea can collapse in the hands of a careless or
recklessly optimizing coder.

One example of such scenarios is pictured in the documentation linked
by Tore: In the output pipeline, Linux's fragmentation code *assumes*
there's no fragment header (if I'm not missing something), so if the
packet is an atomic fragment, the code will generate packets with
consecutive fragment headers, where only one is supposed to be legal.

Another example is the incoming pipeline: Netfilter's fragment
reassembly module goes through pains to pretend incoming fragments are
actually a single/full packet, which involves some layer-3 header
corruption. If you're interested, look up "This is one of the reasons
why I've learned to hate atomic fragments so much" here:
https://github.com/NICMx/NAT64/wiki/nf_defrag_ipv4-and-nf_defrag_ipv6#implementation-gotchas.
This corruption can sometimes be reverted, sometimes it cannot. Any
module can call skb_linearize() and ruin everything
(https://github.com/NICMx/NAT64/wiki/nf_defrag_ipv4-and-nf_defrag_ipv6#nf_defrag_ipv6---kernels-313).

In general, the skb_linearize() function is discouraged, which is why
I personally do not consider this input quirk a strong argument
against atomic fragments. However, I feel it does show that
*defragmenting IPv6 routers* can exist in the wild (though they are
very unlikely), and this can easily break RFC 6145's assumptions
regarding the DF flag and the redundant fragment header (among other,
even more important things).

I just can't help but wonder why is that RFC 6145 chooses to store
state in fields that were originally not intended for that purpose.
Saying "Okay, this fragment header probably means the IPv4 node wasn't
using Path MTU discovery several packets ago" is trusting the IPv6
network (including all routers in-between) behaves in a peculiar way.
It sounds to me like awkward design.

Well, I could be missing something more important since RFC 6145
doesn't always explain its rationale. Anyway, that's my two cents.

I'd like to apologize to Fernando. A fairly long time ago we discussed
this and he asked for some suggested text for the draft, and I didn't
answer. I can still do it if it's relevant.

Alberto

On Tue, Apr 28, 2015 at 1:46 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>
>> On Apr 27, 2015, at 11:41 PM, Tore Anderson <tore@fud.no> wrote:
>>
>> - Sunset4 may be appropriate, as facilitating the disablement of IPv4
>>  in (parts of) the network is perhaps the most important use case for
>>  SIIT. However there's no fitting work item listed in the sunset4
>>  charter as far as I can see.
>
> We can talk with Marc and Wes about that. Yes, it may be appropriate.


From nobody Tue Apr 28 11:17:28 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60171B2B66 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 11:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWLsgxIsnxt1 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 11:17:26 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F1261A89C6 for <ipv6@ietf.org>; Tue, 28 Apr 2015 11:17:26 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id A7DA661A6; Tue, 28 Apr 2015 11:17:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=5Dl0c1UBsU4vRdNb+1lYLAEcHcI=; b= d2uvGSbyhwwj4b2I0FLY+irbQP3N3oFFTciz9d3vmaMw2QIHEcBhKWopEQcP+vq9 Ovy1/ABmErtuRYoc6sIDe1ucotPLulbaXQYFMVm8Kv1NxT5EB8omQ3oCPPK59hcW jHmZvpfB57M6Fnmi35MKqK37cKkJ8oXbAkp5tNQiGcU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=NOLRIkk2j7w7+8IRFBG5nR2KA3 7J8nXjnrM37Dy+0Iwib/1aqvAGccWqYJp+65PV622q54lygZQBEln2EYuIGZcSih 8TAC8li0132MMe0HBMB6SU+i/I/o9+76zz616yjloVRXh3nx6Q1DAVMVuSwbQz8u WKGhiUmZ+4c/IFX1M=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 606BF61B9; Tue, 28 Apr 2015 11:17:25 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 0825443D983A; Tue, 28 Apr 2015 20:17:13 +0200 (CEST)
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3927EABD-0202-4250-BB47-3E135102AB89"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
Date: Tue, 28 Apr 2015 20:17:12 +0200
Message-Id: <8E150E02-9A95-4282-A897-68A6A5F469A4@employees.org>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tjaV7FUOHFsMe3VRqYZ76x9WVwg>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 18:17:28 -0000

--Apple-Mail=_3927EABD-0202-4250-BB47-3E135102AB89
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>> We've rev'ed the aforementioned I-D with minor clarifications =
requested
>> by implementers:
>> =
<https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-generation=
-01>
>>=20
>> We think the current version of the I-D is ready for WGLC.
>=20
> The ID contains three essential parts: why the recommendations, a =
relatively minor change to RFC 2460, and some deep surgery on RFC 6145. =
Let me as a question on that last, if you would.
>=20
> Have those proposed changes been vetted with the implementors you =
mentioned?
>=20
> If this is the consensus of the working group, I personally would be =
in favor of churning 6145 rather than making future implementors read =
two documents in parallel. I would want to do that in 6man.

yes,  I also agree with you that it would be better to reissue RFC6145. =
I think there are better homes for that than 6man, but if no-one else =
volunteers, then let=E2=80=99s have a discussion with our ADs.

cheers,
Ole


--Apple-Mail=_3927EABD-0202-4250-BB47-3E135102AB89
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

iQEcBAEBCgAGBQJVP86oAAoJEFuJXizso86gUjQH/2ePY6hPrWtzpV+iYIFSE+M+
4exWPZb4KRp6NaaVHhzhz7R2HkMOFtED0NWOTPK+nhgUHzNWKlx+eBMBFGNOHNmE
rxQWTLcRI1WqR1Afm8BnF2/5ZVsIIbtLPWGj3wHwO87xfWp/f5o59R0dBEQIG6YX
87/IlYVvj7GurTRMV6kJwGbURP8G9UzfW9dipJbhMA3yG7sW67Yslagja2itdb1X
bZoGHL2TMUwMjLWTZ8490MTa0Ds+IZGOwi547NlU2lmz6YsqNmAFEnyJnijCBnvB
AFNJs646yzS8JcQc8fCzVOEtvmhNmndW5ZD0ZS3cadSZ4zyedm+Unf6W66SDgOE=
=3lf0
-----END PGP SIGNATURE-----

--Apple-Mail=_3927EABD-0202-4250-BB47-3E135102AB89--


From nobody Tue Apr 28 12:11:18 2015
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E194E1A0171 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 12:11:16 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tu5WPsnyVVJA for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 12:11:15 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::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 8C7031A014C for <ipv6@ietf.org>; Tue, 28 Apr 2015 12:11:15 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so26164123ieb.3 for <ipv6@ietf.org>; Tue, 28 Apr 2015 12:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:date:message-id:cc:to:mime-version;  bh=OcwYnIsvC7bdcmDSZNsyrvtYe/59SVfBK1PM2xxeZV4=; b=xKKRFqZ5KvVtZzgpmImeVFDuonFj//92QrwLo0pq51a2pdBsbsr/udll8qy588fVFh TrsF9G6x2Bg9jz2ytIsYYicx4R/h67alV+ILe7rCKm/g0ZNU8c3NFw7afc6DNmNE4SY5 5r1a8HncAMPyL/PM8NP5NimM3Osv+RGdA/L7JRy2OW4URwgdO4VBGZU7utXYbcEsEBBq pN4sEmnev8zrKMZYnTrVMf235j3BGnSzTIWaNJK8OCiAqNsSZWYIy63qRw3jyeGCHFdD w1n6echNXEdYrgqDAzoTRO/Yo9oyl+GgFauOJtz6J4qQCyApT3r1ljmVvg2TG1CYBCmL XEbw==
X-Received: by 10.50.50.148 with SMTP id c20mr9225911igo.0.1430248275011; Tue, 28 Apr 2015 12:11:15 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id t41sm15297006ioe.5.2015.04.28.12.11.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Apr 2015 12:11:13 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
X-Pgp-Agent: GPGMail 2.5b6
Content-Type: multipart/signed; boundary="Apple-Mail=_DD2EFF5C-2462-476F-BC1D-FDCD2B7DFFEF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Result of 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
Date: Tue, 28 Apr 2015 12:11:11 -0700
Message-Id: <4B437FBC-B618-4BF9-A837-A0A8B5EE97FA@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/RnCEy1DAxidp8F3Oz8UmATmwq50>
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 19:11:17 -0000

--Apple-Mail=_DD2EFF5C-2462-476F-BC1D-FDCD2B7DFFEF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

The chairs conclude there is a consensus in the 6MAN working to have =
this draft become a working group draft.  The authors should submit the =
next version as a 6MAN working group document.

However, while we are adopting this document, there are still a number =
of issues that must be resolved before this document could be advanced =
to the IESG.

Thanks,
Bob & Ole



--Apple-Mail=_DD2EFF5C-2462-476F-BC1D-FDCD2B7DFFEF
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

iQEcBAEBCgAGBQJVP9tQAAoJEK7rdBF357uomAMH/jRy3AhLlPlDWIqALzrAL8wV
R1/bcnxWspR2V4pui5nD2YUG5qvn78oDwAZsMcm8+JCCY26QyplEadafm1Wk9nlt
TCKrsGlbjFCGsNzzCIjEj3lvvaHFiaca2OoClXskJJl3xA6dWMnVr+CehrG+dpny
5meJNWJpskOYVQpCvILuYNM5k6VhlP2B1vWOazHIbA3Ua2s1Lpsr0IKiLS0PQyNm
8jKUzayUPoO5BCvvkvc7ipJ0FdZiD7niAAWYvA8ymwhIw/rbkm5+Y68iE9T98y5G
T8/iI3JeiSB4jw+Owq4Gf70T8c/wif4fJzX4YDgxOKb/LnWxYDIHtotV053bdEo=
=7P73
-----END PGP SIGNATURE-----

--Apple-Mail=_DD2EFF5C-2462-476F-BC1D-FDCD2B7DFFEF--


From nobody Tue Apr 28 15:48:30 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFAAC1A8968 for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 15:48:22 -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, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTXfylvDiifo for <ipv6@ietfa.amsl.com>; Tue, 28 Apr 2015 15:48:18 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::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 113861A902E for <ipv6@ietf.org>; Tue, 28 Apr 2015 15:48:18 -0700 (PDT)
Received: by pabtp1 with SMTP id tp1so8991569pab.2 for <ipv6@ietf.org>; Tue, 28 Apr 2015 15:48:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QD+72VA87nRDyYm2IuzqKhStjpDpJYrK8wQCqLJ8mzs=; b=XBUBMunQhTEWJ1A/Q8cshpmtrTdmb8Y66Mx7xgYjs5RFGedXrXtF1nzQizAW7mjEMw OCiPmJrxBwKn+dwFrXzDEORRRUqSLJVrLOz997ff4FihpCZvMLGMT0FAq2DwduAy6Igu j+OzUiqDdousS+MJajHn539Fu/yufFUbZfbKo7bdvRwQl1Z/vXldAkdCFK8G/HOeAtGE 55Fxl6/a9mLzuroQD9/D/xDjj3ESUYvkvTTw0ypQsW3wnk2Ve+S0HX1aymVcy8PrbzW+ G3bSYeEoealHp4kLNnnBoPvAMzazvqyHqPj3/n/fYg7s6yQ/x/a3poJM9Oc3n7eIHdN9 8FBA==
X-Received: by 10.66.228.130 with SMTP id si2mr36197136pac.92.1430261297795; Tue, 28 Apr 2015 15:48:17 -0700 (PDT)
Received: from ?IPv6:2406:e007:5efe:1:28cc:dc4c:9703:6781? ([2406:e007:5efe:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id ea4sm23326993pbb.94.2015.04.28.15.48.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Apr 2015 15:48:16 -0700 (PDT)
Message-ID: <55400E2F.6020603@gmail.com>
Date: Wed, 29 Apr 2015 10:48:15 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>, Tore Anderson <tore@fud.no>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <20150428071803.7c8b29f5@echo.ms.redpill-linpro.com> <CBB02F0C-939D-4812-9D53-EB381637BBDC@cisco.com> <20150428084154.74320042@echo.ms.redpill-linpro.com> <41275F44-F36C-438A-A957-8FB2B216CE81@cisco.com>
In-Reply-To: <41275F44-F36C-438A-A957-8FB2B216CE81@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PllGAqnXYlp6CtPx3xERRzE4jZI>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "jool@nic.mx" <jool@nic.mx>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 22:48:22 -0000

On 28/04/2015 18:46, Fred Baker (fred) wrote:
> 
>> On Apr 27, 2015, at 11:41 PM, Tore Anderson <tore@fud.no> wrote:
>>
>> - Sunset4 may be appropriate, as facilitating the disablement of IPv4
>>  in (parts of) the network is perhaps the most important use case for
>>  SIIT. However there's no fitting work item listed in the sunset4
>>  charter as far as I can see.
> 
> We can talk with Marc and Wes about that. Yes, it may be appropriate.

There's always the intarea WG if nobody else will take it.
I agree that the work should be done.

   Brian


From nobody Wed Apr 29 03:13:34 2015
Return-Path: <liushucheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1471ACD11 for <ipv6@ietfa.amsl.com>; Wed, 29 Apr 2015 03:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o5-LyQC1kt-O for <ipv6@ietfa.amsl.com>; Wed, 29 Apr 2015 03:13:31 -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 6A5081A2130 for <ipv6@ietf.org>; Wed, 29 Apr 2015 03:13:30 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVL78219; Wed, 29 Apr 2015 10:13:29 +0000 (GMT)
Received: from SZXEMA414-HUB.china.huawei.com (10.82.72.73) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 29 Apr 2015 11:13:20 +0100
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.195]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0158.001; Wed, 29 Apr 2015 18:12:45 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: Ole Troan <otroan@employees.org>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Topic: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Index: AQHQgU7gqfZyH/Fn9UKmbQJ5OldPg51hKKSAgAENuQCAAY6/MA==
Date: Wed, 29 Apr 2015 10:12:45 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB600D5AAE@SZXEMA509-MBS.china.huawei.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <8E150E02-9A95-4282-A897-68A6A5F469A4@employees.org>
In-Reply-To: <8E150E02-9A95-4282-A897-68A6A5F469A4@employees.org>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.123.42]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8lDqQJMSJ1bITA1pu2JJoNfrUxU>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2015 10:13:33 -0000

SGkgT2xlLA0KDQpJdCBzZWVtcyB0byB1cyB0aGF0IHdlIGFncmVlIHRoYXQgdGhlIGJlc3Qgd2F5
IGlzIHRvIGhhdmUgdGhpcyBkb2N1bWVudCBkZXByZWNhdGUgdGhlIGdlbmVyYXRpb24gb2YgYXRv
bWljIGZyYWdtZW50cywgYW5kIGhhdmUgdGhlIFJGQzYxNDUgdXBkYXRlcyBpbiBhIHNlcGFyYXRl
IGRvY3VtZW50IChSRkM2MTQ1YmlzKS4NCg0KU2hvdWxkIHdlIHVwZGF0ZSBvdXIgZG9jdW1lbnQg
YWNjb3JkaW5nbHksIGFuZCByZXN1Ym1pdCwgYW5kIHRoZW4gbWFrZSBwcm9ncmVzcz8gVGhhbmtz
Lg0KDQpDaGVlcnMsDQpXaWxsDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJv
bTogT2xlIFRyb2FuIFttYWlsdG86b3Ryb2FuQGVtcGxveWVlcy5vcmddDQo+IFNlbnQ6IFdlZG5l
c2RheSwgQXByaWwgMjksIDIwMTUgMjoxNyBBTQ0KPiBUbzogRnJlZCBCYWtlciAoZnJlZCkNCj4g
Q2M6IEZlcm5hbmRvIEdvbnQ7IDZtYW4gV0c7IDZtYW4tY2hhaXJzQHRvb2xzLmlldGYub3JnOw0K
PiBkcmFmdC1pZXRmLTZtYW4tZGVwcmVjYXRlLWF0b21mcmFnLWdlbmVyYXRpb25AdG9vbHMuaWV0
Zi5vcmcNCj4gU3ViamVjdDogUmU6IE1vdmluZyBmb3J3YXJkDQo+IGRyYWZ0LWlldGYtNm1hbi1k
ZXByZWNhdGUtYXRvbWZyYWctZ2VuZXJhdGlvbi0wMSAoUmU6IEktRCBBY3Rpb246DQo+IGRyYWZ0
LWlldGYtNm1hbi1kZXByZWNhdGUtYXRvbWZyYWctZ2VuZXJhdGlvbi0wMS50eHQpDQo+IA0KPiA+
PiBXZSd2ZSByZXYnZWQgdGhlIGFmb3JlbWVudGlvbmVkIEktRCB3aXRoIG1pbm9yIGNsYXJpZmlj
YXRpb25zDQo+ID4+IHJlcXVlc3RlZCBieSBpbXBsZW1lbnRlcnM6DQo+ID4+IDxodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi02bWFuLWRlcHJlY2F0ZS1hdG9tZnJhZy1nZW5l
cg0KPiA+PiBhdGlvbi0wMT4NCj4gPj4NCj4gPj4gV2UgdGhpbmsgdGhlIGN1cnJlbnQgdmVyc2lv
biBvZiB0aGUgSS1EIGlzIHJlYWR5IGZvciBXR0xDLg0KPiA+DQo+ID4gVGhlIElEIGNvbnRhaW5z
IHRocmVlIGVzc2VudGlhbCBwYXJ0czogd2h5IHRoZSByZWNvbW1lbmRhdGlvbnMsIGEgcmVsYXRp
dmVseQ0KPiBtaW5vciBjaGFuZ2UgdG8gUkZDIDI0NjAsIGFuZCBzb21lIGRlZXAgc3VyZ2VyeSBv
biBSRkMgNjE0NS4gTGV0IG1lIGFzIGENCj4gcXVlc3Rpb24gb24gdGhhdCBsYXN0LCBpZiB5b3Ug
d291bGQuDQo+ID4NCj4gPiBIYXZlIHRob3NlIHByb3Bvc2VkIGNoYW5nZXMgYmVlbiB2ZXR0ZWQg
d2l0aCB0aGUgaW1wbGVtZW50b3JzIHlvdQ0KPiBtZW50aW9uZWQ/DQo+ID4NCj4gPiBJZiB0aGlz
IGlzIHRoZSBjb25zZW5zdXMgb2YgdGhlIHdvcmtpbmcgZ3JvdXAsIEkgcGVyc29uYWxseSB3b3Vs
ZCBiZSBpbiBmYXZvciBvZg0KPiBjaHVybmluZyA2MTQ1IHJhdGhlciB0aGFuIG1ha2luZyBmdXR1
cmUgaW1wbGVtZW50b3JzIHJlYWQgdHdvIGRvY3VtZW50cyBpbg0KPiBwYXJhbGxlbC4gSSB3b3Vs
ZCB3YW50IHRvIGRvIHRoYXQgaW4gNm1hbi4NCj4gDQo+IHllcywgIEkgYWxzbyBhZ3JlZSB3aXRo
IHlvdSB0aGF0IGl0IHdvdWxkIGJlIGJldHRlciB0byByZWlzc3VlIFJGQzYxNDUuIEkgdGhpbmsN
Cj4gdGhlcmUgYXJlIGJldHRlciBob21lcyBmb3IgdGhhdCB0aGFuIDZtYW4sIGJ1dCBpZiBuby1v
bmUgZWxzZSB2b2x1bnRlZXJzLCB0aGVuDQo+IGxldOKAmXMgaGF2ZSBhIGRpc2N1c3Npb24gd2l0
aCBvdXIgQURzLg0KPiANCj4gY2hlZXJzLA0KPiBPbGUNCg0K


From nobody Wed Apr 29 04:10:02 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 356B01A6F11 for <ipv6@ietfa.amsl.com>; Wed, 29 Apr 2015 04:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLW6KnPhSvu0 for <ipv6@ietfa.amsl.com>; Wed, 29 Apr 2015 04:09:59 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C74EB1B2C2D for <ipv6@ietf.org>; Wed, 29 Apr 2015 04:09:59 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id F1C8E6146; Wed, 29 Apr 2015 04:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=99LFcfKdGbjnnzsoHTz73avHn8M=; b= Oh2rpnViJP+z7GK69eYkaPySb710owThSUEXzJN6mtt3TgAWW0y1f8vcJiO1+X79 LPeURzqPGkWI8ImFa3lQwK9W+Sz2dP+DrR8bIhLTeBTOFPMzmvP8ZdWhVi186geX /YVaJH92DUZ22NAJBrHmvgtqdICC40JbgQ+uaTigtYI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=sBCi7RMQftQj4YoAOSZdHnzlxz djXtnqXqp40UqcIpAeE6/5foZBXeNFUHRgFvMqD6zscTqv2RPKytM/sDxgyszUV8 Gv2Bxrq30pinsLeHWM+zwULFXWigxrxhRAqDP3LdqNMW6KDxNXEwaKB1FtwS6AH8 Eq+5VFJ9gu0b6KH/8=
Received: from gomlefisk.localdomain (unknown [173.38.220.48]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 3CFD560B7; Wed, 29 Apr 2015 04:09:58 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 4AFDE440F0B4; Wed, 29 Apr 2015 13:09:55 +0200 (CEST)
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_235701A6-485C-48EE-8211-CEE13AFE74A5"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB600D5AAE@SZXEMA509-MBS.china.huawei.com>
Date: Wed, 29 Apr 2015 13:09:54 +0200
Message-Id: <B8B29AD0-EF6F-4226-A91F-01DF3A28CEAB@employees.org>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <8E150E02-9A95-4282-A897-68A6A5F469A4@employees.org> <C9B5F12337F6F841B35C404CF0554ACB600D5AAE@SZXEMA509-MBS.china.huawei.com>
To: "Liushucheng (Will)" <liushucheng@huawei.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HvDLlONo27IVzFZZDui4LFiY0d0>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2015 11:10:01 -0000

--Apple-Mail=_235701A6-485C-48EE-8211-CEE13AFE74A5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Will,

> It seems to us that we agree that the best way is to have this =
document deprecate the generation of atomic fragments, and have the =
RFC6145 updates in a separate document (RFC6145bis).
>=20
> Should we update our document accordingly, and resubmit, and then make =
progress? Thanks.

I=E2=80=99d suggest you keep the draft as is for the moment, until the =
relevant text is moved over to 6145bis, and that has found a new home.

another question on this proposed change. as we=E2=80=99re looking at =
making RFC2460 Internet Standard.
can this change; e.g with an updated host not including the FH and a =
legacy translator lead to incompatibility problems?

cheers,
Ole

>> -----Original Message-----
>> From: Ole Troan [mailto:otroan@employees.org]
>> Sent: Wednesday, April 29, 2015 2:17 AM
>> To: Fred Baker (fred)
>> Cc: Fernando Gont; 6man WG; 6man-chairs@tools.ietf.org;
>> draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org
>> Subject: Re: Moving forward
>> draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action:
>> draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
>>=20
>>>> We've rev'ed the aforementioned I-D with minor clarifications
>>>> requested by implementers:
>>>> =
<https://tools.ietf.org/html/draft-ietf-6man-deprecate-atomfrag-gener
>>>> ation-01>
>>>>=20
>>>> We think the current version of the I-D is ready for WGLC.
>>>=20
>>> The ID contains three essential parts: why the recommendations, a =
relatively
>> minor change to RFC 2460, and some deep surgery on RFC 6145. Let me =
as a
>> question on that last, if you would.
>>>=20
>>> Have those proposed changes been vetted with the implementors you
>> mentioned?
>>>=20
>>> If this is the consensus of the working group, I personally would be =
in favor of
>> churning 6145 rather than making future implementors read two =
documents in
>> parallel. I would want to do that in 6man.
>>=20
>> yes,  I also agree with you that it would be better to reissue =
RFC6145. I think
>> there are better homes for that than 6man, but if no-one else =
volunteers, then
>> let=E2=80=99s have a discussion with our ADs.
>>=20
>> cheers,
>> Ole
>=20


--Apple-Mail=_235701A6-485C-48EE-8211-CEE13AFE74A5
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

iQEcBAEBCgAGBQJVQLwDAAoJEFuJXizso86g0DAH/jyUuEsIMNB3ctb2UzR7tCNq
KsfNl10OFXau6Vui3RoqnZYGxsyXlIPQZgx4spE6BGtMC9FqA1NG/LAYxMFxjTd7
olFdReAq+V9s28Zw3wyXQOPDAtHyFPQNLbBUQpJjjqAU7Ts1PdBuyXXBaUKyA4go
l+AIuX3gj/TshD8s2Obzp1QepQFNGf/z5/8AYYyOB5XLjV7I+FOmYzKCQ+2CBz0P
bs7/HPS3NgbMbJK0L7kO/Ena/mZJviRm42DrYp00Rue8JggCIxbgXLsdrM7wlmvn
2MAC4SgpeJR5/5uyureNxZmi7TAwHiCZG5pF/UnLUMjL0HPRmsq0d98HbUEPKvY=
=CMbX
-----END PGP SIGNATURE-----

--Apple-Mail=_235701A6-485C-48EE-8211-CEE13AFE74A5--


From nobody Thu Apr 30 12:42:14 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB8C1A9057 for <ipv6@ietfa.amsl.com>; Thu, 30 Apr 2015 12:42: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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0joZxI7BGb7Z for <ipv6@ietfa.amsl.com>; Thu, 30 Apr 2015 12:42:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::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 EBDFF1A700A for <ipv6@ietf.org>; Thu, 30 Apr 2015 12:42:10 -0700 (PDT)
Received: from [186.137.82.224] (helo=[192.168.3.107]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YnuLV-0006Lv-5l; Thu, 30 Apr 2015 21:42:05 +0200
Message-ID: <55427E9A.40906@si6networks.com>
Date: Thu, 30 Apr 2015 16:12:26 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
In-Reply-To: <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TNNJG-Af--eQigZKDGLKRoyc5rM>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2015 19:42:13 -0000

Hi, Fred,

On 04/27/2015 11:11 PM, Fred Baker (fred) wrote:
> 
> The ID contains three essential parts: why the recommendations, a
> relatively minor change to RFC 2460, and some deep surgery on RFC
> 6145. Let me as a question on that last, if you would.
> 
> Have those proposed changes been vetted with the implementors you
> mentioned?

Yes.



> If this is the consensus of the working group, I personally would be
> in favor of churning 6145 rather than making future implementors read
> two documents in parallel. I would want to do that in 6man.

I agree with you.

So... should a revision of RFC6145 be done here? Or, if not, what's the
procedure to find a home for it?

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Apr 30 12:42:22 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C75651ACE0D for <ipv6@ietfa.amsl.com>; Thu, 30 Apr 2015 12:42:15 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYOcilMK3eWX for <ipv6@ietfa.amsl.com>; Thu, 30 Apr 2015 12:42:14 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::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 8DA4B1A700A for <ipv6@ietf.org>; Thu, 30 Apr 2015 12:42:13 -0700 (PDT)
Received: from [186.137.82.224] (helo=[192.168.3.107]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YnuLZ-0006M0-Ra; Thu, 30 Apr 2015 21:42:10 +0200
Message-ID: <55428281.4060707@si6networks.com>
Date: Thu, 30 Apr 2015 16:29:05 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>,  "Liushucheng (Will)" <liushucheng@huawei.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <8E150E02-9A95-4282-A897-68A6A5F469A4@employees.org> <C9B5F12337F6F841B35C404CF0554ACB600D5AAE@SZXEMA509-MBS.china.huawei.com> <B8B29AD0-EF6F-4226-A91F-01DF3A28CEAB@employees.org>
In-Reply-To: <B8B29AD0-EF6F-4226-A91F-01DF3A28CEAB@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/U8IZkeHaz7sDeEb_Ep3dYi1n_As>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2015 19:42:15 -0000

Hi, Ole,

On 04/29/2015 08:09 AM, Ole Troan wrote:
> 
>> It seems to us that we agree that the best way is to have this
>> document deprecate the generation of atomic fragments, and have the
>> RFC6145 updates in a separate document (RFC6145bis).
>> 
>> Should we update our document accordingly, and resubmit, and then
>> make progress? Thanks.
> 
> I’d suggest you keep the draft as is for the moment, until the
> relevant text is moved over to 6145bis, and that has found a new
> home.

What's the "procedure" to find a home for RFC6145bis?

If there's consensus to do the RFC6145 update as a separate document,
I'd probably rev without the RFC6145 text and progress the document.

For instance, having the document progressed wuld be useful for the
RFC6145 update itself.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Apr 30 13:24:22 2015
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D593A1A0037 for <ipv6@ietfa.amsl.com>; Thu, 30 Apr 2015 13:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLq8skatSexT for <ipv6@ietfa.amsl.com>; Thu, 30 Apr 2015 13:24:19 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 768AC1A0004 for <ipv6@ietf.org>; Thu, 30 Apr 2015 13:24:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2037; q=dns/txt; s=iport; t=1430425461; x=1431635061; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=vqhxX4xTxNYvXUfiKRWPfNZvszfLvM5ulZhRp7gvpX4=; b=e7uWxh1Ccyhb7U4sn1rqzCrGZoEzoJ/hEF1T4mX60odahz/9qUy3SJyg tFRauetjLTTMrVEoOgFhZW0bZ8Vs3qBswnGwy1zqO0tkYYHo7n/4Iv/bw Tg/julv/dCbU6CN8q4xVPpjk3YAxxWbWAQeudlvUxdXvrbLeRauuqwIaw E=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A4BQBCjkJV/4cNJK1cgwyBLwWDFsoVAoFXTAEBAQEBAYELhCABAQEDASNWBQsCAQgOCiMHAgIyJQIEDgUOiBUItQqTVQEBAQEBAQEBAQEBAQEBAQEBAQEBGIs4hQUHgmgvgRYFkWqBd4E4hxmBI40sg16DUCOCOIE8b4FEgQEBAQE
X-IronPort-AV: E=Sophos;i="5.11,678,1422921600";  d="asc'?scan'208";a="413018259"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP; 30 Apr 2015 20:24:20 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t3UKOIOk003625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Apr 2015 20:24:18 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.172]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Thu, 30 Apr 2015 15:24:18 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Topic: Moving forward draft-ietf-6man-deprecate-atomfrag-generation-01 (Re: I-D Action: draft-ietf-6man-deprecate-atomfrag-generation-01.txt)
Thread-Index: AQHQgU7liPOJOD1i1UeQA2xTungMaZ1iAo4AgAENvQCAAQr7gIAAD/cAgAIdzoCAAA9rAA==
Date: Thu, 30 Apr 2015 20:24:18 +0000
Message-ID: <CE160F2A-3AC4-4E4F-9F28-2F1807C5392B@cisco.com>
References: <20150428005529.16774.5976.idtracker@ietfa.amsl.com> <553EDBDC.6020108@si6networks.com> <0EC0C140-050F-4275-AA27-EFA9B00C045F@cisco.com> <8E150E02-9A95-4282-A897-68A6A5F469A4@employees.org> <C9B5F12337F6F841B35C404CF0554ACB600D5AAE@SZXEMA509-MBS.china.huawei.com> <B8B29AD0-EF6F-4226-A91F-01DF3A28CEAB@employees.org> <55428281.4060707@si6networks.com>
In-Reply-To: <55428281.4060707@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_26A38FF8-CE08-477B-884A-8B7402952BB7"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/QKzOle-kNDOQd8c6PJyVBBpwVAg>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Congxiao Bao <congxiao@cernet.edu.cn>, 6man WG <ipv6@ietf.org>, Tore Anderson <tore@fud.no>, "Kevin Yin \(kyin\)" <kyin@cisco.com>, Xing Li <xing@cernet.edu.cn>, "draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org" <draft-ietf-6man-deprecate-atomfrag-generation@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2015 20:24:21 -0000

--Apple-Mail=_26A38FF8-CE08-477B-884A-8B7402952BB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Apr 30, 2015, at 12:29 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> What's the "procedure" to find a home for RFC6145bis?

I think it=E2=80=99s a gimongously arduous process like =E2=80=9Cask the =
AD=E2=80=9D.

My suggestion:

I=E2=80=99ll start out by asking Heather for her preferred XML source =
for the draft. It would be nice to have the right input. =46rom that, I =
can create something under a name like draft-baker-rfc6145-bis-*.txt, =
and insert changes from the erratum, your draft, and Tore Anderson=E2=80=99=
s draft. We can then discuss it, wherever the right place turns out to =
be, including intarea. Where I=E2=80=99m going to push back is people =
wanting to make random changes; it=E2=80=99s one thing to have proven =
changes incorporated, and quite another to have armchair pundits =
comment.

The document is largely based on (e.g. a repeat of) SIIT, which has =
implementations, and there are multiple implementations of 6145. I=E2=80=99=
ll want each of those implementers to agree to the update.

--Apple-Mail=_26A38FF8-CE08-477B-884A-8B7402952BB7
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 - http://gpgtools.org

iQEVAwUBVUKPcZ9ieig10VPpAQK2vAf9GfManfNKhtTyB5Me3uyNq1OxqPYtZ9GS
96+VKKVPSglmYwRYvZa222LvlIR13zeWHQRPkFt1X4QfuwTB3aPQBkrjMQAsdwY0
mXpKnx5qQs5hCFWTYcaT5GxiphG6LOuDIwLAOtBHozZ8FMJCveNywRxbC3hOVzUT
+bV4L69d+EvspmF4Aklt/8zyIGLiMGLZbU1UpwpepEJi/RWCRAsq5AmCYAJHJnAZ
MwVIFfJhKDbXmRlSwCIHnDSgcNjKMZvjIJBb3zFp9xfkKiReVJ4JjInrINNqXTL0
Uuzm3bn3bciQ6Fws5DL5l7/Djhy0RtStCpfq9fpG1urTit8Puo5FdQ==
=z7C9
-----END PGP SIGNATURE-----

--Apple-Mail=_26A38FF8-CE08-477B-884A-8B7402952BB7--

