Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt

Colin Perkins <csp@csperkins.org> Wed, 09 April 2014 11:00 UTC

Return-Path: <csp@csperkins.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 8CB1D1A01EA for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 04:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 WKjBpevsnwK1 for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 04:00:52 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8321A01D1 for <rtcweb@ietf.org>; Wed, 9 Apr 2014 04:00:51 -0700 (PDT)
Received: from [130.209.247.112] (port=64867 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1WXqFJ-0008Dq-ST for rtcweb@ietf.org; Wed, 09 Apr 2014 12:00:50 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20140409100258.9712.74771.idtracker@ietfa.amsl.com>
Date: Wed, 9 Apr 2014 12:00:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org>
References: <20140409100258.9712.74771.idtracker@ietfa.amsl.com>
To: rtcweb@ietf.org
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/REgXw1MDM1RmCB73iGIlMdgK1BE
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt
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: Wed, 09 Apr 2014 11:00:56 -0000

On 9 Apr 2014, at 11:02, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.
> 
>        Title           : WebRTC Data Channels
>        Authors         : Randell Jesup
>                          Salvatore Loreto
>                          Michael Tuexen
> 	Filename        : draft-ietf-rtcweb-data-channel-08.txt
> 	Pages           : 15
> 	Date            : 2014-04-09
> 
> Abstract:
>   The Real-Time Communication in WEB-browsers working group is charged
>   to provide protocol support for direct interactive rich communication
>   using audio, video, and data between two peers' web-browsers.  This
>   document specifies the non-(S)RTP media data transport aspects of the
>   WebRTC framework.  It provides an architectural overview of how the
>   Stream Control Transmission Protocol (SCTP) is used in the WebRTC
>   context as a generic transport service allowing WEB-browsers to
>   exchange generic data from peer to peer.

This talks about “(S)RTP” throughout, but the rtp-usage draft requires that SRTP be used for WebRTC, and disallows plain RTP. I think this draft could be simplified by changing “(S)RTP” to “SRTP” throughout.

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