5612
INFORMATIONAL
Enterprise Number for Documentation Use
Authors: P. Eronen, D. Harrington
Date: August 2009
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
This document describes an Enterprise Number (also known as SMI Network Management Private Enterprise Code) for use in documentation. This memo provides information for the Internet community.
RFC 5612
INFORMATIONAL
Network Working Group P. Eronen
Request for Comments: 5612 Nokia
Category: Informational D. Harrington
Huawei Technologies (USA)
August 2009
<span class="h1">Enterprise Number for Documentation Use</span>
Abstract
This document describes an Enterprise Number (also known as SMI
Network Management Private Enterprise Code) for use in documentation.
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
<a href="./rfc1065">RFC 1065</a> [<a href="./rfc1065" title=""Structure and identification of management information for TCP/IP-based internets"">RFC1065</a>] (later superceded by [<a href="./rfc1155" title=""Structure and identification of management information for TCP/IP-based internets"">RFC1155</a>] and [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>])
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 "1.3.6.1.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 the "Private Enterprise Number Application Form"
[<a href="#ref-Application">Application</a>] for more information on how to request an Enterprise
Number from IANA, and [<a href="#ref-Numbers" title=""Private Enterprise Numbers"">Numbers</a>] for the list of currently assigned
numbers.
<span class="grey">Eronen & Harrington Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5612">RFC 5612</a> Enterprise Number for Documentation Use August 2009</span>
Enterprise Numbers have also been used for many other purposes than
OIDs in various protocols; for example:
o "STRUCTURED-DATA" identifiers in Syslog [<a href="./rfc5424" title=""The Syslog Protocol"">RFC5424</a>]
o "Vendor-Specific" RADIUS attributes [<a href="./rfc2865" title=""Remote Authentication Dial In User Service (RADIUS)"">RFC2865</a>]
o Mobile IPv4 vendor/organization-specific extensions [<a href="./rfc3115" title=""Mobile IP Vendor/ Organization-Specific Extensions"">RFC3115</a>]
o User-defined error information in RSVP [<a href="./rfc5284" title=""User-Defined Errors for RSVP"">RFC5284</a>]
o Vendor options in DHCPv4 [<a href="./rfc3925" title=""Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)"">RFC3925</a>]
o Enterprise-specific information elements in the IP Flow
Information Export (IPFIX) protocol [<a href="./rfc5101" title=""Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information"">RFC5101</a>]
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.
This Enterprise Number is not intended to be implemented. It is not
expected that any implementation would send it, or that any
implementation would treat it specially when receiving it.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Enterprise Number for Documentation Use</span>
The Enterprise Number 32473 has been allocated for use in examples in
RFCs, books, documentation, and the like.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
IANA has updated the registration for Enterprise Number 32473 to
point to this RFC.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Allocating an enterprise number for documentation use does not have
any direct impact on security.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
The need for an Enterprise Number for documentation use was
identified by Rainer Gerhards for the examples in [<a href="./rfc5424" title=""The Syslog Protocol"">RFC5424</a>]. The
authors would also like to thank Michelle Cotton for her help, and
Alfred Hoenes for his comments. This document borrows text from
[<a href="./rfc5398" title=""Autonomous System (AS) Number Reservation for Documentation Use"">RFC5398</a>] and ideas from [<a href="./rfc4735" title=""Example Media Types for Use in Documentation"">RFC4735</a>].
<span class="grey">Eronen & Harrington Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5612">RFC 5612</a> Enterprise Number for Documentation Use August 2009</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-Numbers">Numbers</a>] IANA, "Private Enterprise Numbers",
<<a href="http://www.iana.org/assignments/enterprise-numbers">http://www.iana.org/assignments/enterprise-numbers</a>>,
2009.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-Application">Application</a>]
IANA, "Protocol Registration Forms",
<a href="http://www.iana.org/protocols/apply/">http://www.iana.org/protocols/apply/</a>.
[<a id="ref-RFC1065">RFC1065</a>] Rose, M. and K. McCloghrie, "Structure and identification
of management information for TCP/IP-based internets", <a href="./rfc1065">RFC</a>
<a href="./rfc1065">1065</a>, August 1988.
[<a id="ref-RFC1155">RFC1155</a>] Rose, M. and K. McCloghrie, "Structure and identification
of management information for TCP/IP-based internets", STD
16, <a href="./rfc1155">RFC 1155</a>, May 1990.
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)",
STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
[<a id="ref-RFC2865">RFC2865</a>] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", <a href="./rfc2865">RFC</a>
<a href="./rfc2865">2865</a>, June 2000.
[<a id="ref-RFC3115">RFC3115</a>] Dommety, G. and K. Leung, "Mobile IP Vendor/
Organization-Specific Extensions", <a href="./rfc3115">RFC 3115</a>, April 2001.
[<a id="ref-RFC3925">RFC3925</a>] Littlefield, J., "Vendor-Identifying Vendor Options for
Dynamic Host Configuration Protocol version 4 (DHCPv4)",
<a href="./rfc3925">RFC 3925</a>, October 2004.
[<a id="ref-RFC4735">RFC4735</a>] Taylor, T., "Example Media Types for Use in
Documentation", <a href="./rfc4735">RFC 4735</a>, October 2006.
[<a id="ref-RFC5101">RFC5101</a>] Claise, B., "Specification of the IP Flow Information
Export (IPFIX) Protocol for the Exchange of IP Traffic
Flow Information", <a href="./rfc5101">RFC 5101</a>, January 2008.
[<a id="ref-RFC5284">RFC5284</a>] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP",
<a href="./rfc5284">RFC 5284</a>, August 2008.
<span class="grey">Eronen & Harrington Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5612">RFC 5612</a> Enterprise Number for Documentation Use August 2009</span>
[<a id="ref-RFC5398">RFC5398</a>] Huston, G., "Autonomous System (AS) Number Reservation for
Documentation Use", <a href="./rfc5398">RFC 5398</a>, December 2008.
[<a id="ref-RFC5424">RFC5424</a>] Gerhards, R., "The Syslog Protocol", <a href="./rfc5424">RFC 5424</a>, March 2009.
Authors' Addresses
Pasi Eronen
Nokia Research Center
P.O. Box 407
FIN-00045 Nokia Group
Finland
EMail: [email protected]
David Harrington
Huawei Technologies (USA)
1700 Alma Drive, Suite 100
Plano, TX 75075
USA
EMail: [email protected]
Eronen & Harrington Informational [Page 4]
Annotations
Select text to annotate