Group
View at oid-info.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.
ITU-T SG 17 & ISO/IEC JTC 1/SC 6
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
2.6.6.5 | grimstad | 1 | 1 | Al Grimstad |
2.6.6.444 | 444 | 0 | 0 | Andrew Draskoy |
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
2.6.0 | protocols | 4 | 48 | This arc is for MHS (Message Handling Systems) application contexts and protocols. |
2.6.1 | ipms | 20 | 164 | Interpersonal messaging (IPMS). |
2.6.2 | asdc | 1 | 2 | X.400 Abstract Service Definition Conventions, as found in X.407. |
2.6.3 | mts | 10 | 54 | Mmessage transfer system (MTS). |
2.6.4 | ms | 11 | 154 | Message store (MS). |
2.6.5 | arch | 7 | 63 | Overall architecture. |
2.6.7 | edims | 19 | 36 | EDI (Electronic Data Interchange) messaging. |
2.6.8 | vmgs | 18 | 25 | Voice Messaging System |
2.6.9 | management | 11 | 44 | MHS (Message Handling Systems) management. |
2.6.10 | routing | 6 | 96 | MHS (Message Handling Systems) routing. |