draft-ietf-idr-bgp-prefix-orf-01.txt   draft-ietf-idr-bgp-prefix-orf-02.txt 
Network Working Group Enke Chen Network Working Group Enke Chen
Internet Draft Srihari R. Sangli Internet Draft Srihari R. Sangli
Expiration Date: October 2005 Cisco Systems Expiration Date: May 2006 Cisco Systems
Address Prefix Based Outbound Route Filter for BGP-4 Address Prefix Based Outbound Route Filter for BGP-4
draft-ietf-idr-bgp-prefix-orf-01.txt draft-ietf-idr-bgp-prefix-orf-02.txt
1. Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
or will be disclosed, and any of which I become aware will be have been or will be disclosed, and any of which he or she becomes
disclosed, in accordance with RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
2. Abstract Abstract
This document defines a new Outbound Router Filter type for BGP, This document defines a new Outbound Router Filter type for BGP,
termed "Address Prefix Outbound Route Filter", that can be used to termed "Address Prefix Outbound Route Filter", that can be used to
perform address prefix based route filtering. This ORF-type supports perform address prefix based route filtering. This ORF-type supports
prefix length or range based matching, wild-card based address prefix prefix length or range based matching, wild-card based address prefix
matching, as well as the exact address prefix matching for address matching, as well as the exact address prefix matching for address
families. families.
3. Introduction 1. Introduction
The Cooperative Outbound Route Filtering Capability defined in [BGP- The Cooperative Outbound Route Filtering Capability defined in [BGP-
ORF] provides a mechanism for a BGP speaker to send to its BGP peer a 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 set of Outbound Route Filters (ORFs) that can be used by its peer to
filter its outbound routing updates to the speaker. filter its outbound routing updates to the speaker.
This documents defines a new ORF-type for BGP, termed "Address Prefix This documents defines a new ORF-type for BGP, termed "Address Prefix
Outbound Route Filter (Address Prefix ORF)", that can be used to Outbound Route Filter (Address Prefix ORF)", that can be used to
perform address prefix based route filtering. The Address Prefix ORF perform address prefix based route filtering. The Address Prefix ORF
supports prefix length or range based matching, wild-card based supports prefix length or range based matching, wild-card based
address prefix matching, as well as the exact address prefix matching address prefix matching, as well as the exact address prefix matching
for address families [BGP-MP]. for address families [BGP-MP].
4. Address Prefix ORF-Type 2. Address Prefix ORF-Type
The Address Prefix ORF-Type allows one to express ORFs in terms of The Address Prefix ORF-Type allows one to express ORFs in terms of
address prefixes. That is, it provides address prefix based route address prefixes. That is, it provides address prefix based route
filtering, including prefix length or range based matching, as well filtering, including prefix length or range based matching, as well
as wild-card address prefix matching. as wild-card address prefix matching.
Conceptually an Address Prefix ORF entry consists of the fields Conceptually an Address Prefix ORF entry consists of the fields
<Sequence, Match, Length, Prefix, Minlen, Maxlen>. <Sequence, Match, Length, Prefix, Minlen, Maxlen>.
The "Sequence" field specifies the relative ordering of the entry The "Sequence" field specifies the relative ordering of the entry
skipping to change at page 3, line 13 skipping to change at page 3, line 13
unsigned integers. unsigned integers.
This document imposes the following requirement on the values of This document imposes the following requirement on the values of
these fields: these fields:
0 <= Length < Minlen <= Maxlen 0 <= Length < Minlen <= Maxlen
In addition, the "Maxlen" must be no more than the maximum length (in In addition, the "Maxlen" must be no more than the maximum length (in
bits) of a host address for a given address family [BGP-MP]. bits) of a host address for a given address family [BGP-MP].
5. Address Prefix ORF Encoding 3. Address Prefix ORF Encoding
The value of the ORF-Type for the Address Prefix ORF-Type is 64. The value of the ORF-Type for the Address Prefix ORF-Type is 64.
An Address Prefix ORF entry is encoded as follows. The "Match" field An Address Prefix ORF entry is encoded as follows. The "Match" field
of the entry is encoded in the "Match" field of the common part [BGP- of the entry is encoded in the "Match" field of the common part [BGP-
ORF], and the remaining fields of the entry is encoded in the "Type ORF], and the remaining fields of the entry is encoded in the "Type
specific part" as follows. specific part" as follows.
+--------------------------------+ +--------------------------------+
| Sequence (4 octets) | | Sequence (4 octets) |
skipping to change at page 4, line 5 skipping to change at page 4, line 5
+--------------------------------+ +--------------------------------+
| Length (1 octet) | | Length (1 octet) |
+--------------------------------+ +--------------------------------+
| Prefix (variable length) | | Prefix (variable length) |
+--------------------------------+ +--------------------------------+
Note that the Prefix field contains the address prefix followed by Note that the Prefix field contains the address prefix followed by
enough trailing bits to make the end of the field fall on an octet enough trailing bits to make the end of the field fall on an octet
boundary. The value of the trailing bits is irrelevant. boundary. The value of the trailing bits is irrelevant.
6. Address Prefix ORF Matching 4. Address Prefix ORF Matching
In addition to the general matching rules defined in [BGP-ORF], In addition to the general matching rules defined in [BGP-ORF],
several Address Prefix ORF specific matching rules are defined as several Address Prefix ORF specific matching rules are defined as
follows. follows.
Consider an Address Prefix ORF entry, and a route maintained by a BGP Consider an Address Prefix ORF entry, and a route maintained by a BGP
speaker with NLRI in the form of <Prefix, Length>. speaker with NLRI in the form of <Prefix, Length>.
The route is considered as "no match" to the ORF entry if the NLRI is The route is considered as "no match" to the ORF entry if the NLRI is
neither more specific than, nor equal to, the <Prefix, Length> fields neither more specific than, nor equal to, the <Prefix, Length> fields
skipping to change at page 5, line 5 skipping to change at page 5, line 5
When more than one Address Prefix ORF entry match the NLRI of the When more than one Address Prefix ORF entry match the NLRI of the
route, the "first-match" rule applies. That is, the ORF entry with route, the "first-match" rule applies. That is, the ORF entry with
the smallest sequence number (among all the matching ORF entries) is the smallest sequence number (among all the matching ORF entries) is
considered as the sole match, and it would determine whether the considered as the sole match, and it would determine whether the
route should be advertised. route should be advertised.
The assignment of the sequence numbers is a local matter for the BGP The assignment of the sequence numbers is a local matter for the BGP
speaker that sends the Address Prefix ORF entries. speaker that sends the Address Prefix ORF entries.
7. IANA Considerations 5. IANA Considerations
This document specifies a new Outbound Route Filtering (ORF) type, This document specifies a new Outbound Route Filtering (ORF) type,
Address Prefix ORF. The value of the ORF-type is 64. Address Prefix ORF. The value of the ORF-type is 64.
8. Security Considerations 6. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
9. References 7. Normative References
[BGP-4] Rekhter, Y., T. Li, and S. Hares, "A Border Gateway Protocol [BGP-4] Rekhter, Y., T. Li, and S. Hares, "A Border Gateway Protocol
4 (BGP-4)", draft-ietf-idr-bgp4-26.txt, December 2004. 4 (BGP-4)", draft-ietf-idr-bgp4-26.txt, December 2004.
[BGP-MP] Bates, T., Chandra, R., Katz, D. and Y. Rekhter, [BGP-MP] Bates, T., Chandra, R., Katz, D. and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
[BGP-ORF] Chen, E., and Rekhter, Y., "Cooperative Route Filtering [BGP-ORF] Chen, E., and Rekhter, Y., "Cooperative Route Filtering
Capability for BGP-4", draft-ietf-idr-route-filter-11.txt, December Capability for BGP-4", draft-ietf-idr-route-filter-12.txt, July 2005.
2004.
10. Author Information 8. Author Information
Enke Chen Enke Chen
Cisco Systems, Inc. Cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Email: enkechen@cisco.com Email: enkechen@cisco.com
Srihari R. Sangli Srihari R. Sangli
Cisco Systems, Inc. Cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Email: rsrihari@cisco.com Email: rsrihari@cisco.com
11. Full Copyright Notice 9. Full Copyright Notice
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 End of changes. 17 change blocks. 
19 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/