From be6bc3a1e05f30263da6cdfd7c25c59f04d6faad Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Fri, 5 Mar 2021 21:58:28 +0100 Subject: [PATCH 1/3] xep-0294: add mapping for a=extmap-allow-mixed --- xep-0294.xml | 86 +++++++++++++++++++++++++++++++--------------------- xep.ent | 1 + 2 files changed, 52 insertions(+), 35 deletions(-) diff --git a/xep-0294.xml b/xep-0294.xml index cadb51c8..828b48a6 100644 --- a/xep-0294.xml +++ b/xep-0294.xml @@ -19,6 +19,7 @@ XEP-0167 RFC 5285 + RFC 8285 @@ -61,7 +62,7 @@

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

 @@ -69,48 +70,52 @@

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

  1. Enable negotiations of the RTP Header extensions as defined in - RFC 5285.
    2. + RFC 5285 and 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:

- - - - - - - - - - - - - - - - - - - - - - - - - -
AttributeDescriptionInclusionPossible values
idThe ID of the extensionsREQUIRED1-256, 4096-4351
uriThe URI that defines the extensionREQUIREDAny valid URI
sendersWhich party is allowed to send the negotiated RTP Header ExtensionsOPTIONAL (defaults to "both")"initiator", "responder", and "both"
- -

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.

+

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

+ + + + + + + + + + + + + + + + + + + + + + + + + +
AttributeDescriptionInclusionPossible values
idThe ID of the extensionsREQUIRED1-256, 4096-4351
uriThe URI that defines the extensionREQUIREDAny valid URI
sendersWhich party is allowed to send the negotiated RTP Header ExtensionsOPTIONAL (defaults to "both")"initiator", "responder", and "both"
+ +

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.

 @@ -132,6 +137,9 @@ describe it. Any other form of parameter can be stored as the 'key' attribute in 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;) @@ -150,11 +158,13 @@ describe it. Any other form of parameter can be stored as the 'key' attribute in uri='urn:ietf:params:rtp-hdrext:ntp-56' id='4907'/> + ]]>

Example reply where the responder accepts the timestamp offset - and the 56-bit synchronisation metadata header extensions.

+ and the 56-bit synchronisation metadata header extensions as well as the + <extmap-allow-mixed/>.

@@ -186,6 +196,10 @@ describe it. Any other form of parameter can be stored as the 'key' attribute in 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 5285 section 6 into equivalent XMPP:

@@ -206,6 +221,7 @@ a=extmap:3 URI-frametype + ]]> diff --git a/xep.ent b/xep.ent index 000bce20..98cdeb85 100644 --- a/xep.ent +++ b/xep.ent @@ -702,6 +702,7 @@ THE SOFTWARE. RFC 8446 RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 <http://tools.ietf.org/html/rfc8446>." > RFC 8467 RFC 8467: Padding Policies for Extension Mechanisms for DNS (EDNS(0)) <http://tools.ietf.org/html/rfc8467>." > RFC 8484 RFC 8484: DNS Queries over HTTPS (DoH) <http://tools.ietf.org/html/rfc8484>." > +RFC 8285 RFC 8285: A General Mechanism for RTP Header Extensions <http://tools.ietf.org/html/rfc8285>." > From 1b77f50b115fd65ce2120c5b1ec9aa56944e9012 Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Mon, 8 Mar 2021 13:47:17 +0100 Subject: [PATCH 2/3] update to 8285 --- xep-0294.xml | 11 +++++------ xep.ent | 1 - 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/xep-0294.xml b/xep-0294.xml index 828b48a6..37641f8d 100644 --- a/xep-0294.xml +++ b/xep-0294.xml @@ -8,7 +8,7 @@
Jingle RTP Header Extensions Negotiation This specification defines an XMPP extension to negotiate - the use of the use of RTP Header Extension as defined by RFC 5285 + the use of the use of RTP Header Extension as defined by RFC 8285 with Jingle RTP sessions &LEGALNOTICE; 0294 @@ -18,7 +18,6 @@ Council XEP-0167 - RFC 5285 RFC 8285 @@ -62,7 +61,7 @@

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

 @@ -70,7 +69,7 @@

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

  1. Enable negotiations of the RTP Header extensions as defined in - RFC 5285 and RFC 8285.
    2. + RFC 8285.
  2. Map these parameters to Session Description Protocol (SDP; see &rfc4566;) to enable interoperability.
@@ -192,7 +191,7 @@

The <rtp-hdrext/> element maps to the "a:extmap=" SDP line - defined in RFC 5285. The ID is mapped to the 'id' attribute, the + 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.

@@ -200,7 +199,7 @@ 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 5285 section 6 into equivalent XMPP:

+

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

RFC 5246 RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 <http://tools.ietf.org/html/rfc5246>." > RFC 5256 RFC 5256: Internet Message Access Protocol - SORT and THREAD Extensions <http://tools.ietf.org/html/rfc5256>." > RFC 5280 RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile <http://tools.ietf.org/html/rfc5280>." > -RFC 5285 RFC 5285: A General Mechanism for RTP Header Extensions <http://tools.ietf.org/html/rfc5285>." > RFC 5322 RFC 5322: Internet Message Format <http://tools.ietf.org/html/rfc5322>." > RFC 5359 RFC 5359: Session Initiation Protocol Service Examples <http://tools.ietf.org/html/rfc5359>." > RFC 5389 RFC 5389: Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/rfc5389>." > From b69af45439e802e603e4b950ac8457ec2c3c061d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Sun, 28 Mar 2021 14:30:10 +0200 Subject: [PATCH 3/3] XEP-0294: add revision block --- xep-0294.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0294.xml b/xep-0294.xml index 37641f8d..c527d533 100644 --- a/xep-0294.xml +++ b/xep-0294.xml @@ -33,6 +33,12 @@ olivier.crete@collabora.co.uk olivier.crete@collabora.co.uk + + 1.1 + 2021-03-28 + ph +

Add mapping for a=extmap-allow-mixed

 + 1.0 2015-08-11