There is an ASF wide OID assigned, so I think you can just ask Alex for
a sub-id for Fortress.

https://cwiki.apache.org/confluence/display/DIRxPMGT/OID+Assignment+Scheme

Kind Regards,
Stefan


On 09/22/2016 08:25 PM, Shawn McKinney wrote:
> I’m in favor of registering anew because if / when fortress becomes an apache 
> TLP we won’t have do this again.  And, because there aren’t any advantages to 
> sharing an IANA with the parent project, that I can think of.
> 
> We can assume it will take a few weeks before a new IANA # can be obtained.
> 
> WDYT?
> 
> Shawn
> 
>> On Sep 22, 2016, at 1:09 PM, Chris Pike <clp...@psu.edu> wrote:
>>
>> Are there plans to do this? I don't want to go to the trouble of changing 
>> it, then having to change it again.
>>
>>
>> ----- Original Message -----
>> From: "Shawn McKinney" <smckin...@apache.org>
>> To: fortress@directory.apache.org
>> Sent: Thursday, September 22, 2016 2:06:11 PM
>> Subject: Re: Schema Base OID
>>
>> Correct.  There’s another issue here.  That fortress IANA # is a relic:
>>  38088
>>  Joshua Tree Software, LLC
>>    Shawn McKinney
>>      shawn.mckinney&jtstools.com
>>
>> and should use apache directory's, or perhaps register for another specific 
>> to apache fortress.
>>
>> Shawn
>>
>>> On Sep 22, 2016, at 12:46 PM, Chris Pike <clp...@psu.edu> wrote:
>>>
>>> nm, I think we figured out that the OID is wrong in the old files
>>>
>>>
>>> ----- Original Message -----
>>> From: "Chris Pike" <clp...@psu.edu>
>>> To: fortress@directory.apache.org
>>> Sent: Thursday, September 22, 2016 12:19:56 PM
>>> Subject: Schema Base OID
>>>
>>> Shawn,
>>>
>>> Looking at the change in the schema file to use a base objectidentifier
>>>
>>> https://github.com/apache/directory-fortress-core/commit/b87766080fa096e66b6289accad62ba0de7dbba2#diff-e95924a7d2c92a1675f9a245a80c3b8e
>>>
>>> the base identifier is set to "1.3.6.1.4.1.38088", but shouldn't it be 
>>> "1.3.6.1.4.1.1.38088" (an extra 1 between 1 and 38088)?
> 

Reply via email to