IETF Logo Mail Archive

Re: [MMUSIC] What is an m-line?

Emil Ivov <emcho@jitsi.org> Thu, 16 May 2013 17:52 UTC

Return-Path: <emcho@sip-communicator.org>
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 C0D6C11E812A for <mmusic@ietfa.amsl.com>; Thu, 16 May 2013 10:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 TIX3ZtzXSB1k for <mmusic@ietfa.amsl.com>; Thu, 16 May 2013 10:52:26 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id E70FD11E8126 for <mmusic@ietf.org>; Thu, 16 May 2013 10:52:25 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id ey16so2980629wid.5 for <mmusic@ietf.org>; Thu, 16 May 2013 10:52:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=I2TlNnewVIz/YKzF5hmJu3soxR8S0k1GM7/oiK6FZ2E=; b=Iqmd3YwBugA8nhLbmMvOZLJPAXio44geq4xjnMUnWgHn6zRgGYEUxqsn2MpfA1DOKc AppLYpx1K3za+3SNRZAVXr530vNwgcotvPpUSe9y4n3JkwfyoRtUQgm/SqsQku+ncMxE NseWjv2gMhUJ271OJqOdPo1/8TnZtY7X7mdJ10jFahtQgn1oFA/vOKxBbhI6xf7TXtcU CHCcUXQ9w5825GWyun1ctNH1BLdR6hodPiMp3Ps6KOU9usEhih2TYs5bfLBFjEjSSbSi jhMGkJtSLJY/BzbIF7ZUTV7Hz1B/8rMBfF0cGHJOvvxdU1JBvVuEJSLjrbzw7BvSy685 xqgQ==
X-Received: by 10.180.189.68 with SMTP id gg4mr12290231wic.27.1368726744865; Thu, 16 May 2013 10:52:24 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [2607:f8b0:400c:c01::231]) by mx.google.com with ESMTPSA id dj7sm5324930wib.6.2013.05.16.10.52.23 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 10:52:24 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id ox1so3275862veb.36 for <mmusic@ietf.org>; Thu, 16 May 2013 10:52:22 -0700 (PDT)
X-Received: by 10.58.50.198 with SMTP id e6mr28496038veo.30.1368726742522; Thu, 16 May 2013 10:52:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.167.197 with HTTP; Thu, 16 May 2013 10:52:01 -0700 (PDT)
In-Reply-To: <CABkgnnUiWZnbC1vbs2qAUOB-HEr-CQYynS4wrzwpMFA5PB=Q3Q@mail.gmail.com>
References: <CABkgnnWPWMLEecfqksGJrWrqvsu44gts48igUiLyiVV0iPhwQQ@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E782F@xmb-aln-x02.cisco.com> <5193B1DB.2070308@alum.mit.edu> <1922EE35-127D-459C-AC7A-D2E98A0CDBA0@csperkins.org> <BLU169-W119163BAE68316B331EE12193A20@phx.gbl> <5193EA5C.7050905@alvestrand.no> <BLU169-W743682718AEA906C0F3C2A93A20@phx.gbl> <CABkgnnULK4Af+G4sg8Nnsa27v8wtB3fF3Ei2=x9Q7vDf+5Ak9Q@mail.gmail.com> <51950CED.6020305@jitsi.org> <CABkgnnUiWZnbC1vbs2qAUOB-HEr-CQYynS4wrzwpMFA5PB=Q3Q@mail.gmail.com>
From: Emil Ivov <emcho@jitsi.org>
Date: Thu, 16 May 2013 20:52:01 +0300
Message-ID: <CAPvvaaL_Gw4XWOO=VGThp6kyq-NJpB+0EFjXyWHNamfOtDfHrg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQkmOnI8M5j37V4Vr+2KWjHaum/nTEFx8xLL69H9mA7p3J6e4BCw4K+ECZv8SKVfm65Pt1oz
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] What is an m-line?
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: Thu, 16 May 2013 17:52:26 -0000

On Thu, May 16, 2013 at 8:12 PM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> On 16 May 2013 09:44, Emil Ivov <emcho@jitsi.org> wrote:
>>> I think that is a perfectly pragmatic conclusion to reach.  However,
>>> it still leaves the issue open.  I'd like to at least reach a point
>>> where there is agreement on just one model for interpreting the SDP
>>> that is output and input to the WebRTC API.
>>
>> If we agree that basing design decisions on legacy devices and their
>> view of what an m= line is (or rather isn't). Then is there any reason
>> not to accept the RTP-centric description of an m= line that Colin
>> described?
>
> Yes, it might be premature. I'm not sure that we've explored all of
> the implications of that statement.  For instance, no one has even
> discussed call transfer scenarios yet. We haven't explored the
> consequences of SSRC collision.

Could you please be more specific about the sorts of problems you
expect and how they are caused by adhering to the basics of RTP?

> We have to agree that the model we use actually fits the sorts of
> things that need to fit.

I always thought people agreed on that when they chose RTP for these
things, but again, I'd be very interested to hear about the problems
you expect.

Emil

--
https://jitsi.org

v2.23.0 | Report a Bug | By Email