Private Enterprise Number (PEN) practices and Internet Assigned Numbers Authority (IANA) considerations for registration procedures
draft-liang-iana-pen-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Pearl Liang , Alexey Melnikov | ||
Last updated | 2012-12-31 (Latest revision 2012-06-29) | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)