Re: Protocol Action: NOPEER community for BGP route scope control to BCP

john heasley <heas@shrubbery.net> Wed, 04 June 2003 15:52 UTC

Date: Tue, 03 Jun 2003 17:52:14 +0000
From: john heasley <heas@shrubbery.net>
To: The IESG <iesg-secretary@ietf.org>
Cc: ietf@ietf.org, RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>
Subject: Re: Protocol Action: NOPEER community for BGP route scope control to BCP
Message-ID: <20030603175214.GC7578@shrubbery.net>
References: <200306021524.LAA11839@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200306021524.LAA11839@ietf.org>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

please note that the ptomaine list, formerly ptomaine@shrubbery.net, has
been consumed by GROW.

Date: Fri, 2 May 2003 13:29:11 -0700
       The PTOMAINE mailing list is in the process of being
        retired. GROW is taking its place. If you are not already
        on the GROW list and want to subscribe, the information is: 

          General Discussion:  grow@lists.uoregon.edu
          To Subscribe:        majordomo@lists.uoregon.edu (subscribe grow)
          Archive:             http://darkwing.uoregon.edu/~llynch/grow

Mon, Jun 02, 2003 at 11:24:35AM -0400, The IESG:
> 
> The IESG has approved the Internet-Draft 'NOPEER community for BGP
> route scope control' <draft-ietf-ptomaine-nopeer-03.txt> as a BCP.
> This document is the product of the Prefix Taxonomy Ongoing Measurement
> & Inter Network Experiment Working Group. The IESG contact persons are
> Randy Bush and Bert Wijnen.
> 
>  Technical Summary
>    
>    This document proposes the use of a BGP community to advise BGP
>    peers and others on the scope of propagation the originating AS
>    intended for a prefix. This proposed well-known advisory
>    transitive community is intended to allow an origin AS to specify
>    the extent to which it suggests that a specific prefix should be
>    externally propagated. In particular this community, termed here
>    as NOPEER, allows an origin AS to suggest that a route with this
>    attribute need not be advertised across bilateral peer
>    connections.
>    
>  Working Group Summary
>    
>    There were no technical issues raised in working group discussion
>    or working group last call.
>    
>  Protocol Quality
>    
>    This document was reviewed for the IESG by Randy Bush.

Re: Protocol Action: NOPEER community for BGP rou… john heasley