Re: [rtcweb] Should we reference the pause/resume I-D?

Randell Jesup <randell-ietf@jesup.org> Tue, 18 March 2014 22:59 UTC

Return-Path: <randell-ietf@jesup.org>
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 70F751A0446 for <rtcweb@ietfa.amsl.com>; Tue, 18 Mar 2014 15:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001] 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 oz0gwo4O8W9O for <rtcweb@ietfa.amsl.com>; Tue, 18 Mar 2014 15:59:08 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC551A040E for <rtcweb@ietf.org>; Tue, 18 Mar 2014 15:59:07 -0700 (PDT)
Received: from pool-71-175-4-197.phlapa.fios.verizon.net ([71.175.4.197]:3667 helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <randell-ietf@jesup.org>) id 1WQ2yI-0006zZ-Jh for rtcweb@ietf.org; Tue, 18 Mar 2014 17:58:59 -0500
Message-ID: <5328CF7D.1020703@jesup.org>
Date: Tue, 18 Mar 2014 18:58:05 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <1447FA0C20ED5147A1AA0EF02890A64B1CF8B463@ESESSMB209.ericsson.se> <CAOW+2dsb1GqQmOxf7V6C1Xd_LG12d+kanSm80=kSwmQY=B7GSg@mail.gmail.com> <CAOJ7v-3S1axGPVWB8TF_ALwZ6ExF-D7m3MGsfrkx6EsQNWNpxQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-3S1axGPVWB8TF_ALwZ6ExF-D7m3MGsfrkx6EsQNWNpxQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Get-Message-Sender-Via: r2-chicago.webserversystems.com: authenticated_id: randell@jesup.org
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/xqNTB8HkXxGdTdwI9HXHA0z3bcc
Subject: Re: [rtcweb] Should we reference the pause/resume I-D?
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: Tue, 18 Mar 2014 22:59:09 -0000

On 3/12/2014 4:56 PM, Justin Uberti wrote:
> Agreed. Aren't there also patent declarations against this doc from 
> multiple holders?
>
> While SDP will likely be removed from the API in the future, the 
> replacement would be a app-specific message sent over websockets, 
> which seems like it would work just fine.

Except that WebSockets doesn't work peer2peer, which means both delay 
and issues with signaling configurations without a server sitting 
between the users.

However, an app-specific message sent over a DataChannel should work 
just fine.

The downside would be that everything becomes app-specific, which would 
be a problem for any sort of federation or peering setup, and likely 
gatewaying to legacy.


-- 
Randell Jesup -- rjesup a t mozilla d o t com