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

Harald Alvestrand <harald@alvestrand.no> Mon, 03 December 2012 08:10 UTC

Return-Path: <harald@alvestrand.no>
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 67FC421F887C for <mmusic@ietfa.amsl.com>; Mon, 3 Dec 2012 00:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 BG8R144MwJPI for <mmusic@ietfa.amsl.com>; Mon, 3 Dec 2012 00:10:44 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 494E621F8876 for <mmusic@ietf.org>; Mon, 3 Dec 2012 00:10:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id B039039E0FD; Mon, 3 Dec 2012 09:10:42 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHDh0NXr+sUN; Mon, 3 Dec 2012 09:10:42 +0100 (CET)
Received: from [192.168.1.107] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 4C72D39E04C; Mon, 3 Dec 2012 09:10:41 +0100 (CET)
Message-ID: <50BC5E80.4090006@alvestrand.no>
Date: Mon, 03 Dec 2012 09:10:40 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.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>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B04CC3A@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
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 08:10:45 -0000

On 12/03/2012 09:00 AM, Christer Holmberg wrote:
> Hi,
>
> I guess it would be nice to hear from the browser/endpoint people whether they see a need for covering non-RTP in BUNDLE.
>
> If NOT, it would mean a minimum of two 5-tuples, instead of one (one for the bundled RTP media, and one for the data channel).

Speaking with my browser implementor hat on, I want to avoid adding an 
extra 5-tuple for data channels.

Our stats on improvement from the introduction of rtcp-mux were pretty 
compelling that the issue is real.

>
> Regards,
>
> Christer
>
>
>
>
> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald Alvestrand
> Sent: 3. joulukuuta 2012 9:54
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] SCTP question: Where does it multiplex?
>
> On 12/01/2012 07:09 PM, Paul Kyzivat wrote:
>> I must say that I am getting confused about what is being multiplexed
>> here. We must be very careful to be precise.
>>
>> SCTP defines an *association*, which in simple cases is bound to a
>> 5-tuple. (For now lets not talk about the cases where each end can
>> have more than one address.)
>>
>> SCTP multiplexes multiple one-way *streams* over an association.
>> (These are not RTP streams.)
>>
>> RTCWEB binds pairs of sctp-streams together into *channels*.
> I'm not talking about any of these levels. I'm talking about the reuse of the RTP session's 5-tuple for the DTLS/SRTP 5-tuple, as described in RFC 5764 section 5.1.2.
>
> I said the same thing earlier on this thread (Nov 5), when you first responded (thanks for being the first responder!)
>
> You do make the point that the term "multiplex" is so over-used, it should probably be abandoned altogether - but that section talks about (de)multiplexing, so changing terminology is probably too late for that particular usage.
>
>                 Harald
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic