Re: [Idr] [GROW] Question about BGP Large Communities

Alvaro Retana <aretana.ietf@gmail.com> Tue, 04 February 2020 19:09 UTC

Return-Path: <aretana.ietf@gmail.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 34C06120113; Tue, 4 Feb 2020 11:09:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 B8-QOgx2aV28; Tue, 4 Feb 2020 11:09:04 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 83EF21201A3; Tue, 4 Feb 2020 11:09:04 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id g19so20885757eds.11; Tue, 04 Feb 2020 11:09:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=cWD+Qxp4p29FJPcKHN0kuKMOKXT+Am69NNvKzVl+r8M=; b=mglXjORsh4qiWEz1FqrF3CSDAiOM6Szoia2xTqChiPK1Aaf7Hu+Ee+4owXzMNIr9cQ NJJ0NhPeYWI1Mq8bPqeqRC5wzs/Ok7pPljfTIdypQPfrZhnXg6oTAeKliiPRFdidqSs8 WyWXuO7E+LOWM/pDqEhSkZiQGwCmUGg03Ez9X2B+qMrsxwimqF6iLHVKI/wjCTbGJt54 QFBcK8/jMXJW4x8I+Jyx9ImXeZGUjXJ5z/pfWk6wv9v0xYTeQ9OkHNPAgwwnAE40kOxa FQM2kuF3kb5X+50XHEiQumN9KLaok4aHREaFElA25aOaft0LhbfVte/lXZGXAGps5Er1 +ofg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=cWD+Qxp4p29FJPcKHN0kuKMOKXT+Am69NNvKzVl+r8M=; b=asugfypGpx1q+0ulRMAPJZ2yZwGzbxnUWtPbd8LnfDQNPF7TH/ijy1RFvW2H5cSD3j 7fFFNvAp6IEdUCr2leZSDVlhwlHzN0KKOh+QC0ArrHfIEr1vvKXgX50XWwOACO/HJRZr yK/+sZD9gj7G4NIuZTfeMyw4vBj3VmF+KOPKsqSt1Tb3HMUjezQxlYPGiNM5GTNDcL1/ +gEX+9dA7Ats9YC0Ou7/khwIiPeo0KCHf6J1Rlo5E/O3llBmFzPJG7dJvq2Ryt+D/+lu 1RFE8yYQ9UVLc6+tsC4ifGCXQd2oi3ND74tkJkDyC0SEW9q547Sz9XCHg9283nPgAA7g wIbg==
X-Gm-Message-State: APjAAAWxSFL4Ljn4KBbTYuuSTKhuml1J4bT6sYjSHLQCEzEdi7xhqwFe pAOG30s8LU9msatdr/+S+x8X0GhhWZmocwSpzuY=
X-Google-Smtp-Source: APXvYqyqquCcnWZYE+jZXnE/YPlBKz+unPOpXVR0VDGBMVx/1f87CmCCEN2RvxdsqAQnoEMBx6NlcGqCMCX+ZwO13Bo=
X-Received: by 2002:a17:906:cf8f:: with SMTP id um15mr26922415ejb.289.1580843343025; Tue, 04 Feb 2020 11:09:03 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 4 Feb 2020 11:09:01 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <DM6PR09MB54489301E52DD711E031400984030@DM6PR09MB5448.namprd09.prod.outlook.com>
References: <DM6PR09MB54489301E52DD711E031400984030@DM6PR09MB5448.namprd09.prod.outlook.com>
MIME-Version: 1.0
Date: Tue, 4 Feb 2020 11:09:01 -0800
Message-ID: <CAMMESszpxmUrvNxf4tj6GCy8rjoG_SwvQCqRPOqu-2hc=nC=vQ@mail.gmail.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram=40nist.gov@dmarc.ietf.org>
Cc: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "grow@ietf.org" <grow@ietf.org>, John Heasly <heas@shrubbery.net>, "idr@ietf.org" <idr@ietf.org>, Job Snijders <job@ntt.net>, Nick Hilliard <nick@foobar.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Xa0veVItgoA6-PdlSKtPKVv4Ek8>
Subject: Re: [Idr] [GROW] 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 19:09:06 -0000

On February 4, 2020 at 1:22:11 PM, Sriram, Kotikalapudi (Fed) wrote:

[Speaking as a WG participant.]


Sriram:

Hi!


...
> 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"?

No.

There is no IANA registry for Global Administrator because it is
simply a "four-octet namespace identifier...SHOULD be an ASN"
[rfc8092], but it doesn't have to be.

Skimming through draft-ietf-grow-route-leak-detection-mitigation, I
would say (personal opinion) that you have two options:

(1) Describe the Local Data Parts so that they are well-known when
used by any ASN (Global Administrator).  This has the disadvantage
that the values may collide with existing policies (?).

(2) Request IANA to assign an ASN for this application.  Take a look
at rfc7249/§2.1, which talks about the allocation of special-purpose
AS Numbers.  The advantage is obviously that collisions can be
avoided, but it seems to me that it may be too much (an ASN) for just
this application.

So...if an ASN is requested, it would be independent of Large Communities.


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

rfc8092 "defines the BGP Large Communities attribute as an optional
transitive path attribute".

Regards,

Alvaro.