IETF Logo Mail Archive

[Idr] question about BGP extended community

li zhenqiang <li_zhenqiang@hotmail.com> Fri, 14 April 2017 09:16 UTC

Return-Path: <li_zhenqiang@hotmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2906128768 for <idr@ietfa.amsl.com>; Fri, 14 Apr 2017 02:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.286
X-Spam-Level:
X-Spam-Status: No, score=0.286 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 zBwXzxIw8aDy for <idr@ietfa.amsl.com>; Fri, 14 Apr 2017 02:16:56 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253085.outbound.protection.outlook.com [40.92.253.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2163127A90 for <idr@ietf.org>; Fri, 14 Apr 2017 02:16:55 -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=CV+KomEhsQZet8sNXFs49Za4A5SSes0QZ2C1L4AHiTw=; b=vG5j+HW3YFLfWETWhV1UxcsLbGe2+VVm1Pi1azH/0E/uxY7TJmLzl1Pb8kGxVAc+kzwZLPj+iboZ877NArSW2aaOuImR2tGzaOSPugPtqC89INhWKHntuZTIe6+nAmP+Iy8eXwCTjPfLoOlrv63uCUNSQHUwS6Nm49pdViq0fHg/55VcJBBhluH+QkG1/CqIV0YfYDIZRXKdCYAc1COrOk2bPzb9TlIqsYxKESyBZL5jET3pyw11rArlJj11MGi1stm/Tv2jXeIKzdIdOuWjwMe3sKby1Q0usGYUA1uFBBFi/1ZylxMdE01B96UUWhUh/c6gR+R0U8Bljue7J2MCfw==
Received: from PU1APC01FT042.eop-APC01.prod.protection.outlook.com (10.152.252.53) by PU1APC01HT040.eop-APC01.prod.protection.outlook.com (10.152.253.247) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Fri, 14 Apr 2017 09:16:52 +0000
Received: from HK2PR0601MB1361.apcprd06.prod.outlook.com (10.152.252.52) by PU1APC01FT042.mail.protection.outlook.com (10.152.253.96) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Fri, 14 Apr 2017 09:16:52 +0000
Received: from HK2PR0601MB1361.apcprd06.prod.outlook.com ([10.165.182.19]) by HK2PR0601MB1361.apcprd06.prod.outlook.com ([10.165.182.19]) with mapi id 15.01.1019.028; Fri, 14 Apr 2017 09:16:51 +0000
From: li zhenqiang <li_zhenqiang@hotmail.com>
To: idr <idr@ietf.org>
CC: rv <rv@NIC.DTAG.DE>, wangruixue <wangruixue@chinamobile.com>, Zhuangshunwan <zhuangshunwan@huawei.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
Thread-Topic: question about BGP extended community
Thread-Index: AQHStP/aKV88viQwok+b5ZwWc2ZVkA==
Date: Fri, 14 Apr 2017 09:16:51 +0000
Message-ID: <HK2PR0601MB1361C0B1786C4C68CCC05762FC050@HK2PR0601MB1361.apcprd06.prod.outlook.com>
Accept-Language: zh-CN, 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=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:7A2638D58849EBF53E5646608948A7D29383C32ABCB3B15C1103F3C8991CAA7D; UpperCasedChecksum:302DA298D6C9027593AA73513621C87FCAE5D91AD6B6EF2E3B37EA9C62C2A3F2; SizeAsReceived:7840; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; PU1APC01HT040; 5:XvhKbxhXI9t28XuACx0NhSZsLfBqSQkkl13uuEStHlIAQQtz+gQdj/ENVO2qS6G2QUyP01wzCIyjLAhI3wl/UqbFpPFuvgSVvTcQNis++5440tHrCo0BI87TLNAA9E0S383Sz9MOjewnBzXlIHCBzg==; 24:74U5cnvbu7KIkHqaTkKEurSTWCi6MMULZ0Yb04SPUCnYmWhz9oKb7lPWNVVcr6dwy2MedKmv5QWT82icHz71JCETuJkoc+jGkLahrxP6DVQ=; 7:Vdx6QdSzcEPlam2+qUSGTmOfaWKnHRicvNiS7bd8fmCJ9NNe0CCeSiayb0ZTLNU65vTu85XLpcYAqCoP7+dYHbG4RgWII/CYIvi1twFZvJLpivDoxdlO7lnjSrgB0ciZukHcPeyE4HEOhcGBqmZsKNRxagI7CobZKjcj2AL3R51mFQZh8gOWlKkxu3WMbGML1K3EUhxYzMIywtfobapUGdlCYoiTYkgGWaiX7XXh+qYwLC8deUT12jA+zZI5WCjVQEWEy84XpksxWjiQjXSahO0IV01gXB2JeBxyCiTn1KDQ8U/WUFMmbrS8N3KbxdQW
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:PU1APC01HT040; H:HK2PR0601MB1361.apcprd06.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: 5591e726-5b4c-4cfb-b607-08d48316fa69
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:PU1APC01HT040;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:PU1APC01HT040; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT040;
x-forefront-prvs: 02778BF158
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HK2PR0601MB1361C0B1786C4C68CCC05762FC050HK2PR0601MB1361_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Apr 2017 09:16:51.7303 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT040
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/sOG-69WQxGRFgG-C2pQYJfCvMc8>
Subject: [Idr] question about BGP extended community
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 09:16:58 -0000

Hi all,

As per RFC4360, BGP extended community is a transitive optional attribute and RFC4271 specifies it is not required or expected that all BGP implementations support all optional attributes.  If we do want the BGP peer supports some kinds of extended communities, how to determine this? Check all the peers in advance? MPLS level 3 VPN, for example, uses the extended community to carry route target information, all the relevant BGP peers should support the RT extended community, but we can not expect this according to RFC4360 and RFC4271. The traffic action extended community as defined in RFC5575 (BGP flowspec) and updated in https://datatracker.ietf.org/doc/draft-li-idr-flowspec-populate-to-fib/<file:///C:/Users/cmcc/AppData/Roaming/Foxmail7/Temp-9608-20170414150941/%C2%A0https://datatracker.ietf.org/doc/draft-li-idr-flowspec-populate-to-fib/>, for another example, is expected to be supported by the receiver, which is not guaranteed by the transitive optional attribute. Do we need to do something here? Thank you very much for your help.

Best Regards,
________________________________
li_zhenqiang@hotmail.com

v2.23.0 | Report a Bug | By Email