draft-ietf-idr-bgp-prefix-orf-00.txt   draft-ietf-idr-bgp-prefix-orf-01.txt 
Network Working Group Enke Chen Network Working Group Enke Chen
Internet Draft Redback Networks Internet Draft Srihari R. Sangli
Expiration Date: February 2005 Srihari R. Sangli Expiration Date: October 2005 Cisco Systems
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-00.txt draft-ietf-idr-bgp-prefix-orf-01.txt
1. Status of this Memo 1. Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668. disclosed, in accordance with RFC 3668.
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 2. Abstract
This document defines a new Outbound Router Filter type for BGP, This document defines a new Outbound Router Filter type for BGP,
skipping to change at page 2, line 29 skipping to change at page 2, line 29
4. Address Prefix ORF-Type 4. 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 is a number that specifies the relative ordering The "Sequence" field specifies the relative ordering of the entry
of the entry. among all the Address Prefix ORF entries.
The "Match" field specifies whether this entry is "PERMIT" (value 0), The "Match" field specifies whether this entry is "PERMIT" (value 0),
or "DENY" (value 1). or "DENY" (value 1).
The "Length" field indicates the length in bits of the address The "Length" field indicates the length in bits of the address
prefix. A length of zero indicates a prefix that matches all (as prefix. A length of zero indicates a prefix that matches all (as
specified by the address family) addresses (with prefix itself of specified by the address family) addresses (with prefix itself of
zero octets). zero octets).
The "Prefix" field contains an address prefix of an address family. The "Prefix" field contains an address prefix of an address family.
skipping to change at page 4, line 12 skipping to change at page 4, line 12
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 6. 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 <length, prefix>. 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 <Length, Prefix> fields neither more specific than, nor equal to, the <Prefix, Length> fields
of the ORF entry. of the ORF entry.
When the NLRI is either more specific than, or equal to, the <Length, When the NLRI is either more specific than, or equal to, the <Prefix,
Prefix> fields of the ORF entry, the route is considered as a match Length> fields of the ORF entry, the route is considered as a match
to the ORF entry only if the NLRI match condition as listed in the to the ORF entry only if the NLRI match condition as listed in the
following table is satisfied. following table is satisfied.
ORF Entry NLRI ORF Entry NLRI
Minlen Maxlen Match Condition Minlen Maxlen Match Condition
+------------------------------------------------------+ +------------------------------------------------------+
| un-spec. un-spec. NLRI.legnth == ORF.length | | un-spec. un-spec. NLRI.legnth == ORF.length |
+------------------------------------------------------+ +------------------------------------------------------+
| specified un-spec. NLRI.length >= ORF.Minlen | | specified un-spec. NLRI.length >= ORF.Minlen |
+------------------------------------------------------+ +------------------------------------------------------+
| un-spec. specified NLRI.length <= ORF.Maxlen | | un-spec. specified NLRI.length <= ORF.Maxlen |
+------------------------------------------------------+ +------------------------------------------------------+
| specified specified NLRI.length >= ORF.Minlen | | specified specified NLRI.length >= ORF.Minlen |
| AND NLRI.length <= ORF.Maxlen | | AND NLRI.length <= ORF.Maxlen |
+------------------------------------------------------+ +------------------------------------------------------+
It is possible that the speaker would have more than one Prefix When more than one Address Prefix ORF entry match the NLRI of the
Address ORF entry that matches the NLRI of the route. In that case route, the "first-match" rule applies. That is, the ORF entry with
the "first-match" rule applies. That is, the ORF entry with the the smallest sequence number (among all the matching ORF entries) is
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.
7. Security Considerations The assignment of the sequence numbers is a local matter for the BGP
speaker that sends the Address Prefix ORF entries.
7. IANA Considerations
This document specifies a new Outbound Route Filtering (ORF) type,
Address Prefix ORF. The value of the ORF-type is 64.
8. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
8. References 9. 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-24.txt, November 2003. 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-10.txt, March Capability for BGP-4", draft-ietf-idr-route-filter-11.txt, December
2004. 2004.
9. Author Information 10. Author Information
Enke Chen Enke Chen
Redback Networks, Inc. Cisco Systems, Inc.
300 Holger Way 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Email: enke@redback.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
10. Full Copyright Notice 11. Full Copyright Notice
Copyright (C) The Internet Society (2004). 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 is provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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