idnits 2.17.1 draft-ietf-idr-bgp-prefix-orf-03.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 212. ** 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. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. 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 146 has weird spacing: '...ecified un-s...' == Line 150 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 174, 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-13 Summary: 7 errors (**), 0 flaws (~~), 8 warnings (==), 4 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: November 2006 Cisco Systems 6 Address Prefix Based Outbound Route Filter for BGP-4 8 draft-ietf-idr-bgp-prefix-orf-03.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 Cooperative Outbound Route Filtering Capability defined in [BGP- 45 ORF] provides a mechanism for a BGP speaker to send to its BGP peer a 46 set of Outbound Route Filters (ORFs) that can be used by its peer to 47 filter 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 follows. 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 Note that the Prefix field contains the address prefix followed by 120 enough trailing bits to make the end of the field fall on an octet 121 boundary. The value of the trailing bits is irrelevant. 123 4. Address Prefix ORF Matching 125 In addition to the general matching rules defined in [BGP-ORF], 126 several Address Prefix ORF specific matching rules are defined as 127 follows. 129 Consider an Address Prefix ORF entry, and a route maintained by a BGP 130 speaker with NLRI in the form of . 132 The route is considered as "no match" to the ORF entry if the NLRI is 133 neither more specific than, nor equal to, the fields 134 of the ORF entry. 136 When the NLRI is either more specific than, or equal to, the fields of the ORF entry, the route is considered as a match 138 to the ORF entry only if the NLRI match condition as listed in the 139 following table is satisfied. 141 ORF Entry NLRI 142 Minlen Maxlen Match Condition 143 +------------------------------------------------------+ 144 | un-spec. un-spec. NLRI.legnth == ORF.length | 145 +------------------------------------------------------+ 146 | specified un-spec. NLRI.length >= ORF.Minlen | 147 +------------------------------------------------------+ 148 | un-spec. specified NLRI.length <= ORF.Maxlen | 149 +------------------------------------------------------+ 150 | specified specified NLRI.length >= ORF.Minlen | 151 | AND NLRI.length <= ORF.Maxlen | 152 +------------------------------------------------------+ 154 When more than one Address Prefix ORF entry match the NLRI of the 155 route, the "first-match" rule applies. That is, the ORF entry with 156 the smallest sequence number (among all the matching ORF entries) is 157 considered as the sole match, and it would determine whether the 158 route should be advertised. 160 The assignment of the sequence numbers is a local matter for the BGP 161 speaker that sends the Address Prefix ORF entries. 163 5. IANA Considerations 165 This document specifies a new Outbound Route Filtering (ORF) type, 166 Address Prefix ORF. The value of the ORF-type is 64. 168 6. Security Considerations 170 This extension to BGP does not change the underlying security issues. 172 7. Normative References 174 [BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 175 4 (BGP-4)", RFC 4271, January 2006. 177 [BGP-MP] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, 178 "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. 180 [BGP-ORF] Chen, E., and Rekhter, Y., "Cooperative Route Filtering 181 Capability for BGP-4", draft-ietf-idr-route-filter-13.txt, March 182 2006. 184 8. Author Information 186 Enke Chen 187 Cisco Systems, Inc. 188 170 W. Tasman Dr. 189 San Jose, CA 95134 191 EMail: enkechen@cisco.com 193 Srihari R. Sangli 194 Cisco Systems, Inc. 195 170 W. Tasman Dr. 196 San Jose, CA 95134 198 EMail: rsrihari@cisco.com 200 9. Full Copyright Notice 202 Copyright (C) The Internet Society (2006). This document is subject 203 to the rights, licenses and restrictions contained in BCP 78, and 204 except as set forth therein, the authors retain all their rights. 206 This document and the information contained herein are provided on an 207 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 208 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 209 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 210 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 211 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 212 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.