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

Robert Raszuk <robert@raszuk.net> Wed, 05 February 2020 09:01 UTC

Return-Path: <robert@raszuk.net>
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 110BD1202A0 for <idr@ietfa.amsl.com>; Wed, 5 Feb 2020 01:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 2Y4crFaKItDN for <idr@ietfa.amsl.com>; Wed, 5 Feb 2020 01:01:47 -0800 (PST)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 71EE612029C for <idr@ietf.org>; Wed, 5 Feb 2020 01:01:47 -0800 (PST)
Received: by mail-oi1-x22b.google.com with SMTP id l9so12575oii.5 for <idr@ietf.org>; Wed, 05 Feb 2020 01:01:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VEL2ORiR/VfxeuTBlmzRplBOQ7/a/1dJZd+LeRF5R9M=; b=befkKOx+q7UMHEnimGHHlcjLYd0DL1mjGItYglPsRhEaKkJjFUgeb2xCx2/zHO1OAx cyfUv4uF0RuZQRlGALliBgo1hiwGZRpdUuCpoPoj+/fTa6nMQzuGRmBc0pADha6Ioda2 IjOMnIeYcKm0gZfne/NpY1Y/ym9m9Gwb8/9nFS6WwG90DRQb+UCPUcb3kR4cEQGQcHi2 Yy6I0Wvrp3daxla1Zas1AqSmKri1QZ8UL6pMef5JTMzlbvJv3t6ZXkGAYbENoUXICj/h nhFCtn8RmbcRodQXr9/8wm6EY6/o9LPT8mnaxY8Bh3jUhcszaFckzYGvzQR8Tjs77JFq 4syA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VEL2ORiR/VfxeuTBlmzRplBOQ7/a/1dJZd+LeRF5R9M=; b=p1oe4cpuHM9N8Iv0LLC7teRNE+KFMmDXNVoDuhnH8PE2+sQAFQyTExsGJM9OykNpiL 4nhMMM5fh5SyHPWGFyLO/2eW293vfy/IRGtCoXrOqXlnZnkiRmT86YnO+PTc2tJ0Xs7J NfErWM0Vxg/ALNp/2UNj87hTXTZpCTG8HHoTmGjk0snLgGajCuVsH22Lsot9ruGZK3F0 cRwaaEcOaSuQAKNlY5OjVM/N3nQEQW0Sn1OcABZXgWGHi087GMhYG/Q3O9YXL5fFY+pY w3tsHihXv0ackLM2fmVhe00VFWahtzPtAIVFpo0QUwIFOgdiUsXfIHAdOiw+uKY23+p3 eAmg==
X-Gm-Message-State: APjAAAV59F+IB/Duivzf0Z+mXDYYEk81prD4FTwOdlNyoT8R5wmveNEl ZSvdbgHQqRjfzPol7rcih+ptMFus3+QltOEJ1TP0Pg==
X-Google-Smtp-Source: APXvYqwDHAoDVAZpj3KIHahrIFamCgJbou00hTpQLaIHfvkCt5CT1RJXkP4UIgRrM9DMCWj5qOtseSb4Au8NQ/6HRUE=
X-Received: by 2002:aca:4306:: with SMTP id q6mr2195413oia.54.1580893306642; Wed, 05 Feb 2020 01:01:46 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR09MB54489301E52DD711E031400984030@DM6PR09MB5448.namprd09.prod.outlook.com> <BN6PR11MB1890AA431F63030DFE310902C0030@BN6PR11MB1890.namprd11.prod.outlook.com> <CAOj+MMH-xff0VUBy5UZZp7FH7_ES5A5ZCcUqFin2UP0hOnpjug@mail.gmail.com> <5603F4C9-7ECD-4A9C-AF81-49AE292CEE83@cisco.com> <CAOj+MMF3K6jCp+CDg92ua7qH5hkQ1V+g0JoFt_zf+zCogwVZ7g@mail.gmail.com> <90fab3d5ec794e95be0d86cae2d4a235@huawei.com> <CAH1iCirCG8vXXRJPJgaYbCCvsxNtFvBha39Hs2a3xVYkCV=SEQ@mail.gmail.com>
In-Reply-To: <CAH1iCirCG8vXXRJPJgaYbCCvsxNtFvBha39Hs2a3xVYkCV=SEQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 5 Feb 2020 10:01:37 +0100
Message-ID: <CAOj+MMFJE+7BATTrKFmtmQ7P0HCKceOVXgBhnxcd_Xkvf6YOOQ@mail.gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "idr@ietf.org" <idr@ietf.org>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f87679059dd067f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/eLeTLV9sMzKupp0ePVGpoRS5NEc>
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: Wed, 05 Feb 2020 09:01:49 -0000

Just to clarify one subtle point.

In wide communities types are either operator assigned or IANA driven - no
new code from vendor is required in contrast to extended community. That
along with variable length is what makes wide communities universal.

Sure that some vendors or individuals are scared about policy aspect of
wide communities processing - but implementing policy handling any
arbitrary types (irrespective of IANA or local assignment) is optional.

- - -

To the topic of using Large Communities - I do recommend whichever encoding
is chosen to always be able to insert and carry originator's ASN. All zeros
are meaningless read: anonymous.

Thx,
R.


On Wed, Feb 5, 2020 at 2:45 AM Brian Dickson <brian.peter.dickson@gmail.com>
wrote:

> Disagree, we want something deployed (large) and deployable (requiring
> only IANA action, no vendor activity) immediately.
> IMHO, any special handling or new code points or upgrades are non-starters.
> This particularly applies to wide and extended
> Brian
>
> On Tue, Feb 4, 2020 at 5:41 PM Dongjie (Jimmy) <jie.dong@huawei.com>
> wrote:
>
>> Agree that for this case it may be more convenient to just use extended
>> community with a new type, this could avoid any possible collision with
>> existing deployments, and save the effort of assigning a set of ASNs. Wide
>> community may be too powerful for this:)
>>
>>
>>
>> Best regards,
>>
>> Jie
>>
>