datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

BGP Communities for Data Collection
draft-ietf-grow-collection-communities-08

RFC
Document Stream: IETF
Last updated: 2005-08-23
Intended RFC status: Best Current Practice
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 4384
Responsible AD: David Kessens
IESG Note: RFC 4384
BCP 0114
Send notices to: gih@telstra.net, isoc-contact@aarnet.edu.au, dmm@1-4-5.net

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-grow-collection-communities.

Abstract:
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 memo defines standard (outbound) communities and their encodings for export to BGP route collectors. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Authors:
David Meyer <dmm@1-4-5.net>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)