IETF Logo Mail Archive

Re: [rtcweb] No Plan - but what's the proposal

Cullen Jennings <fluffy@iii.ca> Mon, 03 June 2013 19:53 UTC

Return-Path: <fluffy@iii.ca>
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 988D021E805A for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 12:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vQztEXoxZ2cc for <rtcweb@ietfa.amsl.com>; Mon, 3 Jun 2013 12:52:52 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id EF72B1F0D1D for <rtcweb@ietf.org>; Mon, 3 Jun 2013 12:42:53 -0700 (PDT)
Received: from sjc-vpn1-987.cisco.com (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CFB5E22E25B; Mon, 3 Jun 2013 15:42:46 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <51A8EB7F.6000506@jitsi.org>
Date: Mon, 03 Jun 2013 13:42:43 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC9403AD-47B1-4875-9420-A189FB75C5A9@iii.ca>
References: <51A65017.4090502@jitsi.org> <C3639EB3-0F44-4893-88DA-BB9F9C96A116@iii.ca> <51A8EB7F.6000506@jitsi.org>
To: Emil Ivov <emcho@jitsi.org>
X-Mailer: Apple Mail (2.1503)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] No Plan - but what's the proposal
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: Mon, 03 Jun 2013 19:53:16 -0000

I just wanted to quickly clear up I was not treating any of your ideas as a joke at all. Inline ….

On May 31, 2013, at 12:27 PM, Emil Ivov <emcho@jitsi.org> wrote:

>> 
>> The idea of exposing a low level API to the media stack and having
>> the all proposing to do FEC, RTX, SDP processing ect has been
>> discussed many times across the various working groups. It' jokingly
>> refereed to as comment 22 at this point.
> 
> I appreciate you are trying to turn this into a joke (which I think is a pity provide your chairing role in this working group), but abandoning SDP really isn't what this is about. You might have noticed text about this as early as the abstract:

I am not treating any of this as a joke at all - I am trying to understand what your roposal is. The "Comment 22" jokingly refers to some comments made by Mathew at WebRTC and nothing really to do this given that, as you say, this still uses Offer / Answer 

> 
>  This document does not question the use of SDP and the Offer/Answer
>  model or the value they have in terms of interoperability with legacy
>  or other non-WebRTC devices.

v2.23.0 | Report a Bug | By Email