Re: [rtcweb] Codec control and SDP offer/answer frequency

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 24 August 2012 06:22 UTC

Return-Path: <christer.holmberg@ericsson.com>
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 2CD4821F8581 for <rtcweb@ietfa.amsl.com>; Thu, 23 Aug 2012 23:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.173
X-Spam-Level:
X-Spam-Status: No, score=-6.173 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mib6pW+8HG3U for <rtcweb@ietfa.amsl.com>; Thu, 23 Aug 2012 23:22:38 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 35AF121F8577 for <rtcweb@ietf.org>; Thu, 23 Aug 2012 23:22:37 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-b9-50371da8222d
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 62.D7.17130.8AD17305; Fri, 24 Aug 2012 08:22:32 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Fri, 24 Aug 2012 08:22:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>, "harald@alvestrand.no" <harald@alvestrand.no>
Date: Fri, 24 Aug 2012 08:18:37 +0200
Thread-Topic: [rtcweb] Codec control and SDP offer/answer frequency
Thread-Index: AQHNgW8HRNeyJMFktEekoJ61nDHCnJdn4IsAgACdL6I=
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05853409FF2F11@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05853409FF2EE3@ESESSCMS0356.eemea.ericsson.se>, <5035F12F.9000608@alvestrand.no> <7F2072F1E0DE894DA4B517B93C6A05853409FF2EF9@ESESSCMS0356.eemea.ericsson.se> <503608A5.6090304@alvestrand.no> <7F2072F1E0DE894DA4B517B93C6A0585340A1E3A73@ESESSCMS0356.eemea.ericsson.se> <50361279.3040204@alvestrand.no> <7F2072F1E0DE894DA4B517B93C6A0585340A1E3A7D@ESESSCMS0356.eemea.ericsson.se> <50369456.90605@alvestrand.no>, <E44893DD4E290745BB608EB23FDDB76228FB98@008-AM1MPN1-042.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB76228FB98@008-AM1MPN1-042.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM+Jvre4KWfMAg7Nf9SyO9XWxWZz/u4jN Yu2/dnYHZo8rE66weixZ8pPJ4+6tS0wBzFFcNimpOZllqUX6dglcGd0LtrIWNLFVfPqwg7mB 8TZLFyMnh4SAicSLL/fYIGwxiQv31gPZXBxCAqcYJdb0tjBDOAsYJW6uvcbaxcjBwSZgIdH9 TxukQUQgS+LepX5WEJtZQF3izuJz7CA2i4CqxMSHs8BsYQEniWXP+5kh6p0l7p3dyghhW0n0 Ln0AZvMKhEvsXr8TavE0Fok9s3+DNXMKhEl8aFvPBGIzAl33/dQaJohl4hK3nsxngrhaQGLJ nvPMELaoxMvH/1gh6kUl7rSvZ4So15FYsPsTG4StLbFs4WtmiMWCEidnPmGZwCg2C8nYWUha ZiFpmYWkZQEjyypG4dzEzJz0cnO91KLM5OLi/Dy94tRNjMCIOrjlt8EOxk33xQ4xSnOwKInz 6qnu9xcSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAuCc3MOh7rfR2EzOP1mavCc9kOwz4+PN/ nVKR7D2z4d+WK0cCQzz0ZGS/6E6zFPpY/Fj6oe3VDrE160P5+CfP5T/cI89ivLj7UOOftZ/P /D0lnPSvcu2/Fi6lG/9nfw2Y9JvFjKd31VWlblduhVbmAvn+Iu2zq7eE+Lh3WJo9rRHVamX5 Z+OlxFKckWioxVxUnAgAYGItTHYCAAA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Codec control and SDP offer/answer frequency
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: Fri, 24 Aug 2012 06:22:39 -0000

Hi,

>>> So, if I understand you correctly: you suggest that the codec control
>>information is transported using SDP/a=imageattr "internally" (between app
>>and browser), but then people can send it over the wire however they want?
>>
>>Yes. I believe that's the model we have agreed on.
>>
>
> I think that is fully in line with how SDP is treated in RTCWeb in general (at least so far), so there does not seem to be anything special about this case.

Fair enough.

But, that means that IF we use SDP offer/answer on the wire, and that offer/answer is not appropriate for codec control, we need to define another mechanism.

(By "we" I don't necessarily mean the rtcweb wg, but the community in general)

Regards,

Christer