From 1b89aa4e0011512cca6635b302e95296ce8aed02 Mon Sep 17 00:00:00 2001 From: Daniel Gultsch Date: Mon, 20 Apr 2020 21:28:25 +0200 Subject: [PATCH 1/2] XEP-0167: add rtcp-mux element --- xep-0167.xml | 5 +++++ xep.ent | 1 + 2 files changed, 6 insertions(+) diff --git a/xep-0167.xml b/xep-0167.xml index 4e5f6dd8..c96e75ae 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -341,12 +341,14 @@ + ]]>

The &DESCRIPTION; element is intended to be a child of a Jingle &CONTENT; element as specified in XEP-0166.

The &DESCRIPTION; element MUST possess a 'media' attribute that specifies the media type, such as "audio" or "video", where the media type SHOULD be as registered at &ianamedia;.

The &DESCRIPTION; element MAY possess a 'ssrc' attribute that specifies the 32-bit synchronization source for this media stream, as defined in RFC 3550.

After inclusion of one or more &PAYLOADTYPE; child elements, the &DESCRIPTION; element MAY also contain a <bandwidth/> element that specifies the allowable or preferred bandwidth for use by this application type. The 'type' attribute of the <bandwidth/> element SHOULD be a value for the SDP "bwtype" parameter as listed in the &ianasdp;. For RTP sessions, often the <bandwidth/> element will specify the "session bandwidth" as described in Section 6.2 of RFC 3550, measured in kilobits per second as described in Section 5.2 of RFC 4566.

+

Also, the &DESCRIPTION; element MAY contain a <rtcp-mux/> element that specifies the ability to multiplex RTP Data and Control Packets on a single port as described in &rfc5761;.

The encodings SHOULD be provided in order of preference by placing the most-preferred payload type as the first &PAYLOADTYPE; child of the &DESCRIPTION; element and the least-preferred payload type as the last child.

The attributes of the &PAYLOADTYPE; element are as follows:

@@ -1759,6 +1761,9 @@ Romeo Juliet type='payloadElementType' minOccurs='0' maxOccurs='unbounded'/> + RFC 5574 RFC 5574: RTP Payload Format for the Speex Codec <http://tools.ietf.org/html/rfc5574>." > RFC 5576 RFC 5576: Source-Specific Media Attributes in the Session Description Protocol (SDP) <http://tools.ietf.org/html/rfc5576>." > RFC 5646 RFC 5646: Tags for Identifying Languages <http://tools.ietf.org/html/rfc5646>." > +RFC 5761 RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port <http://tools.ietf.org/html/rfc5761>." > RFC 5763 RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS) <http://tools.ietf.org/html/rfc5763>." > RFC 5766 RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/rfc5766>." > RFC 5785 RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs) <http://tools.ietf.org/html/rfc5785>." > From d91479d484f4701b2611a8e1ad8a733ef5674d64 Mon Sep 17 00:00:00 2001 From: Daniel Gultsch Date: Wed, 22 Apr 2020 09:43:41 +0200 Subject: [PATCH 2/2] XEP-0167: add version block for rtcp-mux change --- xep-0167.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0167.xml b/xep-0167.xml index c96e75ae..3332cb71 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -42,6 +42,12 @@ &seanegan; &robmcqueen; &diana; + + 1.2.0 + 2020-04-22 + dg +

Introduce <rtcp-mux/> element to signal the ability to multiplex RTP Data and Control Packets.

 + 1.1.2 2020-03-19