1.8 Vendor-Extensible Fields

The following fields in this protocol can be extended by vendors:

  • Custom Attributes in the Manifest Response: This capability is provided by the VendorExtensionAttributes field, as specified in section 2.2.2. Implementers can ensure that extensions do not conflict by assigning extensions an XML namespace that is unique to their implementation.

  • Custom Data Elements in the Manifest Response: This capability is provided by the VendorExtensionDataElement field, as specified in section 2.2.2.6.1. Implementers can ensure that extensions do not conflict by assigning extensions an XML namespace that is unique to their implementation.

  • Custom Boxes in the Fragment Response: This capability is provided by the VendorExtensionUUID field, as specified in section 2.2.4.

  • Custom Media Formats for Audio: This capability is provided by the AudioTag and CodecPrivateData fields, as specified in section 2.2.2.5. Implementers can ensure that extensions do not conflict by assigning extensions a GUID (as specified in [MS-DTYP] section 2.3.4.1) that is embedded in the CodecPrivateData field, as specified in [WFEX].

  • Custom Descriptive Codes for Media Formats: This capability is provided by the FourCC field, as specified in section 2.2.2.5. Implementers can ensure that extensions do not conflict by registering extension codes with the MPEG4-RA, as specified in [ISO/IEC-14496-12].

  • Custom HTTP Headers in the Manifest Response: This capability is provided by the underlying transport layer (HTTP), as specified in [RFC2616] section 6.

  • Custom HTTP Headers in the Fragment Response: This capability is provided by the underlying transport layer (HTTP), as specified in [RFC2616] section 6.

  • Custom HTTP Headers in the Fragment Request: This capability is provided by the underlying transport layer (HTTP), as specified in [RFC2616] section 5.

  • Custom HTTP Headers in the Manifest Request: This capability is provided by the underlying transport layer (HTTP), as specified in [RFC2616] section 5.

Show: