OID for LDAP and SNMP MIBs

Object_Id               : 277
Title                   : OID for LDAP and SNMP MIBs
Node_Type               : ProcessOrProcedure
Format                  : 
Address                 : 
Keywords                : OID
                          SNMP
                          LDAP
                          Identifier
                          ISO
                          AARNET
Abstract                : 
                          
 We now have an ISO Object Identifier prefix.  This is:

  iso(1).org(3).dod(6).internet(1).private(4).enterprise(1).aarnet(8852)

Object identifiers are used primariliy to identify SNMP and LDAP variables.

If an institution defines it's own LDAP variables (and most institutions
will eventually wish to do that) then the variable should have a 'real'
object identifier.

I'm suggesting that we define the OID's sub-allocation as:

1)  For further allocation by RNOs
    ...aarnet(8852).region(0)     
    ...aarnet(8852).region(0).nsw(1)
    ...aarnet(8852).region(0).vic(2)
       and in descending population until
    ...aarnet(8852).region(0).nt(8)

    It is expeceted that RNOs will reserve 0 for their own purposes:

       aarnet(8852).region(0).nsw(1).rno(0)

    and allocate other prefixes for their members

       aarnet(8852).region(0).nsw(1).usyd(1)

    AARNet will allocate prefixes to national institutions and
    the members that fall through the cracks.

      aarnet(8852).region(0).au(0).csiro(1)

    It is expected that members will then allocate the OIDs
    to organisational units within their organisation:

       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1)
       aarnet(8852).region(0).nsw(1).usyd(1).compsci(2)

    before allocating an OID to an application such as LDAP
    which might then use further object identifiers:

       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1).ldap(0)
       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1).ldap(0).usydPerson(1)
       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1).ldap(0).usydPerson(1).studentid(1)
       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1).ldap(0).usydPerson(1).campus(2)
       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1).ldap(0).usydOU(2)
       aarnet(8852).region(0).nsw(1).usyd(1).itservices(1).ldap(0).usydOU(2).costcode(1)

2) For use in a sector-wide LDAP schema which is an Australian
   version of EDUCAUSE's eduPerson schema.  For example, items
   such as the person's authority to reserve QoS across AARNet
   for a videoconferencing  call would appear in the schema.
   The schema would not duplicate eduPerson items.

       aarnet(8852).ldap(1).aarnetEduPerson(1)

3) For use in any SNMP management information bases:

       aarnet(8852).snmp(2).SOFTWARENAME(n).SOFTWAREVERSION(m)...

   AARNet will allocate OID prefixes to any software written by an author
   served by AARNet.  The sole condition is that the author must provide
   a MIB which AARNet will make available to the public.

4) All other prefixes are unallocated and unused at present.

Your comments would be appreciated.   I'll then write up a
recommended standard and allocation procedure.

Glen

-- 
 Glen Turner                                 Network Engineer
 (08) 8303 3936      Australian Academic and Research Network
 glen.turner@aarnet.edu.au          http://www.aarnet.edu.au/
--
                         
                          
Date_Entry_Last_Modified: $Date: 2001/03/22 08:33:34 $
Entry_Last_Modified_By  : $Author: horton $
Asset_Qualification     : 
Other_Opinions          : 
Contact_Person          : 
IP_or_Copyright_Owner   : AARNET
Support_re_Ownership    : 
Date_Item_Created       : 
Usage_Conditions        : 
Support_re_Usage_Condns : 
Authors_and_Contributors: 
Projects_Used_In        : 
Obtained_From           : 
Derived_From            : 
Related_Items           : 78
Context_or_When_To_Use  : 
Procedure_Number        : 
Authorisation_for_Use   : 
Additional_Info         :