IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 02 November 2012 14:53 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 E648021F8A28 for <mmusic@ietfa.amsl.com>; Fri, 2 Nov 2012 07:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level:
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 16F-mLjqAc2X for <mmusic@ietfa.amsl.com>; Fri, 2 Nov 2012 07:53:32 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 369BF21F8614 for <mmusic@ietf.org>; Fri, 2 Nov 2012 07:53:32 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta15.westchester.pa.mail.comcast.net with comcast id JbKp1k0030Fqzac5Feu6w4; Fri, 02 Nov 2012 14:54:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta08.westchester.pa.mail.comcast.net with comcast id JetK1k00K3ZTu2S3UetKzb; Fri, 02 Nov 2012 14:53:19 +0000
Message-ID: <5093DE68.80508@alum.mit.edu>
Date: Fri, 02 Nov 2012 10:53:28 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: mmusic@ietf.org
References: <5093A2C9.9040001@alvestrand.no>
In-Reply-To: <5093A2C9.9040001@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 02 Nov 2012 14:53:33 -0000

On 11/2/12 6:39 AM, Harald Alvestrand wrote:
> As currently specified, the DTLS/SCTP protocol is carefully specified in
> such a way that it can ride on the same 5-tuple as an SRTP session. I'd
> like to keep that property when we SDP-negotiate it.

It is? How? Where is that specified?

	Thanks,
	Paul

> The proposed syntax for DTLS/SCTP seems to be
>
> m=<something, likely application> <port number> DTLS/SCTP <fmt data,
> mostly meaningless>
>
> I see two ways to define this as a multiplex:
>
> - Give the same port number as another m= line in the same SDP session
> - Give a meaningless port number, and use the a=group:BUNDLE (of
> whatever flavor) to give which port number it's actually multiplexed
> together with.
>
> The best way to do this may be obvious after the BUNDLE discussion, but
> in case there are other considerations .... are there thoughts?
>
>                 Harald
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

v2.23.0 | Report a Bug | By Email