Standards
and other documents defining OIDs
that are captured in the OID repository
Choose a
category of documents:
· ITU-T Recommendations
·
ISO/IEC standards
·
IETF RFCs
·
Miscellaneous
Note:
mistakes found in OIDs defined in those documents are indicated as comments under
the standard number or document title.
Note: The list is not exhaustive.
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. J.126
159. J.166
160. J.191
161. J.192
162. J.800.2
163. Q.48
164. Q.253
165. Q.706
166. Q.708
167. Q.711
168.
Q.733.1
169.
Q.733.2
170.
Q.733.3 + Amd. 1
171.
Q.733.4
172.
Q.733.5
173.
Q.736.1
174.
Q.736.3
175.
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.
176.
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.
177. 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:
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. The 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. The 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. The 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?
178. Q.751.4 (1998)
179. Q.752
180. Q.753 (1997)
181. 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 } |
Ř The first OID
above-mentioned has been registered this way: {itu-t(0) recommendation(0) q(17) q754(754)}
Ř {oMAP 0}, in the second line of the table, is contradictory with 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 table
haven’t been captured yet.
182. Q.755
183.
Q.755.1
184.
Q.755.2 (1997)
185.
Q.765
186. Q.765bis
187. Q.765.1 (1998)
188.
Q.765.1bis + Q.765.1bis Amd. 1
189. Q.765.5 Amd. 1
190. Q.765.4 (2000)
191. Q.765.5 + Q.765.5 Amd. 1
192. Q.768
193. Q.773 (1997)
194. Q.775
195. Q.812 + Q.812 App.I + Q.812 Amd. 1
196. Q.813 (1998)
197. Q.814 (2000)
198. Q.815 (2000)
199. Q.816.1
200. Q.821 (2000) + Q.821 Cor.1
201. Q.821.1
202. Q.822 (1994)
203. Q.822.1
204.
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.
205.
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.
206.
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.
207.
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.
208. Q.824.3 (1995)
209. Q.824.4 (1995)
210.
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.
211.
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.
212.
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.
213.
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.
214.
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.
215.
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.
216.
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.
217.
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.
218.
Q.833.1: incomplete capture
219.
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.
220.
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.
221. Q.850 + Q.850 Addendum1 + Q.850 Amd. 1
222. Q.860 (2000)
223. Q.932 (1998) + Q.932 Amd. 1
224. Q.941
· Q.951.1?
· Q.951.2?
· Q.951.3?
· Q.951.4?
· Q.951.5?
· Q.951.6?
225. Q.951.7 (1997)
· Q.951.8?
226. Q.952 (1993)
227. Q.952.7 (1997)
228. Q.953.1
229. Q.953.2
230. Q.953.3 (1997)
231. Q.953.4
232. Q.953.5
233. 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)}
234. Q.954.2 (1995)
235. Q.955.1 (1992)
236. Q.955.3 (1993)
237. Q.956.2 (1995)
238. Q.956.3 (1995)
239. Q.957.1 (1996)
240. Q.1218 + Q.1218 Addendum 1
241. Q.1219
242.
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 ITU-T 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 is the value of “id-at-inMobility”.
243. 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.
244.
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.
245. Q.1238.2
246. Q.1238.3
247. Q.1238.4
248. Q.1238.5
249. Q.1238.6
250. Q.1238.7
251. 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.
252. Q.1248.2
253. Q.1248.3
254. Q.1248.4
255. Q.1248.5
256. Q.1248.6
257. Q.1248.7
258. Q.1400 + Q.1400 Addendum 1
259. Q.1521
260. Q.1551
261. Q.1711
262. Q.1721
263. Q.1902.1
264. Q.1902.2
265. Q.1902.3
266. Q.1902.4
267. Q.1902.5
268. Q.1902.6
269. Q.2724.1
270. Q.2735.1
271. 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 define node numbered 10 at
the same level of the tree.
272. Q.2932.1
273. Q.2957.1 + Q.2957.1 Amd. 1
274. Q.2964.1
275. Q.2981
276. Q.2982
277. Q.2984
Subclause 8.1: “Abstract definition
of the prenegotiation operations”
Ř Replace
{itu-t(0) recommendation(0)
q(17) 2982 cc-operations(1)}
with
{itu-t(0) recommendation(0)
q(17) 2981 cc-operations(1)}
Ř
Replace
{itu-t(0) recommendation(0) q(17)
2982 call-object-class-definitions(5)}
with
{itu-t(0) recommendation(0) q(17)
2981 call-object-class-definitions(5)}
278. Q.2991.1
279. T.4 + T.4 Amd.1 + T.4 Amd. 2
280. T.30 + T.30 Amd. 1 + T.30 Amd. 2 + T.30 Amd. 3 + T.30 Amd. 4 + T.30 Cor.1
281. T.43 + T.43 Amd. 1
282. T.44 + T.44 Amd. 1
283. T.80
284. T.81
285. T.82
286. T.84 + T.84 Amd. 1
287. T.86
288. T.100
289. T.107
290. T.123
291. T.124 (1998)
Subclause 8.7: “GCCPDU
definitions »
GCC-PROTOCOL DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
…
This subclause defines an ASN.1 module named
“GCC-PROTOCOL”. The problem is that this subclause
doesn’t indicate the level of the tree where this module has to be registered.
Recommendation ITU-T T.123 defines an equivalent module at the following
level of the tree : {itu-t(0)
recommendation(0) t(20) t123(123)annexb(2) 1}, where annexb(2) corresponds to the annex in which
the module is defined
Recommendation ITU-T
T.135 imports a module:
URST-PROTOCOL DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
-- Export all symbols
-- Imports definitions from T.124
IMPORTS
TextString,
SimpleTextString, DialingString, ExtraDialingString, SubAddressString,
H221NonStandardIdentifier, Key, NonStandardParameter, ChallengeResponse,
ChallengeRequest,
Privilege
FROM GCC-PROTOCOL {itu-t(0) recommendation(0) t(20) 124};
292. T.125 (1998)
293. T.126 (1997)
294. T.127 (1995)
295. T.128 (1998)
296. T.134 (1998)
297. T.135 (1998)
298. T.136 (1999)
299. T.137 (2000)
300. T.172 (1998)
301. T.173 (1997)
302. T.174
303. T.175
304. T.190
305. T.191
306. T.192 (1998)
307. T.330 (1988)
Annex
A defines the following ASN.1 module:
TLMAAbsService {ccitt-t330}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN…
But
ccitt-t330 is not a legal OID. We
think the OID should more or less look like:
TLMAAbsService {ITU-T Recommendation(0)
t(20) t330(330) tLMAAbsService(0)}
308. T.411 (1993) + T.411 Cor.1
309. T.412 + T.412 Cor.1
310. T.412 Cor.2
311. T.413 (1994)
312. T.414 + T.414 Cor. 1 + T.414 Cor. 2
313. T.415 (1993) + T.415 Cor. 1 + T.415 Cor. 2
314. T.416 (1993) + T.416 Cor. 1
315. T.417 (1993) + T.417 Amd. 1 + T.417 Amd. 2 + T.417 Cor. 1
316. T.418 (1993)
317. T.419 (1995)
318. T.421 (1994)
319. T.422 (1999)
320. T.424 (1996)
321. T.433 (1992) + T.433 Amd. 1
322. T.434 (1999)
323. T.435 (1995)
324. T.436 (1995)
325. T.503 + T.503 Amd. 1 + T.503 Amd. 2 + T.503 Amd. 3 + T.503 Amd. 4 + T.503 Cor.1
326. T.506
327.
T.611
328. X.36
329. X.110
330. X.115
331. X.116
332. X.121
333. X.122
334. X.123
335. X.124
336. X.125
337. X.130
338. X.131
339. X.134
340. X.135
341. X.136
342. X.137
343. X.138
344. X.139
345. X.140
346. X.141
347. X.144
348. X.145
349. X.146
350. X.150
351.
X.160
352.
X.162: incomplete
capture
{itu-t(0) recommendation(0) x(24) x162(162)}
This OID and his following children have been captured:
cnmAsn1Modules(2) - cnmmanagedObjectClass(3) - cnmpackage(4)
- cnmparameter(5) - cnmnameBinding(6)
- cnmattribute(7) - cnmattributeGroup(8)
- cnmaction(9) - cnmnotification(10)
- cnmFunctionalUnit(11)
– miscellaneous(12)
Download this Recommendation
in order to capture remaining OIDs. Only children of attribute(7) haven’t been captured yet.
353. X.163
354. X.170
355. X.171
356. X.180
357. X.181
358. X.200
359. X.207
360. X.208
361. X.209
362. X.210
363. X.211
364. X.212
365. X.213
366. X.214
367. X.215
368. X.216
369. X.217
370. X.218
371. X.219
372. X.220
373. X.222
374. X.223
375. X.224
376. X.225
377. X.226
378. X.227
379. X.228
380. X.229
381. X.233
382. X.234
383. X.235
384. X.236
385. X.237
386. X.237 bis
387. X.244
388. X.245
389. X.246
390. X.247
391. X.248
392. X.249
393. X.255
394. X.256
395. X.257
396. X.263
397. X.264
398. X.272
399. X.273
400. X.281
401.
X.282: incomplete capture
We wanted to capture the
following object identifier which is defined in C.3 (informative annex):
{iso(1) member-body(2)
us(840) 802dot3(10006) repeaterMgt(19) attribute(7) sysResetTime(47)}
Unfortunately, we don’t have any information about 802dot3(10006)
and repeaterMgt(19).
Note also that 802dot3(10006) is an illegal identifier in ASN.1: It shall begin with a lowercase
letter.
The following OIDs haven’t
been captured for the same reasons:
{iso(1) member-body(2)
us(840) 802dot3(10006) repeaterMgt(19) attribute(7) repeaterResetTimeStamp(48)}
{iso(1) member-body(2)
us(840) 802dot3(10006) repeaterMgt(19) action(9) resetSystem(49)}
{joint-iso-itu-t(2) datalink-layer(15)
management(0)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10)
Download this Recommendation in
order to capture the remaining OIDs, defined under those arcs. Only children of
asn1Modules(2) have been
captured.
402.
X.283: incomplete capture
{joint-iso-ccitt(2) network-layer(13)
management(0) nLM(2)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs. Only children of asn1Modules(2) have been
captured.
403.
X.284: incomplete capture
{joint-iso-ccitt(2) transport-layer(14) management(0)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs. Only children of asn1Modules(2) have been
captured.
404.
X.287: incomplete capture
{joint-iso-ccitt(2) ms(9) smi(3) part8(8)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs. Only children of asn1Modules(2) have been
captured.
405. X.290
406. X.292
407. X.293
408. X.294
409. X.295
410. X.296
411. X.400
412. X.403
413. X.404
414. X.407
415. X.408
416. X.411
417. X.413
418. X.419
419. X.421
420. X.445
421. X.446
422. X.460
423. X.480
424. X.481
425. X.482
426. X.483
427. X.484
428. X.485
429. X.486
430. X.487
431. X.488
432. X.500
433. X.501
434. X.509
435. X.511
436. X.518
437. X.519
438. X.520
439. X.521
440. X.525
441. X.530
442. X.581
443. X.582
444. X.583
445. X.584
446. X.585
447. X.586
448. X.601
449. X.605
450. X.606
451. X.610
452. X.612
453. X.613
454. X.614
455. X.622
456. X.623
457. X.625
458. X.630
459. X.633
460. X.634
461. X.637
462. X.638
463. X.639
464. X.641
465. X.642
466. X.650
467. X.662
468. X.665
469. X.666
470. X.669
471. X.670
472. X.671
473. X.681
474. X.682
475. X.683
476. X.690
477. X.691
478. X.692
479. X.693
480. X.700
481. X.701
482. X.702
483. X.710
484. X.711
485. X.712
486. X.720
487. X.721
488. X.723
489. X.724
490. X.725
491. X.727
492. X.730
493. X.731
494. X.732
495. X.733
496. X.734
497. X.735
498. X.736
499. X.737
500. X.738
501. X.739
502. X.740
503. X.741
504. X.742
505. X.743
506. X.744
507. X.745
508. X.748
509. X.749
510.
X.750: incomplete capture
{joint-iso-ccitt(2) ms(9) function(2) part16(16)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs.
511.
X.751: incomplete capture
{joint-iso-ccitt(2) ms(9) function(2) part17(17)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10) - relationshipClass(11) - relationshipRole(13)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs.
512.
X.753: incomplete capture
{joint-iso-ccitt(2) ms(9) function(2) part21(21)}
This OID and his following children have been captured:
standardSpecificExtensions(0) – asn1Modules(2) - managedObjectClass(3)
- package(4) - parameter(5) - nameBinding(6) -
attribute(7) - attributeGroup(8) - action(9) -
notification(10) - relationshipClass(11) – relationMapping(12) - relationshipRole(13)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs.
513.
X.754: incomplete capture
{itu-t(0) recommendation(0)
x(24) eecmod(754) 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, defined under those arcs.
514. X.770
515. X.780
516. X.780.1
517. X.781
518.
X.790: incomplete capture
{itu-t(0) recommendation(0)
x(24) x790(790) informationModel(0}
This OID and his following children have been captured:
asn1Modules(2) - managedObjectClass(3) -
package(4) – parameter(5) - nameBinding(6) -
attribute(7) - notification(10)
Download this Recommendation in
order to capture remaining OIDs, defined under those arcs.
519. X.791
520. X.800
521. X.802
522. X.803
523. X.810
524. X.811
525. X.812
526. X.813
527. X.814
528. X.815
529. X.816
530. X.830
531. X.831
532. X.832
533. X.833
534. X.834
535. X.835
536. X.841
537. X.842
538. X.851
539. X.852
540. X.853
541. X.860
542. X.861
543. X.862
544. X.863
545. X.880
546. X.881
547. X.882
548.
X.952
Recommendation ITU-T X.952 has been
assigned the arc trader(100) under the object identifier {joint-iso-itu-t(2)} in the international
registration tree. But the last number currently assigned under joint-iso-itu-t(2) is 24, so number 100 reserved for X.952 seams not correct. We propose
to assign the arc 25 to X.952 and name it odp instead of trader.
If this
proposition is accepted, the following changes have to be applied:
The ASN.1 module named TraderDefinitions has the following object
identifier:
{joint-iso-itu-t 2}
Arc 2 under joint-iso-itu-t is
reserved for ACSE.
Replace:
TraderDefinitions {joint-iso-itu-t 2}
with:
TraderDefinitions {joint-iso-itu-t odp(25} trader(0)
asn1Modules(2) traderDefinitions(0)}
Annex A defines object identifiers under {joint-iso-itu-t trader(100)}
Replace:
id-trader OBJECT IDENTIFIER ::= {joint-iso-itu-t trader(100)}
with:
id-trader OBJECT IDENTIFIER ::= {joint-iso-itu-t odp(25) trader(0)}
The ASN.1 module named PrinterServiceOfferDefinitions has the following object
identifier:
{joint-iso-itu-t 2}
Arc 2 under joint-iso-itu-t is
reserved to ACSE.
Replace:
PrinterServiceOfferDefinitions {joint-iso-itu-t 2}
with:
PrinterServiceOfferDefinitions {joint-iso-itu-t odp(25} trader(0)
asn1Modules(2) printerServiceOfferDefinitions (1)}
In the IMPORTS statement of module PrinterServiceOfferDefinitions, replace:
id-trader-at,
id-trader-oc-serviceOffer
FROM id-trader{joint-iso-itu-t
trader(100)};
with:
id-trader-at,
id-trader-oc-serviceOffer
FROM TraderDefinitions {joint-iso-itu-t odp(25} trader(0)
asn1Modules(2) traderDefinitions(0)};
549. Z.140
550. Z.200
551. Z.500
1. ISO 3166-1
2. ISO 6523
3. ISO/IEC FCD 7816-3
4. ISO/IEC FDIS 7816-4
5. ISO/IEC FCD 7816-15
6. ISO/IEC 8571-1 (+ Amd. + TCs)
7. ISO/IEC 8571-2 (+ Amd. + TCs)
8. ISO/IEC 8571-3 (+ Amd. + TCs)
9. ISO/IEC 8571-4 (+ Amd. + TCs)
10. ISO/IEC 8650-1
11. ISO/IEC 9040
12. ISO/IEC 9041-1
13. ISO/IEC 9041-2
14. ISO/IEC FDIS 9798-5
· ISO/IEC 10031-1
15. ISO/IEC 10031-2
16. ISO/IEC 10118-3
17. ISO/IEC 10166-1
18. ISO/IEC 10589
19. ISO/IEC 10740-2
20. ISO 14813
21. ISO/IEC CD 14888-2
22. ISO/IEC 2nd WD 14888-3
23. ISO/IEC WD 15961
24. ISO/IEC WD 15962
· And others not listed here.
Notes: Obsoleted RFCs are between round
brackets. RFCs preceded with a dot weren't taken into account (usually because
they are obsolete). RFCs whose OIDs were automatically extracted are preceded
with a number.