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

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

Return-Path: <emil@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 A6D5621F90DF for <mmusic@ietfa.amsl.com>; Thu, 16 May 2013 09:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 0dVwxCb7XpGp for <mmusic@ietfa.amsl.com>; Thu, 16 May 2013 09:44:43 -0700 (PDT)
Received: from mail-bk0-x236.google.com (mail-bk0-x236.google.com [IPv6:2a00:1450:4008:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 957BB21F85C3 for <mmusic@ietf.org>; Thu, 16 May 2013 09:44:42 -0700 (PDT)
Received: by mail-bk0-f54.google.com with SMTP id it19so1222783bkc.13 for <mmusic@ietf.org>; Thu, 16 May 2013 09:44:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=ceNns6kki52dK7BKQEo+gIFk5En67o63DrDb5WIdPOA=; b=gtf4Hh8xqKA1mf2hwlSPZC5wEVvSkcfnkf0q5NwHpcYInWPdK2L7RhLbfdMZ6fWzYU f2xr0hXC4OGqCu42vNEP1Jcs88P7JvpNblj75RjdT2rZiHF8b8mPhOKeTU21m/JAlaqb PSsFv05lpekiXf8Ss3+xvwUDyqL4YgUd3TSYtuAGQKf1dUltcRxYtwWJcodc8CqUu5Et UcSb2iS+pByXQBhnIcduGHCAYuSEd/wLR2paiNjEcBGkjhx1c09DnnrSFbiJ42zylRI9 psvNorriIlI9lw9TWLd5+SnncokIFY2qAIxt8M7qtGhWolyrpwqgJ0msI25QkVJ05/1b /KZg==
X-Received: by 10.204.245.201 with SMTP id lv9mr13718489bkb.102.1368722670303; Thu, 16 May 2013 09:44:30 -0700 (PDT)
Received: from camionet.local ([79.100.215.70]) by mx.google.com with ESMTPSA id tc9sm2264557bkb.18.2013.05.16.09.44.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 09:44:29 -0700 (PDT)
Message-ID: <51950CED.6020305@jitsi.org>
Date: Thu, 16 May 2013 19:44:29 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@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>
In-Reply-To: <CABkgnnULK4Af+G4sg8Nnsa27v8wtB3fF3Ei2=x9Q7vDf+5Ak9Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQmR78rrk8p1iW4haxKjHjr0e2Ki2p6VgL5VmbLH0O6Zq7guekc1CkRgnB7NH8zmKZ8piik6
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 16:44:43 -0000

On 16.05.13, 19:35, Martin Thomson wrote:
> On 15 May 2013 15:43, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
>> Harald finally said:
>>
>> "I see the idea that *any application* should produce SDP that's useful in
>> such a scenario as an illusion, and pursuing that illusion is just going to
>> hurt us."
>>
>> [BA] Agree. s/illusion/delusion/ :)
> 
> 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?

Emil


-- 
https://jitsi.org