One document matched: draft-chen-bgp-ext-community-orf-00.txt
Network Working Group Enke Chen
Internet Draft Cisco Systems
Expiration Date: December 2006 Yakov Rekhter
Juniper Networks
Extended Community Based Outbound Route Filter for BGP-4
draft-chen-bgp-ext-community-orf-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This document defines a new Outbound Router Filter type for BGP,
termed "Extended Community Outbound Route Filter", that can be used
to perform extended community based route filtering.
Chen & Rekhter [Page 1]
Internet Draft draft-chen-bgp-ext-community-orf-00.txt June 2006
1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119].
2. Introduction
The Cooperative Outbound Route Filtering Capability defined in [BGP-
ORF] provides a mechanism for a BGP speaker to send to its BGP peer a
set of Outbound Route Filters (ORFs) that can be used by its peer to
filter its outbound routing updates to the speaker.
This document defines a new Outbound Router Filter type for BGP
[BGP-4], termed "Extended Community Outbound Route Filter", that can
be used to perform the extended community [BGP-EXT-COMMUNITIES] based
route filtering.
3. Extended Communities ORF-Type
The Extended Community ORF-Type allows to express ORFs in terms of
BGP Extended Communities. That is, the Extended Communities ORF-Type
provides Extended Communities-based route filtering.
Conceptually the ORF-value of the Extended Communities ORF-Type
consists of a single Extended Community.
The sender SHOULD set the value of the Match field to PERMIT; the
receiver SHOULD ignore the value of the Match field.
The remote peer should consider only those routes whose Extended
Communities attribute has at least one Extended Community in common
with the Extended Communities list specified in the ORF.
Chen & Rekhter [Page 2]
Internet Draft draft-chen-bgp-ext-community-orf-00.txt June 2006
4. Extended Communities ORF Encoding
The value of the ORF-Type for the Extended Communities ORF-Type is 3.
The type-specific part of Extended Communities ORF-Type consists of a
single Extended Community encoded as an eight-octets field.
5. IANA Considerations
This document specifies a new Outbound Route Filtering (ORF) type,
Extended Community ORF. The value of the ORF-type is 3.
6. Security Considerations
This extension to BGP does not change the underlying security issues.
7. Normative References
[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC4271, January 2006.
[BGP-EXT-COMMUNITIES] Sangli, S., Tappan, D., and Y. Rekhter, "BGP
Extended Communities Attribute", RFC4360, February 2006.
[BGP-ORF] Chen, E., and Rekhter, Y., "Cooperative Route Filtering
Capability for BGP-4", draft-ietf-idr-route-filter-14.txt, June 2006.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
8. Author Information
Enke Chen
Cisco Systems, Inc.
170 W. Tasman Dr.
San Jose, CA 95134
EMail: enkechen@cisco.com
Yakov Rekhter
Juniper Networks, Inc.
1194 N. Mathilda Ave
Sunnyvale, CA 94089
Chen & Rekhter [Page 3]
Internet Draft draft-chen-bgp-ext-community-orf-00.txt June 2006
EMail: yakov@juniper.net
9. Intellectual Property Considerations
This section is taken from Section 5 of RFC 3668.
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
10. Copyright Notice
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Chen & Rekhter [Page 4]
| PAFTECH AB 2003-2026 | 2026-04-24 08:59:11 |