Difference between revisions of "RFC5612"
| Line 7: | Line 7: | ||
Enterprise Number for Documentation Use | Enterprise Number for Documentation Use | ||
| − | Abstract | + | '''Abstract''' |
This document describes an Enterprise Number (also known as SMI | This document describes an Enterprise Number (also known as SMI | ||
Network Management Private Enterprise Code) for use in documentation. | Network Management Private Enterprise Code) for use in documentation. | ||
| − | Status of This Memo | + | '''Status of This Memo''' |
This memo provides information for the Internet community. It does | This memo provides information for the Internet community. It does | ||
| Line 18: | Line 18: | ||
memo is unlimited. | memo is unlimited. | ||
| − | Copyright Notice | + | '''Copyright Notice''' |
Copyright (c) 2009 IETF Trust and the persons identified as the | Copyright (c) 2009 IETF Trust and the persons identified as the | ||
document authors. All rights reserved. | document authors. All rights reserved. | ||
| − | This document is subject to BCP 78 and the IETF Trust's Legal | + | This document is subject to [[BCP78|BCP 78]] and the IETF Trust's Legal |
Provisions Relating to IETF Documents in effect on the date of | Provisions Relating to IETF Documents in effect on the date of | ||
publication of this document (http://trustee.ietf.org/license-info). | publication of this document (http://trustee.ietf.org/license-info). | ||
| Line 31: | Line 31: | ||
== Introduction == | == Introduction == | ||
| − | RFC 1065 [RFC1065] (later superceded by [RFC1155] and [RFC2578]) | + | [[RFC1065|RFC 1065]] [[RFC1065]] (later superceded by [[RFC1155]] and [[RFC2578]]) |
created a subtree (arc) of object identifiers (OIDs) for identifying | created a subtree (arc) of object identifiers (OIDs) for identifying | ||
management objects that are defined unilaterally by a single party, | management objects that are defined unilaterally by a single party, | ||
| Line 49: | Line 49: | ||
OIDs in various protocols; for example: | OIDs in various protocols; for example: | ||
| − | o "STRUCTURED-DATA" identifiers in Syslog [RFC5424] | + | o "STRUCTURED-DATA" identifiers in Syslog [[RFC5424]] |
| − | o "Vendor-Specific" RADIUS attributes [RFC2865] | + | o "Vendor-Specific" RADIUS attributes [[RFC2865]] |
| − | o Mobile IPv4 vendor/organization-specific extensions [RFC3115] | + | o Mobile IPv4 vendor/organization-specific extensions [[RFC3115]] |
| − | o User-defined error information in RSVP [RFC5284] | + | o User-defined error information in RSVP [[RFC5284]] |
| − | o Vendor options in DHCPv4 [RFC3925] | + | o Vendor options in DHCPv4 [[RFC3925]] |
o Enterprise-specific information elements in the IP Flow | o Enterprise-specific information elements in the IP Flow | ||
| − | Information Export (IPFIX) protocol [RFC5101] | + | Information Export (IPFIX) protocol [[RFC5101]] |
Documents related to these protocols may include examples that | Documents related to these protocols may include examples that | ||
| Line 84: | Line 84: | ||
The need for an Enterprise Number for documentation use was | The need for an Enterprise Number for documentation use was | ||
| − | identified by Rainer Gerhards for the examples in [RFC5424]. The | + | identified by Rainer Gerhards for the examples in [[RFC5424]]. The |
authors would also like to thank Michelle Cotton for her help, and | authors would also like to thank Michelle Cotton for her help, and | ||
Alfred Hoenes for his comments. This document borrows text from | Alfred Hoenes for his comments. This document borrows text from | ||
| − | [RFC5398] and ideas from [RFC4735]. | + | [[RFC5398]] and ideas from [[RFC4735]]. |
== References == | == References == | ||
| Line 103: | Line 103: | ||
http://www.iana.org/protocols/apply/. | http://www.iana.org/protocols/apply/. | ||
| − | [RFC1065] Rose, M. and K. McCloghrie, "Structure and identification | + | [[RFC1065]] Rose, M. and K. McCloghrie, "Structure and identification |
of management information for TCP/IP-based internets", RFC | of management information for TCP/IP-based internets", RFC | ||
1065, August 1988. | 1065, August 1988. | ||
| − | [RFC1155] Rose, M. and K. McCloghrie, "Structure and identification | + | [[RFC1155]] Rose, M. and K. McCloghrie, "Structure and identification |
of management information for TCP/IP-based internets", STD | of management information for TCP/IP-based internets", STD | ||
| − | 16, RFC 1155, May 1990. | + | 16, [[RFC1155|RFC 1155]], May 1990. |
| − | [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, | + | [[RFC2578]] McCloghrie, K., Perkins, D., and J. Schoenwaelder, |
"Structure of Management Information Version 2 (SMIv2)", | "Structure of Management Information Version 2 (SMIv2)", | ||
| − | STD 58, RFC 2578, April 1999. | + | [[STD58|STD 58]], [[RFC2578|RFC 2578]], April 1999. |
| − | [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, | + | [[RFC2865]] Rigney, C., Willens, S., Rubens, A., and W. Simpson, |
"Remote Authentication Dial In User Service (RADIUS)", RFC | "Remote Authentication Dial In User Service (RADIUS)", RFC | ||
2865, June 2000. | 2865, June 2000. | ||
| − | [RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/ | + | [[RFC3115]] Dommety, G. and K. Leung, "Mobile IP Vendor/ |
| − | Organization-Specific Extensions", RFC 3115, April 2001. | + | Organization-Specific Extensions", [[RFC3115|RFC 3115]], April 2001. |
| − | [RFC3925] Littlefield, J., "Vendor-Identifying Vendor Options for | + | [[RFC3925]] Littlefield, J., "Vendor-Identifying Vendor Options for |
Dynamic Host Configuration Protocol version 4 (DHCPv4)", | Dynamic Host Configuration Protocol version 4 (DHCPv4)", | ||
| − | RFC 3925, October 2004. | + | [[RFC3925|RFC 3925]], October 2004. |
| − | [RFC4735] Taylor, T., "Example Media Types for Use in | + | [[RFC4735]] Taylor, T., "Example Media Types for Use in |
| − | Documentation", RFC 4735, October 2006. | + | Documentation", [[RFC4735|RFC 4735]], October 2006. |
| − | [RFC5101] Claise, B., "Specification of the IP Flow Information | + | [[RFC5101]] Claise, B., "Specification of the IP Flow Information |
Export (IPFIX) Protocol for the Exchange of IP Traffic | Export (IPFIX) Protocol for the Exchange of IP Traffic | ||
| − | Flow Information", RFC 5101, January 2008. | + | Flow Information", [[RFC5101|RFC 5101]], January 2008. |
| − | [RFC5284] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", | + | [[RFC5284]] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", |
| − | RFC 5284, August 2008. | + | [[RFC5284|RFC 5284]], August 2008. |
| − | [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for | + | [[RFC5398]] Huston, G., "Autonomous System (AS) Number Reservation for |
| − | Documentation Use", RFC 5398, December 2008. | + | Documentation Use", [[RFC5398|RFC 5398]], December 2008. |
| − | [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009. | + | [[RFC5424]] Gerhards, R., "The Syslog Protocol", [[RFC5424|RFC 5424]], March 2009. |
Authors' Addresses | Authors' Addresses | ||
| Line 158: | Line 158: | ||
EMail: [email protected] | EMail: [email protected] | ||
| + | |||
| + | [[Category:Informational]] | ||
Latest revision as of 21:57, 11 October 2020
Network Working Group P. Eronen Request for Comments: 5612 Nokia Category: Informational D. Harrington
Huawei Technologies (USA)
August 2009
Enterprise Number for Documentation Use
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 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.
Contents
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 "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" [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 the 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.
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.
Enterprise Number for Documentation Use
The Enterprise Number 32473 has been allocated for use in examples in RFCs, books, documentation, and the like.
IANA Considerations
IANA has updated the registration for Enterprise Number 32473 to point to this RFC.
Security Considerations
Allocating an enterprise number for documentation use does not have any direct impact on security.
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.
References
Normative References
[Numbers] IANA, "Private Enterprise Numbers",
<http://www.iana.org/assignments/enterprise-numbers>, 2009.
Informative References
[Application]
IANA, "Protocol Registration Forms",
http://www.iana.org/protocols/apply/.
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.
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: [email protected]
David Harrington Huawei Technologies (USA) 1700 Alma Drive, Suite 100 Plano, TX 75075 USA
EMail: [email protected]
