Re: [IPFIX] [Idr] discussion about exporting BGP community information in IPFIX

li zhenqiang <li_zhenqiang@hotmail.com> Wed, 07 June 2017 09:03 UTC

Return-Path: <li_zhenqiang@hotmail.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 6224512EB25; Wed, 7 Jun 2017 02:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.114
X-Spam-Level:
X-Spam-Status: No, score=-1.114 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 EtZk8ROJ-425; Wed, 7 Jun 2017 02:02:59 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253068.outbound.protection.outlook.com [40.92.253.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB36212EB1B; Wed, 7 Jun 2017 02:02:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nT/3+WtiRMXDnrMITnOgsj6Neq1j/X+WaJZ+0o+XoVs=; b=kUfXTN14UZDNXI6PpoVqxVAPrr985ujyPlYjv2agZ+wBnhan1DrFAWO2epajayYeL19xylYkC2f44Vgm/HDmd7lpod2DlYAQeaUUXWC79yaQdBDG48Am851Kx0+g1WVZDjX6hQITCfQbm3iFxULhXIHs4cmG/EJ9khsbaV6l6VzNFKS3vcbwQzmoTy8Mw+xq12o53vszU3EyznFrqfafeiQuq/fNcBv1cxaDfhlnbSmGV0SciNGiTSGYpONKlir04x/y4DNOis3gzp/1UHD+9leGgfEdLgYqI/g/j37XWZKZ2I163X9nAWMIAo+2Ey74R0EsEXwci/iSz5usIreILw==
Received: from PU1APC01FT028.eop-APC01.prod.protection.outlook.com (10.152.252.53) by PU1APC01HT054.eop-APC01.prod.protection.outlook.com (10.152.253.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1101.12; Wed, 7 Jun 2017 09:02:55 +0000
Received: from HK2PR0601MB1361.apcprd06.prod.outlook.com (10.152.252.53) by PU1APC01FT028.mail.protection.outlook.com (10.152.252.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.11 via Frontend Transport; Wed, 7 Jun 2017 09:02:55 +0000
Received: from HK2PR0601MB1361.apcprd06.prod.outlook.com ([fe80::2115:a445:9d1f:b88b]) by HK2PR0601MB1361.apcprd06.prod.outlook.com ([fe80::2115:a445:9d1f:b88b%14]) with mapi id 15.01.1157.012; Wed, 7 Jun 2017 09:02:55 +0000
From: li zhenqiang <li_zhenqiang@hotmail.com>
To: li zhenqiang <li_zhenqiang@hotmail.com>, opsawg <opsawg@ietf.org>, idr <idr@ietf.org>, "ipfix@ietf.org" <ipfix@ietf.org>
Thread-Topic: [Idr] discussion about exporting BGP community information in IPFIX
Thread-Index: AQHS0sec79+PG+QhZkiBAviflUwRGQ==
Date: Wed, 7 Jun 2017 09:02:55 +0000
Message-ID: <HK2PR0601MB13614AD1610E2FA97C21A682FCC80@HK2PR0601MB1361.apcprd06.prod.outlook.com>
References: <HK2PR0601MB13617E5EA5828A10E5B3D1A6FCF80@HK2PR0601MB1361.apcprd06.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-slblob-mailprops: /2cIMDU2oIDcIHxUb2SJGGOFsV7jhLDdZFxEjNmBlYAvyWC8eI25TQ1mVBQtHXUSFTWAzroA7T1gdvtD8Kfq0rZkaTMdE6dujFH6KRhTrO8WftdbU+Ex7SXbA6i9QXVIfkxH8drcdkBS9ZXm5Z5UoIN38i7c729mlYRTvVJbc9uPNkzBeNHiOt7gjH7YUE/3KqFG3LQF58FN1JsWgMltyUmiteXdE4ACpa1KbHuBQV9oFKEdHM6iZdVPd/Xyz5VQ3ZIIL1hQmHO/D/ECwNGXEU7oUL6c9sxwIluCGxK0jfGC1GUt//C5OZNNNg077welfLIGNhsGxGVFstg2zKlsOdk3wp+imu4cvNEE0b7QGtQcXMFeIwb/97fYTMicdlv+xzqxXz49y92kHvaeH2VwwwfWf/cZnU9VlGRdQnM1jFAPaoJo+20g5IVG+ID95uyDMK2yzocqAL41epRyS4JnAEHBYh3Hls9UWlsw4sMvh3D0IOjel5ZMxdguPyS874Owj5Ku6oWWWLJXM1qMHo98nsgjBhtg+dKMliehF3wWxFNvyOXlC3i6DWxNThHtM8rkvWZjAdrgB/a22cwYvgrvteIrTK0kc/GsVzMoI8KQBhRkP+tiXPn/TAVaTE66sdU50IFcBOjQ8Oea6f5veDvMzx2Uko4GfMQ2z+jlZOwY7k81I3/MeE+TM/Jnk6Sv71k+TmLRVAeDxYNnJ+tgL+IDodxjZpj72zITgKF7FljohG1YSoko/00ubwiqI6cpM5q6rHi4IC0RMkgD0giOKK6pZ96BByxoKLmrMhY0NXh6iz76ibbRwACXoZcG9vePL6GX+Ah1zBLfBkMw8LRsVA5tAm2VbDQDMnEtMK8iGDC9KxdcF/rMfIH/Ri7fs0RSwmui0yrEuX7+s6veiOw++H3pxBvhIUdTlk4wsbGgvNR0suuCIRo5rpgIPyP2z6tFeB1lRasbSYNFuPU=
authentication-results: hotmail.com; dkim=none (message not signed) header.d=none;hotmail.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:B8670E88EA8FC250CFFBB5E8E0C05AFB392F1D2E52A17847340D4A32A915C2F1; UpperCasedChecksum:C915819449F8DE6326B1E55C96CBD6F140EE035E5DF28A215879AFD7AFF0F09E; SizeAsReceived:9346; Count:45
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [fmm1+/gNH2+ijUfgm54O66lfGcWrbUH+]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT054; 24:H+/8nBI7D3i/LABukTx4zMB5t4/sGNs5KMv8DXsB+0XgvkZ7Q9kvJoTQP1KxTAI2Jy1xJs7tsgaa9skjqrfn1NUWuqBl4yKa4UG1Z5vTvTM=; 7:CeZwu6SV4s1FdO/OsoMM/DqWe2pcfoPGnMtM6DZxC9XaExQ2mAwWNFMO14NQEESIExD+nSrLmDd2O3bdj5Z5+/IjxCgJYLp7IfclzxkWvtWBbVM1PUODjKd57vevPRBpNkj3dM8koyd5BXc/O5sQ2YOXNXnp62vE+6vjmYvMp8X60a1ELc3lOO5aiA8n0vAujZuA/+yiBqApd/Q+LGkdTJ7v2ok5ZU69iEX9zZeC+9qJnsMl1PaMB4sGwCXUxVd98wQyNdLR2bjpKa8xzuKjxNMv5Z1kgr5qfibCdofjPtBwX3rsTrzYctl9CYbRuL61
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:PU1APC01HT054; H:HK2PR0601MB1361.apcprd06.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-traffictypediagnostic: PU1APC01HT054:
x-ms-office365-filtering-correlation-id: 57b304dc-c778-41e4-1487-08d4ad83f988
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(201702181274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:PU1APC01HT054;
x-ms-exchange-slblob-mailprops: ZJ4yP2VsLUPvaqQMme6J7o+6yf4+VswJSrrFXU8+pvi4tI3Jb0FeLxL7vcZ5pz83R8P38q7VU8KnDcuL+m/ceq8Y86o6+uNc+GaehCnSfCreJKd/bS1Qp5T9oVERAzcnCrJmXilNL+HllO/VWSbyLh4m4kR61SENzw+eB8NP1/c1eh4CfH981WH/OdE1KApCpufzQa2tYbhAKb10BafhFv3woy4T0TyAkuMYTQ2bMxltNMEQ/nz5hEZN3FBrc4BPRZ4XC1+lK0dqFkQksGyERemJx+vJdyV4JXtm3tUIBlAJ4XfepT/WITcnljD78cTD2rI4dmFYx1tQwJwYvE9M8IE2NFilnDejMZ6Bq8zxR6xzuc3H3piL+RDW8rd7i1VJLG99MjTrlswSYeN10AJQPCnyUGMEM8QZg6F3+Y0Be24oRJil4Eb90LTa5S99GUnmDUu+POqpsvIu43UxV/jc4OVzYhT3l6Jl8sBcwEh5/Rrd/n/W7FK7vhviCtGjgb++HbNz99Cu19m/FM39hTZgso8/ikw4zAO6T1sLCPIbVWbi/swvLY3zqVaEPmt0A1OTvyFiBI3OzIzLMf16i4Zs8OcyiiimYY2MDxeTEb6LgYL86nvyBBhYdtFA3YYaBs16qtziqFXZ5t3ArI5/XtJOnW2IBNt5EiHbwKwVKKBrdp+yRLm6efbh3KJaMHk0GeDDPvamh9HScA2pLSXFZc8rBXEg+UBfv8ANTJPLkjk7tqJqoTnOpw7e8+xTpjSLWLbQtav5YdMdMKdCaNyMNtEjIDlEacwqS79wqu41cjXpqCL2kZF6v0NsEGlIZ1VhxO3O+8sPbgeKOLWD6D7qcDNsmJBlgrZAxnoG+SFn0F7d1Arz/+64db9tg4X3z+qUCYeFOho07q+1HRZUSbZ/lfGhK66+Qn/n3bH18sijDW1NrY5XrfhI1cmwJOVlCW6HoGGg
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:PU1APC01HT054; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PU1APC01HT054;
x-forefront-prvs: 03319F6FEF
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HK2PR0601MB13614AD1610E2FA97C21A682FCC80HK2PR0601MB1361_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2017 09:02:55.0943 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT054
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/iS-SN5-LDw-7Jypv5ZSNZmAqAdU>
Subject: Re: [IPFIX] [Idr] discussion about exporting BGP community information in IPFIX
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 07 Jun 2017 09:03:01 -0000

about question 1, the message length.
A WG draft, https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-extended-messages/, extends the maximum update message size of BGP beyond 4096 bytes to 65535 bytes. So, one IPFIX message may not be sufficient to fit all the communities related to a specific flow. BGP speakers that support the extended message feature SHOULD take care to handle the IPFIX message properly, such as only convey as many communities as possible in the IPFIX message. The collector that receives an IPFIX message with maximum length and BGP communities contained in its data set SHOULD be aware of the BGP communities may be truncated due to limited message space. In this case, it is RECOMMENDED to configure export policy on the exporter to limit the BGP communities to be exported, to export only some specific communities, for example, or not to export some communities.

To solve this problem completely, we should update IPFIX Protocol Specification RFC7011 to support message splitting.

Your comments are appreciated.

________________________________
li_zhenqiang@hotmail.com

From: li zhenqiang<mailto:li_zhenqiang@hotmail.com>
Date: 2017-05-22 14:49
To: opsawg<mailto:opsawg@ietf.org>; idr<mailto:idr@ietf.org>; ipfix@ietf.org<mailto:ipfix@ietf.org>
Subject: [Idr] discussion about exporting BGP community information in IPFIX
Hello experts from OPSAWG, IDR and IPFIX,

This mail is to follow up the discussion in the mail lists and face to face meetings.

Since traffic aggregation in BGP community granularity is useful for several applications such as backbone network traffic engineering, https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-bgp-community/ introduces new information elements(IEs) in IPFIX to export the BGP community information of a specific traffic flow. At present, this draft only defines the IEs for standard community specified in RFC1997. To solve the following two significant questions raised in the previous meetings and mails, I solicit more comments and solution alternatives.

Question 1: Does one IPFIX message  have enough space to fit all the communities related to a specific flow?
BGP community, including standard, extended, large and community container, is a path  attribute of BGP distributed in an update message. Since the maximum length of one BGP message is 4096  bytes as per RFC4271 and 64K bytes for one IPFIX message as per RFC7011, the answer for this question SHOULD be yes. Howerer, some experts say the specification for BGP message lenth in RFC4271  is out of date. Its length is not limited to 4096 bytes. But I do not know the new specification. Solution alternatives for this question are also welcomed.

Question 2: Do we need to cover other kinds of BGP communities, such as extended, large and community container?
Based on previous discussion, large community defined in RFC8092 will be covered in the next version, since it has the same application purpose as standard community. Till now, we do not reach consensus about extended community defined in RFC4360 and community container defined in https://datatracker.ietf.org/doc/draft-ietf-idr-wide-bgp-communities/. We usually do not use the statistical information based on extended community or community container to do traffic engineering tasks. If you think it is useful to export these two kinds of BGP community informaiton in IPFIX, please show your opinions and application use cases.

Thank you all very much and best regards,

________________________________
li_zhenqiang@hotmail.com