Enterprise Number for Documentation Use
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 5612.
|Authors||David Harrington, Pasi Eronen|
|Last updated||2015-10-14 (Latest revision 2009-03-02)|
|RFC stream||Internet Engineering Task Force (IETF)|
|IESG||IESG state||RFC 5612 (Informational)|
|Responsible AD||Dan Romascanu|
|Send notices to||(None)|
Network Working Group P. Eronen Internet-Draft Nokia Intended status: Informational D. Harrington Expires: September 3, 2009 Huawei Technologies (USA) March 2, 2009 Enterprise Number for Documentation Use draft-eronen-enterprise-number-documentation-01.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. 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. This Internet-Draft will expire on September 3, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document describes an Enterprise Number (also known as SMI Network Management Private Enterprise Code) for use in documentation. Eronen & Harrington Expires September 3, 2009 [Page 1] Internet-Draft Enterprise Number for Documentation Use March 2009 1. Introduction RFC 1065 [RFC1065] (later superceded by [RFC1155] and [RFC2578]) created a subtree (arc) of object identifiers (OIDs) for identifying management objects that are defined unilaterally by a single party, such as an enterprise. The subtree for a particular enterprise consists of the prefix "220.127.116.11.4.1.", followed by the Enterprise Number assigned for that enterprise. Enterprise Numbers are allocated by IANA, and are also known as "Private Enterprise Numbers", "Enterprise Codes", and "SMI (Structure of Management Information) Network Management Private Enterprise Codes". See [Application] for more information on how to request an Enterprise Number from IANA, and [Numbers] for the list of currently assigned numbers. Enterprise Numbers have also been used for many other purposes than OIDs in various protocols; for example: o "STRUCTURED-DATA" identifiers in Syslog [RFC5424] o "Vendor-Specific" RADIUS attributes [RFC2865] o Mobile IPv4 vendor/organization-specific extensions [RFC3115] o User-defined error information in RSVP [RFC5284] o Vendor options in DHCPv4 [RFC3925] o Enterprise-specific information elements in IP Flow Information Export (IPFIX) protocol [RFC5101] Documents related to these protocols may include examples that contain Enterprise Numbers. To reduce the likelihood of conflict and confusion, this document specifies an Enterprise Number for use in examples in RFCs, books, documentation, and the like. 2. Enterprise Number for Documentation Use The Enterprise Number 32473 has been allocated for use in examples in RFCs, books, documentation, and the like. 3. IANA Considerations IANA is asked to update (has updated) the registration for Enterprise Number 32473 to point to this RFC. 4. Security Considerations Allocating an enterprise number for documentation use does not have Eronen & Harrington Expires September 3, 2009 [Page 2] Internet-Draft Enterprise Number for Documentation Use March 2009 any direct impact on security. 5. Acknowledgments The need for an Enterprise Number for documentation use was identified by Rainer Gerhards for the examples in [RFC5424]. The authors would also like to thank Michelle Cotton for her help, and Alfred Hoenes for his comments. This document borrows text from [RFC5398] and ideas from [RFC4735]. 6. References 6.1. Normative References [Numbers] IANA, "Private Enterprise Numbers", URL http://www.iana.org/assignments/enterprise-numbers, 2009. 6.2. Informative References [Application] IANA, "Private Enterprise Number (PEN) Request Template", URL http://pen.iana.org/pen/PenApplication.page, 2009. [RFC1065] Rose, M. and K. McCloghrie, "Structure and identification of management information for TCP/IP-based internets", RFC 1065, August 1988. [RFC1155] Rose, M. and K. McCloghrie, "Structure and identification of management information for TCP/IP-based internets", STD 16, RFC 1155, May 1990. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/ Organization-Specific Extensions", RFC 3115, April 2001. [RFC3925] Littlefield, J., "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)", RFC 3925, October 2004. Eronen & Harrington Expires September 3, 2009 [Page 3] Internet-Draft Enterprise Number for Documentation Use March 2009 [RFC4735] Taylor, T., "Example Media Types for Use in Documentation", RFC 4735, October 2006. [RFC5101] Claise, B., "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information", RFC 5101, January 2008. [RFC5284] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", RFC 5284, August 2008. [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for Documentation Use", RFC 5398, December 2008. [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009. Authors' Addresses Pasi Eronen Nokia Research Center P.O. Box 407 FIN-00045 Nokia Group Finland Email: firstname.lastname@example.org David Harrington Huawei Technologies (USA) 1700 Alma Drive, Suite 100 Plano, TX 75075 USA Email: email@example.com Eronen & Harrington Expires September 3, 2009 [Page 4]