OID reference

group

2.6.6

Identification

Identifier and names

Parent
2.6 (mhs)
Node code
6
Node names
  • group
  • id-group
Numeric OID
2.6.6
URN notation
urn:oid:2.6.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{2 6 6}

  • {joint-iso-itu-t(2) mhs(6) group(6)}
  • {joint-iso-itu-t(2) mhs(6) id-group(6)}
  • {joint-iso-ccitt(2) mhs(6) group(6)}
  • {joint-iso-ccitt(2) mhs(6) id-group(6)}
OID-IRI notation
  • /2/6/6
  • /Joint-ISO-ITU-T/6/6
Named path variants
  • /joint-iso-itu-t/mhs/group
  • /joint-iso-itu-t/mhs/id-group
  • /joint-iso-ccitt/mhs/group
  • /joint-iso-ccitt/mhs/id-group

The displayed source records contain one distinct definition. Compare its source records.

id-group ID ::=
  {joint-iso-itu-t mhs(6) group(6)}

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Group
Sources for this description

OID Repository

View at oid-base.com
In his book "Understanding X.500: The Directory", page 379, David Chadwick says: Back in 1988 the experts defining the X.400 Recommendations had some T-shirts made, and each T-shirt was allocated an object identifier, under the stub {joint-iso-ccitt(2) mhs-motis(6) group(6)}. Thus each T-shirt owner was effectively allocated a unique object identifier. Unfortunately , D. Chadwick did not attend the X.400 meetings in 1988, so does not know who bought a T-shirt.

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Definitions without a descriptionITU official formal descriptions1 record · 1 source
id-group · unspecifiedITU official formal descriptions1 source

Status in source: unspecified.

Names: id-group

Technical details
{
  "smi_kind": "OBJECT IDENTIFIER",
  "definition": [
    "id-group",
    "ID",
    "::=",
    "{",
    "joint-iso-itu-t",
    "mhs",
    "(",
    "6",
    ")",
    "group",
    "(",
    "6",
    ")",
    "}"
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 2.6)

J. Craigie & C.-U. Manros

Current Registration Authority (inferred from ancestor 2)

ITU-T SG 17 & ISO/IEC JTC 1/SC 6

Direct children (3)

OIDNameDirect childrenDescendantsDescription
2.6.6.5 grimstad25 Al Grimstad
2.6.6.200 20019
2.6.6.444 44400 Andrew Draskoy

Siblings (10)

OIDNameDirect childrenDescendantsDescription
2.6.0 protocols, id-mhs-protocols448 This arc is for MHS (Message Handling Systems) application contexts and protocols.
2.6.1 ipms, id-ipms20249 Interpersonal messaging (IPMS).
2.6.2 asdc12 X.400 Abstract Service Definition Conventions, as found in X.407.
2.6.3 mts, id-mts1054 Mmessage transfer system (MTS).
2.6.4 ms, id-ms11154 Message store (MS).
2.6.5 arch, id-arch765 Overall architecture.
2.6.7 edims, id-edims20151 EDI (Electronic Data Interchange) messaging.
2.6.8 vmgs, id-vmgs19112 Voice Messaging System
2.6.9 management, id-management, mhs-management11546 MHS (Message Handling Systems) management.
2.6.10 routing, id-routing, id-mhs-routing696 MHS (Message Handling Systems) routing.