idnits 2.17.1 draft-richardson-bgp4-reflect-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 380 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 90 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 8468 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 ** Obsolete normative reference: RFC 2796 (Obsoleted by RFC 4456) Summary: 9 errors (**), 0 flaws (~~), 4 warnings (==), 2 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 Route Reflection 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 Route Reflective - An Alternative to Full Mesh IBGP" [RFC2796]. 56 2. Overview 58 These objects are used to control and manage a BGP-4 implementation 59 that supports Route Reflection [RFC2796]. 61 This MIB defines a system-wide scalar object, and extends two tables 62 defined in [BGP-MIB]: the BGP Peer Table, and the BGP-4 Received 63 Path Attribute Table. 65 - bgpClusterId { bgp 11 1 } 67 The locally configured Cluster-ID. 69 - bgpPeerReflectTable { bgp 11 2 } 71 This table maintains information on whether each peer is configured 72 as a reflector client of this router. 74 - bgp4ReflectTable { bgp 11 3 } 76 This table maintains information about the Route Reflection specific 77 path attributes (Cluster List and Originator-ID) received with routes. 79 3. Definitions 81 BGP4-REFLECT-MIB DEFINITIONS ::= BEGIN 83 IMPORTS 84 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 85 IpAddress, mib-2 86 FROM SNMPv2-SMI 87 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 88 FROM SNMPv2-CONF 89 TruthValue 90 FROM SNMPv2-TC 91 bgp 92 FROM BGP-MIB; 94 bgpReflect MODULE-IDENTITY 95 LAST-UPDATED "200102230000Z" 96 ORGANIZATION "IETF IDR Working Group" 97 CONTACT-INFO "E-mail: idr@merit.net 99 Mathew Richardson (Author) 100 E-mail: mrr@nexthop.com 101 Shane Wright (Author) 102 E-mail: swright@nexthop.com 103 517 W. William Street 104 Ann Arbor, MI 48103-4943 105 Tel: +1 734 973-2200 106 Fax: +1 734 615-3241 108 Susan Hares (Editor) 109 517 W. William Street 110 Ann Arbor, MI 48103-4943 111 Tel: +1 734 973-2200 112 Fax: +1 734 615-3241 113 E-mail: skh@nexthop.com" 115 REVISION "200102230000Z" 116 DESCRIPTION 117 "Extension of the MIB module for BGP-4 to include 118 information about attributes and characteristics defined 119 in BGP Route Reflection." 120 REFERENCE 121 "RFC 2796 - BGP Route Reflection" 122 ::= { bgp 11 } 124 bgpClusterId OBJECT-TYPE 125 SYNTAX IpAddress 126 MAX-ACCESS read-only 127 STATUS current 128 DESCRIPTION 129 "The configured Cluster-ID of the local router. A value 130 of 0.0.0.0 indicates the absence of this value." 131 REFERENCE 132 "RFC 2796 - BGP Route Reflection" 133 ::= { bgpReflect 1 } 135 bgpPeerReflectTable OBJECT-TYPE 136 SYNTAX SEQUENCE OF BgpPeerReflectEntry 137 MAX-ACCESS not-accessible 138 STATUS current 139 DESCRIPTION 140 "BGP Peer Reflect Table. This table maintains information 141 about whether each peer is a Route Reflector." 142 REFERENCE 143 "RFC 2796 - BGP Route Reflection" 144 ::= { bgpReflect 2 } 146 bgpPeerReflectEntry OBJECT-TYPE 147 SYNTAX BgpPeerReflectEntry 148 MAX-ACCESS not-accessible 149 STATUS current 150 DESCRIPTION 151 "Peer related information pertaining to Route Reflection." 152 REFERENCE 153 "RFC 2796 - BGP Route Reflection" 154 AUGMENTS { bgpPeerEntry } 155 ::= { bgpPeerReflectTable 1 } 157 BgpPeerReflectEntry ::= SEQUENCE { 158 bgpPeerIsReflectorClient 159 TruthValue 160 } 162 bgpPeerIsReflectorClient OBJECT-TYPE 163 SYNTAX INTEGER { 164 nonClient(0), 165 client(1), 166 meshedClient(2) 167 } 168 MAX-ACCESS read-only 169 STATUS current 170 DESCRIPTION 171 "This value indicates whether the given peer is a reflector 172 client of this router, or not. A value of nonClient 173 indicates that this peer is not a reflector client. A 174 value of client indicates that this peer is a reflector 175 client that is not fully meshed with other reflector 176 clients. A value of meshedClient indicates that the 177 peer is a reflector client and is fully meshed with all 178 other reflector clients." 179 REFERENCE 180 "RFC 2796 - BGP Route Reflection" 181 ::= { bgpPeerReflectEntry 1 } 183 bgp4ReflectTable OBJECT-TYPE 184 SYNTAX SEQUENCE OF Bgp4ReflectEntry 185 MAX-ACCESS not-accessible 186 STATUS current 187 DESCRIPTION 188 "BGP Reflect Table. This table contains the route 189 reflection specific path attributes received with a 190 given route." 191 REFERENCE 192 "RFC 2796 - BGP Route Reflection" 193 ::= { bgpReflect 3 } 195 bgp4ReflectEntry OBJECT-TYPE 196 SYNTAX Bgp4ReflectEntry 197 MAX-ACCESS not-accessible 198 STATUS current 199 DESCRIPTION 200 "Information about the route reflection specific path 201 attributes received with a given route." 202 AUGMENTS { bgp4PathAttrTable } 203 ::= { bgp4ReflectTable 1 } 205 Bgp4ReflectEntry ::= SEQUENCE { 206 bgp4PathAttrOriginatorId 207 IpAddress, 208 bgp4PathAttrClusterList 209 OCTET STRING, 210 } 212 bgp4PathAttrOriginatorId OBJECT-TYPE 213 SYNTAX IpAddress 214 MAX-ACCESS read-only 215 STATUS current 216 DESCRIPTION 217 "The Originator-ID identifying the router that initially 218 advertised this destination to a Route Reflector. A 219 value of 0.0.0.0 indicates the absence of this attribute. 220 This attribute is defined in [RFC2796]." 221 ::= { bgp4ReflectEntry 1 } 223 bgp4PathAttrClusterList OBJECT-TYPE 224 SYNTAX OCTET STRING (SIZE(0..4096)) 225 MAX-ACCESS read-only 226 STATUS current 227 DESCRIPTION 228 "A sequence of four octet long values representing the 229 reflection path that the route has passed. Each four 230 octet long value represents the ID of a cluster that 231 the route has traversed. A length of zero (0) indicates 232 the absence of this attribute. This attribute is defined 233 in [RFC2796]." 234 ::= { bgp4ReflectEntry 2 } 236 END 238 4. Intellectual Property 240 The IETF takes no position regarding the validity or scope of any 241 intellectual property or other rights that might be claimed to 242 pertain to the implementation or use of the technology described in 243 this document or the extent to which any license under such rights 244 might or might not be available; neither does it represent that it 245 has made any effort to identify any such rights. Information on the 246 IETF's procedures with respect to rights in standards-track and 247 standards-related documentation can be found in BCP-11. Copies of 248 claims of rights made available for publication and any assurances of 249 licenses to be made available, or the result of an attempt made to 250 obtain a general license or permission for the use of such 251 proprietary rights by implementors or users of this specification can 252 be obtained from the IETF Secretariat. 254 5. Acknowledgements 256 The authorse would like to thank the following individuals without 257 whom this document would never have been possible: 259 J. Haas, NextHop Technologies 261 6. References 263 [BGP-MIB] Hares, S., Haas, J., "Definitions of Managed Objects for the 264 Fourth Version of Border Gateway Protocol (BGP-4)", 265 draft-ietf-idr-bgp4-mib-05.txt, December 2001. 267 [RFC2796] Bates, T., Chandra, R., "BGP Route Reflection - An Alternative 268 to Full Mesh IBGP", RFC-2796, April 2000. 270 7. Security Considerations 272 Security considerations are beyond the scope of this document. See 273 [BGP-MIB] for a more detailed discussion of the security implications 274 of this document. 276 8. Authors' Address 278 Mathew Richardson 279 NextHop Technologies 280 517 W. William 281 Ann Arbor, MI 48103-4943 282 Phone: +1 734 973-2200 283 Fax: +1 734 615-3241 284 Email: mrr@nexthop.com 286 Shane Wright 287 NextHop Technologies 288 517 W. William 289 Ann Arbor, MI 48103-4943 290 Phone: +1 734 973-2200 291 Fax: +1 734 615-3241 292 Email: swright@nexthop.com 294 Susan Hares 295 NextHop Technologies 296 517 W. William 297 Ann Arbor, MI 48103-4943 298 Phone: +1 734 973-2200 299 Fax: +1 734 615-3241 300 Email: skh@nexthop.com 302 9. Full Copyright Statement 304 Copyright (C) The Internet Society (1999). All Rights Reserved. 306 This document and translations of it may be copied and furnished to 307 others, and derivative works that comment on or otherwise explain it 308 or assist in its implementation may be prepared, copied, published 309 and distributed, in whole or in part, without restriction of any 310 kind, provided that the above copyright notice and this paragraph are 311 included on all such copies and derivative works. However, this 312 document itself may not be modified in any way, such as by removing 313 the copyright notice or references to the Internet Society or other 314 Internet organizations, except as needed for the purpose of 315 developing Internet standards in which case the procedures for 316 copyrights defined in the Internet Standards process must be 317 followed, or as required to translate it into languages other than 318 English. 320 The limited permissions granted above are perpetual and will not be 321 revoked by the Internet Society or its successors or assigns. 323 This document and the information contained herein is provided on an 324 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 325 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 326 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 327 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 328 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 330 Expires August 2001