idnits 2.17.1 draft-chen-bgp-ext-community-orf-00.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 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 159. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 130. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 137. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 143. ** 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 3 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 4 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 -- 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) == Outdated reference: A later version (-17) exists of draft-ietf-idr-route-filter-14 Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Enke Chen 3 Internet Draft Cisco Systems 4 Expiration Date: December 2006 Yakov Rekhter 5 Juniper Networks 7 Extended Community Based Outbound Route Filter for BGP-4 9 draft-chen-bgp-ext-community-orf-00.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Abstract 36 This document defines a new Outbound Router Filter type for BGP, 37 termed "Extended Community Outbound Route Filter", that can be used 38 to perform extended community based route filtering. 40 1. Specification of Requirements 42 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 43 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 44 document are to be interpreted as described in RFC2119 [RFC2119]. 46 2. Introduction 48 The Cooperative Outbound Route Filtering Capability defined in [BGP- 49 ORF] provides a mechanism for a BGP speaker to send to its BGP peer a 50 set of Outbound Route Filters (ORFs) that can be used by its peer to 51 filter its outbound routing updates to the speaker. 53 This document defines a new Outbound Router Filter type for BGP 54 [BGP-4], termed "Extended Community Outbound Route Filter", that can 55 be used to perform the extended community [BGP-EXT-COMMUNITIES] based 56 route filtering. 58 3. Extended Communities ORF-Type 60 The Extended Community ORF-Type allows to express ORFs in terms of 61 BGP Extended Communities. That is, the Extended Communities ORF-Type 62 provides Extended Communities-based route filtering. 64 Conceptually the ORF-value of the Extended Communities ORF-Type 65 consists of a single Extended Community. 67 The sender SHOULD set the value of the Match field to PERMIT; the 68 receiver SHOULD ignore the value of the Match field. 70 The remote peer should consider only those routes whose Extended 71 Communities attribute has at least one Extended Community in common 72 with the Extended Communities list specified in the ORF. 74 4. Extended Communities ORF Encoding 76 The value of the ORF-Type for the Extended Communities ORF-Type is 3. 78 The type-specific part of Extended Communities ORF-Type consists of a 79 single Extended Community encoded as an eight-octets field. 81 5. IANA Considerations 83 This document specifies a new Outbound Route Filtering (ORF) type, 84 Extended Community ORF. The value of the ORF-type is 3. 86 6. Security Considerations 88 This extension to BGP does not change the underlying security issues. 90 7. Normative References 92 [BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 93 (BGP-4)", RFC4271, January 2006. 95 [BGP-EXT-COMMUNITIES] Sangli, S., Tappan, D., and Y. Rekhter, "BGP 96 Extended Communities Attribute", RFC4360, February 2006. 98 [BGP-ORF] Chen, E., and Rekhter, Y., "Cooperative Route Filtering 99 Capability for BGP-4", draft-ietf-idr-route-filter-14.txt, June 2006. 101 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 102 Requirement Levels", BCP 14, RFC 2119, March 1997. 104 8. Author Information 106 Enke Chen 107 Cisco Systems, Inc. 108 170 W. Tasman Dr. 109 San Jose, CA 95134 111 EMail: enkechen@cisco.com 113 Yakov Rekhter 114 Juniper Networks, Inc. 115 1194 N. Mathilda Ave 116 Sunnyvale, CA 94089 117 EMail: yakov@juniper.net 119 9. Intellectual Property Considerations 121 This section is taken from Section 5 of RFC 3668. 123 The IETF takes no position regarding the validity or scope of any 124 Intellectual Property Rights or other rights that might be claimed to 125 pertain to the implementation or use of the technology described in 126 this document or the extent to which any license under such rights 127 might or might not be available; nor does it represent that it has 128 made any independent effort to identify any such rights. Information 129 on the procedures with respect to rights in RFC documents can be 130 found in BCP 78 and BCP 79. 132 Copies of IPR disclosures made to the IETF Secretariat and any 133 assurances of licenses to be made available, or the result of an 134 attempt made to obtain a general license or permission for the use of 135 such proprietary rights by implementers or users of this 136 specification can be obtained from the IETF on-line IPR repository at 137 http://www.ietf.org/ipr. 139 The IETF invites any interested party to bring to its attention any 140 copyrights, patents or patent applications, or other proprietary 141 rights that may cover technology that may be required to implement 142 this standard. Please address the information to the IETF at ietf- 143 ipr@ietf.org. 145 10. Copyright Notice 147 Copyright (C) The Internet Society (2006). 149 This document is subject to the rights, licenses and restrictions 150 contained in BCP 78, and except as set forth therein, the authors 151 retain all their rights. 153 This document and the information contained herein are provided on an 154 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 155 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 156 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 157 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 158 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 159 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.