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.

ITU-T Recommendations

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:

Annex A

          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)}

Annex B

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

ISO standards

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 2^nd WD 14888-3

23. ISO/IEC WD 15961

24. ISO/IEC WD 15962

25. ISO/IEC 19785

26. ISO/IEC 19794-2

27. ISO/IEC 19794-4

28. ISO/IEC 19794-5

29. ISO/IEC 29192-3

· And others not listed here.

IETF RFCs, I-Ds, BCPs, FYIs, STDs

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.

• BCP (33)
• BCP 64
• BCP 66 (no OID found)
• BCP 74
• draft-ietf-policy-core-schema-16
• draft-ietf-sigtran-sctp-mib-10
• draft-ietf-snmpconf-diffpolicy-09
• draft-mcdonald-iana-charset-mib-02
• FYI 16

• RFC 187 (no OID found)

• RFC (822)

• RFC (987)

• RFC (1026)

• RFC (1065) to (1067)

• RFC 1085 (no OID found)

• RFC (1095)

• RFC (1098)

• RFC (1115)
• RFC (1138)

1. RFC 1142

• RFC (1148)

2. RFC 1155
3. RFC 1156

• RFC 1157 (no OID found)

• RFC (1158)

• RFC (1162)

• RFC 1165 (no OID found)

• RFC (1186)

• RFC 1189 (no OID found)

4. RFC 1212
5. RFC (1213)
6. RFC 1214
   References "nameForms" and "interface" are not defined.
7. RFC 1215

• RFC (1218)

8. RFC 1224
9. RFC 1227

• RFC (1228)

10. RFC 1229
11. RFC 1230
12. RFC 1231

• RFC (1232) to (1233)

13. RFC 1238

• RFC (1243)
• RFC (1248)

• RFC (1252) to (1253)
• RFC (1255)

14. RFC 1269

• RFC (1271)

15. RFC 1274
    We have found the following errors:
    1. references "attributeType", "mhsAttributeType", "mhsObjectClass" and "objectClass" are not defined;
    2. ATTRIBUTE "singleLevelQuality" is missing its OID (which we took to be {pilotAttributeType 50}).
16. RFC 1276

• RFC (1284)

17. RFC 1285

• RFC (1286)

• RFC (1289)

• RFC (1298)

• RFC 1303 (no OID found)

• RFC (1304)

• RFC (1315) to (1318)

18. RFC 1319
19. RFC 1320
20. RFC 1321

• RFC (1327)

• RFC 1351 to 1352 (no OID found)

21. RFC 1353

• RFC (1354)

• RFC (1368)

22. RFC 1381
23. RFC 1382

• RFC (1389)

• RFC 1390 (no OID found)

• RFC (1398)
• RFC (1406) to (1407)

24. RFC 1414

• RFC (1417)

• RFC 1420 (no OID found)

25. RFC 1423

• RFC (1442) to (1444)

• RFC 1445 to 1446 (no OID found)

26. RFC 1447

• RFC (1448) to (1450)

27. RFC 1451
28. RFC 1461
29. RFC 1471
30. RFC 1472
31. RFC 1473
32. RFC 1474

• RFC (1484) to (1485)
• RFC (1487)

33. RFC 1493
34. RFC 1494

• RFC (1495)

35. RFC 1507

• RFC (1508)

• RFC (1509) (no OID found)

• RFC 1510 (no OID found)

36. RFC 1512
37. RFC 1513

• RFC (1514)

38. RFC (1515)

• RFC (1516)

39. RFC 1525
40. RFC 1559

• RFC (1565) to (1567)

• RFC (1573)

41. RFC 1592
42. RFC 1593

• RFC (1595) to (1596)

• RFC (1604)

43. RFC 1611
44. RFC 1612

• RFC (1623)

45. RFC 1628
46. RFC 1643

• RFC (1650)

47. RFC 1657
48. RFC 1658
49. RFC 1659
50. RFC 1660

• RFC (1665)

51. RFC 1666
52. RFC 1694

• RFC (1695)

53. RFC 1696
    Please note the 3 following assignments (and particularly the case difference between mdmM*IB* and mdmM*ib*):
    mdmMIB MODULE-IDENTITY
        LAST-UPDATED "9406120000Z"
        ORGANIZATION "IETF Modem Management Working Group"
        CONTACT-INFO
                "        Steven Waldbusser
                 Postal: Carnegie Mellon University
                         5000 Forbes Ave
                         Pittsburgh, PA, 15213
                         US
                    Tel: +1 412 268 6628
                    Fax: +1 412 268 4987
                 E-mail: waldbusser@cmu.edu"
        DESCRIPTION
                "The MIB module for management of dial-up modems."
        ::= { mdmMIB 1 }
    mdmMib OBJECT IDENTIFIER ::= { mib-2 38 }
    mdmMIBObjects OBJECT IDENTIFIER ::= { mdmMIB 1 }
    "mdmMib" isn't used elsewhere in the ASN.1 module and "mdmMIB" is a circular reference to itself.
    My guess is that the first two aforementioned assignments should be replaced with:
    mdmMIB MODULE-IDENTITY
        LAST-UPDATED "9406120000Z"
        ORGANIZATION "IETF Modem Management Working Group"
        CONTACT-INFO
                "        Steven Waldbusser
                 Postal: Carnegie Mellon University
                         5000 Forbes Ave
                         Pittsburgh, PA, 15213
                         US
                    Tel: +1 412 268 6628
                    Fax: +1 412 268 4987
                 E-mail: waldbusser@cmu.edu"
        DESCRIPTION
                "The MIB module for management of dial-up modems."
        ::= { mib-2 38 }
54. RFC 1697
55. RFC 1724
56. RFC 1742

• RFC (1743)

57. RFC 1747
58. RFC 1748
59. RFC 1749
60. RFC (1757)

• RFC 1758 (no OID found)

61. RFC (1759)

• RFC (1777) to (1779)
• RFC (1781)

62. RFC 1792
63. RFC 1801
64. RFC 1804

• RFC (1836) to (1838)

65. RFC 1850

• RFC 1901 (no OID found)

• RFC (1902)

• RFC (1903) (no OID found)

• RFC (1904) to (1908)

• RFC 1909 (no OID found)

66. RFC 1910

• RFC (1987)

67. RFC 2006
68. RFC 2011
69. RFC (2012)
70. RFC 2013
71. RFC 2020
72. RFC 2021
73. RFC 2024
74. RFC 2025

• RFC (2037)

• RFC 2040 (no OID found)

75. RFC 2051

• RFC (2064)

• RFC (2074) (no OID found)

• RFC (2078) (no OID found)

76. RFC 2079

• RFC (2089)

77. RFC 2096
78. RFC 2108
79. RFC 2115
80. RFC 2127
81. RFC 2128
82. RFC 2144

• RFC (2155)

83. RFC 2156
84. RFC 2157
85. RFC 2158
86. RFC 2160
87. RFC 2161
88. RFC 2164

• RFC 2188 (no OID found)

89. RFC 2206
90. RFC 2213
91. RFC 2214
92. RFC 2232

• RFC (2233)

93. RFC 2238

• RFC (2239)

94. RFC 2247

• RFC (2248) to (2249)

• RFC (2251) (no OID found)

• RFC (2257)

• RFC (2261) to (2265)

95. RFC 2266
96. RFC 2268

• RFC (2271) to (2275)

97. RFC 2287
98. RFC 2293
99. RFC 2294

• RFC 2297 (no OID found)

100. RFC 2311
101. RFC 2312

• RFC (2313) to (2314)

102. RFC 2320
103. RFC 2325

• RFC (2358)

• RFC (2366)

104. RFC 2417

• RFC (2437)

105. RFC (2452)
106. RFC 2454
107. RFC 2455
108. RFC 2456
109. RFC 2457

• RFC (2459)

110. RFC 2465
111. RFC 2466

• RFC 2479 (no OID found)

• RFC (2493)

112. RFC 2494
113. RFC 2495
114. RFC 2496
115. RFC 2510
116. RFC 2511
117. RFC 2512
118. RFC 2513
119. RFC 2514
120. RFC 2515

• RFC 2524 (no OID found)

121. RFC 2528
122. RFC 2558

• RFC (2559)

123. RFC 2560
124. RFC 2561
125. RFC 2562

• RFC 2563 (no OID found)

126. RFC (2564)
127. RFC (2571)
128. RFC (2572)
129. RFC (2573)

• RFC (2574)

130. RFC (2575)
131. RFC (2576)
132. RFC 2578

• RFC 2579 (no OID found)

133. RFC 2580
134. RFC 2584

• RFC (2591) to (2592)

135. RFC 2594
136. RFC 2601

• RFC 2602 to 2603 (no OID found)

137. RFC 2605

• RFC (2611) (no OID found)

138. RFC 2613
139. RFC 2618
140. RFC 2619
141. RFC 2620
142. RFC 2621

• RFC (2630)

143. RFC 2633
144. RFC 2634
145. RFC 2649
146. RFC 2662
147. RFC (2665)
148. RFC 2666
149. RFC 2667
150. RFC (2668)
151. RFC 2669
152. RFC 2670
153. RFC 2674
154. RFC 2677
155. RFC 2707
156. RFC 2720

• RFC 2730 (no OID found)

157. RFC 2737

• RFC 2741 (no OID found)

158. RFC 2742

• RFC 2743 (no OID found)

• RFC 2744 (no OID found)

159. RFC 2758
160. RFC 2786
161. RFC 2787
162. RFC 2788
163. RFC 2789
164. RFC 2790
165. RFC 2797
166. RFC 2819

• RFC 2822
• RFC 2828 (no OID found)

167. RFC 2837
168. RFC 2847

• RFC (2851)

• RFC 2853 (no OID found)

169. RFC 2856
170. RFC 2863
171. RFC 2864
172. RFC 2875
173. RFC 2876

• RFC (2885) (no OID found)

• RFC 2895 (no OID found)

174. RFC 2898
175. RFC 2922
176. RFC 2925

• RFC 2926 (no OID found)

177. RFC 2932
178. RFC 2933
179. RFC 2934
180. RFC 2940
181. RFC 2954
182. RFC 2955
183. RFC 2959
184. RFC 2981
185. RFC 2982
186. RFC 2984
187. RFC 2985
188. RFC 2986

• RFC 2994 (no OID found)

• RFC 2999 (no OID found)

189. RFC 3014

• RFC 3015 (no OID found)

190. RFC 3019
191. RFC 3020
192. RFC 3029
193. RFC 3039
194. RFC 3055
195. RFC 3058

• RFC 3060 (no OID found)

196. RFC 3062

• RFC 3065 (no OID found)

197. RFC 3083
198. RFC 3114
199. RFC 3125
200. RFC 3126
201. RFC 3144

• RFC 3145 (no OID found)

202. RFC 3159
203. RFC 3161

• RFC 3163 (no OID found)

204. RFC 3165
205. RFC 3176
206. RFC 3183
207. RFC 3185

• RFC 3198 (no OID found)

208. RFC 3201
209. RFC 3202

• RFC (3211)

210. RFC 3217
211. RFC 3231
212. RFC 3273
213. RFC 3274
214. RFC 3276
215. RFC 3278
216. RFC 3279
     The OBJECT IDENTIFIER value "id-characteristic-two-basis" is defined twice in RFC3279:
     1. in the (informal) body, the last arc is "basisType(1)";
     2. in the ASN.1 module, the last arc is "basisType(3)".
     Which one is correct? (I guess it is the second which is already available in our OID repository as http://www.oid-info.com/get/1.2.840.10045.1.2.3)
217. RFC 3280
     Note that the OBJECT IDENTIFIER value is (rightly) defined as {iso(1) member-body(2) us(840) x9-57(10040) 2} in the body where as in is wrongly defined as {**joint-iso-itu-t(2)** member-body(2) us(840) x9cm(10040)} in section A.2. Also note that, whilst this is not forbidden, the identifier associated with arc 10040 is x9-57 in the body whereas it is x9cm in section A.2.
     Note that the OBJECT IDENTIFIER value "anyPolicy" uses the misspelt value id-ce-certicate-policies which should read id-ce-certificatePolicies.
218. RFC 3281
219. RFC 3287
220. RFC 3289
221. RFC 3291
222. RFC 3295
223. RFC 3317
224. RFC 3318
225. RFC 3369
226. RFC 3370
227. RFC 3371

• RFC 3375 (no OID found)

• RFC 3377 (no OID found)

228. RFC 3383 (submitted, author informed)
229. RFC 3394

• RFC 3406 (no OID found)

230. RFC 3411
231. RFC 3412
232. RFC 3413
233. RFC 3414
234. RFC 3415

• RFC 3416 (no OID found)

235. RFC 3417
236. RFC 3418
237. RFC 3419
238. RFC 3433
239. RFC 3434
240. RFC 3440
241. RFC 3447

• RFC 3494 (no OID found)

242. RFC 3498
243. RFC 3512

• RFC 3525 (no OID found)

244. RFC 3559
245. RFC 3560
246. RFC 3565

• RFC 3566 (no OID found)

247. RFC 3571

• RFC 3572 to 3583 (no OID found)

248. RFC 3584

• RFC 3575 to 3590 (no OID found)

249. RFC 3591
250. RFC 3592
251. RFC 3593

• RFC 3594 (no OID found)
• RFC 3597 to 3598 (no OID found)
• RFC 3601 (no OID found)

252. RFC 3606

• RFC 3610 (no OID found)

253. RFC 3621
254. RFC 3635
255. RFC 3636
256. RFC 3637

• RFC 3647 (no OID found)

257. RFC 3657
258. RFC 3673
259. RFC 3674

• RFC 3703 (no OID found)

260. RFC 3705

• RFC 3712 (no OID found)
• RFC 3727 (no OID found)

261. RFC 3728
262. RFC 3729
263. RFC 3737
264. RFC 3747
265. RFC 3770
266. RFC 3779
267. RFC 3805
268. RFC 3806
269. RFC 3808
270. RFC 3811
271. RFC 3812
272. RFC 3813
273. RFC 3814
274. RFC 3815
275. RFC 3816
276. RFC 3820
277. RFC 3826
278. RFC 3872
279. RFC 3873
280. RFC 3909
281. RFC 3928
282. RFC 3944 (no OID found)
283. RFC 4008
284. RFC 4022
285. RFC 4044
286. RFC 4055
287. RFC 4069
288. RFC 4070
289. RFC 4087
290. RFC 4108
291. RFC 4120
292. RFC 4133
293. RFC 4150
294. RFC 4178
295. RFC 4188
296. RFC 4210
297. RFC 4211
298. RFC 4212
299. RFC 4220
300. RFC 4231
301. RFC 4262
302. RFC 4268
303. RFC 4273

• RFC 4275 (no OIDs found)

304. RFC 4292
305. RFC 4293
306. RFC 4295
307. RFC 4318
308. RFC 4319
309. RFC 4322
310. RFC 4327
311. RFC 4357
312. RFC 4363
313. RFC 4369
314. RFC 4373
315. RFC 4404
316. RFC 4438
317. RFC 4439
318. RFC 4444
319. RFC 4455
320. RFC 4490
321. RFC 4491
322. RFC 4498
323. RFC 4544
324. RFC 4545
325. RFC 4546
326. RFC 4556
327. RFC 4560
328. RFC 4624
329. RFC 4625
330. RFC 4626
331. RFC 4631

• RFC 4663 (no OIDs found)

332. RFC 4668
333. RFC 4669
334. RFC 4670
335. RFC 4671
336. RFC 4672
337. RFC 4673
338. RFC 4683
339. RFC 4706
340. RFC 4711
341. RFC 4747
342. RFC 4780
343. RFC 4805
344. RFC 4807
345. RFC 4836
346. RFC 4837
347. RFC 4878
348. RFC 4935
349. RFC 4936
350. RFC 4939
351. RFC 4945
352. RFC 4983
353. RFC 4985
354. RFC 4998
355. RFC 5017
356. RFC 5060
357. RFC 5097
358. RFC 5098
359. RFC 5126
360. RFC 5131
361. RFC 5132
362. RFC 5208
363. RFC 5240
364. RFC 5280
365. RFC 5324
366. RFC 5428
367. RFC 5480
368. RFC 5488
369. RFC 5519
370. RFC 5525
371. RFC 5601
372. RFC 5602
373. RFC 5603
374. RFC 5604
375. RFC 5605
376. RFC 5639
377. RFC 5643
378. RFC 5650
379. RFC 5652
380. RFC 5676
381. RFC 5728
382. RFC 5751
383. RFC 5752
384. RFC 5753
385. RFC 5754
386. RFC 5755
387. RFC 5758
388. RFC 5794
     The OID of the ASN.1 module in appendix B is wrong: {iso(1) member-body(2) korea(400) nsri(200046) algorithm (1) symmetric-encryption-algorithm(1) asn1-module(0) alg-oids(0)}. The country code for Korea is 410 (as correctly used in the other OIDs), not 400.

• RFC 5803 (no OIDs found)

389. RFC 5813
390. RFC 5815
391. RFC 5833
392. RFC 5834
393. RFC 5911
394. RFC 5912
395. RFC 5913
396. RFC 5914
397. RFC 5915
398. RFC 5916
399. RFC 5917
400. RFC 5958
401. RFC 6010
402. RFC 6031
403. RFC 6032
404. RFC 6109
405. RFC 6113
406. RFC 6170
407. RFC 6171
408. RFC 6173
409. RFC 6187
410. RFC 6210
411. RFC 6211

• RFC 6484 (no OIDs found)
• RFC 6487 (no OIDs found)
• RFC 6490 (no OIDs found)

Miscellaneous

• 3GPP TS 29.002 V7.5.0 (Sep 2006)
• Canada: GOC PKI Object Identifiers - Governance and Registration Process
• Cisco SNMP MIBs (including CISCO-LOCAL-DIRECTOR-MIB)
• COSIRA OID descriptions (15 June 2005)
• DICOM Part 5: Data Structures and Encoding
• GnuPG OID Register
• Harald Alvestrand's OID repository
• HL7:
• Registered HL7 OIDs (files fulloidroot.pdf, codingsystems.pdf and memberroots.pdf dated April 30, 2004)
• OIDs for use in European HL7 artefacts (v. 1.1, 15 Aug 2004)
• UK Issued OIDs (5 May 2011)
• IANA:
• media feature tags
• network management parameters (SMI numbers)
• private enterprise numbers
• ISO/IEC 6523-1 list of International Code Designators (ICDs)
• Microsoft:

· http://support.microsoft.com/kb/287547

· http://technet.microsoft.com/library/dd875548

· http://technet.microsoft.com/library/dd875530

· http://technet.microsoft.com/library/ee424312

• MIT OIDs
• Mozilla PKI1 OIDs
• Nederlands Normalisatie-instituut (NEN)
• Nederlands Registratie uitgegeven OID's PKI voor de overheid
• NIST Cryptographic Algorithm Object Registration
• oidview.com
• Peter Gutmann's dumpasn1.cfg file
• Phil Griffin's website
• PKIX OIDs
• TeleTrusT Deutschland e.V.
• Terena's Directory Schema Registry
• SMI Network Management Directory Policy Core Information Model LDAP Schema
• Swedish OIDs assigned by the Swedish Standards Institute (SIS)