idnits 2.17.1 draft-richardson-bgp4-confed-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 307 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 3 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 34 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 8469 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 1965 (Obsoleted by RFC 3065) 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 Confederations 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 "Autonomous System Confederations for BGP" [RFC1965]. 56 2. Overview 58 These objects are used to control and manage a BGP-4 implementation 59 that supports AS Confederations [RFC1965]. 61 This MIB defines a system-wide scalar object, and extends one table 62 defined in [BGP-MIB]: the BGP Peer Table. 64 This MIB defines the following primary objects: 66 - bgpConfederationId { bgp 12 1 } 68 The locally configured Confederation ID Number. 70 - bgpPeerConfedTable { bgp 12 2 } 72 Whether each peer is in the same Confederation as the router. 74 3. Definitions 76 BGP-CONFED-MIB DEFINITIONS ::= BEGIN 78 IMPORTS 79 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 80 mib-2, 81 FROM SNMPv2-SMI 82 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 83 FROM SNMPv2-CONF 84 TruthValue 85 FROM SNMPv2-TC 86 bgp 87 FROM BGP-MIB; 89 bgpConfed MODULE-IDENTITY 90 LAST-UPDATED "200102230000Z" 91 ORGANIZATION "IETF IDR Working Group" 92 CONTACT-INFO "E-mail: idr@merit.net 94 Mathew Richardson (Author) 95 E-mail: mrr@nexthop.com 96 Shane Wright (Author) 97 E-mail: swright@nexthop.com 98 517 W. William Street 99 Ann Arbor, MI 48103-4943 100 Tel: +1 734 973-2200 101 Fax: +1 734 615-3241 103 Susan Hares (Editor) 104 517 W. William Street 105 Ann Arbor, MI 48103-4943 106 Tel: +1 734 973-2200 107 Fax: +1 734 615-3241 108 E-mail: skh@nexthop.com" 110 REVISION "200102230000Z" 111 DESCRIPTION 112 "Extension of the MIB module for BGP-4 to include 113 about BGP Confederations." 114 REFERENCE 115 "RFC 1965 - Autonomous System Confederations for BGP" 116 "RFC 1771 - Border Gateway Protocol version 4 (BGP-4)" 118 ::= { bgp 12 } 120 bgpConfederationId OBJECT-TYPE 121 SYNTAX INTEGER (0..65535) 122 MAX-ACCESS read-only 123 STATUS current 124 DESCRIPTION 125 "The local Confederation Identification Number. A value 126 of zero (0) indicates the absence of this value." 127 REFERENCE 128 "RFC 1965 - Autonomous System Confederations for BGP" 129 ::= { bgpConfed 1 } 131 bgpPeerConfedTable OBJECT-TYPE 132 SYNTAX SEQUENCE OF BgpPeerConfedEntry 133 MAX-ACCESS not-accessible 134 STATUS current 135 DESCRIPTION 136 "BGP Peer Confederation Table. This table contains 137 information on whether a given peer is in the same 138 Confederation as the router." 139 ::= { bgpConfed 2 } 141 bgpPeerConfedEntry OBJECT-TYPE 142 SYNTAX BgpPeerConfedEntry 143 MAX-ACCESS not-accessible 144 STATUS current 145 DESCRIPTION 146 "Information on whether a given peer is in the same 147 Confederation as the router." 148 AUGMENTS { bgpPeerEntry } 149 ::= { bgpPeerConfedTable 1 } 151 BgpPeerConfedEntry ::= SEQUENCE { 152 bgpPeerInConfederation 153 TruthValue 154 } 156 bgpPeerInConfederation OBJECT-TYPE 157 SYNTAX TruthValue 158 MAX-ACCESS read-only 159 STATUS current 160 DESCRIPTION 161 "This value indicates whether the given peer is in our 162 confederation or not." 163 ::= { bgpPeerConfedEntry 1 } 165 END 167 4. Intellectual Property 169 The IETF takes no position regarding the validity or scope of any 170 intellectual property or other rights that might be claimed to 171 pertain to the implementation or use of the technology described in 172 this document or the extent to which any license under such rights 173 might or might not be available; neither does it represent that it 174 has made any effort to identify any such rights. Information on the 175 IETF's procedures with respect to rights in standards-track and 176 standards-related documentation can be found in BCP-11. Copies of 177 claims of rights made available for publication and any assurances of 178 licenses to be made available, or the result of an attempt made to 179 obtain a general license or permission for the use of such 180 proprietary rights by implementors or users of this specification can 181 be obtained from the IETF Secretariat. 183 5. Acknowledgements 185 The authors would like to thank the following individuals without 186 whom this document would never have been possible: 188 J. Haas, NextHop Technologies 190 6. References 192 [BGP-MIB] Hares, S., Haas, J., "Definitions of Managed Objects for the 193 Fourth Version of Border Gateway Protocol (BGP-4)", 194 draft-ietf-idr-bgp4-mib-05.txt, December 2001. 196 [RFC1965] Traina, P. "Autonomous System Confederations for BGP", 197 RFC-1965, June 1996. 199 7. Security Considerations 201 Security considerations are beyond the scope of this document. See 202 [BGP-MIB] for a more detailed discussion of the security implications 203 of this document. 205 8. Authors' Address 207 Mathew Richardson 208 NextHop Technologies 209 517 W. William 210 Ann Arbor, MI 48103-4943 211 Phone: +1 734 973-2200 212 Fax: +1 734 615-3241 213 Email: mrr@nexthop.com 215 Shane Wright 216 NextHop Technologies 217 517 W. William 218 Ann Arbor, MI 48103-4943 219 Phone: +1 734 973-2200 220 Fax: +1 734 615-3241 221 Email: swright@nexthop.com 223 Susan Hares 224 NextHop Technologies 225 517 W. William 226 Ann Arbor, MI 48103-4943 227 Phone: +1 734 973-2200 228 Fax: +1 734 615-3241 229 Email: skh@nexthop.com 231 9. Full Copyright Statement 233 Copyright (C) The Internet Society (1999). All Rights Reserved. 235 This document and translations of it may be copied and furnished to 236 others, and derivative works that comment on or otherwise explain it 237 or assist in its implementation may be prepared, copied, published 238 and distributed, in whole or in part, without restriction of any 239 kind, provided that the above copyright notice and this paragraph are 240 included on all such copies and derivative works. However, this 241 document itself may not be modified in any way, such as by removing 242 the copyright notice or references to the Internet Society or other 243 Internet organizations, except as needed for the purpose of 244 developing Internet standards in which case the procedures for 245 copyrights defined in the Internet Standards process must be 246 followed, or as required to translate it into languages other than 247 English. 249 The limited permissions granted above are perpetual and will not be 250 revoked by the Internet Society or its successors or assigns. 252 This document and the information contained herein is provided on an 253 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 254 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 255 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 256 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 257 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 259 Expires August 2001