There is an ASF wide OID assigned, so I think you can just ask Alex for
a sub-id for Fortress.
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.
>> 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: email@example.com
>> 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:
>> Joshua Tree Software, LLC
>> Shawn McKinney
>> and should use apache directory's, or perhaps register for another specific
>> to apache fortress.
>>> 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: firstname.lastname@example.org
>>> Sent: Thursday, September 22, 2016 12:19:56 PM
>>> Subject: Schema Base OID
>>> Looking at the change in the schema file to use a base objectidentifier
>>> the base identifier is set to "126.96.36.199.4.1.38088", but shouldn't it be
>>> "188.8.131.52.184.108.40.206088" (an extra 1 between 1 and 38088)?