
From nobody Sun Feb 12 19:48:56 2017
Return-Path: <zhoutianran@huawei.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1DFA129513; Sun, 12 Feb 2017 19:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARRKfb8ClTSX; Sun, 12 Feb 2017 19:48:53 -0800 (PST)
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 5331D1293F0; Sun, 12 Feb 2017 19:48:53 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGJ13073; Mon, 13 Feb 2017 03:48:51 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 13 Feb 2017 03:48:49 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Mon, 13 Feb 2017 11:48:44 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "IPFIX@ietf.org" <IPFIX@ietf.org>
Thread-Topic: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
Thread-Index: AdKFqjl1xBXNvf7XRCiwopLruYITLAAAEJpw
Date: Mon, 13 Feb 2017 03:49:47 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-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.111.156.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.58A12CA3.01A3, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 33fb402d6dc0fc4450fa91eef5291391
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/NuMLPwttDZAYKm3WILI825-tyFI>
Cc: "draft-li-opsawg-ipfix-bgp-community.authors@ietf.org" <draft-li-opsawg-ipfix-bgp-community.authors@ietf.org>
Subject: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 03:48:55 -0000

Dear IPFIX,

Since the IPFIX WG is concluded, this IE extension draft is processed now i=
n OPSAWG.
Thanks very much for the previous comments and discussions on this draft in=
 this mailing list.
Now the OPSAWG is polling for adoption of this I-D. I sincerely appreciate =
your opinion and review.

Best Regards,
Tianran Zhou

-----Original Message-----
From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Tianran Zhou
Sent: Monday, February 13, 2017 11:37 AM
To: opsawg@ietf.org
Cc: opsawg-chairs@ietf.org
Subject: [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-=
02

Dear OPSAWG,

In Seoul, we got enough interest and positive response on this IPFIX IE ext=
ension draft.
By the authors' request, this email starts a formal poll. The chairs would =
like to know if the WG participants agree that the following document shoul=
d be adopted as a WG document in OPSAWG.

Export BGP community information in IP Flow Information Export (IPFIX)
https://tools.ietf.org/html/draft-li-opsawg-ipfix-bgp-community-02

The adoption poll will take two weeks. Please let us know your opinion by F=
eb 27. It would also be good to hear who is willing to review and/or implem=
ent or deploy the extension described in the document.

Since we already found that the majority of the f2f participants at our IET=
F97 session like this idea, please do speak up now if you do not agree or h=
ave serious objections (with explanation of course).

Regards,
Tianran

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


From nobody Sun Feb 12 21:16:07 2017
Return-Path: <gurong_cmcc@outlook.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C50A512947C; Sun, 12 Feb 2017 21:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.018
X-Spam-Level: 
X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CplEzs8iuJTl; Sun, 12 Feb 2017 21:16:03 -0800 (PST)
Received: from SNT004-OMC4S13.hotmail.com (snt004-omc4s13.hotmail.com [65.55.90.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A25891204D9; Sun, 12 Feb 2017 21:15:57 -0800 (PST)
Received: from APC01-PU1-obe.outbound.protection.outlook.com ([65.55.90.201]) by SNT004-OMC4S13.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sun, 12 Feb 2017 21:15:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LSxQV+i+VJhXoi43kQeNMVQ6033UQ7R536aWM9+72D8=; b=s71xQ3HUvTabTk/k4Zxhyc8kNEdU2T3hTWUz3By9hpYZO5QRByns212hE3VPFZt58AKCY84I+NcqyDVIEkLz2gMglP/Y2/qSYPwIQis/InqqkViiOXQVGqNcIKX+c5+vLlHp9/Arcq93reLTxBIcOPbL6kGHBBmaWity57Dovm5Vdz5SqKMnCbYID2syBsO/vSpcGSkqj+zGY6RVB6gn7slKYyBlj/weiVSbUzpysmqmOrZiMhwRnnF3MhCNzYANTJ7RGG5E9mTFz7q4/GxS6mY8OaP0XM/a1b4FBHUkYwbVXWDilMWAMlDllcE6X3Iq5MpHy1skGeA00LO54v93HQ==
Received: from HK2APC01FT007.eop-APC01.prod.protection.outlook.com (10.152.248.52) by HK2APC01HT168.eop-APC01.prod.protection.outlook.com (10.152.249.230) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.2; Mon, 13 Feb 2017 05:15:54 +0000
Received: from HKNPR02MB1843.apcprd02.prod.outlook.com (10.152.248.54) by HK2APC01FT007.mail.protection.outlook.com (10.152.248.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.2 via Frontend Transport; Mon, 13 Feb 2017 05:15:54 +0000
Received: from HKNPR02MB1843.apcprd02.prod.outlook.com ([fe80::55cc:8e34:53c7:e065]) by HKNPR02MB1843.apcprd02.prod.outlook.com ([fe80::55cc:8e34:53c7:e065%14]) with mapi id 15.01.0888.030; Mon, 13 Feb 2017 05:15:54 +0000
From: =?gb2312?B?ucsgyNY=?= <gurong_cmcc@outlook.com>
To: Tianran Zhou <zhoutianran@huawei.com>, "IPFIX@ietf.org" <IPFIX@ietf.org>
Thread-Topic: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
Thread-Index: AdKFqjl1xBXNvf7XRCiwopLruYITLAAAEJpwAANatM4=
Date: Mon, 13 Feb 2017 05:15:54 +0000
Message-ID: <HKNPR02MB1843C24EA99FEEE8D95015AF8B590@HKNPR02MB1843.apcprd02.prod.outlook.com>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=outlook.com;
x-incomingtopheadermarker: OriginalChecksum:6F6457D120566377CC1BBB099ECF8E8A85F566D6AF703A9B7C3D8B721DDC827B; UpperCasedChecksum:CA54324D6455C5831EDE89B05FFC36E03881442AFD492DC513E1D3F63250DAB7; SizeAsReceived:8036; Count:39
x-tmn: [8Pglmbr3zmy94/Rgk4fus0K0DA1IfHrBkvZtXywsu/M=]
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; HK2APC01HT168; 5:a1P79EytujiS8H5A8AgKmYeWDjG52mFjm2rfb8SfpoX6obVTiu3aQCIVv1EzclbFhD0vXTDcF5zL8KBcnVjmUsMwtEjZh6LTYHzEGqty57ysA/9MvTfqU5s0myfwbvy9k4yghA4CoUFYcRpkOR8H3g==; 24:m58H+acVcUWUoNJ2cXMnKuUDWcAdb7CR4ZcI356RUIF5iXgcNOG6zm+mJ/5aY3DRj+n8lu1jAuY9NXrLNPXvokkbsno04i7+7XfaBw/IKQM=; 7:KG6V19msC9wkvVCjhE3tQ7rPWcFY3yl2J4EHBNN9DMR2/Z/7BRyqxHz/KOzDW8vStz8NpyJpSIsKS5wVeNsZi26zR9kib5WxV6fj+UrXOM03Fjb15pNvzY8RG3/3rA7+pD4YWjBvjy9iB3FIr+8pO7NXrUHi0ahKmci35bKQXG+QcsLtew39QHSazx0CnoqjlRsWv10cMVOfVVSPu6ULi424DX+KSxgSfQJOZ6+iZ647TuS7der2zQ5k2u6RNPraV0W6sVinkiDL21XtIEys9pA6CGoWmqiZLF4oPR8a1e2Cz8Qs9lanZiWm+4A9CPdPJtwkQh/qsXj9p+DNA7HDzcF2JU0XTq7fEW/NQh9kqIh+yCC1F3pMzI1y0UUStguy74AroDDN9Pbt42OFiWFM1LaTup9/X7QfA6q1aIta+IDkVQ+J1q7peUPqVmPsDFSJ4lH6kIPFpy8cd/D+OfsRLsaxTUL/K8sIF1ZKsicxenfIEFqZFeF4YY55+K/lzCNOqOSKz7hxcjq4zbTXDPzyCg==
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900007); DIR:OUT; SFP:1102; SCL:1; SRVR:HK2APC01HT168; H:HKNPR02MB1843.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: a16193f5-ca3f-4c3a-f1dc-08d453cf62b2
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(5061506426)(5061507331)(1603103135)(1601125107)(1603101373)(1701031045); SRVR:HK2APC01HT168; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015086)(82015046); SRVR:HK2APC01HT168; BCL:0; PCL:0; RULEID:; SRVR:HK2APC01HT168; 
x-forefront-prvs: 02176E2458
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HKNPR02MB1843C24EA99FEEE8D95015AF8B590HKNPR02MB1843apcp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Feb 2017 05:15:54.2870 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT168
X-OriginalArrivalTime: 13 Feb 2017 05:15:57.0019 (UTC) FILETIME=[41B78AB0:01D285B8]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/-C5Opr_OqiIgN1gVuixyqxgCCaU>
Cc: "draft-li-opsawg-ipfix-bgp-community.authors@ietf.org" <draft-li-opsawg-ipfix-bgp-community.authors@ietf.org>
Subject: [IPFIX] =?gb2312?b?tPC4tDogV0cgYWRvcHRpb24gcG9sbCBmb3IgZHJhZnQt?= =?gb2312?b?bGktb3BzYXdnLWlwZml4LWJncC1jb21tdW5pdHktMDI=?=
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 05:16:06 -0000

--_000_HKNPR02MB1843C24EA99FEEE8D95015AF8B590HKNPR02MB1843apcp_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGksIGRlYXIgYWxsLiBBcyBhIGNvLWF1dGhvciwgSSBzdXBwb3J0IHRoZSBhZG9wdGlvbiBvZiB0
aGlzIGRyYWZ0IGFzIGEgd29yayBncm91cCBkb2N1bWVudC4gSGVyZSB0aHJlZSBpbmZvcm1hdGlv
biBlbGVtZW50cyBpbmNsdWRpbmcgYmdwQ29tbXVuaXR5LCBiZ3BTb3VyY2VDb21tdW5pdHlMaXN0
IGFuZCBiZ3BEZXN0aW5hdGlvbkNvbW11bml0eUxpc3QgYXJlIGludHJvZHVjZWQgaW4gb3JkZXIg
dG8gY2FycnkgQkdQIGNvbW11bml0eSBpbmZvcm1hdGlvbi4gV2UgZG8gdGhpbmsgaXQncyBhIG5l
Y2Vzc2FyeSBhbmQgdXNlZnVsIGV4dGVuc2lvbi4NCg0KDQpCZXN0IHJlZ2FyZHMuDQpHdSBSb25n
DQpndXJvbmdfY21jY0BvdXRsb29rLmNvbQ0KZ3Vyb25nQGNoaW5hbW9iaWxlLmNvbQ0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCreivP7IyzogVGlhbnJhbiBaaG91IDx6aG91dGlh
bnJhbkBodWF3ZWkuY29tPg0Kt6LLzcqxvOQ6IDIwMTfE6jLUwjEzyNUgMzo0OQ0KytW8/sjLOiBJ
UEZJWEBpZXRmLm9yZw0Ks63LzTogZHJhZnQtbGktb3BzYXdnLWlwZml4LWJncC1jb21tdW5pdHku
YXV0aG9yc0BpZXRmLm9yZw0K1vfM4jogRlc6IFdHIGFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0LWxp
LW9wc2F3Zy1pcGZpeC1iZ3AtY29tbXVuaXR5LTAyDQoNCkRlYXIgSVBGSVgsDQoNClNpbmNlIHRo
ZSBJUEZJWCBXRyBpcyBjb25jbHVkZWQsIHRoaXMgSUUgZXh0ZW5zaW9uIGRyYWZ0IGlzIHByb2Nl
c3NlZCBub3cgaW4gT1BTQVdHLg0KVGhhbmtzIHZlcnkgbXVjaCBmb3IgdGhlIHByZXZpb3VzIGNv
bW1lbnRzIGFuZCBkaXNjdXNzaW9ucyBvbiB0aGlzIGRyYWZ0IGluIHRoaXMgbWFpbGluZyBsaXN0
Lg0KTm93IHRoZSBPUFNBV0cgaXMgcG9sbGluZyBmb3IgYWRvcHRpb24gb2YgdGhpcyBJLUQuIEkg
c2luY2VyZWx5IGFwcHJlY2lhdGUgeW91ciBvcGluaW9uIGFuZCByZXZpZXcuDQoNCkJlc3QgUmVn
YXJkcywNClRpYW5yYW4gWmhvdQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTog
T1BTQVdHIFttYWlsdG86b3BzYXdnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBUaWFu
cmFuIFpob3UNClNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMTMsIDIwMTcgMTE6MzcgQU0NClRvOiBv
cHNhd2dAaWV0Zi5vcmcNCkNjOiBvcHNhd2ctY2hhaXJzQGlldGYub3JnDQpTdWJqZWN0OiBbT1BT
QVdHXSBXRyBhZG9wdGlvbiBwb2xsIGZvciBkcmFmdC1saS1vcHNhd2ctaXBmaXgtYmdwLWNvbW11
bml0eS0wMg0KDQpEZWFyIE9QU0FXRywNCg0KSW4gU2VvdWwsIHdlIGdvdCBlbm91Z2ggaW50ZXJl
c3QgYW5kIHBvc2l0aXZlIHJlc3BvbnNlIG9uIHRoaXMgSVBGSVggSUUgZXh0ZW5zaW9uIGRyYWZ0
Lg0KQnkgdGhlIGF1dGhvcnMnIHJlcXVlc3QsIHRoaXMgZW1haWwgc3RhcnRzIGEgZm9ybWFsIHBv
bGwuIFRoZSBjaGFpcnMgd291bGQgbGlrZSB0byBrbm93IGlmIHRoZSBXRyBwYXJ0aWNpcGFudHMg
YWdyZWUgdGhhdCB0aGUgZm9sbG93aW5nIGRvY3VtZW50IHNob3VsZCBiZSBhZG9wdGVkIGFzIGEg
V0cgZG9jdW1lbnQgaW4gT1BTQVdHLg0KDQpFeHBvcnQgQkdQIGNvbW11bml0eSBpbmZvcm1hdGlv
biBpbiBJUCBGbG93IEluZm9ybWF0aW9uIEV4cG9ydCAoSVBGSVgpDQpodHRwczovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtbGktb3BzYXdnLWlwZml4LWJncC1jb21tdW5pdHktMDINCg0KVGhl
IGFkb3B0aW9uIHBvbGwgd2lsbCB0YWtlIHR3byB3ZWVrcy4gUGxlYXNlIGxldCB1cyBrbm93IHlv
dXIgb3BpbmlvbiBieSBGZWIgMjcuIEl0IHdvdWxkIGFsc28gYmUgZ29vZCB0byBoZWFyIHdobyBp
cyB3aWxsaW5nIHRvIHJldmlldyBhbmQvb3IgaW1wbGVtZW50IG9yIGRlcGxveSB0aGUgZXh0ZW5z
aW9uIGRlc2NyaWJlZCBpbiB0aGUgZG9jdW1lbnQuDQoNClNpbmNlIHdlIGFscmVhZHkgZm91bmQg
dGhhdCB0aGUgbWFqb3JpdHkgb2YgdGhlIGYyZiBwYXJ0aWNpcGFudHMgYXQgb3VyIElFVEY5NyBz
ZXNzaW9uIGxpa2UgdGhpcyBpZGVhLCBwbGVhc2UgZG8gc3BlYWsgdXAgbm93IGlmIHlvdSBkbyBu
b3QgYWdyZWUgb3IgaGF2ZSBzZXJpb3VzIG9iamVjdGlvbnMgKHdpdGggZXhwbGFuYXRpb24gb2Yg
Y291cnNlKS4NCg0KUmVnYXJkcywNClRpYW5yYW4NCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCk9QU0FXRyBtYWlsaW5nIGxpc3QNCk9QU0FXR0BpZXRm
Lm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHNhd2cNCg==

--_000_HKNPR02MB1843C24EA99FEEE8D95015AF8B590HKNPR02MB1843apcp_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><span style=3D"font-family: Calibri, Arial, Helvetica, sans-serif, 'Appl=
e Color Emoji', 'Segoe UI Emoji', NotoColorEmoji, 'Segoe UI Symbol', 'Andro=
id Emoji', EmojiSymbols; font-size: 16px;">Hi, dear all. As a co-author, I =
support the adoption of this draft
 as a work group document. Here&nbsp;</span><span style=3D"font-family: Cal=
ibri, Arial, Helvetica, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', =
NotoColorEmoji, 'Segoe UI Symbol', 'Android Emoji', EmojiSymbols; font-size=
: 16px;">three information elements including
 bgpCommunity, bgpSourceCommunityList and bgpDestinationCommunityList are i=
ntroduced&nbsp;in order to carry BGP community information. We do think it'=
s a necessary and useful&nbsp;extension.</span><br>
</p>
<p><span style=3D"font-family: Calibri, Arial, Helvetica, sans-serif, 'Appl=
e Color Emoji', 'Segoe UI Emoji', NotoColorEmoji, 'Segoe UI Symbol', 'Andro=
id Emoji', EmojiSymbols; font-size: 16px;"><br>
</span></p>
Best regards.</div>
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
Gu Rong</div>
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
gurong_cmcc@outlook.com</div>
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
gurong@chinamobile.com<br>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>=B7=A2=BC=FE=C8=CB:</b> Tianr=
an Zhou &lt;zhoutianran@huawei.com&gt;<br>
<b>=B7=A2=CB=CD=CA=B1=BC=E4:</b> 2017=C4=EA2=D4=C213=C8=D5 3:49<br>
<b>=CA=D5=BC=FE=C8=CB:</b> IPFIX@ietf.org<br>
<b>=B3=AD=CB=CD:</b> draft-li-opsawg-ipfix-bgp-community.authors@ietf.org<b=
r>
<b>=D6=F7=CC=E2:</b> FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-com=
munity-02</font>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Dear IPFIX,<br>
<br>
Since the IPFIX WG is concluded, this IE extension draft is processed now i=
n OPSAWG.<br>
Thanks very much for the previous comments and discussions on this draft in=
 this mailing list.<br>
Now the OPSAWG is polling for adoption of this I-D. I sincerely appreciate =
your opinion and review.<br>
<br>
Best Regards,<br>
Tianran Zhou<br>
<br>
-----Original Message-----<br>
From: OPSAWG [<a href=3D"mailto:opsawg-bounces@ietf.org">mailto:opsawg-boun=
ces@ietf.org</a>] On Behalf Of Tianran Zhou<br>
Sent: Monday, February 13, 2017 11:37 AM<br>
To: opsawg@ietf.org<br>
Cc: opsawg-chairs@ietf.org<br>
Subject: [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-=
02<br>
<br>
Dear OPSAWG,<br>
<br>
In Seoul, we got enough interest and positive response on this IPFIX IE ext=
ension draft.<br>
By the authors' request, this email starts a formal poll. The chairs would =
like to know if the WG participants agree that the following document shoul=
d be adopted as a WG document in OPSAWG.<br>
<br>
Export BGP community information in IP Flow Information Export (IPFIX)<br>
<a href=3D"https://tools.ietf.org/html/draft-li-opsawg-ipfix-bgp-community-=
02">https://tools.ietf.org/html/draft-li-opsawg-ipfix-bgp-community-02</a><=
br>
<br>
The adoption poll will take two weeks. Please let us know your opinion by F=
eb 27. It would also be good to hear who is willing to review and/or implem=
ent or deploy the extension described in the document.<br>
<br>
Since we already found that the majority of the f2f participants at our IET=
F97 session like this idea, please do speak up now if you do not agree or h=
ave serious objections (with explanation of course).<br>
<br>
Regards,<br>
Tianran<br>
<br>
_______________________________________________<br>
OPSAWG mailing list<br>
OPSAWG@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg">https://www.ietf.o=
rg/mailman/listinfo/opsawg</a><br>
</div>
</span></font></div>
</div>
</div>
</body>
</html>

--_000_HKNPR02MB1843C24EA99FEEE8D95015AF8B590HKNPR02MB1843apcp_--


From nobody Mon Feb 13 04:40:10 2017
Return-Path: <paitken@Brocade.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E491112963E; Mon, 13 Feb 2017 04:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7cDeY5OWn7ej; Mon, 13 Feb 2017 04:40:07 -0800 (PST)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [IPv6:2620:100:9001:7a::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 B3F49129621; Mon, 13 Feb 2017 04:40:07 -0800 (PST)
Received: from pps.filterd (m0000542.ppops.net [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1DCYdcT023331; Mon, 13 Feb 2017 04:39:56 -0800
Received: from brmwp-exmb12.corp.brocade.com ([208.47.132.227]) by mx0a-000f0801.pphosted.com with ESMTP id 28j2w25tbc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 13 Feb 2017 04:39:56 -0800
Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by BRMWP-EXMB12.corp.brocade.com (172.16.59.130) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 05:39:51 -0700
Received: from [172.27.212.154] (172.27.212.154) by EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 13:39:48 +0100
To: Tianran Zhou <zhoutianran@huawei.com>, "IPFIX@ietf.org" <IPFIX@ietf.org>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-MBX.china.huawei.com>
From: PJ Aitken <pjaitken@brocade.com>
Message-ID: <f2921126-418f-de35-cbec-be1605be4663@brocade.com>
Date: Mon, 13 Feb 2017 12:39:44 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.27.212.154]
X-ClientProxiedBy: hq1wp-excas14.corp.brocade.com (10.70.38.103) To EMEAWP-EXMB11.corp.brocade.com (172.29.11.85)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-13_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702130124
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/FTjl71zSH5J1NzacOzp5AdIdeBI>
Cc: "draft-li-opsawg-ipfix-bgp-community.authors@ietf.org" <draft-li-opsawg-ipfix-bgp-community.authors@ietf.org>
Subject: Re: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 12:40:09 -0000

Per section 6 of RFC7012, new IPFIX Information Elements can be added by 
direct application to IANA; there's no need for a draft or RFC.

However, the introduction and examples may be valuable, especially for 
BGP experts who are less familiar with IPFIX.

I've no objection to adopting the draft.

P.


On 13/02/17 03:49, Tianran Zhou wrote:
> Dear IPFIX,
>
> Since the IPFIX WG is concluded, this IE extension draft is processed now in OPSAWG.
> Thanks very much for the previous comments and discussions on this draft in this mailing list.
> Now the OPSAWG is polling for adoption of this I-D. I sincerely appreciate your opinion and review.
>
> Best Regards,
> Tianran Zhou
>
> -----Original Message-----
> From: OPSAWG [mailto:opsawg-bounces@ietf.org] On Behalf Of Tianran Zhou
> Sent: Monday, February 13, 2017 11:37 AM
> To: opsawg@ietf.org
> Cc: opsawg-chairs@ietf.org
> Subject: [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
>
> Dear OPSAWG,
>
> In Seoul, we got enough interest and positive response on this IPFIX IE extension draft.
> By the authors' request, this email starts a formal poll. The chairs would like to know if the WG participants agree that the following document should be adopted as a WG document in OPSAWG.
>
> Export BGP community information in IP Flow Information Export (IPFIX)
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dli-2Dopsawg-2Dipfix-2Dbgp-2Dcommunity-2D02&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=e8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&s=xYsTrrFuD2dlfxdp0X3pcPMw4vuozglfpGLv4A5TKNw&e=
>
> The adoption poll will take two weeks. Please let us know your opinion by Feb 27. It would also be good to hear who is willing to review and/or implement or deploy the extension described in the document.
>
> Since we already found that the majority of the f2f participants at our IETF97 session like this idea, please do speak up now if you do not agree or have serious objections (with explanation of course).
>
> Regards,
> Tianran
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_opsawg&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=e8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&s=lUyPAeQ2BUnIuqL4qUS1w45CNe3JixjYQzYQVN4Y3q4&e=
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipfix&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=Xx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&m=e8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&s=lOUrCUQVhsdnIWvSTJycjdy-0V6yZZ9NvjU2N-wZn18&e=


From nobody Mon Feb 13 23:33:24 2017
Return-Path: <lizhenqiang@chinamobile.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954E31294F7; Mon, 13 Feb 2017 23:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JWvt9PMzL7yd; Mon, 13 Feb 2017 23:33:18 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7FB12947A; Mon, 13 Feb 2017 23:33:16 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.1]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec58a2b2b1257-8a6c5; Tue, 14 Feb 2017 15:33:05 +0800 (CST)
X-RM-TRANSID: 2eec58a2b2b1257-8a6c5
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[223.72.55.152]) by rmsmtp-syy-appsvr01-12001 (RichMail) with SMTP id 2ee158a2b2afdeb-59c94; Tue, 14 Feb 2017 15:33:05 +0800 (CST)
X-RM-TRANSID: 2ee158a2b2afdeb-59c94
Date: Tue, 14 Feb 2017 15:34:38 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: "PJ Aitken" <pjaitken@brocade.com>, Zhoutianran <zhoutianran@huawei.com>,  "ipfix@ietf.org" <IPFIX@ietf.org>, opsawg <opsawg@ietf.org>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B2B@NKGEML515-MBX.china.huawei.com>,  <f2921126-418f-de35-cbec-be1605be4663@brocade.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <201702141534369518773@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart832001274031_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/5owlwMQI1Or7Gi02nNeJK0Iu1M8>
Cc: "draft-li-opsawg-ipfix-bgp-community.authors@ietf.org" <draft-li-opsawg-ipfix-bgp-community.authors@ietf.org>
Subject: Re: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 07:33:20 -0000

This is a multi-part message in MIME format.

------=_001_NextPart832001274031_=----
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: base64

SSBzdXBwb3J0IHRoZSBhZG9wdGlvbiBvZiB0aGlzIGRyYWZ0IGFzIGEgY28tYXV0aG9yLiBUaGUg
cmVxdWlyZW1lbnQgY29tZXMgZnJvbSB0aGUgZmllbGQgbmV0d29yay4NCg0KQmVzdCBSZWdhcmRz
DQoNCg0KbGl6aGVucWlhbmdAY2hpbmFtb2JpbGUuY29tDQogDQpGcm9tOiBQSiBBaXRrZW4NCkRh
dGU6IDIwMTctMDItMTMgMjA6MzkNClRvOiBUaWFucmFuIFpob3U7IElQRklYQGlldGYub3JnDQpD
QzogZHJhZnQtbGktb3BzYXdnLWlwZml4LWJncC1jb21tdW5pdHkuYXV0aG9yc0BpZXRmLm9yZw0K
U3ViamVjdDogUmU6IFtJUEZJWF0gRlc6IFdHIGFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0LWxpLW9w
c2F3Zy1pcGZpeC1iZ3AtY29tbXVuaXR5LTAyDQpQZXIgc2VjdGlvbiA2IG9mIFJGQzcwMTIsIG5l
dyBJUEZJWCBJbmZvcm1hdGlvbiBFbGVtZW50cyBjYW4gYmUgYWRkZWQgYnkgDQpkaXJlY3QgYXBw
bGljYXRpb24gdG8gSUFOQTsgdGhlcmUncyBubyBuZWVkIGZvciBhIGRyYWZ0IG9yIFJGQy4NCiAN
Ckhvd2V2ZXIsIHRoZSBpbnRyb2R1Y3Rpb24gYW5kIGV4YW1wbGVzIG1heSBiZSB2YWx1YWJsZSwg
ZXNwZWNpYWxseSBmb3IgDQpCR1AgZXhwZXJ0cyB3aG8gYXJlIGxlc3MgZmFtaWxpYXIgd2l0aCBJ
UEZJWC4NCiANCkkndmUgbm8gb2JqZWN0aW9uIHRvIGFkb3B0aW5nIHRoZSBkcmFmdC4NCiANClAu
DQogDQogDQpPbiAxMy8wMi8xNyAwMzo0OSwgVGlhbnJhbiBaaG91IHdyb3RlOg0KPiBEZWFyIElQ
RklYLA0KPg0KPiBTaW5jZSB0aGUgSVBGSVggV0cgaXMgY29uY2x1ZGVkLCB0aGlzIElFIGV4dGVu
c2lvbiBkcmFmdCBpcyBwcm9jZXNzZWQgbm93IGluIE9QU0FXRy4NCj4gVGhhbmtzIHZlcnkgbXVj
aCBmb3IgdGhlIHByZXZpb3VzIGNvbW1lbnRzIGFuZCBkaXNjdXNzaW9ucyBvbiB0aGlzIGRyYWZ0
IGluIHRoaXMgbWFpbGluZyBsaXN0Lg0KPiBOb3cgdGhlIE9QU0FXRyBpcyBwb2xsaW5nIGZvciBh
ZG9wdGlvbiBvZiB0aGlzIEktRC4gSSBzaW5jZXJlbHkgYXBwcmVjaWF0ZSB5b3VyIG9waW5pb24g
YW5kIHJldmlldy4NCj4NCj4gQmVzdCBSZWdhcmRzLA0KPiBUaWFucmFuIFpob3UNCj4NCj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogT1BTQVdHIFttYWlsdG86b3BzYXdnLWJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBUaWFucmFuIFpob3UNCj4gU2VudDogTW9uZGF5
LCBGZWJydWFyeSAxMywgMjAxNyAxMTozNyBBTQ0KPiBUbzogb3BzYXdnQGlldGYub3JnDQo+IENj
OiBvcHNhd2ctY2hhaXJzQGlldGYub3JnDQo+IFN1YmplY3Q6IFtPUFNBV0ddIFdHIGFkb3B0aW9u
IHBvbGwgZm9yIGRyYWZ0LWxpLW9wc2F3Zy1pcGZpeC1iZ3AtY29tbXVuaXR5LTAyDQo+DQo+IERl
YXIgT1BTQVdHLA0KPg0KPiBJbiBTZW91bCwgd2UgZ290IGVub3VnaCBpbnRlcmVzdCBhbmQgcG9z
aXRpdmUgcmVzcG9uc2Ugb24gdGhpcyBJUEZJWCBJRSBleHRlbnNpb24gZHJhZnQuDQo+IEJ5IHRo
ZSBhdXRob3JzJyByZXF1ZXN0LCB0aGlzIGVtYWlsIHN0YXJ0cyBhIGZvcm1hbCBwb2xsLiBUaGUg
Y2hhaXJzIHdvdWxkIGxpa2UgdG8ga25vdyBpZiB0aGUgV0cgcGFydGljaXBhbnRzIGFncmVlIHRo
YXQgdGhlIGZvbGxvd2luZyBkb2N1bWVudCBzaG91bGQgYmUgYWRvcHRlZCBhcyBhIFdHIGRvY3Vt
ZW50IGluIE9QU0FXRy4NCj4NCj4gRXhwb3J0IEJHUCBjb21tdW5pdHkgaW5mb3JtYXRpb24gaW4g
SVAgRmxvdyBJbmZvcm1hdGlvbiBFeHBvcnQgKElQRklYKQ0KPiBodHRwczovL3VybGRlZmVuc2Uu
cHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3Rvb2xzLmlldGYub3JnX2h0bWxfZHJh
ZnQtMkRsaS0yRG9wc2F3Zy0yRGlwZml4LTJEYmdwLTJEY29tbXVuaXR5LTJEMDImZD1Ed0lDQWcm
Yz1JTF9YcVFXT2p1YmdmcUlOaTJqVHpnJnI9WHg5NzI5eFlEWW9DZ0JEZGNwMUZLdDVQeVlkMVRD
b1hOS2h5UFk4Q0ZwOCZtPWU4VV9nUHdDX0gySTV5SzdYTW03SVoyOVBVMXJnMHdOYlBzSnZERzZS
REkmcz14WXNUcnJGdUQyZGxmeGRwMFgzcGNQTXc0dnVvemdsZnBHTHY0QTVUS053JmU9DQo+DQo+
IFRoZSBhZG9wdGlvbiBwb2xsIHdpbGwgdGFrZSB0d28gd2Vla3MuIFBsZWFzZSBsZXQgdXMga25v
dyB5b3VyIG9waW5pb24gYnkgRmViIDI3LiBJdCB3b3VsZCBhbHNvIGJlIGdvb2QgdG8gaGVhciB3
aG8gaXMgd2lsbGluZyB0byByZXZpZXcgYW5kL29yIGltcGxlbWVudCBvciBkZXBsb3kgdGhlIGV4
dGVuc2lvbiBkZXNjcmliZWQgaW4gdGhlIGRvY3VtZW50Lg0KPg0KPiBTaW5jZSB3ZSBhbHJlYWR5
IGZvdW5kIHRoYXQgdGhlIG1ham9yaXR5IG9mIHRoZSBmMmYgcGFydGljaXBhbnRzIGF0IG91ciBJ
RVRGOTcgc2Vzc2lvbiBsaWtlIHRoaXMgaWRlYSwgcGxlYXNlIGRvIHNwZWFrIHVwIG5vdyBpZiB5
b3UgZG8gbm90IGFncmVlIG9yIGhhdmUgc2VyaW91cyBvYmplY3Rpb25zICh3aXRoIGV4cGxhbmF0
aW9uIG9mIGNvdXJzZSkuDQo+DQo+IFJlZ2FyZHMsDQo+IFRpYW5yYW4NCj4NCj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gT1BTQVdHIG1haWxpbmcg
bGlzdA0KPiBPUFNBV0dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQu
Y29tL3YyL3VybD91PWh0dHBzLTNBX193d3cuaWV0Zi5vcmdfbWFpbG1hbl9saXN0aW5mb19vcHNh
d2cmZD1Ed0lDQWcmYz1JTF9YcVFXT2p1YmdmcUlOaTJqVHpnJnI9WHg5NzI5eFlEWW9DZ0JEZGNw
MUZLdDVQeVlkMVRDb1hOS2h5UFk4Q0ZwOCZtPWU4VV9nUHdDX0gySTV5SzdYTW03SVoyOVBVMXJn
MHdOYlBzSnZERzZSREkmcz1sVXlQQWVRMkJVbkl1cUw0cVVTMXc0NUNOZTNKaXhqWVF6WVFWTjRZ
M3E0JmU9DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+IElQRklYIG1haWxpbmcgbGlzdA0KPiBJUEZJWEBpZXRmLm9yZw0KPiBodHRwczovL3Vy
bGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3d3dy5pZXRmLm9yZ19t
YWlsbWFuX2xpc3RpbmZvX2lwZml4JmQ9RHdJQ0FnJmM9SUxfWHFRV09qdWJnZnFJTmkyalR6ZyZy
PVh4OTcyOXhZRFlvQ2dCRGRjcDFGS3Q1UHlZZDFUQ29YTktoeVBZOENGcDgmbT1lOFVfZ1B3Q19I
Mkk1eUs3WE1tN0laMjlQVTFyZzB3TmJQc0p2REc2UkRJJnM9bE9VckNVUVZoc2RuSVd2U1RKeWNq
ZHktMFY2eVpaOU52alUyTi13Wm4xOCZlPQ0KIA0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCklQRklYIG1haWxpbmcgbGlzdA0KSVBGSVhAaWV0Zi5vcmcN
Cmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXBmaXgNCiANCiANCg==

------=_001_NextPart832001274031_=----
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DISO-8859-1"><style>body { line-height: 1.5; }blockquote { margin-top: =
0px; margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; fo=
nt-family: ????; color: rgb(0, 0, 0); line-height: 1.5; }</style></head><b=
ody>=0A<div><span></span>I support the adoption of this draft as a co-auth=
or. The requirement comes from the field network.</div>=0A<div><br></div><=
div>Best Regards</div><hr style=3D"width: 210px; height: 1px;" color=3D"#b=
5c4df" size=3D"1" align=3D"left">=0A<div><span><div style=3D"MARGIN: 10px;=
 FONT-FAMILY: verdana; FONT-SIZE: 10pt"><div>lizhenqiang@chinamobile.com</=
div></div></span></div>=0A<blockquote style=3D"margin-top: 0px; margin-bot=
tom: 0px; margin-left: 0.5em;"><div>&nbsp;</div><div style=3D"border:none;=
border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><div style=3D"PA=
DDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-FAMILY:tahoma;CO=
LOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px"><=
div><b>From:</b>&nbsp;<a href=3D"mailto:pjaitken@brocade.com">PJ Aitken</a=
></div><div><b>Date:</b>&nbsp;2017-02-13&nbsp;20:39</div><div><b>To:</b>&n=
bsp;<a href=3D"mailto:zhoutianran@huawei.com">Tianran Zhou</a>; <a href=3D=
"mailto:IPFIX@ietf.org">IPFIX@ietf.org</a></div><div><b>CC:</b>&nbsp;<a hr=
ef=3D"mailto:draft-li-opsawg-ipfix-bgp-community.authors@ietf.org">draft-l=
i-opsawg-ipfix-bgp-community.authors@ietf.org</a></div><div><b>Subject:</b=
>&nbsp;Re: [IPFIX] FW: WG adoption poll for draft-li-opsawg-ipfix-bgp-comm=
unity-02</div></div></div><div><div>Per section 6 of RFC7012, new IPFIX In=
formation Elements can be added by </div>=0A<div>direct application to IAN=
A; there's no need for a draft or RFC.</div>=0A<div>&nbsp;</div>=0A<div>Ho=
wever, the introduction and examples may be valuable, especially for </div=
>=0A<div>BGP experts who are less familiar with IPFIX.</div>=0A<div>&nbsp;=
</div>=0A<div>I've no objection to adopting the draft.</div>=0A<div>&nbsp;=
</div>=0A<div>P.</div>=0A<div>&nbsp;</div>=0A<div>&nbsp;</div>=0A<div>On 1=
3/02/17 03:49, Tianran Zhou wrote:</div>=0A<div>&gt; Dear IPFIX,</div>=0A<=
div>&gt;</div>=0A<div>&gt; Since the IPFIX WG is concluded, this IE extens=
ion draft is processed now in OPSAWG.</div>=0A<div>&gt; Thanks very much f=
or the previous comments and discussions on this draft in this mailing lis=
t.</div>=0A<div>&gt; Now the OPSAWG is polling for adoption of this I-D. I=
 sincerely appreciate your opinion and review.</div>=0A<div>&gt;</div>=0A<=
div>&gt; Best Regards,</div>=0A<div>&gt; Tianran Zhou</div>=0A<div>&gt;</d=
iv>=0A<div>&gt; -----Original Message-----</div>=0A<div>&gt; From: OPSAWG =
[mailto:opsawg-bounces@ietf.org] On Behalf Of Tianran Zhou</div>=0A<div>&g=
t; Sent: Monday, February 13, 2017 11:37 AM</div>=0A<div>&gt; To: opsawg@i=
etf.org</div>=0A<div>&gt; Cc: opsawg-chairs@ietf.org</div>=0A<div>&gt; Sub=
ject: [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02=
</div>=0A<div>&gt;</div>=0A<div>&gt; Dear OPSAWG,</div>=0A<div>&gt;</div>=
=0A<div>&gt; In Seoul, we got enough interest and positive response on thi=
s IPFIX IE extension draft.</div>=0A<div>&gt; By the authors' request, thi=
s email starts a formal poll. The chairs would like to know if the WG part=
icipants agree that the following document should be adopted as a WG docum=
ent in OPSAWG.</div>=0A<div>&gt;</div>=0A<div>&gt; Export BGP community in=
formation in IP Flow Information Export (IPFIX)</div>=0A<div>&gt; https://=
urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2=
Dli-2Dopsawg-2Dipfix-2Dbgp-2Dcommunity-2D02&amp;d=3DDwICAg&amp;c=3DIL_XqQW=
OjubgfqINi2jTzg&amp;r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&amp;m=
=3De8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&amp;s=3DxYsTrrFuD2dlfxdp0X3=
pcPMw4vuozglfpGLv4A5TKNw&amp;e=3D</div>=0A<div>&gt;</div>=0A<div>&gt; The =
adoption poll will take two weeks. Please let us know your opinion by Feb =
27. It would also be good to hear who is willing to review and/or implemen=
t or deploy the extension described in the document.</div>=0A<div>&gt;</di=
v>=0A<div>&gt; Since we already found that the majority of the f2f partici=
pants at our IETF97 session like this idea, please do speak up now if you =
do not agree or have serious objections (with explanation of course).</div=
>=0A<div>&gt;</div>=0A<div>&gt; Regards,</div>=0A<div>&gt; Tianran</div>=
=0A<div>&gt;</div>=0A<div>&gt; ___________________________________________=
____</div>=0A<div>&gt; OPSAWG mailing list</div>=0A<div>&gt; OPSAWG@ietf.o=
rg</div>=0A<div>&gt; https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=
__www.ietf.org_mailman_listinfo_opsawg&amp;d=3DDwICAg&amp;c=3DIL_XqQWOjubg=
fqINi2jTzg&amp;r=3DXx9729xYDYoCgBDdcp1FKt5PyYd1TCoXNKhyPY8CFp8&amp;m=3De8U=
_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&amp;s=3DlUyPAeQ2BUnIuqL4qUS1w45CN=
e3JixjYQzYQVN4Y3q4&amp;e=3D</div>=0A<div>&gt;</div>=0A<div>&gt; __________=
_____________________________________</div>=0A<div>&gt; IPFIX mailing list=
</div>=0A<div>&gt; IPFIX@ietf.org</div>=0A<div>&gt; https://urldefense.pro=
ofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman_listinfo_ipfix&amp;d=
=3DDwICAg&amp;c=3DIL_XqQWOjubgfqINi2jTzg&amp;r=3DXx9729xYDYoCgBDdcp1FKt5Py=
Yd1TCoXNKhyPY8CFp8&amp;m=3De8U_gPwC_H2I5yK7XMm7IZ29PU1rg0wNbPsJvDG6RDI&amp=
;s=3DlOUrCUQVhsdnIWvSTJycjdy-0V6yZZ9NvjU2N-wZn18&amp;e=3D</div>=0A<div>&nb=
sp;</div>=0A<div>_______________________________________________</div>=0A<=
div>IPFIX mailing list</div>=0A<div>IPFIX@ietf.org</div>=0A<div>https://ww=
w.ietf.org/mailman/listinfo/ipfix</div>=0A<div>&nbsp;</div>=0A<div>&nbsp;<=
/div>=0A</div></blockquote>=0A</body></html>
------=_001_NextPart832001274031_=------




From nobody Wed Feb 15 19:15:29 2017
Return-Path: <lizhenqiang@chinamobile.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C191295FA; Wed, 15 Feb 2017 19:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YX_xJMl8J09; Wed, 15 Feb 2017 19:15:20 -0800 (PST)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id A69BF12996D; Wed, 15 Feb 2017 19:15:18 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.13]) by rmmx-syy-dmz-app06-12006 (RichMail) with SMTP id 2ee658a51943162-b55dc; Thu, 16 Feb 2017 11:15:15 +0800 (CST)
X-RM-TRANSID: 2ee658a51943162-b55dc
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[223.72.55.167]) by rmsmtp-syy-appsvr07-12007 (RichMail) with SMTP id 2ee758a51941e50-9ee2e; Thu, 16 Feb 2017 11:15:15 +0800 (CST)
X-RM-TRANSID: 2ee758a51941e50-9ee2e
Date: Thu, 16 Feb 2017 11:15:17 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: grow-bounces <grow-bounces@ietf.org>, zhoutianran <zhoutianran@huawei.com>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B05@NKGEML515-MBX.china.huawei.com>,  <7023a95c-c6a9-4d6a-b009-8f35e447aa4e@gmail.com>,  <76CD132C3ADEF848BD84D028D243C9279357F4EA@NKGEML515-MBX.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <2017021611151726192539@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart588125845745_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/OThRDe866lgvEbWryVsXwWOhVM8>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 03:15:23 -0000

This is a multi-part message in MIME format.

------=_001_NextPart588125845745_=----
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: base64

RGVhciBJZ25hcywNCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgeW91ciBzdXBwb3J0IGFuZCBz
dWdnZXN0aW9uLg0KDQpTaW5jZSB0aGUgcHJvYmxlbSB0byBiZSBzb2x2ZWQgaW4gdGhpcyBkcmFm
dCBjb21lcyBmcm9tIHRoZSBmaWVsZCBuZXR3b3JrLCB3ZSBvbmx5IHByb3ZpZGUgdGhlIG1ldGhv
ZCB0byBjYXJyeSBzdGFuZGFyZCBCR1AgY29tbW11bml0aWVzIGluIElQRklYLiBFeHRlbmRlZCBj
b21tdW5pdGllcyBhcmUgdXN1c2xseSB1c2VkIGZvciBvdGhlciBwdXJwb3NlcyB0aGFuIHN0YW5k
YXJkIGNvbW11bml0aWVzLCBzdWNoIGFzIHJvdXRlIHRhcmdldCwgYWN0aW9ucyBmb3IgQkdQIGZs
b3dzcGVjIGV0Yy4gV2hldGhlciBvciBub3Qgd2UgcmVhbGx5IG5lZWQgdG8gY292ZXIgZW50ZW5k
ZWQgY29tbXVuaXRpZXMsIEkgd2FudCB0byBzZWUgbW9yZSBjb21tZW50cy4gTGFyZ2UgY29tbXVu
aXRpZXMgYXJlIHJlbGF2aXRlbHkgbmV3LiBSRkM4MDkyIHdhcyBwdWJsaXNoZWQgcmVjZW50bGx5
LiAgQW55d2F5LCBob3dldmVyLCBpdCBpcyBlYXN5IGZvciB1cyB0byBjb3ZlciBib3RoIGV4dGVu
ZGVkIGNvbW11bml0aWVzIFtSRkM0MzYwXSBhbmQgbGFyZ2UgY29tbXVuaXRpZXMgW1JGQzgwOTJd
IGFmdGVyIHRoZSBhZG9wdGlvbiBhbmQgZnVydGhlciBjb21tZW50IGNvbnNlbnN1cy4gVGV4dCBj
b250cmlidXRpb24gaXMgd2VsY29tZS4gQnkgdGhlIHdheSwgSSB3YW50IHRvIGtub3cgdGhlIG9w
aW5pb25zIGFib3V0IHRoZSB3aWRlIGNvbW11bml0aWVzLiBEbyB3ZSBuZWVkIHRvIGNvdmVyIHRo
ZW0gdG9nZXRoZXI/DQoNCkFzIHlvdSBzYWlkLCB0aGlzIGRyYWZ0IHdhcyBhIGdvb2Qgc3RhcnQu
IEl0IGhhcyB2YWx1ZSB0byBiZSBhIHdvcmtpbmcgZ3JvdXAgaXRlbS4gV2UgY2FuIGNvbnRpbnVl
IHRoZSBjb21tZW50cyBhbmQgZGlzY3Vzc2lvbiBhZnRlciB0aGUgYWRvcHRpb24gYW5kIHdlIHdp
bGwgaW1wcm92ZSB0aGUgZG9jdW1lbnQgYWNjb3JkaW5nIHRvIHRoZSBjb25zZW5zdXMuIE9wZXJh
dGlvbmFsIGNvbnNpZGVyYXRpb25zIHdpbGwgYmUgY292ZXJlZCBpbiB0aGUgbmV4dCB2ZXJzaW9u
Lg0KDQpCZXN0IFJlZ2FyZHMsDQpaaGVucWlhbmcgTGkNCkNoaW5hIE1vYmlsZQ0KIA0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEdST1cgW21haWx0bzpncm93LWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBJZ25hcyBCYWdkb25hcw0KU2VudDogVHVlc2RheSwgRmVicnVh
cnkgMTQsIDIwMTcgOTo0NiBQTQ0KVG86IFRpYW5yYW4gWmhvdSA8emhvdXRpYW5yYW5AaHVhd2Vp
LmNvbT4NCkNjOiBvcHNhd2dAaWV0Zi5vcmc7IG9wc2F3Zy1jaGFpcnNAaWV0Zi5vcmc7IGdyb3dA
aWV0Zi5vcmcgZ3Jvd0BpZXRmLm9yZyA8Z3Jvd0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbR1JP
V10gW09QU0FXR10gV0cgYWRvcHRpb24gcG9sbCBmb3IgZHJhZnQtbGktb3BzYXdnLWlwZml4LWJn
cC1jb21tdW5pdHktMDINCiANCkhpIHRoZXJlLA0KIA0KW0NvcHlpbmcgR1JPVyBXRyBhcyB0aGlz
IG1pZ2h0IGJlIHJlbGV2YW50IHRvIHRoZWlyIGNvdmVyYWdlIGFyZWFzXQ0KIA0KVGhlIGRvY3Vt
ZW50IHNlZW1zIHRvIGJlIGEgZ29vZCBzdGFydCBidXQgY292ZXJzIG9ubHkgc3RhbmRhcmQgY29t
bXVuaXRpZXMuIFRoaXMgaXMgbm90IHN1ZmZpY2llbnQgZ2l2ZW4gdGhlIHVuaXZlcnNhbCBkZXBs
b3ltZW50IG9mIDQgb2N0ZXQgQVNOcy4gQm90aCBleHRlbmRlZCBjb21tdW5pdGllcyBbUkZDNDM2
MF0gYW5kIGxhcmdlIGNvbW11bml0aWVzIFtSRkM4MDkyXSBhcmUgbmVlZGVkIGFuZCBhcmUgdXNl
ZCB0byBhZGRyZXNzIHRoZSBzaWduYWxsaW5nIHJlcXVpcmVtZW50cyBmb3IgQVM0IEFTTnMuIEhh
dmluZyBzZXBhcmF0ZSBkb2N1bWVudHMgZWFjaCBhZGRyZXNzaW5nIG9ubHkgYSBzcGVjaWZpYyB0
eXBlIG9mIGNvbW11bml0eSBkb2VzIG5vdCBzZWVtIHByYWN0aWNhbCBhbmQgcmF0aW9uYWwuIFRo
ZSBkb2N1bWVudCBzaG91bGQgaW5jbHVkZSB0aGUgZGVmaW5pdGlvbnMgZm9yIElFcyBjb3Zlcmlu
ZyBleHRlbmRlZCBhbmQgbGFyZ2UgY29tbXVuaXRpZXMuDQogDQpXaGF0IGlzIHRoZSBsb2dpYyBv
ZiBzZWxlY3RpbmcgbXVsdGlwbGUgY29tbXVuaXRpZXMgZm9yIGV4cG9ydCB0aGF0IGEgcHJlZml4
IG1heSBoYXZlIGJlZW4gZGVjb3JhdGVkIHdpdGg/IElzIGl0IGFsbCBvZiB0aGVtIGFsbCB0aGUg
dGltZT8gVGhlIHVwcGVyIGxpbWl0IG1heSBiZSByZWFjaGluZyAxNjAwMCBzdGFuZGFyZCBjb21t
dW5pdGllcyBwZXIgcHJlZml4IC0gd291bGQgdGhhdCBmaXQgaW50byByZXN1bHRpbmcgSVBGSVgg
SUU/IElmIHRoZXJlIGlzIGEgbGltaXQsIGhvdyBkb2VzIGl0IHdvcms/IElzIHRoZXJlIGFueSBp
bnRlcnByZXRhdGlvbiBkb25lIG9uIHRoZSB2YWx1ZXMgb2YgdGhlIGNvbW11bml0aWVzIChhbGwg
dHlwZXMsIG5vdCBqdXN0IHN0YW5kYXJkIG9uZXMpPyBUaG9zZSBhbGwgYXJlIG9wZXJhdGlvbmFs
IGNvbnNpZGVyYXRpb25zIGFzcGVjdHMgYW5kIHNob3VsZCBiZSBjb3ZlcmVkIGluIHRoZSBkb2N1
bWVudCwgYXBwZW5kaXggQSBsaWtlbHkgY291bGQgYmUgYSBnb29kIHBsYWNlIGZvciBpdC4NCiAN
ClNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIG9uIHRoZSBwcml2YWN5IGFzcGVjdHMgd291bGQgdG8g
YmUgY292ZXJlZC4NCiANCklnbmFzDQogDQogDQogDQogDQpPbiAxMy8wMi8yMDE3IDAzOjM2LCBU
aWFucmFuIFpob3Ugd3JvdGU6DQo+IERlYXIgT1BTQVdHLA0KPg0KPiBJbiBTZW91bCwgd2UgZ290
IGVub3VnaCBpbnRlcmVzdCBhbmQgcG9zaXRpdmUgcmVzcG9uc2Ugb24gdGhpcyBJUEZJWCBJRSBl
eHRlbnNpb24gZHJhZnQuDQo+IEJ5IHRoZSBhdXRob3JzJyByZXF1ZXN0LCB0aGlzIGVtYWlsIHN0
YXJ0cyBhIGZvcm1hbCBwb2xsLiBUaGUgY2hhaXJzIHdvdWxkIGxpa2UgdG8ga25vdyBpZiB0aGUg
V0cgcGFydGljaXBhbnRzIGFncmVlIHRoYXQgdGhlIGZvbGxvd2luZyBkb2N1bWVudCBzaG91bGQg
YmUgYWRvcHRlZCBhcyBhIFdHIGRvY3VtZW50IGluIE9QU0FXRy4NCj4NCj4gRXhwb3J0IEJHUCBj
b21tdW5pdHkgaW5mb3JtYXRpb24gaW4gSVAgRmxvdyBJbmZvcm1hdGlvbiBFeHBvcnQgKElQRklY
KQ0KPiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbGktb3BzYXdnLWlwZml4LWJn
cC1jb21tdW5pdHktMDINCj4NCj4gVGhlIGFkb3B0aW9uIHBvbGwgd2lsbCB0YWtlIHR3byB3ZWVr
cy4gUGxlYXNlIGxldCB1cyBrbm93IHlvdXIgb3BpbmlvbiBieSBGZWIgMjcuIEl0IHdvdWxkIGFs
c28gYmUgZ29vZCB0byBoZWFyIHdobyBpcyB3aWxsaW5nIHRvIHJldmlldyBhbmQvb3IgaW1wbGVt
ZW50IG9yIGRlcGxveSB0aGUgZXh0ZW5zaW9uIGRlc2NyaWJlZCBpbiB0aGUgZG9jdW1lbnQuDQo+
DQo+IFNpbmNlIHdlIGFscmVhZHkgZm91bmQgdGhhdCB0aGUgbWFqb3JpdHkgb2YgdGhlIGYyZiBw
YXJ0aWNpcGFudHMgYXQgb3VyIElFVEY5NyBzZXNzaW9uIGxpa2UgdGhpcyBpZGVhLCBwbGVhc2Ug
ZG8gc3BlYWsgdXAgbm93IGlmIHlvdSBkbyBub3QgYWdyZWUgb3IgaGF2ZSBzZXJpb3VzIG9iamVj
dGlvbnMgKHdpdGggZXhwbGFuYXRpb24gb2YgY291cnNlKS4NCj4NCj4gUmVnYXJkcywNCj4gVGlh
bnJhbg0KPg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiBPUFNBV0cgbWFpbGluZyBsaXN0DQo+IE9QU0FXR0BpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29wc2F3Zw0KIA0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkdST1cgbWFpbGluZyBsaXN0DQpHUk9XQGll
dGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dyb3cNCg==

------=_001_NextPart588125845745_=----
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DGB2312"><style>body { line-height: 1.5; }blockquote { margin-top: 0px;=
 margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; font-f=
amily: =CE=A2=C8=ED=D1=C5=BA=DA; color: rgb(0, 0, 0); line-height: 1.5; }<=
/style></head><body>=0A<div><span></span>Dear Ignas,</div><div><br></div><=
div>Thank you very much for your support and suggestion.</div><div><br></d=
iv><div>Since the problem to be solved in this draft comes from the field =
network, we only provide the method to carry standard BGP commmunities in =
IPFIX. Extended communities are ususlly used for other purposes than stand=
ard communities, such as route target, actions for BGP flowspec etc. Wheth=
er or not we really need to cover entended communities, I want to see more=
 comments. Large communities are relavitely new. RFC8092 was published rec=
entlly. &nbsp;Anyway, however, it is easy for us to cover b<span style=3D"=
font-size: 10.5pt; line-height: 1.5; background-color: window;">oth extend=
ed communities [RFC4360] and large communities [RFC8092]</span><span style=
=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;">&nbsp;=
after the adoption and further comment consensus. Text contribution is wel=
come. By the way, I want to know the opinions about the wide communities. =
Do we need to cover them together?</span></div><div><span style=3D"font-si=
ze: 10.5pt; line-height: 1.5; background-color: window;"><br></span></div>=
<div><span style=3D"font-size: 10.5pt; line-height: 1.5; background-color:=
 window;">As you said, this draft was a good start. It has value to be a w=
orking group item. We can continue the comments and discussion after the a=
doption and we will improve the document according to the consensus. O</sp=
an><span style=3D"font-size: 10.5pt; line-height: 1.5; background-color: w=
indow;">perational considerations will be covered in the next version.</sp=
an></div><div><br></div><div>Best Regards,</div><div>Zhenqiang Li</div><di=
v>China Mobile</div><blockquote style=3D"margin-top: 0px; margin-bottom: 0=
px; margin-left: 0.5em;"><div>=0A<div>&nbsp;</div>=0A<div>-----Original Me=
ssage-----</div>=0A<div>From: GROW [mailto:grow-bounces@ietf.org] On Behal=
f Of Ignas Bagdonas</div>=0A<div>Sent: Tuesday, February 14, 2017 9:46 PM<=
/div>=0A<div>To: Tianran Zhou &lt;zhoutianran@huawei.com&gt;</div>=0A<div>=
Cc: opsawg@ietf.org; opsawg-chairs@ietf.org; grow@ietf.org grow@ietf.org &=
lt;grow@ietf.org&gt;</div>=0A<div>Subject: Re: [GROW] [OPSAWG] WG adoption=
 poll for draft-li-opsawg-ipfix-bgp-community-02</div>=0A<div>&nbsp;</div>=
=0A<div>Hi there,</div>=0A<div>&nbsp;</div>=0A<div>[Copying GROW WG as thi=
s might be relevant to their coverage areas]</div>=0A<div>&nbsp;</div>=0A<=
div>The document seems to be a good start but covers only standard communi=
ties. This is not sufficient given the universal deployment of 4 octet ASN=
s. Both extended communities [RFC4360] and large communities [RFC8092] are=
 needed and are used to address the signalling requirements for AS4 ASNs. =
Having separate documents each addressing only a specific type of communit=
y does not seem practical and rational. The document should include the de=
finitions for IEs covering extended and large communities.</div>=0A<div>&n=
bsp;</div>=0A<div>What is the logic of selecting multiple communities for =
export that a prefix may have been decorated with? Is it all of them all t=
he time? The upper limit may be reaching 16000 standard communities per pr=
efix - would that fit into resulting IPFIX IE? If there is a limit, how do=
es it work? Is there any interpretation done on the values of the communit=
ies (all types, not just standard ones)? Those all are operational conside=
rations aspects and should be covered in the document, appendix A likely c=
ould be a good place for it.</div>=0A<div>&nbsp;</div>=0A<div>Security con=
siderations on the privacy aspects would to be covered.</div>=0A<div>&nbsp=
;</div>=0A<div>Ignas</div>=0A<div>&nbsp;</div>=0A<div>&nbsp;</div>=0A<div>=
&nbsp;</div>=0A<div>&nbsp;</div>=0A<div>On 13/02/2017 03:36, Tianran Zhou =
wrote:</div>=0A<div>&gt; Dear OPSAWG,</div>=0A<div>&gt;</div>=0A<div>&gt; =
In Seoul, we got enough interest and positive response on this IPFIX IE ex=
tension draft.</div>=0A<div>&gt; By the authors' request, this email start=
s a formal poll. The chairs would like to know if the WG participants agre=
e that the following document should be adopted as a WG document in OPSAWG=
.</div>=0A<div>&gt;</div>=0A<div>&gt; Export BGP community information in =
IP Flow Information Export (IPFIX)</div>=0A<div>&gt; https://tools.ietf.or=
g/html/draft-li-opsawg-ipfix-bgp-community-02</div>=0A<div>&gt;</div>=0A<d=
iv>&gt; The adoption poll will take two weeks. Please let us know your opi=
nion by Feb 27. It would also be good to hear who is willing to review and=
/or implement or deploy the extension described in the document.</div>=0A<=
div>&gt;</div>=0A<div>&gt; Since we already found that the majority of the=
 f2f participants at our IETF97 session like this idea, please do speak up=
 now if you do not agree or have serious objections (with explanation of c=
ourse).</div>=0A<div>&gt;</div>=0A<div>&gt; Regards,</div>=0A<div>&gt; Tia=
nran</div>=0A<div>&gt;</div>=0A<div>&gt; _________________________________=
______________</div>=0A<div>&gt; OPSAWG mailing list</div>=0A<div>&gt; OPS=
AWG@ietf.org</div>=0A<div>&gt; https://www.ietf.org/mailman/listinfo/opsaw=
g</div>=0A<div>&nbsp;</div>=0A<div>_______________________________________=
________</div>=0A<div>GROW mailing list</div>=0A<div>GROW@ietf.org</div>=
=0A<div>https://www.ietf.org/mailman/listinfo/grow</div>=0A</div></blockqu=
ote>=0A</body></html>
------=_001_NextPart588125845745_=------




From nobody Thu Feb 16 03:15:51 2017
Return-Path: <paitken@Brocade.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 240BB129A1A; Thu, 16 Feb 2017 03:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlqA1x1Pr5qG; Thu, 16 Feb 2017 03:15:48 -0800 (PST)
Received: from mx0a-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::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 A7474129A18; Thu, 16 Feb 2017 03:15:46 -0800 (PST)
Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1GBBJWa015626; Thu, 16 Feb 2017 03:15:37 -0800
Received: from brmwp-exmb11.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 28m20cfuu4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 03:15:37 -0800
Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by BRMWP-EXMB11.corp.brocade.com (172.16.59.77) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 04:15:34 -0700
Received: from [172.27.212.154] (172.27.212.154) by EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 12:15:30 +0100
To: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>, grow-bounces <grow-bounces@ietf.org>, zhoutianran <zhoutianran@huawei.com>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B05@NKGEML515-MBX.china.huawei.com> <7023a95c-c6a9-4d6a-b009-8f35e447aa4e@gmail.com> <76CD132C3ADEF848BD84D028D243C9279357F4EA@NKGEML515-MBX.china.huawei.com> <2017021611151726192539@chinamobile.com>
From: PJ Aitken <pjaitken@brocade.com>
Message-ID: <9f060f89-a2a8-5f87-4d66-088cb389ac14@brocade.com>
Date: Thu, 16 Feb 2017 11:15:24 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2017021611151726192539@chinamobile.com>
Content-Type: multipart/alternative; boundary="------------AB5957A2F268C5981C80C3F2"
X-Originating-IP: [172.27.212.154]
X-ClientProxiedBy: hq1wp-excas11.corp.brocade.com (10.70.36.102) To EMEAWP-EXMB11.corp.brocade.com (172.29.11.85)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160110
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/v7Qu_7spMuYmTheZyXh6AHNVhxI>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 11:15:49 -0000

--------------AB5957A2F268C5981C80C3F2
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit

Ignas Bagdonas wrote:


 > The upper limit may be reaching 16000 standard communities per prefix 
- would that fit into resulting IPFIX IE? If there is a limit, how does 
it work?


A quick calculation suggests that the maximum would be 16376 x 4-octet 
ASNs. See the figure below.

The constraining factor is the RFC7011 IPFIX Message Header "Length" 
field, since this is only 16 bits.

Splitting a list across multiple IPFIX messagesis a question which the 
IPFIX community hasn't discussed.Unfortunately the basicList "Semantic" 
field only defines the relationship among the different values within a 
single message; the relationship among values in different messages is 
not defined.

IPFIX Collectors might reasonably assume that information in subsequent 
messages supersedes information in earlier messages, so splitting a list 
across multiple messages would not have the desired effect.


      0                   1                   2                   3      
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
|       Version Number          |        Length = 65532         |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
|                           Export Time                         |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
|                       Sequence Number                         |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
|                    Observation Domain ID                      |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
|          Set ID = 256         |         Length = 65516        |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
|      255      |      List Length = 65509      | semantic=allOf|     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     | 
      bSCL FieldId = 459       |      bSCL Field Length=4      |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     | 
              bgpSourceCommunityList value 1 = x               |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     | 
              bgpSourceCommunityList value 2 = x               |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+      
                               ...     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     | 
              bgpSourceCommunityList value 16376 = x           |     
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


P.



--------------AB5957A2F268C5981C80C3F2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><tt>Ignas Bagdonas wrote:</tt></p>
    <p><tt><br>
      </tt><tt>&gt; The upper limit may be reaching 16000 standard
        communities per prefix - would that fit into resulting IPFIX IE?
        If there is a limit, how does it work?</tt></p>
    <p><tt><br>
        A quick calculation suggests that the maximum would be 16376 x
        4-octet ASNs. See the figure below.</tt><tt><br>
      </tt></p>
    <p><tt>The constraining factor is the RFC7011 IPFIX Message Header
        "Length" field, since this is only 16 bits.<br>
      </tt></p>
    <p><tt><tt>Splitting a list across multiple IPFIX messages</tt></tt><tt>
        is a question which the IPFIX community hasn't discussed.</tt><tt>
        Unfortunately the basicList "Semantic" field only defines the
        relationship among the different values within a single message;
        the relationship among values in different messages is not
        defined.<br>
      </tt></p>
    <p><tt>IPFIX Collectors might reasonably assume that information in
        subsequent messages supersedes information in earlier messages,
        so splitting a list across multiple messages would not have the
        desired effect.</tt><tt><br>
      </tt></p>
    <p><br>
    </p>
    <pre><font face="Andale Mono">     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |       Version Number          |        Length = <font color="#cc0000">65532</font>         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           Export Time                         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                       Sequence Number                         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                    Observation Domain ID                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |          Set ID = 256         |         Length = <font color="#cc0000">65516</font>        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      255      |      List Length = <font color="#cc0000">65509</font>      | semantic=allOf|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      bSCL FieldId = 459       |      bSCL Field Length=4      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |              bgpSourceCommunityList value 1 = x               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |              bgpSourceCommunityList value 2 = x               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   ...
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |              bgpSourceCommunityList value <font color="#cc0000">16376</font> = x           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</font></pre>
    <p>
      <tt><br>
      </tt></p>
    <p><tt>P.</tt><br>
    </p>
    <br>
  </body>
</html>

--------------AB5957A2F268C5981C80C3F2--


From nobody Thu Feb 16 04:28:05 2017
Return-Path: <paitken@Brocade.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5730D129AB8; Thu, 16 Feb 2017 04:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kg5l86nGZXT; Thu, 16 Feb 2017 04:27:59 -0800 (PST)
Received: from mx0a-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::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 035481294E6; Thu, 16 Feb 2017 04:27:58 -0800 (PST)
Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1GCHcd9002277; Thu, 16 Feb 2017 04:17:38 -0800
Received: from brmwp-exmb12.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 28m20cg1nj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 04:17:38 -0800
Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by BRMWP-EXMB12.corp.brocade.com (172.16.59.130) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 05:17:35 -0700
Received: from [172.27.212.154] (172.27.212.154) by EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 13:17:30 +0100
To: =?UTF-8?B?5p2O5oyv5by6?= <13911635816@139.com>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>, grow-bounces <grow-bounces@ietf.org>, zhoutianran <zhoutianran@huawei.com>
References: <2d89235f-bbd2-4774-9472-4c4cea99a0e4@Tims-iPhone>
From: PJ Aitken <pjaitken@brocade.com>
Message-ID: <286d611d-32ae-7401-9790-a58f95301410@brocade.com>
Date: Thu, 16 Feb 2017 12:17:25 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2d89235f-bbd2-4774-9472-4c4cea99a0e4@Tims-iPhone>
Content-Type: multipart/alternative; boundary="------------4FFBB7D44CD467F5C1E090E3"
X-Originating-IP: [172.27.212.154]
X-ClientProxiedBy: hq1wp-excas11.corp.brocade.com (10.70.36.102) To EMEAWP-EXMB11.corp.brocade.com (172.29.11.85)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160119
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/maTYTz3soDf2lB7mgpyXCP82Nqs>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:28:00 -0000

--------------4FFBB7D44CD467F5C1E090E3
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

If the list would be longer than can be accommodated in a single IPFIX 
message, then some mechanism would need to be defined to allow the list 
to be exported.

Ideally this should be a generic mechanism allowing the export of any 
large IPFIX content. However, it might be simpler to define a mechanism 
that's specific to the export of long lists.

There may be several solutions. eg, it might be a compression mechanism 
allowing the content to fit into a single message. Or the content might 
be carried across multiple messages.

If you feel it's an issue - especially if it would block your current 
work - then please start the discussion in the OPSAWG because the IPFIX 
WG is closed.

Thanks,
P.

On 16/02/17 12:02, 李振强 wrote:
> The length of IPFIX message is sufficient for BGP standard 
> communities, since the length of standard community is 4 octets. But 
> the sizes of extended community, large community and wide community 
> are bigger than the size of standard community. If the working group 
> agrees to cover the above all kinds of communities in this draft, do 
> you think we should open the discussion for IPFIX and basicList 
> message splitting?


--------------4FFBB7D44CD467F5C1E090E3
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    If the list would be longer than can be accommodated in a single
    IPFIX message, then some mechanism would need to be defined to allow
    the list to be exported.<br>
    <br>
    Ideally this should be a generic mechanism allowing the export of
    any large IPFIX content. However, it might be simpler to define a
    mechanism that's specific to the export of long lists.<br>
    <br>
    There may be several solutions. eg, it might be a compression
    mechanism allowing the content to fit into a single message. Or the
    content might be carried across multiple messages.<br>
    <br>
    If you feel it's an issue - especially if it would block your
    current work - then please start the discussion in the OPSAWG
    because the IPFIX WG is closed.<br>
    <br>
    Thanks,<br>
    P.<br>
    <br>
    <div class="moz-cite-prefix">On 16/02/17 12:02, 李振强 wrote:<br>
    </div>
    <blockquote
      cite="mid:2d89235f-bbd2-4774-9472-4c4cea99a0e4@Tims-iPhone"
      type="cite"><font size="3"><span
          style="-webkit-tap-highlight-color: rgba(26, 26, 26,
          0.301961); -webkit-text-size-adjust: auto; background-color:
          rgba(255, 255, 255, 0);">The length of IPFIX message is
          sufficient for BGP standard communities, since the length of
          standard community is 4 octets. But the sizes of extended
          community, large community and wide community are bigger than
          the size of standard community. If the working group agrees to
          cover the above all kinds of communities in this draft, do you
          think we should open the discussion for IPFIX and basicList
          message splitting?</span></font></blockquote>
    <br>
  </body>
</html>

--------------4FFBB7D44CD467F5C1E090E3--


From nobody Thu Feb 16 06:13:56 2017
Return-Path: <13911635816@139.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3615512940E; Thu, 16 Feb 2017 04:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level: 
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_LOCAL_DIGITS=0.001, FROM_LOCAL_HEX=0.006, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlOZP5halGDs; Thu, 16 Feb 2017 04:02:44 -0800 (PST)
Received: from n9-37.mail.139.com (n9-37.mail.139.com [221.176.9.37]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3EE1294FD; Thu, 16 Feb 2017 04:02:42 -0800 (PST)
X-RM-TagInfo: emlType=0                                       
X-Richmail-Antispam: sCL2rVi0borhSzeOjpYxWEmrxqxSIjpgsIL2jVqxeZIR0RM= 
X-RM-SPAM-FLAG: 00000000
Received: from Tims-iPhone (unknown[223.72.55.167]) by rmsmtp-rmapp-18-12045 (RichMail) with SMTP id 2f0d58a594de027-9844c; Thu, 16 Feb 2017 20:02:41 +0800 (CST)
X-RM-TRANSID: 2f0d58a594de027-9844c
Date: Thu, 16 Feb 2017 20:02:40 +0800
From: =?utf-8?Q?=E6=9D=8E=E6=8C=AF=E5=BC=BA?= <13911635816@139.com>
To: PJ Aitken <pjaitken@brocade.com>,  "=?utf-8?Q?lizhenqiang=40chinamobile.com?=" <lizhenqiang@chinamobile.com>, grow-bounces <grow-bounces@ietf.org>,  zhoutianran <zhoutianran@huawei.com>
Message-ID: <2d89235f-bbd2-4774-9472-4c4cea99a0e4@Tims-iPhone>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="58a594e0_490e181c_13a7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/RBnBULqXPIPmdk9LBIhKB8MWR6s>
X-Mailman-Approved-At: Thu, 16 Feb 2017 06:13:56 -0800
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "=?utf-8?Q?ipfix=40ietf.org?=" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:02:46 -0000

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


Thank you P.J. Aitken.

The length of IP=46IX message is sufficient for BGP standard communities,=
 since the length of standard community is 4 octets. But the sizes of ext=
ended community, large community and wide community are bigger than the s=
ize of standard community. If the working group agrees to cover the above=
 all kinds of communities in this draft, do you think we should open the =
discussion for IP=46IX and basicList message splitting=3F

Sorry for the duplicate mails.

Best Regards
Zhenqiang Li



--=E5=8F=91=E8=87=AA139=E9=82=AE=E7=AE=B1APP
=E7=82=B9=E5=87=BB=E4=B8=8B=E8=BD=BD=E4=BD=BF=E7=94=A8=EF=BC=8C=E8=BD=BB=E6=
=9D=BE=E7=AE=A1=E7=90=86=E9=82=AE=E7=AE=B1pushemail.10086.cn/d/d.html(htt=
p://pushemail.10086.cn/d/d.html)

=E5=9C=A82017-02-16 19:59:59
=E6=9D=8E=E6=8C=AF=E5=BC=BA<13911635816=40139.com>=E5=86=99=E9=81=93:


=E5=8F=91=E4=BB=B6=E4=BA=BA:PJ Aitken<pjaitken=40brocade.com>
=E6=97=A5=E6=9C=9F:2017-02-16 19:16:00
=E6=94=B6=E4=BB=B6=E4=BA=BA:lizhenqiang=40chinamobile.com<lizhenqiang=40c=
hinamobile.com>, grow-bounces<grow-bounces=40ietf.org>, zhoutianran<zhout=
ianran=40huawei.com>
=E4=B8=BB=E9=A2=98:Re: =5BIP=46IX=5D =5BGROW=5D =5BOPSAWG=5D WG adoption =
poll fordraft-li-opsawg-ipfix-bgp-community-02


Ignas Bagdonas wrote:



>The upper limit may be reaching 16000 standard communities per prefix - =
would that fit into resulting IP=46IX IE=3F If there is a limit, how does=
 it work=3F



A quick calculation suggests that the maximum would be 16376 x 4-octet AS=
Ns. See the figure below.



The constraining factor is the R=46C7011 IP=46IX Message Header =22Length=
=22 field, since this is only 16 bits.



Splitting a list across multiple IP=46IX messagesis a question which the =
IP=46IX community hasn't discussed.Unfortunately the basicList =22Semanti=
c=22 field only defines the relationship among the different values withi=
n a single message; the relationship among values in different messages i=
s not defined.



IP=46IX Collectors might reasonably assume that information in subsequent=
 messages supersedes information in earlier messages, so splitting a list=
 across multiple messages would not have the desired effect.






0          1          2          3   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 =
8 9 0 1 2 3 4 5 6 7 8 9 0 1   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+   =7C    Version Number     =7C    Length =3D65532=
=7C   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  =
 =7C              Export Time             =7C   +-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   =7C            Sequence Number=
             =7C   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+   =7C          Observation Domain ID           =7C   +-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   =7C     Set I=
D =3D 256     =7C     Length =3D65516=7C   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   =7C   255   =7C   List Length =3D65=
509=7C semantic=3DallOf=7C   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+   =7C   bSCL =46ieldId =3D 459    =7C   bSCL =46iel=
d Length=3D4   =7C   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+   =7C       bgpSourceCommunityList value 1 =3D x        =7C=
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   =7C=
       bgpSourceCommunityList value 2 =3D x        =7C   +-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                  ...   =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   =7C  =
     bgpSourceCommunityList value16376=3D x      =7C   +-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+





P.



=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
IP=46IX mailing list
IP=46IX=40ietf.org
https://www.ietf.org/mailman/listinfo/ipfix

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


<br><font size=3D=223=22><span style=3D=22-webkit-tap-highlight-color: rg=
ba(26, 26, 26, 0.301961); -webkit-text-size-adjust: auto; background-colo=
r: rgba(255, 255, 255, 0);=22>Thank you P.J. Aitken.</span></font><div><f=
ont size=3D=223=22><span style=3D=22-webkit-tap-highlight-color: rgba(26,=
 26, 26, 0.301961); -webkit-text-size-adjust: auto; background-color: rgb=
a(255, 255, 255, 0);=22><br></span></font></div><div><font size=3D=223=22=
><span style=3D=22-webkit-tap-highlight-color: rgba(26, 26, 26, 0.301961)=
; -webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);=22>The length of IP=46IX message is sufficient for BGP standard commun=
ities, since the length of standard community is 4 octets. But the sizes =
of extended community, large community and wide community are bigger than=
 the size of standard community. If the working group agrees to cover the=
 above all kinds of communities in this draft, do you think we should ope=
n the discussion for IP=46IX and basicList message splitting=3F</span></f=
ont></div><div><font size=3D=223=22><span style=3D=22-webkit-tap-highligh=
t-color: rgba(26, 26, 26, 0.301961); -webkit-text-size-adjust: auto; back=
ground-color: rgba(255, 255, 255, 0);=22><br></span></font></div><div><fo=
nt size=3D=223=22><span style=3D=22-webkit-tap-highlight-color: rgba(26, =
26, 26, 0.301961); -webkit-text-size-adjust: auto; background-color: rgba=
(255, 255, 255, 0);=22>Sorry for the duplicate mails.</span></font></div>=
<div><font size=3D=223=22><span style=3D=22-webkit-tap-highlight-color: r=
gba(26, 26, 26, 0.301961); -webkit-text-size-adjust: auto; background-col=
or: rgba(255, 255, 255, 0);=22><br></span></font></div><div><font size=3D=
=223=22><span style=3D=22-webkit-tap-highlight-color: rgba(26, 26, 26, 0.=
301961); -webkit-text-size-adjust: auto; background-color: rgba(255, 255,=
 255, 0);=22>Best Regards&nbsp;</span></font></div><div><font size=3D=223=
=22><span style=3D=22-webkit-tap-highlight-color: rgba(26, 26, 26, 0.3019=
61); -webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255=
, 0);=22>Zhenqiang Li&nbsp;</span></font></div><div><font size=3D=223=22>=
<span style=3D=22-webkit-tap-highlight-color: rgba(26, 26, 26, 0.301961);=
 -webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0)=
;=22><br></span></font></div><div><br></div><br><font color=3D=22=23a8a8a=
8=22 style=3D=22font-size:15px=22>--=E5=8F=91=E8=87=AA139=E9=82=AE=E7=AE=B1=
APP<br>=E7=82=B9=E5=87=BB=E4=B8=8B=E8=BD=BD=E4=BD=BF=E7=94=A8=EF=BC=8C=E8=
=BD=BB=E6=9D=BE=E7=AE=A1=E7=90=86=E9=82=AE=E7=AE=B1 <a href=3D=22http://p=
ushemail.10086.cn/d/d.html=22><font color=3D=22=23a8a8a8=22>pushemail.100=
86.cn/d/d.html</font></a></font><br><br>=E5=9C=A82017-02-16 19:59:59<br>=E6=
=9D=8E=E6=8C=AF=E5=BC=BA&lt;13911635816=40139.com&gt;=E5=86=99=E9=81=93:<=
br><br><div style=3D=22 padding-left:10px =22><div style=3D=22border-left=
:2px solid =23999999; =22><div style=3D=22font-size: 12px;background:=23e=
fefef;padding:8px;=22><br><b>=E5=8F=91=E4=BB=B6=E4=BA=BA:</b>PJ Aitken &l=
t;pjaitken=40brocade.com&gt;<br><b>=E6=97=A5=E6=9C=9F:</b>2017-02-16 19:1=
6:00<br><b>=E6=94=B6=E4=BB=B6=E4=BA=BA:</b>lizhenqiang=40chinamobile.com =
&lt;lizhenqiang=40chinamobile.com&gt; , grow-bounces &lt;grow-bounces=40i=
etf.org&gt; , zhoutianran &lt;zhoutianran=40huawei.com&gt;<br><b>=E4=B8=BB=
=E9=A2=98:</b>Re: =5BIP=46IX=5D =5BGROW=5D =5BOPSAWG=5D WG adoption poll =
fordraft-li-opsawg-ipfix-bgp-community-02<br></div><br><div>

<meta content=3D=22text/html; charset=3Dutf-8=22 http-equiv=3D=22Content-=
Type=22>
<title></title>


<p><tt>Ignas Bagdonas wrote:</tt></p>
<p><tt><br></tt> <tt>&gt; The upper limit may be reaching 16000
standard communities per prefix - would that fit into resulting
IP=46IX IE=3F If there is a limit, how does it work=3F</tt></p>
<p><tt><br>
A quick calculation suggests that the maximum would be 16376 x
4-octet ASNs. See the figure below.</tt><tt><br></tt></p>
<p><tt>The constraining factor is the R=46C7011 IP=46IX Message Header
=22Length=22 field, since this is only 16 bits.<br></tt></p>
<p><tt><tt>Splitting a list across multiple IP=46IX
messages</tt></tt> <tt>is a question which the IP=46IX community
hasn't discussed.</tt> <tt>Unfortunately the basicList =22Semantic=22
field only defines the relationship among the different values
within a single message; the relationship among values in different
messages is not defined.<br></tt></p>
<p><tt>IP=46IX Collectors might reasonably assume that information in
subsequent messages supersedes information in earlier messages, so
splitting a list across multiple messages would not have the
desired effect.</tt><tt><br></tt></p>
<p><br></p>
<pre><font face=3D=22Andale Mono=22>     0                   1           =
        2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C       Version Number          =7C        Length =3D <font color=3D=
=22=23CC0000=22>65532</font>         =7C
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C                           Export Time                         =7C=

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C                       Sequence Number                         =7C=

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C                    Observation Domain ID                      =7C=

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C          Set ID =3D 256         =7C         Length =3D <font colo=
r=3D=22=23CC0000=22>65516</font>        =7C
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C      255      =7C      List Length =3D <font color=3D=22=23CC0000=
=22>65509</font>      =7C semantic=3DallOf=7C
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C      bSCL =46ieldId =3D 459       =7C      bSCL =46ield Length=3D=
4      =7C
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C              bgpSourceCommunityList value 1 =3D x               =7C=

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C              bgpSourceCommunityList value 2 =3D x               =7C=

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   ...
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    =7C              bgpSourceCommunityList value <font color=3D=22=23CC0=
000=22>16376</font> =3D x           =7C
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</fo=
nt>
</pre>
<p><tt><br></tt></p>
<p><tt>P.</tt><br></p>
<br>


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
<br>IP=46IX mailing list
<br>IP=46IX=40ietf.org
<br>https://www.ietf.org/mailman/listinfo/ipfix
<br></div></div></div>
--58a594e0_490e181c_13a7--



From nobody Thu Feb 16 08:14:33 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16FC2129D94; Thu, 16 Feb 2017 08:14:27 -0800 (PST)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHC6zxXm6eW8; Thu, 16 Feb 2017 08:14:25 -0800 (PST)
Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 338E2129D91; Thu, 16 Feb 2017 08:14:25 -0800 (PST)
Received: by mail-wr0-x243.google.com with SMTP id i10so2633594wrb.0; Thu, 16 Feb 2017 08:14:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=+bWWxAH+qosXgSd71fhV11pgpsEcCpBhxx9/LUqv+JE=; b=UXFa2x/rrGZwyuuwZokHUAZBc564a1eAOXlM7PctNFlsDgz+1s5dLGIPyoC6VuF6UZ E1NoYimc2XqeCy1ba4/IYo3rGBNjh3ql34sEsZMhikYmOohD2ZVaeUBxs8w4YK6T/NuP ZTu+wuOc8N13U976rLBzGo1R2SGFnm++wI2yYHHzFwPDcufWjhzvqyLae4to3YI6Dwav huYKM3c4Vy0YQywVRvEVYxXDPCOKX2f1Sc9QB7uP4wvyV67exIOgnTkJbAewPZmqbPW8 2TRILRBu+NsRlOLMCBu7VKAuY1aL057Bi9rTj7voomZR/qxdxtVa3wbDpwyj73/4yTfJ 6FiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=+bWWxAH+qosXgSd71fhV11pgpsEcCpBhxx9/LUqv+JE=; b=djjPapzI4BqC7mbkfbT3rECExTq5GkSmol7izsNusdqcsEM6ulEIej1PYPgNQhrppr w3+/LE4GbfmDtqQaCkOgjAdAZs9Muf+Xu+XRC2+JWPBJ5eyN+I7R4HWJ9QgWWLh5zw7E zHIuval6uTMRl4J1cZb3calJGIa0d+KpPSPySnUcok+j3IBkB3RSLuN1S812p9s0t1BX 0EIR+KCRAlkg+DjxcYcEvt5wMRWQyTPPhCPopxni5F3o+6xJnXdEq5UpRL4/rL5Uhj/u rDVnz+luq19GUY7zIUWPC4/HpTsDdYTnuZmJro6Xb1Sej/3i2rDtOJFS6UvvkExbDB4m JB0g==
X-Gm-Message-State: AMke39m8XYTYrOJOOM30htHSuAV02d08rzHRwBl1dnJ6vcKNXbCOSPG3Jk6uHGvJyWlOkw==
X-Received: by 10.223.139.213 with SMTP id w21mr3086012wra.108.1487261663740;  Thu, 16 Feb 2017 08:14:23 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id q16sm9478229wra.69.2017.02.16.08.14.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 08:14:23 -0800 (PST)
To: PJ Aitken <pjaitken@brocade.com>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>, grow-bounces <grow-bounces@ietf.org>, zhoutianran <zhoutianran@huawei.com>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B05@NKGEML515-MBX.china.huawei.com> <7023a95c-c6a9-4d6a-b009-8f35e447aa4e@gmail.com> <76CD132C3ADEF848BD84D028D243C9279357F4EA@NKGEML515-MBX.china.huawei.com> <2017021611151726192539@chinamobile.com> <9f060f89-a2a8-5f87-4d66-088cb389ac14@brocade.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <92fe27fc-f26b-ce1a-44c3-c16a33f9ad01@gmail.com>
Date: Thu, 16 Feb 2017 16:14:20 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <9f060f89-a2a8-5f87-4d66-088cb389ac14@brocade.com>
Content-Type: multipart/alternative; boundary="------------C9938F43EEFC00B6FCF389FE"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/MkCWHOn-2P5c3t4N9Qrajx609jI>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 16:14:27 -0000

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



On 16/02/2017 11:15, PJ Aitken wrote:
>
> IPFIX Collectors might reasonably assume that information in 
> subsequent messages supersedes information in earlier messages, so 
> splitting a list across multiple messages would not have the desired 
> effect.
>
>

Hi Paul

Could you not have multiple discrete templates?

Stewart

--------------C9938F43EEFC00B6FCF389FE
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">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 16/02/2017 11:15, PJ Aitken wrote:<br>
    </div>
    <blockquote
      cite="mid:9f060f89-a2a8-5f87-4d66-088cb389ac14@brocade.com"
      type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <p><tt>IPFIX Collectors might reasonably assume that information
          in subsequent messages supersedes information in earlier
          messages, so splitting a list across multiple messages would
          not have the desired effect.</tt><tt><br>
        </tt></p>
      <br>
    </blockquote>
    <br>
    Hi Paul<br>
    <br>
    Could you not have multiple discrete templates?<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------C9938F43EEFC00B6FCF389FE--


From nobody Thu Feb 16 09:08:51 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE8A129DA3; Thu, 16 Feb 2017 09:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cx1Hhc1ELGgw; Thu, 16 Feb 2017 09:08:45 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 916B2129D26; Thu, 16 Feb 2017 09:08:23 -0800 (PST)
Received: by puck.nether.net (Postfix, from userid 162) id 3A35454080D; Thu, 16 Feb 2017 12:08:23 -0500 (EST)
Date: Thu, 16 Feb 2017 12:08:23 -0500
From: Jared Mauch <jared@puck.Nether.net>
To: =?utf-8?B?5p2O5oyv5by6?= <13911635816@139.com>
Message-ID: <20170216170823.GA30571@puck.nether.net>
References: <5c1874b1-e7cd-4d6f-869f-b4d2f334f94d@Tims-iPhone>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5c1874b1-e7cd-4d6f-869f-b4d2f334f94d@Tims-iPhone>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/pY9zawG6QlFN1aHfYuu8fB8Pm8w>
Cc: "ipfix@ietf.org" <ipfix@ietf.org>, grow <grow@ietf.org>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>, opsawg-chairs <opsawg-chairs@ietf.org>, PJ Aitken <pjaitken@brocade.com>, grow-bounces <grow-bounces@ietf.org>, opsawg <opsawg@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 17:08:46 -0000

On Thu, Feb 16, 2017 at 07:53:23PM +0800, 李振强 wrote:
> Thank you P.J. Aitken.
> 
> The length of IPFIX message is sufficient for BGP standard communities, since the length of standard community is 4 octets. But the sizes of extended community, large community and wide community are bigger than the size of standard community. If the working group agrees to cover the above all kinds of communities in this draft, do you think we should open the discussion for IPFIX
> 

	I believe there should be coverage for 1997 as well as the upcoming large communities.

	- Jared


From nobody Thu Feb 16 09:43:23 2017
Return-Path: <job@instituut.net>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149541295A6 for <ipfix@ietfa.amsl.com>; Thu, 16 Feb 2017 09:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KwW32kdRT8zt for <ipfix@ietfa.amsl.com>; Thu, 16 Feb 2017 09:43:14 -0800 (PST)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B101129483 for <ipfix@ietf.org>; Thu, 16 Feb 2017 09:43:12 -0800 (PST)
Received: by mail-wr0-x231.google.com with SMTP id z61so16744215wrc.1 for <ipfix@ietf.org>; Thu, 16 Feb 2017 09:43:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=i38Bqohl4JqpJIzKPMNceTc/lylplcieeTNuM6uw8l8=; b=a+N0ytT0nuX/VgU8URCZ7pbgQkQpEcP5Ve+a2TF717WVnSsmU8LffyjckxXsSY9gcn 5nW9kX2Pt/fY4aideZ+9CX1l6Y5fj47+QAAcQ47PYJIDs27ZU4Et4cwsIupVhIPN6vWm FTSVJXpNkpFxfzvvFN8TTxzlNoS8stRtoNotEtUlMIhXXygkdTnY/s2zZ9m56RYm3Bm8 +L6nE/Hn7aAeZ0CfsRxpsO8VCet4lFPDtmCR0bm3t2LspMn6LkdhCfWnNThuk+V0yiS1 jj7Cnex6km81avf0ij98NV+aTEUSvnvRdOFBldzuMe6eZSAxAsxVeQRyUa/w9EEgCv3e Qp7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=i38Bqohl4JqpJIzKPMNceTc/lylplcieeTNuM6uw8l8=; b=XETNnMAqkwsf208AAXx5pYYQddzXSmc57+JE5ZRt5vEElAbmzfauRLH9nAd6bYCvWb cINUuWlPPswMmHIkQ9ZuLSL8Vc2A8dEQSufdbz4eG4/Hv4rinrk0HKalEAeV8ZHTL6Un lSHe5bxLIDaEBCh6bI7Iq+4rVRW2Dnl7m6zxA+Xb8bjf5fcrK/RuTM952jSlgo/hHuHm 3mmX7Z0dHfBubVSf7Etx4CXdwjP/RE+7aglfzty7ArEOdOKcxsIPTmwM/3i8zwO1RzTF 182kcREqGkKtzYZEwvebe9J9U42dUCdLlxAoAA7Dyo0zrfh0IwIM5TgNl7tQTiTwkWMK G0yw==
X-Gm-Message-State: AMke39k7qSFTKdOYJU5iB39+9a8CnMTYGarjFEsws/+IHrVLzvCF7kqjtpiwoiw+a81bSQ==
X-Received: by 10.223.135.184 with SMTP id b53mr3388198wrb.169.1487266990367;  Thu, 16 Feb 2017 09:43:10 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:a51d:3d60:b612:cbf5]) by smtp.gmail.com with ESMTPSA id n18sm9663070wra.64.2017.02.16.09.43.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 09:43:09 -0800 (PST)
Date: Thu, 16 Feb 2017 18:43:08 +0100
From: Job Snijders <job@instituut.net>
To: Jared Mauch <jared@puck.Nether.net>
Message-ID: <20170216174308.GO1115@hanna.meerval.net>
References: <5c1874b1-e7cd-4d6f-869f-b4d2f334f94d@Tims-iPhone> <20170216170823.GA30571@puck.nether.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20170216170823.GA30571@puck.nether.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/D73427Mo7o7dtCi1aRx7qVW4YW4>
Cc: "ipfix@ietf.org" <ipfix@ietf.org>, grow <grow@ietf.org>, =?utf-8?B?5p2O5oyv5by6?= <13911635816@139.com>, opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, PJ Aitken <pjaitken@brocade.com>, grow-bounces <grow-bounces@ietf.org>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 17:43:15 -0000

On Thu, Feb 16, 2017 at 12:08:23PM -0500, Jared Mauch wrote:
> On Thu, Feb 16, 2017 at 07:53:23PM +0800, 李振强 wrote:
> > The length of IPFIX message is sufficient for BGP standard
> > communities, since the length of standard community is 4 octets. But
> > the sizes of extended community, large community and wide community
> > are bigger than the size of standard community. If the working group
> > agrees to cover the above all kinds of communities in this draft, do
> > you think we should open the discussion for IPFIX
> > 
> 
> I believe there should be coverage for 1997 as well as the upcoming
> large communities.

Agreed. There certainly is merit in covering RFC 1997 (32-bit), RFC 4360
(64-bit) and RFC 8092 (96-bit). For each of these one can fit (at least
a few) of such communities in the 16 bits worth of length of the 'outer
enveloppe' that is the IPFIX record. Should be pretty straight forward.

On the other hand, the current version of the Wide communities draft has
a container mechanism, the outer layer at that level also has a 16-bit
field, like IPFIX has. One can't fit a 16-bit thing in a 16-bit + with
space left for leading / trailing IPFIX related data. I don't
immediately have suggestions how to fit this reliably.

Kind regards,

Job


From nobody Thu Feb 16 10:18:23 2017
Return-Path: <pds@lugs.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001F31294F5; Thu, 16 Feb 2017 10:18:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYIvwPzuy8jz; Thu, 16 Feb 2017 10:18:15 -0800 (PST)
Received: from COL004-OMC1S12.hotmail.com (col004-omc1s12.hotmail.com [65.55.34.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEB6B129406; Thu, 16 Feb 2017 10:18:15 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com ([65.55.34.9]) by COL004-OMC1S12.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Thu, 16 Feb 2017 10:18:15 -0800
Received: from BY2NAM03FT042.eop-NAM03.prod.protection.outlook.com (10.152.84.56) by BY2NAM03HT185.eop-NAM03.prod.protection.outlook.com (10.152.85.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Thu, 16 Feb 2017 18:18:13 +0000
Received: from BL2PR01MB1937.prod.exchangelabs.com (10.152.84.51) by BY2NAM03FT042.mail.protection.outlook.com (10.152.85.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10 via Frontend Transport; Thu, 16 Feb 2017 18:18:13 +0000
Received: from BL2PR01MB1937.prod.exchangelabs.com ([10.167.96.7]) by BL2PR01MB1937.prod.exchangelabs.com ([10.167.96.7]) with mapi id 15.01.0888.030; Thu, 16 Feb 2017 18:18:12 +0000
From: Peter Schoenmaker <pds@lugs.com>
To: grow <grow@ietf.org>
Thread-Topic: [GROW] [IPFIX] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02
Thread-Index: AQHSiEtG+ae0gX3OjUmRbGjLIve7haFr3fiAgAATd4A=
Date: Thu, 16 Feb 2017 18:18:12 +0000
Message-ID: <BL2PR01MB19378C13434ADC065C69C929DF5A0@BL2PR01MB1937.prod.exchangelabs.com>
References: <5c1874b1-e7cd-4d6f-869f-b4d2f334f94d@Tims-iPhone> <20170216170823.GA30571@puck.nether.net>
In-Reply-To: <20170216170823.GA30571@puck.nether.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=lugs.com;
x-incomingtopheadermarker: OriginalChecksum:08605FDDA42EE23473857900127FF7054255BC83AAC3A6E75082DA545EAFD51F; UpperCasedChecksum:23B68353A4848F9BAC7694AC748F4D320592D09F52F294A74B0E1DBF72550954; SizeAsReceived:7978; Count:37
x-ms-exchange-messagesentrepresentingtype: 1
x-incomingheadercount: 37
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; BY2NAM03HT185; 5:y3iPGA7y1A5hCXQcEE/f5o2QFRz+2ArjHMb8ebFYNsoVL0scA7axzALxImbl3+PHfd+KoqEn9P5b1yuA9kUKLK+wBrApXHk/a7pi9jDjSMl5D/lARDSQK3Oec+IT9WmBeicEjfcrytFdh79NjuPn09afq9hem0nPgUCOYPHkREc=; 24:yJpxacC2NOnF/fl4V2OvmlSrv3wSI6CQAhsf2xc6CzuO+C2M/xuK/ZS+4aIpIZyPZFT74ye39wdoWIAw2WTYlgN1cNCvtHpKtkTTM+onMQA=; 7:aRH6cbwCIn3Gxe/tc6HvhgBcY5EB/gHJS6LqHFcvoKeXhVeb4nceMZS9cFkWoWiz374x9OSp+sgim3rQRwaZ0ylJNoUMPLhQ6iiswzjNoY9YQctXaTRSjn/UxWezMgk/sAyV1E8sf5qx4GvLe8CyHVWogecKyj3osaKd2vMzf2Ux7VSYc1KXddYZtOFvVcDl9jzYucyqugc+w4sdmcWgmp+SPI+cdstlQmNTywDuZopBvSWjxeiFNepNK4QCcjF73JxA19jClyJvzNKWOS5A+owYfzHvJhxXRnXAa/40ItF/vD7wryZA9GUqmhj2vXWT
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900011); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2NAM03HT185; H:BL2PR01MB1937.prod.exchangelabs.com; FPR:; SPF:None; MLV:ovrnspm; LANG:en; 
x-ms-office365-filtering-correlation-id: 1469f04a-cee7-4869-1b03-08d456982954
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061046)(5061506529)(5061507331)(1603103135)(1601125210)(1603101373)(1701031045); SRVR:BY2NAM03HT185; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:BY2NAM03HT185; BCL:0; PCL:0; RULEID:; SRVR:BY2NAM03HT185; 
x-forefront-prvs: 0220D4B98D
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <C135E38584489E4AB068A55030070D5E@prod.exchangelabs.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2017 18:18:12.6523 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM03HT185
X-OriginalArrivalTime: 16 Feb 2017 18:18:15.0359 (UTC) FILETIME=[0A6314F0:01D28881]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/nId5VWF6u7nj7bnJ5zXD47GIpRE>
Cc: "ipfix@ietf.org" <ipfix@ietf.org>, Jared Mauch <jared@puck.Nether.net>, =?utf-8?B?5p2O5oyv5by6?= <13911635816@139.com>, opsawg-chairs <opsawg-chairs@ietf.org>, PJ Aitken <pjaitken@brocade.com>, opsawg <opsawg@ietf.org>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll fordraft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:18:17 -0000

SGkgbWFpbCB0aHJlYWQgZm9sa3M6DQoNCkl0IGFwcGVhcnMgdGhhdCB0aGlzIHRocmVhZCBoYWQg
Z3Jvdy1ib3VuY2VzQGlldGYub3JnIGFkZGVkIHRvIHRoZSBlbWFpbCBsaXN0IChhbmQgc3Vic2Vx
dWVudGx5IGdyb3dAaWV0Zi5vcmcgd2FzIGFkZCkuICBUaGlzIHdhcyBjYXVzaW5nIHRoZSBlbWFp
bHMgc2VudCB0byBib3VuY2UsIGFuZCBub3QgbWFrZSBpdCB0byB0aGUgZ3JvdyBtYWlsaW5nIGxp
c3QuICBQbGVhc2UgbWFrZSBzdXJlIGdyb3ctYm91bmNlc0BpZXRmLm9yZyBpcyBub3QgaW4gdGhl
IHRvL2NjLCBhbmQgZ3Jvd0BpZXRmLm9yZyBpcyBpbmNsdWRlZCB3aGVuIHJlc3BvbmRpbmcuDQoN
CnRoYW5rcw0KDQpQZXRlcg0KDQogDQoNCg0K


From nobody Thu Feb 16 13:10:32 2017
Return-Path: <paitken@Brocade.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B331294A5; Thu, 16 Feb 2017 13:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNvXqPYgP0Cf; Thu, 16 Feb 2017 13:10:22 -0800 (PST)
Received: from mx0a-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::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 872A11294F4; Thu, 16 Feb 2017 13:10:22 -0800 (PST)
Received: from pps.filterd (m0048192.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1GLAESg022426; Thu, 16 Feb 2017 13:10:14 -0800
Received: from brmwp-exmb12.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 28m1ya1xde-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 13:10:14 -0800
Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by BRMWP-EXMB12.corp.brocade.com (172.16.59.130) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 14:10:11 -0700
Received: from [10.252.49.8] (10.252.49.8) by EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 22:10:05 +0100
To: Stewart Bryant <stewart.bryant@gmail.com>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B05@NKGEML515-MBX.china.huawei.com> <7023a95c-c6a9-4d6a-b009-8f35e447aa4e@gmail.com> <76CD132C3ADEF848BD84D028D243C9279357F4EA@NKGEML515-MBX.china.huawei.com> <2017021611151726192539@chinamobile.com> <9f060f89-a2a8-5f87-4d66-088cb389ac14@brocade.com> <92fe27fc-f26b-ce1a-44c3-c16a33f9ad01@gmail.com>
From: PJ Aitken <pjaitken@brocade.com>
Message-ID: <975eea07-1183-2356-dd32-e5543f9f8aa6@brocade.com>
Date: Thu, 16 Feb 2017 21:10:00 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <92fe27fc-f26b-ce1a-44c3-c16a33f9ad01@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.252.49.8]
X-ClientProxiedBy: hq1wp-excas12.corp.brocade.com (10.70.38.22) To EMEAWP-EXMB11.corp.brocade.com (172.29.11.85)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_14:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/k7mCdisWKihEvv1DNL-SrNHcLNo>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:10:24 -0000

Stewart: yes, there could be multiple templates with multiple data records.

However there's nothing to provide the necessary "All of <these>" 
semantics to allow the collector to join up the lists in a meaningful 
way - ie, specifying which lists to use / not to use, and in which order 
if that's important.

Also, the data held by the collector may be indeterminate as the data 
records change - eg if list#1 and list#4 were updated, but updates 
hadn't yet been received for list#2 and list#3. So there'd have to be a 
"hold" time when nothing is changing and/or a signal that the current 
state is good - which then leads to questions of how to handle data loss 
(eg, if the update for list#2 wasn't received in time, or arrived late.

If single packet data export is no longer sufficient - as seems likely - 
then, since we already have several ideas, it'd be worth some IPFIX 
experts pondering what the correct solution should be.

P.


> On 16/02/2017 11:15, PJ Aitken wrote:
>>
>> IPFIX Collectors might reasonably assume that information in 
>> subsequent messages supersedes information in earlier messages, so 
>> splitting a list across multiple messages would not have the desired 
>> effect.
>>
>>
>
> Hi Paul
>
> Could you not have multiple discrete templates?
>
> Stewart


From paolo@ntt.net  Thu Feb 16 14:52:38 2017
Return-Path: <paolo@ntt.net>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C37912955E; Thu, 16 Feb 2017 14:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WrCN4yc5_JmP; Thu, 16 Feb 2017 14:52:37 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 3176D124281; Thu, 16 Feb 2017 14:52:37 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.88) (envelope-from <paolo@ntt.net>) id 1ceUue-0003og-5a (paolo@us.ntt.net); Thu, 16 Feb 2017 22:52:33 +0000
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Paolo Lucente <paolo@ntt.net>
X-Priority: 3
In-Reply-To: <2017021611151726192539@chinamobile.com>
Date: Thu, 16 Feb 2017 23:52:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC4D38F4-7735-4C76-8590-FF6B4B012949@ntt.net>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B05@NKGEML515-MBX.china.huawei.com> <7023a95c-c6a9-4d6a-b009-8f35e447aa4e@gmail.com> <76CD132C3ADEF848BD84D028D243C9279357F4EA@NKGEML515-MBX.china.huawei.com> <2017021611151726192539@chinamobile.com>
To: lizhenqiang@chinamobile.com
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/FCafaDk9yMlJXrJHbR1-4R5aLUo>
X-Mailman-Approved-At: Thu, 16 Feb 2017 20:41:16 -0800
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 22:54:52 -0000

Hi,

I support Ignas comment with regards to Extended and Large communities.

Can you make evident the role, ie. via an example, of the bgpCommunity
IE compared to the one of bgpDestinationCommunityList?

Also, i'm puzzled by the presence of bgpSourceCommunityList: i see that
in "1. Introduction" you kind of close that up saying that there is a
Mediator that would take care of the correlation - understandable but
then again we all know with a (loosely determined) level of indirection
any problem can be addressed; since you also say the draft comes "comes
from the field network", i was wondering whether you were subtending to
reverse BGP lookups to make this work in practice. In which case, i'd
say warning flag: BGP lookups against the source IP address/prefix of a
flow would be of no general applicability at all - think, for example,
to the common case of an ISP (remotely) connected to an IXP where you
have N BGP peers and hence potentially multiple advertisements per
prefix, which one you pick for correlation would not be a deterministic
exercise.

Paolo


> On 16 Feb 2017, at 04:15, lizhenqiang@chinamobile.com wrote:
>=20
> Dear Ignas,
>=20
> Thank you very much for your support and suggestion.
>=20
> Since the problem to be solved in this draft comes from the field =
network, we only provide the method to carry standard BGP commmunities =
in IPFIX. Extended communities are ususlly used for other purposes than =
standard communities, such as route target, actions for BGP flowspec =
etc. Whether or not we really need to cover entended communities, I want =
to see more comments. Large communities are relavitely new. RFC8092 was =
published recentlly.  Anyway, however, it is easy for us to cover both =
extended communities [RFC4360] and large communities [RFC8092] after the =
adoption and further comment consensus. Text contribution is welcome. By =
the way, I want to know the opinions about the wide communities. Do we =
need to cover them together?
>=20
> As you said, this draft was a good start. It has value to be a working =
group item. We can continue the comments and discussion after the =
adoption and we will improve the document according to the consensus. =
Operational considerations will be covered in the next version.
>=20
> Best Regards,
> Zhenqiang Li
> China Mobile
> =20
> -----Original Message-----
> From: GROW [mailto:grow-bounces@ietf.org] On Behalf Of Ignas Bagdonas
> Sent: Tuesday, February 14, 2017 9:46 PM
> To: Tianran Zhou <zhoutianran@huawei.com>
> Cc: opsawg@ietf.org; opsawg-chairs@ietf.org; grow@ietf.org =
grow@ietf.org <grow@ietf.org>
> Subject: Re: [GROW] [OPSAWG] WG adoption poll for =
draft-li-opsawg-ipfix-bgp-community-02
> =20
> Hi there,
> =20
> [Copying GROW WG as this might be relevant to their coverage areas]
> =20
> The document seems to be a good start but covers only standard =
communities. This is not sufficient given the universal deployment of 4 =
octet ASNs. Both extended communities [RFC4360] and large communities =
[RFC8092] are needed and are used to address the signalling requirements =
for AS4 ASNs. Having separate documents each addressing only a specific =
type of community does not seem practical and rational. The document =
should include the definitions for IEs covering extended and large =
communities.
> =20
> What is the logic of selecting multiple communities for export that a =
prefix may have been decorated with? Is it all of them all the time? The =
upper limit may be reaching 16000 standard communities per prefix - =
would that fit into resulting IPFIX IE? If there is a limit, how does it =
work? Is there any interpretation done on the values of the communities =
(all types, not just standard ones)? Those all are operational =
considerations aspects and should be covered in the document, appendix A =
likely could be a good place for it.
> =20
> Security considerations on the privacy aspects would to be covered.
> =20
> Ignas
> =20
> =20
> =20
> =20
> On 13/02/2017 03:36, Tianran Zhou wrote:
> > Dear OPSAWG,
> >
> > In Seoul, we got enough interest and positive response on this IPFIX =
IE extension draft.
> > By the authors' request, this email starts a formal poll. The chairs =
would like to know if the WG participants agree that the following =
document should be adopted as a WG document in OPSAWG.
> >
> > Export BGP community information in IP Flow Information Export =
(IPFIX)
> > https://tools.ietf.org/html/draft-li-opsawg-ipfix-bgp-community-02
> >
> > The adoption poll will take two weeks. Please let us know your =
opinion by Feb 27. It would also be good to hear who is willing to =
review and/or implement or deploy the extension described in the =
document.
> >
> > Since we already found that the majority of the f2f participants at =
our IETF97 session like this idea, please do speak up now if you do not =
agree or have serious objections (with explanation of course).
> >
> > Regards,
> > Tianran
> >
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www.ietf.org/mailman/listinfo/opsawg
> =20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From nobody Mon Feb 20 00:58:43 2017
Return-Path: <lizhenqiang@chinamobile.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6404A128BA2; Mon, 20 Feb 2017 00:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODsUNf_mhvww; Mon, 20 Feb 2017 00:58:33 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id F219512706D; Mon, 20 Feb 2017 00:58:31 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.17]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee258aaafb0d4b-061ae; Mon, 20 Feb 2017 16:58:24 +0800 (CST)
X-RM-TRANSID: 2ee258aaafb0d4b-061ae
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[221.130.253.135]) by rmsmtp-syy-appsvr09-12009 (RichMail) with SMTP id 2ee958aaafaefa8-27ea6; Mon, 20 Feb 2017 16:58:23 +0800 (CST)
X-RM-TRANSID: 2ee958aaafaefa8-27ea6
Date: Mon, 20 Feb 2017 16:58:32 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: "Paolo Lucente" <paolo@ntt.net>
References: <BBA82579FD347748BEADC4C445EA0F21A22B8B05@NKGEML515-MBX.china.huawei.com>,  <7023a95c-c6a9-4d6a-b009-8f35e447aa4e@gmail.com>,  <76CD132C3ADEF848BD84D028D243C9279357F4EA@NKGEML515-MBX.china.huawei.com>,  <2017021611151726192539@chinamobile.com>,  <EC4D38F4-7735-4C76-8590-FF6B4B012949@ntt.net>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <2017021710323644287217@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart511787134451_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/p5tDMAiyxEKs2-Bnebbky0U-n3M>
Cc: opsawg <opsawg@ietf.org>, opsawg-chairs <opsawg-chairs@ietf.org>, grow <grow@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-community-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 08:58:36 -0000

This is a multi-part message in MIME format.

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

SGkgUGFvbG/vvIwNCg0KVGhhbmsgeW91IGZvciB5b3Ugb3Bpbmlvbi4gVGhlIGV4dGVuZGVkIGFu
ZCBsYXJnZSBjb21tdW5pdGllcyB3aWxsIGJlIGNvbnNpZGVyZWQgYWZ0ZXIgdGhlIGFkb3B0aW9u
IGFuZCBhY2NvcmRpbmcgdG8gdGhlIHdvcmtpbmcgZ3JvdXAgY29uc2Vuc3VzLg0KDQpQbGVhc2Ug
c2VlIHRoZSBhcHBlbmRpeCAgaW4gdGhlIGRyYWZ0IGZvciB0aGUgZXhhbXBsZS4gYmdwRGVzdGlu
YXRpb25Db21tdW5pdHlMaXN0IGlzIGEgYmFzaWNMaXN0IG9mIGJncENvbW11bml0eS4NCg0KSWYg
eW91IGRvbid0IGxpa2UgdGhlIEJHUCBjb21tdW5pdGllcyBhY2NvcmRpbmcgdG8gdGhlIHNvdXJj
ZSBJUCBvZiBhIHNwZWNpZmljIGZsb3csIHlvdSBjYW4gaW5kaWNhdGUgaXQgaW4gdGhlIHRlbXBs
ZXRlLCBpLmUuIGRvIG5vdCBzcGVjaWZ5IGJncFNvdXJjZUNvbW11bml0eUxpc3QgSUUgaW4gdGhl
IHRlbXBsZXRlIHNldC4gVGhlbiB0aGUgZXhwb3J0ZXIgd2lsbCBub3QgZXhwb3J0IHRoZSBpbmZv
cm1hdGlvbi4gDQoNCmJncFNvdXJjZUNvbW11bml0eUxpc3QgZG9lcyBoYXZlIHZhbHVlcyBpbiBz
b21lIG5ldHdvcmsgZW52aXJvbm1lbnRzLiBGb3IgZXhhbXBsZSwgIHRoZSBvdmVyYWxsbCBuZXR3
b3JrIG9mIENoaW5hIE1vYmlsZSBjb25zaXN0cyBvZiBhIGJhY2tib25lIG5ldHdvcmsgYW5kIHNl
dmVyYWwgcHJvdmluY2UgbmV0d29ya3MuIEVhY2ggY29tcG9uZW50IG5ldHdvcmsgaXMgY29uZmln
dXJlZCB3aXRoIGEgZmV3IGNvbW11bml0aWVzLiBCR1AgYW5vdW5jZXMgdGhvc2UgY29tbXVuaXRp
ZXMgYW1vbmcgdGhlIGNvbXBvbmVudCBuZXR3b3Jrcy4gV2hlbiBvbmUgcHJvdmluY2Ugd2FudHMg
dG8ga25vdyB3aGVyZSAoaS5lLiBmcm9tIHdoaWNoIHByb3ZpbmNlcykgaXRzIGluY29taW5nIHRy
YWZmaWMgY29tZXMgZnJvbSwgaXQgY2FuIHVzZSBiZ3BTb3VyY2VDb21tdW5pdHlMaXN0Lg0KDQpC
ZXN0IFJlZ2FyZHMsDQpaaGVucWlhbmcNCg0KDQpsaXpoZW5xaWFuZ0BjaGluYW1vYmlsZS5jb20N
CiANCkZyb206IFBhb2xvIEx1Y2VudGUNCkRhdGU6IDIwMTctMDItMTcgMDY6NTINClRvOiBsaXpo
ZW5xaWFuZw0KQ0M6IHpob3V0aWFucmFuOyBvcHNhd2c7IG9wc2F3Zy1jaGFpcnM7IGdyb3c7IGlw
Zml4QGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0dST1ddIFtPUFNBV0ddIFdHIGFkb3B0aW9uIHBv
bGwgZm9yIGRyYWZ0LWxpLW9wc2F3Zy1pcGZpeC1iZ3AtY29tbXVuaXR5LTAyDQogDQpIaSwNCiAN
Ckkgc3VwcG9ydCBJZ25hcyBjb21tZW50IHdpdGggcmVnYXJkcyB0byBFeHRlbmRlZCBhbmQgTGFy
Z2UgY29tbXVuaXRpZXMuDQogDQpDYW4geW91IG1ha2UgZXZpZGVudCB0aGUgcm9sZSwgaWUuIHZp
YSBhbiBleGFtcGxlLCBvZiB0aGUgYmdwQ29tbXVuaXR5DQpJRSBjb21wYXJlZCB0byB0aGUgb25l
IG9mIGJncERlc3RpbmF0aW9uQ29tbXVuaXR5TGlzdD8NCiANCkFsc28sIGknbSBwdXp6bGVkIGJ5
IHRoZSBwcmVzZW5jZSBvZiBiZ3BTb3VyY2VDb21tdW5pdHlMaXN0OiBpIHNlZSB0aGF0DQppbiAi
MS4gSW50cm9kdWN0aW9uIiB5b3Uga2luZCBvZiBjbG9zZSB0aGF0IHVwIHNheWluZyB0aGF0IHRo
ZXJlIGlzIGENCk1lZGlhdG9yIHRoYXQgd291bGQgdGFrZSBjYXJlIG9mIHRoZSBjb3JyZWxhdGlv
biAtIHVuZGVyc3RhbmRhYmxlIGJ1dA0KdGhlbiBhZ2FpbiB3ZSBhbGwga25vdyB3aXRoIGEgKGxv
b3NlbHkgZGV0ZXJtaW5lZCkgbGV2ZWwgb2YgaW5kaXJlY3Rpb24NCmFueSBwcm9ibGVtIGNhbiBi
ZSBhZGRyZXNzZWQ7IHNpbmNlIHlvdSBhbHNvIHNheSB0aGUgZHJhZnQgY29tZXMgImNvbWVzDQpm
cm9tIHRoZSBmaWVsZCBuZXR3b3JrIiwgaSB3YXMgd29uZGVyaW5nIHdoZXRoZXIgeW91IHdlcmUg
c3VidGVuZGluZyB0bw0KcmV2ZXJzZSBCR1AgbG9va3VwcyB0byBtYWtlIHRoaXMgd29yayBpbiBw
cmFjdGljZS4gSW4gd2hpY2ggY2FzZSwgaSdkDQpzYXkgd2FybmluZyBmbGFnOiBCR1AgbG9va3Vw
cyBhZ2FpbnN0IHRoZSBzb3VyY2UgSVAgYWRkcmVzcy9wcmVmaXggb2YgYQ0KZmxvdyB3b3VsZCBi
ZSBvZiBubyBnZW5lcmFsIGFwcGxpY2FiaWxpdHkgYXQgYWxsIC0gdGhpbmssIGZvciBleGFtcGxl
LA0KdG8gdGhlIGNvbW1vbiBjYXNlIG9mIGFuIElTUCAocmVtb3RlbHkpIGNvbm5lY3RlZCB0byBh
biBJWFAgd2hlcmUgeW91DQpoYXZlIE4gQkdQIHBlZXJzIGFuZCBoZW5jZSBwb3RlbnRpYWxseSBt
dWx0aXBsZSBhZHZlcnRpc2VtZW50cyBwZXINCnByZWZpeCwgd2hpY2ggb25lIHlvdSBwaWNrIGZv
ciBjb3JyZWxhdGlvbiB3b3VsZCBub3QgYmUgYSBkZXRlcm1pbmlzdGljDQpleGVyY2lzZS4NCiAN
ClBhb2xvDQogDQogDQo+IE9uIDE2IEZlYiAyMDE3LCBhdCAwNDoxNSwgbGl6aGVucWlhbmdAY2hp
bmFtb2JpbGUuY29tIHdyb3RlOg0KPiANCj4gRGVhciBJZ25hcywNCj4gDQo+IFRoYW5rIHlvdSB2
ZXJ5IG11Y2ggZm9yIHlvdXIgc3VwcG9ydCBhbmQgc3VnZ2VzdGlvbi4NCj4gDQo+IFNpbmNlIHRo
ZSBwcm9ibGVtIHRvIGJlIHNvbHZlZCBpbiB0aGlzIGRyYWZ0IGNvbWVzIGZyb20gdGhlIGZpZWxk
IG5ldHdvcmssIHdlIG9ubHkgcHJvdmlkZSB0aGUgbWV0aG9kIHRvIGNhcnJ5IHN0YW5kYXJkIEJH
UCBjb21tbXVuaXRpZXMgaW4gSVBGSVguIEV4dGVuZGVkIGNvbW11bml0aWVzIGFyZSB1c3VzbGx5
IHVzZWQgZm9yIG90aGVyIHB1cnBvc2VzIHRoYW4gc3RhbmRhcmQgY29tbXVuaXRpZXMsIHN1Y2gg
YXMgcm91dGUgdGFyZ2V0LCBhY3Rpb25zIGZvciBCR1AgZmxvd3NwZWMgZXRjLiBXaGV0aGVyIG9y
IG5vdCB3ZSByZWFsbHkgbmVlZCB0byBjb3ZlciBlbnRlbmRlZCBjb21tdW5pdGllcywgSSB3YW50
IHRvIHNlZSBtb3JlIGNvbW1lbnRzLiBMYXJnZSBjb21tdW5pdGllcyBhcmUgcmVsYXZpdGVseSBu
ZXcuIFJGQzgwOTIgd2FzIHB1Ymxpc2hlZCByZWNlbnRsbHkuICBBbnl3YXksIGhvd2V2ZXIsIGl0
IGlzIGVhc3kgZm9yIHVzIHRvIGNvdmVyIGJvdGggZXh0ZW5kZWQgY29tbXVuaXRpZXMgW1JGQzQz
NjBdIGFuZCBsYXJnZSBjb21tdW5pdGllcyBbUkZDODA5Ml0gYWZ0ZXIgdGhlIGFkb3B0aW9uIGFu
ZCBmdXJ0aGVyIGNvbW1lbnQgY29uc2Vuc3VzLiBUZXh0IGNvbnRyaWJ1dGlvbiBpcyB3ZWxjb21l
LiBCeSB0aGUgd2F5LCBJIHdhbnQgdG8ga25vdyB0aGUgb3BpbmlvbnMgYWJvdXQgdGhlIHdpZGUg
Y29tbXVuaXRpZXMuIERvIHdlIG5lZWQgdG8gY292ZXIgdGhlbSB0b2dldGhlcj8NCj4gDQo+IEFz
IHlvdSBzYWlkLCB0aGlzIGRyYWZ0IHdhcyBhIGdvb2Qgc3RhcnQuIEl0IGhhcyB2YWx1ZSB0byBi
ZSBhIHdvcmtpbmcgZ3JvdXAgaXRlbS4gV2UgY2FuIGNvbnRpbnVlIHRoZSBjb21tZW50cyBhbmQg
ZGlzY3Vzc2lvbiBhZnRlciB0aGUgYWRvcHRpb24gYW5kIHdlIHdpbGwgaW1wcm92ZSB0aGUgZG9j
dW1lbnQgYWNjb3JkaW5nIHRvIHRoZSBjb25zZW5zdXMuIE9wZXJhdGlvbmFsIGNvbnNpZGVyYXRp
b25zIHdpbGwgYmUgY292ZXJlZCBpbiB0aGUgbmV4dCB2ZXJzaW9uLg0KPiANCj4gQmVzdCBSZWdh
cmRzLA0KPiBaaGVucWlhbmcgTGkNCj4gQ2hpbmEgTW9iaWxlDQo+ICANCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogR1JPVyBbbWFpbHRvOmdyb3ctYm91bmNlc0BpZXRmLm9y
Z10gT24gQmVoYWxmIE9mIElnbmFzIEJhZ2RvbmFzDQo+IFNlbnQ6IFR1ZXNkYXksIEZlYnJ1YXJ5
IDE0LCAyMDE3IDk6NDYgUE0NCj4gVG86IFRpYW5yYW4gWmhvdSA8emhvdXRpYW5yYW5AaHVhd2Vp
LmNvbT4NCj4gQ2M6IG9wc2F3Z0BpZXRmLm9yZzsgb3BzYXdnLWNoYWlyc0BpZXRmLm9yZzsgZ3Jv
d0BpZXRmLm9yZyBncm93QGlldGYub3JnIDxncm93QGlldGYub3JnPg0KPiBTdWJqZWN0OiBSZTog
W0dST1ddIFtPUFNBV0ddIFdHIGFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0LWxpLW9wc2F3Zy1pcGZp
eC1iZ3AtY29tbXVuaXR5LTAyDQo+ICANCj4gSGkgdGhlcmUsDQo+ICANCj4gW0NvcHlpbmcgR1JP
VyBXRyBhcyB0aGlzIG1pZ2h0IGJlIHJlbGV2YW50IHRvIHRoZWlyIGNvdmVyYWdlIGFyZWFzXQ0K
PiAgDQo+IFRoZSBkb2N1bWVudCBzZWVtcyB0byBiZSBhIGdvb2Qgc3RhcnQgYnV0IGNvdmVycyBv
bmx5IHN0YW5kYXJkIGNvbW11bml0aWVzLiBUaGlzIGlzIG5vdCBzdWZmaWNpZW50IGdpdmVuIHRo
ZSB1bml2ZXJzYWwgZGVwbG95bWVudCBvZiA0IG9jdGV0IEFTTnMuIEJvdGggZXh0ZW5kZWQgY29t
bXVuaXRpZXMgW1JGQzQzNjBdIGFuZCBsYXJnZSBjb21tdW5pdGllcyBbUkZDODA5Ml0gYXJlIG5l
ZWRlZCBhbmQgYXJlIHVzZWQgdG8gYWRkcmVzcyB0aGUgc2lnbmFsbGluZyByZXF1aXJlbWVudHMg
Zm9yIEFTNCBBU05zLiBIYXZpbmcgc2VwYXJhdGUgZG9jdW1lbnRzIGVhY2ggYWRkcmVzc2luZyBv
bmx5IGEgc3BlY2lmaWMgdHlwZSBvZiBjb21tdW5pdHkgZG9lcyBub3Qgc2VlbSBwcmFjdGljYWwg
YW5kIHJhdGlvbmFsLiBUaGUgZG9jdW1lbnQgc2hvdWxkIGluY2x1ZGUgdGhlIGRlZmluaXRpb25z
IGZvciBJRXMgY292ZXJpbmcgZXh0ZW5kZWQgYW5kIGxhcmdlIGNvbW11bml0aWVzLg0KPiAgDQo+
IFdoYXQgaXMgdGhlIGxvZ2ljIG9mIHNlbGVjdGluZyBtdWx0aXBsZSBjb21tdW5pdGllcyBmb3Ig
ZXhwb3J0IHRoYXQgYSBwcmVmaXggbWF5IGhhdmUgYmVlbiBkZWNvcmF0ZWQgd2l0aD8gSXMgaXQg
YWxsIG9mIHRoZW0gYWxsIHRoZSB0aW1lPyBUaGUgdXBwZXIgbGltaXQgbWF5IGJlIHJlYWNoaW5n
IDE2MDAwIHN0YW5kYXJkIGNvbW11bml0aWVzIHBlciBwcmVmaXggLSB3b3VsZCB0aGF0IGZpdCBp
bnRvIHJlc3VsdGluZyBJUEZJWCBJRT8gSWYgdGhlcmUgaXMgYSBsaW1pdCwgaG93IGRvZXMgaXQg
d29yaz8gSXMgdGhlcmUgYW55IGludGVycHJldGF0aW9uIGRvbmUgb24gdGhlIHZhbHVlcyBvZiB0
aGUgY29tbXVuaXRpZXMgKGFsbCB0eXBlcywgbm90IGp1c3Qgc3RhbmRhcmQgb25lcyk/IFRob3Nl
IGFsbCBhcmUgb3BlcmF0aW9uYWwgY29uc2lkZXJhdGlvbnMgYXNwZWN0cyBhbmQgc2hvdWxkIGJl
IGNvdmVyZWQgaW4gdGhlIGRvY3VtZW50LCBhcHBlbmRpeCBBIGxpa2VseSBjb3VsZCBiZSBhIGdv
b2QgcGxhY2UgZm9yIGl0Lg0KPiAgDQo+IFNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIG9uIHRoZSBw
cml2YWN5IGFzcGVjdHMgd291bGQgdG8gYmUgY292ZXJlZC4NCj4gIA0KPiBJZ25hcw0KPiAgDQo+
ICANCj4gIA0KPiAgDQo+IE9uIDEzLzAyLzIwMTcgMDM6MzYsIFRpYW5yYW4gWmhvdSB3cm90ZToN
Cj4gPiBEZWFyIE9QU0FXRywNCj4gPg0KPiA+IEluIFNlb3VsLCB3ZSBnb3QgZW5vdWdoIGludGVy
ZXN0IGFuZCBwb3NpdGl2ZSByZXNwb25zZSBvbiB0aGlzIElQRklYIElFIGV4dGVuc2lvbiBkcmFm
dC4NCj4gPiBCeSB0aGUgYXV0aG9ycycgcmVxdWVzdCwgdGhpcyBlbWFpbCBzdGFydHMgYSBmb3Jt
YWwgcG9sbC4gVGhlIGNoYWlycyB3b3VsZCBsaWtlIHRvIGtub3cgaWYgdGhlIFdHIHBhcnRpY2lw
YW50cyBhZ3JlZSB0aGF0IHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQgc2hvdWxkIGJlIGFkb3B0ZWQg
YXMgYSBXRyBkb2N1bWVudCBpbiBPUFNBV0cuDQo+ID4NCj4gPiBFeHBvcnQgQkdQIGNvbW11bml0
eSBpbmZvcm1hdGlvbiBpbiBJUCBGbG93IEluZm9ybWF0aW9uIEV4cG9ydCAoSVBGSVgpDQo+ID4g
aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxpLW9wc2F3Zy1pcGZpeC1iZ3AtY29t
bXVuaXR5LTAyDQo+ID4NCj4gPiBUaGUgYWRvcHRpb24gcG9sbCB3aWxsIHRha2UgdHdvIHdlZWtz
LiBQbGVhc2UgbGV0IHVzIGtub3cgeW91ciBvcGluaW9uIGJ5IEZlYiAyNy4gSXQgd291bGQgYWxz
byBiZSBnb29kIHRvIGhlYXIgd2hvIGlzIHdpbGxpbmcgdG8gcmV2aWV3IGFuZC9vciBpbXBsZW1l
bnQgb3IgZGVwbG95IHRoZSBleHRlbnNpb24gZGVzY3JpYmVkIGluIHRoZSBkb2N1bWVudC4NCj4g
Pg0KPiA+IFNpbmNlIHdlIGFscmVhZHkgZm91bmQgdGhhdCB0aGUgbWFqb3JpdHkgb2YgdGhlIGYy
ZiBwYXJ0aWNpcGFudHMgYXQgb3VyIElFVEY5NyBzZXNzaW9uIGxpa2UgdGhpcyBpZGVhLCBwbGVh
c2UgZG8gc3BlYWsgdXAgbm93IGlmIHlvdSBkbyBub3QgYWdyZWUgb3IgaGF2ZSBzZXJpb3VzIG9i
amVjdGlvbnMgKHdpdGggZXhwbGFuYXRpb24gb2YgY291cnNlKS4NCj4gPg0KPiA+IFJlZ2FyZHMs
DQo+ID4gVGlhbnJhbg0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCj4gPiBPUFNBV0cgbWFpbGluZyBsaXN0DQo+ID4gT1BTQVdHQGlldGYu
b3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHNhd2cNCj4g
IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBH
Uk9XIG1haWxpbmcgbGlzdA0KPiBHUk9XQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vZ3Jvdw0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPiBHUk9XIG1haWxpbmcgbGlzdA0KPiBHUk9XQGlldGYub3JnDQo+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZ3Jvdw0KIA0KIA0K

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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3Dutf-8"><style>body { line-height: 1.5; }blockquote { margin-top: 0px; =
margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; font-fa=
mily: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; color: rgb(0, 0, 0); line-heig=
ht: 1.5; }body { font-size: 10.5pt; color: rgb(0, 0, 0); line-height: 1.5;=
 }</style></head><body>=0A<div><span></span>Hi Paolo=EF=BC=8C</div><div><b=
r></div><div>Thank you for you opinion. The extended and large communities=
 will be considered after the adoption and according to the working group =
consensus.</div><div><br></div><div>Please see the appendix &nbsp;in the d=
raft for the example. bgpDestinationCommunityList is a basicList of bgpCom=
munity.</div><div><br></div><div>If you don't like the BGP communities acc=
ording to the source IP of a specific flow, you can indicate it in the tem=
plete, i.e. do not specify bgpSourceCommunityList IE in the templete set. =
Then the exporter will not export the information.&nbsp;</div><div><br></d=
iv><div>bgpSourceCommunityList does have values in some network environmen=
ts. For example, &nbsp;the overalll network of China Mobile consists of a =
backbone network and several province networks. Each component network is =
configured with a few communities. BGP anounces those communities among th=
e component networks. When one province wants to know where (i.e. from whi=
ch provinces) its incoming traffic comes from, it can use&nbsp;<span style=
=3D"font-size: 10.5pt; line-height: 1.5; background-color: window;">bgpSou=
rceCommunityList.</span></div>=0A<div><br></div><div>Best Regards,<br>Zhen=
qiang</div><hr style=3D"width: 210px; height: 1px;" color=3D"#b5c4df" size=
=3D"1" align=3D"left">=0A<div><span><div style=3D"MARGIN: 10px; FONT-FAMIL=
Y: verdana; FONT-SIZE: 10pt"><div>lizhenqiang@chinamobile.com</div></div><=
/span></div>=0A<blockquote style=3D"margin-top: 0px; margin-bottom: 0px; m=
argin-left: 0.5em;"><div>&nbsp;</div><div style=3D"border:none;border-top:=
solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><div style=3D"PADDING-RIGHT=
: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000=
; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px"><div><b>From=
:</b>&nbsp;<a href=3D"mailto:paolo@ntt.net">Paolo Lucente</a></div><div><b=
>Date:</b>&nbsp;2017-02-17&nbsp;06:52</div><div><b>To:</b>&nbsp;<a href=3D=
"mailto:lizhenqiang@chinamobile.com">lizhenqiang</a></div><div><b>CC:</b>&=
nbsp;<a href=3D"mailto:zhoutianran@huawei.com">zhoutianran</a>; <a href=3D=
"mailto:opsawg@ietf.org">opsawg</a>; <a href=3D"mailto:opsawg-chairs@ietf.=
org">opsawg-chairs</a>; <a href=3D"mailto:grow@ietf.org">grow</a>; <a href=
=3D"mailto:ipfix@ietf.org">ipfix@ietf.org</a></div><div><b>Subject:</b>&nb=
sp;Re: [GROW] [OPSAWG] WG adoption poll for draft-li-opsawg-ipfix-bgp-comm=
unity-02</div></div></div><div><div>&nbsp;</div>=0A<div>Hi,</div>=0A<div>&=
nbsp;</div>=0A<div>I support Ignas comment with regards to Extended and La=
rge communities.</div>=0A<div>&nbsp;</div>=0A<div>Can you make evident the=
 role, ie. via an example, of the bgpCommunity</div>=0A<div>IE compared to=
 the one of bgpDestinationCommunityList?</div>=0A<div>&nbsp;</div>=0A<div>=
Also, i'm puzzled by the presence of bgpSourceCommunityList: i see that</d=
iv>=0A<div>in "1. Introduction" you kind of close that up saying that ther=
e is a</div>=0A<div>Mediator that would take care of the correlation - und=
erstandable but</div>=0A<div>then again we all know with a (loosely determ=
ined) level of indirection</div>=0A<div>any problem can be addressed; sinc=
e you also say the draft comes "comes</div>=0A<div>from the field network"=
, i was wondering whether you were subtending to</div>=0A<div>reverse BGP =
lookups to make this work in practice. In which case, i'd</div>=0A<div>say=
 warning flag: BGP lookups against the source IP address/prefix of a</div>=
=0A<div>flow would be of no general applicability at all - think, for exam=
ple,</div>=0A<div>to the common case of an ISP (remotely) connected to an =
IXP where you</div>=0A<div>have N BGP peers and hence potentially multiple=
 advertisements per</div>=0A<div>prefix, which one you pick for correlatio=
n would not be a deterministic</div>=0A<div>exercise.</div>=0A<div>&nbsp;<=
/div>=0A<div>Paolo</div>=0A<div>&nbsp;</div>=0A<div>&nbsp;</div>=0A<div>&g=
t; On 16 Feb 2017, at 04:15, lizhenqiang@chinamobile.com wrote:</div>=0A<d=
iv>&gt; </div>=0A<div>&gt; Dear Ignas,</div>=0A<div>&gt; </div>=0A<div>&gt=
; Thank you very much for your support and suggestion.</div>=0A<div>&gt; <=
/div>=0A<div>&gt; Since the problem to be solved in this draft comes from =
the field network, we only provide the method to carry standard BGP commmu=
nities in IPFIX. Extended communities are ususlly used for other purposes =
than standard communities, such as route target, actions for BGP flowspec =
etc. Whether or not we really need to cover entended communities, I want t=
o see more comments. Large communities are relavitely new. RFC8092 was pub=
lished recentlly.&nbsp; Anyway, however, it is easy for us to cover both e=
xtended communities [RFC4360] and large communities [RFC8092] after the ad=
option and further comment consensus. Text contribution is welcome. By the=
 way, I want to know the opinions about the wide communities. Do we need t=
o cover them together?</div>=0A<div>&gt; </div>=0A<div>&gt; As you said, t=
his draft was a good start. It has value to be a working group item. We ca=
n continue the comments and discussion after the adoption and we will impr=
ove the document according to the consensus. Operational considerations wi=
ll be covered in the next version.</div>=0A<div>&gt; </div>=0A<div>&gt; Be=
st Regards,</div>=0A<div>&gt; Zhenqiang Li</div>=0A<div>&gt; China Mobile<=
/div>=0A<div>&gt;&nbsp; </div>=0A<div>&gt; -----Original Message-----</div=
>=0A<div>&gt; From: GROW [mailto:grow-bounces@ietf.org] On Behalf Of Ignas=
 Bagdonas</div>=0A<div>&gt; Sent: Tuesday, February 14, 2017 9:46 PM</div>=
=0A<div>&gt; To: Tianran Zhou &lt;zhoutianran@huawei.com&gt;</div>=0A<div>=
&gt; Cc: opsawg@ietf.org; opsawg-chairs@ietf.org; grow@ietf.org grow@ietf.=
org &lt;grow@ietf.org&gt;</div>=0A<div>&gt; Subject: Re: [GROW] [OPSAWG] W=
G adoption poll for draft-li-opsawg-ipfix-bgp-community-02</div>=0A<div>&g=
t;&nbsp; </div>=0A<div>&gt; Hi there,</div>=0A<div>&gt;&nbsp; </div>=0A<di=
v>&gt; [Copying GROW WG as this might be relevant to their coverage areas]=
</div>=0A<div>&gt;&nbsp; </div>=0A<div>&gt; The document seems to be a goo=
d start but covers only standard communities. This is not sufficient given=
 the universal deployment of 4 octet ASNs. Both extended communities [RFC4=
360] and large communities [RFC8092] are needed and are used to address th=
e signalling requirements for AS4 ASNs. Having separate documents each add=
ressing only a specific type of community does not seem practical and rati=
onal. The document should include the definitions for IEs covering extende=
d and large communities.</div>=0A<div>&gt;&nbsp; </div>=0A<div>&gt; What i=
s the logic of selecting multiple communities for export that a prefix may=
 have been decorated with? Is it all of them all the time? The upper limit=
 may be reaching 16000 standard communities per prefix - would that fit in=
to resulting IPFIX IE? If there is a limit, how does it work? Is there any=
 interpretation done on the values of the communities (all types, not just=
 standard ones)? Those all are operational considerations aspects and shou=
ld be covered in the document, appendix A likely could be a good place for=
 it.</div>=0A<div>&gt;&nbsp; </div>=0A<div>&gt; Security considerations on=
 the privacy aspects would to be covered.</div>=0A<div>&gt;&nbsp; </div>=
=0A<div>&gt; Ignas</div>=0A<div>&gt;&nbsp; </div>=0A<div>&gt;&nbsp; </div>=
=0A<div>&gt;&nbsp; </div>=0A<div>&gt;&nbsp; </div>=0A<div>&gt; On 13/02/20=
17 03:36, Tianran Zhou wrote:</div>=0A<div>&gt; &gt; Dear OPSAWG,</div>=0A=
<div>&gt; &gt;</div>=0A<div>&gt; &gt; In Seoul, we got enough interest and=
 positive response on this IPFIX IE extension draft.</div>=0A<div>&gt; &gt=
; By the authors' request, this email starts a formal poll. The chairs wou=
ld like to know if the WG participants agree that the following document s=
hould be adopted as a WG document in OPSAWG.</div>=0A<div>&gt; &gt;</div>=
=0A<div>&gt; &gt; Export BGP community information in IP Flow Information =
Export (IPFIX)</div>=0A<div>&gt; &gt; https://tools.ietf.org/html/draft-li=
-opsawg-ipfix-bgp-community-02</div>=0A<div>&gt; &gt;</div>=0A<div>&gt; &g=
t; The adoption poll will take two weeks. Please let us know your opinion =
by Feb 27. It would also be good to hear who is willing to review and/or i=
mplement or deploy the extension described in the document.</div>=0A<div>&=
gt; &gt;</div>=0A<div>&gt; &gt; Since we already found that the majority o=
f the f2f participants at our IETF97 session like this idea, please do spe=
ak up now if you do not agree or have serious objections (with explanation=
 of course).</div>=0A<div>&gt; &gt;</div>=0A<div>&gt; &gt; Regards,</div>=
=0A<div>&gt; &gt; Tianran</div>=0A<div>&gt; &gt;</div>=0A<div>&gt; &gt; __=
_____________________________________________</div>=0A<div>&gt; &gt; OPSAW=
G mailing list</div>=0A<div>&gt; &gt; OPSAWG@ietf.org</div>=0A<div>&gt; &g=
t; https://www.ietf.org/mailman/listinfo/opsawg</div>=0A<div>&gt;&nbsp; </=
div>=0A<div>&gt; _______________________________________________</div>=0A<=
div>&gt; GROW mailing list</div>=0A<div>&gt; GROW@ietf.org</div>=0A<div>&g=
t; https://www.ietf.org/mailman/listinfo/grow</div>=0A<div>&gt; __________=
_____________________________________</div>=0A<div>&gt; GROW mailing list<=
/div>=0A<div>&gt; GROW@ietf.org</div>=0A<div>&gt; https://www.ietf.org/mai=
lman/listinfo/grow</div>=0A<div>&nbsp;</div>=0A<div>&nbsp;</div>=0A</div><=
/blockquote>=0A</body></html>
------=_001_NextPart511787134451_=------



