idnits 2.17.1 draft-richardson-bgp4-ext-comm-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 295 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 7 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** There are 35 instances of lines with control characters in the document. ** The abstract seems to contain references ([BGP-MIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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.) -- The document date (February 2001) is 8470 days in the past. Is this intentional? 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 (-15) exists of draft-ietf-idr-bgp4-mib-05 == Outdated reference: A later version (-09) exists of draft-ramachandra-bgp-ext-communities-08 -- Possible downref: Normative reference to a draft: ref. 'BGP-EXTCOMM' Summary: 8 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group M. Richardson 2 INTERNET DRAFT S. Wright 3 Expires August 2001 S. Hares 4 NextHop 5 February 2001 7 Definitions of Managed Objects 9 for the Extended Communities Attribute in Border 11 Gateway Protocol (BGP-4) 13 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC 2026. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet- Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Copyright Notice 38 Copyright (C) The Internet Society (1999). All Rights Reserved. 40 Abstract 42 This memo is an extension to the SNMP MIB. It specifies an IAB 43 standards track protocol for the Internet community, and requests 44 discussion and suggestions for improvements. This memo extends 45 the MIB defined in [BGP-MIB]. 47 Distribution of this memo is unlimited. Please forward comments to 48 idr@merit.net. 50 1. Introduction 52 This memo defines extensions to the MIB defined in [BGP-MIB]. In 53 particular, it describes managed objects based upon attributes defined 54 in "BGP Extended Communities Attribute" [BGP-EXTCOMM]. 56 2. Overview 58 These objects are used to control and manage a BGP-4 implementation 59 that supports BGP Extended Communities [BGP-EXTCOMM]. This MIB extends 60 one table defined in [BGP-MIB]: the BGP-4 Received Path Attribute Table. 62 This MIB defines the following primary objects: 64 - bgp4ExtCommTable { bgp 13 1 } 66 This table contains the set of extended communities received with each 67 incoming route. 69 3. Definitions 71 BGP4-EXT-COMM-MIB DEFINITIONS ::= BEGIN 73 IMPORTS 74 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 75 mib-2 76 FROM SNMPv2-SMI 77 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 78 FROM SNMPv2-CONF 79 bgp 80 FROM BGP-MIB; 82 bgpExtComm MODULE-IDENTITY 83 LAST-UPDATED "200102230000Z" 84 ORGANIZATION "IETF IDR Working Group" 85 CONTACT-INFO "E-mail: idr@merit.net 87 Mathew Richardson (Author) 88 E-mail: mrr@nexthop.com 89 Shane Wright (Author) 90 E-mail: swright@nexthop.com 91 517 W. William Street 92 Ann Arbor, MI 48103-4943 93 Tel: +1 734 973-2200 94 Fax: +1 734 615-3241 96 Susan Hares (Editor) 97 517 W. William Street 98 Ann Arbor, MI 48103-4943 99 Tel: +1 734 933-2200 100 Fax: +1 734 615-3241 101 E-mail: skh@nexthop.com" 103 REVISION "200102230000Z" 104 DESCRIPTION 105 "Extension of the MIB module for BGP-4 to include 106 information about the Extended Communities attribute 107 associated with incoming routes." 108 REFERENCE 109 "BGP-EXTCOMM - BGP Extended Communities Attribute" 111 ::= { bgp 13 } 113 bgp4ExtCommTable OBJECT-TYPE 114 SYNTAX SEQUENCE OF Bgp4ExtCommEntry 115 MAX-ACCESS not-accessible 116 STATUS current 117 DESCRIPTION 118 "BGP Extended Communities Table. This table contains 119 information on the Extended Communities [BGP-EXTCOMM] 120 learned with incoming routes." 121 REFERENCE 122 "RFC 1771 - Border Gateway Protocol version 4 (BGP4)" 123 ::= { bgpExtComm 1 } 125 bgp4ExtCommEntry OBJECT-TYPE 126 SYNTAX Bgp4ExtCommEntry 127 MAX-ACCESS not-accessible 128 STATUS current 129 DESCRIPTION 130 "Information about the Extended Communities [BGP-EXTCOMM] 131 learned with a route." 132 AUGMENTS { bgp4PathAttrTable } 133 ::= { bgp4ExtCommTable 1 } 135 Bgp4ExtCommEntry ::= SEQUENCE { 136 bgp4PathAttrExtComm 137 OCTET STRING 138 } 140 bgp4PathAttrExtComm OBJECT-TYPE 141 SYNTAX OCTET STRING (SIZE(0..4096)) 142 MAX-ACCESS read-only 143 STATUS current 144 DESCRIPTION 145 "A sequence of values each eight octets long, and each 146 representing an extended community that was received 147 with the route. The values of each of the individual 148 octets may have semantic meaning. A length of zero (0) 149 indicates the absence of this attribute." 150 REFERENCE 151 "BGP-EXTCOMM - BGP Extended Communities Attribute" 152 ::= { bgp4ExtCommEntry 1 } 154 END 156 4. Intellectual Property 158 The IETF takes no position regarding the validity or scope of any 159 intellectual property or other rights that might be claimed to 160 pertain to the implementation or use of the technology described in 161 this document or the extent to which any license under such rights 162 might or might not be available; neither does it represent that it 163 has made any effort to identify any such rights. Information on the 164 IETF's procedures with respect to rights in standards-track and 165 standards-related documentation can be found in BCP-11. Copies of 166 claims of rights made available for publication and any assurances of 167 licenses to be made available, or the result of an attempt made to 168 obtain a general license or permission for the use of such 169 proprietary rights by implementors or users of this specification can 170 be obtained from the IETF Secretariat. 172 5. Acknowledgements 174 The authors would like to thank the following individuals without 175 whom this document would never have been possible: 177 J. Haas, NextHop Technologies 179 6. References 181 [BGP-MIB] Hares, S., Haas, J., "Definitions of Managed Objects for the 182 Fourth Version of Border Gateway Protocol (BGP-4)", 183 draft-ietf-idr-bgp4-mib-05.txt, December 2001. 185 [BGP-EXTCOMM] Ramachandra, S., Tappan, D., "BGP Extended Communities 186 Attribute", draft-ramachandra-bgp-ext-communities-08.txt, 187 February 2001. 189 7. Security Considerations 191 Security considerations are beyond the scope of this document. See 192 [BGP-MIB] for a more detailed discussion of the security implications 193 of this document. 195 8. Authors' Address 197 Mathew Richardson 198 NextHop Technologies 199 517 W. William 200 Ann Arbor, MI 48103-4943 201 Phone: +1 734 973-2200 202 Fax: +1 734 615-3241 203 Email: mrr@nexthop.com 205 Shane Wright 206 NextHop Technologies 207 517 W. William 208 Ann Arbor, MI 48103-4943 209 Phone: +1 734 973-2200 210 Fax: +1 734 615-3241 211 Email: swright@nexthop.com 213 Susan Hares 214 NextHop Technologies 215 517 W. William 216 Ann Arbor, MI 48103-4943 217 Phone: +1 734 973-2200 218 Fax: +1 734 615-3241 219 Email: skh@nexthop.com 221 9. Full Copyright Statement 223 Copyright (C) The Internet Society (1999). All Rights Reserved. 225 This document and translations of it may be copied and furnished to 226 others, and derivative works that comment on or otherwise explain it 227 or assist in its implementation may be prepared, copied, published 228 and distributed, in whole or in part, without restriction of any 229 kind, provided that the above copyright notice and this paragraph are 230 included on all such copies and derivative works. However, this 231 document itself may not be modified in any way, such as by removing 232 the copyright notice or references to the Internet Society or other 233 Internet organizations, except as needed for the purpose of 234 developing Internet standards in which case the procedures for 235 copyrights defined in the Internet Standards process must be 236 followed, or as required to translate it into languages other than 237 English. 239 The limited permissions granted above are perpetual and will not be 240 revoked by the Internet Society or its successors or assigns. 242 This document and the information contained herein is provided on an 243 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 244 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 245 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 246 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 247 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 249 Expires August 2001