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

"Roni Even" <ron.even.tlv@gmail.com> Wed, 15 February 2012 10:06 UTC

Return-Path: <ron.even.tlv@gmail.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 4D61821F87D0 for <clue@ietfa.amsl.com>; Wed, 15 Feb 2012 02:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 lnhjDFSen2uR for <clue@ietfa.amsl.com>; Wed, 15 Feb 2012 02:06:37 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id B06D421F87A1 for <clue@ietf.org>; Wed, 15 Feb 2012 02:06:36 -0800 (PST)
Received: by qan41 with SMTP id 41so826022qan.10 for <clue@ietf.org>; Wed, 15 Feb 2012 02:06:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=pvouXsHSxZg7fulP5Z0So76Oy9NLFXKOZnmb65cFSB8=; b=jgRR754IK5afFWyfBuBGlk94/zgGS6FLip2NzDXwf8IrWcgmnWqkaEVsBFw62It4BX jPkqhFha95zmP0uV4ETohdYOm8kIs+gp57kJe6dbLSsod0S3dW0TOwJamgCepyQEm3lz TPoJSB9WszKaIR0RGn1P151nP9uEjaRT+lOTk=
Received: by 10.229.136.16 with SMTP id p16mr15068174qct.24.1329300396104; Wed, 15 Feb 2012 02:06:36 -0800 (PST)
Received: from windows8d787f9 (75-147-4-157-NewEngland.hfc.comcastbusiness.net. [75.147.4.157]) by mx.google.com with ESMTPS id dk2sm9621261qab.12.2012.02.15.02.06.35 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Feb 2012 02:06:35 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, 'Jonathan Lennox' <jonathan@vidyo.com>, clue@ietf.org
References: <4f38f239.c77d0e0a.7414.fffff1b2@mx.google.com> <C3759687E4991243A1A0BD44EAC823034DD493CBC2@BE235.mail.lan> <7F2072F1E0DE894DA4B517B93C6A05852C3D87DE16@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C3D87DE16@ESESSCMS0356.eemea.ericsson.se>
Date: Wed, 15 Feb 2012 12:06:19 +0200
Message-ID: <4f3b83ab.02bfe00a.55f8.1234@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A3_01CCEBDA.3AE3D770"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AczqQZbet2tZzr5TTIGnqnddD7r6fQAJqSIQAFMAVzAABSmL0A==
Content-Language: en-us
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 10:06:41 -0000

Hi Christer,

I assume BUNDLE allows you also to provide the multiplexing information also
for multiple m-lines of the same media type, one example if they represent
different contend using the SDP content attribute to describe each stream.
It provides you one more degree a freedom when describing the media streams

 

Roni

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
Sent: Wednesday, February 15, 2012 9:37 AM
To: Jonathan Lennox; Roni Even; clue@ietf.org
Subject: RE: [clue] comment on draft-lennox-clue-rtp-usage-0

 

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