Re: [MMUSIC] Inconsistent text in BUNDLE and mux-exclusive regarding IDENTICAL/TRANSPORT SDP attributes

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 07 April 2017 12:29 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C86A9124281 for <mmusic@ietfa.amsl.com>; Fri, 7 Apr 2017 05:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0G3hBL75gqbt for <mmusic@ietfa.amsl.com>; Fri, 7 Apr 2017 05:29:16 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FC5E129438 for <mmusic@ietf.org>; Fri, 7 Apr 2017 05:29:16 -0700 (PDT)
X-AuditID: c1b4fb25-c27a798000006af2-e4-58e7861a3549
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by (Symantec Mail Security) with SMTP id 49.97.27378.A1687E85; Fri, 7 Apr 2017 14:29:14 +0200 (CEST)
Received: from ESESSMB102.ericsson.se ([169.254.2.218]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0339.000; Fri, 7 Apr 2017 14:29:13 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Inconsistent text in BUNDLE and mux-exclusive regarding IDENTICAL/TRANSPORT SDP attributes
Thread-Index: AQHSr5qPeaTVwEGRC06ccSzz9agQmg==
Date: Fri, 7 Apr 2017 12:29:44 +0000
Message-ID: <D50D611C.1AB4B%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.2.170228
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_D50D611C1AB4Bchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHLMWRmVeSWpSXmKPExsUyM2K7qK5U2/MIg0erJCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujPVP7rAWfAyq+DT9PFsD4z2PLkZODgkBE4kls86xdzFycQgJ rGeUuLrtNjOEs5hR4tPnA0AOBwebgIVE9z9tkAYRAXWJr3t7mEFsYYEiiVXzO1gg4sUStz/O g7L1JBbcXA9WwyKgIvHg+RomEJtXwFrixO3rjCA2o4CYxPdTEHFmAXGJW0/mM0EcJCCxZM95 ZghbVOLl43+sILYo0Mx9/76yQcQVJa5OXw7VmyBx/udKRoj5ghInZz5hmcAoNAvJ2FlIymYh KYOIG0i8PzefGcLWlli28DWUrS+x8ctZRgjbWuJ101cWZDULGDlWMYoWpxYn5aYbGeulFmUm Fxfn5+nlpZZsYgTGysEtv1V3MF5+43iIUYCDUYmHN+HHkwgh1sSy4srcQ4wSHMxKIrzq74FC vCmJlVWpRfnxRaU5qcWHGKU5WJTEeR33XYgQEkhPLEnNTk0tSC2CyTJxcEo1MLJdCmGzf7Ix bx+jgk+A/Zfpd6OLlR+80jO9zd95rYw/y06clyfp68753TPnn7Z30vG361Vl/CoUmr1k57y1 V0N3hOW+SFN0nM5bECNYpSof8GRKn+XHI9xL0xjWcMkvsolWkWUpSZuQvemjtVhxwu55Ux/x Gx++lyI6qXCym3sZ/6TNiktklViKMxINtZiLihMBNLjE5ZECAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/m5rdyKHozSsPGTzGsODDP2m5ox8>
Subject: Re: [MMUSIC] Inconsistent text in BUNDLE and mux-exclusive regarding IDENTICAL/TRANSPORT SDP attributes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 07 Apr 2017 12:29:19 -0000

Hi,

I’ve now updated the BUNDLE text to be consistent and correct when it comes to IDENTICAL/TRANSPORT SDP attributes.

In addition, I have written text regarding the usage of media specific attributes (e.g., rtcp-mux) with m- lines associated with different media.

https://github.com/cdh4u/draft-sdp-bundle/pull/33

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on behalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Date: Monday 3 April 2017 at 21:29
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Subject: [MMUSIC] Inconsistent text in BUNDLE and mux-exclusive regarding IDENTICAL/TRANSPORT SDP attributes

Hi,

When looking for the changes needed regarding including media specific attributes in bundled m- lines, I realized that there is inconsistent text between BUNDLE and draft-mux-exclusive:

Section 3 of draft-mux-exclusive says:

   The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the 'rtcp-
   mux-only' attribute is 'IDENTICAL', which means that the attribute,
   if used within a BUNDLE group
   [I-D.ietf-mmusic-sdp-bundle-negotiation], must be associated with all
   multiplexed RTP-based media descriptions within the BUNDLE group.

Section 8.1 of BUNDLE says:


   When an offerer associates SDP attributes with a bundled "m=" line

   associated with a shared address, IDENTICAL and TRANSPORT mux

   category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are

   associated with the "m=" line only if the "m=" line is also

   associated with the offerer BUNDLE-tag.  Otherwise the offerer MUST

   NOT associate such SDP attributes with the "m=" line.

Section 10.3.1.1 of BUNDLE says:


   When an offerer generates an initial offer, the offerer MUST

   associate an SDP 'rtcp-mux' attribute [RFC5761] with each bundled

   RTP-based "m=" line in the offer, including a bundle-only "m=" line.

   In addition, the offerer MUST associate an SDP 'rtcp-mux-only'

   attribute [I-D.ietf-mmusic-mux-exclusive] with each RTP-based bundle-

   only "m=" line, and MAY associated an SDP 'rtcp-mux-only' attribute

   with other bundled RTP-based "m=" lines.

The text in section 8.1 describes the correct behaviour.

Regards,

Christer