draft-ietf-idr-bgp-prefix-orf-04.txt   draft-ietf-idr-bgp-prefix-orf-05.txt 
Network Working Group E. Chen Network Working Group E. Chen
Internet Draft S. Sangli Internet Draft S. Sangli
Expiration Date: January 2007 Cisco Systems Expiration Date: January 2009 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-04.txt draft-ietf-idr-bgp-prefix-orf-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. 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
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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.
Abstract Abstract
This document defines a new Outbound Router Filter type for BGP, This document defines a new Outbound Router Filter (ORF) type for
termed "Address Prefix Outbound Route Filter", that can be used to BGP, termed "Address Prefix Outbound Route Filter", that can be used
perform address prefix based route filtering. This ORF-type supports to perform address prefix based route filtering. This ORF-type
prefix length or range based matching, wild-card based address prefix supports prefix length or range based matching, wild-card based
matching, as well as the exact address prefix matching for address address prefix matching, as well as the exact address prefix matching
families. for address families.
1. Introduction 1. Introduction
The Outbound Route Filtering Capability defined in [BGP-ORF] provides The Outbound Route Filtering Capability defined in [BGP-ORF] provides
a mechanism for a BGP speaker to send to its BGP peer a set of 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 Outbound Route Filters (ORFs) that can be used by its peer to filter
its outbound routing updates to the speaker. 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
skipping to change at page 3, line 10 skipping to change at page 3, line 10
with value 0. with value 0.
The fields "Sequence", "Length", "Minlen", and "Maxlen" are all The fields "Sequence", "Length", "Minlen", and "Maxlen" are all
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 However, tests related to the "Minlen" or "Maxlen" value should be
bits) of a host address for a given address family [BGP-MP]. omitted when the "Minlen" or "Maxlen" field (respectively) is
unspecified.
In addition, the "Maxlen" value must be no more than the maximum
length (in bits) of a host address for a given address family [BGP-
MP].
3. 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
ORF], and the remaining fields of the entry is encoded in the "Type [BGP-ORF], and the remaining fields of the entry is encoded in the
specific part" as shown in Figure 1. "Type specific part" as shown in Figure 1.
+--------------------------------+ +--------------------------------+
| Sequence (4 octets) | | Sequence (4 octets) |
+--------------------------------+ +--------------------------------+
| Minlen (1 octet) | | Minlen (1 octet) |
+--------------------------------+ +--------------------------------+
| Maxlen (1 octet) | | Maxlen (1 octet) |
+--------------------------------+ +--------------------------------+
| Length (1 octet) | | Length (1 octet) |
+--------------------------------+ +--------------------------------+
skipping to change at page 4, line 26 skipping to change at page 4, line 26
of the ORF entry. of the ORF entry.
When the NLRI is either more specific than, or equal to, the <Prefix, When the NLRI is either more specific than, or equal to, the <Prefix,
Length> 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 Table to the ORF entry only if the NLRI match condition as listed in Table
1 is satisfied. 1 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.length == 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 |
+------------------------------------------------------+ +------------------------------------------------------+
Table 1: Address Prefix ORF Matching Table 1: Address Prefix ORF Matching
skipping to change at page 5, line 12 skipping to change at page 5, line 12
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.
5. 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.
6. 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
[BGP-4].
7. Normative References 7. Normative References
[BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol [BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol
4 (BGP-4)", RFC 4271, January 2006. 4 (BGP-4)", RFC 4271, January 2006.
[BGP-MP] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, [BGP-MP] Bates, T., Chandra, R., Rekhter, Y., and D. Katz,
"Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007.
[BGP-ORF] Chen, E., and Rekhter, Y., "Outbound Route Filtering [BGP-ORF] Chen, E., and Rekhter, Y., "Outbound Route Filtering
Capability for BGP-4", draft-ietf-idr-route-filter-15.txt, July 2006. Capability for BGP-4", draft-ietf-idr-route-filter-17.txt, June 2008.
8. 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
skipping to change at page 6, line 31 skipping to change at page 6, line 31
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
10. Full Copyright Notice 10. Full Copyright Notice
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The IETF Trust (2008).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. 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 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, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 11 change blocks. 
25 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/