Re: [Idr] Question about BGP Large Communities

"Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov> Wed, 05 February 2020 01:28 UTC

Return-Path: <kotikalapudi.sriram@nist.gov>
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 28F68120072; Tue, 4 Feb 2020 17:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, BODY_ENHANCEMENT=0.001, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nist.gov
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 nB6-Tfet79hW; Tue, 4 Feb 2020 17:28:43 -0800 (PST)
Received: from GCC02-DM3-obe.outbound.protection.outlook.com (mail-dm3gcc02on2095.outbound.protection.outlook.com [40.107.91.95]) (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 6848A120058; Tue, 4 Feb 2020 17:28:43 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B4JzgHOTMOTsn5A+5siBZhwEXJPgT+9nuQ3SSHbuyli/bIWTrToB06TQW3pjNRebB6cTc2ZfezqXB5nyUxbvMeJDMJRaUlaiXkjiiV6TntGrvEWzF+oUreUN0TiHMQhpRaKlum2a5EMqLBuyhFxkxvK61/Yh7GarEbBdD3vfR1dY2XJd3+em72tIC4qjsKO9nejSY7bc0D73P3ohh0DDprMG5l2shcuOq1Pb3UIZaizr26GlDt84bBky8ggeUy9ZR+b4ChYHMkI1SRAd+xnK/PuRN9pTYU26xq3cNgXnS8klftrXvKRfdKwWz6TCnoHXJM02JDX4Y/bi3F/PFz6hig==
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=U3gWDpkKF4JSuewHAJFRgwkyBSNWDSQOTiCLX9YfmII=; b=UhkHKjA7zhM1qysvSIWUDeV86Zxn4C04RBA6sFtYDNEIbOCzk9oGIIhGI8pqC362wOFlOIER/QElAPZtdNx5SpOv2/vE6eJWWlQibSATy7YCg5xMnm0F3f/2vJVXIzhfKKdKmwopKm2kcXeVFVGt5f7dvSH7K4MxVt4gwqR0weu+zbxNP2B3WT3zMgQTlQy1gluNpqQsO31jEEwNW+KmR4R5zXSYw7Pk3HcLrYQSZDufLbCOrVdhUs5IVgpBVCqJZ/Nt1nJXoytqHdOhprRMPIDGc/nWUesgDK4ompFbjFrZtsZ5BtSzCOA6bfCg8C4QSWQ5bpG6hXlB9zf0Py0zPw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nist.gov; dmarc=pass action=none header.from=nist.gov; dkim=pass header.d=nist.gov; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nist.gov; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=U3gWDpkKF4JSuewHAJFRgwkyBSNWDSQOTiCLX9YfmII=; b=bxvkRCTMRE8Ox2pyreCXtyyD76/mQuPZy3gDcC5MWpPZ3EGBQJ75Gb+2B5Kesh3kS/Qj5vxZkHbAogCI42aQl4U8dEXpe19H/eNcS/ff5U3zQL0wHGFGgOYIkJerwMDzJNmeZBlkKh8LYDt8C9AGhKn+A8mckJ9j/KgzqaOc5Ik=
Received: from DM6PR09MB5448.namprd09.prod.outlook.com (20.180.61.9) by DM6PR09MB4191.namprd09.prod.outlook.com (20.179.167.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21; Wed, 5 Feb 2020 01:28:41 +0000
Received: from DM6PR09MB5448.namprd09.prod.outlook.com ([fe80::6430:ee45:4fc4:f468]) by DM6PR09MB5448.namprd09.prod.outlook.com ([fe80::6430:ee45:4fc4:f468%6]) with mapi id 15.20.2707.020; Wed, 5 Feb 2020 01:28:41 +0000
From: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
To: John Heasly <heas@shrubbery.net>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>
CC: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: Question about BGP Large Communities
Thread-Index: AdXbeNI4t0SppYFnSky8PqLGmuct1gAIu5NAAASXzAAAA08B8A==
Date: Wed, 5 Feb 2020 01:28:41 +0000
Message-ID: <DM6PR09MB544817A892B1F331E972DF9384020@DM6PR09MB5448.namprd09.prod.outlook.com>
References: <DM6PR09MB54489301E52DD711E031400984030@DM6PR09MB5448.namprd09.prod.outlook.com> <BN6PR11MB1890AA431F63030DFE310902C0030@BN6PR11MB1890.namprd11.prod.outlook.com> <20200204225458.GB57481@shrubbery.net>
In-Reply-To: <20200204225458.GB57481@shrubbery.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kotikalapudi.sriram@nist.gov;
x-originating-ip: [129.6.140.161]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: ce750baa-21e7-480d-566b-08d7a9dabbe6
x-ms-traffictypediagnostic: DM6PR09MB4191:
x-microsoft-antispam-prvs: <DM6PR09MB41913A57E62072C7B350C81E84020@DM6PR09MB4191.namprd09.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0304E36CA3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(396003)(39860400002)(366004)(136003)(199004)(189003)(186003)(86362001)(81166006)(5660300002)(81156014)(8676002)(8936002)(66946007)(66556008)(316002)(54906003)(66476007)(9686003)(110136005)(66446008)(64756008)(53546011)(6506007)(33656002)(4326008)(26005)(52536014)(76116006)(55016002)(2906002)(7696005)(71200400001)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR09MB4191; H:DM6PR09MB5448.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5YtHMeFA6u0jv+YJVwOhZFj1SfjTP2uX8RL9AvMMUS4aetJndRUbIyP2SX+4DVrFAhWejTWSU85/kfJjDe3H6aKPEGgI3Djpz5NjZ+29YQWKhWNWtukTm1zc/M6wAyzKQhKqStM4iazpCVvcAD8qofc8p4keGrw45qALo0C0ivjuWOQvW/WGgrFd7QHKxnyt9Uz02RbuSqL9uLmPjR6nRYESnCO/PZNK+MYM1z9MJoUvZ2cZycB3H1ayQBqzyclMp29CaKJqvRfveytwztiv91T2wuH9VYODxjfEIC1ztUIIrBz6SUk3fdTdaoqtkOy9bADWxT8WCzdH40kyrCYABJXbC9b6d9WewBw9wtOsX0qROJkIGT/j0yLxUiVmwoJaRCnukGZFHFuzCDQfM+MrXp/V3sW+0jM6+Hj3Cr00hCgmfKVIWqyeDkGkG25wW3E5
x-ms-exchange-antispam-messagedata: IasWMK31R02JCiRFJWmusKTUnQda7CnPnTBp4AC/yFtSA1MicSkysZ5RRGB65mvSlhbmkWOEzFUyVtMFfzAb5DeNKT7TWRHV1gxpfkKQ1m2VNS8/s2yGKoTE1BrYirAWiFXQEzdT5HQNBkwuyk8O0A==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-Network-Message-Id: ce750baa-21e7-480d-566b-08d7a9dabbe6
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2020 01:28:41.5469 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qB1dQquXhrGOU+bjjHUD48qgZGBmBaBKO6jcRggXzsJf52lyjKB1A9m9Dp2UW6sf1FhLbqz5p5/VU8P/JMpCsA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR09MB4191
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Xe-2yoPY_j710NY7QK-RdMinv7c>
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: Wed, 05 Feb 2020 01:28:45 -0000

> > Does anyone want to co-author and suggest changes?
I would also be glad to participate in that effort.

I have looked at the proposals in the two drafts (Jacob and John H).  
There are a few observations I would like to share.

As Alvaro pointed out, RFC 8092 says:
   This document defines the BGP Large Communities attribute as an
   optional transitive path attribute of variable length.

That means *all* BGP Large Communities are transitive. Do you agree?
RFC 8195 seems to be written in that spirit as well. 

The first 32 bits together are a Global Administrator (GA) ID.
So, it seems it would not be possible to use any part of it as data.
Otherwise, collisions (ambiguity) could happen when 
other LCs use 4-octet ASNs in the Global Administrator field. Agree?
I see Jacob's draft proposes using some portion of the first 32 bits as data.
The draft that John Heasly shared sets the first 32-bits to ASN value 0
to designate WK-LC;  so no part of the first 32-bits is data.

Another idea to consider: 
Why not request IANA to assign a range of 256 or 1024 or some number (?) 
of 4-byte ASN values to be allocated and used as GA ID for transitive WK-LCs?
A function (e.g., route-leak protection) that requires transitive WK-LC 
will be allocated one these ASN values.
Then we don't waste any part of the first 32-bits to designate "type" of LC.
That cleanly leaves 64 bits for local data (as RFC 8092 specifies)
which can accommodate two 4-byte ASNs if needed.

Sriram

> -----Original Message-----
> From: John Heasly <heas@shrubbery.net>
> Sent: Tuesday, February 4, 2020 5:55 PM
> To: Jakob Heitz (jheitz) <jheitz@cisco.com>
> Cc: Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov>ov>; Job Snijders
> <job@ntt.net>et>; Nick Hilliard <nick@foobar.org>rg>; John Heasly
> <heas@shrubbery.net>et>; 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: Re: Question about BGP Large Communities
> 
> Tue, Feb 04, 2020 at 08:45:40PM +0000, Jakob Heitz (jheitz):
> > 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?
> 
> Hey Jacob,
> I'd work on that with you.  Job, Morrow and I also started a draft for
> Large WKCs, but we have not submitted anything - nor made any recent
> progress.
> 
> IIRC, the direction we were intending to use 0 (zero) as the ASN, then
> define local data part 1 as WKC itself, and local data part 2 to be a
> value associated.
> 
> I've attached that I have written so far.  Job and Morrow may or may not
> endorse this approach at this point.
> 
> -heas