Other OID Registration - ANSI/ISO for the U.S.

The syntax of the organization name is composed of a numeric form
assigned by ANSI and an alphanumeric form provided by the
organization. Each of these identifiers is unique within the ANSI
register. The identifiers are globally unambiguous when added to a
sequence of identifiers that precede it in the hierarchy. The
preceding identifiers are {2 16 840 1}. They represent
{joint-iso-ccitt(2) country(16) US(840) organization(1)} in the
hierarchy.





MORE INFO:

From swatskil@ncr.disa.mil  Wed Jan 20 14:47:59 1999
From: "Swatski, Leonard" <swatskil@ncr.disa.mil>
To: "'pvc@mitre.org'" <pvc@mitre.org>
Cc: "Engebretson, Douglas" <engebred@ncr.disa.mil>,
        "'plzak@nic.mil'"
	 <plzak@nic.mil>, "Cain, Ed" <caine@ncr.disa.mil>,
        "Bradshaw, George"
	 <bradshag@ncr.disa.mil>,
        "'kevin.mills@nist.gov'" <kevin.mills@nist.gov>,
        "Rose, Jim" <RoseJ@ncr.disa.mil>, "'iana@iana.org'"
<iana@iana.org>
Subject: Registration of MIBs for Airlines Electronic Engineering
Committe
	e (AEEC)
Date: Wed, 20 Jan 1999 17:49:25 -0500
Importance: low
X-Priority: 5

Hello Vinh,

I have done research on how you might get AEEC management information
bases (MIBS) registered officially.  There are five approaches you can
take, and they are listed in order of increasing difficulty (in my
opinion):

1.  Use an international Code Designator (ICD) already assigned to an
international aeronautical organization, like the International Civil
Aviation Organization (ICAO), if such an ICD exists.  Your MIB prefix
would then be 1.3.X, where "X" is the ICD for ICAO or equivalent.  The
MITRE folks in McLean VA, who were developing the OSI-based
Aeronautical Telecommunication Network (ATN), may be able to help you.
The last time I talked to the ATN folks was July 1993, and my POC was
Dick Rucker (703) 883-7098.

2.  Ask the Internet Assigned Numbers Authority (IANA)
 to register AEEC under one of their subtrees.  They register
vendor-specific MIBS under prefix 1.3.6.1.4.1.  See "Managing
Internetworks with SNMP", by Mark Miller, 1993, page 97 and Appendix
"F".  AEEC is more of an international standards consortium than a
private enterprise, so IANA might want to use a different prefix for
you.  Bill Manning can probably help you with this approach.  Bill's
phone number is (310) 822-1511.

3.  Ask the Air Force to ask DISA to allocate a prefix for you under
the root of the DOD subtree.  Your prefix would then be 1.3.6.X, where
"X "is not equal to one.  As far as I know, IANA is the only
organization assigned a subtree under the DOD root, and this
assignment was done in the 1980's.  DISA POC is Doug Engebretson.

4.  Ask NIST to allocate a prefix for you under the U.S. government
subtree.  Your prefix would then be 1.3.5.X.  I do not know whether
any managed objects have been registered under the U.S. root.  Kevin
Mills of NIST might be abe to help you with this approach.

5.  Ask NIST how to get AEEC registered as an international
organization, with an international code designator (ICD) assigned
under ISO Standard 6523.  Your prefix would then be 1.3.X, where "X"
is the new ICD assigned to you.

Again, I would seek advice from Kevin Mills here.

Len Swatski
DISA JIEO Center for Standards


