grow: Protocol Action: 'BGP Communities for Data Collection' to BCP

The IESG <iesg-secretary@ietf.org> Tue, 23 November 2004 21:36 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06532 for <grow-archive@lists.ietf.org>; Tue, 23 Nov 2004 16:36:14 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id iANLPRlR003528; Tue, 23 Nov 2004 13:25:27 -0800 (PST)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id iANLPR6B003522; Tue, 23 Nov 2004 13:25:27 -0800 (PST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id iANLPPHp003382 for <grow@lists.uoregon.edu>; Tue, 23 Nov 2004 13:25:26 -0800 (PST)
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CWheR-0001Uz-Qb; Tue, 23 Nov 2004 15:52:39 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, grow mailing list <grow@lists.uoregon.edu>, grow chair <gih@telstra.net>, grow chair <isoc-contact@aarnet.edu.au>, grow chair <dmm@1-4-5.net>
Subject: grow: Protocol Action: 'BGP Communities for Data Collection' to BCP
Message-Id: <E1CWheR-0001Uz-Qb@megatron.ietf.org>
Date: Tue, 23 Nov 2004 15:52:39 -0500
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

The IESG has approved the following document:

- 'BGP Communities for Data Collection '
   <draft-ietf-grow-collection-communities-06.txt> as a BCP

This document is the product of the Global Routing Operations Working Group. 

The IESG contact persons are David Kessens and Bert Wijnen.

RFC Editor note:

In section 2., please replace 'refered' with 'referred'.

Technical Summary
 
 BGP communities (RFC 1997) are used by service providers for many
 purposes, including tagging of customer, peer, and geographically
 originated routes.  Such tagging is typically used to control the
 scope of redistribution of routes within a provider's network, and to
 its peers and customers. With the advent of large scale BGP data
 collection (and associated research), it has become clear that the
 information carried in such communities is essential for a deeper
 understanding of the global routing system. This document defines
 standard (outbound) communities and their encodings for export to BGP
 route collectors.
 
Working Group Summary
 
 This document is a product of the grow working group.
 
Protocol Quality
 
 David Kessens reviewed this document for the IESG.

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/