Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt
Barry Dingle <btdingle@gmail.com> Wed, 09 April 2014 11:41 UTC
Return-Path: <btdingle@gmail.com>
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 11DAC1A0249 for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 04:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 oe5pSZ3b92yq for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 04:41:53 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5631A0242 for <rtcweb@ietf.org>; Wed, 9 Apr 2014 04:41:46 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w61so2331286wes.29 for <rtcweb@ietf.org>; Wed, 09 Apr 2014 04:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=W2Sf/iEwX4/wAkXlaQh5FDaDMD8cHvHSzP+m8T/q2vc=; b=Ciz6fSSIkCO6+7oQcNg7lpWklgCdlwLER/LBBCqXgLjOU5p0ECw07/FQKvXSrJymrp f8phPEzdJu9PLMv7IW22q+H4BzvCeV4YCZZs+KhNVMSwA1CzI2OctBbM2JIqP51HYArk BAhYXEAUMg9OX/2ZRKbQJBdw+ucDVPdBbYQCDHmD5P2pr7Cnhm18GbWzfJIbHObmLRBp CUfc9G/zmqPlnJKD75466FKUMAZav/3y/n7cux9Pe9T26U038+7CjQ+1lqSniL7uePsA Y27i4nqEtCqoZpSkI6B3zeQRXgskDeV2WEHXEw5vFuOfJUgEi70AgWmo7CNwx4LulLfT deRw==
X-Received: by 10.180.20.176 with SMTP id o16mr36962492wie.7.1397043705046; Wed, 09 Apr 2014 04:41:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.91.212 with HTTP; Wed, 9 Apr 2014 04:41:25 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2B7AAB@ESESSMB209.ericsson.se>
References: <20140409100258.9712.74771.idtracker@ietfa.amsl.com> <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D2B7AAB@ESESSMB209.ericsson.se>
From: Barry Dingle <btdingle@gmail.com>
Date: Wed, 09 Apr 2014 21:41:25 +1000
Message-ID: <CAN=GVAvLNyw6m0_edBOSJhq_tAy0duCjKHtq4ed+rLwW5_U35A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="bcaec53f35f5c66cf704f69a9563"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/MJZSQ-1wg4vh4cplPyGHonTMW7Q
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Colin Perkins <csp@csperkins.org>
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:41:58 -0000
Hi, If "WebRTC Data Channel" is to be used for other use-cases than just WebRTC, then the Title needs to change. But what do we call it? Cheers, Barry Dingle Australia On Wed, Apr 9, 2014 at 9:22 PM, Christer Holmberg < christer.holmberg@ericsson.com> wrote: > Hi, > > The WebRTC Data Channel will be used also for non-WebRTC applications (it > is e.g. base for the CLUE Data Channel), where the must-use-SRTP rule does > not necessarily apply. > > Having said that, I DO think that the draft text need to be more generic. > WebRTC can be described as a use-case, but it shall be clear that the > mechanism can also be used in other environments. > > Regards. > > Christer > > -----Original Message----- > From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Colin Perkins > Sent: 9. huhtikuuta 2014 14:01 > To: rtcweb@ietf.org > Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt > > 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/ > > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Barry Dingle
- [rtcweb] I-D Action: draft-ietf-rtcweb-data-chann… internet-drafts
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Colin Perkins
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Paul Kyzivat
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Colin Perkins
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Colin Perkins
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Magnus Westerlund
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Harald Alvestrand
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-c… Michael Tuexen