Files
linux-cloud-router/OID-REGISTRY.txt
T

299 lines
9.7 KiB
Plaintext

Private Enterprise Number 67380 S. Koszewski
Category: Registry November 2026
OID Registry for the Linux Manager Arc 1.3.6.1.4.1.67380.10.1
Abstract
This document is the registry of Object Identifiers (OIDs) under the
arc 1.3.6.1.4.1.67380.10.1, which the registry of the Private
Enterprise Number 67380 delegates to Linux Manager. It defines the
tree of the arc, the rules for allocating OIDs in it, and lists every
allocation.
Table of Contents
1. Introduction
2. Root
3. Rules
4. Tree
5. Statuses
6. Assignments
7. Requesting an OID
8. References
Author's Address
1. Introduction
The tree of the arc follows the layout of the root registry of the
Private Enterprise Number 67380 [PEN-REGISTRY]: it is split by
function at its top level, and another arc holds experimental
definitions.
In this document, an OID written with a leading dot, such as ".2.1",
is relative to the OID root given in Section 2.
2. Root
+===========================+==========================+
| Item | Value |
+===========================+==========================+
| OID root | 1.3.6.1.4.1.67380.10.1 |
+---------------------------+--------------------------+
| Parent registry entry | .10.1 linux-manager |
+---------------------------+--------------------------+
Table 1: Root
3. Rules
* A number is used once among its siblings. Arcs and leaves are
never reused or renumbered.
* An allocated OID is never deleted. A retired OID is marked
deprecated and stays listed.
* A frozen arc takes no new children. Its existing children keep
their status.
* Leaves under an arc are assigned in order, starting from 1.
* Function arc numbers have the same meaning as in the root
registry, both under the root of this arc and under its
experimental arc ".99".
* Every leaf is listed in this document before it is used in
released software.
* An experimental OID under ".99" is never used in released
software or in production. A definition that leaves the
experimental arc gets a new OID; the experimental OID is not
moved.
* LDAP descriptors (short names) of schema elements under ".2"
carry the prefix "linuxManager".
* Documentation and test examples use "1.3.6.1.4.1.32473" [RFC5612]
or "2.999", never this arc.
4. Tree
1.3.6.1.4.1.67380.10.1 Linux Manager
.0 reserved, never allocated
.1 SNMP (reserved)
.2 LDAP / directory
.2.1 attribute types
.2.2 object classes
.3 PKI / X.509
.3.1 certificate policies
.3.2 extended key usages (KeyPurposeId)
.99 Experimental: mirrors the function arcs
Figure 1: Tree
5. Statuses
The statuses are those of the root registry [PEN-REGISTRY]:
reserved, active, frozen and deprecated.
6. Assignments
Each entry gives the OID and its name, followed by its fields. The
owner of every entry is "Slawomir Koszewski Org.".
6.1. Arcs
.0 reserved
Description: Never allocated
Status: reserved
Allocated: 2026-11-21
Reference: none
.1 snmp
Description: SNMP MIB modules, held for later use
Status: reserved
Allocated: 2026-11-21
Reference: [RFC2578]
.2 ldap
Description: The LDAP schema of the package
Status: active
Allocated: 2026-11-21
Reference: [RFC4512]
.2.1 ldap-attribute-types
Description: LDAP attribute types
Status: active
Allocated: 2026-11-21
Reference: [RFC4512], Section 4.1.2
.2.2 ldap-object-classes
Description: LDAP object classes
Status: active
Allocated: 2026-11-21
Reference: [RFC4512], Section 4.1.1
.3 pki
Description: PKI and X.509
Status: active
Allocated: 2026-11-21
Reference: [RFC5280]
.3.1 pki-certificate-policies
Description: Certificate policies
Status: active
Allocated: 2026-11-21
Reference: [RFC5280], Section 4.2.1.4
.3.2 pki-extended-key-usages
Description: Extended key usages (KeyPurposeId)
Status: active
Allocated: 2026-11-21
Reference: [RFC5280], Section 4.2.1.12
.99 experimental
Description: Experimental definitions, never in
production
Status: active
Allocated: 2026-11-21
Reference: [RFC4520], Section 3.1
6.2. LDAP Attribute Types
Every attribute type below has the status active, was allocated on
2026-11-21, and is defined in "linuxmanager_ldap.py" of this
repository.
.2.1.1 linuxManagerScope
An authorization scope of the account
.2.1.2 linuxManagerPrivateKey
A private key, PEM
.2.1.3 linuxManagerCertificateRequest
The CSR of a CA, PEM
.2.1.4 linuxManagerCRLNumber
The number of the last CRL of a CA
.2.1.5 linuxManagerCRLSource
Signed or uploaded, where the CRL of a CA came from
.2.1.6 linuxManagerRetired
When a CA was retired
.2.1.7 linuxManagerKind
Ca, router, user or external, the kind of a certificate
.2.1.8 linuxManagerTemplate
The template of a certificate
.2.1.9 linuxManagerSubjectAltName
A subject alternative name of a certificate
.2.1.10 linuxManagerNotAfter
When a certificate expires
.2.1.11 linuxManagerRevoked
When a certificate was revoked
.2.1.12 linuxManagerRevocationReason
Why a certificate was revoked
.2.1.13 linuxManagerConsoleLogin
Whether the user may use a console
.2.1.14 linuxManagerConsoleAccount
The local account the console of the user runs as
.2.1.15 linuxManagerWireGuardPeer
A WireGuard peer of the user, its public key and IPs
.2.1.16 linuxManagerPasskey
A passkey of the user, its credential as JSON
.2.1.17 linuxManagerRedirectUri
A redirect URI of an OpenID Connect client
.2.1.18 linuxManagerPostLogoutRedirectUri
A post-logout redirect URI of an OpenID Connect client
.2.1.19 linuxManagerAllowedGroup
A group whose members may sign in to an OpenID Connect
client
.2.1.20 linuxManagerGrantType
A grant an OpenID Connect client may use besides the
authorization code
.2.1.21 linuxManagerPublicClient
Whether an OpenID Connect client has no secret
.2.1.22 linuxManagerClientScope
A scope of a resource an OpenID Connect client may ask for
.2.1.23 linuxManagerResourceScope
A scope of a resource of the OpenID Provider
6.3. LDAP Object Classes
Every object class below has the status active, was allocated on
2026-11-21, and is defined in "linuxmanager_ldap.py" of this
repository.
.2.2.1 linuxManagerAccount
Auxiliary: properties of a user or a Manager-only account
.2.2.2 linuxManagerAuthority
Structural: a CA of the PKI
.2.2.3 linuxManagerCertificate
Structural: a certificate a CA of the PKI issued
.2.2.4 linuxManagerRole
Structural: a role of a resource of the OpenID Provider
7. Requesting an OID
An allocation is a change to this document. The change adds an
entry to Section 6 with every field filled in, and for a new arc
also updates Figure 1. A new function arc is first allocated in the
root registry [PEN-REGISTRY].
8. References
[PEN-REGISTRY]
Koszewski, S., "OID Registry for Private Enterprise
Number 67380", November 2026.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578,
DOI 10.17487/RFC2578, April 1999,
<https://www.rfc-editor.org/info/rfc2578>.
[RFC4512] Zeilenga, K., Ed., "Lightweight Directory Access Protocol
(LDAP): Directory Information Models", RFC 4512,
DOI 10.17487/RFC4512, June 2006,
<https://www.rfc-editor.org/info/rfc4512>.
[RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
Considerations for the Lightweight Directory Access
Protocol (LDAP)", BCP 64, RFC 4520, DOI 10.17487/RFC4520,
June 2006, <https://www.rfc-editor.org/info/rfc4520>.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008,
<https://www.rfc-editor.org/info/rfc5280>.
[RFC5612] Eronen, P. and D. Harrington, "Enterprise Number for
Documentation Use", RFC 5612, DOI 10.17487/RFC5612,
August 2009, <https://www.rfc-editor.org/info/rfc5612>.
Author's Address
Slawomir Koszewski