idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-tc-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 11, 2011) is 4667 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing Working Group J. Haas 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track July 11, 2011 5 Expires: January 12, 2012 7 Definitions of Textual Conventions for the Management of the Fourth 8 Version of Border Gateway Protocol (BGP-4) 9 draft-ietf-idr-bgp4-mibv2-tc-mib-03 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 which defines Textual Conventions for the management of BGP-4. The 15 intent is that these textual conventions will be used in BGP-related 16 MIB modules that would otherwise define their own representations. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 12, 2012. 35 Copyright Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. The Internet-Standard Management Framework . . . . . . . . . . 3 54 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 57 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 59 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 61 1. Introduction 63 This memo defines a portion of the Management Information Base (MIB) 64 which defines Textual Conventions for the management of BGP-4. The 65 intent is that these textual conventions will be used in BGP-related 66 MIB modules that would otherwise define their own representations. 68 See the BGP-4 specification [RFC4271] and Multiprotocol Extensions 69 for BGP-4 [RFC4760] for an introduction to the concepts these textual 70 conventions cover. 72 2. The Internet-Standard Management Framework 74 For a detailed overview of the documents that describe the current 75 Internet-Standard Management Framework, please refer to section 7 of 76 RFC 3410 [RFC3410]. 78 Managed objects are accessed via a virtual information store, termed 79 the Management Information Base or MIB. MIB objects are generally 80 accessed through the Simple Network Management Protocol (SNMP). 81 Objects in the MIB are defined using the mechanisms defined in the 82 Structure of Management Information (SMI). This memo specifies a MIB 83 module that is compliant to the SMIv2, which is described in STD 58, 84 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 85 [RFC2580]. 87 3. Definitions 89 BGP4V2-TC-MIB DEFINITIONS ::= BEGIN 91 IMPORTS 92 mib-2, MODULE-IDENTITY FROM SNMPv2-SMI 93 TEXTUAL-CONVENTION FROM SNMPv2-TC; 95 bgp4V2TC MODULE-IDENTITY 96 LAST-UPDATED "201101170000Z" 97 ORGANIZATION "IETF IDR Working Group" 98 CONTACT-INFO "E-mail: idr@ietf.org" 100 DESCRIPTION 101 "Textual conventions for BGP-4. 103 Copyright (C) The IETF Trust (2011). This 104 version of this MIB module is part of RFC XXX; 105 see the RFC itself for full legal notices." 106 -- RFC Editor - replace XXX with RFC number 108 REVISION "201101170000Z" 109 DESCRIPTION 110 "Initial version." 111 ::= { mib-2 XXX } 113 -- 114 -- Textual Conventions 115 -- 117 Bgp4V2IdentifierTC ::= TEXTUAL-CONVENTION 118 DISPLAY-HINT "1d." 119 STATUS current 120 DESCRIPTION 121 "The representation of a BGP Identifier. BGP Identifiers 122 are presented in the received network byte order. 124 The BGP Identifier is displayed as if it is an IP address, 125 even if it would be an illegal one." 126 REFERENCE 127 "RFC 4273, Section 4.2" 128 SYNTAX OCTET STRING(SIZE (4)) 130 Bgp4V2AddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION 131 STATUS current 132 DESCRIPTION 133 "The representation of a BGP AFI. The value of this object 134 should be restricted to be between the values of 0 and 135 65535." 136 REFERENCE 137 "RFC 4760, Section 3" 138 SYNTAX INTEGER { 139 ipv4(1), 140 ipv6(2) 141 } 143 Bgp4V2SubsequentAddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION 144 STATUS current 145 DESCRIPTION 146 "The representation of a BGP SAFI" 147 REFERENCE 148 "RFC 4760, Section 3. The value of this object should be 149 restricted to be between the values of 0 and 255." 150 SYNTAX INTEGER { 151 unicast(1), 152 multicast(2), 153 mpls(4) 154 } 156 END 158 4. Security Considerations 160 This module does not define any management objects. Instead, it 161 defines a set of textual conventions which may be used by other 162 modules which use the BGP-4 protocol to define management objects. 163 Meaningful security considerations can only be written in the MIB 164 modules that define management objects. Therefore, this document has 165 no impact on the security of the Internet. 167 5. IANA Considerations 169 IANA is requested to assign this MIB module an OID under mib-2. 171 6. References 173 6.1. Normative References 175 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 176 Schoenwaelder, Ed., "Structure of Management Information 177 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 179 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 180 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 181 STD 58, RFC 2579, April 1999. 183 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 184 "Conformance Statements for SMIv2", STD 58, RFC 2580, 185 April 1999. 187 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 188 Protocol 4 (BGP-4)", RFC 4271, January 2006. 190 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 191 "Multiprotocol Extensions for BGP-4", RFC 4760, 192 January 2007. 194 6.2. Informative References 196 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 197 "Introduction and Applicability Statements for Internet- 198 Standard Management Framework", RFC 3410, December 2002. 200 Author's Address 202 Jeffrey Haas 203 Juniper Networks 205 EMail: jhaas@juniper.net