
From nobody Thu Oct  1 10:45:36 2015
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C29531A82E2 for <opsawg@ietfa.amsl.com>; Thu,  1 Oct 2015 10:45:29 -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 kMI-Ev74duBL for <opsawg@ietfa.amsl.com>; Thu,  1 Oct 2015 10:45:28 -0700 (PDT)
Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com [209.85.160.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4EC11A7028 for <opsawg@ietf.org>; Thu,  1 Oct 2015 10:45:28 -0700 (PDT)
Received: by ykft14 with SMTP id t14so87014555ykf.0 for <opsawg@ietf.org>; Thu, 01 Oct 2015 10:45:28 -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:date:message-id:subject:from:to :content-type; bh=1tEcP7twO/TwBP0BDA3Yz1wXMMFQ5aKjWbk1WbTJR5w=; b=VXJEWDtFiOy51noe9QpCRplMB3iEpeIFkR3VOY4yW7McvKdQQ2a1NqIfpcrLOmhpdP eEfQQ36fDf5g7WXBwAuY4n4z+XTikDEsOiPs2qdgerxVN8NH//OiU7DUFWaG/sEAMp5i mciHzgodFccic76Twy+bE+8jGY6wTLrdLGsQaUkJdQbZHAeXJ3oMxGxLB0ClgbAA4jnC m/c0s0Dh3w/RFsPeBYV89MN3iF20MwlsOA2I+EcQWFiv0xHXb6XxuP2Xb1/2+XA7zdnB 6VtTiNOLPOrBZBCLiWmhb15bYs4fsXKItgQbffjTuDTY7Jxj+txkNvMDFSGw+SZk4KKT PEGw==
X-Gm-Message-State: ALoCoQmijPsVHTFFrsCyOIe0hb0vg20KPOCzInOMt5TeYpPr6SebynHTZGg9c61wARXGc/Jncc90
MIME-Version: 1.0
X-Received: by 10.170.42.20 with SMTP id 20mr9195601ykk.43.1443721527906; Thu, 01 Oct 2015 10:45:27 -0700 (PDT)
Received: by 10.37.52.135 with HTTP; Thu, 1 Oct 2015 10:45:27 -0700 (PDT)
Date: Thu, 1 Oct 2015 13:45:27 -0400
Message-ID: <CAHw9_iKEN6MwO_EWTrXF-8aOB7-HQ-E5=GKt0Xpgt_qxiUef6A@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/R3HbzHvIuIftlFZWDFWl07nhfnM>
Subject: [OPSAWG] draft-ietf-opsawg-capwap-alt-tunnel - returned to WG.
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2015 17:45:29 -0000

Hi all,

Apologies for not mentioning this sooner, this status update fell
through the cracks....

I requested that draft-ietf-opsawg-capwap-alt-tunnel be returned to
the working group (from the IESG, where it had been sitting forlornly)
so that it can be merged with
draft-you-opsawg-capwap-separation-for-mp.
This occurred on September 7th.

Once the new content is merged in, we hope to do a compressed WGLC and
then resubmit to the IESG.

Thanks to Benoit for noticing that we hadn't mentioned this to the WG.

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 Mon Oct  5 08:57:54 2015
Return-Path: <evyncke@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D22B1B3213; Mon,  5 Oct 2015 08:57:52 -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 RP0cJ6s-TLKh; Mon,  5 Oct 2015 08:57:50 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F4BA1B31FE; Mon,  5 Oct 2015 08:57:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8976; q=dns/txt; s=iport; t=1444060644; x=1445270244; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2hmYvAMGDAEn8eMIQn77S14g6VFJIB/wznuz2DDm02Q=; b=ePU57/qa22knopQ4235KIrodQFqcXr1BtzIK7G+LBA6IsV+3MYFC5Ps0 Epf9o7AF7+rNnYjOVZOPEYAgBxTr0kb7QtG4UQyRztn1/WnzSIXOwE0eP 4WXh+vT/Xih1f1MMVd3AZaQzjFa0r0s9slKz7mtso51UJEKuwSz1Pnnd4 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOAgDknBJW/40NJK1egydUbga+DQENgVoXDIV3AhyBFTgUAQEBAQEBAYEKhCQBAQEEAQEBIBE5AQkCEAIBCA4DAwECAwIfBwICAiULFQgIAgQBDQUUiBoNqHSUCAEBAQEBAQEBAQEBAQEBAQEBAQEBAReBIoVRAYR9hDUlGBsHBoJjgUMBBI0FiHcBhRaIAIFWR4NxgyOOQ4NuAR8BAUKCRIE+cYZ2AR8EH4EGAQEB
X-IronPort-AV: E=Sophos;i="5.17,639,1437436800"; d="scan'208";a="34603285"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-4.cisco.com with ESMTP; 05 Oct 2015 15:57:23 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t95FvKnN003267 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 5 Oct 2015 15:57:22 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 5 Oct 2015 10:57:20 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1104.000; Mon, 5 Oct 2015 10:57:20 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Fernando Gont <fgont@si6networks.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
Thread-Index: AQHQ71LND9NEJgM1I0iEabKS/qboHJ5do7gA
Date: Mon, 5 Oct 2015 15:57:20 +0000
Message-ID: <D2386149.59FC9%evyncke@cisco.com>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com>
In-Reply-To: <55F76EA7.6090405@si6networks.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.5.150821
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.138.46]
Content-Type: text/plain; charset="utf-8"
Content-ID: <DD1BA57B1695D24BA46E9F064799130D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/DE_P1NmHADys-q9Moy6qh8EI4CI>
Cc: TSV Area <tsv-area@ietf.org>, "'opsec@ietf.org'" <opsec@ietf.org>, Internet Area <int-area@ietf.org>, tsvwg <tsvwg@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 15:57:52 -0000

RmVybmFuZG8sIEZyZWQgYW5kIFBhdWwsDQoNClNvcnJ5IGZvciBiZWxhdGVkIHJlcGx5LCBoZXJl
IGFyZSBhIGNvdXBsZSBvZiBjb21tZW50czoNCg0KVGhlIHRpdGxlIGlzIGEgbGl0dGxlIGFtYmln
dW91cyBJTUhPIGl0IGlzICJPbiBGaXJld2FsbHMgaW4gU2VjdXJpdHkiDQooYmVjYXVzZSB0aGV5
IGFsc28gYXBwbHkgaW5zaWRlIGFuICdpbnRyYW5ldCcpIG9yICJPbiBGaXJld2FsbHMgaW4NCklu
dGVybmV0IFByb3RvY29sIChJUCkgU2VjdXJpdHkiIG9yICJPbiBmaXJld2FsbHMgYW5kIFNlY3Vy
aXR5IG9mIHRoZQ0KSW50ZXJuZXQiID8NCg0KVGhlIGludHJvZHVjdGlvbiBsb29rcyBtb3JlIGxp
a2UgYW4gaGlzdG9yeSwgc28gc2hvdWxkIHBlcmhhcHMgYmUgcmVuYW1lZD8NCg0KVGVybWlub2xv
Z3kgc2VjdGlvbiBzaG91bGQgcGVyaGFwcyBhcHBlYXIgbW9yZSBsaWtlIGFuIHVzdWFsIHRlcm1p
bm9sb2d5DQpzZWN0aW9uIGFuZCBub3QgYXMgYSBmcmVlLWZvcm0gdGV4dD8NCg0KU2VjdGlvbiAz
LjIgKGVuZCB0byBlbmQgcHJpbmNpcGxlKSBpcyBpbnRlcmVzdGluZyBidXQgaXMgYSBsaXR0bGUg
Y29tcGxleA0KdG8gcmVhZC4NCg0KU2VjdGlvbiAzLjMsIHVuc3VyZSB3aGV0aGVyIEkgYW0gcmVh
ZGluZyBpdCBjb3JyZWN0bHkgYnV0IEkgZG9uJ3QgYWdyZWUNCndpdGggdGhlIHN0YXRlbWVudCB0
aGF0IGZpcmV3YWxsIGNhbiBwcm90ZWN0IHRoZSAobmV0d29yaykgaW5mcmFzdHJ1Y3R1cmUNCmFn
YWluc3QgRG9TIGF0dGFjayAoYXMgaGludGVkIGJ5ICJtZXNzYWdlIHZvbHVtZSBvdmVyd2hlbG1z
IikuIFJhdGUNCmxpbWl0ZXJzIG9yIERvUyBzY3J1YmJpbmcgZGV2aWNlcyBkbyBub3QgcXVhbGlm
eSBhcyAnZmlyZXdhbGwnIElNSE8uDQoNCkkgdGhpbmsgc2VjdGlvbiAzLjQgKGEgZ29vZCBvbmUp
IHJhdGhlciBiZWxvbmdzIHRvIHNlY3Rpb24gNCBhbmQgc2hvdWxkDQphbGlnbiB0aGUgdGF4b25v
bXkuDQoNClNlY3Rpb24gNC4xLCBzcGxpdCB0aGUgZmlyc3QgcGFyYWdyYXBoIGluIHR3byBwYXJ0
cy4gVGhlIHNlY29uZCBvbmUgYmVpbmcNCnRoZSBleGFtcGxlIGdpdmVuID0+IHRvIG1ha2UgaXQg
Y2xlYXIgdGhhdCB0aGUgInNlc3Npb25zIG1heSBuZXZlciBiZQ0KaW5pdGlhdGVkIGZyb20gdGhl
IG91dHNpZGUiIGJlbG9uZ3MgdG8gdGhlIGV4YW1wbGUgb25seQ0KDQpTZWN0aW9uIDQuMSwgMm5k
IHBhcmFncmFwaCwgdGhlIHdvcmQgJ3Rlc3RpbmcnIGhhcyBhbiBhY3RpdmUgdG9uZSBpbiBteQ0K
KG5vbiBuYXRpdmUpIEVuZ2xpc2gsIHdoeSBub3QgdXNpbmcgYSBtb3JlIHBhc3NpdmUgdmVyYiBz
dWNoIGFzICJpbnNwZWN0Ig0Kb3IgImNoZWNrIiA/DQoNClNlY3Rpb24gNC4xLCBhdCB0aGUgcmlz
ayBvZiBhcHBlYXJpbmcgYXMgJ3B1cmlzdCcsIEkgd291bGQgbW92ZSB0aGUgTkFUDQpzZWN0aW9u
IGZyb20gdGhpcyBzZWN0aW9uIGFuZCBjcmVhdGUgb25lIG9uIHRoaXMgdG9waWMuDQoNClNlY3Rp
b24gNC4yLCBvciByYXRoZXIgdGhlIHBlcmltZXRlciBleGlzdHMgYnV0IGl0IHZlcnkgdmVyeSBz
bWFsbCA6IG9uZQ0KcGh5c2ljYWwgbGluayA6LSkgb3Igd2lkZXI6IG9uZSBsb2dpY2FsIHBlcmlt
ZXRlciB3aXRob3V0IGFueSBzdHJpY3QNCmdlb2dyYXBoaWNhbCBib3VuZGFyaWVzLg0KDQpTZWN0
aW9uIDQuMiwgc2hvdWxkIG1ha2UgaXQgY2xlYXIgdGhhdCB0aGUgJ3RhZ2dpbmcnIGlzIHJlcXVp
cmVkIChiZWluZw0KSUVFRSA4MDIuMVEgVkxBTiB0YWcgb3IgLi4uKSwgYW5kLCB0aGUgZW5kIG9m
IHRoZSBzZWN0aW9uIGlzIHJhdGhlcg0KbmVnYXRpdmUgb24gdGhpcyBzcGVjaWZpYyBGVy4NCg0K
U2VjdGlvbiA0LjMsIEkgbGlrZSBpdCBvZiBjb3Vyc2UgOi0pLCBhbmQgSSBhZ3JlZSB0aGVyZSBh
cmUgbm93IHNjYWxhYmxlDQphbGdvcml0aG0gdG8gZGV0ZWN0IGFub21hbGllcyBldmVuIHdpdGgg
YSBzaW5nbGUgbm9kZSAodGhhbmtzIHRvDQpzZWxmLWxlYXJuaW5nIDotKSkNCg0KU2VjdGlvbiA0
LjMsICJSZXB1dGF0aW9uIGRhdGFiYXNlcyBoYXZlIGEgYmFkIHJlcHV0YXRpb24iIGlzIGEgZnVu
DQpzZW50ZW5jZSA6LSkNCg0KU2VjdGlvbiA1LCBJIHdvdWxkIGFsc28gdXNlIHRoZSB3b3JkcyBv
ZiB3aGl0ZSBhbmQgYmxhY2sgbGlzdHMgYXMgdGhleSBhcmUNCndlbGwta25vd24uIEkgd29uZGVy
IGFsc28gd2h5IHRoZXJlIGlzIGEgc3BlY2lmaWMgc2VjdGlvbiA1LjEgd2l0aG91dCBhDQpzZWN0
aW9uIDUuMj8gSSB3b3VsZCByZW1vdmUgdGhpcyBoZWFkaW5nIGFuZCBrZWVwIHRoZSB0ZXh0LiBE
b24ndCBmb3JnZXQNCnRvIG1lbnRpb24gSFRUUCAyLjAgJiB3b3JrcyBzdWNoIGFzIFFVSUMuDQoN
ClNlY3Rpb24gNiwgc2hvdWxkIGFsc28gbWVudGlvbiB0aGF0IEZUUCAmIFNJUCBjYW4gYmUgdXNl
ZCBmb3IgZHluYW1pYw0KcG9ydHMuIEl0IHNob3VsZCBhbHNvIG1lbnRpb24vcmVwZWF0IHRoYXQg
cG9ydCA4MCBpcyBub3Qgb25seSBhYm91dCBIVFRQDQpidXQgZm9yIG1hbnkgcHJvdG9jb2xzICd0
dW5uZWxlZCcgb3ZlciBIVFRQLg0KDQpTZWN0aW9uIDYsIHRlbXBvcmFyeSBhZGRyZXNzZXMgYXJl
IGluZGVlZCBhbm5veWluZyBpbiBzb21lIGNhc2VzIGJ1dCBJUA0KYWRkcmVzc2VzIGNhbiBhbHNv
IGJlIHNwb29mZWQuIFNob3VsZCBtZW50aW9uIGFudGktc3Bvb2Zpbmc/IEFuZC9vciBJUFNFQw0K
QUg/DQoNClNlY3Rpb24gNyBpcyBhYm91dCBsYXllci0zL2xheWVyLTQgJ3BhY2tldCBmaWx0ZXJp
bmcnIHdoaWNoIGlzIGEgc3BlY2lmaWMNCmtpbmQgb2YgZmlyZXdhbGxzIHdoaWxlIHRoZSBJLUQg
dGl0bGUgYXBwZWFycyB0byBiZSBtb3JlIGdlbmVyaWMuIEkNCnN1Z2dlc3QgdG8ga2VlcCB0aGUg
c2VjdGlvbiBidXQgbWFrZSB0aXRsZSBtb3JlIHNwZWNpZmljIGFuZCBhZGQgc29tZQ0KaW50cm9k
dWN0aW9uIHNlbnRlbmNlcyB0byB0aGlzIHNlY3Rpb24uDQoNClNlY3Rpb24gNywgSSBsaWtlIHRo
ZSBwb2ludCBhYm91dCBGVyBiZWNvbWluZyB0aGUgRG9TIDotKSAod2hpY2ggaXMgcGxhaW4NCnRy
dWUpLiANCg0KU2VjdGlvbiA4LCBraW5kIG9mIHJlcGVhdHMgYSBmb3JtZXIgcG9pbnQuLi4gVXNl
ZnVsIHRleHQgYnV0IHNob3VsZCB1bmlmeQ0KYW5kIGF0IGEgc2luZ2xlIGxvY2F0aW9uDQoNClNl
Y3Rpb24gMTAgaXMgb2YgY291cnNlIGxvb2tpbmcgZm9yIGhlYXRlZCBjb21tZW50cyBmcm9tIHRo
ZSBjb21tdW5pdHkuLi4NCkhlcmUgYXJlIGEgY291cGxlOg0KLSB3b25kZXIgd2hldGhlciB0aGUg
SUVURiBjb3VsZCBoYXZlIHJlY29tbWVuZGF0aW9ucyBmb3IgYWxsIGNhc2VzPw0KTW9yZW92ZXIs
IHNpdHVhdGlvbiB3aWxsIHByb2JhYmx5IGNvbnRpbnVlIHRvIGV2b2x2ZQ0KLSB6b25lLWJhc2Vk
IHNob3VsZCBhbHNvIGFsbG93IElDTVAgaW5ib3VuZCA7LSkNCi0gZG8gd2UgcmVhbGx5IHdhbnQg
dG8gdHJ1c3QgUENQPw0KLSByb2xlLWJhc2VkLCB0aGUgcm91dGluZyB0ZWNobmlxdWUgaXMgaW50
cm9kdWNlIG5vdyBhbmQgbm90IHByZXZpb3VzbHk/DQotIHRoZSByb3V0aW5nIHRlY2huaXF1ZSB3
b3VsZCBwcm9iYWJseSBiZSBjb21wbGV4IHRvIGludHJvZHVjZSBhbmQgaGF2ZQ0Kc29tZSBzY2Fs
aW5nIGxpbWl0Pw0KDQpUaGVyZSBhcmUgYWxzbyBpbXBvcnRhbnQgKElNSE8pIHRvcGljcyBNSVNT
SU5HOg0KLSBtb3JlIGFuZCBtb3JlIHRyYWZmaWMgYXJlIGVuY3J5cHRlZCwgZ29vZCBmb3IgcHJp
dmFjeSwgYmFkIGZvciBmaXJld2FsbHMNCmFzIHRoZXkgYXJlIGJsaW5kIG5vdyBhbmQgbW9zdGx5
IHVzZWxlc3MNCi0gcmVjb21tZW5kYXRpb24gZm9yIE5PVCBCTE9DS0lORyB0cmFmZmljIG92ZXIg
dGhlIEludGVybmV0IChleGNlcHQgdG8NCmVhY2ggSVNQIG93biBpbmZyYXN0cnVjdHVyZSk/DQot
IGxvZ2dpbmcgLyBhdWRpdGluZyBmdW5jdGlvbiBpcyBtaXNzaW5nICh0YWxraW5nIGFib3V0IHNl
Y3VyaXR5IGhlcmUpDQotIGxvZ2dpbmcgb2YgZXZlbnQgaXMgbWlzc2luZyAodGFsa2luZyBhYm91
dCBvcGVyYXRpb24gaGVyZSkNCg0KSG9wZSB0aGlzIGhlbHBzIHRvIGltcHJvdmUgdGhpcyAtMDAg
dmVyc2lvbiB3aGljaCBpcyBhbHJlYWR5IHF1aXRlIGNvbXBsZXRlDQoNCi3DqXJpYw0KDQoNCg0K
DQoNCg0KDQoNCg0KT24gMTUvMDkvMTUgMDM6MDQsICJPUFNFQyBvbiBiZWhhbGYgb2YgRmVybmFu
ZG8gR29udCINCjxvcHNlYy1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBmZ29udEBzaTZu
ZXR3b3Jrcy5jb20+IHdyb3RlOg0KDQo+Rm9sa3MsDQo+DQo+V2UgaGF2ZSBwdWJsaXNoZWQgYW4g
SS1EIGVudGl0bGVkICJPbiBGaXJld2FsbHMgaW4gSW50ZXJuZXQgU2VjdXJpdHkiLg0KPlRoZSBJ
LUQgaXMgYXZhaWxhYmxlIGF0Og0KPjxodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtZ29udC1vcHNhd2ctZmlyZXdhbGxzLWFuYWx5c2lzDQo+LTAwLnR4dD4uDQo+DQo+
T3VyIEktRCBjb3ZlcnMgYSBicm9hZCByYW5nZSBvZiB0b3BpY3MgKHJhbmdpbmcgZnJvbSBvcGVy
YXRpb25zIHRvDQo+aW50ZXJuZXQgYW5kIHRyYW5zcG9ydCBhcmVhIHRvcGljcykgLS0gaGVuY2Ug
dGhlIGNyb3NzcG9zdCBvZiB0aGlzDQo+YW5ub3VuY2VtZW50IHRvIG11bHRpcGxlIG1haWxpbmct
bGlzdHMuDQo+DQo+V2hpbGUgd2UgKGNvLWF1dGhvcnMpIGFyZSBzdWJzY3JpYmVkIHRvIG1vc3Qg
b2YgdGhlIGxpc3RzIHRvIHdoaWNoIHRoaXMNCj5hbm5vdW5jZW1lbnQgaXMgYmVpbmcgY3Jvc3Nw
b3N0ZWQsIHdlIGV4cGVjdCAoZm9yIHRoZSBzYWtlIG9mIHVuaWZ5aW5nDQo+dGhlIGRpc2N1c3Np
b24gaW4gYSBzaW5nbGUgcGxhY2UpIHRoZSBkaXNjdXNzaW9uIHRvIGhhcHBlbiBpbiB0aGUNCj5v
cHNhd2dAaWV0Zi5vcmcgbWFpbGluZy1saXN0Lg0KPg0KPllvdXIgZmVlZGJhY2sgd2lsbCBiZSB2
ZXJ5IHdlbGNvbWUuDQo+DQo+VGhhbmtzIQ0KPg0KPkJlc3QgcmVnYXJkcywNCj5GZXJuYW5kbw0K
Pg0KPg0KPg0KPg0KPi0tLS0tLS0tIEZvcndhcmRlZCBNZXNzYWdlIC0tLS0tLS0tDQo+U3ViamVj
dDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPmRyYWZ0LWdvbnQtb3BzYXdnLWZpcmV3
YWxscy1hbmFseXNpcy0wMC50eHQNCj5EYXRlOiBNb24sIDE0IFNlcCAyMDE1IDE3OjQ5OjQxIC0w
NzAwDQo+RnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnDQo+VG86IFBhdWwgRS4gSG9mZm1h
biA8cGF1bC5ob2ZmbWFuQHZwbmMub3JnPiwgRmVybmFuZG8gR29udA0KPjxmZ29udEBzaTZuZXR3
b3Jrcy5jb20+LCBGZXJuYW5kbyBHb250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+LCBGcmVkDQo+
QmFrZXIgPGZyZWRAY2lzY28uY29tPiwgRnJlZCBCYWtlciA8ZnJlZEBjaXNjby5jb20+LCBQYXVs
IEhvZmZtYW4NCj48cGF1bC5ob2ZmbWFuQHZwbmMub3JnPg0KPg0KPg0KPkEgbmV3IHZlcnNpb24g
b2YgSS1ELCBkcmFmdC1nb250LW9wc2F3Zy1maXJld2FsbHMtYW5hbHlzaXMtMDAudHh0DQo+aGFz
IGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBGZXJuYW5kbyBHb250IGFuZCBwb3N0ZWQg
dG8gdGhlDQo+SUVURiByZXBvc2l0b3J5Lg0KPg0KPk5hbWU6CQlkcmFmdC1nb250LW9wc2F3Zy1m
aXJld2FsbHMtYW5hbHlzaXMNCj5SZXZpc2lvbjoJMDANCj5UaXRsZToJCU9uIEZpcmV3YWxscyBp
biBJbnRlcm5ldCBTZWN1cml0eQ0KPkRvY3VtZW50IGRhdGU6CTIwMTUtMDktMTUNCj5Hcm91cDoJ
CUluZGl2aWR1YWwgU3VibWlzc2lvbg0KPlBhZ2VzOgkJMTcNCj5VUkw6DQo+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWdvbnQtb3BzYXdnLWZpcmV3YWxscy1hbmFs
eXNpcy0NCj4wMC50eHQNCj5TdGF0dXM6DQo+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtZ29udC1vcHNhd2ctZmlyZXdhbGxzLWFuYWx5c2lzLw0KPkh0bWxpemVkOg0KPmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1nb250LW9wc2F3Zy1maXJld2FsbHMtYW5h
bHlzaXMtMDANCj4NCj4NCj5BYnN0cmFjdDoNCj4gICBUaGlzIGRvY3VtZW50IGFuYWx5emVzIHRo
ZSByb2xlIG9mIGZpcmV3YWxscyBpbiBJbnRlcm5ldCBzZWN1cml0eSwNCj4gICBhbmQgc3VnZ2Vz
dHMgYSBsaW5lIG9mIHJlYXNvbmluZyBhYm91dCB0aGVpciB1c2FnZS4gIEl0IGFuYWx5emVzDQo+
ICAgY29tbW9uIGtpbmRzIG9mIGZpcmV3YWxscyBhbmQgdGhlIGNsYWltcyBtYWRlIGZvciB0aGVt
Lg0KPg0KPg0KPg0KPg0KPg0KPlBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUg
b2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+c3VibWlzc2lvbg0KPnVudGlsIHRoZSBodG1s
aXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+
DQo+VGhlIElFVEYgU2VjcmV0YXJpYXQNCj4NCj4NCj4NCj4NCj5fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPk9QU0VDIG1haWxpbmcgbGlzdA0KPk9QU0VD
QGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHNlYw0K
DQo=


From nobody Mon Oct  5 13:01:51 2015
Return-Path: <wtackabury@us.ibm.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED4F1B4F86 for <opsawg@ietfa.amsl.com>; Mon,  5 Oct 2015 13:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.108
X-Spam-Level: 
X-Spam-Status: No, score=-3.108 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MSGID_FROM_MTA_HEADER=0.001, 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 T6pXy69erX_Z for <opsawg@ietfa.amsl.com>; Mon,  5 Oct 2015 13:01:48 -0700 (PDT)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9A801B4F88 for <opsawg@ietf.org>; Mon,  5 Oct 2015 13:01:47 -0700 (PDT)
Received: from localhost by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <opsawg@ietf.org> from <wtackabury@us.ibm.com>; Mon, 5 Oct 2015 14:01:47 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 5 Oct 2015 14:01:37 -0600
X-IBM-Helo: d03dlp03.boulder.ibm.com
X-IBM-MailFrom: wtackabury@us.ibm.com
X-IBM-RcptTo: opsawg@ietf.org
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 1FB7F19D803F for <opsawg@ietf.org>; Mon,  5 Oct 2015 13:49:49 -0600 (MDT)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by b03cxnp08025.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t95K0LFv63701096 for <opsawg@ietf.org>; Mon, 5 Oct 2015 13:00:21 -0700
Received: from d03av01.boulder.ibm.com (localhost [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t95K1ZJ4009225 for <opsawg@ietf.org>; Mon, 5 Oct 2015 14:01:35 -0600
Received: from d50lp02.ny.us.ibm.com (d50lp02.pok.ibm.com [146.89.104.208]) by d03av01.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id t95K1Xhu008944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <opsawg@ietf.org>; Mon, 5 Oct 2015 14:01:34 -0600
Message-Id: <201510052001.t95K1Xhu008944@d03av01.boulder.ibm.com>
Received: from /spool/local by d50lp02.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <opsawg@ietf.org> from <wtackabury@us.ibm.com>; Mon, 5 Oct 2015 16:01:30 -0400
Received: from smtp.notes.na.collabserv.com (192.155.248.67) by d50lp02.ny.us.ibm.com (158.87.18.21) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256/256) Mon, 5 Oct 2015 16:01:27 -0400
Received: from /spool/local by smtp.notes.na.collabserv.com with smtp.notes.na.collabserv.com ESMTP for <opsawg@ietf.org> from <wtackabury@us.ibm.com>; Mon, 5 Oct 2015 20:01:26 -0000
Received: from us1a3-smtp01.a3.dal06.isc4sb.com (10.106.154.100) by smtp.notes.na.collabserv.com (10.106.227.16) with smtp.notes.na.collabserv.com ESMTP; Mon, 5 Oct 2015 20:00:52 -0000
Received: from us1a3-mail64.a3.dal09.isc4sb.com ([10.142.3.135]) by us1a3-smtp01.a3.dal06.isc4sb.com with ESMTP id 2015100520011256-505146 ; Mon, 5 Oct 2015 20:01:12 +0000 
In-Reply-To: 
From: "Wayne Tackabury" <wtackabury@us.ibm.com>
To: opsawg@ietf.org
Date: Mon, 5 Oct 2015 20:00:51 +0000
Sensitivity: 
References: 
MIME-Version: 1.0
Importance: Normal
X-Priority: 3 (Normal)
X-Mailer: Lotus Domino Web Server Build V851SAAS_09212015_FP3 September 28, 2015
X-LLNOutbound: False
X-Disclaimed: 65195
X-TNEFEvaluated: 1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
x-cbid: 15100520-0017-0000-0000-00000E64B7AA
X-IBM-ISS-SpamDetectors: Score=0.40304; BY=0; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.40304; ST=0; TS=0; UL=0; ISC=
X-IBM-ISS-DetailInfo: BY=3.00004472; HX=3.00000236; KW=3.00000007; PH=3.00000004; SC=3.00000117; SDB=6.00598493; UDB=6.00262312; UTC=2015-10-05 20:01:25
x-cbparentid: 15100520-5938-0000-0000-00000076441D
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/cgkmS-rDFafGm618VMinQW1eseo>
Cc: paitken@brocade.com
Subject: [OPSAWG] A proposal  on draft-aitken-ipfix-unobserved-fields
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 20:01:50 -0000

<div class=3D"socmaildefaultfont" dir=3D"ltr" style=3D"font-family:Arial;fo=
nt-size:10.5pt" ><div class=3D"socmaildefaultfont" dir=3D"ltr" style=3D"fon=
t-family:Arial;font-size:10.5pt" ><div dir=3D"ltr" >Hi all:</div>
<div dir=3D"ltr" >&nbsp;</div>
<div dir=3D"ltr" >In work we are doing here, we have found rather compellin=
g value, to put it mildly, in the scope and techniques which are covered in=
 a draft which was submitted to the now-closed IPFIX working group, &nbsp;d=
raft-aitken-ipfix-unobserved-fields.&nbsp; Its latest manifestation (as a -=
.03 rev) is to be found at <a href=3D"https://datatracker.ietf.org/doc/draf=
t-aitken-ipfix-unobserved-fields/" >https://datatracker.ietf.org/doc/draft-=
aitken-ipfix-unobserved-fields/</a>.</div>
<div dir=3D"ltr" >&nbsp;</div>
<div dir=3D"ltr" >This was submitting when the wg was in its closing throes=
.&nbsp; HIstory from the list was unearthed by Paul Aitken indicating that =
the draft has value, but had not yet received sufficient list commentary to=
 move forward, at the exact moment that wg closure was sought.</div>
<div dir=3D"ltr" >&nbsp;</div>
<div dir=3D"ltr" >I have reached out to that original author and the wg cha=
ir, Benoit Claise, who is an active member of this area wg as well of cours=
e.&nbsp; Benoit recommended that in the current state of the IPFIX wg, that=
 I approach this area wg with an interest in revival and refinement of this=
 draft (which I am willing to particpate in), with an eye towards its event=
ual elevation to be a companion to the other Proposed Standard RFCs produce=
d by the IPFIX WG.</div>
<div dir=3D"ltr" >&nbsp;</div>
<div dir=3D"ltr" >It is in that spirit I submit this post, I hope my protoc=
ol of approach is in order.&nbsp; If there is another viable strategy for e=
levation of this draft than wg reactivation, please let me know.</div>
<div dir=3D"ltr" >&nbsp;</div>
<div dir=3D"ltr" >Thanks in advance,</div>
<div dir=3D"ltr" >&nbsp;</div>
<div dir=3D"ltr" >Wayne Tackabury</div>
<div dir=3D"ltr" >IBM Security Systems</div>
<div dir=3D"ltr" >&nbsp;</div></div></div><BR>


From nobody Mon Oct  5 13:17:57 2015
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58DD41B4F94 for <opsawg@ietfa.amsl.com>; Mon,  5 Oct 2015 13:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, 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 E68600lAbVgH for <opsawg@ietfa.amsl.com>; Mon,  5 Oct 2015 13:17:51 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F5941B4F93 for <opsawg@ietf.org>; Mon,  5 Oct 2015 13:17:51 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id DD08EE7C; Mon,  5 Oct 2015 22:17:49 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id p9eWhNn3Dwtk; Mon,  5 Oct 2015 22:17:48 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Mon,  5 Oct 2015 22:17:48 +0200 (CEST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id A8EC320053; Mon,  5 Oct 2015 22:17:48 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id HXIdnLUr4wZL; Mon,  5 Oct 2015 22:17:47 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 14D7E2004E; Mon,  5 Oct 2015 22:17:46 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id F3340377D94B; Mon,  5 Oct 2015 22:17:45 +0200 (CEST)
Date: Mon, 5 Oct 2015 22:17:45 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Wayne Tackabury <wtackabury@us.ibm.com>
Message-ID: <20151005201743.GA38729@elstar.local>
Mail-Followup-To: Wayne Tackabury <wtackabury@us.ibm.com>, opsawg@ietf.org, paitken@brocade.com
References: <201510052001.t95K1Xhu008944@d03av01.boulder.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201510052001.t95K1Xhu008944@d03av01.boulder.ibm.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/QHhcNSPd82PrKv9sqhJpa3A7bS0>
Cc: paitken@brocade.com, opsawg@ietf.org
Subject: Re: [OPSAWG] A proposal  on draft-aitken-ipfix-unobserved-fields
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 20:17:54 -0000

Wayne,

I agree that having a well-defined low-complexity mechanism to
indicate that certain values are missing would be valuable. I know
that some exporters simple report 0 for fields they have no value for
and this is really bad (unless 0 has been specifically reserved for
this purpose). So I support work in this space but I won't have much
time to be involved.

PS: We had a similar problem in SNMP land where agents reported 0 for
    counters they did not support and it has been effort to convince
    people to not report values for object instances that do not have
    a value; part of the problem were poorly written SNMP managers
    that could not deal with missing values. A good solution will be
    incrementally deployable, allowing those who care to do the right
    thing and those who prefer to not care to stay simple minded about
    null values (until they start to care).

On Mon, Oct 05, 2015 at 08:00:51PM +0000, Wayne Tackabury wrote:
>    Hi all:
> 
>    In work we are doing here, we have found rather compelling value, to put
>    it mildly, in the scope and techniques which are covered in a draft which
>    was submitted to the now-closed IPFIX working group,
>     draft-aitken-ipfix-unobserved-fields.  Its latest manifestation (as a
>    -.03 rev) is to be found at
>    [1]https://datatracker.ietf.org/doc/draft-aitken-ipfix-unobserved-fields/.
> 
>    This was submitting when the wg was in its closing throes.  HIstory from
>    the list was unearthed by Paul Aitken indicating that the draft has value,
>    but had not yet received sufficient list commentary to move forward, at
>    the exact moment that wg closure was sought.
> 
>    I have reached out to that original author and the wg chair, Benoit
>    Claise, who is an active member of this area wg as well of course.  Benoit
>    recommended that in the current state of the IPFIX wg, that I approach
>    this area wg with an interest in revival and refinement of this draft
>    (which I am willing to particpate in), with an eye towards its eventual
>    elevation to be a companion to the other Proposed Standard RFCs produced
>    by the IPFIX WG.
> 
>    It is in that spirit I submit this post, I hope my protocol of approach is
>    in order.  If there is another viable strategy for elevation of this draft
>    than wg reactivation, please let me know.
> 
>    Thanks in advance,
> 
>    Wayne Tackabury
>    IBM Security Systems
> 
> 
> References
> 
>    Visible links
>    1. https://datatracker.ietf.org/doc/draft-aitken-ipfix-unobserved-fields/

> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Wed Oct  7 10:22:24 2015
Return-Path: <warren@kumari.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDED61A00B2 for <opsawg@ietfa.amsl.com>; Wed,  7 Oct 2015 05:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.578
X-Spam-Level: 
X-Spam-Status: No, score=-0.578 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 LSO7WoTiRfpG for <opsawg@ietfa.amsl.com>; Wed,  7 Oct 2015 05:24:42 -0700 (PDT)
Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71B981A0063 for <opsawg@ietf.org>; Wed,  7 Oct 2015 05:24:33 -0700 (PDT)
Received: by ykdz138 with SMTP id z138so14451988ykd.2 for <opsawg@ietf.org>; Wed, 07 Oct 2015 05:24:32 -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:date:message-id:subject:from:to :content-type; bh=LGxhX+eVDVCpjbkcelOq3Q974OEA7TUo+8axpGJISiA=; b=A1GVnQtOjJoUjDohZM5lUjBogggmxYFiwNauPXqZtEDyG53uw8GT7M5QQsvOM37QBC RtiscOKJ6YPJkzmIdKo5AYlhdaisZe6Vva0n02o6QHn26E9V77EnriFsv1BtGFLyGnPW jyjvzSzREB7kTJ1Ysm1tdK9Bx8ypEWU6PthajCKl3QAxzKV6wCp9P+o/faMIm2o86+U4 C541l4QcgbIEQ1P4ty++nqNCHLc18ME1/3PofL7/DU0a/RO2m6ms4IDcnr9p23Lv1koP e8IhsqkbYNHvAT1GNAo9qAFmpD/6yaK9cy5fLkPFBz1IhsuN62minjDg2y8p4+zyZxyW /eUw==
X-Gm-Message-State: ALoCoQktAu9LdO1GLAfDR1QpUjjb+XsoQ28b+uCckcnutxTGSH29zfHxa/Sa9eMHV3/A0XkKgpgY
MIME-Version: 1.0
X-Received: by 10.13.216.65 with SMTP id a62mr501889ywe.109.1444220672585; Wed, 07 Oct 2015 05:24:32 -0700 (PDT)
Received: by 10.37.124.69 with HTTP; Wed, 7 Oct 2015 05:24:32 -0700 (PDT)
Date: Wed, 7 Oct 2015 08:24:32 -0400
Message-ID: <CAHw9_iL6rEONKDGz02Le9nt8NyhRKDEm=GT9AFkqpprdUme3SA@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/2np_uSVBzO0p1dp7Ce52uVHG56c>
Subject: [OPSAWG] Call for agenda items for IETF94 - Yokohama.
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Oct 2015 12:24:44 -0000

Dear WG,


This is a reminder that we will be having a joint WG session with Ops Area.

Please send in requests for agenda time.

We give priority to documents that have been discussed and have open
isses, which are not able to get to consensus on the list / would
benefit from in person back nad forth...

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 Fri Oct  9 03:25:51 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498151A8AAE; Fri,  9 Oct 2015 03:25:45 -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 78aoGP_iibxw; Fri,  9 Oct 2015 03:25:42 -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 287FF1A8AAD; Fri,  9 Oct 2015 03:25:41 -0700 (PDT)
Received: from 17-182-245-190.fibertel.com.ar ([190.245.182.17] 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 1ZkUrl-0005m9-HF; Fri, 09 Oct 2015 12:25:34 +0200
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56179631.8060803@si6networks.com>
Date: Fri, 9 Oct 2015 07:25:53 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <D2386149.59FC9%evyncke@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/9J3dTKznmz5Gn3gCbyAzfw7tZZs>
Cc: IPv6 Operations <v6ops@ietf.org>, Internet Area <int-area@ietf.org>, tsvwg <tsvwg@ietf.org>, draft-gont-opsawg-firewalls-analysis@tools.ietf.org, "'opsec@ietf.org'" <opsec@ietf.org>, TSV Area <tsv-area@ietf.org>
Subject: Re: [OPSAWG] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2015 10:25:45 -0000

Hi, Eric,

Thanks so much for your feedback! Please find my comments in-line....


On 10/05/2015 12:57 PM, Eric Vyncke (evyncke) wrote:
> Fernando, Fred and Paul,
> 
> Sorry for belated reply, here are a couple of comments:
> 
> The title is a little ambiguous IMHO it is "On Firewalls in Security"
> (because they also apply inside an 'intranet') or "On Firewalls in
> Internet Protocol (IP) Security" or "On firewalls and Security of the
> Internet" ?

How about "On Firewalls in Network Security"?


> The introduction looks more like an history, so should perhaps be renamed?

How about splitting the historical part into a stand-alone section
renamed as "Firewalls in the IETF" or the like?



> Terminology section should perhaps appear more like an usual terminology
> section and not as a free-form text?

mm.. I guess that from the current contents we can define "firewall" and
"perimeter"?



> Section 3.2 (end to end principle) is interesting but is a little complex
> to read.

Any suggestions on how to improve the text?



> Section 3.3, unsure whether I am reading it correctly but I don't agree
> with the statement that firewall can protect the (network) infrastructure
> against DoS attack (as hinted by "message volume overwhelms"). Rate
> limiters or DoS scrubbing devices do not qualify as 'firewall' IMHO.

Could you elaborate a bit?  e.g., why wouldn't a rate-limited qualify as
a firewall?



> I think section 3.4 (a good one) rather belongs to section 4 and should
> align the taxonomy.

Yep. Looks like we could move this into the base Section 4. (Or were you
meaning something else?)




> Section 4.1, split the first paragraph in two parts. The second one being
> the example given => to make it clear that the "sessions may never be
> initiated from the outside" belongs to the example only

OK, will do.



> Section 4.1, 2nd paragraph, the word 'testing' has an active tone in my
> (non native) English, why not using a more passive verb such as "inspect"
> or "check" ?

Agreed. Will do.



> Section 4.1, at the risk of appearing as 'purist', I would move the NAT
> section from this section and create one on this topic.

Please let me think about this one. f you have any suggestions regarding
whre in the I-D you'd put such a section, please let me know.



> Section 4.2, or rather the perimeter exists but it very very small : one
> physical link :-) or wider: one logical perimeter without any strict
> geographical boundaries.

Yes. :-)



> Section 4.2, should make it clear that the 'tagging' is required (being
> IEEE 802.1Q VLAN tag or ...),

OK.


> and, the end of the section is rather
> negative on this specific FW.

I see... any hints for improvement?



> Section 4.3, I like it of course :-), and I agree there are now scalable
> algorithm to detect anomalies even with a single node (thanks to
> self-learning :-))

Could you elaborate a bit? :-)




> Section 4.3, "Reputation databases have a bad reputation" is a fun
> sentence :-)

Indeed! :-)



> Section 5, I would also use the words of white and black lists as they are
> well-known. I wonder also why there is a specific section 5.1 without a
> section 5.2? 

Section 5.2 was forthcomming... (will hopefuly be there in version -01
of the I-D)


> I would remove this heading and keep the text. Don't forget
> to mention HTTP 2.0 & works such as QUIC.

Will do.



> Section 6, should also mention that FTP & SIP can be used for dynamic
> ports.

Will do.


> It should also mention/repeat that port 80 is not only about HTTP
> but for many protocols 'tunneled' over HTTP.

Will do.



> Section 6, temporary addresses are indeed annoying in some cases but IP
> addresses can also be spoofed.

What we meant here is that things like IPv6 temporary addresses change
such assumption.


But yes, we should comment on spoofing.


> Should mention anti-spoofing? And/or IPSEC
> AH?

Anti spoofing in terms of RPF, or something else?



> Section 7 is about layer-3/layer-4 'packet filtering' which is a specific
> kind of firewalls while the I-D title appears to be more generic. I
> suggest to keep the section but make title more specific and add some
> introduction sentences to this section.

Good grief! Will do.




> Section 8, kind of repeats a former point... Useful text but should unify
> and at a single location

You mean with Section 4.1?





> Section 10 is of course looking for heated comments from the community...

[FWIW, Section 10 will be split into a different document... such that
the heat happens elsewhere :-) ]


> Here are a couple:
> - wonder whether the IETF could have recommendations for all cases?

Certainly not for all -- but better to have something covered, than
nothing :-)


> Moreover, situation will probably continue to evolve
> - zone-based should also allow ICMP inbound ;-)

.... if they relate to an ongoing session?




> There are also important (IMHO) topics MISSING:
> - more and more traffic are encrypted, good for privacy, bad for firewalls
> as they are blind now and mostly useless

Yes and no.

If you mean TLS, it prevents DPI, but still allows for filtering based
on port numbers...


> - recommendation for NOT BLOCKING traffic over the Internet (except to
> each ISP own infrastructure)?

not blocking which sort of traffic?


> - logging / auditing function is missing (talking about security here)
> - logging of event is missing (talking about operation here)

Do you mean in the recommendations section, or elsewhere?

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 Fri Oct  9 05:24:55 2015
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 546BB1B3AB3; Fri,  9 Oct 2015 05:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_LOW=-0.7, 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 OItdfJv9d0oP; Fri,  9 Oct 2015 05:24:49 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF7FA1B3AB1; Fri,  9 Oct 2015 05:24:49 -0700 (PDT)
Received: from [192.168.10.203] ([131.171.200.169]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MV5hN-1a7Nk93j3d-00YV2f; Fri, 09 Oct 2015 14:24:45 +0200
To: Fernando Gont <fgont@si6networks.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com> <56179631.8060803@si6networks.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
X-Enigmail-Draft-Status: N1110
Message-ID: <5617B205.5030004@gmx.net>
Date: Fri, 9 Oct 2015 14:24:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <56179631.8060803@si6networks.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="T6GxDuM0cmKqW3APrO8F3OExgVdUa25n5"
X-Provags-ID: V03:K0:BN75GeL5RZhMIFU8yhB7HThUK4Ex2HxWtXlgR6V6lnniR08MXzv yiTYNtK0LhaU/+WOFb1JNCMQBT9d8l6EDmDRJQVugzAQRBKn0WCH0xE0qWHsfXdxQg4VWMU mFbBTG+uO2okOj3ZcEhOYJIKkRJIx4rjTbZ0cFgKqG54MR2w3VWu7gyTHSqA8Xn5XWQ0IkY o2crQNs8d/h5RuW2JuctQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:mFVi/bH4GdE=:1sgbPpUzZJDIlTGH9s18D9 cjkQjj25dD+wwUICP/LE1c78WMHxvyXBblIiLh+DB/RsVlTvhVNWzYsDshpUwpHCFTbA/L57a A2mzBCizzwJvsntASWooDTShV505AIk7lDahVF2p58f1XsDlFZ8w3nNpXjTn7ZcGqSjz73M3E EBOpDtiIlsCU0SjLGAlcC2XTviEaoIHyJckf1YFPwZnQW2aZyTIkIa6AbRQDVTM8DxRramvj9 H9scUmmcmlZ+cfYueWoOVxOhagP+t/fCT83DBaQ99twn14+L9lwvMoVsodNW2Cf6m1ZpOdQfJ OKhG49H325bXM04GU/QVDPh371slzeOJCAInwL40gAqAu2X7OOJsuNg0HOTUViTP9uFmlTE6s 2IPSCW5Jx9qoiYqxVFYeC+wJEi9yaJx+4KEbA1vYyMNItDuW5pAUvjF+UmCZRNzhvc32Sy3/k k39Pmxj03JPVR5VNNLrDYTsfhNgAgiA5IAN5PhBIv7VzGbkJQACH+RnBpgA7ZL8JqKtsWHLfD J2FAZ2b8+i21JzWmIHta74Z4oJgxfcvUT38Pb4Sv35GQTIl3NQDw6WsR0xx4tgEkQkw9hCUX3 rFQCRRQ6Fh7lYiLRIqmoxsc015X7LPFQsmjSiuQnjwd8CisjVCOJCRRol8f0ONNfQWeQqj0uE TvMrLyg4O65MGg4WARMTJUk5gPov08swbeqD14Sat++RWr169cwR6oFCySgYG968aBUqRnaER f7EG9DoK7OcDfHODyqUvXus16Zaty2IJ+U+ylzQsEy0t4y6R13mw3tWmx54=
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/Iu2NZuqXuNsVF7y8ri-ni-3xQXQ>
Cc: draft-gont-opsawg-firewalls-analysis@tools.ietf.org, Internet Area <int-area@ietf.org>
Subject: Re: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2015 12:24:51 -0000

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

Dear authors,

Who is the target audience for this document?

Do you think that audience cares about your opinion particularly since
firewalls are around for a little while already? (One might argue that
you are about 20 years late with this document.)

Aren't you worried that readers might think you are a bit biased? I
would be more interested to read a document written by an end-host-based
firewall manufacturer that argues for the deployment of network-based
firewalls.

Ciao
Hannes

PS: The recommendations do not appear to be new and have been mentioned
in other documents already.


--T6GxDuM0cmKqW3APrO8F3OExgVdUa25n5
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.0.22 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJWF7IFAAoJEGhJURNOOiAtU4gH/26Ca1en1BZgozRLBTvFZFxO
9ZxHXhDTvkzIw5sRt1ApVILg1sQr4pXGQwNzmlrz53TmuRbC3v78dKOj3IB4k+Xr
hBsSRPFx4rCFdDsy9GFQtNjRDaLUQ8Ewx6In6SDikt2eDHbTU2mFCeZMgpsWp2UP
svqTDcOhf5zxdPTaSVssXAFz8IIQHPlFjElVUCUPqfbP7sSF8jIEOH9uAt9B5MKP
nzcNscDhIOKlovqChiPjIowy985M2GbrCxVig9cRzPqXwa2gRqDJChoK35BLygx5
gV3pIhb3z4YD1RlHnIDH08r5nBroWNeeYt0vUX9JqD594eeKQ1ufmA9iXJRT8qI=
=XHtE
-----END PGP SIGNATURE-----

--T6GxDuM0cmKqW3APrO8F3OExgVdUa25n5--


From nobody Sun Oct 11 17:26:03 2015
Return-Path: <marka@isc.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A931B2F3B; Sun, 11 Oct 2015 17:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.411
X-Spam-Level: 
X-Spam-Status: No, score=-6.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_HI=-5, 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 sTeZGaRQC894; Sun, 11 Oct 2015 17:25:59 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00F7A1B2F39; Sun, 11 Oct 2015 17:25:58 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id C4FC81FCAB9; Mon, 12 Oct 2015 00:25:55 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 88C2F16004B; Mon, 12 Oct 2015 00:25:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 6AA86160059; Mon, 12 Oct 2015 00:25:55 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id in2rmxRXyVLM; Mon, 12 Oct 2015 00:25:55 +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 B713A16004B; Mon, 12 Oct 2015 00:25:54 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 8F7CD3A2FFD8; Mon, 12 Oct 2015 11:25:51 +1100 (EST)
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
From: Mark Andrews <marka@isc.org>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com> <56179631.8060803@si6networks.com> <5617B205.5030004@gmx.net>
In-reply-to: Your message of "Fri, 09 Oct 2015 14:24:37 +0200." <5617B205.5030004@gmx.net>
Date: Mon, 12 Oct 2015 11:25:51 +1100
Message-Id: <20151012002551.8F7CD3A2FFD8@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/2YQl6xBz6jtMyIkyAx59U-oPmPQ>
Cc: draft-gont-opsawg-firewalls-analysis@tools.ietf.org, Internet Area <int-area@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 00:26:00 -0000

In message <5617B205.5030004@gmx.net>, Hannes Tschofenig writes:
> 
> Dear authors,
> 
> Who is the target audience for this document?
> 
> Do you think that audience cares about your opinion particularly since
> firewalls are around for a little while already? (One might argue that
> you are about 20 years late with this document.)
> 
> Aren't you worried that readers might think you are a bit biased? I
> would be more interested to read a document written by an end-host-based
> firewall manufacturer that argues for the deployment of network-based
> firewalls.
> 
> Ciao
> Hannes
> 
> PS: The recommendations do not appear to be new and have been mentioned
> in other documents already.

Lots of the content is pertanent today.  Look at the treatement of
DNS packets in todays firewalls.

It took years to get EDNS packets larger then 512 bytes through
most firewalls by default.  Some still block packets bigger than
512 bytes.

There are firewalls that block queries that are not in a small set
to types.

There are firewalls that block fragmented responses leaving the
site.  Who is the firewall protecting in this case and is it really
the firewall's job to do that protection?

There are firewalls that block fragmented responses to outgoing
queries.  How hard is it to add permit <src-addr,dst-addr,proto=udp,
fragoffset!=0> when adding <src-addr,dst-addr,proto=udp,src-port=53,
dst-port=???> to allow reply traffic through?  Open up a slit for
the non initial fragments.

There are still firewalls that block queries with the DO bit.  This
breaks DNSSSEC.

There are firewalls that block queries with the AD bit.  The use
of AD is documented in RFC 6840.

There are firewalls that block queries with the last reserved DNS
header bit set.  The bit should be ignored by the server.

There are firewalls that block requests with a unknown opcode.  This
should elicit a NOTIMP from the server.

Firewalls are blocking EDNS packets with the version != 0 which
breaks EDNS version negotiation and with that the ability to use
the feature reliably in future enhancements.  This is despite the
initial EDNS specification (RFC 2671) saying to return BADVERS to
such packets.

Firewalls are blocking EDNS packets with unknown EDNS flags despite
the initial EDNS specifiction (RFC 2671) saying that servers need
to ignore them.

Firewall that block unknown EDNS options.  This is going to impact
on the deployment of EDNS COOKIES.  Unknown EDNS options are supposed
to be ignored, RFC 6891.  This behaviour was undefined in RFC2671.

The DNS is a query response protocol.  If you don't get response
it is a little hard to tell if the server is down, if a packet just
got lost, if there is a router down or if it is a stupid firewall
vendor that thinks it is useful to drop well defined queries with
well defined response behaviour specified.

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


From nobody Mon Oct 12 07:01:38 2015
Return-Path: <prvs=77277e3e67=uri@ll.mit.edu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D407E1B326F; Mon, 12 Oct 2015 07:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.709
X-Spam-Level: 
X-Spam-Status: No, score=-3.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, 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 bP3Gs-1PuYJa; Mon, 12 Oct 2015 07:01:35 -0700 (PDT)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 055671B3279; Mon, 12 Oct 2015 07:01:34 -0700 (PDT)
Received: from LLE2K10-HUB02.mitll.ad.local (LLE2K10-HUB02.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id t9CE1Vga029786; Mon, 12 Oct 2015 10:01:31 -0400
From: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
To: Mark Andrews <marka@isc.org>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
Thread-Index: AQHRAo2SjgoyVRd82Ei0b3lm/8gAtJ5nBLfMgADjYoA=
Date: Mon, 12 Oct 2015 14:01:30 +0000
Message-ID: <D24134E9.1DF72%uri@ll.mit.edu>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com> <56179631.8060803@si6networks.com> <5617B205.5030004@gmx.net> <20151012002551.8F7CD3A2FFD8@rock.dv.isc.org>
In-Reply-To: <20151012002551.8F7CD3A2FFD8@rock.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.5.150821
x-originating-ip: [172.26.148.51]
Content-Type: text/plain; charset="utf-8"
Content-ID: <27767B3F7774F84388B4E3FBC79854CB@ll.mit.edu>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33,  0.0.0000 definitions=2015-10-12_08:2015-10-12,2015-10-12,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1510120163
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/5Z_TJ3OIvOs3RmEMPVB9vnJwFCc>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "draft-gont-opsawg-firewalls-analysis@tools.ietf.org" <draft-gont-opsawg-firewalls-analysis@tools.ietf.org>, Internet Area <int-area@ietf.org>
Subject: Re: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 14:01:37 -0000

T24gMTAvMTEvMTUsIDIwOjI1LCAiT1BTQVdHIG9uIGJlaGFsZiBvZiBNYXJrIEFuZHJld3MiDQo8
b3BzYXdnLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIG1hcmthQGlzYy5vcmc+IHdyb3Rl
Og0KDQo+SW4gbWVzc2FnZSA8NTYxN0IyMDUuNTAzMDAwNEBnbXgubmV0PiwgSGFubmVzIFRzY2hv
ZmVuaWcgd3JpdGVzOg0KPj4gDQo+PiBEZWFyIGF1dGhvcnMsDQo+PiANCj4+IFdobyBpcyB0aGUg
dGFyZ2V0IGF1ZGllbmNlIGZvciB0aGlzIGRvY3VtZW50Pw0KPj4gDQo+PiBEbyB5b3UgdGhpbmsg
dGhhdCBhdWRpZW5jZSBjYXJlcyBhYm91dCB5b3VyIG9waW5pb24gcGFydGljdWxhcmx5IHNpbmNl
DQo+PiBmaXJld2FsbHMgYXJlIGFyb3VuZCBmb3IgYSBsaXR0bGUgd2hpbGUgYWxyZWFkeT8gKE9u
ZSBtaWdodCBhcmd1ZSB0aGF0DQo+PiB5b3UgYXJlIGFib3V0IDIwIHllYXJzIGxhdGUgd2l0aCB0
aGlzIGRvY3VtZW50LikNCj4+IA0KPj4gQXJlbid0IHlvdSB3b3JyaWVkIHRoYXQgcmVhZGVycyBt
aWdodCB0aGluayB5b3UgYXJlIGEgYml0IGJpYXNlZD8gSQ0KPj4gd291bGQgYmUgbW9yZSBpbnRl
cmVzdGVkIHRvIHJlYWQgYSBkb2N1bWVudCB3cml0dGVuIGJ5IGFuIGVuZC1ob3N0LWJhc2VkDQo+
PiBmaXJld2FsbCBtYW51ZmFjdHVyZXIgdGhhdCBhcmd1ZXMgZm9yIHRoZSBkZXBsb3ltZW50IG9m
IG5ldHdvcmstYmFzZWQNCj4+IGZpcmV3YWxscy4NCj4+IA0KPj4gQ2lhbw0KPj4gSGFubmVzDQo+
PiANCj4+IFBTOiBUaGUgcmVjb21tZW5kYXRpb25zIGRvIG5vdCBhcHBlYXIgdG8gYmUgbmV3IGFu
ZCBoYXZlIGJlZW4gbWVudGlvbmVkDQo+PiBpbiBvdGhlciBkb2N1bWVudHMgYWxyZWFkeS4NCj4N
Cj5Mb3RzIG9mIHRoZSBjb250ZW50IGlzIHBlcnRhbmVudCB0b2RheS4NCg0KVGhhdOKAmXMgbm90
IGEgZ29vZCByZWFzb24gZm9yIHdyaXRpbmcgYSBuZXcgZG9jdW1lbnQgY29udGFpbmluZyB0aGUg
b2xkDQpyZWNvbW1lbmRhdGlvbnPigKY/DQoNCg==


From nobody Tue Oct 13 06:50:10 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B22591B3F6A; Tue, 13 Oct 2015 06:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, SPF_HELO_PASS=-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 XE_nKKn8fjSE; Tue, 13 Oct 2015 06:50:06 -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 3F4F41B3F70; Tue, 13 Oct 2015 06:50:06 -0700 (PDT)
Received: from 17-182-245-190.fibertel.com.ar ([190.245.182.17] 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 1Zlzxm-0007Tu-IN; Tue, 13 Oct 2015 15:49:58 +0200
From: Fernando Gont <fgont@si6networks.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com> <56179631.8060803@si6networks.com> <5617B205.5030004@gmx.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <561CF54C.5000206@si6networks.com>
Date: Tue, 13 Oct 2015 09:13:00 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5617B205.5030004@gmx.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/1TKPbahxqtyWa7oO0RI-GjImpcA>
Cc: draft-gont-opsawg-firewalls-analysis@tools.ietf.org, Internet Area <int-area@ietf.org>
Subject: Re: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 13:50:08 -0000

Hi, Hannes,

On 10/09/2015 09:24 AM, Hannes Tschofenig wrote:
> 
> Who is the target audience for this document?

Everyone that may care about firewalls and/or their implications.



> Do you think that audience cares about your opinion particularly since
> firewalls are around for a little while already? (One might argue that
> you are about 20 years late with this document.)

I don't think I could possibly assess what the audience (as a whole)
cares about. Besides, I don't have much of a big ego to expect people to
care what *I* think. What I *can* tell is that a number of people have
already expressed that they found the document to be valuable. And I
would expect people to care about the topic and the content of the
document, regardless of who happens to be the author.

Regarding the timeliness... I guess that, because firewalls *are*
being deployed for v6, we have the "luxury" of doing things right this
time.


> Aren't you worried that readers might think you are a bit biased? I
> would be more interested to read a document written by an end-host-based
> firewall manufacturer that argues for the deployment of network-based
> firewalls.

To be honest, what would really worry me would be if, rather than
focusing on the technical content of the I-D, people fall into
"argumentum ad hominem" (https://en.wikipedia.org/wiki/Ad_hominem) --
particularly if they are speculations.

(FWIW, I never bought the argument that "the security paradigm will move
from network centric to host centric" -- both because (for years) it has
not been network centric (but rather mixed host/network-centric) and
because I don't find any concrete and compelling reasons for which that
will change. However, such argument is not the focus of this document
(at least, not yet). I'd say that both kinds of firewalls serve a
different (and rather complimentary) purpose.)

That said, if you find any bias or room for improvement in the document,
please do let us know.


> PS: The recommendations do not appear to be new and have been mentioned
> in other documents already.

FWIW, the recommendations will be moved out into a separate document.

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 Tue Oct 13 06:56:45 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E62791B405F; Tue, 13 Oct 2015 06:56:41 -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 f92rCA_ooBJ7; Tue, 13 Oct 2015 06:56:40 -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 8F9941B405D; Tue, 13 Oct 2015 06:56:40 -0700 (PDT)
Received: from 17-182-245-190.fibertel.com.ar ([190.245.182.17] 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 1Zm04A-0007Xm-Sj; Tue, 13 Oct 2015 15:56:35 +0200
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
X-Forwarded-Message-Id: <20151013134530.1812.78498.idtracker@ietfa.amsl.com>
Message-ID: <561D0CB7.3040606@si6networks.com>
Date: Tue, 13 Oct 2015 10:52:55 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151013134530.1812.78498.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/aau1umk3NCxGNQITmnunhByc-qo>
Cc: James Woodyatt <jhw@nestlabs.com>, IPv6 Operations <v6ops@ietf.org>, Internet Area <int-area@ietf.org>
Subject: [OPSAWG] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 13:56:42 -0000

FYI.

This rev hopefully addresses some/most/all of the comments received so
far (mostly by Eric Vyncke and James Woodyatt).

More comments/feedback will be welcome.

Thanks,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for
draft-gont-opsawg-firewalls-analysis-01.txt
Date: Tue, 13 Oct 2015 06:45:30 -0700
From: internet-drafts@ietf.org
To: Fred Baker <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>


A new version of I-D, draft-gont-opsawg-firewalls-analysis-01.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-opsawg-firewalls-analysis
Revision:	01
Title:		On Firewalls in Network Security
Document date:	2015-10-13
Group:		Individual Submission
Pages:		17
URL:
https://www.ietf.org/internet-drafts/draft-gont-opsawg-firewalls-analysis-01.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-opsawg-firewalls-analysis/
Htmlized:
https://tools.ietf.org/html/draft-gont-opsawg-firewalls-analysis-01
Diff:
https://www.ietf.org/rfcdiff?url2=draft-gont-opsawg-firewalls-analysis-01

Abstract:
   This document analyzes the role of firewalls in network security, and
   suggests a line of reasoning about their usage.  It analyzes common
   kinds of firewalls and the claims made for them.





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





From nobody Wed Oct 14 16:50:07 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB6D1A9026; Wed, 14 Oct 2015 16:50:06 -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 h4ewc-8FtyIC; Wed, 14 Oct 2015 16:50:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8A51A901E; Wed, 14 Oct 2015 16:50:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AB4C31832B6; Wed, 14 Oct 2015 16:49:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151014234951.AB4C31832B6@rfc-editor.org>
Date: Wed, 14 Oct 2015 16:49:51 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/a0UpWSQW7abGOzE0mizEA2EgJ5s>
Cc: drafts-update-ref@iana.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: [OPSAWG] RFC 7630 on HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 23:50:06 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7630

        Title:      HMAC-SHA-2 Authentication Protocols in the 
                    User-based Security Model (USM) for SNMPv3 
        Author:     J. Merkle, Ed.,
                    M. Lochter
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2015
        Mailbox:    johannes.merkle@secunet.com, 
                    manfred.lochter@bsi.bund.de
        Pages:      14
        Characters: 29324
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-hmac-sha-2-usm-snmp-06.txt

        URL:        https://www.rfc-editor.org/info/rfc7630

        DOI:        http://dx.doi.org/10.17487/RFC7630

This memo specifies new HMAC-SHA-2 authentication protocols for the
User-based Security Model (USM) for SNMPv3 defined in RFC 3414.

This document is a product of the Operations and Management Area Working Group 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 Thu Oct 15 01:23:23 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753751A905E; Thu, 15 Oct 2015 01:23:19 -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 MA_d7UUD2UpA; Thu, 15 Oct 2015 01:23:09 -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 C92021A905F; Thu, 15 Oct 2015 01:23:08 -0700 (PDT)
Received: from [181.165.117.147] (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 1ZmdoP-00073o-1x; Thu, 15 Oct 2015 10:22:58 +0200
To: Mark Andrews <marka@isc.org>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com> <56179631.8060803@si6networks.com> <5617B205.5030004@gmx.net> <20151012002551.8F7CD3A2FFD8@rock.dv.isc.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <561F6266.5070700@si6networks.com>
Date: Thu, 15 Oct 2015 05:23:02 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151012002551.8F7CD3A2FFD8@rock.dv.isc.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/Y6nLR9DnxPG195SV5YXI7a9vltw>
Cc: draft-gont-opsawg-firewalls-analysis@tools.ietf.org, Internet Area <int-area@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 08:23:19 -0000

Hi, Mark,

Thanks so much for your input Comments in-line...

On 10/11/2015 09:25 PM, Mark Andrews wrote:
> 
> Lots of the content is pertanent today.  Look at the treatement of
> DNS packets in todays firewalls.
> 
> It took years to get EDNS packets larger then 512 bytes through
> most firewalls by default.  Some still block packets bigger than
> 512 bytes.
[....]

Question: Has all of this been summarized somewhere?

If not, it would seem that it would be desirable to explicitly include
all this evil behavior in e.g. the forthcoming "advice" document.

Thoughts?

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 Oct 15 01:30:06 2015
Return-Path: <marka@isc.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99D561A9089; Thu, 15 Oct 2015 01:30:03 -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 RZcxsMVdd4r3; Thu, 15 Oct 2015 01:30:02 -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 11F271A9095; Thu, 15 Oct 2015 01:30:02 -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 B81581FCCBB; Thu, 15 Oct 2015 08:29:58 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 56AD6160045; Thu, 15 Oct 2015 08:30:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 40B9C160073; Thu, 15 Oct 2015 08:30: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 r_5TzeBD2L5F; Thu, 15 Oct 2015 08:30: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 E7D54160045; Thu, 15 Oct 2015 08:29:59 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id CDE863A88052; Thu, 15 Oct 2015 19:29:54 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <20150915004941.13204.35415.idtracker@ietfa.amsl.com> <55F76EA7.6090405@si6networks.com> <D2386149.59FC9%evyncke@cisco.com> <56179631.8060803@si6networks.com> <5617B205.5030004@gmx.net> <20151012002551.8F7CD3A2FFD8@rock.dv.isc.org> <561F6266.5070700@si6networks.com>
In-reply-to: Your message of "Thu, 15 Oct 2015 05:23:02 -0300." <561F6266.5070700@si6networks.com>
Date: Thu, 15 Oct 2015 19:29:54 +1100
Message-Id: <20151015082954.CDE863A88052@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/muuQNW_SN-v_JTbZGxHJEyMAtn4>
Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Internet Area <int-area@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, draft-gont-opsawg-firewalls-analysis@tools.ietf.org
Subject: Re: [OPSAWG] [Int-area] [OPSEC] "On Firewalls in Internet Security" (Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-00.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 08:30:05 -0000

In message <561F6266.5070700@si6networks.com>, Fernando Gont writes:
> Hi, Mark,
> 
> Thanks so much for your input Comments in-line...
> 
> On 10/11/2015 09:25 PM, Mark Andrews wrote:
> > 
> > Lots of the content is pertanent today.  Look at the treatement of
> > DNS packets in todays firewalls.
> > 
> > It took years to get EDNS packets larger then 512 bytes through
> > most firewalls by default.  Some still block packets bigger than
> > 512 bytes.
> [....]
> 
> Question: Has all of this been summarized somewhere?

Parts of it show up in EDNS compliance failures graphs at
<https://ednscomp.isc.org/compliance/summary.html>.  There
are server level reports the last compliance run at
<https://ednscomp.isc.org/> as well as a online tester.

draft-andrews-dns-no-response-issue also talks about parts
of it.

> If not, it would seem that it would be desirable to explicitly include
> all this evil behavior in e.g. the forthcoming "advice" document.
> 
> Thoughts?

Perhaps.  Pointing out badness is the first step to getting it
fixed.
 
> Thanks!
> 
> Best regards,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Oct 15 05:43:18 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C65631B311D; Thu, 15 Oct 2015 05:43:16 -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 43RhGsoahV_k; Thu, 15 Oct 2015 05:43: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 67E261B311C; Thu, 15 Oct 2015 05:43:13 -0700 (PDT)
Received: from [181.165.117.147] (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 1Zmhs6-0008M0-56; Thu, 15 Oct 2015 14:43:02 +0200
References: <20151015123705.4548.36728.idtracker@ietfa.amsl.com>
To: IPv6 Operations <v6ops@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
X-Forwarded-Message-Id: <20151015123705.4548.36728.idtracker@ietfa.amsl.com>
Message-ID: <561F9F7C.2030907@si6networks.com>
Date: Thu, 15 Oct 2015 09:43:40 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151015123705.4548.36728.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/78Ykkv-Gs_qS7lRscS48-QfjGt8>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: [OPSAWG] Revision of "Why operators drop IPv6 packets with EHs" (Fwd: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 12:43:16 -0000

Folks,

We have revised our I-D "Operational Implications of IPv6 Packets with
Extension Headers".

The new revision is available at:
<https://www.ietf.org/internet-drafts/draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt>

This version hopefully addresses at least part of the comments received
from Eric Vyncke.

Your feedback will be very appreciated.

Thanks!

Best regards,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for
draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt
Date: Thu, 15 Oct 2015 05:37:05 -0700
From: internet-drafts@ietf.org
To: Gert Doering <gert@space.net>, Nick Hilliard <nick@inex.ie>,
Shucheng LIU (Will) <liushucheng@huawei.com>, Gert Doering
<gert@space.net>, Warren Kumari <warren@kumari.net>, Will Liu (Shucheng)
<liushucheng@huawei.com>, Fernando Gont <fgont@si6networks.com>, Nick
Hilliard <nick@inex.ie>, Fernando Gont <fgont@si6networks.com>, Warren
Kumari <warren@kumari.net>


A new version of I-D, draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-v6ops-ipv6-ehs-packet-drops
Revision:	01
Title:		Operational Implications of IPv6 Packets with Extension Headers
Document date:	2015-10-15
Group:		Individual Submission
Pages:		14
URL:
https://www.ietf.org/internet-drafts/draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-v6ops-ipv6-ehs-packet-drops/
Htmlized:
https://tools.ietf.org/html/draft-gont-v6ops-ipv6-ehs-packet-drops-01
Diff:
https://www.ietf.org/rfcdiff?url2=draft-gont-v6ops-ipv6-ehs-packet-drops-01

Abstract:
   This document summarizes the security and operational implications of
   IPv6 extension headers, and attempts to analyze reasons why packets
   with IPv6 extension headers may be dropped in the public Internet.





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





From nobody Thu Oct 15 08:37:19 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6A9E1B3381; Thu, 15 Oct 2015 08:37:18 -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 Xe9dKSVYtv3D; Thu, 15 Oct 2015 08:37:16 -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 554401B3215; Thu, 15 Oct 2015 08:37:16 -0700 (PDT)
Received: from [190.19.233.70] (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 1Zmkac-0001CH-EQ; Thu, 15 Oct 2015 17:37:10 +0200
To: Tom Herbert <tom@herbertland.com>
References: <20151015123705.4548.36728.idtracker@ietfa.amsl.com> <561F9F7C.2030907@si6networks.com> <CALx6S37TbLADNw9ycLLgZO73Oidn7f_wiQRt9r2nOcg1ewzb8A@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <561FC729.4070701@si6networks.com>
Date: Thu, 15 Oct 2015 12:32:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CALx6S37TbLADNw9ycLLgZO73Oidn7f_wiQRt9r2nOcg1ewzb8A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/0RQfhBJwlNcKwMz1RxTwbaVgsFc>
Cc: IPv6 Operations <v6ops@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Revision of "Why operators drop IPv6 packets with EHs" (Fwd: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 15:37:18 -0000

Hi, Tom,

Thanks so much for your prompt feedback! Please find my comments in-line...

On 10/15/2015 12:18 PM, Tom Herbert wrote:
> Hi Fernado,
> 
> In section 4.1.3:
> 
> "As layer-4 port information increases the entropy of the hash, it is
> highly desirable to use it where possible."
> 
> IMO, the use of IPv6 flow label for ECMP as described in RFC6438 is a
> much better solution to target. The flow label can provide the
> equivalent of layer-4 entropy without requiring devices to parse the
> transport layer. This will work not only with extension headers
> present, as well as other "unusual" protocols that devices may not or
> cannot parse like GRE, IPIP, ESP, etc.

I agree with this. But my understanding was that implementations we're
still setting this to 0 -- that's why this wasn't mentioned as an option.


> Major OSes are now setting flow
> labels for entropy, and AFAIK some switch and NIC vendors now have
> support to use flow label as input to ECMP hash. It might be worth it
> to mention this alternative in the draft.

I guess that mean Linux, Mac OS, *BSD, and MS Windows?

If you know of anything we can reference regarding this change, that
would be awesome. -- I will try to perform some tests myself, anyway.

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 Thu Oct 15 09:08:35 2015
Return-Path: <tom@herbertland.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8111B31B6 for <opsawg@ietfa.amsl.com>; Thu, 15 Oct 2015 09:08:27 -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 y4VleScwvrFS for <opsawg@ietfa.amsl.com>; Thu, 15 Oct 2015 09:08:21 -0700 (PDT)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com [209.85.223.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 7BCA41A9170 for <opsawg@ietf.org>; Thu, 15 Oct 2015 09:08:21 -0700 (PDT)
Received: by iofl186 with SMTP id l186so95149222iof.2 for <opsawg@ietf.org>; Thu, 15 Oct 2015 09:08:20 -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=4bbg5BynOw1tqMeu6+2sCNpL6Oh2qEeRVxrjHYgosJQ=; b=K/GRETa1sQXTy3wp0AJfD+xGD9TenL0Q/kLwj9wNf/udEXOipKVboAeOf1XtCeOgMP BmC/wz5+SOVNVls7Cw9t9vPET80ECUhm3Tu652px/SxBB+3SAYDsbYvbx0Cr7Oq6uwY8 uu5eGDuiBOb8VG4kkIVwg3ndri5eJunrhkBbfTIqfAbul1r2YyWwIqHH0EDbnI0Ap7Rv NwplJp4R409tHj4l1gQiY5sS9iwsipJDLgCYzSKSPKXnbS2naOHMg6++8yed8M8Va8Ce jP79Z6glTcN+PrMNyQXHPGZUBRKWDdUnWPo1AmZfQQDKVHTXsACpia5fTpy0ajcvuvWt dbZg==
X-Gm-Message-State: ALoCoQmOh3PXXYEefwU7wWqbN3ity9zTBYF7Cyou16BnzILyF07/sRFdk23zPV7Xp9oh16xZTD0K
MIME-Version: 1.0
X-Received: by 10.107.16.158 with SMTP id 30mr8364287ioq.50.1444925300797; Thu, 15 Oct 2015 09:08:20 -0700 (PDT)
Received: by 10.107.25.74 with HTTP; Thu, 15 Oct 2015 09:08:20 -0700 (PDT)
In-Reply-To: <561FC729.4070701@si6networks.com>
References: <20151015123705.4548.36728.idtracker@ietfa.amsl.com> <561F9F7C.2030907@si6networks.com> <CALx6S37TbLADNw9ycLLgZO73Oidn7f_wiQRt9r2nOcg1ewzb8A@mail.gmail.com> <561FC729.4070701@si6networks.com>
Date: Thu, 15 Oct 2015 09:08:20 -0700
Message-ID: <CALx6S34+-2QYw7ztoz5hF-g4oSkO04o5L0mrirs6n_FSz3Wfug@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/0syAcLA0NrSjBrivcDMp5emJm40>
Cc: IPv6 Operations <v6ops@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Revision of "Why operators drop IPv6 packets with EHs" (Fwd: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-01.txt)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 16:08:27 -0000

>> Major OSes are now setting flow
>> labels for entropy, and AFAIK some switch and NIC vendors now have
>> support to use flow label as input to ECMP hash. It might be worth it
>> to mention this alternative in the draft.
>
> I guess that mean Linux, Mac OS, *BSD, and MS Windows?
>
> If you know of anything we can reference regarding this change, that
> would be awesome. -- I will try to perform some tests myself, anyway.
>
Mac OS (and BSD) is already deployed with setting non-zero flow labels
which we have verified. Starting with Linux 4.3 flow labels will be
set by default. I don't know about Windows.

Within the data center network we view the use of flow labels for ECMP
as a critical feature since it eliminates one barrier we have to
deploying extension headers or new/alternative protocols. Switches
should not need to parse the transport layer for packet forwarding,
only edge devices will need to parse transport headers to implement
security.

Tom

 > 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 Thu Oct 15 10:39:34 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BC91B3257; Thu, 15 Oct 2015 10:39: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 Fy877bNR6xn7; Thu, 15 Oct 2015 10:39:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1CC1AD0C9; Thu, 15 Oct 2015 10:39:30 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151015173930.19121.44913.idtracker@ietfa.amsl.com>
Date: Thu, 15 Oct 2015 10:39:30 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/jWxw1ZS9NoTzfyym097cYaueiWE>
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 17:39:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.

        Title           : HMAC-SHA-2 Authentication Protocols in USM for SNMPv3
        Authors         : Johannes Merkle
                          Manfred Lochter
	Filename        : draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.txt
	Pages           : 14
	Date            : 2015-10-15

Abstract:
   This memo specifies new HMAC-SHA-2 authentication protocols for the
   User-based Security Model (USM) for SNMPv3 defined in RFC 3414.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00


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

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


From nobody Thu Oct 15 10:42:57 2015
Return-Path: <Johannes.Merkle@secunet.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FCB61B308A for <opsawg@ietfa.amsl.com>; Thu, 15 Oct 2015 10:42:55 -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 Te9awp8ibVWy for <opsawg@ietfa.amsl.com>; Thu, 15 Oct 2015 10:42:52 -0700 (PDT)
Received: from a.mx.secunet.com (a.mx.secunet.com [195.81.216.161]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A5D81ACDF6 for <opsawg@ietf.org>; Thu, 15 Oct 2015 10:42:52 -0700 (PDT)
Received: from localhost (alg1 [127.0.0.1]) by a.mx.secunet.com (Postfix) with ESMTP id B097D1A00F9 for <opsawg@ietf.org>; Thu, 15 Oct 2015 19:42:50 +0200 (CEST)
X-Virus-Scanned: by secunet
Received: from a.mx.secunet.com ([127.0.0.1]) by localhost (a.mx.secunet.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id h9gJNBzyxZ3R for <opsawg@ietf.org>; Thu, 15 Oct 2015 19:42:48 +0200 (CEST)
Received: from mail-essen-01.secunet.de (unknown [10.53.40.204]) by a.mx.secunet.com (Postfix) with ESMTP id A15F81A00F6 for <opsawg@ietf.org>; Thu, 15 Oct 2015 19:42:48 +0200 (CEST)
Received: from [172.16.40.201] (172.16.40.201) by mail-essen-01.secunet.de (10.53.40.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 15 Oct 2015 19:42:47 +0200
To: <opsawg@ietf.org>
References: <20151014234951.AB4C31832B6@rfc-editor.org>
From: Johannes Merkle <johannes.merkle@secunet.com>
Message-ID: <561FE597.5080305@secunet.com>
Date: Thu, 15 Oct 2015 19:42:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151014234951.AB4C31832B6@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.16.40.201]
X-EXCLAIMER-MD-CONFIG: 2c86f778-e09b-4440-8b15-867914633a10
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/OhYmi9kfGCc-RQ3BhikPgXZUQFw>
Subject: Re: [OPSAWG] RFC 7630 on HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2015 17:42:55 -0000

unfortunately, there is an error in the MIB module: the reference to the IANA registry is incorrect. Thus, the RFC
Editor, IANA and IESG decided to obsolete the RFC and issue a corrected one. I have just uploaded the new draft, and
there will be another IETF LC.

Please refrain from implementing the MIB!

Sorry for that confusion.

Johannes

rfc-editor@rfc-editor.org schrieb am 15.10.2015 um 01:49:
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 7630
> 
>         Title:      HMAC-SHA-2 Authentication Protocols in the 
>                     User-based Security Model (USM) for SNMPv3 
>         Author:     J. Merkle, Ed.,
>                     M. Lochter
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       October 2015
>         Mailbox:    johannes.merkle@secunet.com, 
>                     manfred.lochter@bsi.bund.de
>         Pages:      14
>         Characters: 29324
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-opsawg-hmac-sha-2-usm-snmp-06.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc7630
> 
>         DOI:        http://dx.doi.org/10.17487/RFC7630
> 
> This memo specifies new HMAC-SHA-2 authentication protocols for the
> User-based Security Model (USM) for SNMPv3 defined in RFC 3414.
> 
> This document is a product of the Operations and Management Area Working Group 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
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


-- 
Mit freundlichen Grüßen,
Dr. Johannes Merkle
Principal
Division Innere Sicherheit
secunet Security Networks AG
Mergenthaler Allee 77
65760 Eschborn
Germany
Telefon +49 201 54 54-3091
Telefax +49 201 54 54-1325
Mobil   +49 175 2224439
johannes.merkle@secunet.com
www.secunet.com


From nobody Fri Oct 16 05:19:29 2015
Return-Path: <rick.casarez@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D911A1AB9; Fri, 16 Oct 2015 05:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, 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 lCN9hbZzZtch; Fri, 16 Oct 2015 05:19:21 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AF271A86FF; Fri, 16 Oct 2015 05:19:21 -0700 (PDT)
Received: by wijp11 with SMTP id p11so7615528wij.0; Fri, 16 Oct 2015 05:19:19 -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=5PIs9VpKhm466HCXmgkaItbZ1+ZQxOehfgHU/B33/zk=; b=relHq23TfQcCWEaDxAfnwp+/5iB9NzymxP65HWthyCE1EClwe3hsTgnHs4VQPLtLNR +lMGXznCHOYg6MvR1ctIInYqWkud/rebUftNH4lVTSzv89hru49fqfFPGWD9VVRnQjK/ 2nNrWT9R3nxr7V+uQeIlNqZVkoGiZeIVedBD4LxQ7ASyrgOw1pylHJtyV7bPti2oiWKM 4fqx3FRPwc3QWoPZq6U/oZuhH/2KWl4n9RDKj2TmptqzQ4gzICoaVzk8/YhsOO3D+iqJ WgVqbHjSuPUY6xlXqd+vBGxhrUlw2PaDnUJK6n90pBjCfKcNGHfLnL7x80Fr4jrvspFM dEuQ==
MIME-Version: 1.0
X-Received: by 10.180.211.8 with SMTP id my8mr4362596wic.21.1444997959851; Fri, 16 Oct 2015 05:19:19 -0700 (PDT)
Received: by 10.27.108.76 with HTTP; Fri, 16 Oct 2015 05:19:19 -0700 (PDT)
In-Reply-To: <561D0CB7.3040606@si6networks.com>
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com> <561D0CB7.3040606@si6networks.com>
Date: Fri, 16 Oct 2015 08:19:19 -0400
Message-ID: <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com>
From: Rick Casarez <rick.casarez@gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a11c38e0e193a8b052237ce50
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/jIBb7S4Z757W--PgrqxY0EIGHGU>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, Internet Area <int-area@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 12:19:28 -0000

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

While I get amused reading such things are we sure we need lines like this
in the document?

"...and attempts to end the bickering on the topic, which is, for the most
part, of little value in illuminating the discussion."

A few parts of the introduction I think can be re-worded to express the
issues professionally without getting people defensive by making the
statements you are making. Rise above it.

In Section 2:

Firewall - I am wondering if a better definition can be made. From what you
wrote I cannot distinguish between a Firewall and an ACL. No mention of
state tracking for instance etc.

Defense-in-depth - I think you should define this term in this section
since you go on to use it in following sections. It helps by also showing
the differences between it and perimeter.

Section 3.3:

The sentence:

"By that line of reasoning, a firewall primarily protects infrastructure,
by preventing traffic that would attack it from it."

I think flows better as:

"By that line of reasoning, a firewall primarily protects infrastructure,
by preventing traffic that would attack it."

or

"A firewall primarily protects against infrastructure attacks."

Section 5.1:

"The drawback of this approach is that the security goal of "block traffic
unless it is explicitly allowed" prevents useful new applications."

I am not sure I understand this line. It blocks new applications from
immediately traversing the firewall. I know from experience though that
when a discussion is had with the NetSec team the application can be added
to the allow list. So not sure a "default deny" means new stuff never gets
allowed as the text insinuates.

Section 6:

There are temporary IPv4 addresses too. Usually the prefix is allowed with
a set access or security profile. The only problems I am aware of is if you
mix hosts with differing access/security profiles into one subnet. This is
fixed by designating subnets for specific profiles. IPv6 is not any
different and can work the same way.

As for application being tunneled over well-known ports that sounds like a
breakdown of communication between the Service Owners and NetSec. Simple
communication *should* lead to the creation of a profile for that new
application and its individual port. By doing what you describe it sounds
like a Service Owner trying to get out of doing due diligence with NetSec
or not knowing what port their application needs for access (More common
than you might think).

-------------------
Cheers, Rick

Experiences not things.

On Tue, Oct 13, 2015 at 9:52 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> FYI.
>
> This rev hopefully addresses some/most/all of the comments received so
> far (mostly by Eric Vyncke and James Woodyatt).
>
> More comments/feedback will be welcome.
>
> Thanks,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for
> draft-gont-opsawg-firewalls-analysis-01.txt
> Date: Tue, 13 Oct 2015 06:45:30 -0700
> From: internet-drafts@ietf.org
> To: Fred Baker <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
>
>
> A new version of I-D, draft-gont-opsawg-firewalls-analysis-01.txt
> has been successfully submitted by Fernando Gont and posted to the
> IETF repository.
>
> Name:           draft-gont-opsawg-firewalls-analysis
> Revision:       01
> Title:          On Firewalls in Network Security
> Document date:  2015-10-13
> Group:          Individual Submission
> Pages:          17
> URL:
>
> https://www.ietf.org/internet-drafts/draft-gont-opsawg-firewalls-analysis-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-gont-opsawg-firewalls-analysis/
> Htmlized:
> https://tools.ietf.org/html/draft-gont-opsawg-firewalls-analysis-01
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-gont-opsawg-firewalls-analysis-01
>
> Abstract:
>    This document analyzes the role of firewalls in network security, and
>    suggests a line of reasoning about their usage.  It analyzes common
>    kinds of firewalls and the claims made for them.
>
>
>
>
>
> 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
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

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

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div><div><di=
v><div>While I get amused reading such things are we sure we need lines lik=
e this in the document?<br><br>&quot;...and attempts to end the bickering o=
n the topic, which is,
   for the most part, of little value in illuminating the discussion.&quot;=
<br><br></div>A few parts of the introduction I think can be re-worded to e=
xpress the issues professionally without getting people defensive by making=
 the statements you are making. Rise above it.<br><br></div>In Section 2:<b=
r><br></div><div>Firewall - I am wondering if a better definition can be ma=
de. From what you wrote I cannot distinguish between a Firewall and an ACL.=
 No mention of state tracking for instance etc.<br><br></div><div>Defense-i=
n-depth - I think you should define this term in this section since you go =
on to use it in following sections. It helps by also showing the difference=
s between it and perimeter.<br></div><br></div>Section 3.3:<br><br></div>Th=
e sentence:<br><br>&quot;By that line of reasoning, a firewall primarily pr=
otects
   infrastructure, by preventing traffic that would attack it from it.&quot=
;<br><br></div>I think flows better as:<br><br>&quot;By that line of reason=
ing, a firewall primarily protects
   infrastructure, by preventing traffic that would attack it.&quot;<br><br=
></div>or<br><br></div>&quot;A firewall primarily protects against infrastr=
ucture attacks.&quot;<br><br></div>Section 5.1:<br><br>&quot;The drawback o=
f this approach is that the security goal of &quot;block
   traffic unless it is explicitly allowed&quot; prevents useful new
   applications.&quot;<br><br></div>I am not sure I understand this line. I=
t blocks new applications from immediately traversing the firewall. I know =
from experience though that when a discussion is had with the NetSec team t=
he application can be added to the allow list. So not sure a &quot;default =
deny&quot; means new stuff never gets allowed as the text insinuates. <br><=
br></div>Section 6:<br><br></div>There are temporary IPv4 addresses too. Us=
ually the prefix is allowed with a set access or security profile. The only=
 problems I am aware of is if you mix hosts with differing access/security =
profiles into one subnet. This is fixed by designating subnets for specific=
 profiles. IPv6 is not any different and can work the same way. <br><br></d=
iv>As for application being tunneled over well-known ports that sounds like=
 a breakdown of communication between the Service Owners and NetSec. Simple=
 communication *should* lead to the creation of a profile for that new appl=
ication and its individual port. By doing what you describe it sounds like =
a Service Owner trying to get out of doing due diligence with NetSec or not=
 knowing what port their application needs for access (More common than you=
 might think). <br></div><div class=3D"gmail_extra"><br clear=3D"all"><div>=
<div class=3D"gmail_signature"><div dir=3D"ltr">-------------------<br>Chee=
rs, Rick<br><br>Experiences not things.</div></div></div>
<br><div class=3D"gmail_quote">On Tue, Oct 13, 2015 at 9:52 AM, Fernando Go=
nt <span dir=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" target=3D=
"_blank">fgont@si6networks.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">FYI.<br>
<br>
This rev hopefully addresses some/most/all of the comments received so<br>
far (mostly by Eric Vyncke and James Woodyatt).<br>
<br>
More comments/feedback will be welcome.<br>
<br>
Thanks,<br>
Fernando<br>
<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: New Version Notification for<br>
draft-gont-opsawg-firewalls-analysis-01.txt<br>
Date: Tue, 13 Oct 2015 06:45:30 -0700<br>
From: <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org<=
/a><br>
To: Fred Baker &lt;<a href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&gt;=
, Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com">fgont@si6netwo=
rks.com</a>&gt;<br>
<br>
<br>
A new version of I-D, draft-gont-opsawg-firewalls-analysis-01.txt<br>
has been successfully submitted by Fernando Gont and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-gont-opsawg-firewalls-a=
nalysis<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 On Firewalls in Network Security<b=
r>
Document date:=C2=A0 2015-10-13<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 17<br>
URL:<br>
<a href=3D"https://www.ietf.org/internet-drafts/draft-gont-opsawg-firewalls=
-analysis-01.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org=
/internet-drafts/draft-gont-opsawg-firewalls-analysis-01.txt</a><br>
Status:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-gont-opsawg-firewalls-ana=
lysis/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/draft-gont-opsawg-firewalls-analysis/</a><br>
Htmlized:<br>
<a href=3D"https://tools.ietf.org/html/draft-gont-opsawg-firewalls-analysis=
-01" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft=
-gont-opsawg-firewalls-analysis-01</a><br>
Diff:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-gont-opsawg-firewalls-=
analysis-01" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcd=
iff?url2=3Ddraft-gont-opsawg-firewalls-analysis-01</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document analyzes the role of firewalls in network securi=
ty, and<br>
=C2=A0 =C2=A0suggests a line of reasoning about their usage.=C2=A0 It analy=
zes common<br>
=C2=A0 =C2=A0kinds of firewalls and the claims made for them.<br>
<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div><br></div>

--001a11c38e0e193a8b052237ce50--


From nobody Fri Oct 16 13:39:24 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB9A1A033A; Fri, 16 Oct 2015 13:39:21 -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 nyYecmtA78Yh; Fri, 16 Oct 2015 13:39:18 -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 AF86D1A0235; Fri, 16 Oct 2015 13:39:18 -0700 (PDT)
Received: from [190.19.233.70] (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 1ZnBmS-0004v7-NZ; Fri, 16 Oct 2015 22:39:13 +0200
To: Rick Casarez <rick.casarez@gmail.com>
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com> <561D0CB7.3040606@si6networks.com> <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <562155BC.6030701@si6networks.com>
Date: Fri, 16 Oct 2015 16:53:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/fpJlrKbi3j1zmBLAHru6eeJ14Rg>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, Internet Area <int-area@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 20:39:21 -0000

Hi, Rick,

Thanks so much for your feedback! Please find my responses in-line...

On 10/16/2015 09:19 AM, Rick Casarez wrote:
> While I get amused reading such things are we sure we need lines like
> this in the document?
> 
> "...and attempts to end the bickering on the topic, which is, for the
> most part, of little value in illuminating the discussion."
> 
> A few parts of the introduction I think can be re-worded to express the
> issues professionally without getting people defensive by making the
> statements you are making. Rise above it.

I'll re-check the text -- The Intro was going to be re-worked, anyway.



> In Section 2:
> 
> Firewall - I am wondering if a better definition can be made. From what
> you wrote I cannot distinguish between a Firewall and an ACL. 

An ACL is a policy. A firewall is a device that enforces filtering policies.


> No mention
> of state tracking for instance etc.

Ok, will try to add somethin in this respect.



> Defense-in-depth - I think you should define this term in this section
> since you go on to use it in following sections.

Will do.



> Section 3.3:
> 
> The sentence:
> 
> "By that line of reasoning, a firewall primarily protects
> infrastructure, by preventing traffic that would attack it from it."
> 
> I think flows better as:
> 
> "By that line of reasoning, a firewall primarily protects
> infrastructure, by preventing traffic that would attack it."
> 
> or
> 
> "A firewall primarily protects against infrastructure attacks."

This seond option my work. (Your first option changes the meaning of the
sentence).



> Section 5.1:
> 
> "The drawback of this approach is that the security goal of "block
> traffic unless it is explicitly allowed" prevents useful new applications."
> 
> I am not sure I understand this line. It blocks new applications from
> immediately traversing the firewall. I know from experience though that
> when a discussion is had with the NetSec team the application can be
> added to the allow list. So not sure a "default deny" means new stuff
> never gets allowed as the text insinuates.

Well, that depends on where the firewall is being deployed, and if it is
actively managed.



> Section 6:
> 
> There are temporary IPv4 addresses too.

Not by definition I'd say. Or... would you mind elaborating a bit more
in this respect?



> As for application being tunneled over well-known ports that sounds like
> a breakdown of communication between the Service Owners and NetSec.
> Simple communication *should* lead to the creation of a profile for that
> new application and its individual port. By doing what you describe it
> sounds like a Service Owner trying to get out of doing due diligence
> with NetSec or not knowing what port their application needs for access
> (More common than you might think).

Yes. Or, at times, a user/app trying to circumvent unmanaged firewalls.
-- Ironically, at times these protocols are referred to as "firewall
friendly".

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 Fri Oct 16 14:13:57 2015
Return-Path: <cb.list6@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1301A1AD0; Fri, 16 Oct 2015 14:13:53 -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 PtcQJTUPptO4; Fri, 16 Oct 2015 14:13:51 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c: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 CA4BD1A002A; Fri, 16 Oct 2015 14:13:50 -0700 (PDT)
Received: by wicgb1 with SMTP id gb1so25142251wic.1; Fri, 16 Oct 2015 14:13:49 -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=V5g+OCcLHbMHHyzh/GlYvcnndyM9wWLHYLTD7S+fCEg=; b=ZRURDvwGrdoriQneGudU0INPqxa2C1xSGyZcf0LARy+Pb7l0tyqIfWghGo3FqHX4KG ouyEd1UpNfSKxPoCMXU5/ufxebolOjPowW8S0+ygMg6G7zqJV/BJ2awaVIw5puD+VdoP XspxBkoJnysh4LAF8zeiiqvKnQeJ3VorX1V6J2iQ2boFn6GWB3xZ5e5H3YuIb6DTKnJp 7qREyJn60/mLBvVXE7MkgjYqeN9DGdSoFy/+/XCfaoaBPu6/0CodID1a8Rw/JNRTqjro 3b94FB/lvpjf8H365MJ1GUe6L99NtRZ7ImmhtPz7Dq53zM0b60khGr22zn+GbHP1BEh0 iF0w==
MIME-Version: 1.0
X-Received: by 10.180.104.69 with SMTP id gc5mr7313825wib.69.1445030029313; Fri, 16 Oct 2015 14:13:49 -0700 (PDT)
Received: by 10.194.192.40 with HTTP; Fri, 16 Oct 2015 14:13:49 -0700 (PDT)
In-Reply-To: <562155BC.6030701@si6networks.com>
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com> <561D0CB7.3040606@si6networks.com> <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com> <562155BC.6030701@si6networks.com>
Date: Fri, 16 Oct 2015 14:13:49 -0700
Message-ID: <CAD6AjGTt4tNkMXbDLQMMRWq7ydJQ4uthAbre-kc6W3rsSTmucQ@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=f46d043bdbe6964ea605223f453b
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/RTJcy70b4rlpntre_mr5cmxPdiQ>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, Internet Area <int-area@ietf.org>, Rick Casarez <rick.casarez@gmail.com>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 21:13:53 -0000

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

I think this is important work, but i think this draft is too broad to be
effective in its current form.  I think it would be a great value to adopt
the common enterprise network view and scope of a "stateful firewall" that
most people
think of... from the likes of Checkpoint, Palo Alto, ...


On Fri, Oct 16, 2015 at 12:53 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> Hi, Rick,
>
> Thanks so much for your feedback! Please find my responses in-line...
>
> On 10/16/2015 09:19 AM, Rick Casarez wrote:
> > While I get amused reading such things are we sure we need lines like
> > this in the document?
> >
> > "...and attempts to end the bickering on the topic, which is, for the
> > most part, of little value in illuminating the discussion."
> >
> > A few parts of the introduction I think can be re-worded to express the
> > issues professionally without getting people defensive by making the
> > statements you are making. Rise above it.
>
> I'll re-check the text -- The Intro was going to be re-worked, anyway.
>
>
>
> > In Section 2:
> >
> > Firewall - I am wondering if a better definition can be made. From what
> > you wrote I cannot distinguish between a Firewall and an ACL.
>
> An ACL is a policy. A firewall is a device that enforces filtering
> policies.
>
>
This defintion makes every on path device a firewall.  This is not a good
places to go.


> > No mention
> > of state tracking for instance etc.
>
> Ok, will try to add somethin in this respect.
>
>
>
This is the core of what 99% of the world thinks a firewall is.


>
> > Defense-in-depth - I think you should define this term in this section
> > since you go on to use it in following sections.
>
> Will do.
>
>
>
> > Section 3.3:
> >
> > The sentence:
> >
> > "By that line of reasoning, a firewall primarily protects
> > infrastructure, by preventing traffic that would attack it from it."
> >
> > I think flows better as:
> >
> > "By that line of reasoning, a firewall primarily protects
> > infrastructure, by preventing traffic that would attack it."
> >
> > or
> >
> > "A firewall primarily protects against infrastructure attacks."
>
> This seond option my work. (Your first option changes the meaning of the
> sentence).
>
>
>
eh...what is infrastructure... slippery slope here.


> > Section 5.1:
> >
> > "The drawback of this approach is that the security goal of "block
> > traffic unless it is explicitly allowed" prevents useful new
> applications."
> >
> > I am not sure I understand this line. It blocks new applications from
> > immediately traversing the firewall. I know from experience though that
> > when a discussion is had with the NetSec team the application can be
> > added to the allow list. So not sure a "default deny" means new stuff
> > never gets allowed as the text insinuates.
>
> Well, that depends on where the firewall is being deployed, and if it is
> actively managed.
>
>
Actively managed vs not actively are worlds apart.  Do not lump them
together.

Same with stateful vs stateless


>
>
> > Section 6:
> >
> > There are temporary IPv4 addresses too.
>
> Not by definition I'd say. Or... would you mind elaborating a bit more
> in this respect?
>
>
>
> > As for application being tunneled over well-known ports that sounds like
> > a breakdown of communication between the Service Owners and NetSec.
> > Simple communication *should* lead to the creation of a profile for that
> > new application and its individual port. By doing what you describe it
> > sounds like a Service Owner trying to get out of doing due diligence
> > with NetSec or not knowing what port their application needs for access
> > (More common than you might think).
>
> Yes. Or, at times, a user/app trying to circumvent unmanaged firewalls.
> -- Ironically, at times these protocols are referred to as "firewall
> friendly".
>
>
Yes... own the PC via Phishing or Flash, then use PCP from the PC to open
all the rules you want!

CB


> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

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

<div dir=3D"ltr">I think this is important work, but i think this draft is =
too broad to be effective in its current form.=C2=A0 I think it would be a =
great value to adopt the common enterprise network view and scope of a &quo=
t;stateful firewall&quot; that most people=C2=A0<div>think of... from the l=
ikes of Checkpoint, Palo Alto, ...<div><br><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Fri, Oct 16, 2015 at 12:53 PM, Fernando Gont <=
span dir=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" target=3D"_bl=
ank">fgont@si6networks.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, Rick,<br>
<br>
Thanks so much for your feedback! Please find my responses in-line...<br>
<span class=3D""><br>
On 10/16/2015 09:19 AM, Rick Casarez wrote:<br>
&gt; While I get amused reading such things are we sure we need lines like<=
br>
&gt; this in the document?<br>
&gt;<br>
&gt; &quot;...and attempts to end the bickering on the topic, which is, for=
 the<br>
&gt; most part, of little value in illuminating the discussion.&quot;<br>
&gt;<br>
&gt; A few parts of the introduction I think can be re-worded to express th=
e<br>
&gt; issues professionally without getting people defensive by making the<b=
r>
&gt; statements you are making. Rise above it.<br>
<br>
</span>I&#39;ll re-check the text -- The Intro was going to be re-worked, a=
nyway.<br>
<span class=3D""><br>
<br>
<br>
&gt; In Section 2:<br>
&gt;<br>
&gt; Firewall - I am wondering if a better definition can be made. From wha=
t<br>
&gt; you wrote I cannot distinguish between a Firewall and an ACL.<br>
<br>
</span>An ACL is a policy. A firewall is a device that enforces filtering p=
olicies.<br>
<span class=3D""><br></span></blockquote><div>=C2=A0</div><div>This definti=
on makes every on path device a firewall.=C2=A0 This is not a good places t=
o go.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
<br>
&gt; No mention<br>
&gt; of state tracking for instance etc.<br>
<br>
</span>Ok, will try to add somethin in this respect.<br>
<span class=3D""><br>
<br></span></blockquote><div><br></div><div>This is the core of what 99% of=
 the world thinks a firewall is.</div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><span class=3D"">
<br>
&gt; Defense-in-depth - I think you should define this term in this section=
<br>
&gt; since you go on to use it in following sections.<br>
<br>
</span>Will do.<br>
<span class=3D""><br>
<br>
<br>
&gt; Section 3.3:<br>
&gt;<br>
&gt; The sentence:<br>
&gt;<br>
&gt; &quot;By that line of reasoning, a firewall primarily protects<br>
&gt; infrastructure, by preventing traffic that would attack it from it.&qu=
ot;<br>
&gt;<br>
&gt; I think flows better as:<br>
&gt;<br>
&gt; &quot;By that line of reasoning, a firewall primarily protects<br>
&gt; infrastructure, by preventing traffic that would attack it.&quot;<br>
&gt;<br>
&gt; or<br>
&gt;<br>
&gt; &quot;A firewall primarily protects against infrastructure attacks.&qu=
ot;<br>
<br>
</span>This seond option my work. (Your first option changes the meaning of=
 the<br>
sentence).<br>
<span class=3D""><br>
<br></span></blockquote><div><br></div><div>eh...what is infrastructure... =
slippery slope here.=C2=A0</div><div><br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><span class=3D"">
<br>
&gt; Section 5.1:<br>
&gt;<br>
&gt; &quot;The drawback of this approach is that the security goal of &quot=
;block<br>
&gt; traffic unless it is explicitly allowed&quot; prevents useful new appl=
ications.&quot;<br>
&gt;<br>
&gt; I am not sure I understand this line. It blocks new applications from<=
br>
&gt; immediately traversing the firewall. I know from experience though tha=
t<br>
&gt; when a discussion is had with the NetSec team the application can be<b=
r>
&gt; added to the allow list. So not sure a &quot;default deny&quot; means =
new stuff<br>
&gt; never gets allowed as the text insinuates.<br>
<br>
</span>Well, that depends on where the firewall is being deployed, and if i=
t is<br>
actively managed.<br>
<span class=3D""><br></span></blockquote><div><br></div><div>Actively manag=
ed vs not actively are worlds apart.=C2=A0 Do not lump them together.</div>=
<div><br></div><div>Same with stateful vs stateless</div><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><span class=3D"">
<br>
<br>
&gt; Section 6:<br>
&gt;<br>
&gt; There are temporary IPv4 addresses too.<br>
<br>
</span>Not by definition I&#39;d say. Or... would you mind elaborating a bi=
t more<br>
in this respect?<br>
<span class=3D""><br>
<br>
<br>
&gt; As for application being tunneled over well-known ports that sounds li=
ke<br>
&gt; a breakdown of communication between the Service Owners and NetSec.<br=
>
&gt; Simple communication *should* lead to the creation of a profile for th=
at<br>
&gt; new application and its individual port. By doing what you describe it=
<br>
&gt; sounds like a Service Owner trying to get out of doing due diligence<b=
r>
&gt; with NetSec or not knowing what port their application needs for acces=
s<br>
&gt; (More common than you might think).<br>
<br>
</span>Yes. Or, at times, a user/app trying to circumvent unmanaged firewal=
ls.<br>
-- Ironically, at times these protocols are referred to as &quot;firewall<b=
r>
friendly&quot;.<br>
<br></blockquote><div><br></div><div>Yes... own the PC via Phishing or Flas=
h, then use PCP from the PC to open all the rules you want!</div><div><br><=
/div><div>CB</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks!<br>
<br>
Best regards,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a><=
br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</div></div></blockquote></div><br></div></div></div></div>

--f46d043bdbe6964ea605223f453b--


From nobody Sun Oct 18 05:35:58 2015
Return-Path: <rick.casarez@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 274CC1A1EF1; Sun, 18 Oct 2015 05:35:56 -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 rVAglF89nYob; Sun, 18 Oct 2015 05:35:53 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c: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 3D45B1A1BF5; Sun, 18 Oct 2015 05:35:53 -0700 (PDT)
Received: by wikq8 with SMTP id q8so17132669wik.1; Sun, 18 Oct 2015 05:35:51 -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=LoDuQ1J6h2LokW6XxnptwZ6YAbq6HrznNEjVoH4it14=; b=C9dSsn0ZJN+SQlK+EdYw17yq7zz1B3XM2hT/KAu/VgibBpP7PeDNnwQHaHVCA+BuIa oE42xVtdOJnOcMB6Cdt7oG5NxzMVj7l4+CDNL5w2TRW1mY9/Jq2Yub3bfAyIWzZSmYam Zo+FO4JKMCNbOS56p2MQbfUA0HagjTAAFMUSDbXSPUSSHVamKPwSV0Q3MBnFjyCkNmO1 CuI4DYd37kYyYBupvCuPS6alOSjqNicgSJ5xASZYDCG7DrbfQ8jOl2nqNlCkl8k8U08y 5V3voeV7eAS3gCx+Id9veUcdH/nzlsnT2ky6xdtZ6SwWh37M/KnFhTa9599RtALN+adI U/tg==
MIME-Version: 1.0
X-Received: by 10.180.211.8 with SMTP id my8mr14347969wic.21.1445171751683; Sun, 18 Oct 2015 05:35:51 -0700 (PDT)
Received: by 10.27.108.76 with HTTP; Sun, 18 Oct 2015 05:35:51 -0700 (PDT)
In-Reply-To: <562155BC.6030701@si6networks.com>
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com> <561D0CB7.3040606@si6networks.com> <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com> <562155BC.6030701@si6networks.com>
Date: Sun, 18 Oct 2015 08:35:51 -0400
Message-ID: <CAGWMUT686GhqGQ+H4McBXy7mmDChPQJH2kDzU_SNQAceFCucUA@mail.gmail.com>
From: Rick Casarez <rick.casarez@gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a11c38e0ee60cfd05226044ae
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/C3grSLrjkrhXiMWkPl33A6xYlxM>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, Internet Area <int-area@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2015 12:35:56 -0000

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

Just trying to help. Answers in line.

-------------------
Cheers, Rick

Experiences not things.

On Fri, Oct 16, 2015 at 3:53 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> Hi, Rick,
>
> Thanks so much for your feedback! Please find my responses in-line...
>
> On 10/16/2015 09:19 AM, Rick Casarez wrote:
> > While I get amused reading such things are we sure we need lines like
> > this in the document?
> >
> > "...and attempts to end the bickering on the topic, which is, for the
> > most part, of little value in illuminating the discussion."
> >
> > A few parts of the introduction I think can be re-worded to express the
> > issues professionally without getting people defensive by making the
> > statements you are making. Rise above it.
>
> I'll re-check the text -- The Intro was going to be re-worked, anyway.
>
> [Rick] Sounds good. Thanks.

>
>
> > In Section 2:
> >
> > Firewall - I am wondering if a better definition can be made. From what
> > you wrote I cannot distinguish between a Firewall and an ACL.
>
> An ACL is a policy. A firewall is a device that enforces filtering
> policies.
>
> [Rick] Your definition would encompass routers and switches who have
ACL/Filters on interfaces/SVIs. I would not consider these firewalls.

>
> > No mention
> > of state tracking for instance etc.
>
> Ok, will try to add somethin in this respect.
>
> [Rick] Please do, as Ca mentions this is how the vast majority of the
world define it as. This even includes common compliance audits like
PCI/SOC etc.

>
>
> > Defense-in-depth - I think you should define this term in this section
> > since you go on to use it in following sections.
>
> Will do.
>
>
>
> > Section 3.3:
> >
> > The sentence:
> >
> > "By that line of reasoning, a firewall primarily protects
> > infrastructure, by preventing traffic that would attack it from it."
> >
> > I think flows better as:
> >
> > "By that line of reasoning, a firewall primarily protects
> > infrastructure, by preventing traffic that would attack it."
> >
> > or
> >
> > "A firewall primarily protects against infrastructure attacks."
>
> This seond option my work. (Your first option changes the meaning of the
> sentence).
>
>
>
> > Section 5.1:
> >
> > "The drawback of this approach is that the security goal of "block
> > traffic unless it is explicitly allowed" prevents useful new
> applications."
> >
> > I am not sure I understand this line. It blocks new applications from
> > immediately traversing the firewall. I know from experience though that
> > when a discussion is had with the NetSec team the application can be
> > added to the allow list. So not sure a "default deny" means new stuff
> > never gets allowed as the text insinuates.
>
> Well, that depends on where the firewall is being deployed, and if it is
> actively managed.
>
> [Rick] I am unaware of any firewall deployed that is no longer managed.
The only cases I can think of is if the company has fired all engineers
after initial deployment. This would make it a business problem, not a
technical one since appropriate staffing is a business item.

Placement of the firewall is moot since if staffing is done correctly the
scenario I describe above should happen. If not staffed properly the
business has issues not related to creating new applications. In other
words it is not really the firewalls fault but the business for not having
anyone to maintain a piece of gear they deployed.

>
>
> > Section 6:
> >
> > There are temporary IPv4 addresses too.
>
> Not by definition I'd say. Or... would you mind elaborating a bit more
> in this respect?
>
>  [Rick] My apologies on this one got some wires crossed. This is good to
go.

>
>
> > As for application being tunneled over well-known ports that sounds like
> > a breakdown of communication between the Service Owners and NetSec.
> > Simple communication *should* lead to the creation of a profile for that
> > new application and its individual port. By doing what you describe it
> > sounds like a Service Owner trying to get out of doing due diligence
> > with NetSec or not knowing what port their application needs for access
> > (More common than you might think).
>
> Yes. Or, at times, a user/app trying to circumvent unmanaged firewalls.
> -- Ironically, at times these protocols are referred to as "firewall
> friendly".
>

 [Rick] The scenario makes no sense other than a mismanaged company
frankly. You are essentially encouraging something against BCP. Even beyond
security you will make it difficult to troubleshoot if everything is using
the same port to traverse the firewall.

>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>

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

<div dir=3D"ltr">Just trying to help. Answers in line.<br><div class=3D"gma=
il_extra"><br clear=3D"all"><div><div><div dir=3D"ltr">-------------------<=
br>Cheers, Rick<br><br>Experiences not things.</div></div></div>
<br><div class=3D"gmail_quote">On Fri, Oct 16, 2015 at 3:53 PM, Fernando Go=
nt <span dir=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" target=3D=
"_blank">fgont@si6networks.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Hi, Rick,<br>
<br>
Thanks so much for your feedback! Please find my responses in-line...<br>
<br>
On 10/16/2015 09:19 AM, Rick Casarez wrote:<br>
&gt; While I get amused reading such things are we sure we need lines like<=
br>
&gt; this in the document?<br>
&gt;<br>
&gt; &quot;...and attempts to end the bickering on the topic, which is, for=
 the<br>
&gt; most part, of little value in illuminating the discussion.&quot;<br>
&gt;<br>
&gt; A few parts of the introduction I think can be re-worded to express th=
e<br>
&gt; issues professionally without getting people defensive by making the<b=
r>
&gt; statements you are making. Rise above it.<br>
<br>
I&#39;ll re-check the text -- The Intro was going to be re-worked, anyway.<=
br>
<br></blockquote><div>[Rick] Sounds good. Thanks. <br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
<br>
<br>
&gt; In Section 2:<br>
&gt;<br>
&gt; Firewall - I am wondering if a better definition can be made. From wha=
t<br>
&gt; you wrote I cannot distinguish between a Firewall and an ACL.<br>
<br>
An ACL is a policy. A firewall is a device that enforces filtering policies=
.<br>
<br></blockquote><div>[Rick] Your definition would encompass routers and sw=
itches who have ACL/Filters on interfaces/SVIs. I would not consider these =
firewalls. <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt; No mention<br>
&gt; of state tracking for instance etc.<br>
<br>
Ok, will try to add somethin in this respect.<br>
<br></blockquote><div>[Rick] Please do, as Ca mentions this is how the vast=
 majority of the world define it as. This even includes common compliance a=
udits like PCI/SOC etc. <br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
&gt; Defense-in-depth - I think you should define this term in this section=
<br>
&gt; since you go on to use it in following sections.<br>
<br>
Will do.<br>
<br>
<br>
<br>
&gt; Section 3.3:<br>
&gt;<br>
&gt; The sentence:<br>
&gt;<br>
&gt; &quot;By that line of reasoning, a firewall primarily protects<br>
&gt; infrastructure, by preventing traffic that would attack it from it.&qu=
ot;<br>
&gt;<br>
&gt; I think flows better as:<br>
&gt;<br>
&gt; &quot;By that line of reasoning, a firewall primarily protects<br>
&gt; infrastructure, by preventing traffic that would attack it.&quot;<br>
&gt;<br>
&gt; or<br>
&gt;<br>
&gt; &quot;A firewall primarily protects against infrastructure attacks.&qu=
ot;<br>
<br>
This seond option my work. (Your first option changes the meaning of the<br=
>
sentence).<br>
<br>
<br>
<br>
&gt; Section 5.1:<br>
&gt;<br>
&gt; &quot;The drawback of this approach is that the security goal of &quot=
;block<br>
&gt; traffic unless it is explicitly allowed&quot; prevents useful new appl=
ications.&quot;<br>
&gt;<br>
&gt; I am not sure I understand this line. It blocks new applications from<=
br>
&gt; immediately traversing the firewall. I know from experience though tha=
t<br>
&gt; when a discussion is had with the NetSec team the application can be<b=
r>
&gt; added to the allow list. So not sure a &quot;default deny&quot; means =
new stuff<br>
&gt; never gets allowed as the text insinuates.<br>
<br>
Well, that depends on where the firewall is being deployed, and if it is<br=
>
actively managed.<br>
<br></blockquote><div>[Rick] I am unaware of any firewall deployed that is =
no longer managed. The only cases I can think of is if the company has fire=
d all engineers after initial deployment. This would make it a business pro=
blem, not a technical one since appropriate staffing is a business item.<br=
><br></div><div>Placement of the firewall is moot since if staffing is done=
 correctly the scenario I describe above should happen. If not staffed prop=
erly the business has issues not related to creating new applications. In o=
ther words it is not really the firewalls fault but the business for not ha=
ving anyone to maintain a piece of gear they deployed.=C2=A0 <br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<br>
<br>
&gt; Section 6:<br>
&gt;<br>
&gt; There are temporary IPv4 addresses too.<br>
<br>
Not by definition I&#39;d say. Or... would you mind elaborating a bit more<=
br>
in this respect?<br>
<br></blockquote><div>=C2=A0[Rick] My apologies on this one got some wires =
crossed. This is good to go.<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
&gt; As for application being tunneled over well-known ports that sounds li=
ke<br>
&gt; a breakdown of communication between the Service Owners and NetSec.<br=
>
&gt; Simple communication *should* lead to the creation of a profile for th=
at<br>
&gt; new application and its individual port. By doing what you describe it=
<br>
&gt; sounds like a Service Owner trying to get out of doing due diligence<b=
r>
&gt; with NetSec or not knowing what port their application needs for acces=
s<br>
&gt; (More common than you might think).<br>
<br>
Yes. Or, at times, a user/app trying to circumvent unmanaged firewalls.<br>
-- Ironically, at times these protocols are referred to as &quot;firewall<b=
r>
friendly&quot;.<br></blockquote><div>=C2=A0</div><div>=C2=A0[Rick] The scen=
ario makes no sense other than a mismanaged company frankly. You are essent=
ially encouraging something against BCP. Even beyond security you will make=
 it difficult to troubleshoot if everything is using the same port to trave=
rse the firewall.<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks!<br>
<br>
Best regards,<br>
<span><font color=3D"#888888">--<br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si=
6networks.com</a><br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a11c38e0ee60cfd05226044ae--


From nobody Sun Oct 18 19:52:25 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6391A00F4 for <opsawg@ietfa.amsl.com>; Sun, 18 Oct 2015 19:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.322
X-Spam-Level: 
X-Spam-Status: No, score=-0.322 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, FUZZY_CREDIT=1.678, 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 SKE_w7l4I7r9 for <opsawg@ietfa.amsl.com>; Sun, 18 Oct 2015 19:52:22 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e: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 93EFD1A00B1 for <opsawg@ietf.org>; Sun, 18 Oct 2015 19:52:22 -0700 (PDT)
Received: by padhk11 with SMTP id hk11so14648032pad.1 for <opsawg@ietf.org>; Sun, 18 Oct 2015 19:52:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=DxbfjLB784889KpEKPPNK9vPMG+n8J/hiSKOvhZSxQo=; b=GkcuhU0IPZvdLfzlAVFiImeK7xdQ9Q0PnT8DUHgtbSDxKHUGTSVtHa+8oM+0QyZGbf jICx63xc2E2gW/fuPQDnqFTQmuVOIsp3hGIT5b6dV+HVw6ig88Vpi4wxhClBXL5+jm62 DXhwo0PPNEbzo32CHvUWD6thiFWJfPNQYYDXbRSgv6cmnLX+00pqwCLHxUuTFu6iDubA 8IY9wbOYf8jnuAR0lMpfuXZh6f6BBcxtv4WIQ/2qNj6YzPK+6zTI4PbDELL28J49+FTF gY0mTvJdgut/AXszZXHDqG2ERQRyPGlsJT0oobA7fwxCoU0KRvCVnwD/zF8ZKXBTOkwr 9k7Q==
X-Received: by 10.66.158.233 with SMTP id wx9mr31944156pab.157.1445223142031;  Sun, 18 Oct 2015 19:52:22 -0700 (PDT)
Received: from [192.168.178.25] (221.231.69.111.dynamic.snap.net.nz. [111.69.231.221]) by smtp.gmail.com with ESMTPSA id z12sm33150581pbt.30.2015.10.18.19.52.19 for <opsawg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Oct 2015 19:52:20 -0700 (PDT)
To: opsawg@ietf.org
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56245AE1.405@gmail.com>
Date: Mon, 19 Oct 2015 15:52:17 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151013134530.1812.97650.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/hIVpKPKiX04jrjDN8ugWZBu-WEU>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 02:52:23 -0000

Hmm. I've finally made time to read this draft, to find out what the
fuss is about...

Firstly, I have to find a polite way of saying... well, I can't, so
here it is: delete the Introduction and try again. I think the present
text is guaranteed to annoy just about everybody, and evidently it will
not "end the bickering."

(I gave my own potted history of security in the IETF in the plenary
at IETF 88, slides 2-4.)

Then, I can see 12 RFCs in the index whose titles include the word 'firewall'
and that only scratches the surface; there are literally hundreds of references
to firewalls in existing RFCs. IMHO, if this draft aims to survey the field,
it needs to survey the IETF and non-IETF literature much better (perhaps as
an appendix).

Overall, this draft seems to me to be an opinion piece. That's fine of course,
everyone is entitled to state their opinion, but I'm not sure that it helps
the IETF to know what to do next. It reads more like a CCR editorial article
or an Independent Submission RFC.

To some more specific comments:

Section 4.1 seems to increase rather than decrease the popular confusion
between firewall functions and NAT functions. I would prefer to see
NAT described in a separate section *as a side issue*. NAT failure modes
are not the same as firewall failure modes.

Section 4.3 cites draft-vyncke-advanced-ipv6-security, which is very dead
as far as I can tell. I don't think we should be citing dead work
in a current IETF draft.

Regards
   Brian Carpenter


From nobody Mon Oct 19 09:10:01 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B91F21A8765; Mon, 19 Oct 2015 09:09:58 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151019160958.28797.21848.idtracker@ietfa.amsl.com>
Date: Mon, 19 Oct 2015 09:09:58 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/pV2yWtTXrPUiVRewkGbWWbUs5pY>
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-capwap-alt-tunnel-06.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 16:09:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.

        Title           : Alternate Tunnel Encapsulation for Data Frames in CAPWAP
        Authors         : Rong Zhang
                          Zhen Cao
                          Hui Deng
                          Rajesh S. Pazhyannur
                          Sri Gundavelli
                          Li Xue
                          Jianjie You
	Filename        : draft-ietf-opsawg-capwap-alt-tunnel-06.txt
	Pages           : 23
	Date            : 2015-10-19

Abstract:
   Control And Provisioning of Wireless Access Points (CAPWAP) defines a
   specification to encapsulate a station's data frames between the
   Wireless Transmission Point (WTP) and Access Controller (AC).
   Specifically, the station's IEEE 802.11 data frames can be either
   locally bridged or tunneled to the AC.  When tunneled, a CAPWAP data
   channel is used for tunneling.  In many deployments encapsulating
   data frames to an entity other than the AC (for example to an Access
   Router (AR)) is desirable.  Further, it may also be desirable to use
   different tunnel encapsulations to carry the stations' data frames.
   This document provides a specification for this and refers to it as
   alternate tunnel encapsulation.  The alternate tunnel encapsulation
   allows 1) the WTP to tunnel non-management data frames to an endpoint
   different from the AC and 2) the WTP to tunnel using one of many
   known encapsulation types such as IP-IP, IP-GRE, CAPWAP.  The WTP may
   advertise support for alternate tunnel encapsulation during the
   discovery or join process and AC may select one of the supported
   alternate tunnel encapsulation types while configuring the WTP.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-capwap-alt-tunnel/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-opsawg-capwap-alt-tunnel-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-capwap-alt-tunnel-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 Mon Oct 19 09:46:22 2015
Return-Path: <prvs=77346405dc=uri@ll.mit.edu>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922411A8A75 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 09:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FUZZY_CREDIT=1.678, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, 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 8DQNUcVoDpax for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 09:46:18 -0700 (PDT)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id BF5FD1A8A79 for <opsawg@ietf.org>; Mon, 19 Oct 2015 09:46:18 -0700 (PDT)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id t9JGhpIu014587; Mon, 19 Oct 2015 12:46:16 -0400
From: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
Thread-Index: AQHRChlVKo8M4jljT0KQAGjg6aSJVJ5zBqCA
Date: Mon, 19 Oct 2015 16:44:37 +0000
Message-ID: <D24A9604.20C16%uri@ll.mit.edu>
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com>
In-Reply-To: <56245AE1.405@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.5.5.150821
x-originating-ip: [172.25.177.187]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3528103465_145400752"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33,  0.0.0000 definitions=2015-10-19_14:2015-10-15,2015-10-19,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1510190287
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/07HLdXir34YbYVMOUxrRGw0ujIg>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 16:46:20 -0000

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

On 10/18/15, 22:52 , "OPSAWG on behalf of Brian E Carpenter"
<opsawg-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:

>Hmm. I've finally made time to read this draft, to find out what the
>fuss is about...

:-)

>Overall, this draft seems to me to be an opinion piece. That's fine of
>course,
>everyone is entitled to state their opinion, but I'm not sure that it
>helps
>the IETF to know what to do next. It reads more like a CCR editorial
>article
>or an Independent Submission RFC.

+1

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

MIIQ0AYJKoZIhvcNAQcCoIIQwTCCEL0CAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGggg6fMIIE6jCCA9KgAwIBAgIKE5SxSwAAAABE8TANBgkqhkiG9w0BAQsFADBRMQswCQYD
VQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJ
MRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1MDYxNTE2MjQzOVoXDTE2MDYxNDE2MjQzOVow
YTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNV
BAsTBlBlb3BsZTEgMB4GA1UEAxMXQmx1bWVudGhhbC5VcmkuNTAwMTA1ODQwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQC0tVFZOYvbDipiXfjylg0yIORem8AMZ4UQJ7EM2BI8
jKLj/h3RwH4w2DOMdepALLUqscSrpX6HPbo80M1O0cSSIYcYl8wQzDAMmvoD3HWbupwSXEPf
eRtBo26jAvsDkOp46TPu40Pu61AkHx4vIgqU7XkofKhow18Ka/9ZkJ+oSnLK6Xy9+n8JiViO
kTm2NjyF+CcpAobwZ3lBepHihvK3EilYR6V1EHQb+Y+2aWtexkFzBNXaN7i4Sdzq+LNSzCON
DDDnRxA2c/B/p7MBDzocaigPxmKOHcE5eamxCgpJEUVCEALzeVZxcYURDJw68tZ90pJSLuw7
r6iigykQbRINAgMBAAGjggGyMIIBrjAdBgNVHQ4EFgQUQzxm8xAhtcoaGyRStaMMhrmd7/Mw
DgYDVR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1Ud
HwQsMCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYB
BQUHAQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExD
QTMwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3
FQcEMDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAi
BgNVHSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3
EgIBAwEIMBkGA1UdEQQSMBCBDnVyaUBsbC5taXQuZWR1MCcGCSsGAQQBgjcUAgQaHhgATABM
AFUAcwBlAHIAUwBpAGcALQBTAFcwDQYJKoZIhvcNAQELBQADggEBAI8vbC+RZJEH0jhe5e9w
F18xYCquDo5kxkoD83qYcVPVFYPnjuAvZ6o9ENa3F0GiAjFVm6HcUbm0zeWT6ZDYIrbh7GRM
4IO8pD9ziwvLIx8rvLvUhiBpsZvznVOWX1yGC0UkIKyiseAszczAYFVJonKB8jDRnxgFlPlo
mFUaDtjL86cyp+pHc+ffUVyqMxacABFutJJ72HcK7tIf2gnh2qLdKToiTkDIWT+b1RrkQPSr
Gr0YapAC5PgHd/RRY75FHdW/OEQOFimouKnBc5F2VsDJg0Ae9i0+nJPWwSpoXe0ISqIUMO47
Ei6ySfHR2mjymbByxmT5W3gAT3M2gyOd/XUwggS8MIIDpKADAgECAgEpMA0GCSqGSIb3DQEB
BQUAMFQxCzAJBgNVBAYTAlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQww
CgYDVQQLEwNQS0kxFjAUBgNVBAMTDU1JVExMIFJvb3QgQ0EwHhcNMTMxMjE3MDAwMDAwWhcN
MjAxMjMxMjM1OTU5WjBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFi
b3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2jBSdW18tuW1tNxG6h8B0kqckFZQAAtoHCkvUpUEX6jF
vBd8mQI53GyLYRuAo4HWJpe7/izFXOfSJDs6UM5ovvCOfXg2bJgDYlBC9JDcLBFIn0nppOu9
RvpjWSixtC56crwJ5Us5QPdtxtKdek5LJXl2oKw3w8lihUixePbxWad1m7ZMKKagvm9zTybP
6FumKRxeYJjSpB2+cAYjoGGEbSVHyx8uzHm6xAoBMHxa8by+yDz8Jzk6sP9iilgP3iXSGoCA
mhyBzvlQQ5QNNWP+Emo9jz/ukKhYVB/VwdxtoquPAqn4ifDAIaM9dtb05cy1gXAFSP3Z/iUk
xyBZZUORfwIDAQABo4IBmjCCAZYwEgYDVR0TAQH/BAgwBgEB/wIBADAdBgNVHQ4EFgQU12Bm
DntJjXVMDf3PRt7IxxKHyr8wHwYDVR0jBBgwFoAUZ6p6z/QKprlytYqg0p3yEMND7SkwDgYD
VR0PAQH/BAQDAgGGMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0cDovL2NybC5s
bC5taXQuZWR1L2dldHRvP0xMUkNBMCcGCCsGAQUFBzABhhtodHRwOi8vb2NzcC5sbC5taXQu
ZWR1L29jc3AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC5sbC5taXQuZWR1L2dldGNy
bD9MTFJDQTCBkgYDVR0gBIGKMIGHMA0GCyqGSIb3EgIBAwEGMA0GCyqGSIb3EgIBAwEIMA0G
CyqGSIb3EgIBAwEHMA0GCyqGSIb3EgIBAwEJMA0GCyqGSIb3EgIBAwEKMA0GCyqGSIb3EgIB
AwELMA0GCyqGSIb3EgIBAwEOMA0GCyqGSIb3EgIBAwEPMA0GCyqGSIb3EgIBAwEQMA0GCSqG
SIb3DQEBBQUAA4IBAQAsf9HBn72qU7UTgkxarjAc7iynhcDEgWwezYKtd/SLGSQ0DhtzIV/L
TCxqULjOd+H+HTqMJXB8+nHnzhyqQ43RsnGZOFT5RfzPh94db/ZJ3ql244DwlJI7yXBA2DkZ
cEEgOWC9bHcrElzU6NnigahSW5odVJrhmH/XhQAcMS77E5H62yyxK1WPPgcBipGVnu1xSHbT
iHe7DqfWQ2tVMLUf23XYhIua94kJsQd4jSh71NVD0e7F4snAoqQMI98MzDYeLOkjlzKRs77r
/aMsPAKx6nMaOvRL7Cy0Pjp51i2qFkbGmX8ofnh2kerjTTvRJ/g22r1MV8RR1PktjMsNOsPf
MIIE7TCCA9WgAwIBAgIKKHB6MgAAAAAtBzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJV
UzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYD
VQQDEwpNSVRMTCBDQS0zMB4XDTE1MDEyMzE3NDkyOVoXDTE2MDEyMzE3NDkyOVowYTELMAkG
A1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBl
b3BsZTEgMB4GA1UEAxMXQmx1bWVudGhhbC5VcmkuNTAwMTA1ODQwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQDF+Rcs9hNO5hvlE0YeltqeXGUW1u3RVMG4/2ag6J2FgcsOJxOZ
y/m+7FeYfCo3XYrNqx6/3IZmDSYln3JnxzPionDcbK2TJ9xAOoWlrUykAhgUl+PCO8ahDV5Y
c0tmMzf5MXBrsub0nUyJeDkxOUY2Id58D1UVzzXh9Kvjc+ZCcBRFoViAgn7MznnuvK8Y5m7L
or1oLWSxNNUyp98gC4EpdHLnA8yP1WqmNr0x+YssjJgEiIfZFqx8Gvv2OqtHaFGHh7Y6+WOW
IZULMaAc9JJEq8ctns9mGIRldf2JMFcNsahQJDhgUspmP6c1Wz9OrUxsgwnGQ5feIq9c/4YZ
YEZ/AgMBAAGjggG1MIIBsTAdBgNVHQ4EFgQUR0hebk4i6063YnpEEVXyQUyfSFMwDgYDVR0P
AQH/BAQDAgUgMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQsMCow
KKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUHAQEE
WjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMwJwYI
KwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcEMDAu
BiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2F69Bwg+vtIAIBZAIBBDAlBgNVHSUE
HjAcBgRVHSUABggrBgEFBQcDBAYKKwYBBAGCNwoDBDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMBkGA1UdEQQSMBCBDnVyaUBsbC5taXQuZWR1MCcGCSsGAQQBgjcUAgQaHhgATABMAFUA
cwBlAHIARQBuAGMALQBTAFcwDQYJKoZIhvcNAQELBQADggEBADim5zjTb/h3ea/66DNM6wSm
i1Ti9F2f2/Are2a7a9E/IPXfleh39lVG7uTaneEJMSHzDltkB5k6DYMv/t28ntQm2jLI9adM
wccDlKSR2uIDsiA7jodiTxbqL/aRi+WC4ybWWhXuzSbkMesayt5QAKpuKLAr7newfZaWx8zP
nWU1nWZBbJR7cLKgUTaEiQu/NlCWIFJIC9yRhze+KR41vIa+7niQnUANjoYCCu32Z8xgxhK4
kQr5teUVUNDoCj02x781GFfwCknxpsWEm95OWM1iaXKCGJ8ciioulEzksZUrIHdImISaQVV+
Xdmbcd3OH6y8fNl1mZdXn8sxNJc+/g0xggH1MIIB8QIBATBfMFExCzAJBgNVBAYTAlVTMR8w
HQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNVBAMT
Ck1JVExMIENBLTMCChOUsUsAAAAARPEwDQYJYIZIAWUDBAIBBQCgaTAvBgkqhkiG9w0BCQQx
IgQgqVvXKq581Htt2lGDSN2QhuYv1jjIqeoTp8z6v1b0o9YwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTUxMDE5MTY0NDI1WjANBgkqhkiG9w0BAQEFAASC
AQB374otjtZb45ZxGLHhD8TF23bcOY7HZujia4ONEbLVHyqKmg8m1yxN9ZC48chGO/WK1aQm
hJ+625SFCHGVMLdX8np/+fjpmL7VvjiJcP7EnQwerbjFznzIz8SeS/LW13d4EV5AqZPpnmw5
v+yVQ5hITCt6YmzyyCI4XPyC8sD3ErxaqRlAUH3B+yi4YjQBFw8CujJZxHFbzj/417tJVbbi
mLf839YZ+1AiNJGqMMHajSKeoYDAhj8d/qIBeOgu8NOEgekD4uV+39MLrZt5zEqQW0IIQN5g
2fnTHQ4q1MObeXsC/zzwjee1oxGFpyg95/j284TYwEI415Yt9fTCWR5B

--B_3528103465_145400752--


From nobody Mon Oct 19 16:16:38 2015
Return-Path: <marka@isc.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 639321B2E42 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 16:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.233
X-Spam-Level: 
X-Spam-Status: No, score=-0.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FUZZY_CREDIT=1.678, 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 G3JoTb47LroX for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 16:16:36 -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 EC86D1B2E12 for <opsawg@ietf.org>; Mon, 19 Oct 2015 16:16:35 -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 69B581FCC40; Mon, 19 Oct 2015 23:16:32 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B4EEE16003F; Mon, 19 Oct 2015 23:16:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9337716008B; Mon, 19 Oct 2015 23:16:36 +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 IPnGvJumooLo; Mon, 19 Oct 2015 23:16:36 +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 37B3616003F; Mon, 19 Oct 2015 23:16:36 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id CB57D3AC7EDB; Tue, 20 Oct 2015 10:16:28 +1100 (EST)
To: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
From: Mark Andrews <marka@isc.org>
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com> <D24A9604.20C16%uri@ll.mit.edu>
In-reply-to: Your message of "Mon, 19 Oct 2015 16:44:37 -0000." <D24A9604.20C16%uri@ll.mit.edu>
Date: Tue, 20 Oct 2015 10:16:28 +1100
Message-Id: <20151019231628.CB57D3AC7EDB@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/cLBeX0Zu2uOA__oZe4KpEmcUW8M>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 23:16:37 -0000

In message <D24A9604.20C16%uri@ll.mit.edu>, "Blumenthal, Uri - 0553 - MITLL" wr
ites:
> 
> On 10/18/15, 22:52 , "OPSAWG on behalf of Brian E Carpenter"
> <opsawg-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:
> 
> >Hmm. I've finally made time to read this draft, to find out what the
> >fuss is about...
> 
> :-)
> 
> >Overall, this draft seems to me to be an opinion piece. That's fine of
> >course,
> >everyone is entitled to state their opinion, but I'm not sure that it
> >helps
> >the IETF to know what to do next. It reads more like a CCR editorial
> >article
> >or an Independent Submission RFC.
> 
> +1
> 

Actually it gives good advice to firewall vendors.  In many cases
they do more harm than good by not actually understanding the
protocols that they inspect.  They block extension unnecessarially.

We design a protocol to be future proof and the firewall vendors
stuff up that design for no reason beyond paranoia.

Take the DNS and the handling of EDNS versions > 0.  These were
thought about when EDNS was designed.  There is a specific error
code to be returned BADVERS along with the highest version if EDNS
the server supports.  The client then retries using a common version
of EDNS.  There is NOTHING here that should concern a firewall
vendor.

What do firewall vendors do?  They code the firewall to drop packets
with EDNS version > 0.  This is despite EDNS aware servers having
explict instructions on how to handle these packets.  If the server
doesn't understand EDNS it doesn't matter if the version is 0 or > 0
as it still noise to the nameserver that doesn't understand EDNS.  It
will either ignore the OPT record completely or return FORMERR.

There is no case to be made for dropping these packets.

When one actually wants to use the capabilities we built into the
protocol one then has to fight the firewalls even to get the packet
delivered.  Cleaning out old/broken firewalls takes decades.

Got to https://ednscomp.isc.org/compliance/summary.html and look
at the firewall graphs to see how much damage firewalls are doing
to the DNS for no good reason.  We have mostly removed the broken
firewalls from in front of the TLD servers.

I have no problem with a firewall block a extension temporarially
if it protecting from a known defect in a product while that product
is getting fixed.  They just shouldn't be blocked by default.

One can test products to ensure that they handle packets with
extensions and get the defects fixed.  Most defects are benign and
you will see a lot of them if you look at
https://ednscomp.isc.org/compliance/summary.html but again they can
be fixed.  We have got most of those in the servers the TLD operators
are running fixed.  In doing this testing I've not seen a single
case of a server being knocked over.

Defects like ignoring the EDNS version.  Returning FORMERR to well
formed packets.  Incorrectly copying fields from the request to the
response or I suspect not clearing a fields when turning the request
packet into a response packet.  But you can't get these defects
fixed unless you can see them.

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


From nobody Mon Oct 19 16:55:27 2015
Return-Path: <melinda.shore@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5B51ACEB6 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 16:55:26 -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 ewTtUSceXBDm for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 16:55:25 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::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 D723D1ACE66 for <opsawg@ietf.org>; Mon, 19 Oct 2015 16:55:24 -0700 (PDT)
Received: by pabrc13 with SMTP id rc13so1375586pab.0 for <opsawg@ietf.org>; Mon, 19 Oct 2015 16:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GkwDp0MIgN94b0N6ISW3/ekYCO8G/kB+pzwUgjo859E=; b=JnKwI7iFBd4qG7784sxqT4qYNXx0U//bXAhA0vBeXhXZnoF1srR6CITgmzKOAyTiYB v9yj3El8QRGMUKx0y31mhyGXlWriY54qG56RHhnYMdURy31sOOM3LFYmvPIH8jJQ7uKL 8177DSq7j6mc2VWrouqQdVjPONT56JCqlOu7mISUUjxhpStbc5s5IJh7FPEOdhwKn4dl Ci8tSq9IFJ33scQJx97poxmalY5cJfwbr1nGREi+kMCm4A9ONpbBmk+elYmZ98yR17KC qD1rRPKEy5yfJ0Gr4LhNmrHetS5VJt1XSg3x7PSmBpLiDHsYW1FqLNxTy/W0zJZI24Oo hIUg==
X-Received: by 10.68.239.33 with SMTP id vp1mr157164pbc.167.1445298924534; Mon, 19 Oct 2015 16:55:24 -0700 (PDT)
Received: from spandex.local (63-140-87-154-radius.dynamic.acsalaska.net. [63.140.87.154]) by smtp.gmail.com with ESMTPSA id im9sm172024pbc.1.2015.10.19.16.55.23 for <opsawg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Oct 2015 16:55:24 -0700 (PDT)
Message-ID: <562582EA.4030301@gmail.com>
Date: Mon, 19 Oct 2015 15:55:22 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: opsawg@ietf.org
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com> <D24A9604.20C16%uri@ll.mit.edu> <20151019231628.CB57D3AC7EDB@rock.dv.isc.org>
In-Reply-To: <20151019231628.CB57D3AC7EDB@rock.dv.isc.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/vBTkHWawh7eDbRY5Y4wbP14uBxI>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2015 23:55:26 -0000

On 10/19/15 3:16 PM, Mark Andrews wrote:
> When one actually wants to use the capabilities we built into the
> protocol one then has to fight the firewalls even to get the packet
> delivered.  Cleaning out old/broken firewalls takes decades.

Right, but vendors do love their firewalls.  It can take an
inordinately long time to get IETF documents out (longer than
it takes to design and implement a product feature) and vendors
are likely to release products that break DNS before a firewalls
draft is done.

I've been watching this discussion and getting a strong sense
of déjà vu, and I think this is going to be a difficult document
to get through the IETF process.  It may be preferable, anyway,
to focus on a series of protocol- or application-specific
firewall problems documents - for example, to move a firewall
considerations for DNS document to dnsop.  It may be the only
way to get consensus about content.

Melinda



From nobody Mon Oct 19 17:39:01 2015
Return-Path: <marka@isc.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEF291B2F74 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 17:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 JgZnKtjeDTls for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 17:38:58 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD9641B2B71 for <opsawg@ietf.org>; Mon, 19 Oct 2015 17:38:58 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id 140DE349315; Tue, 20 Oct 2015 00:38:57 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 92D6116003F; Tue, 20 Oct 2015 00:39:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 81DFE16008B; Tue, 20 Oct 2015 00:39:02 +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 99IJ9ct2i1gx; Tue, 20 Oct 2015 00:39:02 +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 2BFD816003F; Tue, 20 Oct 2015 00:39:02 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 8E74D3AC85D6; Tue, 20 Oct 2015 11:38:24 +1100 (EST)
To: Melinda Shore <melinda.shore@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com> <D24A9604.20C16%uri@ll.mit.edu> <20151019231628.CB57D3AC7EDB@rock.dv.isc.org> <562582EA.4030301@gmail.com>
In-reply-to: Your message of "Mon, 19 Oct 2015 15:55:22 -0800." <562582EA.4030301@gmail.com>
Date: Tue, 20 Oct 2015 11:38:24 +1100
Message-Id: <20151020003824.8E74D3AC85D6@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/bWkmNQ0z3fyDoDxFKDJHVwHbnYo>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 00:39:00 -0000

In message <562582EA.4030301@gmail.com>, Melinda Shore writes:
Input error
> On 10/19/15 3:16 PM, Mark Andrews wrote:
> > When one actually wants to use the capabilities we built into the
> > protocol one then has to fight the firewalls even to get the packet
> > delivered.  Cleaning out old/broken firewalls takes decades.
>
> Right, but vendors do love their firewalls.  It can take an
> inordinately long time to get IETF documents out (longer than
> it takes to design and implement a product feature) and vendors
> are likely to release products that break DNS before a firewalls
> draft is done.

We will be, DNS COOKIES support will be released early next year
and yes we will hit firewalls that block EDNS queries with unknown
options along with all the other breakage out there.  Somewhere
around 90% of servers will return good answers to those queries.
A couple of percent will be blocked by firewalls.  If the servers
behind those firewalls are serving signed zones then DNS lookups
for those zones *will* fail if the recursive server is validating.
Similarly if they return FORMERR.  Some of the errors are benign
to DNS COOKIES.

Despite the fact that we will be doing this I still think that a
document on firewalls should go ahead.

I also have draft-andrews-dns-no-response-issue which looks at DNS
server misbehaviour and it covers all of these areas.  I've had
feedback that the IETF shouldn't be asking TLD operators to be good
network citizens by running checks on the delegated servers and
informing their operators that they are broken.  I've also had
feedback saying "when are you publishing, this is good stuff".

Mark

> I've been watching this discussion and getting a strong sense

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


From nobody Mon Oct 19 18:04:58 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED7B1B2F8C; Mon, 19 Oct 2015 18:04:57 -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 R4hLJ9LjJVNA; Mon, 19 Oct 2015 18:04:55 -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 2AFED1B2F8B; Mon, 19 Oct 2015 18:04:55 -0700 (PDT)
Received: from [181.46.190.53] (helo=[172.16.17.13]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1ZoLMA-0000iy-0D; Tue, 20 Oct 2015 03:04:50 +0200
To: Rick Casarez <rick.casarez@gmail.com>
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com> <561D0CB7.3040606@si6networks.com> <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com> <562155BC.6030701@si6networks.com> <CAGWMUT686GhqGQ+H4McBXy7mmDChPQJH2kDzU_SNQAceFCucUA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <562590A5.90802@si6networks.com>
Date: Mon, 19 Oct 2015 21:53:58 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAGWMUT686GhqGQ+H4McBXy7mmDChPQJH2kDzU_SNQAceFCucUA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/gpSrH1IJsFaR9aVm1YCQKROqqLg>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, Internet Area <int-area@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 01:04:57 -0000

Hi, Rick,

On 10/18/2015 09:35 AM, Rick Casarez wrote:
> Just trying to help. Answers in line.

Indeed -- and that's really appreciated!



>     > In Section 2:
>     >
>     > Firewall - I am wondering if a better definition can be made. From
>     what
>     > you wrote I cannot distinguish between a Firewall and an ACL.
> 
>     An ACL is a policy. A firewall is a device that enforces filtering
>     policies.
> 
> [Rick] Your definition would encompass routers and switches who have
> ACL/Filters on interfaces/SVIs. I would not consider these firewalls.

Well, that's a firewalling functionality. From a strict point of view, a
router does not really drop offending packets, but just forwards them.



>     > No mention
>     > of state tracking for instance etc.
> 
>     Ok, will try to add somethin in this respect.
> 
> [Rick] Please do, as Ca mentions this is how the vast majority of the
> world define it as. This even includes common compliance audits like
> PCI/SOC etc.

Question: WOuld you include this as part of the fw definition, or rather
e.g. simply define "state-tracking"?



>     > Section 5.1:
>     >
>     > "The drawback of this approach is that the security goal of "block
>     > traffic unless it is explicitly allowed" prevents useful new
>     applications."
>     >
>     > I am not sure I understand this line. It blocks new applications from
>     > immediately traversing the firewall. I know from experience though
>     that
>     > when a discussion is had with the NetSec team the application can be
>     > added to the allow list. So not sure a "default deny" means new stuff
>     > never gets allowed as the text insinuates.
> 
>     Well, that depends on where the firewall is being deployed, and if it is
>     actively managed.
> 
> [Rick] I am unaware of any firewall deployed that is no longer managed.

I'm told that comcast does currently deploys this sort of boxes for
their IPv6 residential customers.

And I'd argue that anything that is deployed at the home mostly follows
into this category...



>     > Section 6:
>     >
>     > There are temporary IPv4 addresses too.
> 
>     Not by definition I'd say. Or... would you mind elaborating a bit more
>     in this respect?
> 
>  [Rick] My apologies on this one got some wires crossed. This is good to go.

Thanks for double-checking!



>     > As for application being tunneled over well-known ports that
>     sounds like
>     > a breakdown of communication between the Service Owners and NetSec.
>     > Simple communication *should* lead to the creation of a profile
>     for that
>     > new application and its individual port. By doing what you describe it
>     > sounds like a Service Owner trying to get out of doing due diligence
>     > with NetSec or not knowing what port their application needs for
>     access
>     > (More common than you might think).
> 
>     Yes. Or, at times, a user/app trying to circumvent unmanaged firewalls.
>     -- Ironically, at times these protocols are referred to as "firewall
>     friendly".
>  
>  [Rick] The scenario makes no sense other than a mismanaged company
> frankly. You are essentially encouraging something against BCP. Even
> beyond security you will make it difficult to troubleshoot if everything
> is using the same port to traverse the firewall.

WeÂ¿re not talking about companies, but about e.g. about firewalls
deployed at homes, and applications meant to be employed by such users.

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 Oct 19 18:05:08 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B831B2F9B for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 18:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.224
X-Spam-Level: 
X-Spam-Status: No, score=-0.224 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FUZZY_CREDIT=1.678, SPF_HELO_PASS=-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 FVjQ7VIQnrgG for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 18:05:00 -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 E19EC1B2F95 for <opsawg@ietf.org>; Mon, 19 Oct 2015 18:04:59 -0700 (PDT)
Received: from [181.46.190.53] (helo=[172.16.17.13]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1ZoLMF-0000jN-Ni; Tue, 20 Oct 2015 03:04:56 +0200
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, opsawg@ietf.org
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5625934B.4070006@si6networks.com>
Date: Mon, 19 Oct 2015 22:05:15 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56245AE1.405@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/j01-2qL-fgyCVEkdvpb6dcHw3_U>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 01:05:01 -0000

Hi, Brian,

Thanks so much for your feedback! Please find my comments in-line...

On 10/18/2015 11:52 PM, Brian E Carpenter wrote:
> Hmm. I've finally made time to read this draft, to find out what the
> fuss is about...
> 
> Firstly, I have to find a polite way of saying... well, I can't, so
> here it is: delete the Introduction and try again. I think the present
> text is guaranteed to annoy just about everybody, and evidently it will
> not "end the bickering."

Point taken. The intro will be replaced. While we're past the I-D
submission cutoff, I'll craft replacing text and post it here for review.



> (I gave my own potted history of security in the IETF in the plenary
> at IETF 88, slides 2-4.)

Thanks for the pointer. I will go through it.



> Then, I can see 12 RFCs in the index whose titles include the word 'firewall'
> and that only scratches the surface; there are literally hundreds of references
> to firewalls in existing RFCs. IMHO, if this draft aims to survey the field,
> it needs to survey the IETF and non-IETF literature much better (perhaps as
> an appendix).

Will do.



> Overall, this draft seems to me to be an opinion piece. That's fine of course,
> everyone is entitled to state their opinion, but I'm not sure that it helps
> the IETF to know what to do next. It reads more like a CCR editorial article
> or an Independent Submission RFC.

Among other things, I think it is useful in implicitly noting areas
where further work is needed.



> To some more specific comments:
> 
> Section 4.1 seems to increase rather than decrease the popular confusion
> between firewall functions and NAT functions. I would prefer to see
> NAT described in a separate section *as a side issue*. NAT failure modes
> are not the same as firewall failure modes.

I think that people confuse NAT device vs. NAT functionality.

A NAT device enforces, as a side effect, a diode-firewall (only allow
return traffic) functionality. Address Translation itself has nothing to
do with firewalling, but the side a effect does.

That said, we'll move the NAT stuff to a separate section. Other folks
seem to share your opinion, too.


> Section 4.3 cites draft-vyncke-advanced-ipv6-security, which is very dead
> as far as I can tell. I don't think we should be citing dead work
> in a current IETF draft.

Point taken. Although they might revise soon -- we'll remove or keep it
based on what they do about 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 Mon Oct 19 18:17:53 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCEE1AD0B6 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 18:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 OXRUaxaPbZS1 for <opsawg@ietfa.amsl.com>; Mon, 19 Oct 2015 18:17:49 -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 C617A1B2A29 for <opsawg@ietf.org>; Mon, 19 Oct 2015 18:17:48 -0700 (PDT)
Received: from [181.46.190.53] (helo=[172.16.17.13]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1ZoLYd-0000sg-SL; Tue, 20 Oct 2015 03:17:44 +0200
To: Melinda Shore <melinda.shore@gmail.com>, opsawg@ietf.org
References: <20151013134530.1812.97650.idtracker@ietfa.amsl.com> <56245AE1.405@gmail.com> <D24A9604.20C16%uri@ll.mit.edu> <20151019231628.CB57D3AC7EDB@rock.dv.isc.org> <562582EA.4030301@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56259652.1000409@si6networks.com>
Date: Mon, 19 Oct 2015 22:18:10 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <562582EA.4030301@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ce56ZksgCttf4GCYJKfegav8t-w>
Subject: Re: [OPSAWG] I-D Action: draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 01:17:51 -0000

Hi, Melinda,

Thanks so much for your feedback! Please find my comments in-line....

On 10/19/2015 08:55 PM, Melinda Shore wrote:
> On 10/19/15 3:16 PM, Mark Andrews wrote:
>> When one actually wants to use the capabilities we built into the
>> protocol one then has to fight the firewalls even to get the packet
>> delivered.  Cleaning out old/broken firewalls takes decades.
> 
> Right, but vendors do love their firewalls.  It can take an
> inordinately long time to get IETF documents out (longer than
> it takes to design and implement a product feature) and vendors
> are likely to release products that break DNS before a firewalls
> draft is done.

I think that even with some of the content that we have, plus more
specific stuff (possibly in separate document(s)), at least we have
something to point vendors at.



> I've been watching this discussion and getting a strong sense
> of déjà vu, and I think this is going to be a difficult document
> to get through the IETF process.  It may be preferable, anyway,
> to focus on a series of protocol- or application-specific
> firewall problems documents - for example, to move a firewall
> considerations for DNS document to dnsop.  It may be the only
> way to get consensus about content.

The goal of this document is, to some extent, mostly a high-level
discussion. More detailed stuff should probably be done in separate
documents, and just referenced from this one to keep the problem
"tractable".

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 Tue Oct 20 01:40:53 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC57A1B2E33 for <opsawg@ietfa.amsl.com>; Tue, 20 Oct 2015 01:40:51 -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 CWpKBb7ZYd5l for <opsawg@ietfa.amsl.com>; Tue, 20 Oct 2015 01:40:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id A5DFC1B2E28 for <opsawg@ietf.org>; Tue, 20 Oct 2015 01:40:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A3997187DBF; Tue, 20 Oct 2015 01:40:19 -0700 (PDT)
To: johannes.merkle@secunet.com, manfred.lochter@bsi.bund.de, bclaise@cisco.com, joelja@bogus.com, warren@kumari.net, sob@sobco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151020084019.A3997187DBF@rfc-editor.org>
Date: Tue, 20 Oct 2015 01:40:19 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/bLJevobfCXrLEUqFgc1-bZOPFqc>
Cc: opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: [OPSAWG] [Technical Errata Reported] RFC7630 (4509)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 08:40:52 -0000

The following errata report has been submitted for RFC7630,
"HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7630&eid=4509

--------------------------------------
Type: Technical
Reported by: Johannes Merkle <johannes.merkle@secunet.com>

Section: 8 and 10

Original Text
-------------
snmpModules 235

Corrected Text
--------------
mib-2 235

Notes
-----
IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by the MIB doctors), but the document mentions snmpModules.235

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. 

--------------------------------------
RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
--------------------------------------
Title               : HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
Publication Date    : October 2015
Author(s)           : J. Merkle, Ed., M. Lochter
Category            : PROPOSED STANDARD
Source              : Operations and Management Area Working Group
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG


From nobody Tue Oct 20 02:13:40 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA821B300A; Tue, 20 Oct 2015 02:13:35 -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 wZPPcDtRi7pY; Tue, 20 Oct 2015 02:13:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6A65C1B3006; Tue, 20 Oct 2015 02:13:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5C26A182534; Tue, 20 Oct 2015 02:12:58 -0700 (PDT)
To: johannes.merkle@secunet.com, johannes.merkle@secunet.com, manfred.lochter@bsi.bund.de
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151020091258.5C26A182534@rfc-editor.org>
Date: Tue, 20 Oct 2015 02:12:58 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/QO0ufu4nm3T13pEm_qdfEBhC2lQ>
Cc: opsawg@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [OPSAWG] [Errata Verified] RFC7630 (4509)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 09:13:35 -0000

The following errata report has been verified for RFC7630,
"HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7630&eid=4509

--------------------------------------
Status: Verified
Type: Technical

Reported by: Johannes Merkle <johannes.merkle@secunet.com>
Date Reported: 2015-10-20
Verified by: Benoit Claise (IESG)

Section: 8 and 10

Original Text
-------------
snmpModules 235

Corrected Text
--------------
mib-2 235

Notes
-----
IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by the MIB doctors), but the document mentions snmpModules.235 

--------------------------------------
RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
--------------------------------------
Title               : HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
Publication Date    : October 2015
Author(s)           : J. Merkle, Ed., M. Lochter
Category            : PROPOSED STANDARD
Source              : Operations and Management Area Working Group
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG


From nobody Tue Oct 20 02:13:55 2015
Return-Path: <philips.chenhao@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0E01B3013 for <opsawg@ietfa.amsl.com>; Tue, 20 Oct 2015 02:13: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 pM6RbMqblbY6 for <opsawg@ietfa.amsl.com>; Tue, 20 Oct 2015 02:13: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 2C82F1B3010 for <opsawg@ietf.org>; Tue, 20 Oct 2015 02:13:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BZA39965; Tue, 20 Oct 2015 09:13:38 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 20 Oct 2015 10:13:10 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.146]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0235.001; Tue, 20 Oct 2015 17:13:07 +0800
From: "Chenhao (philips)" <philips.chenhao@huawei.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: New Version Notification for draft-chen-opsawg-dcn-vn2pn-mapping-00.txt
Thread-Index: AQHRCk9qEzqfv+b+8UyPoagSeUhq2Z50AU4Q
Date: Tue, 20 Oct 2015 09:13:07 +0000
Message-ID: <15F8424C3FD6FE4FBC5651B784DBF82189C797C0@nkgeml503-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.160.235]
Content-Type: multipart/alternative; boundary="_000_15F8424C3FD6FE4FBC5651B784DBF82189C797C0nkgeml503mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/BXMC3y08hiH84Taa6Le_qAhxgJo>
Subject: [OPSAWG] FW: New Version Notification for draft-chen-opsawg-dcn-vn2pn-mapping-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 09:13:51 -0000

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

RGVhciBhbGwsDQoNCg0KDQpUaGlzIGlzIGEgbmV3IGRyYWZ0IGZvciBvcHNhd2cuIEl0IG1haW5s
eSBhbmFseXNpcyB0aGUgaXNzdWVzIGV4aXN0ZWQgaW4gZGVwbG95aW5nIHRoZSB2aXJ0dWFsIG5l
dHdvcmsgdG8gdGhlIHVuZGVybmVhdGggcGh5c2ljYWwgbmV0d29yayBpbiBEYXRhQ2VudGVyIG5l
dHdvcmsgLiBUaGUgYmFzaWMgaWRlYSBpcyB0byBhYnN0cmFjdCB0aGUgdW5kZXJuZWF0aCBwaHlz
aWNhbCBuZXR3b3JrIGFzIHNldmVyYWwgZmFicmljcywgd2hpY2ggY2FuIHByb3ZpZGUgdGhlIGZh
YnJpYyBzZXJ2aWNlcyB0byB0aGUgdXBwZXItbGF5ZXIgYXBwbGljYXRpb24vbmV0d29yayBhZG1p
bmlzdHJhdG9yLCB0byBmYWNpbGl0YXRlIHRoZSB3aG9sZSBjb25maWd1cmF0aW9uIHByb2NlZHVy
ZS4NCg0KDQoNCldlIHdvdWxkIGxpa2UgdG8gaGVhciB5b3VyIGNvbW1lbnRzLCB0aGFua3MuDQoN
Cg0KDQoNCg0KQmVzdCByZWdhcmRzLA0KDQpIYW8NCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmddDQpTZW50OiBNb25kYXksIE9jdG9iZXIgMTksIDIwMTUgNToyMSBQTQ0K
VG86IExpeWl6aG91OyBDaGVuaGFvIChwaGlsaXBzKTsgWGluZ2p1biBDaHU7IFlhcGVuZyBXdTsg
WWFwZW5nIFd1OyBMaXlpemhvdTsgQ2hlbmhhbyAocGhpbGlwcyk7IFhpbmdqdW4gQ2h1DQpTdWJq
ZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWNoZW4tb3BzYXdnLWRjbi12
bjJwbi1tYXBwaW5nLTAwLnR4dA0KDQoNCg0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFm
dC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZy0wMC50eHQNCg0KaGFzIGJlZW4gc3VjY2Vz
c2Z1bGx5IHN1Ym1pdHRlZCBieSBIYW8gQ2hlbiBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9z
aXRvcnkuDQoNCg0KDQpOYW1lOiAgICAgICAgICAgICAgIGRyYWZ0LWNoZW4tb3BzYXdnLWRjbi12
bjJwbi1tYXBwaW5nDQoNClJldmlzaW9uOiAgMDANCg0KVGl0bGU6ICAgICAgICAgICAgICAgICAg
VmlydHVhbCBOZXR3b3JrIHRvIFBoeXNpY2FsIE5ldHdvcmsgTWFwcGluZyBpbiBEYXRhQ2VudGVy
IE5ldHdvcmsNCg0KRG9jdW1lbnQgZGF0ZTogICAgICAgMjAxNS0xMC0xOA0KDQpHcm91cDogICAg
ICAgICAgICAgICBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCg0KUGFnZXM6ICAgICAgICAgICAgICAg
MTINCg0KVVJMOiAgICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZy0wMC50eHQNCg0KU3RhdHVzOiAg
ICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWNoZW4tb3BzYXdn
LWRjbi12bjJwbi1tYXBwaW5nLw0KDQpIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBwaW5nLTAwDQoNCg0KDQoN
Cg0KQWJzdHJhY3Q6DQoNCiAgIENsb3VkIHRlbmFudCBuZWVkcyB2aXJ0dWFsIG5ldHdvcmsgdG8g
aW50ZXJjb25uZWN0IHRoZWlyIFZNcyBvbg0KDQogICBzZXJ2ZXIuIEluIG9yZGVyIHRvIGVmZmVj
dGl2ZWx5IGFuZCBlZmZpY2llbnRseSBtYXAgdmlydHVhbCBuZXR3b3JrDQoNCiAgIHRvIHBoeXNp
Y2FsIG5ldHdvcmssIGNlcnRhaW4gbWVjaGFuaXNtIHNob3VsZCBiZSBlbXBsb3llZC4NCg0KDQoN
CiAgIFRoaXMgbWVtbyBhbmFseXNpcyB0aGUgZXhpc3RpbmcgVk4yUE4gbWFwcGluZyB0ZWNobmlx
dWUgZW1wbG95ZWQgaW4NCg0KICAgRGF0YUNlbnRlciBhbmQgcG9pbnQgb3V0IHRoZSBwb3RlbnRp
YWwgc2hvcnRjb21pbmdzIGxpZSBpbiBpdC4gVGhpcw0KDQogICBtZW1vIGFsc28gdHJ5IHRvIHBy
b3ZpZGUgYSBnZW5lcmljIG1lY2hhbmlzbSB0byBmYWNpbGl0YXRlIHRoZSBWTjJQTg0KDQogICBt
YXBwaW5nIGluIERhdGFDZW50ZXIgbmV0d29yay4NCg0KDQoNCg0KDQoNCg0KDQoNClBsZWFzZSBu
b3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9m
IHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWls
YWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3RpZnk7DQoJdGV4dC1qdXN0
aWZ5OmludGVyLWlkZW9ncmFwaDsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6Iue6r+aWh+acrCBDaGFyIjsN
CgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuNXB0
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9
DQpzcGFuLkNoYXINCgl7bXNvLXN0eWxlLW5hbWU6Iue6r+aWh+acrCBDaGFyIjsNCgltc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms657qv5paH5pysOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQovKiBQYWdlIERlZmluaXRpb25zICov
DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcy
LjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29y
ZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZd
LS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+
DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3ht
bD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2
bGluaz0icHVycGxlIiBzdHlsZT0idGV4dC1qdXN0aWZ5LXRyaW06cHVuY3R1YXRpb24iPg0KPGRp
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxh
bmc9IkVOLVVTIj5EZWFyIGFsbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoaXMgaXMgYSBu
ZXcgZHJhZnQgZm9yIG9wc2F3Zy4gSXQgbWFpbmx5IGFuYWx5c2lzIHRoZSBpc3N1ZXMgZXhpc3Rl
ZCBpbiBkZXBsb3lpbmcgdGhlIHZpcnR1YWwgbmV0d29yayB0byB0aGUgdW5kZXJuZWF0aCBwaHlz
aWNhbCBuZXR3b3JrIGluIERhdGFDZW50ZXIgbmV0d29yayAuIFRoZSBiYXNpYyBpZGVhIGlzIHRv
IGFic3RyYWN0IHRoZSB1bmRlcm5lYXRoIHBoeXNpY2FsDQogbmV0d29yayBhcyBzZXZlcmFsIGZh
YnJpY3MsIHdoaWNoIGNhbiBwcm92aWRlIHRoZSBmYWJyaWMgc2VydmljZXMgdG8gdGhlIHVwcGVy
LWxheWVyIGFwcGxpY2F0aW9uL25ldHdvcmsgYWRtaW5pc3RyYXRvciwgdG8gZmFjaWxpdGF0ZSB0
aGUgd2hvbGUgY29uZmlndXJhdGlvbiBwcm9jZWR1cmUuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij5XZSB3b3VsZCBsaWtlIHRvIGhlYXIgeW91ciBjb21tZW50cywgdGhhbmtzLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkJlc3QgcmVnYXJkcyw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+SGFv
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4N
CkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZ10gPGJyPg0KU2VudDogTW9uZGF5LCBPY3RvYmVyIDE5LCAyMDE1IDU6MjEgUE08YnI+
DQpUbzogTGl5aXpob3U7IENoZW5oYW8gKHBoaWxpcHMpOyBYaW5nanVuIENodTsgWWFwZW5nIFd1
OyBZYXBlbmcgV3U7IExpeWl6aG91OyBDaGVuaGFvIChwaGlsaXBzKTsgWGluZ2p1biBDaHU8YnI+
DQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWNoZW4tb3BzYXdn
LWRjbi12bjJwbi1tYXBwaW5nLTAwLnR4dDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1jaGVuLW9wc2F3Zy1kY24tdm4y
cG4tbWFwcGluZy0wMC50eHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+aGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRl
ZCBieSBIYW8gQ2hlbiBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj5OYW1lOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBkcmFmdC1j
aGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5SZXZpc2lvbjombmJzcDsgMDA8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+VGl0bGU6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IFZpcnR1YWwgTmV0d29yayB0byBQaHlzaWNhbCBOZXR3b3JrIE1hcHBpbmcgaW4gRGF0YUNl
bnRlciBOZXR3b3JrPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkRvY3VtZW50IGRhdGU6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IDIwMTUtMTAtMTg8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+R3JvdXA6Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IEluZGl2aWR1YWwgU3VibWlzc2lvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5QYWdlczombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgMTI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+VVJMOiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8YSBocmVmPSJo
dHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtY2hlbi1vcHNhd2ctZGNu
LXZuMnBuLW1hcHBpbmctMDAudHh0Ij4NCjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEO3RleHQt
ZGVjb3JhdGlvbjpub25lIj5odHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtY2hlbi1vcHNhd2ctZGNuLXZuMnBuLW1hcHBpbmctMDAudHh0PC9zcGFuPjwvYT48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+U3RhdHVzOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyA8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1jaGVuLW9w
c2F3Zy1kY24tdm4ycG4tbWFwcGluZy8iPg0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Q7dGV4
dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBwaW5nLzwvc3Bhbj48L2E+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkh0bWxp
emVkOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8YSBocmVmPSJodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY2hlbi1vcHNhd2ctZGNuLXZuMnBuLW1hcHBpbmct
MDAiPg0KPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Q7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFw
cGluZy0wMDwvc3Bhbj48L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+QWJzdHJhY3Q6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyBDbG91ZCB0ZW5hbnQgbmVlZHMgdmly
dHVhbCBuZXR3b3JrIHRvIGludGVyY29ubmVjdCB0aGVpciBWTXMgb248bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7
Jm5ic3A7IHNlcnZlci4gSW4gb3JkZXIgdG8gZWZmZWN0aXZlbHkgYW5kIGVmZmljaWVudGx5IG1h
cCB2aXJ0dWFsIG5ldHdvcms8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7Jm5ic3A7IHRvIHBoeXNpY2FsIG5ldHdv
cmssIGNlcnRhaW4gbWVjaGFuaXNtIHNob3VsZCBiZSBlbXBsb3llZC48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPiZuYnNwOyZuYnNwOyBUaGlzIG1lbW8gYW5hbHlzaXMgdGhlIGV4aXN0aW5nIFZO
MlBOIG1hcHBpbmcgdGVjaG5pcXVlIGVtcGxveWVkIGluPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyBE
YXRhQ2VudGVyIGFuZCBwb2ludCBvdXQgdGhlIHBvdGVudGlhbCBzaG9ydGNvbWluZ3MgbGllIGlu
IGl0LiBUaGlzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyBtZW1vIGFsc28gdHJ5IHRvIHByb3ZpZGUg
YSBnZW5lcmljIG1lY2hhbmlzbSB0byBmYWNpbGl0YXRlIHRoZSBWTjJQTjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJz
cDsmbmJzcDsgbWFwcGluZyBpbiBEYXRhQ2VudGVyIG5ldHdvcmsuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9
IkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBj
b3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0
bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoZSBJRVRGIFNlY3JldGFyaWF0PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_15F8424C3FD6FE4FBC5651B784DBF82189C797C0nkgeml503mbxchi_--


From nobody Tue Oct 20 02:23:45 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3913A1B3051 for <opsawg@ietfa.amsl.com>; Tue, 20 Oct 2015 02:23:44 -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 fXtyTbirSaVU for <opsawg@ietfa.amsl.com>; Tue, 20 Oct 2015 02:23:42 -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 7FEBB1B304E for <opsawg@ietf.org>; Tue, 20 Oct 2015 02:23:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7431; q=dns/txt; s=iport; t=1445333023; x=1446542623; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=YeaFsn2ov6P1CE//ioKFpb7eBvUsQ6+Ssw+9R7SgATM=; b=RjzGgVjNL2udXtSwiWTtyZOAGqS1dQM9yMwa2DPCTAFQqjTk8mF5C+Vx 4W1WL8eW3JjrmEmBwl07jwvlqVRmLbTno9PMvad2duHOGOlnsLyfc0/5l A0tUKMAudEqIEsk28tX16gNcjRLNGksa4GKIQ8R2kZ5yPnXWVnSea9GLY o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DOAQADByZW/xbLJq1EGoQKb7R7iR8BDYFaI4V7AoFwFAEBAQEBAQGBCoQuAQEEeAEQCyEWDwkDAgECAUUGAQwGAgEBBYgnDTvDRgEBAQEBAQEBAQEBAQEBAQEBAQEBARiGd4R+gT2DTAQHhC4Fhz6OZoUZiAaCIIZ4kwkfAQFCghENEIFXPDQBE4VTAQEB
X-IronPort-AV: E=Sophos;i="5.17,706,1437436800";  d="scan'208,217";a="612294725"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 20 Oct 2015 09:23:41 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t9K9NdTV004582; Tue, 20 Oct 2015 09:23:39 GMT
To: RFC Errata System <rfc-editor@rfc-editor.org>, johannes.merkle@secunet.com, manfred.lochter@bsi.bund.de
References: <20151020091258.5C26A182534@rfc-editor.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <56260809.9040501@cisco.com>
Date: Tue, 20 Oct 2015 11:23:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151020091258.5C26A182534@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------050909040904070407080004"
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/AtTYz86Q33MpN_oypd7o7asZw4Q>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] [Errata Verified] RFC7630 (4509)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 09:23:44 -0000

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

Dear all,

The facts:
- The MIB doctors advised not to publish MIB modules under snmpModules 
any longer. IANA updated the registry information. See 
http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-61
- RFC 7360 is published with a mistake. The MIB module should have been 
published under mib-2.235 (as advised by the MIB doctors) but the 
document mentions: snmpModules.235
- The IANA registry is actually correct. snmpUsmHmacSha2MIB is under 
mib-2.235
See http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml
- Solving this issue with an errata doesn't work: indeed MIB modules are 
extracted from RFC, and used within scripts.

Discussing with Michelle (IANA) and the IESG, we had no other choices 
than obsoleting this RFC and re-issuing a new one. Hence this errata and 
draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00. 
<http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new/>

One change to keep in mind for the next version:
OLD:

        REVISION    "201508130000Z"       -- 13 August 2015, midnight
        DESCRIPTION "Initial version, published asRFC 7630 <https://tools.ietf.org/html/rfc7630>"
    ::= { snmpModules 235 }

NEW:

        REVISION     ... new date
        DESCRIPTION "Initial version, published asRFC xxxx <https://tools.ietf.org/html/rfc7630>"
    ::= { mib-2 235 }

The way forward is to publish a new draft ASAP with the above 
correction, to have a one week IETF LC, and to publish the new RFC. At 
that point (and not before because we don't have a replacement RFC), we 
will obsolete RFC 7360.

Regards, Benoit
> The following errata report has been verified for RFC7630,
> "HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7630&eid=4509
>
> --------------------------------------
> Status: Verified
> Type: Technical
>
> Reported by: Johannes Merkle <johannes.merkle@secunet.com>
> Date Reported: 2015-10-20
> Verified by: Benoit Claise (IESG)
>
> Section: 8 and 10
>
> Original Text
> -------------
> snmpModules 235
>
> Corrected Text
> --------------
> mib-2 235
>
> Notes
> -----
> IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by the MIB doctors), but the document mentions snmpModules.235
>
> --------------------------------------
> RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
> --------------------------------------
> Title               : HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
> Publication Date    : October 2015
> Author(s)           : J. Merkle, Ed., M. Lochter
> Category            : PROPOSED STANDARD
> Source              : Operations and Management Area Working Group
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
> .
>


--------------050909040904070407080004
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">Dear all,<br>
      <br>
      The facts:<br>
      - The MIB doctors advised not to publish MIB modules under
      snmpModules any longer. IANA updated the registry information. See
      <a class="moz-txt-link-freetext"
href="http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-61">http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-61</a><br>
      - RFC 7360 is published with a mistake. The MIB module should have
      been published under mib-2.235 (as advised by the MIB doctors) but
      the document mentions: snmpModules.235<br>
      - The IANA registry is actually correct. snmpUsmHmacSha2MIB is
      under mib-2.235<br>
      See <a class="moz-txt-link-freetext"
        href="http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml">http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml</a><br>
      - Solving this issue with an errata doesn't work: indeed MIB
      modules are extracted from RFC, and used within scripts.<br>
      <br>
      Discussing with Michelle (IANA) and the IESG, we had no other
      choices than obsoleting this RFC and re-issuing a new one. Hence
      this errata and <a
href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new/">draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.</a><br>
      <br>
      One change to keep in mind for the next version:<br>
      OLD:<br>
      <pre class="newpage">       REVISION    "201508130000Z"       -- 13 August 2015, midnight
       DESCRIPTION "Initial version, published as <a href="https://tools.ietf.org/html/rfc7630">RFC 7630</a>"
   ::= { snmpModules 235 }</pre>
      NEW:<br>
      <pre class="newpage">       REVISION     ... new date
       DESCRIPTION "Initial version, published as <a href="https://tools.ietf.org/html/rfc7630">RFC xxxx</a>"
   ::= { mib-2 235 }
</pre>
      The way forward is to publish a new draft ASAP with the above
      correction, to have a one week IETF LC, and to publish the new
      RFC. At that point (and not before because we don't have a
      replacement RFC), we will obsolete RFC 7360.<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote cite="mid:20151020091258.5C26A182534@rfc-editor.org"
      type="cite">
      <pre wrap="">The following errata report has been verified for RFC7630,
"HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3". 

--------------------------------------
You may review the report below and at:
<a class="moz-txt-link-freetext" href="http://www.rfc-editor.org/errata_search.php?rfc=7630&amp;eid=4509">http://www.rfc-editor.org/errata_search.php?rfc=7630&amp;eid=4509</a>

--------------------------------------
Status: Verified
Type: Technical

Reported by: Johannes Merkle <a class="moz-txt-link-rfc2396E" href="mailto:johannes.merkle@secunet.com">&lt;johannes.merkle@secunet.com&gt;</a>
Date Reported: 2015-10-20
Verified by: Benoit Claise (IESG)

Section: 8 and 10

Original Text
-------------
snmpModules 235

Corrected Text
--------------
mib-2 235

Notes
-----
IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by the MIB doctors), but the document mentions snmpModules.235 

--------------------------------------
RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
--------------------------------------
Title               : HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
Publication Date    : October 2015
Author(s)           : J. Merkle, Ed., M. Lochter
Category            : PROPOSED STANDARD
Source              : Operations and Management Area Working Group
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG
.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050909040904070407080004--


From nobody Tue Oct 20 05:17:29 2015
Return-Path: <rick.casarez@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF311B3394; Tue, 20 Oct 2015 05:17:27 -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 ZLuXGdkCwHMx; Tue, 20 Oct 2015 05:17:24 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14E0D1B33A3; Tue, 20 Oct 2015 05:17:24 -0700 (PDT)
Received: by wicfx6 with SMTP id fx6so42615602wic.1; Tue, 20 Oct 2015 05:17:22 -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=5Mp4dMTWstIIjiRNPke2GkKSAKjrk+dV9yG9et6NeAQ=; b=P9bWEaSluWj6LwNoNZGu//96oPoLa1DsVMRD5SqO+gTk8eeGXymyf1+Bo52eVrDMUA IaIWcGJVkwqv/BUnBL859EBj3DH7JD49OmWQh2fdwy070a9N3CnNTFEuqEOSfS5N4Wyi z47nnIDfVFQZYPGdHz0glOXI8LkKs9g457z4Vf7Y/v1nekQWwxDsvLsjyoQm56ZYjTlz 7rCRNIAFKS27MgOn12FEluLZHCQOLq/XDtO/wh9Z+SQzwpwW03j302bvsZQ1LvbCFJG5 i6/3tEoPQ711Ayg6lPrMk4294a/Kl74cJdAdwIfFRkG4S2Fyri+fpneDdd5sz2nW7k9r oW/w==
MIME-Version: 1.0
X-Received: by 10.180.211.8 with SMTP id my8mr25676649wic.21.1445343442559; Tue, 20 Oct 2015 05:17:22 -0700 (PDT)
Received: by 10.27.108.76 with HTTP; Tue, 20 Oct 2015 05:17:22 -0700 (PDT)
In-Reply-To: <562590A5.90802@si6networks.com>
References: <20151013134530.1812.78498.idtracker@ietfa.amsl.com> <561D0CB7.3040606@si6networks.com> <CAGWMUT4A5Y=R6KN6oJdGzMOQJ=5aPUr8XJbEhZ3pBJ+hZD8_RA@mail.gmail.com> <562155BC.6030701@si6networks.com> <CAGWMUT686GhqGQ+H4McBXy7mmDChPQJH2kDzU_SNQAceFCucUA@mail.gmail.com> <562590A5.90802@si6networks.com>
Date: Tue, 20 Oct 2015 08:17:22 -0400
Message-ID: <CAGWMUT7ttM5DYZaDSrDdOaswvYmMBwfmMvLaa-dxY7pHWG31Qg@mail.gmail.com>
From: Rick Casarez <rick.casarez@gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a11c38e0e78eea50522883ee9
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/H1wq7mNGo9XuG4Ks-LEBl2fYNUE>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, Internet Area <int-area@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [OPSAWG] [v6ops] Fwd: New Version Notification for draft-gont-opsawg-firewalls-analysis-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 12:17:27 -0000

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

Hmm so maybe the problem is the scope of the draft. You seem to want to
cover home-based unmanaged CPE devices that have firewall functionality
built into them (Not dedicated firewalls as I recognize them). This is a
very specific definition of firewall and a specific type of deployment. If
you changed the introduction and scope to say you are only discussing this
specific type of hardware and deployment then a lot of the problems I have
with the text disappear.

If you however want this draft to cover firewalls in general then you have
to be aware of all the different ways they are deployed and maintained. You
also need to distinguish what separates a firewall from general L3/L4
access-control. I can tell you the industry does differentiate between the
two.

As for your statement that routers just route packets, that has not been
true for well over 18 years if not longer. ACLs/Filters on routing and
switching devices is not a new phenomenon.

Finally, to truly cover the subject you also have to at least mention the
things that have replaced dedicated firewalls for security at the Edge
(Load-balancers with built in Firewall functionality as an example) that
even PCI and SOC have accepted.
-------------------
Cheers, Rick

Experiences not things.

On Mon, Oct 19, 2015 at 8:53 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> Hi, Rick,
>
> On 10/18/2015 09:35 AM, Rick Casarez wrote:
> > Just trying to help. Answers in line.
>
> Indeed -- and that's really appreciated!
>
>
>
> >     > In Section 2:
> >     >
> >     > Firewall - I am wondering if a better definition can be made. Fro=
m
> >     what
> >     > you wrote I cannot distinguish between a Firewall and an ACL.
> >
> >     An ACL is a policy. A firewall is a device that enforces filtering
> >     policies.
> >
> > [Rick] Your definition would encompass routers and switches who have
> > ACL/Filters on interfaces/SVIs. I would not consider these firewalls.
>
> Well, that's a firewalling functionality. From a strict point of view, a
> router does not really drop offending packets, but just forwards them.
>
>
>
> >     > No mention
> >     > of state tracking for instance etc.
> >
> >     Ok, will try to add somethin in this respect.
> >
> > [Rick] Please do, as Ca mentions this is how the vast majority of the
> > world define it as. This even includes common compliance audits like
> > PCI/SOC etc.
>
> Question: WOuld you include this as part of the fw definition, or rather
> e.g. simply define "state-tracking"?
>
>
>
> >     > Section 5.1:
> >     >
> >     > "The drawback of this approach is that the security goal of "bloc=
k
> >     > traffic unless it is explicitly allowed" prevents useful new
> >     applications."
> >     >
> >     > I am not sure I understand this line. It blocks new applications
> from
> >     > immediately traversing the firewall. I know from experience thoug=
h
> >     that
> >     > when a discussion is had with the NetSec team the application can
> be
> >     > added to the allow list. So not sure a "default deny" means new
> stuff
> >     > never gets allowed as the text insinuates.
> >
> >     Well, that depends on where the firewall is being deployed, and if
> it is
> >     actively managed.
> >
> > [Rick] I am unaware of any firewall deployed that is no longer managed.
>
> I'm told that comcast does currently deploys this sort of boxes for
> their IPv6 residential customers.
>
> And I'd argue that anything that is deployed at the home mostly follows
> into this category...
>
>
>
> >     > Section 6:
> >     >
> >     > There are temporary IPv4 addresses too.
> >
> >     Not by definition I'd say. Or... would you mind elaborating a bit
> more
> >     in this respect?
> >
> >  [Rick] My apologies on this one got some wires crossed. This is good t=
o
> go.
>
> Thanks for double-checking!
>
>
>
> >     > As for application being tunneled over well-known ports that
> >     sounds like
> >     > a breakdown of communication between the Service Owners and NetSe=
c.
> >     > Simple communication *should* lead to the creation of a profile
> >     for that
> >     > new application and its individual port. By doing what you
> describe it
> >     > sounds like a Service Owner trying to get out of doing due
> diligence
> >     > with NetSec or not knowing what port their application needs for
> >     access
> >     > (More common than you might think).
> >
> >     Yes. Or, at times, a user/app trying to circumvent unmanaged
> firewalls.
> >     -- Ironically, at times these protocols are referred to as "firewal=
l
> >     friendly".
> >
> >  [Rick] The scenario makes no sense other than a mismanaged company
> > frankly. You are essentially encouraging something against BCP. Even
> > beyond security you will make it difficult to troubleshoot if everythin=
g
> > is using the same port to traverse the firewall.
>
> We=C2=BFre not talking about companies, but about e.g. about firewalls
> deployed at homes, and applications meant to be employed by such users.
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>

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

<div dir=3D"ltr"><div>Hmm so maybe the problem is the scope of the draft. Y=
ou seem to want to cover home-based unmanaged CPE devices that have firewal=
l functionality built into them (Not dedicated firewalls as I recognize the=
m). This is a very specific definition of firewall and a specific type of d=
eployment. If you changed the introduction and scope to say you are only di=
scussing this specific type of hardware and deployment then a lot of the pr=
oblems I have with the text disappear.<br><br></div>If you however want thi=
s draft to cover firewalls in general then you have to be aware of all the =
different ways they are deployed and maintained. You also need to distingui=
sh what separates a firewall from general L3/L4 access-control. I can tell =
you the industry does differentiate between the two. <br><br> <div class=3D=
"gmail_extra">As for your statement that routers just route packets, that h=
as not been true for well over 18 years if not longer. ACLs/Filters on rout=
ing and switching devices is not a new phenomenon.=C2=A0 <br><br></div><div=
 class=3D"gmail_extra">Finally, to truly cover the subject you also have to=
 at least mention the things that have replaced dedicated firewalls for sec=
urity at the Edge (Load-balancers with built in Firewall functionality as a=
n example) that even PCI and SOC have accepted. <br clear=3D"all"></div><di=
v class=3D"gmail_extra"><div><div class=3D"gmail_signature"><div dir=3D"ltr=
">-------------------<br>Cheers, Rick<br><br>Experiences not things.</div><=
/div></div>
<br><div class=3D"gmail_quote">On Mon, Oct 19, 2015 at 8:53 PM, Fernando Go=
nt <span dir=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" target=3D=
"_blank">fgont@si6networks.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Hi, Rick,<br>
<br>
On 10/18/2015 09:35 AM, Rick Casarez wrote:<br>
&gt; Just trying to help. Answers in line.<br>
<br>
Indeed -- and that&#39;s really appreciated!<br>
<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; In Section 2:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Firewall - I am wondering if a better definiti=
on can be made. From<br>
&gt;=C2=A0 =C2=A0 =C2=A0what<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; you wrote I cannot distinguish between a Firew=
all and an ACL.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0An ACL is a policy. A firewall is a device that enf=
orces filtering<br>
&gt;=C2=A0 =C2=A0 =C2=A0policies.<br>
&gt;<br>
&gt; [Rick] Your definition would encompass routers and switches who have<b=
r>
&gt; ACL/Filters on interfaces/SVIs. I would not consider these firewalls.<=
br>
<br>
Well, that&#39;s a firewalling functionality. From a strict point of view, =
a<br>
router does not really drop offending packets, but just forwards them.<br>
<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; No mention<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; of state tracking for instance etc.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Ok, will try to add somethin in this respect.<br>
&gt;<br>
&gt; [Rick] Please do, as Ca mentions this is how the vast majority of the<=
br>
&gt; world define it as. This even includes common compliance audits like<b=
r>
&gt; PCI/SOC etc.<br>
<br>
Question: WOuld you include this as part of the fw definition, or rather<br=
>
e.g. simply define &quot;state-tracking&quot;?<br>
<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Section 5.1:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &quot;The drawback of this approach is that th=
e security goal of &quot;block<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; traffic unless it is explicitly allowed&quot; =
prevents useful new<br>
&gt;=C2=A0 =C2=A0 =C2=A0applications.&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; I am not sure I understand this line. It block=
s new applications from<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; immediately traversing the firewall. I know fr=
om experience though<br>
&gt;=C2=A0 =C2=A0 =C2=A0that<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; when a discussion is had with the NetSec team =
the application can be<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; added to the allow list. So not sure a &quot;d=
efault deny&quot; means new stuff<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; never gets allowed as the text insinuates.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Well, that depends on where the firewall is being d=
eployed, and if it is<br>
&gt;=C2=A0 =C2=A0 =C2=A0actively managed.<br>
&gt;<br>
&gt; [Rick] I am unaware of any firewall deployed that is no longer managed=
.<br>
<br>
I&#39;m told that comcast does currently deploys this sort of boxes for<br>
their IPv6 residential customers.<br>
<br>
And I&#39;d argue that anything that is deployed at the home mostly follows=
<br>
into this category...<br>
<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Section 6:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; There are temporary IPv4 addresses too.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Not by definition I&#39;d say. Or... would you mind=
 elaborating a bit more<br>
&gt;=C2=A0 =C2=A0 =C2=A0in this respect?<br>
&gt;<br>
&gt;=C2=A0 [Rick] My apologies on this one got some wires crossed. This is =
good to go.<br>
<br>
Thanks for double-checking!<br>
<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; As for application being tunneled over well-kn=
own ports that<br>
&gt;=C2=A0 =C2=A0 =C2=A0sounds like<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; a breakdown of communication between the Servi=
ce Owners and NetSec.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Simple communication *should* lead to the crea=
tion of a profile<br>
&gt;=C2=A0 =C2=A0 =C2=A0for that<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; new application and its individual port. By do=
ing what you describe it<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; sounds like a Service Owner trying to get out =
of doing due diligence<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; with NetSec or not knowing what port their app=
lication needs for<br>
&gt;=C2=A0 =C2=A0 =C2=A0access<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; (More common than you might think).<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Yes. Or, at times, a user/app trying to circumvent =
unmanaged firewalls.<br>
&gt;=C2=A0 =C2=A0 =C2=A0-- Ironically, at times these protocols are referre=
d to as &quot;firewall<br>
&gt;=C2=A0 =C2=A0 =C2=A0friendly&quot;.<br>
&gt;<br>
&gt;=C2=A0 [Rick] The scenario makes no sense other than a mismanaged compa=
ny<br>
&gt; frankly. You are essentially encouraging something against BCP. Even<b=
r>
&gt; beyond security you will make it difficult to troubleshoot if everythi=
ng<br>
&gt; is using the same port to traverse the firewall.<br>
<br>
We=C2=BFre not talking about companies, but about e.g. about firewalls<br>
deployed at homes, and applications meant to be employed by such users.<br>
<br>
Thanks!<br>
<br>
Best regards,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a><=
br>
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a11c38e0e78eea50522883ee9--


From nobody Wed Oct 21 14:27:18 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B421A1B2D0B; Wed, 21 Oct 2015 14:27:16 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151021212716.783.90284.idtracker@ietfa.amsl.com>
Date: Wed, 21 Oct 2015 14:27:16 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/yeqWg8z8J-W7KSdhpBxP8HBhoCo>
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2015 21:27:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.

        Title           : HMAC-SHA-2 Authentication Protocols in USM for SNMPv3
        Authors         : Johannes Merkle
                          Manfred Lochter
	Filename        : draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-01.txt
	Pages           : 14
	Date            : 2015-10-21

Abstract:
   This memo specifies new HMAC-SHA-2 authentication protocols for the
   User-based Security Model (USM) for SNMPv3 defined in RFC 3414.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-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 Thu Oct 22 04:14:39 2015
Return-Path: <bingxuere@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A411A1B65 for <opsawg@ietfa.amsl.com>; Thu, 22 Oct 2015 04:14:37 -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 XeJGI6pCNR3w for <opsawg@ietfa.amsl.com>; Thu, 22 Oct 2015 04:14:35 -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 C632F1A1B69 for <opsawg@ietf.org>; Thu, 22 Oct 2015 04:14:35 -0700 (PDT)
Received: by igbhv6 with SMTP id hv6so57361224igb.0 for <opsawg@ietf.org>; Thu, 22 Oct 2015 04:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=Qsdj0ddNpHE+3paaUhyU34bQ6A+MbK8WphcHihQz7po=; b=i/3PQunW6jOMV0g4ct8KV22VACkIo5PbajbRaA1o5MsjueByl2RXpBIIrcv31ZIl+4 8zb3EI7yCNwre11ollXKIpHbpUhMVQY08rpS/HLR/9GBWvbBQbmRvvIjNaONsSdGrfxD 6k16syLdgBRWz5YRl5BSrtu6xon7b/4uNUp+dm/21XiMRk4f/rapKB3dHo0VryT6GAgC 9X92Ljq1vNMjDzjR1fITg5m7gLyXycx+Xcbal6s8p+VA03S3pwtjQlqpxvRO/9/K5imt U0yE9DbjBtD3O4Lex/aX2vqeYx5L3MxGhm854bYfuSBzAXs3xp6wE1P62KafojKLLraS 3FSA==
X-Received: by 10.50.79.169 with SMTP id k9mr15086287igx.50.1445512475149; Thu, 22 Oct 2015 04:14:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.34.179 with HTTP; Thu, 22 Oct 2015 04:13:55 -0700 (PDT)
From: Qiong <bingxuere@gmail.com>
Date: Thu, 22 Oct 2015 19:13:55 +0800
Message-ID: <CAH3bfAB-TQejP7CWPiQZdW=es4U=+a0iZuTur61TSDZYwB4_Yw@mail.gmail.com>
To: opsawg@ietf.org
Content-Type: multipart/alternative; boundary=089e013a01c8998e5b0522af99b7
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/NvAGyWZU-3p9cB7YMMZMS3UqUfc>
Subject: [OPSAWG] [opsawg]Fw: New Version Notification for draft-sun-i2apm-address-pool-management-yang-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 11:14:37 -0000

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

Dear all,

This is the second draft on address pool management. Your comments are more
than welcome. Thanks in advance!

Best wishes
Qiong

*From:* internet-drafts <internet-drafts@ietf.org>
*Date:* 2015-10-18 17:24
*To:* Qiong Sun <sunqiong@ctbri.com.cn>; Mohammed Boucadair
<mohamed.boucadair@orange-ftgroup.com>; Shucheng LIU (Will)
<liushucheng@huawei.com>; Yiu Lee <yiu_lee@cable.comcast.com>; Qiong Sun
<sunqiong@ctbri.com.cn>; Mohamed Boucadair
<mohamed.boucadair@orange-ftgroup.com>; Will Liu (Shucheng)
<liushucheng@huawei.com>; Chongfeng Xie <xiechf@ctbri.com.cn>; Yiu L. Lee
<yiu_lee@cable.comcast.com>; Chongfeng Xie <xiechf@ctbri.com.cn>
*Subject:* New Version Notification for
draft-sun-i2apm-address-pool-management-yang-00.txt

A new version of I-D, draft-sun-i2apm-address-pool-management-yang-00.txt
has been successfully submitted by Qiong Sun and posted to the
IETF repository.

Name: draft-sun-i2apm-address-pool-management-yang
Revision: 00
Title: Address Pool Management Yang Data Model
Document date: 2015-10-18
Group: Individual Submission
Pages: 16
URL:
https://www.ietf.org/internet-drafts/draft-sun-i2apm-address-pool-management-yang-00.txt
Status:
https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-yang/
Htmlized:
https://tools.ietf.org/html/draft-sun-i2apm-address-pool-management-yang-00


Abstract:
   This document describes a YANG data model for address pool
   management.  It can be used to automatically allocate, update and
   delete address pools in different devices of an underlying network.




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
-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================

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

<div dir=3D"ltr">Dear all,<div><br></div><div>This is the second draft on a=
ddress pool management. Your comments are more than welcome. Thanks in adva=
nce!</div><div><br></div><div>Best wishes</div><div>Qiong<br clear=3D"all">=
<div><div style=3D"color:rgb(0,0,0);font-family:=E5=AE=8B=E4=BD=93;font-siz=
e:14px;line-height:21px">=C2=A0</div><div style=3D"color:rgb(0,0,0);font-fa=
mily:=E5=AE=8B=E4=BD=93;font-size:14px;line-height:21px;border-style:solid =
none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3p=
t 0cm 0cm"><div style=3D"padding:8px;font-size:12px;font-family:tahoma;back=
ground-color:rgb(239,239,239)"><div><b>From:</b>=C2=A0<a href=3D"mailto:int=
ernet-drafts@ietf.org">internet-drafts</a></div><div><b>Date:</b>=C2=A02015=
-10-18=C2=A017:24</div><div><b>To:</b>=C2=A0<a href=3D"mailto:sunqiong@ctbr=
i.com.cn">Qiong Sun</a>;=C2=A0<a href=3D"mailto:mohamed.boucadair@orange-ft=
group.com">Mohammed Boucadair</a>;=C2=A0<a href=3D"mailto:liushucheng@huawe=
i.com">Shucheng LIU (Will)</a>;=C2=A0<a href=3D"mailto:yiu_lee@cable.comcas=
t.com">Yiu Lee</a>;=C2=A0<a href=3D"mailto:sunqiong@ctbri.com.cn">Qiong Sun=
</a>;=C2=A0<a href=3D"mailto:mohamed.boucadair@orange-ftgroup.com">Mohamed =
Boucadair</a>;=C2=A0<a href=3D"mailto:liushucheng@huawei.com">Will Liu (Shu=
cheng)</a>;=C2=A0<a href=3D"mailto:xiechf@ctbri.com.cn">Chongfeng Xie</a>;=
=C2=A0<a href=3D"mailto:yiu_lee@cable.comcast.com">Yiu L. Lee</a>;=C2=A0<a =
href=3D"mailto:xiechf@ctbri.com.cn">Chongfeng Xie</a></div><div><b>Subject:=
</b>=C2=A0New Version Notification for draft-sun-i2apm-address-pool-managem=
ent-yang-00.txt</div></div></div><div style=3D"color:rgb(0,0,0);font-family=
:=E5=AE=8B=E4=BD=93;font-size:14px;line-height:21px"><div>=C2=A0</div><div>=
A new version of I-D, draft-sun-i2apm-address-pool-management-yang-00.txt</=
div><div>has been successfully submitted by Qiong Sun and posted to the</di=
v><div>IETF repository.</div><div>=C2=A0</div><div>Name:	 draft-sun-i2apm-a=
ddress-pool-management-yang</div><div>Revision:	00</div><div>Title:	 Addres=
s Pool Management Yang Data Model</div><div>Document date:	2015-10-18</div>=
<div>Group:	 Individual Submission</div><div>Pages:	 16</div><div>URL:=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <a href=3D"=
https://www.ietf.org/internet-drafts/draft-sun-i2apm-address-pool-managemen=
t-yang-00.txt">https://www.ietf.org/internet-drafts/draft-sun-i2apm-address=
-pool-management-yang-00.txt</a></div><div>Status:=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 <a href=3D"https://datatracker.ietf.org/doc/draft-=
sun-i2apm-address-pool-management-yang/">https://datatracker.ietf.org/doc/d=
raft-sun-i2apm-address-pool-management-yang/</a></div><div>Htmlized:=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <a href=3D"https://tools.ietf.org/html/draft=
-sun-i2apm-address-pool-management-yang-00">https://tools.ietf.org/html/dra=
ft-sun-i2apm-address-pool-management-yang-00</a></div><div>=C2=A0</div><div=
>=C2=A0</div><div>Abstract:</div><div>=C2=A0=C2=A0 This document describes =
a YANG data model for address pool</div><div>=C2=A0=C2=A0 management.=C2=A0=
 It can be used to automatically allocate, update and</div><div>=C2=A0=C2=
=A0 delete address pools in different devices of an underlying network.</di=
v><div>=C2=A0</div><div>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</div><div>=C2=
=A0</div><div>=C2=A0</div><div>Please note that it may take a couple of min=
utes from the time of submission</div><div>until the htmlized version and d=
iff are available at <a href=3D"http://tools.ietf.org">tools.ietf.org</a>.<=
/div><div>=C2=A0</div><div>The IETF Secretariat</div></div></div>-- <br><di=
v class=3D"gmail_signature">=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<br>Qiong Sun<br>China Telecom Beijing Research Institude=
<br><br><br>Open source code:<br>lightweight 4over6: <i><a href=3D"http://s=
ourceforge.net/projects/laft6/" target=3D"_blank">http://sourceforge.net/pr=
ojects/laft6/</a></i><br>PCP-natcoord:<i> <a href=3D"http://sourceforge.net=
/projects/pcpportsetdemo/" target=3D"_blank">http://sourceforge.net/project=
s/pcpportsetdemo/</a> </i><br>=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<br><br></div>
</div></div>

--089e013a01c8998e5b0522af99b7--


From nobody Thu Oct 22 05:18:40 2015
Return-Path: <ietfc@btconnect.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E192E1B364F for <opsawg@ietfa.amsl.com>; Thu, 22 Oct 2015 05:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 mWhjGA3C23lg for <opsawg@ietfa.amsl.com>; Thu, 22 Oct 2015 05:18:28 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0740.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::740]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A90901B3663 for <opsawg@ietf.org>; Thu, 22 Oct 2015 05:18:24 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com; 
Received: from pc6 (86.185.87.133) by AMXPR07MB056.eurprd07.prod.outlook.com (10.242.67.151) with Microsoft SMTP Server (TLS) id 15.1.300.14; Thu, 22 Oct 2015 12:17:59 +0000
Message-ID: <043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Johannes Merkle <johannes.merkle@secunet.com>, <manfred.lochter@bsi.bund.de>, Benoit Claise <bclaise@cisco.com>
References: <20151020091258.5C26A182534@rfc-editor.org> <56260809.9040501@cisco.com>
Date: Thu, 22 Oct 2015 13:17:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.185.87.133]
X-ClientProxiedBy: DB4PR02CA0026.eurprd02.prod.outlook.com (10.242.174.154) To AMXPR07MB056.eurprd07.prod.outlook.com (10.242.67.151)
X-Microsoft-Exchange-Diagnostics: 1; AMXPR07MB056; 2:EHocjbPxVTwqu08NgxM1WzSorrXH9tzjzYcGCIwqMcPqel2t2Mh+1Z7jsVLs6a1WnlhMZKunxgMOTDFeLicFfbkjtZM5faPyOq3uJ0SiEy3SJvfs91ObI4Hes7Yt43bEyKbwSMSI40d5QU22H9WvEKSWQReH088cef11X4wOouA=; 3:jGFRPVyeLfj/Owaioy1CIEs4i8saWJgHLx8tdIAEk2BWv/jVv7YvuWmM4oglRSrME04k6UV7fRJ0vKQxYlVS3/IjXDF+m1KJ0YD6duclQC8DKAMrUEH899q6iEtUIUtA1hCNdEXgMKw50vRR2zXQsA==; 25:7a//4LMrgvr7RzGff4JzvLafSgbAOJihB/H6rM0iW9uRAlDWMg28nrefILfpEpj94l02a+shzVq17WQ4dhyXz9nXlEc/CSc6lY4W1Wa/rRLJ1NRz3qWaf4ynM72VkbmDQVw07xuDdLyzFbsCirK5Yh1WHsDs3D1OTDREveoF60Uvt+EipWF4gGQOK28584e623JRUWv+TThr+dr1L9PYAFVzKzoOfGlg3EbLhHev9zNxpJsdrYb8bjy1qHI6DT18; 4:7hLJS5757y6evTCixvz/VWw8ZWlUINZ8JGF+ckNMemAGbFDR3xAs0LLwlNu3WTXbIH8vWjGzu2IIWIcyzWelVa1Dx/H7t6kI2j5S06jr0shBgY2zqbhpl+TdLcq+25wYApr7xSohq1lGQzbxkWqsx7mGgSH4xBqiv8LXPRJQNRekQDgqaAs4c5EmFciSdfCY19oP9KiGwElch1oNIEYBWO2h3u5k9vh91uufiR/SxXH4tha1G2ETOKudglMgt3Ev+mX9dBq5oxIdBYruCW7fQytV3TozGQ37dmMxkDyAIRBlS8TX1krCdPhuWYYNhwwZ+9Kf9+7o+0DiErBK+dv/3srIO9lz5HKDeKj7ERmsfKjHP/UCXNbT6MgtPpvu5KmM
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMXPR07MB056;
X-Microsoft-Antispam-PRVS: <AMXPR07MB05668C9D93963A19E82AC95A0270@AMXPR07MB056.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(95692535739014);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(520078)(3002001)(102215026); SRVR:AMXPR07MB056; BCL:0; PCL:0; RULEID:; SRVR:AMXPR07MB056; 
X-Forefront-PRVS: 0737B96801
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(51444003)(199003)(189002)(377424004)(86362001)(116806002)(5008740100001)(81816999)(62236002)(5001960100002)(44716002)(42186005)(76176999)(106356001)(77096005)(66066001)(1720100001)(7110500001)(47776003)(50986999)(81686999)(40100003)(1456003)(15975445007)(50226001)(64706001)(189998001)(105586002)(5007970100001)(19580405001)(16799955002)(5004730100002)(1556002)(5001920100001)(15188155005)(92566002)(10710500006)(84392001)(122386002)(50466002)(5001770100001)(61296003)(46102003)(101416001)(97736004)(2420400006)(14496001)(44736004)(33646002)(87976001)(4001150100001)(81156007)(23746002)(19580395003)(74416001)(7726001)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMXPR07MB056; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; AMXPR07MB056; 23:c5XrAZD8oZ66SoUK6SF2AYRyxGYGdCkqNRL9Tu?= =?Windows-1252?Q?UqUNr58LwsogY2tQKwu9lelAnHNHLPtXI0ewhfqRtAVzDehgPMFNS4K+?= =?Windows-1252?Q?HCUsN9GQnpXbqVOabjTzsRu0+FI5J+4U/h8C8Wp/qZZWXwitX79/Q5jv?= =?Windows-1252?Q?zcI22kawA1hEcYta7zmr/OgQWgBk042v2tyM6gxkv/0HPCDXjL4cxkMN?= =?Windows-1252?Q?ieYFuQuqWFUSNsG+jOKaaytNPbdlR1qHBaa8WueG5518y8B9EWfnrdLT?= =?Windows-1252?Q?lTKb7eN5pZXsrePBP2bBfFfiDn+AyQbLb0dZ28tdsMMqKp4Jq+C94tDP?= =?Windows-1252?Q?NvWYCCk8QpvGaYqcyfzBFtnwTmYVB3BMbKWjEhTeXs6B5NP5rxkpgcRS?= =?Windows-1252?Q?7NxnG5Nnm/ZWT1MACCxPAFQtnCux+632EMYLJK9fwlZdYZM68Yto5uoI?= =?Windows-1252?Q?pIjnm42vKLWipYsmDrs+8Lz5KBk2uzAyeHfI+lSnkU9tYymvtugkJXu9?= =?Windows-1252?Q?JdjbRJuq4/etAq/Fl1S5Oi9uXWZIvfRn1bxUrElfY94mLTiKZk9h1kh3?= =?Windows-1252?Q?GncwFY7fuxmPOfm5Z2FfO09FWhkIWnz/4z/G1dQsWdzqtz0hwKB+R8cO?= =?Windows-1252?Q?F/E/hOEQ5LikMzkKylubZKWo/V4Zpy0lunBF4j0jZ/J0psXPZ11rarFN?= =?Windows-1252?Q?jr/9/lS9jFr/GobyJlkvDGYF7UBSJEicvrLd1vVUo1L57Cr3NqdgqTpS?= =?Windows-1252?Q?9SU8fuZHRfVuEeefnFe7SAhbP8i3OgQhd+aMBDAwq0sdA5TCtAc4uJkQ?= =?Windows-1252?Q?eSW70MV0aUCQDetZtpmFFr+j6i5zvgc7XXlKxfIHaAjb6nJ+Rls2aTf/?= =?Windows-1252?Q?gEXmmWW5w0wjwf2jw0jGrtlAEPfM1L3RbXvOjVuq5Rc+zDgBExysBtvB?= =?Windows-1252?Q?Mva9rSLd8XY9TlXheXsfYT8gR9eyE0D1XjcN8ZwC8cTF6xkfudv6oRYO?= =?Windows-1252?Q?CuBFwpIknsJ2mS4EMcqC/G3UmwH3GbKmU38m9AgneaeAGm0guo/d1R0i?= =?Windows-1252?Q?whg5RBLIK/9oG/NswtuyYGGWw6mEZlQj/nFZ2EsXOWzNEeBfTtnGavQY?= =?Windows-1252?Q?savD8BK8hKJLh7Kp95Ob7jVvX89VVg4ERWUMPmYq9G8aofMX5tktzhfW?= =?Windows-1252?Q?SHaDdgCG3qV9diUv3FL/vj2YkLHunm91Tc6qcVPVJONGtJQiP1DYNGFk?= =?Windows-1252?Q?NkcIaVwD95CN/EVmyXuy9LJCnXwTspBS/MAtCgS0ZOptE9VFOJ6TRrDd?= =?Windows-1252?Q?eR9gf7BHTso/IgkKxuScDSR2vvE07imccclWo2xwq1g9DBNVxxIZIL1d?= =?Windows-1252?Q?9UuGpAFG9Vx7FeL9M87FyySTPn/tYB47MbF0VWbn8CD35dfykMXTLGLn?= =?Windows-1252?Q?mxPsULlL5O7kmpFYi+TCux2UvE+Ay+yq2SYhvIeqzj+sIs/NCVUnRDLV?= =?Windows-1252?Q?8nl+lem1wFONme9v20UAFDTdslDebFbggpyjrTqlOu4m4G4kChZ2qwD/?= =?Windows-1252?Q?xt74Y34hHOozCQu/0Rb7lyXOR96M4Cc/l4HGo4DlIdkw0IjEXeUc2Fe7?= =?Windows-1252?Q?MEoThgZdo+ooG46vxEZQZM0LsR4uIkPdUM0rqakBfh+4VkXLI9B8t65q?= =?Windows-1252?Q?MR5NeAAg=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; AMXPR07MB056; 5:VWpL1HXWk4c21avUOX63Mb8qIjUb88xBf5iIhR8UktkMaTA9PfMVeS4V25QmNdgM7+la/jaXidGLRZ9FvPYfDxjjLhRlXuJy2K/Rb24vl+aZ0/7tm59jrl/5VhpnNLbt5wTtSuxAAf6n1FSXjTNsPA==; 24:vurHZliNySne1QMMO5x5ZHy5IHUFtZRZUDm/wenG/YZ7d4MuFwjifIFXnEF5ho+9zFjTGhgdqU1Jm4NTXI2/Ggm3Y2/lkV8k3OS7iH2/8sY=; 20:Xv9V10+yOyySpVkeBaUalyFuWriq5HgzzyHAuJRZqscFopXgaRr3gKBJXKvki/D3bgfJNk0btJaTeac/XSKYPg==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Oct 2015 12:17:59.8985 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMXPR07MB056
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/_2rENtflBKPOKQYBTE-K9tQuFpY>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] [Errata Verified] RFC7630 (4509)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 12:18:33 -0000

---- Original Message -----
From: "Benoit Claise" <bclaise@cisco.com>
To: "RFC Errata System" <rfc-editor@rfc-editor.org>;
<johannes.merkle@secunet.com>; <manfred.lochter@bsi.bund.de>
Cc: <opsawg@ietf.org>
Sent: Tuesday, October 20, 2015 10:23


> Dear all,
>
> The facts:
> - The MIB doctors advised not to publish MIB modules under snmpModules
> any longer. IANA updated the registry information. See
>
http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
s-61
> - RFC 7360 is published with a mistake. The MIB module should have
been
> published under mib-2.235 (as advised by the MIB doctors) but the
> document mentions: snmpModules.235

Benoit

Mutter, mutter: it is a shame that the MIB Doctors did not tell us of
this change!

I carefully checked the I-D when it first appeared and was satisfied
that the assignment was in exactly the right place, using all the
information available to me so I think that the I-D was spot on.  And
that it remained correct thoughout its life.

And of course we are now wasting valuable resources making a 'right'
'wrong'!

Is there anything else we have not been told, by e-mail, RFC or I-D,
that might waste our time in future:-(

Tom Petch

> - The IANA registry is actually correct. snmpUsmHmacSha2MIB is under
> mib-2.235
> See http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml
> - Solving this issue with an errata doesn't work: indeed MIB modules
are
> extracted from RFC, and used within scripts.
>
> Discussing with Michelle (IANA) and the IESG, we had no other choices
> than obsoleting this RFC and re-issuing a new one. Hence this errata
and
> draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.
>
<http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-n
ew/>
>
> One change to keep in mind for the next version:
> OLD:
>
>         REVISION    "201508130000Z"       -- 13 August 2015, midnight
>         DESCRIPTION "Initial version, published asRFC 7630
<https://tools.ietf.org/html/rfc7630>"
>     ::= { snmpModules 235 }
>
> NEW:
>
>         REVISION     ... new date
>         DESCRIPTION "Initial version, published asRFC xxxx
<https://tools.ietf.org/html/rfc7630>"
>     ::= { mib-2 235 }
>
> The way forward is to publish a new draft ASAP with the above
> correction, to have a one week IETF LC, and to publish the new RFC. At
> that point (and not before because we don't have a replacement RFC),
we
> will obsolete RFC 7360.
>
> Regards, Benoit
> > The following errata report has been verified for RFC7630,
> > "HMAC-SHA-2 Authentication Protocols in the User-based Security
Model (USM) for SNMPv3".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=7630&eid=4509
> >
> > --------------------------------------
> > Status: Verified
> > Type: Technical
> >
> > Reported by: Johannes Merkle <johannes.merkle@secunet.com>
> > Date Reported: 2015-10-20
> > Verified by: Benoit Claise (IESG)
> >
> > Section: 8 and 10
> >
> > Original Text
> > -------------
> > snmpModules 235
> >
> > Corrected Text
> > --------------
> > mib-2 235
> >
> > Notes
> > -----
> > IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by
the MIB doctors), but the document mentions snmpModules.235
> >
> > --------------------------------------
> > RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
> > --------------------------------------
> > Title               : HMAC-SHA-2 Authentication Protocols in the
User-based Security Model (USM) for SNMPv3
> > Publication Date    : October 2015
> > Author(s)           : J. Merkle, Ed., M. Lochter
> > Category            : PROPOSED STANDARD
> > Source              : Operations and Management Area Working Group
> > Area                : Operations and Management
> > Stream              : IETF
> > Verifying Party     : IESG
> > .
> >
>
>


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


> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>


From nobody Fri Oct 23 02:28:17 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4877E1B3391 for <opsawg@ietfa.amsl.com>; Fri, 23 Oct 2015 02:28: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 AIwRhtokiEpn for <opsawg@ietfa.amsl.com>; Fri, 23 Oct 2015 02:28:10 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4DEB1B33D2 for <opsawg@ietf.org>; Fri, 23 Oct 2015 02:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13923; q=dns/txt; s=iport; t=1445592490; x=1446802090; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=2hsGWi3cCqUIstCHm+Qympp8oeL0WxqZ7VtOcpxSX58=; b=CctNKo5f0q/s8BTMckpj2chEwmCP22afdvF4MPSBsF3d6gHQ4QpVPXGo uBSCqfwPxHNez3Kkvhsq16jANA/v+eHJOiNYczuIH9NpY4PRBpEN/LMjd 2CpWDgQCDcXl52Z9l7SY52hYJd/HC3VCzgu7x/bioY5Zv1hT2GeQZoA6S E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwBAAs/SlW/xbLJq1EGoJpgSFvtQeLBhcBC4UwSgKCEQEBAQEBAYELhDIBAQEDAQEBAWsEBgEFBwQLFQELFg8JAwIBAgEVMAYBDAYCAQEFEIgPCA07xHsBAQEBAQEBAQEBAQEBAQEBAQEBAQEYhneEfoE9gy4iB4QuBYdAjmuFGYgFgVhIhniKQ4hLY4IRDRCBVzw0AROGLwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,186,1444694400";  d="scan'208,217";a="605866841"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2015 09:27:44 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t9N9ReUl021552; Fri, 23 Oct 2015 09:27:41 GMT
To: "t.petch" <ietfc@btconnect.com>, Johannes Merkle <johannes.merkle@secunet.com>, manfred.lochter@bsi.bund.de
References: <20151020091258.5C26A182534@rfc-editor.org> <56260809.9040501@cisco.com> <043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <5629FD77.6080107@cisco.com>
Date: Fri, 23 Oct 2015 11:27:19 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net>
Content-Type: multipart/alternative; boundary="------------030602040309070608020901"
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/GwsLkupMhVFT_S5AQqlOiMm0Uks>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] [Errata Verified] RFC7630 (4509)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2015 09:28:14 -0000

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

Tom,
> ---- Original Message -----
> From: "Benoit Claise" <bclaise@cisco.com>
> To: "RFC Errata System" <rfc-editor@rfc-editor.org>;
> <johannes.merkle@secunet.com>; <manfred.lochter@bsi.bund.de>
> Cc: <opsawg@ietf.org>
> Sent: Tuesday, October 20, 2015 10:23
>
>
>> Dear all,
>>
>> The facts:
>> - The MIB doctors advised not to publish MIB modules under snmpModules
>> any longer. IANA updated the registry information. See
>>
> http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
> s-61
>> - RFC 7360 is published with a mistake. The MIB module should have
> been
>> published under mib-2.235 (as advised by the MIB doctors) but the
>> document mentions: snmpModules.235
> Benoit
>
> Mutter, mutter: it is a shame that the MIB Doctors did not tell us of
> this change!
This discussion was actually triggered by IANA when it tried to figure 
out the registration procedures for SMI SNMPv2 snmpModules Codes 
registry ... in relation to this draft. The MIB doctors and I were involved.

> I carefully checked the I-D when it first appeared and was satisfied
> that the assignment was in exactly the right place, using all the
> information available to me so I think that the I-D was spot on.  And
> that it remained correct thoughout its life.
>
> And of course we are now wasting valuable resources making a 'right'
> 'wrong'!
I share the pain, trust me.
>
> Is there anything else we have not been told, by e-mail, RFC or I-D,
> that might waste our time in future:-(
I don't know what I don't know.
However, when a problem is discovered, it's generally solved. In this 
case, see the update at 
http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number 
s-61, e.g. "[No more registrations accepted ]"

Regards, Benoit
>
> Tom Petch
>
>> - The IANA registry is actually correct. snmpUsmHmacSha2MIB is under
>> mib-2.235
>> See http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml
>> - Solving this issue with an errata doesn't work: indeed MIB modules
> are
>> extracted from RFC, and used within scripts.
>>
>> Discussing with Michelle (IANA) and the IESG, we had no other choices
>> than obsoleting this RFC and re-issuing a new one. Hence this errata
> and
>> draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.
>>
> <http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-n
> ew/>
>> One change to keep in mind for the next version:
>> OLD:
>>
>>          REVISION    "201508130000Z"       -- 13 August 2015, midnight
>>          DESCRIPTION "Initial version, published asRFC 7630
> <https://tools.ietf.org/html/rfc7630>"
>>      ::= { snmpModules 235 }
>>
>> NEW:
>>
>>          REVISION     ... new date
>>          DESCRIPTION "Initial version, published asRFC xxxx
> <https://tools.ietf.org/html/rfc7630>"
>>      ::= { mib-2 235 }
>>
>> The way forward is to publish a new draft ASAP with the above
>> correction, to have a one week IETF LC, and to publish the new RFC. At
>> that point (and not before because we don't have a replacement RFC),
> we
>> will obsolete RFC 7360.
>>
>> Regards, Benoit
>>> The following errata report has been verified for RFC7630,
>>> "HMAC-SHA-2 Authentication Protocols in the User-based Security
> Model (USM) for SNMPv3".
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=7630&eid=4509
>>>
>>> --------------------------------------
>>> Status: Verified
>>> Type: Technical
>>>
>>> Reported by: Johannes Merkle <johannes.merkle@secunet.com>
>>> Date Reported: 2015-10-20
>>> Verified by: Benoit Claise (IESG)
>>>
>>> Section: 8 and 10
>>>
>>> Original Text
>>> -------------
>>> snmpModules 235
>>>
>>> Corrected Text
>>> --------------
>>> mib-2 235
>>>
>>> Notes
>>> -----
>>> IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by
> the MIB doctors), but the document mentions snmpModules.235
>>> --------------------------------------
>>> RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
>>> --------------------------------------
>>> Title               : HMAC-SHA-2 Authentication Protocols in the
> User-based Security Model (USM) for SNMPv3
>>> Publication Date    : October 2015
>>> Author(s)           : J. Merkle, Ed., M. Lochter
>>> Category            : PROPOSED STANDARD
>>> Source              : Operations and Management Area Working Group
>>> Area                : Operations and Management
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>> .
>>>
>>
>
> ------------------------------------------------------------------------
> --------
>
>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>>
> .
>


--------------030602040309070608020901
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">Tom,<br>
    </div>
    <blockquote
      cite="mid:043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">---- Original Message -----
From: "Benoit Claise" <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>
To: "RFC Errata System" <a class="moz-txt-link-rfc2396E" href="mailto:rfc-editor@rfc-editor.org">&lt;rfc-editor@rfc-editor.org&gt;</a>;
<a class="moz-txt-link-rfc2396E" href="mailto:johannes.merkle@secunet.com">&lt;johannes.merkle@secunet.com&gt;</a>; <a class="moz-txt-link-rfc2396E" href="mailto:manfred.lochter@bsi.bund.de">&lt;manfred.lochter@bsi.bund.de&gt;</a>
Cc: <a class="moz-txt-link-rfc2396E" href="mailto:opsawg@ietf.org">&lt;opsawg@ietf.org&gt;</a>
Sent: Tuesday, October 20, 2015 10:23


</pre>
      <blockquote type="cite">
        <pre wrap="">Dear all,

The facts:
- The MIB doctors advised not to publish MIB modules under snmpModules
any longer. IANA updated the registry information. See

</pre>
      </blockquote>
      <pre wrap=""><a class="moz-txt-link-freetext" href="http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number">http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number</a>
s-61
</pre>
      <blockquote type="cite">
        <pre wrap="">- RFC 7360 is published with a mistake. The MIB module should have
</pre>
      </blockquote>
      <pre wrap="">been
</pre>
      <blockquote type="cite">
        <pre wrap="">published under mib-2.235 (as advised by the MIB doctors) but the
document mentions: snmpModules.235
</pre>
      </blockquote>
      <pre wrap="">
Benoit

Mutter, mutter: it is a shame that the MIB Doctors did not tell us of
this change!</pre>
    </blockquote>
    This discussion was actually triggered by IANA when it tried to <span
      style="font-size: 16px;">figure out the registration procedures
      for</span> SMI SNMPv2 snmpModules Codes registry ... in relation
    to this draft. The MIB doctors and I were involved.<br>
    <br>
    <blockquote
      cite="mid:043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">I carefully checked the I-D when it first appeared and was satisfied
that the assignment was in exactly the right place, using all the
information available to me so I think that the I-D was spot on.  And
that it remained correct thoughout its life.

And of course we are now wasting valuable resources making a 'right'
'wrong'!</pre>
    </blockquote>
    I share the pain, trust me.<br>
    <blockquote
      cite="mid:043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">

Is there anything else we have not been told, by e-mail, RFC or I-D,
that might waste our time in future:-(</pre>
    </blockquote>
    I don't know what I don't know.<br>
    However, when a problem is discovered, it's generally solved. In
    this case, see the update at
    <a class="moz-txt-link-freetext" href="http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number">http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number</a>
    s-61, e.g. "[No more registrations accepted ]"<br>
    <br>
    Regards, Benoit<br>
    <blockquote
      cite="mid:043601d10cc3$989ae8a0$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">

Tom Petch

</pre>
      <blockquote type="cite">
        <pre wrap="">- The IANA registry is actually correct. snmpUsmHmacSha2MIB is under
mib-2.235
See <a class="moz-txt-link-freetext" href="http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml">http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml</a>
- Solving this issue with an errata doesn't work: indeed MIB modules
</pre>
      </blockquote>
      <pre wrap="">are
</pre>
      <blockquote type="cite">
        <pre wrap="">extracted from RFC, and used within scripts.

Discussing with Michelle (IANA) and the IESG, we had no other choices
than obsoleting this RFC and re-issuing a new one. Hence this errata
</pre>
      </blockquote>
      <pre wrap="">and
</pre>
      <blockquote type="cite">
        <pre wrap="">draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-00.

</pre>
      </blockquote>
      <pre wrap=""><a class="moz-txt-link-rfc2396E" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-new/">&lt;http://datatracker.ietf.org/doc/draft-ietf-opsawg-hmac-sha-2-usm-snmp-n
ew/&gt;</a>
</pre>
      <blockquote type="cite">
        <pre wrap="">
One change to keep in mind for the next version:
OLD:

        REVISION    "201508130000Z"       -- 13 August 2015, midnight
        DESCRIPTION "Initial version, published asRFC 7630
</pre>
      </blockquote>
      <pre wrap=""><a class="moz-txt-link-rfc2396E" href="https://tools.ietf.org/html/rfc7630">&lt;https://tools.ietf.org/html/rfc7630&gt;</a>"
</pre>
      <blockquote type="cite">
        <pre wrap="">    ::= { snmpModules 235 }

NEW:

        REVISION     ... new date
        DESCRIPTION "Initial version, published asRFC xxxx
</pre>
      </blockquote>
      <pre wrap=""><a class="moz-txt-link-rfc2396E" href="https://tools.ietf.org/html/rfc7630">&lt;https://tools.ietf.org/html/rfc7630&gt;</a>"
</pre>
      <blockquote type="cite">
        <pre wrap="">    ::= { mib-2 235 }

The way forward is to publish a new draft ASAP with the above
correction, to have a one week IETF LC, and to publish the new RFC. At
that point (and not before because we don't have a replacement RFC),
</pre>
      </blockquote>
      <pre wrap="">we
</pre>
      <blockquote type="cite">
        <pre wrap="">will obsolete RFC 7360.

Regards, Benoit
</pre>
        <blockquote type="cite">
          <pre wrap="">The following errata report has been verified for RFC7630,
"HMAC-SHA-2 Authentication Protocols in the User-based Security
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">Model (USM) for SNMPv3".
</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">
--------------------------------------
You may review the report below and at:
<a class="moz-txt-link-freetext" href="http://www.rfc-editor.org/errata_search.php?rfc=7630&amp;eid=4509">http://www.rfc-editor.org/errata_search.php?rfc=7630&amp;eid=4509</a>

--------------------------------------
Status: Verified
Type: Technical

Reported by: Johannes Merkle <a class="moz-txt-link-rfc2396E" href="mailto:johannes.merkle@secunet.com">&lt;johannes.merkle@secunet.com&gt;</a>
Date Reported: 2015-10-20
Verified by: Benoit Claise (IESG)

Section: 8 and 10

Original Text
-------------
snmpModules 235

Corrected Text
--------------
mib-2 235

Notes
-----
IANA registered snmpUsmHmacSha2MIB under mib-2.235 (as advised by
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">the MIB doctors), but the document mentions snmpModules.235
</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">
--------------------------------------
RFC7630 (draft-ietf-opsawg-hmac-sha-2-usm-snmp-06)
--------------------------------------
Title               : HMAC-SHA-2 Authentication Protocols in the
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">User-based Security Model (USM) for SNMPv3
</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Publication Date    : October 2015
Author(s)           : J. Merkle, Ed., M. Lochter
Category            : PROPOSED STANDARD
Source              : Operations and Management Area Working Group
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG
.

</pre>
        </blockquote>
        <pre wrap="">

</pre>
      </blockquote>
      <pre wrap="">

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


</pre>
      <blockquote type="cite">
        <pre wrap="">_______________________________________________
OPSAWG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/opsawg">https://www.ietf.org/mailman/listinfo/opsawg</a>

</pre>
      </blockquote>
      <pre wrap="">
.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030602040309070608020901--


From nobody Fri Oct 23 17:17:15 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F36821B2B02; Fri, 23 Oct 2015 17:17:11 -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 bwpO1poWCu7u; Fri, 23 Oct 2015 17:17:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 908E21B2AF8; Fri, 23 Oct 2015 17:17:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 32364180092; Fri, 23 Oct 2015 17:16:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151024001629.32364180092@rfc-editor.org>
Date: Fri, 23 Oct 2015 17:16:29 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/bDYRs0n2Y17e7YbbI27YFwAXLO0>
Cc: drafts-update-ref@iana.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: [OPSAWG] RFC 7666 on Management Information Base for Virtual Machines Controlled by a Hypervisor
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Oct 2015 00:17:12 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7666

        Title:      Management Information Base for Virtual 
                    Machines Controlled by a Hypervisor 
        Author:     H. Asai, M. MacFaden,
                    J. Schoenwaelder, K. Shima, T. Tsou
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2015
        Mailbox:    panda@hongo.wide.ad.jp, 
                    mrm@vmware.com, 
                    j.schoenwaelder@jacobs-university.de, 
                    keiichi@iijlab.net, 
                    tina.tsou.zouting@huawei.com
        Pages:      52
        Characters: 106260
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-vmm-mib-04.txt

        URL:        https://www.rfc-editor.org/info/rfc7666

        DOI:        http://dx.doi.org/10.17487/RFC7666

This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community.  In particular, this specifies objects for managing
virtual machines controlled by a hypervisor (a.k.a. virtual machine
monitor).

This document is a product of the Operations and Management Area Working Group 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 Oct 26 19:16:33 2015
Return-Path: <13301168517@189.cn>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9EA1B3324 for <opsawg@ietfa.amsl.com>; Mon, 26 Oct 2015 19:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.203
X-Spam-Level: **
X-Spam-Status: No, score=2.203 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_LOCAL_DIGITS=0.001, FROM_LOCAL_HEX=0.006, HELO_IS_SMALL6=0.556, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, SPF_HELO_PASS=-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 D7bVUUsztHvT for <opsawg@ietfa.amsl.com>; Mon, 26 Oct 2015 19:16:28 -0700 (PDT)
Received: from 189.cn (mta.189.cn [121.14.53.138]) by ietfa.amsl.com (Postfix) with ESMTP id C366D1B3323 for <opsawg@ietf.org>; Mon, 26 Oct 2015 19:16:27 -0700 (PDT)
HMM_SOURCE_IP: 10.64.8.34:51134.929785012
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from ctbriwangaij (unknown [10.64.8.34]) by 189.cn (HERMES) with ESMTP id 5DC7515C1E1 for <opsawg@ietf.org>; Tue, 27 Oct 2015 10:16:13 +0800 (CST)
Received: from ctbriwangaij ([219.142.69.75]) by zm-as4(MEDUSA 0.0.0.0) with ESMTP id 7bd17219-0d58-4218-b0a7-2870d4c76900 for opsawg@ietf.org; Tue Oct 27 10:16:17 2015
0/X-Total-Score: 0:
X-FILTER-SCORE: to=<909194829888618a8695874f909388>, score=<1445912177OMWZkqR5bbbbbVbbObbMbVFG556yyxxxxxxxxFxxFxxF> 
X-REAL-FROM: 13301168517@189.cn
X-Receive-IP: 219.142.69.75
From: "Aijun Wang" <13301168517@189.cn>
To: <opsawg@ietf.org>
References: <15F8424C3FD6FE4FBC5651B784DBF82189C7C78D@nkgeml503-mbx.china.huawei.com>
In-Reply-To: <15F8424C3FD6FE4FBC5651B784DBF82189C7C78D@nkgeml503-mbx.china.huawei.com>
Date: Tue, 27 Oct 2015 10:16:08 +0800
Message-ID: <007801d1105d$79807640$6c8162c0$@cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01D110A0.87A3B640"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHRCk9qEzqfv+b+8UyPoagSeUhq2Z50AU4QgAmnI9CAAPNcgA==
Content-Language: zh-cn
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/ERkj0GK4pcCUV78smvo8ky9KxsY>
Subject: Re: [OPSAWG] New Version Notification for draft-chen-opsawg-dcn-vn2pn-mapping-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2015 02:16:31 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0079_01D110A0.87A3B640
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi, Hao:

=20

I think this draft is useful for the service provider to deploy virtual =
network related VAS within DC and can be extended beyond to cover WAN =
domain further.  After standardizing the fabric services model, the =
complex of the VAS application development and the network management =
can be relieved largely.  It is also coincide with the efforts of =
various Yang model definitions that are undergoing in several IETF WG.

>From the viewpoint of service provider, the VN2PN mapping architecture =
is one example of network model deployment scenario. if we can clarify =
and make consensus on this use case, then we can move forward further, =
define the related Yang model and accelerate the deployment of VAS =
services for tenant.

=20

NVO3 WG and L3SM WG are now working on the similar topics, you can also =
contact them for more deeper discussion.

=20

Best Regards.

=20

Aijun Wang

=20

China Telecom Corporation Limited Beijing Research Institute=20

Intelligent Network Product Line

=20

=20

From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Chenhao =
(philips)
Sent: Tuesday, October 20, 2015 5:13 PM
To: opsawg@ietf.org
Subject: [OPSAWG] FW: New Version Notification for =
draft-chen-opsawg-dcn-vn2pn-mapping-00.txt

=20

Dear all,

=20

This is a new draft for opsawg. It mainly analysis the issues existed in =
deploying the virtual network to the underneath physical network in =
DataCenter network . The basic idea is to abstract the underneath =
physical network as several fabrics, which can provide the fabric =
services to the upper-layer application/network administrator, to =
facilitate the whole configuration procedure.

=20

We would like to hear your comments, thanks.

=20

=20

Best regards,

Hao

=20

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
Sent: Monday, October 19, 2015 5:21 PM
To: Liyizhou; Chenhao (philips); Xingjun Chu; Yapeng Wu; Yapeng Wu; =
Liyizhou; Chenhao (philips); Xingjun Chu
Subject: New Version Notification for =
draft-chen-opsawg-dcn-vn2pn-mapping-00.txt

=20

=20

A new version of I-D, draft-chen-opsawg-dcn-vn2pn-mapping-00.txt

has been successfully submitted by Hao Chen and posted to the IETF =
repository.

=20

Name:               draft-chen-opsawg-dcn-vn2pn-mapping

Revision:  00

Title:                  Virtual Network to Physical Network Mapping in =
DataCenter Network

Document date:       2015-10-18

Group:               Individual Submission

Pages:               12

URL:             =
<https://www.ietf.org/internet-drafts/draft-chen-opsawg-dcn-vn2pn-mapping=
-00.txt> =
https://www.ietf.org/internet-drafts/draft-chen-opsawg-dcn-vn2pn-mapping-=
00.txt

Status:          =
<https://datatracker.ietf.org/doc/draft-chen-opsawg-dcn-vn2pn-mapping/> =
https://datatracker.ietf.org/doc/draft-chen-opsawg-dcn-vn2pn-mapping/

Htmlized:        =
<https://tools.ietf.org/html/draft-chen-opsawg-dcn-vn2pn-mapping-00> =
https://tools.ietf.org/html/draft-chen-opsawg-dcn-vn2pn-mapping-00

=20

=20

Abstract:

   Cloud tenant needs virtual network to interconnect their VMs on

   server. In order to effectively and efficiently map virtual network

   to physical network, certain mechanism should be employed.

=20

   This memo analysis the existing VN2PN mapping technique employed in

   DataCenter and point out the potential shortcomings lie in it. This

   memo also try to provide a generic mechanism to facilitate the VN2PN

   mapping in DataCenter network.

=20

                                                                         =
        =20

=20

=20

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.

=20

The IETF Secretariat

=20


------=_NextPart_000_0079_01D110A0.87A3B640
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"=E7=BA=AF=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E7=BA=AF=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char0
	{mso-style-name:"=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC Char";
	mso-style-priority:99;
	mso-style-link:=E6=89=B9=E6=B3=A8=E6=A1=86=E6=96=87=E6=9C=AC;
	font-family:"Calibri","sans-serif";}
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:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Hi, Hao:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I think =
this draft is useful for the service provider to deploy virtual network =
related VAS within DC and can be extended beyond to cover WAN domain =
further. =C2=A0After standardizing the fabric services model, the =
complex of the VAS application development and the network management =
can be relieved largely. =C2=A0It is also coincide with the efforts of =
various Yang model definitions that are undergoing in several IETF =
WG.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>From the viewpoint of service provider, the =
VN2PN mapping architecture is one example of network model deployment =
scenario. if we can clarify and make consensus on this use case, then we =
can move forward further, define the related Yang model and accelerate =
the deployment of VAS services for tenant.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>NVO3 WG and =
L3SM WG are now working on the similar topics, you can also contact them =
for more deeper discussion.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Best =
Regards.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>Aijun Wang<o:p></o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>China&nbsp;Telecom&nbsp;Corporation&nbsp;Limited&nbsp;Beijing&nbsp;Res=
earch&nbsp;Institute&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497=
D'>Intelligent Network Product Line<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> OPSAWG [<a =
href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-bounces@ietf.org</a=
>] <b>On Behalf Of </b>Chenhao (philips)<br><b>Sent:</b> Tuesday, =
October 20, 2015 5:13 PM<br><b>To:</b> <a =
href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</a><br><b>Subject:</b> =
[OPSAWG] FW: New Version Notification for =
draft-chen-opsawg-dcn-vn2pn-mapping-00.txt<o:p></o:p></span></p></div></d=
iv><p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Dear all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>This is a new draft for opsawg. =
It mainly analysis the issues existed in deploying the virtual network =
to the underneath physical network in DataCenter network . The basic =
idea is to abstract the underneath physical network as several fabrics, =
which can provide the fabric services to the upper-layer =
application/network administrator, to facilitate the whole configuration =
procedure.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We would like to hear your comments, =
thanks.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Hao<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>-----Original =
Message-----<br>From: <a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> =
[<a =
href=3D"mailto:internet-drafts@ietf.org">mailto:internet-drafts@ietf.org<=
/a>] <br>Sent: Monday, October 19, 2015 5:21 PM<br>To: Liyizhou; Chenhao =
(philips); Xingjun Chu; Yapeng Wu; Yapeng Wu; Liyizhou; Chenhao =
(philips); Xingjun Chu<br>Subject: New Version Notification for =
draft-chen-opsawg-dcn-vn2pn-mapping-00.txt<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>A new version of I-D, =
draft-chen-opsawg-dcn-vn2pn-mapping-00.txt<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>has been successfully submitted =
by Hao Chen and posted to the IETF repository.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>Name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-chen-opsawg-dcn-vn2pn-mapping<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Revision:&nbsp; =
00<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Virtual Network to =
Physical Network Mapping in DataCenter Network<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Document =
date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2015-10-18<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Individual =
Submission<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Pages:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <a =
href=3D"https://www.ietf.org/internet-drafts/draft-chen-opsawg-dcn-vn2pn-=
mapping-00.txt"><span =
style=3D'color:#1F497D;text-decoration:none'>https://www.ietf.org/interne=
t-drafts/draft-chen-opsawg-dcn-vn2pn-mapping-00.txt</span></a><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a =
href=3D"https://datatracker.ietf.org/doc/draft-chen-opsawg-dcn-vn2pn-mapp=
ing/"><span =
style=3D'color:#1F497D;text-decoration:none'>https://datatracker.ietf.org=
/doc/draft-chen-opsawg-dcn-vn2pn-mapping/</span></a><o:p></o:p></span></p=
><p class=3DMsoPlainText><span =
lang=3DEN-US>Htmlized:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a =
href=3D"https://tools.ietf.org/html/draft-chen-opsawg-dcn-vn2pn-mapping-0=
0"><span =
style=3D'color:#1F497D;text-decoration:none'>https://tools.ietf.org/html/=
draft-chen-opsawg-dcn-vn2pn-mapping-00</span></a><o:p></o:p></span></p><p=
 class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>Abstract:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; Cloud tenant needs =
virtual network to interconnect their VMs on<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; server. In order to =
effectively and efficiently map virtual network<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; to physical =
network, certain mechanism should be employed.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; This memo analysis =
the existing VN2PN mapping technique employed in<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; DataCenter and =
point out the potential shortcomings lie in it. =
This<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp; memo also try to provide a generic mechanism =
to facilitate the VN2PN<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; mapping in =
DataCenter network.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&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=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>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.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>The IETF Secretariat<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0079_01D110A0.87A3B640--


From nobody Tue Oct 27 01:44:02 2015
Return-Path: <philips.chenhao@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8E6A1B515B for <opsawg@ietfa.amsl.com>; Tue, 27 Oct 2015 01:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_12=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 0Q030CTbyRcS for <opsawg@ietfa.amsl.com>; Tue, 27 Oct 2015 01:43: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 008261B504C for <opsawg@ietf.org>; Tue, 27 Oct 2015 01:43:54 -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 BZK07417; Tue, 27 Oct 2015 08:43:52 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 27 Oct 2015 08:43:50 +0000
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.146]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0235.001; Tue, 27 Oct 2015 16:43:47 +0800
From: "Chenhao (philips)" <philips.chenhao@huawei.com>
To: Aijun Wang <13301168517@189.cn>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] New Version Notification for draft-chen-opsawg-dcn-vn2pn-mapping-00.txt
Thread-Index: AQHRCk9qEzqfv+b+8UyPoagSeUhq2Z50AU4QgAmnI9CAAPNcgIAAaNpw
Date: Tue, 27 Oct 2015 08:43:47 +0000
Message-ID: <15F8424C3FD6FE4FBC5651B784DBF82189C8A5F0@nkgeml503-mbx.china.huawei.com>
References: <15F8424C3FD6FE4FBC5651B784DBF82189C7C78D@nkgeml503-mbx.china.huawei.com> <007801d1105d$79807640$6c8162c0$@cn>
In-Reply-To: <007801d1105d$79807640$6c8162c0$@cn>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.160.235]
Content-Type: multipart/alternative; boundary="_000_15F8424C3FD6FE4FBC5651B784DBF82189C8A5F0nkgeml503mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/tQDnbgkccOypXhIBM4Itjg9jNK4>
Subject: Re: [OPSAWG] New Version Notification for draft-chen-opsawg-dcn-vn2pn-mapping-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2015 08:43:59 -0000

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

SGkgQWlqdW4sDQoNClJlYWxseSBhcHByZWNpYXRlIGZvciB5b3VyIGNvbW1lbnRzLiBZZXMsIHRo
aXMgZHJhZnQgZGVzY3JpYmVzIHRoZSBWTjJQTiBtYXBwaW5nIGFyY2hpdGVjdHVyZSB3aGljaCBm
b2N1c2VzIG9uIGEgZmFicmljIGJhc2VkIHNlcnZpY2UgbW9kZWwgKGFrYSBGYWFTIC0gRmFicmlj
IGFzIGEgU2VydmljZSkuICBUaGlzIHdvcmsgaGFzIHdpa2kgcGFnZSBpbiBPREwgYXQgaHR0cHM6
Ly93aWtpLm9wZW5kYXlsaWdodC5vcmcvdmlldy9Qcm9qZWN0X1Byb3Bvc2FsczpGYWFTIGFuZCBo
YXMgcnVubmluZyBjb2RlIGF0IGh0dHBzOi8vZ2l0aHViLmNvbS9vcGVuZGF5bGlnaHQvZmFhcyAu
IEN1cnJlbnRseSB0d28gWUFORyBtb2RlbHMgYXJlIGJlaW5nIGRldmVsb3BlZDogMSkgdGhlIGZh
YnJpYyAgc2VydmljZSBZQU5HIG1vZGVsICwgMikgdGhlIGRldmljZSBjb25maWcgWUFORyBtb2Rl
bC4gV2Ugd2lsbCBzdWJtaXQgdGhlbSBmb3IgZGlzY3Vzc2lvbiBsYXRlci4NCg0KU28gZmFyIHdl
IGZvY3VzIG9uIHRoZSBpbnRyYS1EQyBzY2VuYXJpbyBidXQgSSB0aGluayBpdCBpcyBleHRlbmRh
YmxlLiBXZSB3b3VsZCBsaWtlIHRvIGRpc2N1c3MgbW9yZSB3aXRoIHlvdSBvbiB0aGUgV0FOIGV4
dGVuc2lvbi4gVGhpcyB3b3JrIGlzIG5vdCBsaW1pdGVkIHRvIG92ZXJsYXkgc3VjaCBhcyBWWExB
Ti4gVkxBTiBhbmQgVFJJTEwgYXJlIGFsc28gaW5jbHVkZWQuIFNvIGluIG15IG9waW5pb24gaXQg
aXMgbW9yZSBnZW5lcmljIGNvbXBhcmVkIHRvIE5WTzMgb3ZlcmxheSBuZXR3b3JrLiBGb3Igc3Vy
ZSB3ZSB3aWxsIGNyb3NzIGNoZWNrIHdpdGggdGhlIGV4cGVydHMgdGhlcmUuIEwzU00gZm9jdXNl
cyBvbiBMMyBWUE4gd2hpY2ggaXMgbGVzcyByZWxhdGVkIHRvIHRoaXMgd29yay4NCg0KDQoNCkJl
c3QgcmVnYXJkcywNCg0KSGFvDQoNCkZyb206IE9QU0FXRyBbbWFpbHRvOm9wc2F3Zy1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQWlqdW4gV2FuZw0KU2VudDogVHVlc2RheSwgT2N0b2Jl
ciAyNywgMjAxNSAxMDoxNiBBTQ0KVG86IG9wc2F3Z0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtP
UFNBV0ddIE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtY2hlbi1vcHNhd2ctZGNu
LXZuMnBuLW1hcHBpbmctMDAudHh0DQoNCkhpLCBIYW86DQoNCkkgdGhpbmsgdGhpcyBkcmFmdCBp
cyB1c2VmdWwgZm9yIHRoZSBzZXJ2aWNlIHByb3ZpZGVyIHRvIGRlcGxveSB2aXJ0dWFsIG5ldHdv
cmsgcmVsYXRlZCBWQVMgd2l0aGluIERDIGFuZCBjYW4gYmUgZXh0ZW5kZWQgYmV5b25kIHRvIGNv
dmVyIFdBTiBkb21haW4gZnVydGhlci4gIEFmdGVyIHN0YW5kYXJkaXppbmcgdGhlIGZhYnJpYyBz
ZXJ2aWNlcyBtb2RlbCwgdGhlIGNvbXBsZXggb2YgdGhlIFZBUyBhcHBsaWNhdGlvbiBkZXZlbG9w
bWVudCBhbmQgdGhlIG5ldHdvcmsgbWFuYWdlbWVudCBjYW4gYmUgcmVsaWV2ZWQgbGFyZ2VseS4g
IEl0IGlzIGFsc28gY29pbmNpZGUgd2l0aCB0aGUgZWZmb3J0cyBvZiB2YXJpb3VzIFlhbmcgbW9k
ZWwgZGVmaW5pdGlvbnMgdGhhdCBhcmUgdW5kZXJnb2luZyBpbiBzZXZlcmFsIElFVEYgV0cuDQpG
cm9tIHRoZSB2aWV3cG9pbnQgb2Ygc2VydmljZSBwcm92aWRlciwgdGhlIFZOMlBOIG1hcHBpbmcg
YXJjaGl0ZWN0dXJlIGlzIG9uZSBleGFtcGxlIG9mIG5ldHdvcmsgbW9kZWwgZGVwbG95bWVudCBz
Y2VuYXJpby4gaWYgd2UgY2FuIGNsYXJpZnkgYW5kIG1ha2UgY29uc2Vuc3VzIG9uIHRoaXMgdXNl
IGNhc2UsIHRoZW4gd2UgY2FuIG1vdmUgZm9yd2FyZCBmdXJ0aGVyLCBkZWZpbmUgdGhlIHJlbGF0
ZWQgWWFuZyBtb2RlbCBhbmQgYWNjZWxlcmF0ZSB0aGUgZGVwbG95bWVudCBvZiBWQVMgc2Vydmlj
ZXMgZm9yIHRlbmFudC4NCg0KTlZPMyBXRyBhbmQgTDNTTSBXRyBhcmUgbm93IHdvcmtpbmcgb24g
dGhlIHNpbWlsYXIgdG9waWNzLCB5b3UgY2FuIGFsc28gY29udGFjdCB0aGVtIGZvciBtb3JlIGRl
ZXBlciBkaXNjdXNzaW9uLg0KDQpCZXN0IFJlZ2FyZHMuDQoNCkFpanVuIFdhbmcNCg0KQ2hpbmEg
VGVsZWNvbSBDb3Jwb3JhdGlvbiBMaW1pdGVkIEJlaWppbmcgUmVzZWFyY2ggSW5zdGl0dXRlDQpJ
bnRlbGxpZ2VudCBOZXR3b3JrIFByb2R1Y3QgTGluZQ0KDQoNCkZyb206IE9QU0FXRyBbbWFpbHRv
Om9wc2F3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQ2hlbmhhbyAocGhpbGlwcykN
ClNlbnQ6IFR1ZXNkYXksIE9jdG9iZXIgMjAsIDIwMTUgNToxMyBQTQ0KVG86IG9wc2F3Z0BpZXRm
Lm9yZzxtYWlsdG86b3BzYXdnQGlldGYub3JnPg0KU3ViamVjdDogW09QU0FXR10gRlc6IE5ldyBW
ZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtY2hlbi1vcHNhd2ctZGNuLXZuMnBuLW1hcHBp
bmctMDAudHh0DQoNCg0KRGVhciBhbGwsDQoNCg0KDQpUaGlzIGlzIGEgbmV3IGRyYWZ0IGZvciBv
cHNhd2cuIEl0IG1haW5seSBhbmFseXNpcyB0aGUgaXNzdWVzIGV4aXN0ZWQgaW4gZGVwbG95aW5n
IHRoZSB2aXJ0dWFsIG5ldHdvcmsgdG8gdGhlIHVuZGVybmVhdGggcGh5c2ljYWwgbmV0d29yayBp
biBEYXRhQ2VudGVyIG5ldHdvcmsgLiBUaGUgYmFzaWMgaWRlYSBpcyB0byBhYnN0cmFjdCB0aGUg
dW5kZXJuZWF0aCBwaHlzaWNhbCBuZXR3b3JrIGFzIHNldmVyYWwgZmFicmljcywgd2hpY2ggY2Fu
IHByb3ZpZGUgdGhlIGZhYnJpYyBzZXJ2aWNlcyB0byB0aGUgdXBwZXItbGF5ZXIgYXBwbGljYXRp
b24vbmV0d29yayBhZG1pbmlzdHJhdG9yLCB0byBmYWNpbGl0YXRlIHRoZSB3aG9sZSBjb25maWd1
cmF0aW9uIHByb2NlZHVyZS4NCg0KDQoNCldlIHdvdWxkIGxpa2UgdG8gaGVhciB5b3VyIGNvbW1l
bnRzLCB0aGFua3MuDQoNCg0KDQoNCg0KQmVzdCByZWdhcmRzLA0KDQpIYW8NCg0KDQoNCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc8bWFp
bHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4gW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0
Zi5vcmddDQpTZW50OiBNb25kYXksIE9jdG9iZXIgMTksIDIwMTUgNToyMSBQTQ0KVG86IExpeWl6
aG91OyBDaGVuaGFvIChwaGlsaXBzKTsgWGluZ2p1biBDaHU7IFlhcGVuZyBXdTsgWWFwZW5nIFd1
OyBMaXlpemhvdTsgQ2hlbmhhbyAocGhpbGlwcyk7IFhpbmdqdW4gQ2h1DQpTdWJqZWN0OiBOZXcg
VmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBw
aW5nLTAwLnR4dA0KDQoNCg0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1jaGVuLW9w
c2F3Zy1kY24tdm4ycG4tbWFwcGluZy0wMC50eHQNCg0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1
Ym1pdHRlZCBieSBIYW8gQ2hlbiBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoN
Cg0KDQpOYW1lOiAgICAgICAgICAgICAgIGRyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBw
aW5nDQoNClJldmlzaW9uOiAgMDANCg0KVGl0bGU6ICAgICAgICAgICAgICAgICAgVmlydHVhbCBO
ZXR3b3JrIHRvIFBoeXNpY2FsIE5ldHdvcmsgTWFwcGluZyBpbiBEYXRhQ2VudGVyIE5ldHdvcmsN
Cg0KRG9jdW1lbnQgZGF0ZTogICAgICAgMjAxNS0xMC0xOA0KDQpHcm91cDogICAgICAgICAgICAg
ICBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCg0KUGFnZXM6ICAgICAgICAgICAgICAgMTINCg0KVVJM
OiAgICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1j
aGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZy0wMC50eHQNCg0KU3RhdHVzOiAgICAgICAgIGh0
dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJw
bi1tYXBwaW5nLw0KDQpIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBwaW5nLTAwDQoNCg0KDQoNCg0KQWJzdHJh
Y3Q6DQoNCiAgIENsb3VkIHRlbmFudCBuZWVkcyB2aXJ0dWFsIG5ldHdvcmsgdG8gaW50ZXJjb25u
ZWN0IHRoZWlyIFZNcyBvbg0KDQogICBzZXJ2ZXIuIEluIG9yZGVyIHRvIGVmZmVjdGl2ZWx5IGFu
ZCBlZmZpY2llbnRseSBtYXAgdmlydHVhbCBuZXR3b3JrDQoNCiAgIHRvIHBoeXNpY2FsIG5ldHdv
cmssIGNlcnRhaW4gbWVjaGFuaXNtIHNob3VsZCBiZSBlbXBsb3llZC4NCg0KDQoNCiAgIFRoaXMg
bWVtbyBhbmFseXNpcyB0aGUgZXhpc3RpbmcgVk4yUE4gbWFwcGluZyB0ZWNobmlxdWUgZW1wbG95
ZWQgaW4NCg0KICAgRGF0YUNlbnRlciBhbmQgcG9pbnQgb3V0IHRoZSBwb3RlbnRpYWwgc2hvcnRj
b21pbmdzIGxpZSBpbiBpdC4gVGhpcw0KDQogICBtZW1vIGFsc28gdHJ5IHRvIHByb3ZpZGUgYSBn
ZW5lcmljIG1lY2hhbmlzbSB0byBmYWNpbGl0YXRlIHRoZSBWTjJQTg0KDQogICBtYXBwaW5nIGlu
IERhdGFDZW50ZXIgbmV0d29yay4NCg0KDQoNCg0KDQoNCg0KDQoNClBsZWFzZSBub3RlIHRoYXQg
aXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Np
b24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0
b29scy5pZXRmLm9yZy4NCg0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlZlcmRhbmE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0K
LyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5N
c29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJdGV4dC1h
bGlnbjpqdXN0aWZ5Ow0KCXRleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGg7DQoJZm9udC1zaXpl
OjEwLjVwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCmE6bGluaywg
c3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJs
aW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29QbGFpblRl
eHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHls
ZS1saW5rOiLnuq/mlofmnKwgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4w
MDAxcHQ7DQoJZm9udC1zaXplOjEwLjVwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBk
aXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6
IuaJueazqOahhuaWh+acrCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAw
MDFwdDsNCgl0ZXh0LWFsaWduOmp1c3RpZnk7DQoJdGV4dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFw
aDsNCglmb250LXNpemU6OS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijt9DQpzcGFuLkNoYXINCgl7bXNvLXN0eWxlLW5hbWU6Iue6r+aWh+acrCBDaGFyIjsNCgltc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms657qv5paH5pysOw0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkNoYXIw
DQoJe21zby1zdHlsZS1uYW1lOiLmibnms6jmoYbmlofmnKwgQ2hhciI7DQoJbXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOuaJueazqOahhuaWh+acrDsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uRW1haWxTdHlsZTIxDQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUyMg0KCXttc28tc3R5bGUtdHlwZTpwZXJz
b25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5
N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjMNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30N
Ci5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6
ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0K
CW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0K
CXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1s
PjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpl
eHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVs
YXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJaSC1DTiIgbGlu
az0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9InRleHQtanVzdGlmeS10cmltOnB1bmN0dWF0
aW9uIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkhpIEFpanVuLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5S
ZWFsbHkgYXBwcmVjaWF0ZSBmb3IgeW91ciBjb21tZW50cy4gWWVzLCB0aGlzIGRyYWZ0IGRlc2Ny
aWJlcyB0aGUgVk4yUE4gbWFwcGluZyBhcmNoaXRlY3R1cmUgd2hpY2ggZm9jdXNlcyBvbiBhIGZh
YnJpYyBiYXNlZCBzZXJ2aWNlIG1vZGVsIChha2EgRmFhUyAtIEZhYnJpYyBhcyBhIFNlcnZpY2Up
LiAmbmJzcDtUaGlzIHdvcmsgaGFzIHdpa2kgcGFnZQ0KIGluIE9ETCBhdCA8YSBocmVmPSJodHRw
czovL3dpa2kub3BlbmRheWxpZ2h0Lm9yZy92aWV3L1Byb2plY3RfUHJvcG9zYWxzOkZhYVMiPmh0
dHBzOi8vd2lraS5vcGVuZGF5bGlnaHQub3JnL3ZpZXcvUHJvamVjdF9Qcm9wb3NhbHM6RmFhUzwv
YT4gYW5kIGhhcyBydW5uaW5nIGNvZGUgYXQNCjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9v
cGVuZGF5bGlnaHQvZmFhcyI+aHR0cHM6Ly9naXRodWIuY29tL29wZW5kYXlsaWdodC9mYWFzPC9h
PiAuIEN1cnJlbnRseSB0d28gWUFORyBtb2RlbHMgYXJlIGJlaW5nIGRldmVsb3BlZDogMSkgdGhl
IGZhYnJpYyAmbmJzcDtzZXJ2aWNlIFlBTkcgbW9kZWwgLCAyKSB0aGUgZGV2aWNlIGNvbmZpZyBZ
QU5HIG1vZGVsLiBXZSB3aWxsIHN1Ym1pdCB0aGVtIGZvciBkaXNjdXNzaW9uIGxhdGVyLg0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5
N0QiPlNvIGZhciB3ZSBmb2N1cyBvbiB0aGUgaW50cmEtREMgc2NlbmFyaW8gYnV0IEkgdGhpbmsg
aXQgaXMgZXh0ZW5kYWJsZS4gV2Ugd291bGQgbGlrZSB0byBkaXNjdXNzIG1vcmUgd2l0aCB5b3Ug
b24gdGhlIFdBTiBleHRlbnNpb24uIFRoaXMgd29yayBpczwvc3Bhbj48c3BhbiBsYW5nPSJFTi1V
UyI+DQo8c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+bm90IGxpbWl0ZWQgdG8gb3ZlcmxheSBz
dWNoIGFzIFZYTEFOLiBWTEFOIGFuZCBUUklMTCBhcmUgYWxzbyBpbmNsdWRlZC4gU28gaW4gbXkg
b3BpbmlvbiBpdCBpcyBtb3JlIGdlbmVyaWMgY29tcGFyZWQgdG8gTlZPMyBvdmVybGF5IG5ldHdv
cmsuIEZvciBzdXJlIHdlIHdpbGwgY3Jvc3MgY2hlY2sgd2l0aCB0aGUgZXhwZXJ0cyB0aGVyZS4g
TDNTTSBmb2N1c2VzIG9uIEwzIFZQTiB3aGljaCBpcyBsZXNzDQogcmVsYXRlZCB0byB0aGlzIHdv
cmsuIDxvOnA+PC9vOnA+PC9zcGFuPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkJlc3QgcmVnYXJkcyw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
SGFvPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVD
NERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgYWxpZ249ImxlZnQiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IE9QU0FXRyBbbWFpbHRvOm9wc2F3Zy1ib3VuY2Vz
QGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5BaWp1biBXYW5nPGJyPg0KPGI+U2VudDo8
L2I+IFR1ZXNkYXksIE9jdG9iZXIgMjcsIDIwMTUgMTA6MTYgQU08YnI+DQo8Yj5Ubzo8L2I+IG9w
c2F3Z0BpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW09QU0FXR10gTmV3IFZlcnNp
b24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZy0w
MC50eHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgYWxpZ249ImxlZnQiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkhpLCBIYW86PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PkkgdGhpbmsgdGhpcyBkcmFmdCBpcyB1c2VmdWwgZm9yIHRoZSBzZXJ2aWNlIHByb3ZpZGVyIHRv
IGRlcGxveSB2aXJ0dWFsIG5ldHdvcmsgcmVsYXRlZCBWQVMgd2l0aGluIERDIGFuZCBjYW4gYmUg
ZXh0ZW5kZWQgYmV5b25kIHRvIGNvdmVyIFdBTiBkb21haW4gZnVydGhlci4gJm5ic3A7QWZ0ZXIg
c3RhbmRhcmRpemluZyB0aGUgZmFicmljIHNlcnZpY2VzDQogbW9kZWwsIHRoZSBjb21wbGV4IG9m
IHRoZSBWQVMgYXBwbGljYXRpb24gZGV2ZWxvcG1lbnQgYW5kIHRoZSBuZXR3b3JrIG1hbmFnZW1l
bnQgY2FuIGJlIHJlbGlldmVkIGxhcmdlbHkuICZuYnNwO0l0IGlzIGFsc28gY29pbmNpZGUgd2l0
aCB0aGUgZWZmb3J0cyBvZiB2YXJpb3VzIFlhbmcgbW9kZWwgZGVmaW5pdGlvbnMgdGhhdCBhcmUg
dW5kZXJnb2luZyBpbiBzZXZlcmFsIElFVEYgV0cuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdE
Ij5Gcm9tIHRoZSB2aWV3cG9pbnQgb2Ygc2VydmljZSBwcm92aWRlciwgdGhlIFZOMlBOIG1hcHBp
bmcgYXJjaGl0ZWN0dXJlIGlzIG9uZSBleGFtcGxlIG9mIG5ldHdvcmsgbW9kZWwgZGVwbG95bWVu
dCBzY2VuYXJpby4gaWYgd2UgY2FuIGNsYXJpZnkgYW5kIG1ha2UgY29uc2Vuc3VzIG9uIHRoaXMg
dXNlIGNhc2UsIHRoZW4gd2UgY2FuIG1vdmUNCiBmb3J3YXJkIGZ1cnRoZXIsIGRlZmluZSB0aGUg
cmVsYXRlZCBZYW5nIG1vZGVsIGFuZCBhY2NlbGVyYXRlIHRoZSBkZXBsb3ltZW50IG9mIFZBUyBz
ZXJ2aWNlcyBmb3IgdGVuYW50LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5OVk8zIFdHIGFuZCBMM1NNIFdHIGFyZSBub3cgd29y
a2luZyBvbiB0aGUgc2ltaWxhciB0b3BpY3MsIHlvdSBjYW4gYWxzbyBjb250YWN0IHRoZW0gZm9y
IG1vcmUgZGVlcGVyIGRpc2N1c3Npb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkJlc3QgUmVnYXJkcy48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIGFsaWduPSJsZWZ0IiBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0Ij48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFu
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkFpanVuIFdhbmc8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0ibGVmdCIg
c3R5bGU9InRleHQtYWxpZ246bGVmdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0ibGVmdCIgc3R5bGU9InRleHQtYWxpZ246bGVmdCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5DaGlu
YSZuYnNwO1RlbGVjb20mbmJzcDtDb3Jwb3JhdGlvbiZuYnNwO0xpbWl0ZWQmbmJzcDtCZWlqaW5n
Jm5ic3A7UmVzZWFyY2gmbmJzcDtJbnN0aXR1dGUmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0ibGVmdCIgc3R5bGU9InRleHQtYWxpZ246bGVm
dCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij5JbnRlbGxpZ2VudCBOZXR3b3JrIFByb2R1Y3QgTGluZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgYWxpZ249ImxlZnQiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPjxiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IE9QU0FXRyBbPGEgaHJlZj0ibWFp
bHRvOm9wc2F3Zy1ib3VuY2VzQGlldGYub3JnIj5tYWlsdG86b3BzYXdnLWJvdW5jZXNAaWV0Zi5v
cmc8L2E+XQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5DaGVuaGFvIChwaGlsaXBzKTxicj4NCjxiPlNl
bnQ6PC9iPiBUdWVzZGF5LCBPY3RvYmVyIDIwLCAyMDE1IDU6MTMgUE08YnI+DQo8Yj5Ubzo8L2I+
IDxhIGhyZWY9Im1haWx0bzpvcHNhd2dAaWV0Zi5vcmciPm9wc2F3Z0BpZXRmLm9yZzwvYT48YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gW09QU0FXR10gRlc6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBm
b3IgZHJhZnQtY2hlbi1vcHNhd2ctZGNuLXZuMnBuLW1hcHBpbmctMDAudHh0PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJs
ZWZ0IiBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0i
RU4tVVMiPkRlYXIgYWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+VGhpcyBpcyBhIG5ldyBk
cmFmdCBmb3Igb3BzYXdnLiBJdCBtYWlubHkgYW5hbHlzaXMgdGhlIGlzc3VlcyBleGlzdGVkIGlu
IGRlcGxveWluZyB0aGUgdmlydHVhbCBuZXR3b3JrIHRvIHRoZSB1bmRlcm5lYXRoIHBoeXNpY2Fs
IG5ldHdvcmsgaW4gRGF0YUNlbnRlciBuZXR3b3JrIC4gVGhlIGJhc2ljIGlkZWEgaXMgdG8gYWJz
dHJhY3QgdGhlIHVuZGVybmVhdGggcGh5c2ljYWwNCiBuZXR3b3JrIGFzIHNldmVyYWwgZmFicmlj
cywgd2hpY2ggY2FuIHByb3ZpZGUgdGhlIGZhYnJpYyBzZXJ2aWNlcyB0byB0aGUgdXBwZXItbGF5
ZXIgYXBwbGljYXRpb24vbmV0d29yayBhZG1pbmlzdHJhdG9yLCB0byBmYWNpbGl0YXRlIHRoZSB3
aG9sZSBjb25maWd1cmF0aW9uIHByb2NlZHVyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPldl
IHdvdWxkIGxpa2UgdG8gaGVhciB5b3VyIGNvbW1lbnRzLCB0aGFua3MuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxh
bmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5IYW88bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJv
bTogPGEgaHJlZj0ibWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyI+aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnPC9hPiBbPGEgaHJlZj0ibWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9y
ZyI+bWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZzwvYT5dDQo8YnI+DQpTZW50OiBNb25k
YXksIE9jdG9iZXIgMTksIDIwMTUgNToyMSBQTTxicj4NClRvOiBMaXlpemhvdTsgQ2hlbmhhbyAo
cGhpbGlwcyk7IFhpbmdqdW4gQ2h1OyBZYXBlbmcgV3U7IFlhcGVuZyBXdTsgTGl5aXpob3U7IENo
ZW5oYW8gKHBoaWxpcHMpOyBYaW5nanVuIENodTxicj4NClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5v
dGlmaWNhdGlvbiBmb3IgZHJhZnQtY2hlbi1vcHNhd2ctZGNuLXZuMnBuLW1hcHBpbmctMDAudHh0
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+QSBuZXcgdmVyc2lvbiBv
ZiBJLUQsIGRyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBwaW5nLTAwLnR4dDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij5oYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEhhbyBDaGVuIGFuZCBwb3N0ZWQg
dG8gdGhlIElFVEYgcmVwb3NpdG9yeS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPk5hbWU6Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBw
aW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
bGFuZz0iRU4tVVMiPlJldmlzaW9uOiZuYnNwOyAwMDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaXRsZTombmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgVmlydHVhbCBOZXR3b3JrIHRvIFBo
eXNpY2FsIE5ldHdvcmsgTWFwcGluZyBpbiBEYXRhQ2VudGVyIE5ldHdvcms8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+RG9j
dW1lbnQgZGF0ZTombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgMjAxNS0xMC0x
ODxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxh
bmc9IkVOLVVTIj5Hcm91cDombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgSW5kaXZpZHVhbCBT
dWJtaXNzaW9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPlBhZ2VzOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAxMjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9
IkVOLVVTIj5VUkw6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVy
bmV0LWRyYWZ0cy9kcmFmdC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZy0wMC50eHQiPg0K
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Q7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHBzOi8v
d3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4t
bWFwcGluZy0wMC50eHQ8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5TdGF0dXM6Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9Imh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBwaW5nLyI+
DQo8c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtY2hlbi1vcHNhd2ctZGNuLXZuMnBuLW1h
cHBpbmcvPC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+SHRtbGl6ZWQ6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1jaGVuLW9wc2F3Zy1kY24tdm4ycG4tbWFwcGluZy0wMCI+DQo8c3BhbiBzdHlsZT0iY29sb3I6
IzFGNDk3RDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWNoZW4tb3BzYXdnLWRjbi12bjJwbi1tYXBwaW5nLTAwPC9zcGFuPjwvYT48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5BYnN0cmFjdDo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5i
c3A7Jm5ic3A7IENsb3VkIHRlbmFudCBuZWVkcyB2aXJ0dWFsIG5ldHdvcmsgdG8gaW50ZXJjb25u
ZWN0IHRoZWlyIFZNcyBvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDsmbmJzcDsgc2VydmVyLiBJbiBvcmRlciB0
byBlZmZlY3RpdmVseSBhbmQgZWZmaWNpZW50bHkgbWFwIHZpcnR1YWwgbmV0d29yazxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij4mbmJzcDsmbmJzcDsgdG8gcGh5c2ljYWwgbmV0d29yaywgY2VydGFpbiBtZWNoYW5pc20gc2hv
dWxkIGJlIGVtcGxveWVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7Jm5ic3A7IFRo
aXMgbWVtbyBhbmFseXNpcyB0aGUgZXhpc3RpbmcgVk4yUE4gbWFwcGluZyB0ZWNobmlxdWUgZW1w
bG95ZWQgaW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7Jm5ic3A7IERhdGFDZW50ZXIgYW5kIHBvaW50IG91dCB0
aGUgcG90ZW50aWFsIHNob3J0Y29taW5ncyBsaWUgaW4gaXQuIFRoaXM8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7
Jm5ic3A7IG1lbW8gYWxzbyB0cnkgdG8gcHJvdmlkZSBhIGdlbmVyaWMgbWVjaGFuaXNtIHRvIGZh
Y2lsaXRhdGUgdGhlIFZOMlBOPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyBtYXBwaW5nIGluIERhdGFD
ZW50ZXIgbmV0d29yay48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhl
IHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBh
cmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
VGhlIElFVEYgU2VjcmV0YXJpYXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_15F8424C3FD6FE4FBC5651B784DBF82189C8A5F0nkgeml503mbxchi_--


From nobody Tue Oct 27 15:50:20 2015
Return-Path: <joelja@bogus.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0401A6F77 for <opsawg@ietfa.amsl.com>; Tue, 27 Oct 2015 15:50:19 -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 mRi1pX-zHSNq for <opsawg@ietfa.amsl.com>; Tue, 27 Oct 2015 15:50:18 -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 8FBED1A6F6F for <opsawg@ietf.org>; Tue, 27 Oct 2015 15:50:18 -0700 (PDT)
Received: from mb.local ([8.18.217.2]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id t9RMoHUx033671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <opsawg@ietf.org>; Tue, 27 Oct 2015 22:50:18 GMT (envelope-from joelja@bogus.com)
To: "opsawg@ietf.org" <opsawg@ietf.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <562FFFA3.8070202@bogus.com>
Date: Tue, 27 Oct 2015 15:50:11 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Thunderbird/42.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mGfwCvbthqsdgERcbFrevvTVGGge4Bhm2"
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/2JE20jN9JhmoG51JxaCDJvL-1-0>
Subject: [OPSAWG] Joint opsawg/opsarea meeting - 15:20-17:20 Thursday Afternoon 11/5/2015
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2015 22:50:19 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--mGfwCvbthqsdgERcbFrevvTVGGge4Bhm2
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

If you have agenda items you'd like to address to the ops area  please
get them in soon.

Joel and Benoit


--mGfwCvbthqsdgERcbFrevvTVGGge4Bhm2
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
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlYv/6QACgkQ8AA1q7Z/VrKxmACeLn1qlDb6pIi7pG3VBCEbKVEH
ewcAniFW64OxS0EMJhI385ltJdXiMyTS
=u0k0
-----END PGP SIGNATURE-----

--mGfwCvbthqsdgERcbFrevvTVGGge4Bhm2--


From nobody Tue Oct 27 20:41:53 2015
Return-Path: <bingxuere@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1B01B3420 for <opsawg@ietfa.amsl.com>; Tue, 27 Oct 2015 20:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 v7uP9nKk6yMr for <opsawg@ietfa.amsl.com>; Tue, 27 Oct 2015 20:41:48 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FB921B43E2 for <opsawg@ietf.org>; Tue, 27 Oct 2015 20:41:48 -0700 (PDT)
Received: by iody8 with SMTP id y8so87869997iod.1 for <opsawg@ietf.org>; Tue, 27 Oct 2015 20:41:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=AA/WoHfD5gqA+GvgXWGRQCtCjFR622N1uxy/Bxdhe8c=; b=ig38R+1WiBr/b+N/1AET+bQjKR10PQumFS6PX4lQkdMFKpDnTJ5/dcjFXzqxOAOG5k UO+xqBdzos8vHaWGYvXmX0R2jGVguyqnl+6+8DNdg+ChI2ov73wKmscr8+kCembraroF klXxKNBk+wKjo4lwwpsT5VZbSllnHk1KaEkhKO4MKwshsmjd+/EZzFpeqEmOTbnZmepw oCSjtePws3TiYf5IMesV0dADlSdRRAYop8w0IqJubZW1kKpR9m2laGUVn+L7OOQjE2tv oPeRYHvSXIOspcwo2bwTfGlkJzb0/oKx1JgoUvOT4F2wt/hMO1zp3sh4QJTL2jwbnW0o Bi7w==
X-Received: by 10.107.167.78 with SMTP id q75mr48860863ioe.127.1446003707626;  Tue, 27 Oct 2015 20:41:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.34.179 with HTTP; Tue, 27 Oct 2015 20:41:08 -0700 (PDT)
From: Qiong <bingxuere@gmail.com>
Date: Wed, 28 Oct 2015 11:41:08 +0800
Message-ID: <CAH3bfABJQ8HtU4w9WPvbSs1KbLyo=U9YpCzEx2-bYJefwc3MGg@mail.gmail.com>
To: opsawg@ietf.org
Content-Type: multipart/alternative; boundary=001a114293a8564b49052321f974
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/iSDpCOBrZqZFCm1JMc0XhAo7Jf8>
Subject: [OPSAWG] =?utf-8?q?=5Bopsawg=5DFW=3A_New_Version_Notification_for?= =?utf-8?q?_draft-sun-i2apm-addr=E2=80=8Bess-pool-management-=E2=80=8Barch?= =?utf-8?q?-00?=
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2015 03:41:52 -0000

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

Dear all,

We have submitted two drafts on address pool management, mainly to simplify
the address management procedures in current BNG/CGN/etc. Your comments are
more than welcome.

Thanks a lot!

Qiong Sun from China Telecom


*From:* internet-drafts <internet-drafts@ietf.org>
*Date:* 2015-10-18 17:53
*To:* Qiong Sun <sunqiong@ctbri.com.cn>; Qiong Sun
<sunqiong@ctbri.com.cn>; Chongfeng
Xie <xiechf@ctbri.com.cn>; Jun Bi <junbi@tsinghua.edu.cn>; Jun Bi
<junbi@tsinghua.edu.cn>; Chongfeng Xie <xiechf@ctbri.com.cn>
*Subject:* New Version Notification for
draft-sun-i2apm-address-pool-management-arch-00.txt



A new version of I-D, draft-sun-i2apm-address-pool-management-arch-00.txt
has been successfully submitted by Qiong Sun and posted to the
IETF repository.

Name: draft-sun-i2apm-address-pool-management-arch
Revision: 00
Title: Interface to the Address Pool Management
Document date: 2015-10-18
Group: Individual Submission
Pages: 12
URL:
https://www.ietf.org/internet-drafts/draft-sun-i2apm-address-pool-management-arch-00.txt
Status:
https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-management-arch/
Htmlized:
https://tools.ietf.org/html/draft-sun-i2apm-address-pool-management-arch-00


Abstract:
   This document describes an mechanism for a standard, programmatic
   interface for address pool management.  With the remaining IPv4
   address becoming more and more scattered, it is complicated to
   manually configure the address pools on lots of Broadband Network
   Gateways(BNGs) for operators.  By introducing SDN/NFV in BNG, the
   address pools can be allocated in a centralized way.  It will not
   only simplify the address management for operators, but also improve
   the utilization efficiency of the address pool.




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



-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================




-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================


-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><div>Dear all,=
</div><div><br></div><div>We have submitted two drafts on address pool mana=
gement, mainly to simplify the address management procedures in current BNG=
/CGN/etc.=C2=A0Your comments are more than welcome.</div><div><br></div><di=
v>Thanks a lot!</div><div><br></div><div>Qiong Sun from China Telecom</div>=
<div><br></div><div><div style=3D"color:rgb(0,0,0);line-height:21px;font-fa=
mily:=E5=AE=8B=E4=BD=93;font-size:14px">=C2=A0</div><div style=3D"border-st=
yle:solid none none;padding:3pt 0cm 0cm;color:rgb(0,0,0);line-height:21px;f=
ont-family:=E5=AE=8B=E4=BD=93;font-size:14px;border-top-color:rgb(181,196,2=
23);border-top-width:1pt"><div style=3D"padding:8px;font-family:tahoma;font=
-size:12px;background-color:rgb(239,239,239)"><div><b>From:</b>=C2=A0<a hre=
f=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts</a>=
</div><div><b>Date:</b>=C2=A02015-10-18=C2=A017:53</div><div><b>To:</b>=C2=
=A0<a href=3D"mailto:sunqiong@ctbri.com.cn" target=3D"_blank">Qiong Sun</a>=
;=C2=A0<a href=3D"mailto:sunqiong@ctbri.com.cn" target=3D"_blank">Qiong Sun=
</a>;=C2=A0<a href=3D"mailto:xiechf@ctbri.com.cn" target=3D"_blank">Chongfe=
ng Xie</a>;=C2=A0<a href=3D"mailto:junbi@tsinghua.edu.cn" target=3D"_blank"=
>Jun Bi</a>;=C2=A0<a href=3D"mailto:junbi@tsinghua.edu.cn" target=3D"_blank=
">Jun Bi</a>;=C2=A0<a href=3D"mailto:xiechf@ctbri.com.cn" target=3D"_blank"=
>Chongfeng Xie</a></div><div><b>Subject:</b>=C2=A0New Version Notification =
for draft-sun-i2apm-address-pool-management-arch-00.txt</div></div></div><d=
iv style=3D"color:rgb(0,0,0);line-height:21px;font-family:=E5=AE=8B=E4=BD=
=93;font-size:14px">=C2=A0</div></div><div><br></div><div><br></div><div st=
yle=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Ta=
homa;font-size:14px">A new version of I-D, draft-sun-i2apm-address-pool-man=
agement-arch-00.txt</div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=
=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">has been successfully=
 submitted by Qiong Sun and posted to the</div><div style=3D"color:rgb(0,0,=
0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=
IETF repository.</div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=
=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0</div><div style=
=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahom=
a;font-size:14px">Name:	 draft-sun-i2apm-address-pool-management-arch</div>=
<div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=
=BB=91,Tahoma;font-size:14px">Revision:	00</div><div style=3D"color:rgb(0,0=
,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px"=
>Title:	 Interface to the Address Pool Management</div><div style=3D"color:=
rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-siz=
e:14px">Document date:	2015-10-18</div><div style=3D"color:rgb(0,0,0);font-=
family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">Group:	 =
Individual Submission</div><div style=3D"color:rgb(0,0,0);font-family:=E5=
=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">Pages:	 12</div><d=
iv style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=
=91,Tahoma;font-size:14px">URL:=C2=A0<a style=3D"text-decoration:none!impor=
tant" href=3D"https://www.ietf.org/internet-drafts/draft-sun-i2apm-address-=
pool-management-arch-00.txt" target=3D"_blank">https://www.ietf.org/interne=
t-drafts/draft-sun-i2apm-address-pool-management-arch-00.txt</a></div><div =
style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,=
Tahoma;font-size:14px">Status:=C2=A0<a style=3D"text-decoration:none!import=
ant" href=3D"https://datatracker.ietf.org/doc/draft-sun-i2apm-address-pool-=
management-arch/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-=
sun-i2apm-address-pool-management-arch/</a></div><div style=3D"color:rgb(0,=
0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px=
">Htmlized:=C2=A0<a style=3D"text-decoration:none!important" href=3D"https:=
//tools.ietf.org/html/draft-sun-i2apm-address-pool-management-arch-00" targ=
et=3D"_blank">https://tools.ietf.org/html/draft-sun-i2apm-address-pool-mana=
gement-arch-00</a></div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=
=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0</div><div styl=
e=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Taho=
ma;font-size:14px">=C2=A0</div><div style=3D"color:rgb(0,0,0);font-family:=
=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">Abstract:</div>=
<div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=
=BB=91,Tahoma;font-size:14px">=C2=A0=C2=A0 This document describes an mecha=
nism for a standard, programmatic</div><div style=3D"color:rgb(0,0,0);font-=
family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0=
=C2=A0 interface for address pool management.=C2=A0 With the remaining IPv4=
</div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=
=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0=C2=A0 address becoming more and =
more scattered, it is complicated to</div><div style=3D"color:rgb(0,0,0);fo=
nt-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=
=A0=C2=A0 manually configure the address pools on lots of Broadband Network=
</div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=
=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0=C2=A0 Gateways(BNGs) for operato=
rs.=C2=A0 By introducing SDN/NFV in BNG, the</div><div style=3D"color:rgb(0=
,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14p=
x">=C2=A0=C2=A0 address pools can be allocated in a centralized way.=C2=A0 =
It will not</div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=
=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0=C2=A0 only simplify the=
 address management for operators, but also improve</div><div style=3D"colo=
r:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-s=
ize:14px">=C2=A0=C2=A0 the utilization efficiency of the address pool.</div=
><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=
=BB=91,Tahoma;font-size:14px">=C2=A0</div><div style=3D"color:rgb(0,0,0);fo=
nt-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</div><div style=3D"color:rgb(0,0,0);font-=
family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0</=
div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=
=E9=BB=91,Tahoma;font-size:14px">=C2=A0</div><div style=3D"color:rgb(0,0,0)=
;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">Pl=
ease note that it may take a couple of minutes from the time of submission<=
/div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=
=E9=BB=91,Tahoma;font-size:14px">until the htmlized version and diff are av=
ailable at <a href=3D"http://tools.ietf.org/" target=3D"_blank">tools.ietf.=
org</a>.</div><div style=3D"color:rgb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=
=E9=9B=85=E9=BB=91,Tahoma;font-size:14px">=C2=A0</div><div style=3D"color:r=
gb(0,0,0);font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,Tahoma;font-size=
:14px">The IETF Secretariat</div><div><div><img src=3D"https://ssl.gstatic.=
com/ui/v1/icons/mail/images/cleardot.gif"></div></div><span><font color=3D"=
#888888"><span><font color=3D"#888888"><div><br></div></font></span><div><b=
r clear=3D"all"><br>-- <br></div><div>=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<br>Qiong Sun<br>China Telecom Beijing Research =
Institude<br><br><br>Open source code:<br>lightweight 4over6: <i><a href=3D=
"http://sourceforge.net/projects/laft6/" target=3D"_blank">http://sourcefor=
ge.net/projects/laft6/</a></i><br>PCP-natcoord:<i> <a href=3D"http://source=
forge.net/projects/pcpportsetdemo/" target=3D"_blank">http://sourceforge.ne=
t/projects/pcpportsetdemo/</a> </i><br>=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<br><br></div></font></span></div></div><br><=
br clear=3D"all"><br>-- <br><div class=3D"gmail_signature">=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<br>Qiong Sun<br>China Tele=
com Beijing Research Institude<br><br><br>Open source code:<br>lightweight =
4over6: <i><a href=3D"http://sourceforge.net/projects/laft6/" target=3D"_bl=
ank">http://sourceforge.net/projects/laft6/</a></i><br>PCP-natcoord:<i> <a =
href=3D"http://sourceforge.net/projects/pcpportsetdemo/" target=3D"_blank">=
http://sourceforge.net/projects/pcpportsetdemo/</a> </i><br>=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<br><br clear=3D"all"><b=
r>-- <br></div><div class=3D"gmail_signature">=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<br>Qiong Sun<br>China Telecom Beijing =
Research Institude<br><br><br>Open source code:<br>lightweight 4over6: <i><=
a href=3D"http://sourceforge.net/projects/laft6/" target=3D"_blank">http://=
sourceforge.net/projects/laft6/</a></i><br>PCP-natcoord:<i> <a href=3D"http=
://sourceforge.net/projects/pcpportsetdemo/" target=3D"_blank">http://sourc=
eforge.net/projects/pcpportsetdemo/</a> </i><br>=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<br><br></div>
</div>

--001a114293a8564b49052321f974--

