• Object identifiers (OIDs) and their registration authorities
  • Table of Contents
  • Part 1 – Introductory material
    • 1 Object Identifiers (OIDs) - What? Why? How? Who?
      • 1.1 What is an OID?
      • 1.2 What terminology is used?
      • 1.3 What is a registration authority?
      • 1.4 Why would I want an OID?
      • 1.5 How are they allocated?
      • 1.6 How do I get one?
      • 1.7 Who already has one?
      • 1.8 What else do I need to know?
    • 2 Intended audience
    • 3 Introduction to contents
    • 4 An introduction to the notation for specifying an OID value
  • Part 2 – Background and history
    • 5 ITU-T and ISO/IEC collaboration
    • 6 History of standardization of the OID
      • 6.1 The early years
      • 6.2 Decisions on use of names or numbers to identify arcs in the OID tree
      • 6.3 The current main standards for OIDs, including registration authority procedures
      • 6.4 The introduction of long arcs
      • 6.5 Emergence of the OID repository
      • 6.6 The OID resolution system (ORS)
  • Part 3 – OID tree structure, notations and encodings
    • 7 Structure of the OID tree
      • 7.1 A dissertation on trees
      • 7.2 Early principles established for the OID tree
    • 8 The high-level arcs and the naming of arcs
    • 9 ASN.1 notations for OIDs
      • 9.1 Initial illustrations
      • 9.2 Traditional notation
      • 9.3 The "dot" notation
      • 9.4 OID-IRI notation
      • 9.5 Encoding of OIDs
  • Part 4 – Practical use of OIDs
    • 10 The OID repository
      • 10.1 General description
      • 10.2 The OID repository FAQ page
      • 10.3 Accessing information in the OID repository
      • 10.4 How to update the OID repository
    • 11 The ITU-T module database
    • 12 Early and current use of OIDs
  • Part 5 – More recent developments
    • 13 Internationalization
    • 14 Rules on Unicode labels
    • 15 Long arcs
  • Part 6 – The OID Resolution System (ORS)
    • 16 Concepts and need
    • 17 Operation of the ORS
    • 18 Use of the DNS
  • Part 7 – Obtaining an object identifier, long arc, or DNS look-up capability
    • 19 Choosing a place to be hung from
      • 19.1 A few available options
      • 19.2 Main choices in simple cases
      • 19.3 The "Internet OID"
    • 20 An OID for sub-allocations in a country/state
      • 20.1 Simple allocation
      • 20.2 Use of Unicode labels for arcs under the arc "Country"
    • 21 An OID for an ITU-T Recommendation or International Standard
    • 22 An OID for some other organization or activity
    • 23 Managing sub-allocations, including a country registration authority
    • 24 Getting a long arc Unicode label
    • 25 How to obtain an ORS look-up capability via DNS for your node
    • 26 Discussion of minor conventions on OIDs
  • Appendix A – Summary of the high-level arcs
    • A.1 General
    • A.2 Arc 0 from the root and its sub-arcs
    • A.3 Arc 1 from the root and its sub-arcs
    • A.4 Arc 2 from the root and its sub-arcs
  • Appendix B – Encodings of Object Identifiers
    • B.1 Early decisions on binary encodings
    • B.2 The basic principle of binary OID encodings
    • B.3 Consequences in later years
    • B.4 XML encodings in protocols
  • Appendix C – Operation of a country Registration Authority
    • C.1 General
    • C.2 Check-list of actions to be taken
    • C.3 Historical relics and changes
    • C.4 Suggested template for a letter notifying the operation of an RA for a country
    • C.5 Examples of letters
  • Appendix D – Abbreviations (acronyms) and other terms
  • Annotated Bibliography