Overview#

Audio is sound communication

Ok, technically, audio does not require a recipient however for our purposes it does.

Audio is also a Media-type

LDAP (eDirectory) Attribute Definition#

The Audio AttributeTypes is defined in RFC 2798 as:

• OID of 0.9.2342.19200300.100.1.55
  • eDirectory
  • Microsoft Active Directory
• NAME: Audio
• DESC:
• OBSOLETE flag (only if present)
• EQUALITY: OctetStringMatch
• ORDERING:
• SYNTAX: 1.3.6.1.4.1.1466.115.121.1.40 Octet String
• UPPERBOUND: (Depends on LDAP Server Implementation)
• USAGE UserApplications
• Extended Flags:
  • (only if present)
• Used as MUST in:
• Used MAY in:
  • inetOrgPerson

The Audio AttributeTypes is defined in RFC 1274 as:

• OID of 1.3.6.1.4.1.1466.115.121.1.4
• NAME: Audio
• DESC:
• OBSOLETE flag (only if present)
• EQUALITY:
• ORDERING:
• SYNTAX: (unknown)
• SINGLE-VALUE (only if present)
• NO-USER-MODIFICATION (only if present)
• USAGE UserApplications
• Extended Flags:
  • (only if present)
• Used as MUST in:
• Used MAY in:

The u-law encoding of a value with Audio syntax is the octets of the value itself, an 8KHz uncompressed encoding compatible with the Sun Microsystems Operating System 4.1.3 'play' utility

More Information#

There might be more information for this subject on one of the following:

• 0.9.2342.19200300.100.1.55
• 1.3.6.1.4.1.1466.115.121.1.4
• Audio Surveillance
• Blinding Identity Taxonomy
• Data representation
• Deep Neural networks
• HAMMERCHANT
• InetOrgPerson
• International Standard Recording Code
• LDAP Object Identifier Descriptors
• Media-type
• Perfect Security
• Real-time Transport Protocol
• User-generated content
• Voice

0.9.2342.19200300.100.1.55