Re: [MMUSIC] [rtcweb] About unified Plan and multiple m lines

Suhas Nandakumar <suhasietf@gmail.com> Wed, 24 July 2013 18:14 UTC

Return-Path: <suhasietf@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 145FD11E8110 for <mmusic@ietfa.amsl.com>; Wed, 24 Jul 2013 11:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.733
X-Spam-Level:
X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666]
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 mGcdeqnSpiC4 for <mmusic@ietfa.amsl.com>; Wed, 24 Jul 2013 11:14:38 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id A6D0C11E8125 for <mmusic@ietf.org>; Wed, 24 Jul 2013 11:14:37 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id e11so741933wgh.30 for <mmusic@ietf.org>; Wed, 24 Jul 2013 11:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WhkWZWLOd3/ktWj51dF/oQspYGxslQ/FjSfsYtW8GNA=; b=EuMjyTZvtVz8MvoP0EYl4OEjtflpVDUjZtyL1uXHj1bh95pCCyr2RPa5R7bho5Ekse Z3LCASNALMHR+SG8qW86XhhzK608b65k6w2zV4t1/0BeNBXdvQK6A7XjWme5qZ0cP7e8 5/wwdStIcjoIkmFKCnuYLfFkqwIpfyp4dvwJ5XwZnw9FNJDAwUF7laeHvgc8pI4FbF2C UCB4lhW4VisuJyYwEBIeB4UEas8Y4kMCV/D37cP4UUb/Pw2xKErb4l7JjGFXQWk6k/6p dPX2hswuzk+6rRePQCsqL2q5bWjZfBsnWcoBCQ4cpLlnfMFu2jLRrIMCI2q5PqfdvSnu ZkEw==
MIME-Version: 1.0
X-Received: by 10.194.242.69 with SMTP id wo5mr28215695wjc.30.1374689676776; Wed, 24 Jul 2013 11:14:36 -0700 (PDT)
Received: by 10.194.9.9 with HTTP; Wed, 24 Jul 2013 11:14:36 -0700 (PDT)
In-Reply-To: <51EFFC49.80305@jitsi.org>
References: <CALiegfnLGFz8AcP2YCRq_dzYbxV9NKvSbHvs+MYCTr6RBiDkEg@mail.gmail.com> <CABcZeBM0FuFPhD-swYy6PQgWMjcPH+rZR6Wd3fBH6TRyDFJ8YA@mail.gmail.com> <51EFFC49.80305@jitsi.org>
Date: Wed, 24 Jul 2013 11:14:36 -0700
Message-ID: <CAMRcRGS1kPQfK+VsgmU3OmX2piMuxK2T5J66a6CpebEJH581RA@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: multipart/alternative; boundary="089e0122f0fedc706604e245e18a"
Cc: Iñaki Baz Castillo <ibc@aliax.net>, MMUSIC IETF WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] [rtcweb] About unified Plan and multiple m lines
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: Wed, 24 Jul 2013 18:14:39 -0000

Offerer has all sendrecv , the answerer has one sendrecv (since he can send
only one audio track) and rest recvonly

so the answerer is ok to receive all the audio tracks sent by the offerer,
and he is sending only one from his side (marked as sendrecv)


On Wed, Jul 24, 2013 at 9:09 AM, Emil Ivov <emcho@jitsi.org> wrote:

> (redirecting to mmusic)
>
>
> On 24.07.13, 16:29, Eric Rescorla wrote:
>
>>
>>
>>
>> On Wed, Jul 24, 2013 at 7:08 AM, Iñaki Baz Castillo <ibc@aliax.net
>> <mailto:ibc@aliax.net>> wrote:
>>
>>     Hi, let's suppose WebRTC 1.0 borns with "Unified Plan" built-in, and
>>     my browser receives a session invitation from a conference server, and
>>     there are 8 audio participants in the conference.
>>
>>     So the SDP I receive has 8 "m=audio" lines, maybe with different audio
>>     codecs in each line. And following SDP O/A rules my browser will
>>     generate SDP answer that will also contain 8 "m=audio" lines.
>>
>>     Now, where it is supposed my browser will send my single audio track
>>     to the conference server? What does it mean that I receive 8 "m=audio"
>>     lines while I'm just able to send a single audio track? which m=audio
>>     line should I use for sending RTP?
>>
>>
>> One of them will be a=sendrecv. The others will be a=sendonly.
>> The sendrecv line is the one you use to send media.
>>
>
> I have a few questions here but before that, could you please clarify the
> following:
>
> Are you saying that the above is going to be the case on the offer that
> the callee receives? In other words, the caller "knew" that the callee
> intended to only send one stream so it preset all directions accordingly?
>
> Emil
>
>
>
> --
> https://jitsi.org
>
> ______________________________**_________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/**listinfo/mmusic<https://www.ietf.org/mailman/listinfo/mmusic>
>