[MMUSIC] BUNDLE: Modified text based on decision to mandate RTP/RTCP mux for bundled RTP-based media
Christer Holmberg <christer.holmberg@ericsson.com> Fri, 06 November 2015 08:03 UTC
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BCA11B36DA for <mmusic@ietfa.amsl.com>; Fri, 6 Nov 2015 00:03:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXqd6tezVsR0 for <mmusic@ietfa.amsl.com>; Fri, 6 Nov 2015 00:03:34 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 623551B36FE for <mmusic@ietf.org>; Fri, 6 Nov 2015 00:03:33 -0800 (PST)
X-AuditID: c1b4fb2d-f79626d000004282-97-563c5ed34d43
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 0E.BA.17026.3DE5C365; Fri, 6 Nov 2015 09:03:31 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.202]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0248.002; Fri, 6 Nov 2015 09:03:31 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: Modified text based on decision to mandate RTP/RTCP mux for bundled RTP-based media
Thread-Index: AdEYaaXNkOdFLUA7RSKgA5FSf9ed4g==
Date: Fri, 06 Nov 2015 08:03:30 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37BDF969@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37BDF969ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyM+Jvre7lOJswg75uDYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoErY0vPfJaC/hOMFdsXPWNvYFy4mbGLkZNDQsBE4uj9FnYIW0zi wr31bF2MXBxCAkcYJV5+msMKkhASWMwocbxXtIuRg4NNwEKi+582SFhEQF3i694eZhBbWCBN 4tf0eUwgJSIC2RKLFqZClOhJHN9zH2wVi4CKxLY/e8FsXgFfiWMflrOA2IxAa7+fWsMEYjML iEvcejKfCeIcAYkle84zQ9iiEi8f/2OFsJUk1h7ezgJRny+x691jNoiZghInZz5hmcAoNAvJ qFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGEWLU4uLc9ONjPVSizKTi4vz 8/TyUks2MQJj4uCW37o7GFe/djzEKMDBqMTDa7DcOkyINbGsuDL3EKMEB7OSCK8cs02YEG9K YmVValF+fFFpTmrxIUZpDhYlcd4WpgehQgLpiSWp2ampBalFMFkmDk6pBsZ1p9a9OFO0cr4x 9+NEmRyL7rfZEYaLTt50lGN/F3rAdP3diss6RcXM3ItWWN2MjLZ776YklS3PtUfSU7A2QmCd Hv+d7OOXZUxN7j/vNPoz5/SjZS3Va13f7X02ryfxTv26JPF0xfxfDW7nds8W+eGzYs+zp48r 9N333TB/Kjt3zsEX7x2UfqgqsRRnJBpqMRcVJwIALwg5TIUCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/4lJLPtu4fCrYLTqo_OANRtQJx-Y>
Subject: [MMUSIC] BUNDLE: Modified text based on decision to mandate RTP/RTCP mux for bundled RTP-based media
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 08:03:40 -0000
Hi, Based on the decision to mandate RTP/RTCP mux for BUNDLE, I've modified the associated section in BUNDLE. See below. (We may need some more text, based on where we go with the mux-only issue) For the Github fans, the text can also be found at: https://github.com/cdh4u/draft-sdp-bundle (Note that it is a private repo) Regards, Christer ------------------------- 10.3. RTP/RTCP Multiplexing 10.3.1. General Within a BUNDLE group, the offerer and answerer MUST enable RTP/RTCP multiplexing [RFC5761] for the RTP-based media associated with the BUNDLE group. When RTP/RTCP multiplexing is enabled, the same address:port combination will be used for sending all RTP packets and the RTCP packets associated with the BUNDLE group. Each endpoint will send the packets towards the BUNDLE address of the other endpoint. The same address:port combination MAY be used for receiving RTP packets and RTCP packets. 10.3.2. SDP Offer/Answer Procedures 10.3.2.1. General This section describes how an offerer and answerer use the SDP 'rtcp- mux' attribute [RFC5761] to negotiate usage of RTP/RTCP multiplexing for RTP-based media associated with a BUNDLE group. The procedures in this section only apply to RTP-based "m=" lines. 10.3.2.2. Generating the Initial SDP Offer When an offerer generates an initial offer, the offerer MUST associate an SDP 'rtcp-mux' attribute [RFC5761] with each bundled RTP-based "m=" line (including any bundle-only "m=" line) in the offer. NOTE: The offerer might also associate an SDP 'rtcp' attribute [RFC3605] with a bundled "m=" line, excluding a bundle-only "m=" line, in order to provide a fallback port for RTCP. However, the fallback port will only be used in case the answerer does not include the "m=" line in the BUNDLE group in the associated answer. In the initial offer, the IP address and port combination for RTCP MUST be unique in each bundled RTP-based "m=" line (excluding a 'bundle-only' "m=" line), similar to RTP. 10.3.2.3. Generating the SDP Answer When an answerer generates an answer, if the offerer indicated support of RTP/RTCP multiplexing [RFC5761] within a BUNDLE group in the associated offer, the answerer MUST accept usage of RTP/RTCP multiplexing within the BUNDLE group. If an SDP "rtcp-mux" attribute was not associated with a bundled "m=" line in the associated offer, the answerer MUST NOT included that "m=" line in the BUNDLE group. When the answerer accepts the usage of RTP/RTCP multiplexing within the BUNDLE group, it MUST associate an SDP 'rtcp-mux' attribute with each bundled RTP-based "m=" line in the answer. The answerer MUST NOT associate an SDP 'rtcp' attribute with any bundled "m=" line in the answer. The answerer will use the port value of the selected offerer BUNDLE address for sending RTP and RTCP packets associated with each RTP-based bundled "m=" line towards the offerer. If the usage of RTP/RTCP multiplexing within a BUNDLE group has been negotiated in a previous offer/answer transaction, the answerer MUST associate an SDP 'rtcp-mux' attribute with each bundled RTP-based "m=" line in the answer. 10.3.2.4. Offerer Processing of the SDP Answer When an offerer receives an answer, if the answerer has accepted the usage of RTP/RTCP multiplexing (see Section 10.3.2.3), the answerer follows the procedures for RTP/RTCP multiplexing defined in [RFC5761]. The offerer will use the port value associated with the answerer BUNDLE address for sending RTP and RTCP packets associated with each RTP-based bundled "m=" line towards the answerer. NOTE: If is considered a protocol error if the answerer has not accpeted the usage of RTP/RTCP multiplexing for RTP-based "m=" lines that the answerer included in the BUNDLE group. 10.3.2.5. Modifying the Session When an offerer generatees a subsequent offer, it MUST associate an SDP 'rtcp-mux' attribute with each RTP-based bundled "m=" line (including any bundled "m=" line that the offerer wants to add to the BUNDLE group), unless the offerer wants to disable or remove the "m=" line from the BUNDLE group.
- [MMUSIC] BUNDLE: Modified text based on decision … Christer Holmberg
- Re: [MMUSIC] BUNDLE: Modified text based on decis… Paul Kyzivat