[MMUSIC] Questions on draft-ietf-mmusic-sctp-sdp-05

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 27 January 2014 11:36 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 2BAD11A01E8 for <mmusic@ietfa.amsl.com>; Mon, 27 Jan 2014 03:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.039
X-Spam-Level:
X-Spam-Status: No, score=-0.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, SPF_PASS=-0.001] autolearn=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 vZr3q40WuLbS for <mmusic@ietfa.amsl.com>; Mon, 27 Jan 2014 03:36:19 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 0D5791A0130 for <mmusic@ietf.org>; Mon, 27 Jan 2014 03:36:18 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-53-52e644afd412
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 75.74.04853.FA446E25; Mon, 27 Jan 2014 12:36:16 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0387.000; Mon, 27 Jan 2014 12:36:15 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: Questions on draft-ietf-mmusic-sctp-sdp-05
Thread-Index: Ac8bUQl73YOfrjw4RXqWisjZiYMaaA==
Date: Mon, 27 Jan 2014 11:36:15 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D13BB05@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.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D13BB05ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyM+Jvje4Gl2dBBktOcFtMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGQeWdbEU/DKtuP5kO2MD4029LkZODgkBE4lpM66xQNhiEhfu rWfrYuTiEBI4wSixactuZpCEkMBiRon/34GKODjYBCwkuv9pg4RFBGQk9m7aDFYiDDSnd0cz G0TcUmLKvg/MIOUiAnoSv0/HgIRZBFQlfly8wgRi8wr4Sqx5+gusnBFo7fdTa8DizALiEree zGeCOEdAYsme88wQtqjEy8f/WCFsJYkfGy6xQNTnS+xfu5MFYqagxMmZT1gmMArNQjJqFpKy WUjKIOI6Egt2f2KDsLUlli18zQxjnznwmAlZfAEj+ypGyeLU4uLcdCMDvdz03BK91KLM5OLi /Dy94tRNjMC4OLjlt9EOxpN77A8xSnOwKInzXmetCRISSE8sSc1OTS1ILYovKs1JLT7EyMTB KdXAuEdT3e3c/0k/jdSW+cafC/5Yt7nyVWiJipVym9BOttV3Hyre5Eg+Ue/3w+fj2tVmx/uO 1nzYU9nwc81VrWsc9bzbNkYWBlwr2b1tl6yn1WQXk9zLTfEu+W8WqRQvq+rdeMOyxEnx8cRD 30VW8sbvX7Bx1rLM6IZDn9vO/ObUPbeG0/S4zU9hOyWW4oxEQy3mouJEAIGp7MlZAgAA
Subject: [MMUSIC] Questions on draft-ietf-mmusic-sctp-sdp-05
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: <http://www.ietf.org/mail-archive/web/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: Mon, 27 Jan 2014 11:36:21 -0000

Hi,

Section 5.1 of draft-ietf-mmusic-sctp-sdp-05 describes how an offered SCTP association can be rejected, by in the Answer setting the port value in the associated SDP sctpmap attribute to zero.

Q1:         When an SCTP association is rejected, shall the associated port value in the m- line fmt list also be set to zero? The text only talks about the sctpmap attribute.

The draft does not talk about subsequent offers.

Q2:         Do I need to include all sctpmap attributes in subsequent offers, even if some are associated with previously rejected STCP associations, in order to maintain the order?

Q3:         Can I, in a subsequent offer, remove an SCTP association by setting the associated port value to zero? If so, do I set the port value to zero in the associated sctpmap attribute, and/or the m- line fmt list?

The draft only talks about having a single media-subtype per SCTP association.

Q4:         Is it possible to define multiple media-subtypes per SCTP association?

                Example:

                m=application 54111 DTLS/SCTP 5000
              c=IN IP4 79.97.215.79
              a=sctpmap:5000 webrtc-datachannel 16
              a=sctpmap:5000 bfcp 2
              a=sctpmap:5000 t38 1

                (Each media-subtype could use different SCTP streams within the SCTP association)


Thanks!

Regards,

Christer