IETF Logo Mail Archive

Re: [rtcweb] A problem with both A and B

Emil Ivov <emcho@jitsi.org> Thu, 23 May 2013 11:09 UTC

Return-Path: <emcho@sip-communicator.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE43D21F96E5 for <rtcweb@ietfa.amsl.com>; Thu, 23 May 2013 04:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level:
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=0.6, 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 cGXdPgAWN1gW for <rtcweb@ietfa.amsl.com>; Thu, 23 May 2013 04:09:11 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id BCEF221F96D6 for <rtcweb@ietf.org>; Thu, 23 May 2013 04:09:11 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa10so2850075pad.19 for <rtcweb@ietf.org>; Thu, 23 May 2013 04:09:07 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=9Pah7iUN2BGfvpoYQHdM5u+cY/AkbWgeM6im/7yNoH0=; b=SxaZ8v60pUVkjLSbObMKLikp4byIKbmUR9x1aoYVQkZr7APg84g7N6FDRSz4/Qfn+O j+6a9WkVnvUpGuJ/UzSkKqH9rti7MOxz/rdkQ9BxYLkLiNDPze26tQvcaWyDrk352HaY 6Judtf8oWvxP/pm22kJUZDVUR6COPszW18kjKN04uaha4wmsNL6N56CMV5t/0wr3dJXS j/lW8hOWHoZZwPh+lRlO0JergDTxWWWAwQnSdF5YGDUETRBpV+xLpb8AKhwgQsm+zGva EOrdJQnxRNmBheSwg2W8FDGWk+Tv0Enloc648WvJAHg486XAivL04e8dO37cR7sDBr5j 9Jdg==
X-Received: by 10.68.103.194 with SMTP id fy2mr12225840pbb.158.1369307347014; Thu, 23 May 2013 04:09:07 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [2607:f8b0:400e:c01::229]) by mx.google.com with ESMTPSA id gh9sm11308740pbc.37.2013.05.23.04.09.06 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 04:09:06 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id xb12so2762960pbc.0 for <rtcweb@ietf.org>; Thu, 23 May 2013 04:09:06 -0700 (PDT)
X-Received: by 10.66.216.198 with SMTP id os6mr12539778pac.145.1369307346075; Thu, 23 May 2013 04:09:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.89.234 with HTTP; Thu, 23 May 2013 04:08:45 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C376B8B@ESESSMB209.ericsson.se>
References: <BLU403-EAS40305B2D015B786CC67EB9293AC0@phx.gbl> <CABkgnnXX3zoeKqjFxjsfMgaGGRM0JzymaeWfA13LEjUZ4tGF9Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C373EF0@ESESSMB209.ericsson.se> <519A4C9A.6020501@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1C374F13@ESESSMB209.ericsson.se> <519BD580.7080205@alum.mit.edu> <519C86EF.5080601@ericsson.com> <519CE696.1010606@alum.mit.edu> <1447FA0C20ED5147A1AA0EF02890A64B1C2D081A@ESESSMB209.ericsson.se> <CAMRcRGRkH5evUDZUFKObWD3CjY4wGSGVHQfbLhuV6pQzDc0SJw@mail.gmail.com> <CAMvTgccWBC+4GXJ_mjYj66Lmkhc_eTtr1G3nVC1u59ya1RLgtg@mail.gmail.com> <CAMRcRGSOd7sEx71toD5PJrOS-2RhD3CtCWHP6Br+yf0YS0g8Lg@mail.gmail.com> <519DE4DE.8070508@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C376A54@ESESSMB209.ericsson.se> <519DF308.6050203@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1C376B8B@ESESSMB209.ericsson.se>
From: Emil Ivov <emcho@jitsi.org>
Date: Thu, 23 May 2013 14:08:45 +0300
Message-ID: <CAPvvaaLfhBFJUZmWYw4J7L-T36-nDZYPH7N8+0VDfjF6gvHShA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQl/xZ1t5bqd23wEe022o1+SftUCbhUqgf/vYtuH/c4CL0tQgtp05j3z6WyD6+L8VNckbLgU
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] A problem with both A and B
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 11:09:16 -0000

On Thu, May 23, 2013 at 2:04 PM, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Hi,
>
>>>>> What if the new source produces pre-encoded stream that is not been
>>>>> negotiated within the current session ?
>>>>> example: video m=line with VP8 is setup and H.264 encoded camera is
>>>>> added as new source. This needs a O/A negotiation for the
>>>>> appropriate decoder context to be setup on the receiver side
>>>>
>>>> Obviously this does require a new O/A but I don't see how that case is related to adding and removing SSRCs which do not require O/A exchanges.
>>>
>>> It depends on whether you need to signal the SSRC to the remote endpoint for demux purpose.
>>
>> Exactly, and since I've been arguing that you don't ... :)
>
> Ok. So, maybe I've missed it, but how do you suggest the received media is:
>
> 1. associated with the m- line; and

Payload type. (And you either drop bundle when you run out of those

> 2. demuxed

Based on SSRC and application specific signalling. (Presuming that by
demuxed you mean identified)

Emil

v2.23.0 | Report a Bug | By Email