idnits 2.17.1 draft-eronen-enterprise-number-documentation-01.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.ii 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 date (March 2, 2009) is 5532 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 1065 (Obsoleted by RFC 1155) -- Obsolete informational reference (is this intentional?): RFC 5101 (Obsoleted by RFC 7011) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Eronen 3 Internet-Draft Nokia 4 Intended status: Informational D. Harrington 5 Expires: September 3, 2009 Huawei Technologies (USA) 6 March 2, 2009 8 Enterprise Number for Documentation Use 9 draft-eronen-enterprise-number-documentation-01.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on September 3, 2009. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license-info). 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 This document describes an Enterprise Number (also known as SMI 48 Network Management Private Enterprise Code) for use in documentation. 50 1. Introduction 52 RFC 1065 [RFC1065] (later superceded by [RFC1155] and [RFC2578]) 53 created a subtree (arc) of object identifiers (OIDs) for identifying 54 management objects that are defined unilaterally by a single party, 55 such as an enterprise. The subtree for a particular enterprise 56 consists of the prefix "1.3.6.1.4.1.", followed by the Enterprise 57 Number assigned for that enterprise. 59 Enterprise Numbers are allocated by IANA, and are also known as 60 "Private Enterprise Numbers", "Enterprise Codes", and "SMI (Structure 61 of Management Information) Network Management Private Enterprise 62 Codes". See [Application] for more information on how to request an 63 Enterprise Number from IANA, and [Numbers] for the list of currently 64 assigned numbers. 66 Enterprise Numbers have also been used for many other purposes than 67 OIDs in various protocols; for example: 69 o "STRUCTURED-DATA" identifiers in Syslog [RFC5424] 70 o "Vendor-Specific" RADIUS attributes [RFC2865] 71 o Mobile IPv4 vendor/organization-specific extensions [RFC3115] 72 o User-defined error information in RSVP [RFC5284] 73 o Vendor options in DHCPv4 [RFC3925] 74 o Enterprise-specific information elements in IP Flow Information 75 Export (IPFIX) protocol [RFC5101] 77 Documents related to these protocols may include examples that 78 contain Enterprise Numbers. To reduce the likelihood of conflict and 79 confusion, this document specifies an Enterprise Number for use in 80 examples in RFCs, books, documentation, and the like. 82 2. Enterprise Number for Documentation Use 84 The Enterprise Number 32473 has been allocated for use in examples in 85 RFCs, books, documentation, and the like. 87 3. IANA Considerations 89 IANA is asked to update (has updated) the registration for Enterprise 90 Number 32473 to point to this RFC. 92 4. Security Considerations 94 Allocating an enterprise number for documentation use does not have 95 any direct impact on security. 97 5. Acknowledgments 99 The need for an Enterprise Number for documentation use was 100 identified by Rainer Gerhards for the examples in [RFC5424]. The 101 authors would also like to thank Michelle Cotton for her help, and 102 Alfred Hoenes for his comments. This document borrows text from 103 [RFC5398] and ideas from [RFC4735]. 105 6. References 107 6.1. Normative References 109 [Numbers] IANA, "Private Enterprise Numbers", 110 URL http://www.iana.org/assignments/enterprise-numbers, 111 2009. 113 6.2. Informative References 115 [Application] 116 IANA, "Private Enterprise Number (PEN) Request Template", 117 URL http://pen.iana.org/pen/PenApplication.page, 2009. 119 [RFC1065] Rose, M. and K. McCloghrie, "Structure and identification 120 of management information for TCP/IP-based internets", 121 RFC 1065, August 1988. 123 [RFC1155] Rose, M. and K. McCloghrie, "Structure and identification 124 of management information for TCP/IP-based internets", 125 STD 16, RFC 1155, May 1990. 127 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 128 "Structure of Management Information Version 2 (SMIv2)", 129 STD 58, RFC 2578, April 1999. 131 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 132 "Remote Authentication Dial In User Service (RADIUS)", 133 RFC 2865, June 2000. 135 [RFC3115] Dommety, G. and K. Leung, "Mobile IP Vendor/ 136 Organization-Specific Extensions", RFC 3115, April 2001. 138 [RFC3925] Littlefield, J., "Vendor-Identifying Vendor Options for 139 Dynamic Host Configuration Protocol version 4 (DHCPv4)", 140 RFC 3925, October 2004. 142 [RFC4735] Taylor, T., "Example Media Types for Use in 143 Documentation", RFC 4735, October 2006. 145 [RFC5101] Claise, B., "Specification of the IP Flow Information 146 Export (IPFIX) Protocol for the Exchange of IP Traffic 147 Flow Information", RFC 5101, January 2008. 149 [RFC5284] Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", 150 RFC 5284, August 2008. 152 [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for 153 Documentation Use", RFC 5398, December 2008. 155 [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009. 157 Authors' Addresses 159 Pasi Eronen 160 Nokia Research Center 161 P.O. Box 407 162 FIN-00045 Nokia Group 163 Finland 165 Email: pasi.eronen@nokia.com 167 David Harrington 168 Huawei Technologies (USA) 169 1700 Alma Drive, Suite 100 170 Plano, TX 75075 171 USA 173 Email: dharrington@huawei.com