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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 09 April 2014 11:23 UTC

Return-Path: <christer.holmberg@ericsson.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 B51661A021D for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 04:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 fgdR2i2ue6_f for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 04:23:03 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9061D1A00AF for <rtcweb@ietf.org>; Wed, 9 Apr 2014 04:23:02 -0700 (PDT)
X-AuditID: c1b4fb31-b7f688e000003e64-69-53452d95019f
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 10.6A.15972.59D25435; Wed, 9 Apr 2014 13:23:01 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.191]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0174.001; Wed, 9 Apr 2014 13:23:00 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt
Thread-Index: AQHPU9r8wvMWA0Q1K0mIC9kJW7dm+ZsI/KmAgAAnGWA=
Date: Wed, 9 Apr 2014 11:22:59 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2B7AAB@ESESSMB209.ericsson.se>
References: <20140409100258.9712.74771.idtracker@ietfa.amsl.com> <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org>
In-Reply-To: <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUyM+Jvje5UXddggw3H+CyWvzzBaLH2Xzu7 A5PHtPv32TyWLPnJFMAUxWWTkpqTWZZapG+XwJWx/+A2xoIGwYpvq06zNzBO4u1i5OSQEDCR mN38gxnCFpO4cG89WxcjF4eQwElGieu3prJAOIsZJZq2XADKcHCwCVhIdP/TBmkQEfCSePzg IlhYWMBdoudfLETYQ2LGp+WsELaVxJzLk1lAbBYBFYm5x3aA2bwCvhLPNx0H2yskUC7RdOcP I8gYTgFHiVWvakDCjEDnfD+1hgnEZhYQl7j1ZD4TxJkCEkv2nIc6WVTi5eN/rBC2ksSPDZdY IOp1JBbs/sQGYWtLLFv4mhliraDEyZlPWCYwis5CMnYWkpZZSFpmIWlZwMiyilGyOLU4KTfd yFAvNz23RC+1KDO5uDg/T684dRMjMFYObvltuINx4jX7Q4zSHCxK4rwM0zuDhATSE0tSs1NT C1KL4otKc1KLDzEycXBKNTDmxPIZLPh43UpYz36btbL+7Qc9livlHj/8oTu1afeh1/r+Cpus zzIrSUfpLE9bvzxKIeKk9cFVJ/eW/ubQeB2yLt5i9/4tXFM/91Tt5rpwxOaRv1vVipS4SpX9 FeFnw6udc0SC1ll1JNVOWBInuK/eIcOl7Oaq6XYzun/z9l1qa1D9+Wqzzz8lluKMREMt5qLi RADJOg4ZYwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/a3tcSWU17VXRHX55_d2igv4rLmM
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:23:06 -0000

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