idnits 2.17.1 draft-ietf-idr-bgp-prefix-orf-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 239. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 212. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 219. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 225. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 148 has weird spacing: '...ecified un-s...' == Line 152 has weird spacing: '...ecified spec...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'BGP-4' is defined on line 178, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2858 (ref. 'BGP-MP') (Obsoleted by RFC 4760) == Outdated reference: A later version (-17) exists of draft-ietf-idr-route-filter-15 Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Chen 3 Internet Draft S. Sangli 4 Expiration Date: January 2007 Cisco Systems 6 Address Prefix Based Outbound Route Filter for BGP-4 8 draft-ietf-idr-bgp-prefix-orf-04.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This document defines a new Outbound Router Filter type for BGP, 36 termed "Address Prefix Outbound Route Filter", that can be used to 37 perform address prefix based route filtering. This ORF-type supports 38 prefix length or range based matching, wild-card based address prefix 39 matching, as well as the exact address prefix matching for address 40 families. 42 1. Introduction 44 The Outbound Route Filtering Capability defined in [BGP-ORF] provides 45 a mechanism for a BGP speaker to send to its BGP peer a set of 46 Outbound Route Filters (ORFs) that can be used by its peer to filter 47 its outbound routing updates to the speaker. 49 This documents defines a new ORF-type for BGP, termed "Address Prefix 50 Outbound Route Filter (Address Prefix ORF)", that can be used to 51 perform address prefix based route filtering. The Address Prefix ORF 52 supports prefix length or range based matching, wild-card based 53 address prefix matching, as well as the exact address prefix matching 54 for address families [BGP-MP]. 56 2. Address Prefix ORF-Type 58 The Address Prefix ORF-Type allows one to express ORFs in terms of 59 address prefixes. That is, it provides address prefix based route 60 filtering, including prefix length or range based matching, as well 61 as wild-card address prefix matching. 63 Conceptually an Address Prefix ORF entry consists of the fields 64 . 66 The "Sequence" field specifies the relative ordering of the entry 67 among all the Address Prefix ORF entries. 69 The "Match" field specifies whether this entry is "PERMIT" (value 0), 70 or "DENY" (value 1). 72 The "Length" field indicates the length in bits of the address 73 prefix. A length of zero indicates a prefix that matches all (as 74 specified by the address family) addresses (with prefix itself of 75 zero octets). 77 The "Prefix" field contains an address prefix of an address family. 79 The "Minlen" field indicates the minimum prefix length in bits that 80 is required for "matching". The field is considered as un-specified 81 with value 0. 83 The "Maxlen" field indicates the maximum prefix length in bits that 84 is required for "matching". The field is considered as un-specified 85 with value 0. 87 The fields "Sequence", "Length", "Minlen", and "Maxlen" are all 88 unsigned integers. 90 This document imposes the following requirement on the values of 91 these fields: 93 0 <= Length < Minlen <= Maxlen 95 In addition, the "Maxlen" must be no more than the maximum length (in 96 bits) of a host address for a given address family [BGP-MP]. 98 3. Address Prefix ORF Encoding 100 The value of the ORF-Type for the Address Prefix ORF-Type is 64. 102 An Address Prefix ORF entry is encoded as follows. The "Match" field 103 of the entry is encoded in the "Match" field of the common part [BGP- 104 ORF], and the remaining fields of the entry is encoded in the "Type 105 specific part" as shown in Figure 1. 107 +--------------------------------+ 108 | Sequence (4 octets) | 109 +--------------------------------+ 110 | Minlen (1 octet) | 111 +--------------------------------+ 112 | Maxlen (1 octet) | 113 +--------------------------------+ 114 | Length (1 octet) | 115 +--------------------------------+ 116 | Prefix (variable length) | 117 +--------------------------------+ 119 Figure 1: Address Prefix ORF Encoding 121 Note that the Prefix field contains the address prefix followed by 122 enough trailing bits to make the end of the field fall on an octet 123 boundary. The value of the trailing bits is irrelevant. 125 4. Address Prefix ORF Matching 127 In addition to the general matching rules defined in [BGP-ORF], 128 several Address Prefix ORF specific matching rules are defined as 129 follows. 131 Consider an Address Prefix ORF entry, and a route maintained by a BGP 132 speaker with NLRI in the form of . 134 The route is considered as "no match" to the ORF entry if the NLRI is 135 neither more specific than, nor equal to, the fields 136 of the ORF entry. 138 When the NLRI is either more specific than, or equal to, the fields of the ORF entry, the route is considered as a match 140 to the ORF entry only if the NLRI match condition as listed in Table 141 1 is satisfied. 143 ORF Entry NLRI 144 Minlen Maxlen Match Condition 145 +------------------------------------------------------+ 146 | un-spec. un-spec. NLRI.legnth == ORF.length | 147 +------------------------------------------------------+ 148 | specified un-spec. NLRI.length >= ORF.Minlen | 149 +------------------------------------------------------+ 150 | un-spec. specified NLRI.length <= ORF.Maxlen | 151 +------------------------------------------------------+ 152 | specified specified NLRI.length >= ORF.Minlen | 153 | AND NLRI.length <= ORF.Maxlen | 154 +------------------------------------------------------+ 156 Table 1: Address Prefix ORF Matching 158 When more than one Address Prefix ORF entry match the NLRI of the 159 route, the "first-match" rule applies. That is, the ORF entry with 160 the smallest sequence number (among all the matching ORF entries) is 161 considered as the sole match, and it would determine whether the 162 route should be advertised. 164 The assignment of the sequence numbers is a local matter for the BGP 165 speaker that sends the Address Prefix ORF entries. 167 5. IANA Considerations 169 This document specifies a new Outbound Route Filtering (ORF) type, 170 Address Prefix ORF. The value of the ORF-type is 64. 172 6. Security Considerations 174 This extension to BGP does not change the underlying security issues. 176 7. Normative References 178 [BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 179 4 (BGP-4)", RFC 4271, January 2006. 181 [BGP-MP] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, 182 "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. 184 [BGP-ORF] Chen, E., and Rekhter, Y., "Outbound Route Filtering 185 Capability for BGP-4", draft-ietf-idr-route-filter-15.txt, July 2006. 187 8. Author Information 189 Enke Chen 190 Cisco Systems, Inc. 191 170 W. Tasman Dr. 192 San Jose, CA 95134 194 EMail: enkechen@cisco.com 196 Srihari R. Sangli 197 Cisco Systems, Inc. 198 170 W. Tasman Dr. 199 San Jose, CA 95134 201 EMail: rsrihari@cisco.com 203 9. Intellectual Property Considerations 205 The IETF takes no position regarding the validity or scope of any 206 Intellectual Property Rights or other rights that might be claimed to 207 pertain to the implementation or use of the technology described in 208 this document or the extent to which any license under such rights 209 might or might not be available; nor does it represent that it has 210 made any independent effort to identify any such rights. Information 211 on the procedures with respect to rights in RFC documents can be 212 found in BCP 78 and BCP 79. 214 Copies of IPR disclosures made to the IETF Secretariat and any 215 assurances of licenses to be made available, or the result of an 216 attempt made to obtain a general license or permission for the use of 217 such proprietary rights by implementers or users of this 218 specification can be obtained from the IETF on-line IPR repository at 219 http://www.ietf.org/ipr. 221 The IETF invites any interested party to bring to its attention any 222 copyrights, patents or patent applications, or other proprietary 223 rights that may cover technology that may be required to implement 224 this standard. Please address the information to the IETF at ietf- 225 ipr@ietf.org. 227 10. Full Copyright Notice 229 Copyright (C) The Internet Society (2006). This document is subject 230 to the rights, licenses and restrictions contained in BCP 78, and 231 except as set forth therein, the authors retain all their rights. 233 This document and the information contained herein are provided on an 234 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 235 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 236 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 237 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 238 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 239 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.