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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 09 April 2014 14:12 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 A179B1A0323 for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 n-aOlYqc5MAo for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:12:22 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id 520C91A0318 for <rtcweb@ietf.org>; Wed, 9 Apr 2014 07:12:19 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta10.westchester.pa.mail.comcast.net with comcast id noHC1n0040xGWP85AqCK9Y; Wed, 09 Apr 2014 14:12:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta12.westchester.pa.mail.comcast.net with comcast id nqCJ1n0193ZTu2S3YqCJlJ; Wed, 09 Apr 2014 14:12:19 +0000
Message-ID: <53455542.2030105@alum.mit.edu>
Date: Wed, 09 Apr 2014 10:12:18 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20140409100258.9712.74771.idtracker@ietfa.amsl.com> <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D2B7AAB@ESESSMB209.ericsson.se> <CAN=GVAvLNyw6m0_edBOSJhq_tAy0duCjKHtq4ed+rLwW5_U35A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D2B7B0E@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2B7B0E@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397052739; bh=0wYWpNHsKTqV51D4z3aW3y4JFZ/7JF9L0i27jQFmZj8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=B37o/y+U1wY0DQZTeVicbrc1Lb/Rgfcomq+BgF1jXJN9DHNQ6ZkDbxeqHAR7ktH+t on/4fZAi1X5wKh+WPL17g3LluXy5Pa+bxj6hcYX/NDG068EXhtm0IzLs1MH1Pq9xKg Hm+URjp67rsggJHGgqrPmedlJ3wFaKpQjf8BeW9IR5jFK7q4kmIPUYykZPTkeTgDUH U9Bn4FsKFqXTs4rDdna3i9/i6vBwRw9Pf/4xYxjhgX5B681eeC4rkArGF0AAyB5a9+ cqn5TUe9+nNr3vthC5YQSVmSNS4yAwOAId/GTtrsO1FWwJJENLxCECZCWNNF4prUkP sPgYuKb3tGp+A==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/OEqBbIA0iO5DgNzTR6qsAKR7OXU
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 14:12:26 -0000

SCTP Data Channel, or simply Data Channel.

On 4/9/14 7:46 AM, Christer Holmberg wrote:
> 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?
>
> I think we had this discussion already earlier, and people suggested different new names.
>
> Regards,
>
> Christer
>
>
>
> 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
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>