Re: [rtcweb] Use of offer / answer semantics

Colin Perkins <csp@csperkins.org> Tue, 06 September 2011 16:06 UTC

Return-Path: <csp@csperkins.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 911D421F8BB7 for <rtcweb@ietfa.amsl.com>; Tue, 6 Sep 2011 09:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.522
X-Spam-Level:
X-Spam-Status: No, score=-103.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 h+5eWR9D9Tbs for <rtcweb@ietfa.amsl.com>; Tue, 6 Sep 2011 09:06:42 -0700 (PDT)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id E2AB421F8BB2 for <rtcweb@ietf.org>; Tue, 6 Sep 2011 09:06:41 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1R0yCJ-0001VZ-Xy; Tue, 06 Sep 2011 16:08:27 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <4E6640FC.8080108@jitsi.org>
Date: Tue, 6 Sep 2011 17:08:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C88BD0C8-7AA5-4826-BE75-083A68A84B6F@csperkins.org>
References: <DB0C463A-FF5F-4C15-B2B4-E81B7DF92351@cisco.com> <4E6640FC.8080108@jitsi.org>
To: Emil Ivov <emcho@jitsi.org>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Use of offer / answer semantics
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: Tue, 06 Sep 2011 16:06:42 -0000

On 6 Sep 2011, at 16:49, Emil Ivov wrote:
...
>> 3) When a new codec is specified, and the SPD for the new codec is
>> specified in the MMUSIC WG, no other standardization would should be
>> required for it to be possible to use that in the web browsers.
> 
> I was about to suggest we should also mention the result from the
> PAYLOAD WG here (rather than MMUSIC only) but I believe that's actually
> what Colin meant.


The standards are done in PAYLOAD (was AVT before the split), not MMUSIC, true. My main point though was that the codec names and parameters aren't defined in terms of SDP, but rather using MIME media type names and parameters, which happen to currently get mapped to SDP. 

-- 
Colin Perkins
http://csperkins.org/