Standards and other documents defining OIDs
that are captured in the OID repository

Choose a category of documents:

  • ITU-T Recommendations
  • ISO and 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.

  1. G.774.01
  2. G.774.01 Cor.1
  3. G.774.1
  4. 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.

  1. G.774.03 + G.774.03 Cor.1
  2. G.774.04 + G.774.04 Cor.1
  3. G.774.4
  4. 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.

  1. 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.

  1. G.774.7 (11/1996)
  2. G.774.7 (02/2001)
  3. G.774.8 (04/1997)
  4. G.774.8 (02/2001)
  5. G.774.9 (02/1998)
  6. G.774.9 (02/2001)
  7. G.774.10
  8. G.775
  9. G.776.1
  10. G.776.3
  11. G.780
  12. G.781
  13. G.782
  14. G.783 + G.783 Amd. 1 + G.783 Cor.1
  15. G.784
  16. G.785
  17. G.791
  18. G.792
  19. G.793
  20. G.794
  21. G.795
  22. G.796 + G.796 Amd. 1
  23. G.797
  24. G.798 + G.798 Amd. 1
  25. G.801
  26. G.802
  27. G.803
  28. G.804
  29. G.805
  30. G.806
  31. G.807
  32. G.810
  33. G.811
  34. G.812
  35. G.813 + G.813 Cor.1
  36. G.854.1
  37. G.854.3
  38. G.854.6
  39. G.854.8
  40. G.854.10
  41. G.854.12
  42. G.854.16
  43. 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)}.

  1. G.950
  2. G.957
  3. G.958
  4. G.959.1
  5. G.966
  6. G.972
  7. G.973
  8. G.974
  9. G.975
  10. G.976
  11. G.977
  12. G.7041
  13. G.7042
  14. G.7710
  15. G.7712
  16. G.7713
  17. G.7714
  18. G.7715
  19. G.8080
  20. H.225.0
  21. H.235
  22. H.248
  23. H.460.1
  24. J.126
  25. J.166
  26. J.191
  27. J.192
  28. J.800.2
  29. Q.48
  30. Q.253
  31. Q.706
  32. Q.708
  33. Q.711
  34. Q.733.1
  35. Q.733.2
  36. Q.733.3 + Amd. 1
  37. Q.733.4
  38. Q.733.5
  39. Q.736.1
  40. Q.736.3
  41. 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.

  1. 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.

  1. 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 node2. Is this an indication that a definition is missing in the Recommendation?

  1. Q.751.4 (1998)
  2. Q.752
  3. Q.753 (1997)
  4. 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 "ObjectClasses" 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 cvtCicTables.

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 lineof 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.

  1. Q.755
  2. Q.755.1
  3. Q.755.2 (1997)
  4. Q.765
  5. Q.765bis
  6. Q.765.1 (1998)
  7. Q.765.1bis + Q.765.1bis Amd. 1
  8. Q.765.5 Amd. 1
  9. Q.765.4 (2000)
  10. Q.765.5 + Q.765.5 Amd. 1
  11. Q.768
  12. Q.773 (1997)
  13. Q.775
  14. Q.812 + Q.812 App.I + Q.812 Amd. 1
  15. Q.813 (1998)
  16. Q.814 (2000)
  17. Q.815 (2000)
  18. Q.816.1
  19. Q.821 (2000) + Q.821 Cor.1
  20. Q.821.1
  21. Q.822 (1994)
  22. Q.822.1
  23. 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.

  1. 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.

  1. 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.

  1. 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.

  1. Q.824.3 (1995)
  2. Q.824.4 (1995)
  3. 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.

  1. 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)andasn1Modules(2) have been registered.

  1. 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.

  1. 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.

  1. 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.

  1. 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.

  1. 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.

  1. 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.

  1. Q.833.1: incomplete capture
  2. 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.

  1. 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.

  1. Q.850 + Q.850 Addendum1 + Q.850 Amd. 1
  2. Q.860 (2000)
  3. Q.932 (1998) + Q.932 Amd. 1
  4. Q.941
  • Q.951.1?
  • Q.951.2?
  • Q.951.3?
  • Q.951.4?
  • Q.951.5?
  • Q.951.6?
  1. Q.951.7 (1997)
  • Q.951.8?
  1. Q.952 (1993)
  2. Q.952.7 (1997)
  3. Q.953.1
  4. Q.953.2
  5. Q.953.3 (1997)
  6. Q.953.4
  7. Q.953.5
  8. 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)}

  1. Q.954.2 (1995)
  2. Q.955.1 (1992)
  3. Q.955.3 (1993)
  4. Q.956.2 (1995)
  5. Q.956.3 (1995)
  6. Q.957.1 (1996)
  7. Q.1218 + Q.1218 Addendum 1
  8. Q.1219
  9. 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”.

  1. 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.

  1. 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.

  1. Q.1238.2
  2. Q.1238.3
  3. Q.1238.4
  4. Q.1238.5
  5. Q.1238.6
  6. Q.1238.7
  7. 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.

  1. Q.1248.2
  2. Q.1248.3
  3. Q.1248.4
  4. Q.1248.5
  5. Q.1248.6
  6. Q.1248.7
  7. Q.1400 + Q.1400 Addendum 1
  8. Q.1521
  9. Q.1551
  10. Q.1711
  11. Q.1721
  12. Q.1902.1
  13. Q.1902.2
  14. Q.1902.3
  15. Q.1902.4
  16. Q.1902.5
  17. Q.1902.6
  18. Q.2724.1
  19. Q.2735.1
  20. 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.

  1. Q.2932.1
  2. Q.2957.1 + Q.2957.1 Amd. 1
  3. Q.2964.1
  4. Q.2981
  5. Q.2982
  6. 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)}

  1. Q.2991.1
  2. Q.3303.1
  3. Q.3304.1
  4. T.4 + T.4 Amd.1 + T.4 Amd. 2
  5. T.30 + T.30 Amd. 1 + T.30 Amd. 2 + T.30 Amd. 3 + T.30 Amd. 4 + T.30 Cor.1
  6. T.43 + T.43 Amd. 1
  7. T.44 + T.44 Amd. 1
  8. T.80
  9. T.81
  10. T.82
  11. T.84 + T.84 Amd. 1
  12. T.86
  13. T.100
  14. T.107
  15. T.123
  16. 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};

  1. T.125 (1998)
  2. T.126 (1997)
  3. T.127 (1995)
  4. T.128 (1998)
  5. T.134 (1998)
  6. T.135 (1998)
  7. T.136 (1999)
  8. T.137 (2000)
  9. T.172 (1998)
  10. T.173 (1997)
  11. T.174
  12. T.175
  13. T.190
  14. T.191
  15. T.192 (1998)
  16. 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)}

  1. T.411 (1993) + T.411 Cor.1
  2. T.412 + T.412 Cor.1
  3. T.412 Cor.2
  4. T.413 (1994)
  5. T.414 + T.414 Cor. 1 + T.414 Cor. 2
  6. T.415 (1993) + T.415 Cor. 1 + T.415 Cor. 2
  7. T.416 (1993) + T.416 Cor. 1
  8. T.417 (1993) + T.417 Amd. 1 + T.417 Amd. 2 + T.417 Cor. 1
  9. T.418 (1993)
  10. T.419 (1995)
  11. T.421 (1994)
  12. T.422 (1999)
  13. T.424 (1996)
  14. T.433 (1992) + T.433 Amd. 1
  15. T.434 (1999)
  16. T.435 (1995)
  17. T.436 (1995)
  18. T.503 + T.503 Amd. 1 + T.503 Amd. 2 + T.503 Amd. 3 + T.503 Amd. 4 + T.503 Cor.1
  19. T.506
  20. T.611
  21. X.36
  22. X.110
  23. X.115
  24. X.116
  25. X.121
  26. X.122
  27. X.123
  28. X.124
  29. X.125
  30. X.130
  31. X.131
  32. X.134
  33. X.135
  34. X.136
  35. X.137
  36. X.138
  37. X.139
  38. X.140
  39. X.141
  40. X.144
  41. X.145
  42. X.146
  43. X.150
  44. X.160
  45. 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.

  1. X.163
  2. X.170
  3. X.171
  4. X.180
  5. X.181
  6. X.200
  7. X.207
  8. X.208
  9. X.209
  10. X.210
  11. X.211
  12. X.212
  13. X.213
  14. X.214
  15. X.215
  16. X.216
  17. X.217
  18. X.218
  19. X.219
  20. X.220
  21. X.222
  22. X.223
  23. X.224
  24. X.225
  25. X.226
  26. X.227
  27. X.228
  28. X.229
  29. X.233
  30. X.234
  31. X.235
  32. X.236
  33. X.237
  34. X.237 bis
  35. X.244
  36. X.245
  37. X.246
  38. X.247
  39. X.248
  40. X.249
  41. X.255
  42. X.256
  43. X.257
  44. X.263
  45. X.264
  46. X.272
  47. X.273
  48. X.281
  49. 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).

Notealso 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.

  1. 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.

  1. 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.

  1. 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.

  1. X.290
  2. X.292
  3. X.293
  4. X.294
  5. X.295
  6. X.296
  7. X.400
  8. X.403
  9. X.404
  10. X.407
  11. X.408
  12. X.411
  13. X.413
  14. X.419
  15. X.421
  16. X.445
  17. X.446
  18. X.460
  19. X.480
  20. X.481
  21. X.482
  22. X.483
  23. X.484
  24. X.485
  25. X.486
  26. X.487
  27. X.488
  28. X.500
  29. X.501
  30. X.509
  31. X.511
  32. X.518
  33. X.519
  34. X.520
  35. X.521
  36. X.525
  37. X.530
  38. X.581
  39. X.582
  40. X.583
  41. X.584
  42. X.585
  43. X.586
  44. X.601
  45. X.605
  46. X.606
  47. X.610
  48. X.612
  49. X.613
  50. X.614
  51. X.622
  52. X.623
  53. X.625
  54. X.630
  55. X.633
  56. X.634
  57. X.637
  58. X.638
  59. X.639
  60. X.641
  61. X.642
  62. X.650
  63. X.662
  64. X.665
  65. X.666
  66. X.669
  67. X.670
  68. X.671
  69. X.681
  70. X.682
  71. X.683
  72. X.690
  73. X.691
  74. X.692
  75. X.693
  76. X.700
  77. X.701
  78. X.702
  79. X.710
  80. X.711
  81. X.712
  82. X.720
  83. X.721
  84. X.723
  85. X.724
  86. X.725
  87. X.727
  88. X.730
  89. X.731
  90. X.732
  91. X.733
  92. X.734
  93. X.735
  94. X.736
  95. X.737
  96. X.738
  97. X.739
  98. X.740
  99. X.741
  100. X.742
  101. X.743
  102. X.744
  103. X.745
  104. X.748
  105. X.749
  106. 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.

  1. 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.

  1. 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.

  1. 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.

  1. X.770
  2. X.780
  3. X.780.1
  4. X.781
  5. 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.

  1. X.791
  2. X.800
  3. X.802
  4. X.803
  5. X.810
  6. X.811
  7. X.812
  8. X.813
  9. X.814
  10. X.815
  11. X.816
  12. X.830
  13. X.831
  14. X.832
  15. X.833
  16. X.834
  17. X.835
  18. X.841
  19. X.842
  20. X.851
  21. X.852
  22. X.853
  23. X.860
  24. X.861
  25. X.862
  26. X.863
  27. X.880
  28. X.881
  29. X.882
  30. 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.