Re: [GROW] New Version Notification for draft-ymbk-grow-bgp-collector-communities-02.txt

Jeffrey Haas <jhaas@pfrc.org> Fri, 18 February 2022 21:08 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557453A1284 for <grow@ietfa.amsl.com>; Fri, 18 Feb 2022 13:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 U7OCl3cORLGE for <grow@ietfa.amsl.com>; Fri, 18 Feb 2022 13:08:06 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 7E83A3A127C for <grow@ietf.org>; Fri, 18 Feb 2022 13:08:06 -0800 (PST)
Received: from smtpclient.apple (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 9C86D1E341; Fri, 18 Feb 2022 16:08:05 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DC5AEA5D-2C7D-45AC-BFFD-87ADB396472B"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <m2sfsgozff.wl-randy@psg.com>
Date: Fri, 18 Feb 2022 16:08:04 -0500
Cc: Job Snijders <job@fastly.com>, GMO Crops <grow@ietf.org>
Message-Id: <89931D7A-95E8-4A3A-86DE-9657A47E7331@pfrc.org>
References: <164513217798.20599.9841795221124659450@ietfa.amsl.com> <CB281229-B539-4C52-9914-A4CBDA8D35DB@psg.com> <Yg+Gm2xWrPbFFtTi@snel> <m2sfsgozff.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/6a7-N2_x7NVNej-WDjj5WQKwTg8>
Subject: Re: [GROW] New Version Notification for draft-ymbk-grow-bgp-collector-communities-02.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2022 21:08:12 -0000


> On Feb 18, 2022, at 12:30 PM, Randy Bush <randy@psg.com> wrote:
> 
>> 
>> * 32-bit ASNs don't fit in 16-bit fields. Consider using a set of
>>  Extended Communities?
> 
> next you're gonna want ipv6; sheesh!  :)
> 
> i think the draft tried to finesse and not get into wire format.  but it
> probably should.
> 
> extended or wide?  

If your semantics will happily fit into 6 bytes, extended would work okay for you.  Implementations that support extended communities often let you configure such things even if they're not "well known".

https://www.rfc-editor.org/rfc/rfc5668.html <https://www.rfc-editor.org/rfc/rfc5668.html>

You'd probably just want to ask for a new sub-type for this using the transitive version of the type, and then put the semantics in the local-admin.  Most of the range is defined first come, first served so it's trivial to get an assignment without a lot of work.

https://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml#trans-four-octet-as

-- Jeff