Re: [clue] comment on draft-lennox-clue-rtp-usage-0

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 15 February 2012 07:36 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A61A21F8595 for <clue@ietfa.amsl.com>; Tue, 14 Feb 2012 23:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.43
X-Spam-Level:
X-Spam-Status: No, score=-9.43 tagged_above=-999 required=5 tests=[AWL=1.168, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfgpNlvUUKqC for <clue@ietfa.amsl.com>; Tue, 14 Feb 2012 23:36:56 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 381E221F8594 for <clue@ietf.org>; Tue, 14 Feb 2012 23:36:50 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-4e-4f3b609159d1
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 00.CA.01970.1906B3F4; Wed, 15 Feb 2012 08:36:49 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.175]) by esessmw0247.eemea.ericsson.se ([153.88.115.93]) with mapi; Wed, 15 Feb 2012 08:36:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>, Roni Even <ron.even.tlv@gmail.com>, "clue@ietf.org" <clue@ietf.org>
Date: Wed, 15 Feb 2012 08:36:47 +0100
Thread-Topic: [clue] comment on draft-lennox-clue-rtp-usage-0
Thread-Index: AczqQZbet2tZzr5TTIGnqnddD7r6fQAJqSIQAFMAVzA=
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3D87DE16@ESESSCMS0356.eemea.ericsson.se>
References: <4f38f239.c77d0e0a.7414.fffff1b2@mx.google.com> <C3759687E4991243A1A0BD44EAC823034DD493CBC2@BE235.mail.lan>
In-Reply-To: <C3759687E4991243A1A0BD44EAC823034DD493CBC2@BE235.mail.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C3D87DE16ESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [clue] comment on draft-lennox-clue-rtp-usage-0
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2012 07:36:58 -0000

Hi,

Just a reminder, that BUNDLE is only about multiple m- lines sharing the same port number. It does not prevent you from, within a single m- line, e.g. having multiple SSRC-multiplexed streams.

One of the ideas in RTCWEB has been to have one audio m- line, and one video m- line, sharing the same port number (using BUNDLE), but those m- lines can then contain multiple streams.

Regards,

Christer

________________________________
From: clue-bounces@ietf.org [mailto:clue-bounces@ietf.org] On Behalf Of Jonathan Lennox
Sent: 13. helmikuuta 2012 18:08
To: Roni Even; clue@ietf.org
Subject: Re: [clue] comment on draft-lennox-clue-rtp-usage-0

Hi, Roni -

I don't think my draft discusses "codec information" at all, at least as I understand the term, so I'm not sure quite what you mean by it.

As for BUNDLE, I think it'll emerge that it doesn't work or scale well for complicated cases (e.g., cases where you have many potential captures, or where a source moves between captures, or where a single source could be sent for more than one capture simultaneously).

Also, to avoid confusion, when you say "stream," what do you mean?  The term (unfortunately) means very different things in SDP and in RTP - in the former case, it's the thing identified by an m= line (and thus, pre-BUNDLE, a transport flow), whereas in the latter case, it's the thing identified by an SSRC.  So I'm not quite sure what your draft, and this e-mail, is discussing.

-
Jonathan Lennox
jonathan@vidyo.com

From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Monday, February 13, 2012 6:21 AM
To: clue@ietf.org
Subject: [clue] comment on draft-lennox-clue-rtp-usage-0

Hi,
My view is that there are two separate problems that the draft discusses:


1.       The co-relation between the media capture and the codec information in the offer answer

2.       Multiplexing multiple media streams.

I think that the second problem is addressed in http://tools.ietf.org/html/draft-holmberg-mmusic-sdp-bundle-negotiation-00
As for the mapping I have a proposal to use a capture set group in the SDP for the ampping
Roni