IETF Logo Mail Archive

Re: [Idr] Question about BGP Large Communities

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Tue, 04 February 2020 20:45 UTC

Return-Path: <jheitz@cisco.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 368F3120152; Tue, 4 Feb 2020 12:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.488
X-Spam-Level:
X-Spam-Status: No, score=-14.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, BODY_ENHANCEMENT=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=R+uNP7wU; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QkISP9sJ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocV3cBXkqJRe; Tue, 4 Feb 2020 12:45:46 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A5D812011A; Tue, 4 Feb 2020 12:45:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24754; q=dns/txt; s=iport; t=1580849145; x=1582058745; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=w3bXyPOzk7bG/slkkNM1lEcM66eTFE4uP/fYEOvJ2+g=; b=R+uNP7wUuvL3lAoYPnMB7wBWPKojr2kWSJxFEpBJX0caiRyQli0nW7l/ /4+Z+JWJ7NvorVearaYVxPcpjuLyvzleBrGmoU2vsM54wVMDbAo7DhuZi hBSM36R3q9/48dZIKz9eMHAmuEjxSyNT65838qf9CVOQ5fLK9hrSVcxHm M=;
X-Files: draft-heitz-idr-wklc-00.txt : 8102
X-IPAS-Result: A0BMAABM1zle/5pdJa1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYFqAgEBAQELAYEkLyQFJwVsWCAECyoKh1ADiwGCX4lhiUyEYoFCgRADVAIHAQEBDAEBJQgCAQGBTIJ0AoI3JDcGDgIDAQEBAwIDAQEBAQQBAQECAQUEbYU3DIVmAQEBAQMSGxMBATIFAQ8CAQgRBAEBLwIfER0IAQEEAQkEBQgGBgcHgwUqAYIfAy4BDqIlAoE5iGKCJ4J/AQEFgTMCg2MNC4IFBwMGgTgBjCEagUE/gRFHgkw+ghtJAQEDgSUIARIBIxUWgxWCLI1QEoI6hhyBEohnjnJECoI7g2yCOYEkiXRchEWCSDCHXoRIigSBZo5hgUuHHIIokAsCBAIEBQIOAQEFgWgjZ3FwFTuCbFAYDY4dB4NshRSFP3QCMHeKYQUMF4ELAYEPAQE
IronPort-PHdr: 9a23:nWMMiBQw3bgZBUtdUTgpe94vp9psv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUDNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOi46EcVeRndu/mqwNg5eH8OtLwSI8Ge/5jMTBBjzcBFtKLSpSKjVicn/l/io/IHeaBlJgzz7Zq5uKBKxrkPascxEyYBjMa02jBDOpzNEfOlNjWVvORqfkg396cG54JMGkWxItugk9tJcXKmyZKk+QbFCRDQhKHwupcA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.70,403,1574121600"; d="txt'?scan'208,217";a="406697543"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Feb 2020 20:45:44 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 014Kji8E002742 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 4 Feb 2020 20:45:44 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 4 Feb 2020 14:45:43 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 4 Feb 2020 14:45:43 -0600
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 4 Feb 2020 14:45:43 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=f+jdDFS6uVDo+ciVQtyaclcQiaygK1s8eQJGQlKKTKOYRp7N48fGXwuqegF3tyypkzicQkV3CPFG2gOJSOi8ZA7rFRa87sLvwLhAf+j6T3qoOvy6VlUnuUoDcHSvsjurGrO6ZfdOhVvj/ljHmhWFDvxEe693rk7vPOBG+2NNDUECCpnZxjXsCYbHrDgzv5HLeSTHwBlo5NHxXCz1Lo9MF6268aDak7GWx8o1Rf+FSrcy1f6vWO7/wP/RJbid9LOeeHhlFMBbwZe5ejSS621iNhEStP7uUMPb3gFcXL8SIeg2xxuyv3n9VXsad2KBXbUKAVbg4mW4WzMhkSN/JNO4zw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bzPzlOIer4ABXXn0OamNoshU84Yk6Vnuo9NdpjNNwFI=; b=SgYVNB0vN+iRSdRJSAxgAQF8IubRpEyVIPvMsyIMB74BgEMP9Wx6nAz7LHFpeyevcG5oztL3sfx8UpE4ZVZsLJUAEHJVp4mZtMzHPMDni3SxbSkD9ifD5ywDyj7eHioZyrfzCTC/CEWHMDpoGeANmQgQWT4PJAs3YaLpIbhAVs1xdsxL0ZFVxNW1Iof59qr770WxMDDsFrCsuSVTzKILAt5O7GbSY1I6bKbtK7wiJh1jgidUphDSkl7XE+kZFnxmtxNiPxZ+yWvJJiReUVYXi+X0Z6aN0duB18np14aZ598wNcgJl7bhkhezDe1nU2cGM7ULIYqkxcxQ+L66RUHyeQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bzPzlOIer4ABXXn0OamNoshU84Yk6Vnuo9NdpjNNwFI=; b=QkISP9sJEVfpC53ulnUXK1P26GD1bafvH4RVhBLHA5IqBOex9Y8j6Bg1kt46UZeaqjEOWV4rWvyR/thPMCZpikhBVWrUT1KPaSLGPIo4fQ8lR9WTcqHxCB/zSheCimejiBzy7Z2uaMKWhpbkB09Avh1eyBmxAGUDyVfv/VpoHs0=
Received: from BN6PR11MB1890.namprd11.prod.outlook.com (10.175.101.13) by BN6PR11MB4019.namprd11.prod.outlook.com (10.255.128.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.29; Tue, 4 Feb 2020 20:45:41 +0000
Received: from BN6PR11MB1890.namprd11.prod.outlook.com ([fe80::249a:1b6:689d:3fcf]) by BN6PR11MB1890.namprd11.prod.outlook.com ([fe80::249a:1b6:689d:3fcf%5]) with mapi id 15.20.2686.030; Tue, 4 Feb 2020 20:45:41 +0000
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, Job Snijders <job@ntt.net>, Nick Hilliard <nick@foobar.org>, John Heasly <heas@shrubbery.net>
CC: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "a.e.azimov@gmail.com" <a.e.azimov@gmail.com>, Brian Dickson <brian.peter.dickson@gmail.com>
Thread-Topic: Question about BGP Large Communities
Thread-Index: AdXbeNI4t0SppYFnSky8PqLGmuct1gAIu5NA
Date: Tue, 04 Feb 2020 20:45:40 +0000
Message-ID: <BN6PR11MB1890AA431F63030DFE310902C0030@BN6PR11MB1890.namprd11.prod.outlook.com>
References: <DM6PR09MB54489301E52DD711E031400984030@DM6PR09MB5448.namprd09.prod.outlook.com>
In-Reply-To: <DM6PR09MB54489301E52DD711E031400984030@DM6PR09MB5448.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jheitz@cisco.com;
x-originating-ip: [128.107.241.189]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 768f456c-d545-498b-d4d4-08d7a9b332bf
x-ms-traffictypediagnostic: BN6PR11MB4019:
x-microsoft-antispam-prvs: <BN6PR11MB4019D39E207A3133BD670F50C0030@BN6PR11MB4019.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 03030B9493
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(136003)(376002)(396003)(39860400002)(199004)(189003)(86362001)(4326008)(76116006)(7416002)(71200400001)(81166006)(81156014)(8676002)(966005)(478600001)(66616009)(9686003)(55016002)(66946007)(6506007)(53546011)(33656002)(26005)(2906002)(186003)(8936002)(7696005)(316002)(110136005)(54906003)(64756008)(66446008)(52536014)(66556008)(66476007)(5660300002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB4019; H:BN6PR11MB1890.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 1DWj+4SBqhZrOdfRBbfpH4gN680xRW/06Wt9rhgsiZ+dl79VX4QbjuV+sk3233VI3XvQ7AgENWP0pHeCLecTaDCOvKJw7gwSM0O6RqqxVLKwGDoffaUsVJ1QAvwwCAYt6i/X8nek6XXPYzlYCqLg1BAc3YM+C5rHj1dOm3aa3cWW7ubgUKVmsLzblT+5NZqYe/t7WzIagxZEQ9GUmW09VktNS+OIa/EG0lIUSw3iwLPJialJhSHscb7WbcXabDjpGPKRVPqjgHBTu7TqFKZu/8Lr4cfTsK1bGE+IMpcEQgyiqMwb9JByjA3zJQg9UpF0a5lnPY95Dmzun93265RkPamS6fzZ9U/Tm+XeVu/G1U7uYgOdYPD4NntyRAI1AvgpwHpbKEfefw0mWw+m3tS6G0nf0rxT4qM6KH0UnZuxXbgr9c/pUibYqM24LFc5gpk44CRZVvsNTfZMgzhmbUSfbKLrdNN/DPIYI94clJuOZyGRjXxjIGa4RXE2ZOE923mLQq3PbIsIPPMhaGOczYTTxQ==
x-ms-exchange-antispam-messagedata: WnxfSCWD84SPv2R9ZTwXdkPqSVcaQ71OK9QjDOlJwpg9nJyPT/x0sEfnvSL5F39zAErb/SihfXYXD2abVNG/coBUfboukcixMCo64ebHa8E5MZo8ZlDreMqI7x+2ziGVQUOPEIiipFl8AiMYJwCVDA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/mixed; boundary="_004_BN6PR11MB1890AA431F63030DFE310902C0030BN6PR11MB1890namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 768f456c-d545-498b-d4d4-08d7a9b332bf
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Feb 2020 20:45:41.0737 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: whVzcPfNShY9kMO71YyAyIC1xzVLYeMcryL7LamzFNzkF7+vZMVxoX8oAYFZJc71acd6oBJGeUv+FwGbt0xeFQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB4019
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-36sO1TbOt_CtOKtB5Oo5qDuapE>
X-Mailman-Approved-At: Tue, 04 Feb 2020 14:51:03 -0800
Subject: Re: [Idr] Question about BGP Large Communities
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Feb 2020 20:45:49 -0000

A set of well known large communities could be useful.
I have a draft that I never submitted attached to this email.
Does anyone want to co-author and suggest changes?

Regards,
Jakob.

From: Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov>
Sent: Tuesday, February 4, 2020 10:22 AM
To: Jakob Heitz (jheitz) <jheitz@cisco.com>; Job Snijders <job@ntt.net>; Nick Hilliard <nick@foobar.org>; John Heasly <heas@shrubbery.net>
Cc: idr@ietf.org; grow@ietf.org; idr-chairs@ietf.org; grow-chairs@ietf.org; a.e.azimov@gmail.com; Brian Dickson <brian.peter.dickson@gmail.com>
Subject: Question about BGP Large Communities


In the route leaks solution draft,

https://tools.ietf.org/html/draft-ietf-grow-route-leak-detection-mitigation-02

we (the authors) have proposed using BGP Large Community.

We specify this to be a "well-known transitive Large Community".



Question:

Can the draft simply make an IANA request for

a Global Administrator ASN value for Route Leaks Protection (RLP) type

and request that it be published in IANA registry

as a "well-known Transitive Large Community"?



There is no IANA registry for Large Communities yet;

we have requested IDR and GROW Chairs to facilitate that.



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

Details/background:



We've read the following RFCs related to Large Communities:

https://tools.ietf.org/html/rfc8092

https://tools.ietf.org/html/rfc8195



RFC 8195 has this table:

                 +-------------------------------+-------------------------+

                 |       RFC8092                    | RFC 8195                |

                 +-------------------------------+--------------------------+

                 | Global Administrator    |      ASN                     |

                 |  Local Data Part 1           |    Function              |

                 |  Local Data Part 2           |   Parameter            |

                 +--------------------------------+-------------------------+

which is instructive. In the examples that RFC 8195 offers,

it appears it is *assumed* that the Large Communities are transitive.



For comparison, in Extended Communities (RFC 7153), there are

explicit Type values assigned for Transitive, Non-transitive, etc.

https://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml

However, there is no such explicit Type specification

for Large Communities (in RFC 8092 or elsewhere).



Thank you.

Sriram

v2.23.0 | Report a Bug | By Email