Private Enterprise Number (PEN) practices and Internet Assigned Numbers Authority (IANA) registration considerations
draft-liang-iana-pen-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-10-18
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           P. Liang
Internet-Draft                                                     ICANN
Intended status: Informational                               A. Melnikov
Expires: April 20, 2014                                        Isode Ltd
                                                        October 17, 2013

Private Enterprise Number (PEN) practices and Internet Assigned Numbers
              Authority (IANA) registration considerations
                        draft-liang-iana-pen-02

Abstract

   Private Enterprise Numbers (PENs), are assigned as part of the
   technical protocol parameters and are frequently used in the
   management of network connected equipment or software via SNMP-based
   network management systems, LDAP, DIAMETER or GSS-API.  This document
   discusses what a Private Enterprise Number (PEN) is, common uses and
   registration procedures for IANA Considerations.  The registration
   procedures include instructions and requirement for obtaining a new
   Private Enterprise Number, modification to existing numbers and
   removal of existing numbers.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on April 20, 2014.

Copyright Notice

   Copyright (c) 2013 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Liang & Melnikov         Expires April 20, 2014                 [Page 1]
Internet-Draft                  PEN v.0.2                   October 2013

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Example of use for Private Enterprise Numbers . . . . . . . .   3
   3.  Who can get a Private Enterprise Number?  . . . . . . . . . .   3
   4.  Other useful things to know . . . . . . . . . . . . . . . . .   4
   5.  Syntax for Private Enterprise Numbers . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  New Private Enterprise Numbers  . . . . . . . . . . . . .   5
     7.2.  Modification of Private Enterprise Numbers  . . . . . . .   7
     7.3.  Removals of Private Enterprise Numbers  . . . . . . . . .   8
     7.4.  Historical Assignments  . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   A Private Enterprise Number (PEN, prefix:
   iso.org.dod.internet.private.enterprise (1.3.6.1.4.1)) is a subtree
   of Object Identifiers (OIDs ).  The Private Enterprise Number OID was
   originally defined in [RFC1065].  PEN is a non-negative integer that
   can be used to reference an organization ("enterprise") in protocols
   that require numeric values instead of a human readable organization
   name.

   Currently, procedures for assignment of new PENs and the modification
   of existing PENs are not clearly documented.  Private Enterprise
   Numbers are referenced in RFCs [RFC1157] [RFC1213] and [RFC2578].
   These documents mostly define Simple Network Management Protocol
   (SNMP), Management Information Base (MIB), and Structure of
   Management Information (SMI).  However, none of the above mentioned
   RFCs clearly describe PENs and define the registration procedures.

   Additionally, updates to existing Private Enterprise Numbers can also
   be problematic resulting from the lack of clear registration
   requirements.  Furthermore, modification requests can be hardly
Show full document text