Standards and other documents defining OIDs
that were captured in the OID repository
Choose a category of documents:
· ITU-T Recommendations
· ISO standards
· IETF RFCs
· Miscellaneous
Note: mistakes found in OIDs defined in those documents are indicated as comments under the standard number or document title.
1. G.650
2. G.650.1
3. G.650.2
4. G.651
5. G.652
6. G.653
7. G.654
8. G.655
9. G.661
10. G.662
11. G.663
12. G.664
13. G.671
14. G.681
15. G.691
16. G.692
17. G.693
18. G.694.1
19. G.694.2
20. G.700 (withdrawn)
21. G.701
22. G.702
23. G.703
24. G.704
25. G.705
26. G.706
27. G.707
28. G.708
29. G.709
30. G.711
31. G.712
32. G.713 (withdrawn, now covered by G.712)
33. G.714 (withdrawn, now covered by G.712)
34. G.715 (withdrawn, now covered by G.712)
35. G.720
36. G.721 (withdrawn, now covered by G.726)
37. G.722 + G.722 Annex A + G.722 Appendix II
38. G.722.1 + G.722.1 Cor.1 + G.722.1 Annex A + G.722.1 Annex B
39. G.722.2 + G.722.2 Annex A + G.722.2 Annex B + G.722.2 Annex C + G.722.2 Annex E
40. G.723 (withdrawn, now covered by G.726)
41. G.723.1
42. G.imp.723.1 + G.723.1 Annex A + G.723.1 Annex B + G.723.1 Annex C
43. G.724
44. G.725
45. G.726 + G.726 Annex A + G.726 Appendix II + G.726 Appendix III
46. G.727 + G.727 Annex A + G.727 Appendix II + G.727 Appendix III
47. G.728 + G.728 Annex G + G.728 Annex G Cor.1 + G.728 Annex H + G.728 Annex I + G.728 Annex J + G.728 Appendix I + G.728 Appendix II
48. G.729 + G.729 Annex A + G.729 Annex B + G.729 Annex B Cor.1 + G.729 Annex B Cor.2 + G.729 Annex C + G.729 Annex D + G.729 Annex D Cor.1 + G.729 Annex E + G.729 Annex E Cor.1 + G.729 Annex F + G.729 Annex G + G.729 Annex H + G.729 Annex I + G.729 Annexes Cor.2 + G.729 Appendix I
49. G.731
50. G.732
51. G.733
52. G.734
53. G.735
54. G.736
55. G.737
56. G.738
57. G.739
58. G.741
59. G.742
60. G.743
61. G.744
62. G.745
63. G.746
64. G.747
65. G.751
66. G.752
67. G.753
68. G.754
69. G.755
70. G.761
71. G.763 + G.763 Erratum + G.763 Appendix I
72. G.764 + G.764 Appendix I
73. G.765 + G.765 Appendix I
74. G.766
75. G.767
76. G.Imp.767
77. G.768
78. G.769
79. G.771 (withdrawn)
80. G.772
81. G.773
82. G.774: incomplete capture
{itu-t(0) recommendation(0) g(7) g774(774) informationModel(0) asn1Module(2) sdh(0)}
This OID and his following children have been captured:
asn1Module(2) - managedObjectClass(3) - nameBinding(6) - attribute(7)
Need to download this Recommendation in order to capture remaining OIDS; only children of asn1Module(2) have been captured.
Don’t forget to make sure that OIDs of previous version (09/1992) and its corrigendum have also been captured.
83. G.774.01
84. G.774.01 Cor.1
85. G.774.1
86. G.774.2: incomplete capture
{itu-t(0) recommendation(0) g(7) g774(774) hyphen(127) conf(2) informationModel(0)}
This OID and his following children have been captured:
asn1Module(2) - managedObjectClass(3) - parameter(5) - nameBinding(6) - action(9)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Module(2) have been captured.
Don’t forget to make sure that OIDs of previous version (11/1994) and its corrigendum have also been captured.
87. G.774.03 + G.774.03 Cor.1
88. G.774.04 + G.774.04 Cor.1
89. G.774.4
90. G.774.5: incomplete capture
{itu-t(0) recommendation(0) g(7) g774(774) hyphen(127) cs(5)
informationModel(0)}
This OID and his following children have been captured:
asn1Module(2) - managedObjectClass(3) - package(4) - nameBinding(6) - attribute(7)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Module(2) have been captured.
Don’t forget to make sure that OIDs of previous version (07/1995) and its corrigendum have also been captured.
91. G.774.6: incomplete capture
{itu-t(0) recommendation(0) g(7) g774(774) hyphen(127) pmUni(6) informationModel(0)}
This OID and his following children have been captured:
asn1Module(2) - managedObjectClass(3) - package(4) - nameBinding(6) - attribute(7)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Module(2) have been captured.
Don’t forget to make sure that OIDs of previous version (04/1997) have been captured.
92. G.774.7 (11/1996)
93. G.774.7 (02/2001)
94. G.774.8 (04/1997)
95. G.774.8 (02/2001)
96. G.774.9 (02/1998)
97. G.774.9 (02/2001)
98. G.774.10
99. G.775
100. G.776.1
101. G.776.3
102. G.780
103. G.781
104. G.782
105. G.783 + G.783 Amd. 1 + G.783 Cor.1
106. G.784
107. G.785
108. G.791
109. G.792
110. G.793
111. G.794
112. G.795
113. G.796 + G.796 Amd. 1
114. G.797
115. G.798 + G.798 Amd. 1
116. G.801
117. G.802
118. G.803
119. G.804
120. G.805
121. G.806
122. G.807
123. G.810
124. G.811
125. G.812
126. G.813 + G.813 Cor.1
127. G.854.1
128. G.854.3
129. G.854.6
130. G.854.8
131. G.854.10
132. G.854.12
133. G.854.16
134. G.855.1: incomplete capture
{itu-t recommendation g gntm(85501) informationModel(0)}
This OID and his following children have been captured:
asn1Module(2) - managedObjectClass(3) - package(4) - nameBinding(6) - attribute(7) – action(9) – notification(10) - specificError(12)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Module(2) have been captured.
Be careful! Parameter type OIDs are registered under the following arc: {itu-t recommendation g gntm(85501) informationModel(0) specificError(12)}.
135. G.950
136. G.957
137. G.958
138. G.959.1
139. G.966
140. G.972
141. G.973
142. G.974
143. G.975
144. G.976
145. G.977
146. G.7041
147. G.7042
148. G.7710
149. G.7712
150. G.7713
151. G.7714
152. G.7715
153. G.8080
154. H.225.0
155. H.235
156. H.248
157. H.460.1
158. Q.48
159. Q.253
160. Q.706
161. Q.708
162. Q.711
163. Q.733.1
164. Q.733.2
165. Q.733.3 + Amd. 1
166. Q.733.4
167. Q.733.5
168. Q.736.1
169. Q.736.3
170. Q.751.1: incomplete capture
{itu-t(0) recommendation(0) q(17) omap(751) mtp(1) informationModel(0)}
This OID and his following children have been captured:
specificExtensions(0) - asn1Modules(2) - managedObjectClass(3) – package(4) – parameter(5) – nameBinding(6) – attribute(7) – action(9) – notification(10)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
171. Q.751.2
{itu-t(0) recommendation(0) q(17) omap(751) sccp(2) informationModel(0)}
This OID and his following children have been captured:
specificExtensions(0) - asn1Modules(2) - managedObjectClass(3) – package(4) – parameter(5) – nameBinding(6) – attribute(7) – action(9) – notification(10)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
172. Q.751.3
Subclause 8.1.7 and 8.2.7: “ ASN.1 Definitions”
Ø {itu-t(0) recommendation(0) q(17) omap(751) accounting(3) informationModel(0)}
Arcs below this one are mistakenly defined under {itu-t(0) recommendation(0) q(17) omap(751) accounting(3)} in this recommendation.
Ø ss7AccountingAndVerificationControlPackage-POi OBJECT IDENTIFIER ::= ::= {accountingPackage ss7AccountingAndVerificationControlPackage(3)}
ss7AccountingAndVerificationControlPackage-POi OBJECT IDENTIFIER ::= ::= {accountingPackage ss7AccountingAndVerificationControlPackage(0)}
Two identical OIDs are defined at different nodes located at the same level of the tree. None of them has been registered.
Note that subclause 8.2.7 defines the following OID which hasn’t been registered anymore:
dpcGroupPackage-POi OBJECT IDENTIFIER ::= {accountingPackage dpcGroupPackage (3)}
Ø controlPointerPackage-POi OBJECT IDENTIFIER ::= {accountingPackage controlPointerPackage(1)}
ss7AccountingLogRecordPackage-POi OBJECT IDENTIFIER ::= {accountingPackage ss7AccountingLogRecordPackage(1)}
This recommendation defines 2 different identifiers for the same node. First one above-mentioned has been registered.
Ø measurementControlStatus-AOi OBJECT IDENTIFIER ::= {accountingAttribute measurementControlStatus(6)}
dpcGroupId-AOi OBJECT IDENTIFIER ::= {accountingAttribute dpcGroupId(6)}
This recommendation defines 2 different identifiers for the same node. First one above-mentioned has been registered.
Ø endOfMeasurementTime-AOi OBJECT IDENTIFIER ::= {accountingAttribute endOfMeasurementTime(7)}
mtpAccountId-AOi OBJECT IDENTIFIER ::= {accountingAttribute mtpAccountId(7)}
This recommendation defines 2 different identifiers for the same node. First one above-mentioned has been registered.
Ø {itu-t(0) recommendation(0) q(17) omap(751) accounting(3) informationModel(0) attribute(7)}
All nodes below this arc are reserved, from node 0 to node 7, except node 2. Is this an indication that a definition is missing in the Recommendation?
173. Q.751.4 (1998)
174. Q.752
175. Q.753 (1997)
176. Q.754 (1997)
Subclause 6.1: “Objects and operations”
OMAP runs tests on objects such as the MTP and SCCP routing tables. These objects are described here as "Object Classes" and are identified by an object identifier which specifies this Recommendation and the type of object. This structure is shown below for the OMAP object identifiers mtp-Routing-Tables, sccp-Routing-Tables and cvt‑Cic‑Tables.
|
oMAP |
OBJECT IDENTIFIER :: = { itu-t recommendation q 754 } |
|
mtp-Routing-Tables-1992 |
OBJECT IDENTIFIER :: = { oMAP 0 } |
|
sccp-Routing-Tables-1992 |
OBJECT IDENTIFIER :: = { oMAP 1 } |
|
cvt-Cic-Tables-1992 |
OBJECT IDENTIFIER :: = { oMAP 5 } |
Ø First OID above-mentioned has been registered this way: {itu-t(0) recommendation(0) q(17) q754(754)}
Ø {oMAP 0}, in second line of the board, is contradictory to the module defined in subclause 6.3: OMASE {itu-t(0) recommendation q 754 omase(0)}. Registration of this OID describes it as module named OMASE.
Ø The two last OIDs defined in the board haven’t been captured yet.
177. Q.755
178. Q.755.1
179. Q.755.2 (1997)
180. Q.765
181. Q.765bis
182. Q.765.1 (1998)
183. Q.765.1bis + Q.765.1bis Amd. 1
184. Q.765.5 Amd. 1
185. Q.765.4 (2000)
186. Q.765.5 + Q.765.5 Amd. 1
187. Q.768
188. Q.773 (1997)
189. Q.775
190. Q.812 + Q.812 App.I + Q.812 Amd. 1
191. Q.813 (1998)
192. Q.814 (2000)
193. Q.815 (2000)
194. Q.816.1
195. Q.821 (2000) + Q.821 Cor.1
196. Q.821.1
197. Q.822 (1994)
198. Q.822.1
199. Q.823 (1996): incomplete capture
{itu-t(0) recommendation(0) q(17) q823(823) informationModel(0)}
This OID and his following children have been captured:
specificExtensions(0) - asn1Modules(2) - managedObjectClass(3) – package(4) – nameBinding(5) – attribute(6) – action(7) – notification(8)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
200. Q.824.0 (1995): incomplete capture
{itu-t(0) recommendation(0) q(17) ca(824) dot(127) common(0) informationModel(0)}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) – package(4) – nameBinding(6) – attribute(7) – action(9)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
201. Q.824.1 (1995): incomplete capture
{itu-t(0) recommendation(0) q(17) ca(824) dot(127) isdn(1) informationModel(0)}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) – package(4) – parameter(5) - nameBinding(6) – attribute(7) – action(9)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
202. Q.824.2 (1995): incomplete capture
{itu-t(0) recommendation(0) q(17) ca(824) dot(127) isdnss(2) informationModel(0)}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
203. Q.824.3 (1995)
204. Q.824.4 (1995)
205. Q.824.5 (1997): incomplete capture
{itu-t(0) recommendation(0) q(17) ca(824) dot(127) v5interface(5) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtensions(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9) – notification(10)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
Don’t forget to have a look at the technical corrigendum.
206. Q.824.6: incomplete capture
{itu-t(0) recommendation(0) q(17) ca(824) dot(127) bsm(6) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtensions(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9) – notification(10)
Download this recommendation in order to capture remaining OIDS. Only children of standardSpecificExtensions(0)and asn1Modules(2) have been registered.
207. Q.824.7: incomplete capture
{itu-t(0) recommendation(0) q(17) ca(824) dot(127) ebs(6) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtensions(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9) – notification(10)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
208. Q.825 (1998): incomplete capture
{itu-t(0) recommendation(0) q(17) q825(825) informationModel(0)}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(5) – attribute(6) – action(7) - notification(8)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
209. Q.831 (1997): incomplete capture
{itu-t(0) recommendation(0) q(17) q831(831) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtension(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – notification(10) – parameter(11)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
Don’t forget to have a look at the technical corrigendum.
210. Q.832.1 (1998): incomplete capture
{itu-t(0) recommendation(0) q(17) q832(832) dot(127) vb51(1) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtension(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9) - notification(10) –
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
Don’t forget to have a look at the technical corrigendum.
211. Q.832.2 (1999): incomplete capture
{itu-t(0) recommendation(0) q(17) q832(832) dot(127) vb52(2) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtension(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9) - notification(10) –
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
212. Q.832.3: incomplete capture
{itu-t(0) recommendation(0) q(17) q832(832) dot(127) coor(3) informationModel(0)}
This OID and his following children have been captured:
standardSpecificExtension(0) - asn1Modules(2) - managedObjectClass(3) – package(4) - nameBinding(6) – attribute(7) – action(9) - notification(10) –
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
213. Q.833.1: incomplete capture
214. Q.835 (1999): incomplete capture
{itu-t(0) recommendation(0) q(17) q835(835) informationModel(0)}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) – package(4) – parameter(5) - nameBinding(6) – attribute(7) – action(9) - notification(10) –
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
Don’t forget to have a look at the technical corrigendum.
215. Q.836.1 (2000): incomplete capture
{itu-t(0) recommendation(0) q(17) q835(835) informationModel(0)}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) – package(4) – nameBinding(6) – attribute(7) – action(9) - notification(10) – behaviour(11)
Download this recommendation in order to capture remaining OIDS. Only children of asn1Modules(2) have been registered.
216. Q.850 + Q.850 Addendum1 + Q.850 Amd. 1
217. Q.860 (2000)
218. Q.932 (1998) + Q.932 Amd. 1
219. Q.941
· Q.951.1?
· Q.951.2?
· Q.951.3?
· Q.951.4?
· Q.951.5?
· Q.951.6?
220. Q.951.7 (1997)
· Q.951.8?
221. Q.952 (1993)
222. Q.952.7 (1997)
223. Q.953.1
224. Q.953.2
225. Q.953.3 (1997)
226. Q.953.4
227. Q.953.5
228. Q.954.1 (1993)
Subclause 1.4: “Coding requirements”
Replace
Conference-Add-On-Operations {ccitt recommendation q 954 conference-add-on-operations-and-errors(1)}
with
Conference-Add-On-Operations {ccitt recommendation q 954 conference-add-on(1) operations-and-errors(1)}
229. Q.954.2 (1995)
230. Q.955.1 (1992)
231. Q.955.3 (1993)
232. Q.956.2 (1995)
233. Q.956.3 (1995)
234. Q.957.1 (1996)
235. Q.1218 + Q.1218 Addendum 1
236. Q.1219
237. Q.1228: incomplete capture
{itu-t(0) recommendation(0) q(17) q1228(1228) cs(2)}
This OID and his following children have been captured:
ac(3) – as(5) – rosObject(25) – contract(26) – package(27)
Download this recommendation in order to capture remaining OIDS.
Subclause 4.6: “Object identifiers”
This subclause defines an asn.1 module named spkmGssTokens. This module imports the following OID:
{iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) spkm(1) spkmGssTokens(10)}
Nodes spkm(1) and spkmGssTokens(10) haven’t been registered yet. Subclause 4.6 doesn’t indicate which recommendation defines them.
Appendix II: “Data types”
Subclause 2.4.3: “ Object identifier assignments”
The following object identifier assignments can be used as a starting point for identifying Mobility objects in Recommendation X.500.
id-at-inMobilityID OBJECT IDENTIFIER ::= {id-at-inMobility 0}
id-at-inMobilityPIN OBJECT IDENTIFIER ::= {id-at-inMobility 1}
id-at-inMobilityPrefix OBJECT IDENTIFIER ::= {id-at-inMobility 2}
id-at-inMobilitySubPrefix OBJECT IDENTIFIER ::= {id-at-inMobility 3}
id-oc-inMobilityUserProfile OBJECT IDENTIFIER ::= {id-oc-inMobility 0}
id-oc-inMobilityServiceProvider OBJECT IDENTIFIER ::= {id-oc-inMobility 1}
id-oc-inMobilitySubscriberGroup OBJECT IDENTIFIER ::= {id-oc-inMobility 2}
id-nf-inMobilityUserProfileNameForm OBJECT IDENTIFIER ::= {id-nf-inMobility 0}
id-nf-inMobilityServiceProviderNameForm OBJECT IDENTIFIER ::= {id-nf-inMobility 1}
id-nf-inMobilitySubscriberGroupNameForm OBJECT IDENTIFIER ::= {id-nf-inMobility 2}
Those OIDs haven’t been registered yet. This recommendation doesn’t indicate what value “id-at-inMobility” is.
238. Q.1229
Many OIDs are defined in Q.1229, but this recommendation doesn’t indicate the level of the tree where these OIDs must be created.
239. Q.1238.1: incomplete capture
{itu-t(0) recommendation(0) q(17) q1238(1238)}
This OID and his following children have been captured:
modules(1) - ac(3) – at(4) – as(5) – oc(6) – mt(7) – sf(11) – soa(21) – aca(24) - rosObject(25) – contract(26) – package(27) – avc(29)
Download this recommendation in order to capture remaining OIDS. Only children of modules(1) have been registered.
240. Q.1238.2
241. Q.1238.3
242. Q.1238.4
243. Q.1238.5
244. Q.1238.6
245. Q.1238.7
246. Q.1248.1
Ø {itu-t(0) recommendation(0) q(17) q1248(1248) ac(3) scf-ssfRouteMonitoringAC(33)}
Last arc of this OID should be replaced by the following identifier: scf-ssfRouteMonitoringAC(33).
Ø {itu-t(0) recommendation(0) q(17) q1248(1248) avc(29) assignment(2)}
Last arc of this OID should be replaced by the following identifier: basicService(2). By the way, this OID has been registered with this identifier.
Ø {itu-t(0) recommendation(0) q(17) q1248(1248) avc(29) assignment(3)}
Last arc of this OID should be replaced by the following identifier: lineIdentify(3). By the way, this OID has been registered with this identifier.
247. Q.1248.2
248. Q.1248.3
249. Q.1248.4
250. Q.1248.5
251. Q.1248.6
252. Q.1248.7
253. Q.1400 + Q.1400 Addendum 1
254. Q.1521
255. Q.1551
256. Q.1711
257. Q.1721
258. Q.1902.1
259. Q.1902.2
260. Q.1902.3
261. Q.1902.4
262. Q.1902.5
263. Q.1902.6
264. Q.2724.1
265. Q.2735.1
266. Q.2751.1
Subclause 8.10: “ Abstract syntax productions”
Ø {itu(0) recommendation(0) q(17) omap2(2751) part1(1) informationModel(0) attribute(7) maxLengthSscopUuField(9)}
This recommendation doesn’t indicate the meaning of abbreviation “Uu”.
Ø {itu(0) recommendation(0) q(17) omap2(2751) part1(1) informationModel(0) attribute(7) sscopTimerIdle(9)}
This recommendation doesn’t indicate the meaning of abbreviation “Idle”.
Ø {itu(0) recommendation(0) q(17) omap2(2751) part1(1) informationModel(0) attribute(7) longMessageSupported(36)}
{itu(0) recommendation(0) q(17) omap2(2751) part1(1) informationModel(0) attribute(7) vcTTpPointer(36)}
This recommendation assigns 2 different identifiers to node numbered 36, whereas it doesn’t defines node numbered 10 at the same level of the tree.