INTERNET DRAFT Kaj Tesink Telcordia Technologies August 16, 2004 Definitions of Entity Manufacturing and URN Managed Objects Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it describes additional objects that supplement those defined in the Definitions of Managed Objects for the Entity MIB document [RFCzzzz]. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 1] Internet Draft 08/16/2004 Table of Contents 1 Conventions ............................................... 3 2 The Internet-Standard Management Framework ................ 3 3 Overview .................................................. 3 3.1 entSupplPhysicalManufacturingDate ....................... 3 3.2 entSupplPhysicalUris .................................... 3 4 Object Definitions ........................................ 5 5 Intellectual Property ..................................... 9 6 Acknowledgments ........................................... 9 7 Security Considerations ................................... 10 8 References ................................................ 11 8.1 Normative References .................................... 11 8.2 Informative References .................................. 11 9 Author's Address .......................................... 11 Full Copyright Statement ................................... 11 Expires 02/16/2005Entity Manufacturing and URN Objects [Page 2] Internet Draft 08/16/2004 1. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL", when they appear in this document, are to be interpreted as described in RFC 2119 [RFC2119]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Overview The objects defined in this memo are used in conjunction with objects defined in the Entity MIB [RFCzzzz]. The MIB module defined in this memo is a sparse augmentation of the entPhysicalTable of the ENTITY- MIB -- i.e., it is REQUIRED that an agent implementing objects defined in this memo also implement the relevant ENTITY-MIB objects. The purpose of the augmentation of the entPhysicalTable is to define a managed object for the manufacturing date of a managed entity, and a managed object to support additional information related to the managed entity. 3.1. entSupplPhysicalManufacturingDate This object contains the date of manufacturing of the managed entity. If the manufacturing date is unknown or not supported the object is not instantiated. 3.2. entSupplPhysicalUris This object provides additional identification information about the physical entity. This object may be used to encode for example a URI containing a Common Language Equipment Identifier (CLEI) URI [RFCwwww] for the managed physical entity. If no additional identification information is known or supported about the physical Expires 02/16/2005Entity Manufacturing and URN Objects [Page 3] Internet Draft 08/16/2004 entity the object is not instantiated. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 4] Internet Draft 08/16/2004 4. Object Definitions ENTSUPPL-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, transmission FROM SNMPv2-SMI DateAndTime FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF entPhysicalIndex FROM ENTITY-MIB; entitySupplMIB MODULE-IDENTITY LAST-UPDATED "200408160000Z" -- August 16, 2004 ORGANIZATION "IETF Entity MIB Working Group" CONTACT-INFO "WG charter: http://www.ietf.org/html.charters/entmib-charter.html Mailing Lists: General Discussion: entmib@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/entmib Chair: Margaret Wasserman Postal: Tel: E-mail: margaret@thingmagic.com Author: Kaj Tesink Postal: One Telcordia Drive Piscataway, NJ 08854 USA Tel: +1 732-699-6068 E-mail: kaj@research.telcordia.com" Expires 02/16/2005Entity Manufacturing and URN Objects [Page 5] Internet Draft 08/16/2004 DESCRIPTION "The objects in this MIB module are used in conjunction with objects in the ENTITY-MIB to manage entities Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." -- RFC Ed.: replace yyyy with actual RFC number & remove this notice REVISION "200408160000Z " -- August 16, 2004 DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy with actual RFC number & remove this notice ::= { transmission XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice Expires 02/16/2005Entity Manufacturing and URN Objects [Page 6] Internet Draft 08/16/2004 -- The main sections of the module entitySupplObjects OBJECT IDENTIFIER ::= { entitySupplMIB 1 } entitySupplConformance OBJECT IDENTIFIER ::= { entitySupplMIB 2 } -- These objects provide extensions to the entPhysicalTable. entSupplPhysicalTable OBJECT-TYPE SYNTAX SEQUENCE OF EntSupplPhysicalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for supplementary objects to the entPhysicalTable." ::= { entitySupplObjects 1 } entSupplPhysicalEntry OBJECT-TYPE SYNTAX EntSupplPhysicalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the entSupplPhysicalTable. For each instance of this object there MUST be a corresponding instance of entPhysicalEntry." INDEX { entPhysicalIndex } ::= { entSupplPhysicalTable 1 } EntSupplPhysicalEntry ::= SEQUENCE { entSupplPhysicalManufacturingDate DateAndTime, entSupplPhysicalUris OCTET STRING } entSupplPhysicalManufacturingDate OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The manufacturing date for the physical entity." ::= { entSupplPhysicalEntry 1 } entSupplPhysicalUris OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS current Expires 02/16/2005Entity Manufacturing and URN Objects [Page 7] Internet Draft 08/16/2004 DESCRIPTION "This object contains additional identification information about the physical entity. The object contains URIs and therefore the syntax of this object must conform to RFC 2396 section 2. Multiple URIs may be separated by white space characters." ::= { entSupplPhysicalEntry 2 } -- -- Conformance Statements -- entitySupplGroups OBJECT IDENTIFIER ::= { entitySupplConformance 1 } entitySupplCompliances OBJECT IDENTIFIER ::= { entitySupplConformance 2 } -- Object Groups entitySupplPhysicalGroup OBJECT-GROUP OBJECTS { entSupplPhysicalManufacturingDate, entSupplPhysicalUris } STATUS current DESCRIPTION "A collection of supplemental objects for to support physical entity features." ::= { entitySupplGroups 1 } -- Compliance Statements entitySupplCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities that support this module. Compliance with the entity3Compliance statement of the ENTITY-MIB is prerequisite." MODULE -- this module MANDATORY-GROUPS { entitySupplPhysicalGroup } OBJECT entSupplPhysicalUris MIN-ACCESS read-only Expires 02/16/2005Entity Manufacturing and URN Objects [Page 8] Internet Draft 08/16/2004 DESCRIPTION "Write access is not required." ::= { entitySupplCompliances 1 } END 5. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 6. Acknowledgments The contributions of the Entity MIB Working Group members are gratefully acknowledged. Special thanks go to Mike Heard, Juergen Schoenwaelder, Dave Perkins and Dan Romascanu. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 9] Internet Draft 08/16/2004 7. Security Considerations entSupplPhysicalInfo defined in this MIB module has a MAX-ACCESS clause of read-write; erroreous or unauthorized Writing of this object will result in the provision of misleading information to network management systems. The user of this MIB module must therefore be aware that support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The readable objects in this MIB module (i.e., those with MAX-ACCESS other than not-accessible) may be considered sensitive in some environments since, collectively, they provide information about the managed entities and can reveal some aspects of their configuration. In such environments it is important to control even GET and NOTIFY access to these objects and possibly even to encrypt their values when sending them over the network via SNMP. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 10] Internet Draft 08/16/2004 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFCzzzz] Bierman, A., McCloghrie, K., "Entity MIB (Version 3)", RFCzzzz. 8.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFCwwww] Tesink, K., Robert H. Fox, "A Uniform Resource Name (URN) Namespace for the CLEI Code", RFC wwww, August 2004. 9. Author's Address Kaj Tesink One Telcordia Drive Piscataway, NJ 08854 USA Phone: +1 732 699-6068 EMail: kaj@research.telcordia.com Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it Expires 02/16/2005Entity Manufacturing and URN Objects [Page 11] Internet Draft 08/16/2004 or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 12] Internet Draft 08/16/2004 ************************************************************ * NOTES TO RFC Editor (to be removed prior to publication) * * * * 1.) The normative references [RFCwwww] and [RFCzzzz] * * must be updated to point to the appropriate * * RFC when the corresponding Internet Draft is published, * * and all occurrences of the reference tags must be * * changed. * * * * 2.) Please replace all occurrences of "yyyy" in the * * DESCRIPTION clause of the MODULE-IDENTITY invocation * * in Section 4 with the RFC number assigned to this * * specification and remove the accompanying notes. * * * * 3.) Please replace "XXX" in the MODULE-IDENTITY value * * with an IANA-assigned value under the 'transmission' * * subtree and remove the accompanying note. * * * ************************************************************ Expires 02/16/2005Entity Manufacturing and URN Objects [Page 13]