idnits 2.17.1 draft-ietf-pce-tc-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force E. Stephan 2 Internet-Draft France Telecom 3 Intended status: Standards Track Q. Zhao 4 Created: October 25, 2009 Huawei Technology 5 Expires: March 25, 2009 D. King 6 Old Dog Consulting 8 Definitions of Textual Conventions for Path Computation Element 9 draft-ietf-pce-tc-mib-05 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 for use with network management protocols in the Internet community. 15 In particular, it defines Textual Conventions to represent commonly 16 used Path Computation Element (PCE) management information. The 17 intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and 18 used in PCE related MIB modules to avoid duplicating conventions. 20 Status of this Memo 22 This Internet-Draft is submitted to IETF in full conformance with 23 the provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 Copyright Notice 43 Copyright (c) 2009 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents in effect on the date of 48 publication of this document (http://trustee.ietf.org/license-info). 49 Please review these documents carefully, as they describe your rights 50 and restrictions with respect to this document. 52 This document may contain material from IETF Documents or IETF 53 Contributions published or made publicly available before November 54 10, 2008. The person(s) controlling the copyright in some of this 55 material may not have granted the IETF Trust the right to allow 56 modifications of such material outside the IETF Standards Process. 57 Without obtaining an adequate license from the person(s) controlling 58 the copyright in such materials, this document may not be modified 59 outside the IETF Standards Process, and derivative works of it may 60 not be created outside the IETF Standards Process, except to format 61 it for publication as an RFC or to translate it into languages other 62 than English. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. The Internet-Standard Management Framework . . . . . . . . . . 2 68 3. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 3 69 4. PCE Textual Conventions MIB Definitions . . . . . . . . . . . . 3 70 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 71 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 72 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 74 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 75 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 1. Introduction 79 This memo defines a portion of the Management Information Base (MIB) 80 for use with network management protocols in the Internet community. 81 In particular, it defines Textual Conventions to represent commonly 82 used Path Computation Element (PCE) management information. The 83 intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and 84 used in PCE related MIB modules to avoid duplicating conventions. 86 For an introduction to the concepts of PCE, see [RFC4655]. 88 2. The Internet-Standard Management Framework 90 For a detailed overview of the documents that describe the current 91 Internet-Standard Management Framework, please refer to section 7 of 92 RFC 3410 [RFC3410]. 94 Managed objects are accessed via a virtual information store, termed 95 the Management Information Base or MIB. MIB objects are generally 96 accessed through the Simple Network Management Protocol (SNMP). 97 Objects in the MIB are defined using the mechanisms defined in the 98 Structure of Management Information (SMI). This memo specifies a MIB 99 module that is compliant to the SMIv2, which is described in STD 58, 100 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 101 [RFC2580]. 103 3. Structure of the MIB Module 105 This MIB module defines PCE common SMI items. It defines the nodes 106 for the homing of the MIB modules and TC to be imported and used in 107 PCE related MIB modules. 109 PCE management information is arranged into 3 modules: 110 o PCE-TC-STD-MIB (defined in this memo) defined the root for homing 111 Standard PCE MIB modules; 112 o PCE-DISC-STD-MIB defines the management information for monitoring 113 PCE entities discovery; 114 o PCE-PCEP-STD-MIB defines the information for managing PCE 115 communication protocol; 117 4. PCE Textual Conventions MIB Definitions 119 PCE-TC-STD-MIB DEFINITIONS ::= BEGIN 121 IMPORTS 122 MODULE-IDENTITY, 123 experimental FROM SNMPv2-SMI 124 TEXTUAL-CONVENTION 125 FROM SNMPv2-TC; 127 pceTCDraftMIB MODULE-IDENTITY 128 LAST-UPDATED "200903020000Z" -- March 2, 2009 129 ORGANIZATION "Path Computation Element (PCE) Working Group" 130 CONTACT-INFO " 131 Stephan Emile 132 France Telecom 133 Email: emile.stephan@orange-ftgroup.com 134 Email comments directly to the PCE WG Mailing List at pce@ietf.org 135 WG-URL: http://www.ietf.org/html.charters/pce-charter.html" 136 DESCRIPTION 137 "This memo defines a portion of the Management Information Base 138 (MIB) for use with network management protocols in the Internet 139 community. In particular, it defines Textual Conventions to 140 represent commonly used Path Computation Element (PCE) 141 management information. The intent is that these TEXTUAL 142 CONVENTIONS (TCs) will be imported and used in PCE related MIB 143 modules to avoid duplicating conventions." 144 ::= { pceStdMIB 1 } 146 pceStdMIB OBJECT IDENTIFIER ::= { experimental 9999 } 148 -- RFC Editor: Please see the IANA Considerations Section. 150 -- 'experimental 9999' is a temporary root for running smilint. 152 -- 'pceStdMIB' will be homed in 'mib-2' 154 -- Textual Conventions (sorted alphabetically). 156 PcePcepIdentifier ::= TEXTUAL-CONVENTION 157 DISPLAY-HINT "1d.1d.1d.1d:1d:1d" 158 STATUS current 159 DESCRIPTION 160 "The LDP identifier is a six octet quantity which is used to 161 identify a PCE client." 162 SYNTAX OCTET STRING (SIZE (0..6)) 164 PceRoutingDomainID ::= TEXTUAL-CONVENTION 165 STATUS current 166 DESCRIPTION 167 "A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS 168 information element carries the identifier of a routing domain 169 (area, as) which type depends on both the routing protocol and 170 on the version of Internet protocol in use in this routing 171 domain. 173 This TC defines a common SMI type for the different kinds of 174 routing domain identifiers. 176 A PceRoutingDomainID value is always interpreted within the 177 context of an AddressFamilyNumbers value. Every usage of the 178 PceRoutingDomainID textual convention is required to specify 179 the AddressFamilyNumbers object which provides the context. 181 The value of an PceRoutingDomainID object must always be 182 consistent with the value of the associated 183 AddressFamilyNumbers object. 185 Following is the mapping between AddressFamilyNumbers type and 186 PceRoutingDomainID size: 187 ipV4(1): 188 PceRoutingDomainID is an InetAddressIPv4 corresponding to 189 the name of an OSPF area; 190 ipV6(2): 191 PceRoutingDomainID is an InetAddressIPv6 corresponding to 192 the name of an OSPF area; 193 nsap(3): 194 PceRoutingDomainID type is OCTET STRING (SIZE (0..20)), 195 corresponding to the name of an ISIS area (see RFC 1195); 196 asNumber(18) 197 PceRoutingDomainID type is OCTET STRING (SIZE (2)) 198 corresponding to the name of an Autonomous System. 199 " 200 SYNTAX OCTET STRING (SIZE (0..20)) 202 END 204 5. Security Considerations 206 This module defines only textual conventions. As security 207 considerations can only be written in MIB modules that define 208 management objects this document has no impact on the security of the 209 Internet. 211 6. IANA Considerations 213 IANA is requested to make a MIB OID assignment for pceStdMIB under 214 the mib-2 branch. 216 PCE related standards track MIB modules should be homed under the 217 pceStdMIB subtree. This document also requests IANA to assign { 218 pceStdMIB 1 } to the PCE-TC-STD-MIB specified in this document. 220 7. References 222 7.1. Normative References 224 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 225 Schoenwaelder, Ed., "Structure of Management Information 226 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 228 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 229 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 230 STD 58, RFC 2579, April 1999. 232 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 233 "Conformance Statements for SMIv2", STD 58, RFC 2580, 234 April 1999. 236 7.2. Informative References 238 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 239 "Introduction and Applicability Statements for Internet- 240 Standard Management Framework", RFC 3410, December 2002. 242 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 243 Element (PCE)-Based Architecture", RFC 4655, August 2006. 245 Author's Address 247 Stephan Emile 248 France Telecom 249 2 avenue Pierre Marzin 250 Lannion, F-22307 251 Fax: +33 2 96 05 18 52 252 Email: emile.stephan@orange-ftgroup.com 254 Quintin Zhao 255 Huawei Technology 256 125 Nagog Technology Park 257 Acton, MA 01719 258 US 259 Email: qzhao@huawei.com 261 Daniel King 262 Old Dog Consulting 263 UK 264 Email: daniel@olddog.co.uk