svn commit: r1039014 - in /websites/staging/directory/trunk/content: ./ apacheds/features.html

[bu...@apache.org]

Author: buildbot
Date: Mon Jan 14 23:01:49 2019
New Revision: 1039014

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/features.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 14 23:01:49 2019
@@ -1 +1 @@
-1851302
+1851306

Modified: websites/staging/directory/trunk/content/apacheds/features.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/features.html (original)
+++ websites/staging/directory/trunk/content/apacheds/features.html Mon Jan 14 23:01:49 2019
@@ -247,8 +247,8 @@ h2:hover > .headerlink, h3:hover > .head
 </tr>
 <tr>
 <td align="center">1.3.6.1.4.1.18060.12</td>
-<td align="center">HTTPdvJoe Orton</td>
-<td align="center"></td>
+<td align="center">HTTPd</td>
+<td align="center">Joe Orton</td>
 </tr>
 <tr>
 <td align="center">1.3.6.1.4.1.18060.14</td>
@@ -267,8 +267,8 @@ h2:hover > .headerlink, h3:hover > .head
 </tr>
 <tr>
 <td align="center">1.3.6.1.4.1.18060.17</td>
-<td align="center">Apache Fortress Shawn McKinney</td>
-<td align="center"></td>
+<td align="center">Apache Fortress</td>
+<td align="center">Shawn McKinney</td>
 </tr>
 <tr>
 <td align="center">1.3.6.1.4.1.18060.18</td>
@@ -277,6 +277,176 @@ h2:hover > .headerlink, h3:hover > .head
 </tr>
 </tbody>
 </table>
+<p>Each contact person is the authority for assigning unique <strong>OID</strong> values and ranges to projects or persons. Contact that person for more assignments.</p>
+<h2 id="making-assignments">Making Assignments<a class="headerlink" href="#making-assignments" title="Permanent link">&para;</a></h2>
+<p>Contacts may wonder what scheme is best for making assignments. There is no rule for doing this. However some would recommend assigning the first digit past the enterprise number of an organization to be for identifying a protocol. Obviously we did not do this for <strong>Apache</strong>. The reason for this is because we feel it's better to model the assignments based on the structure of the organization since these are private ranges and need not conform to a global convention.</p>
+<p>However this still does not tell us how contacts should make assignments. I think this is up to you. Perhaps a good example will be how the <strong>Directory</strong> TLP does things which is somewhat specific to their products and the nature of their products.</p>
+<h3 id="assignment-scheme-for-apache-directory">Assignment Scheme For Apache Directory<a class="headerlink" href="#assignment-scheme-for-apache-directory" title="Permanent link">&para;</a></h3>
+<p>The ninth component in the <strong>OID</strong> could be reserved for subprojects like <strong>ApacheDS</strong> and <strong>Triplesec</strong>. This might be more attractive in TLPs with many subprojects because a single authority or contact can be used for a specific subproject. So here could be one assignment scheme:</p>
+<table class="table">
+<thead>
+<tr>
+<th align="center">Branch Assignement</th>
+<th align="center">Assign To</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.0</td>
+<td align="center">ApacheDS</td>
+</tr>
+</tbody>
+</table>
+<p>Here's how the ApacheDS OID is branched off:</p>
+<p>The ninth component in the <strong>OID</strong> could be reserved for subprojects like <strong>ApacheDS</strong> and <strong>Triplesec</strong>. This might be more attractive in TLPs with many subprojects because a single authority or contact can be used for a specific subproject. So here could be one assignment scheme:</p>
+<table class="table">
+<thead>
+<tr>
+<th align="center">Branch Assignement</th>
+<th align="center">Assign To</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.0</td>
+<td align="center">ApacheDS LDAP Controls</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1</td>
+<td align="center">ApacheDS LDAP Extended Operations</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.2</td>
+<td align="center">ApacheDS LDAP Supported Features</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.3</td>
+<td align="center">ApacheDS LDAP Protocol Mechanisms</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4</td>
+<td align="center">ApacheDS LDAP Attribute Values</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.X.0</td>
+<td align="center">ApacheDS LDAP Schema syntaxes</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.X.1</td>
+<td align="center">ApacheDS LDAP Schema matchingRules</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.X.2</td>
+<td align="center">ApacheDS LDAP Schema attributeTypes</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.X.3</td>
+<td align="center">ApacheDS LDAP Schema objectClasses</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.X.4</td>
+<td align="center">ApacheDS LDAP Schema dITStructureRules</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.X.5</td>
+<td align="center">ApacheDS LDAP Schema nameForms</td>
+</tr>
+</tbody>
+</table>
+<p>where <strong>X</strong> is a unique number associated with one of the specific <strong>ApacheDS</strong> schema.</p>
+<p>NOTE: <em>dITContentRules</em> do not have their own OID, rather they reference the <strong>OID</strong> of the structural <em>objectClass</em> they influence. The same sort of situation exists for <em>matchingRuleUse</em> which uses the <strong>OID</strong> of the <em>matchingRule</em> it is associated with.</p>
+<p>And here are the schema <strong>OID</strong>s (where the <strong>X</strong> is substituted by the proper number):</p>
+<table class="table">
+<thead>
+<tr>
+<th align="center">Branch Assignement</th>
+<th align="center">Assign To</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.0</td>
+<td align="center">ApacheDS LDAP Meta Schema</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.1</td>
+<td align="center">ApacheDS LDAP Apache Schema</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.2</td>
+<td align="center">ApacheDS LDAP Apache DNS Schema</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.3</td>
+<td align="center">Apache Directory Documentation Examples Schema</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.4</td>
+<td align="center">Quartz Schema</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.4.5</td>
+<td align="center">Bean Schema</td>
+</tr>
+</tbody>
+</table>
+<p>(Some of those schema are long gone, but the assignement is still existing)</p>
+<h3 id="oids-for-apacheds-specific-controls">OID's for ApacheDS specific controls<a class="headerlink" href="#oids-for-apacheds-specific-controls" title="Permanent link">&para;</a></h3>
+<p>Here are the new <strong>OID</strong>s used:</p>
+<table class="table">
+<thead>
+<tr>
+<th align="center">OID</th>
+<th align="center">Control</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.0.1</td>
+<td align="center">Cascade Control</td>
+</tr>
+</tbody>
+</table>
+<h3 id="oids-for-the-extended-operations">OID's for the extended operations<a class="headerlink" href="#oids-for-the-extended-operations" title="Permanent link">&para;</a></h3>
+<p>Here are the new <strong>OID</strong>s used:</p>
+<table class="table">
+<thead>
+<tr>
+<th align="center">OID</th>
+<th align="center">Extended Operation</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.1</td>
+<td align="center">LaunchDiagnosticUiRequest</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.2</td>
+<td align="center">LaunchDiagnosticUiResponse</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.3</td>
+<td align="center">GracefulShutdownRequest</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.4</td>
+<td align="center">GracefulShutdownResponse</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.5</td>
+<td align="center">GracefulDisconnect</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.6</td>
+<td align="center">StoredProcedureRequest</td>
+</tr>
+<tr>
+<td align="center">1.3.6.1.4.1.18060.0.1.7</td>
+<td align="center">StoredProcedureResponse</td>
+</tr>
+</tbody>
+</table>