Communication interfaces

Go back Parent node: Specifications (1.3.6.1.4.1.37476.3)

Technical information

Dot notation:	`1.3.6.1.4.1.37476.3.5`
ASN.1 notation:	`{ iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 37476 specifications(3) communication(5) }`
OID-IRI notation:	`/ISO/Identified-Organization/6/1/4/1/37476/Specifications/Communication`
WEID notation:	`weid:pen:SX0-3-5-7`
DER encoding:	`06:0A:2B:06:01:04:01:82:A4:64:03:05`

Description

Definition in the Assignment Advisory:

Definitions how systems and applications should communicate. For example, a JSON data structure embedded in another file or transferred inside a foreign protocol. If you want to define a data structure which is saved entirely in a file, then use the arc fileformat(1) instead. If you want to define a data structure which is sent entirely over a TCP/UDP connection, use the arc protocol(2) instead.

Registration Authority

ViaThinkSoft
E-Mail: oidra@viathinksoft.de
Daniel Marschall
ViaThinkSoft
Germany

Subordinate objects

ID	Base36	ASN.1 IDs (comma sep.)	IRI IDs (comma sep.)	RA	Comment	Created	Updated
10	A	oid-whois	OIDWhois	ViaThinkSoft		2021-02-28	2021-02-28

Alternative Identifiers

OIDplus Information Object Application Identifier (ISO/IEC 7816): aid:D276000186B20005005E3AD6528949DB (No PIX allowed)
Name based version 3 / MD5 UUID with namespace UUID_NAMEBASED_NS_OID: guid:628770af-f274-3462-bec2-72c1fa6d0566
Name based version 5 / SHA1 UUID with namespace UUID_NAMEBASED_NS_OID: guid:969f64c1-1b3a-59a7-b669-c6bf77398cee
Application Identifier (ISO/IEC 7816): aid:D276000186F62B0601040182A4640305 (No PIX allowed)