Re: [rtcweb] Offer/answer for heterogeneous encode/decode

Harald Alvestrand <harald@alvestrand.no> Sun, 24 November 2013 16:39 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 065C01AE2FD for <rtcweb@ietfa.amsl.com>; Sun, 24 Nov 2013 08:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.825
X-Spam-Level:
X-Spam-Status: No, score=-6.825 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3vRoSRJzQOO for <rtcweb@ietfa.amsl.com>; Sun, 24 Nov 2013 08:39:41 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 71D0F1ADF46 for <rtcweb@ietf.org>; Sun, 24 Nov 2013 08:39:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id CF69A39E0E1 for <rtcweb@ietf.org>; Sun, 24 Nov 2013 17:39:03 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVYWu8673KJc for <rtcweb@ietf.org>; Sun, 24 Nov 2013 17:39:02 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id AEAB939E070 for <rtcweb@ietf.org>; Sun, 24 Nov 2013 17:39:02 +0100 (CET)
Message-ID: <52922BA1.6070805@alvestrand.no>
Date: Sun, 24 Nov 2013 17:38:57 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOJ7v-2NSo7_KgARkYMDO6bca7msARL83d9gN3570F6sHoCJ9g@mail.gmail.com> <59A91D84-3D29-47C4-8688-CB60844B15D3@cisco.com> <CABkgnnVu8p9nTaWhQYy8GdXkpa6_GGvZwbv8i=kistG5SnskXg@mail.gmail.com> <24B2A6DE-958C-445C-BE77-8BD1661DC33D@cisco.com>
In-Reply-To: <24B2A6DE-958C-445C-BE77-8BD1661DC33D@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] Offer/answer for heterogeneous encode/decode
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 24 Nov 2013 16:39:44 -0000

On 11/23/2013 01:20 AM, Paul Giralt (pgiralt) wrote:
> On Nov 22, 2013, at 7:06 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
>
>> On 22 November 2013 15:44, Paul Giralt (pgiralt) <pgiralt@cisco.com> wrote:
>>> While you’re right that it would work for this scenario, my point was really
>>> that Offer/Answer is not really asymmetric as implied earlier. Take for
>>> example the hypothetical case where you are only able to decode VP8 but only
>>> able to encode H.264. If I offer VP8 as my only codec (because it’s the only
>>> thing I’m able to decode therefore I never want anyone to send me anything
>>> other than VP8) I cannot send H.264 in the offer because that implies I’m
>>> able to decode it. The other side then wants to say it can only receive
>>> H.264 so it would have to send back an answer with only H.264. I guess
>>> there’s nothing really inherently stopping you from doing this because as
>>> far as I can tell, 3264 only says the answer has to be a subset of the offer
>>> for multicast streams, however how would the answering side know that the
>>> offering side is even capable to receiving H.264? Perhaps Offer/Answer can
>>> technically be asymmetric, but it doesn’t seem practical to use it this way
>>> because you cannot really indicate your send and receive capabilities
>>> independent of each other.
>> Judicious application of a=sendonly or a=recvonly avoids this issue.
>> If you want to send H.264, try a=sendonly on a line with H.264.  If
>> you want to receive VP8, try a=recvonly on a line with VP8.
> I gave this as an example of a possible way to do it, but that means you need two separate m= lines - one for send and one for receive. Seems strange to do this for something that you really want to be a single bi-directional stream.

An application that can't talk to itself is kind of bizarre too.

I think this is a corner case.