Re: [Carbon-dev] Applying for an OID from IANA, to be used in a custom object class schema

Hi, This is to complete this thread. As per the mail received with the topic: 'Your request for a Private Enterprise Number has been completed', we are assigned the PEN: 37505. This is also available in the PEN registry at [1]. So the complete OID assigned is: *1.3.6.1.4.1.37505.* * * Although th

Re: [Carbon-dev] Applying for an OID from IANA, to be used in a custom object class schema

Hi, This is just a gentle check.. Could I please know whether any confirmation mail regarding this is received to external-relati...@wso2.com? Thanks, Hasini. On Wed, Jan 5, 2011 at 11:32 AM, Prabath Siriwardana wrote: > I had an offline discussion on this with Hasini.. > > +1 for going ahead..

Re: [Carbon-dev] Applying for an OID from IANA, to be used in a custom object class schema

I had an offline discussion on this with Hasini.. +1 for going ahead... Thanks a lot Hasini for keenly following up on this... Thanks & regards, -Prabath On Mon, Jan 3, 2011 at 4:42 PM, Hasini Gunasinghe wrote: > Hi all, > > There is a requirement of defining a custom object class schema with

Re: [Carbon-dev] Applying for an OID from IANA, to be used in a custom object class schema

On Wed, Jan 5, 2011 at 8:50 AM, Sanjiva Weerawarana wrote: > +1 for going ahead. Please use external-relati...@wso2.com as the email > address for the application so we can track it and manage it properly. > Thanks for seeing this thru. > > Of course I know nothing about LDAP so maybe someone who

Re: [Carbon-dev] Applying for an OID from IANA, to be used in a custom object class schema

+1 for going ahead. Please use external-relati...@wso2.com as the email address for the application so we can track it and manage it properly. Thanks for seeing this thru. Of course I know nothing about LDAP so maybe someone who does should review the technical merits :). Sanjiva. On Mon, Jan 3,

[Carbon-dev] Applying for an OID from IANA, to be used in a custom object class schema

Hi all, There is a requirement of defining a custom object class schema with the required attributes which are not defined in ApacheDS-LDAP by default (issues: CARBON-8215 , CARBON-8054 ) According to the specifica