Re: [GROW] Benoit Claise's No Objection on draft-ietf-grow-large-communities-usage-07: (with COMMENT)

heasley <heas@shrubbery.net> Thu, 11 May 2017 15:36 UTC

Return-Path: <heas@shrubbery.net>
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 ED41F129B38; Thu, 11 May 2017 08:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 dr0Md9aSvVKj; Thu, 11 May 2017 08:36:26 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B61131470; Thu, 11 May 2017 08:30:42 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 6EDA681C7C; Thu, 11 May 2017 15:30:41 +0000 (UTC)
Date: Thu, 11 May 2017 15:30:41 +0000
From: heasley <heas@shrubbery.net>
To: Benoit Claise <bclaise@cisco.com>
Cc: The IESG <iesg@ietf.org>, grow-chairs@ietf.org, jouni.nospam@gmail.com, grow@ietf.org, draft-ietf-grow-large-communities-usage@ietf.org
Message-ID: <20170511153041.GD7377@shrubbery.net>
References: <149450519340.16653.912352335267369890.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <149450519340.16653.912352335267369890.idtracker@ietfa.amsl.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/lShXCi7sOWvDlbuR-IAGilKMEdU>
Subject: Re: [GROW] Benoit Claise's No Objection on draft-ietf-grow-large-communities-usage-07: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 11 May 2017 15:36:28 -0000

Thu, May 11, 2017 at 05:19:53AM -0700, Benoit Claise:
> Benoit Claise has entered the following ballot position for
> draft-ietf-grow-large-communities-usage-07: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-grow-large-communities-usage/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Introduction
> 
>    BGP Large Communities [RFC8092] provide a mechanism to signal opaque
>    information between Autonomous Systems (ASs). 
> 
> Not only "between": BGP communities might also be used inside an AS, as
> you described in the "informational communities"

true; "and within" - would you pen that, job?

> As mentioned by Jouni in his OPS-DIR review:
> One minor nit I have relates to management & administration to the
> large communities functions and description of their semantics. Are
> those maintained somewhere? If there are existing repositories,
> documentation, etc it would be nice to point out those. The document
> now hints to NANOG and NLNOG..

They are not cataloged anywhere.  I think that you are interpretting
this draft to be more than an example of how one might use Large
Communities, that it is standardizing the Local Data fields, which is
not the case.  These values are defined by and have significance to
the ASN/Global Admin in the first field of the Large Comm.

Does this address the comment?