This documents specifies how to negotiate the use of the RTP Header Extensions as defined by &rfc8285; with Jingle RTP sessions.

The Jingle extension defined herein is designed to meet the following requirements:

1. Enable negotiations of the RTP Header extensions as defined in RFC 8285.
2. Map these parameters to Session Description Protocol (SDP; see &rfc4566;) to enable interoperability.

This specification defines a new element, <rtp-hdrext/>, that can be inserted in the <description/> element of a XEP-0167 RTP session.

The attributes of the <rtp-hdrext/> element are:

Any type of RTP Header Extension that requires extra parameters in the a=b form can embed <parameter/> elements to describe it. Any other form of parameter can be stored as the 'key' attribute in a parameter element with an empty value.

This specification defines a new element, <extmap-allow-mixed/>, that can be inserted in the <description/> element of a XEP-0167 RTP session. The element has no attributes.

RTP header extensions are negotiated along the codecs. They follow the same Offer/Answer mechanism based on SDP Offer/Answer. The initiator signals which RTP header extensions it wants to send or receive in the the <session-initiate/> iq stanza. If the responder does not understand the type of header extensions, it MUST remove the element from the reply. If the responder does not wish to provide or receive some kind of RTP header extension, it MUST remove the relevant element from the reply. It MUST then send the remaining elements it wants to keep as-is without modifying them in the <session-accept/> iq stanza.

It MUST NOT add any <rtp-hdrext/> element that was not offered by the initiator. The responder MAY downgrade the senders field from "both" to "initator" or "responder", but MUST NOT modify it if it is "initator" or "responder".

The usage of the <extmap-allow-mixed/> is governed by the SDP Offer/Answer mechanism as well.

Example negotiation where the initiator offers to use the timestamp offset header extension as defined in &rfc5450; and also the requests synchronisation metadata header extension (&rfc6051;) with either the 56-bit or the 64-bit format.

Example reply where the responder accepts the timestamp offset and the 56-bit synchronisation metadata header extensions as well as the <extmap-allow-mixed/>.

Another reply to the same request where the responder accepts only the synchronisation data header extension with the 64-bit format.

The <rtp-hdrext/> element maps to the "a:extmap=" SDP line defined in RFC 8285. The ID is mapped to the 'id' attribute, the direction to the 'senders' attribute and the URI to the 'uri' attribute.

The <extmap-allow-mixed/> element maps to the "a=extmap-allow-mixed" SDP line defined in RFC 8285. Note that a session-level line might need to be mapped to all <description/> elements.

Example conversion of a incomplete sample fragment of a SDP taken from RFC 8285 section 7 into equivalent XMPP:

To advertise its support for Generic Header extensions in Jingle RTP Sessions, when replying to &xep0030; information requests an entity MUST return the following features:

1. URNs for any version of this protocol that the entity supports -- e.g., "urn:xmpp:jingle:apps:rtp:rtp-hdrext:0" for the current version

An example follows:

This document requires no interaction with the Internet Assigned Numbers Authority (IANA).

Thanks to Youness Alaoui for his feedback.