RFC 9371: Registration Procedures for Private Enterprise Numbers (PENs)
In plain English — editorial summary, not part of the RFC
This document describes how Private Enterprise Numbers (PENs) are registered by IANA. It shows how to request a new PEN and how to modify a current PEN. It also gives a brief overview of PEN uses.
Document record
- Document ID
- RFC9371
- Published
- March 2023
- Authors
- A. Baber; P. Hoffman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9304Locator/ID Separation Protocol (LISP): Shared Extension Message and IANA Registry for Packet Type AllocationsCurrent
October 2022
- RFC 9281Entities Involved in the IETF Standards ProcessCurrent
June 2022
- RFC 9519Update to the IANA SSH Protocol Parameters Registry RequirementsCurrent
January 2024
- RFC 9184BGP Extended Community Registries UpdateCurrent
January 2022
- RFC 9029Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters RegistriesObsoleted
June 2021
- RFC 9748Updating the NTP RegistriesCurrent
February 2025
- RFC 9876Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-FormatsCurrent
November 2025
- RFC 8688A Session Initiation Protocol (SIP) Response Code for Rejected CallsCurrent
December 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?