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

Martin Thomson <martin.thomson@gmail.com> Thu, 16 May 2013 18:01 UTC

Return-Path: <martin.thomson@gmail.com>
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 D3C6E21F8F0C for <mmusic@ietfa.amsl.com>; Thu, 16 May 2013 11:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 nYVKF15GrWgj for <mmusic@ietfa.amsl.com>; Thu, 16 May 2013 11:01:07 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA4721F8F09 for <mmusic@ietf.org>; Thu, 16 May 2013 11:01:07 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id f11so2846695wgh.15 for <mmusic@ietf.org>; Thu, 16 May 2013 11:01:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=O5SRWqVuBDcUWcZglU66mdLC08m/PFQrub7mnUhwsHc=; b=y9jH6ielQa37MXOIyx0yN3btCqbykVQLYurEbZjDhN+1JZoa4ZC1/XOWnKjPxa7Xp+ CoDWKEpvsB8YjjmhpQ4vyHYRSD3zs5MhkGC7YwJFy1i2/gxHk0NE4rFae/kz6AgUC7Xc LcQ8tZB8gxdnH+92wyCR/dKcu7lUpSENRkEQn6yeSEYcOXmWvFQOzeYcxkVN7o7C+cgT uP15JkFT/X9l+jv0YJ9yJtDIBYUCpCB+ZTKkmA6Dk8JfHh/BhX3XcybHV+xvDk+0u7zI ra8qEZfpMx2Aw99RdUoxjxp5EKMN40dPhEqh31LKQTCVg13QBV9k4OfqLBYH6ikYoBOp eKrQ==
MIME-Version: 1.0
X-Received: by 10.181.13.112 with SMTP id ex16mr8548941wid.28.1368727266243; Thu, 16 May 2013 11:01:06 -0700 (PDT)
Received: by 10.194.20.135 with HTTP; Thu, 16 May 2013 11:01:06 -0700 (PDT)
In-Reply-To: <CAPvvaaL_Gw4XWOO=VGThp6kyq-NJpB+0EFjXyWHNamfOtDfHrg@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> <CAPvvaaL_Gw4XWOO=VGThp6kyq-NJpB+0EFjXyWHNamfOtDfHrg@mail.gmail.com>
Date: Thu, 16 May 2013 11:01:06 -0700
Message-ID: <CABkgnnUb+sxidkGT4aoVB4aRGPxAaUm89DePQ0wPjyUsxdN2dg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: text/plain; charset=UTF-8
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 18:01:07 -0000

On 16 May 2013 10:52, Emil Ivov <emcho@jitsi.org> wrote:
> 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?

I'm not a strong proponent of these things, and I expect those
proponents to stand up and say something.  However, it is my
understanding that in a call transfer case, the arrival of a new SSRC
is treated as though the remote source has been switched out, not as
though a new participant has been added to the session.  The same has
to be true when a new SSRC is chosen in the case of a collision.

This is clearer when you talk about video.  Does the video from the
new SSRC go in the same window (/frame/<video> tag) as the existing
SSRC, or does it go in a new window?