Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenLDAP
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Christopher Ng
OpenLDAP
Commits
22915aac
Commit
22915aac
authored
22 years ago
by
Kurt Zeilenga
Browse files
Options
Downloads
Patches
Plain Diff
More OID clarifications.
parent
8c03d7ed
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/guide/admin/schema.sdf
+14
-14
14 additions, 14 deletions
doc/guide/admin/schema.sdf
with
14 additions
and
14 deletions
doc/guide/admin/schema.sdf
+
14
−
14
View file @
22915aac
...
...
@@ -94,19 +94,19 @@ OID Assignment
!endblock
You are, of course, free to design a hierarchy suitable to your
organizational needs under your organization's OID. No matter
what
hierarchy you choose, you should maintain a registry of
assignments
you make. This can be a simple flat file or
something more
sophisticated such as the {{OpenLDAP OID Registry}}
organizational needs under your organization's OID. No matter
what
hierarchy you choose, you should maintain a registry of
assignments
you make. This can be a simple flat file or
something more
sophisticated such as the {{OpenLDAP OID Registry}}
({{URL:http://www.openldap.org/faq/index.cgi?file=197}}).
For more information about Object Identifers (and a listing
service)
see {{URL:http://www.alvestrand.no/harald/objectid/}}.
For more information about Object Identifers (and a listing
service)
see {{URL:http://www.alvestrand.no/harald/objectid/}}.
.{{Under no circumstances should you hijack OID namespace!}}
.{{Under no circumstances should you hijack OID namespace!}}
To obtain a
fully
registered OID at {{no cost}}, apply for an OID
under
the {{ORG[expand]IANA}} (IANA) maintained {{Private Enterprise}}
To obtain a registered OID at {{no cost}}, apply for an OID
under
the {{ORG[expand]IANA}} (IANA) maintained {{Private Enterprise}}
arc. Any private enterprise (organization) may request an OID to
be assigned under this arc. Just fill out the {{ORG:IANA}} form
at {{URL: http://www.iana.org/cgi-bin/enterprise.pl}} and your
...
...
@@ -114,15 +114,15 @@ official OID will be sent to you usually within a few days. Your
base OID will be something like {{EX:1.3.6.1.4.1.X}} where {{EX:X}}
is an integer.
Note: Don't let the "MIB/SNMP" statement on the IANA page confuse
you.
OIDs obtained using this form may be used for any purpose
including
identifying LDAP schema elements.
Note: Don't let the "MIB/SNMP" statement on the IANA page confuse
you.
OIDs obtained using this form may be used for any purpose
including
identifying LDAP schema elements.
Alternatively, OID name space may be available from a national
authority (e.g., ANSI).
For private experiments, OIDs under {{EX:1.1}} may be used. The
OID
{{EX:1.1}} arc is dead name space.
For private experiments, OIDs under {{EX:1.1}} may be used. The
OID
{{EX:1.1}} arc is
regarded as
dead name space.
H3: Name Prefix
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment