Re: [GROW] Last Call: <draft-ietf-grow-large-communities-usage-05.txt> (Use of BGP Large Communities) to Informational RFC

Jay Borkenhagen <jayb@braeburn.org> Wed, 12 April 2017 16:04 UTC

Return-Path: <jayb@oz.mt.att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51BB4131777; Wed, 12 Apr 2017 09:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level:
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8] 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 Sjwcv-MBwOi1; Wed, 12 Apr 2017 09:04:07 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 A8235131774; Wed, 12 Apr 2017 09:04:07 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v3CDjBQW037672; Wed, 12 Apr 2017 09:46:46 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 29sn9mgdqs-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Apr 2017 09:46:45 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkiTx000328; Wed, 12 Apr 2017 09:46:45 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkcGT032579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 12 Apr 2017 09:46:38 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi131.aldc.att.com (RSA Interceptor); Wed, 12 Apr 2017 13:46:23 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkNjx017287; Wed, 12 Apr 2017 09:46:23 -0400
Received: from oz.mt.att.com (oz.mt.att.com [135.16.165.23]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3CDkJXW016509; Wed, 12 Apr 2017 09:46:19 -0400
Received: by oz.mt.att.com (Postfix, from userid 1000) id A2161A40E33; Wed, 12 Apr 2017 09:46:18 -0400 (EDT)
X-Mailer: emacs 24.3.1 (via feedmail 11-beta-1 I); VM 8.2.0b under 24.3.1 (x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <22766.12199.587325.838948@oz.mt.att.com>
Date: Wed, 12 Apr 2017 09:46:15 -0400
From: Jay Borkenhagen <jayb@braeburn.org>
To: ietf@ietf.org
Cc: grow-chairs@ietf.org, grow@ietf.org, warren@kumari.net, draft-ietf-grow-large-communities-usage@ietf.org, Enke Chen <enkechen@cisco.com>
Subject: Re: [GROW] Last Call: <draft-ietf-grow-large-communities-usage-05.txt> (Use of BGP Large Communities) to Informational RFC
In-Reply-To: <149158518251.11127.8008659284325510446.idtracker@ietfa.amsl.com>
References: <149158518251.11127.8008659284325510446.idtracker@ietfa.amsl.com>
Reply-To: Jay Borkenhagen <jayb@braeburn.org>
X-GPG-Fingerprint: DDDB 542E D988 94D0 82D3 D198 7DED 6648 2308 D3C0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-12_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=13 phishscore=0 bulkscore=0 spamscore=0 clxscore=1034 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1704120115
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9N1I0PSze58YBZsJhdjEWOdKc2g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:04:09 -0000

On 07-April-2017, The IESG writes:
 > 
 > The IESG has received a request from the Global Routing Operations WG
 > (grow) to consider the following document:
 > - 'Use of BGP Large Communities'
 >   <draft-ietf-grow-large-communities-usage-05.txt> as Informational RFC
 > 
 > The IESG plans to make a decision in the next few weeks, and solicits
 > final comments on this action. Please send substantive comments to the
 > ietf@ietf.org mailing lists by 2017-04-21. Exceptionally, comments may be
 > sent to iesg@ietf.org instead. In either case, please retain the
 > beginning of the Subject line to allow automated sorting.
 > 

The following comment may not measure up to being "substantive", but
those in authority can decide.


I have always liked the way the definition of the "BGP Communities
Attribute" spec in RFC1997 was paired with RFC1998's "An Application
of the BGP Community Attribute in Multi-home Routing": the former for
the "bits on the wire" spec, the latter for "how operators can use it."

draft-ietf-grow-large-communities-usage-05.txt's Introduction section
currently reads as follows:

   BGP Large Communities [RFC8092] provide a mechanism to signal
   opaque information between Autonomous Systems (ASs).  This document
   presents examples of how operators might utilize BGP Large
   Communities to achieve various goals.  This document draws on the
   experience of operator communities such as NANOG [1] and NLNOG [2].

I would like to suggest this minor change:

   BGP Large Communities [RFC8092] provide a mechanism to signal
   opaque information between Autonomous Systems (ASs).  In very much
   the same way that [RFC1998] provides a concrete real-world
   application for [RFC1997]'s communities, this document presents
   examples of how operators might utilize BGP Large Communities to
   achieve various goals.  This document draws on the experience of
   operator communities such as NANOG [1] and NLNOG [2].

Thanks for considering, and very belated thanks to Tony and Enke for
RFC1998. 

						Jay B.