IETF Logo Mail Archive

Re: [MMUSIC] SCTP question: Where does it multiplex?

<Markus.Isomaki@nokia.com> Mon, 03 December 2012 20:23 UTC

Return-Path: <Markus.Isomaki@nokia.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 ED0AC21F87E7 for <mmusic@ietfa.amsl.com>; Mon, 3 Dec 2012 12:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YibrzJjIuWxy for <mmusic@ietfa.amsl.com>; Mon, 3 Dec 2012 12:23:40 -0800 (PST)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2F52921F86EE for <mmusic@ietf.org>; Mon, 3 Dec 2012 12:23:39 -0800 (PST)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qB3KNXad015832; Mon, 3 Dec 2012 22:23:35 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.59]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 3 Dec 2012 22:23:32 +0200
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.131]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.02.0318.003; Mon, 3 Dec 2012 20:23:32 +0000
From: Markus.Isomaki@nokia.com
To: pkyzivat@alum.mit.edu, mmusic@ietf.org
Thread-Topic: [MMUSIC] SCTP question: Where does it multiplex?
Thread-Index: AQHNz7N6WgV/cieAmkiYZjuifDh2VZgEB+uAgAA2wgCAAniGgIAAAgkAgAACugCAAAro0IAAKD+AgACW5ACAAAGfgA==
Date: Mon, 03 Dec 2012 20:23:32 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7623202ED@008-AM1MPN1-042.mgdnok.nokia.com>
References: <5093A2C9.9040001@alvestrand.no> <50B9E3ED.6010604@ericsson.com> <50BA19F9.4040701@alvestrand.no> <50BA47E8.4010909@alum.mit.edu> <50BC5A81.6050503@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B04CC3A@ESESSMB209.ericsson.se> <50BC5E80.4090006@alvestrand.no> <E44893DD4E290745BB608EB23FDDB76231FA24@008-AM1MPN1-042.mgdnok.nokia.com> <50BC8969.6010101@alvestrand.no> <50BD07FC.30809@alum.mit.edu>
In-Reply-To: <50BD07FC.30809@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.163.167.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Dec 2012 20:23:32.0842 (UTC) FILETIME=[10A7F4A0:01CDD194]
X-Nokia-AV: Clean
Subject: Re: [MMUSIC] SCTP question: Where does it multiplex?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Dec 2012 20:23:41 -0000

Hi,

Paul Kyzivat wrote:
>On 12/3/12 6:13 AM, Harald Alvestrand wrote:
>> On 12/03/2012 10:02 AM, Markus.Isomaki@nokia.com wrote:
>>> Hi,
>>>I don't think our QoS (or API) draft yet
>>> clearly explains how DSCP's are learned and set, or whether that is
>>> even going to be a realistic solution.
>>
>> That is indeed the only reason I can think of to specify multiple
>> m-lines for DTLS/SCTP (and we don't need to bundle them together).
>>
>> At the moment, the MMUSIC API doesn't define a way to control which
>> m-line a DTLS assocation gets mapped onto.
>
>MMUSIC *API*???
>
>Do you mean the SDP signaling for this? (draft-ietf-mmusic-sctp-sdp-02)
>
>It specifies a new m-line format for this.
>

Sorry about starting the confusion. I thought this was on rtcweb mailing list and with API I was in my reply actually referring to the QoS/prioritization related APIs in W3C related to WebRTC. Don't know which API Harald is referring to, though :-)

Markus

v2.14.0 | Report a Bug | By Email