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

Christer Holmberg <> Wed, 09 April 2014 11:46 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3150A1A0249 for <>; Wed, 9 Apr 2014 04:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fnsvLrEk8dNK for <>; Wed, 9 Apr 2014 04:46:26 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BF1C71A00E6 for <>; Wed, 9 Apr 2014 04:46:24 -0700 (PDT)
X-AuditID: c1b4fb25-b7f3b8e0000006f1-7e-5345330fa4ea
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 4D.12.01777.F0335435; Wed, 9 Apr 2014 13:46:23 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Wed, 9 Apr 2014 13:46:23 +0200
From: Christer Holmberg <>
To: Barry Dingle <>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt
Thread-Index: AQHPU9r8wvMWA0Q1K0mIC9kJW7dm+ZsI/KmAgAAnGWD//+RHgIAAIoLA
Date: Wed, 09 Apr 2014 11:46:21 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUyM+JvjS6/sWuwwbdtahaP79taLH95gtFi 7b92dgdmj2n377N57Jx1l91jyZKfTAHMUVw2Kak5mWWpRfp2CVwZJ5v9CubIViyYOImxgXGP TBcjJ4eEgInE+VfbWSFsMYkL99azgdhCAocZJfYfzu9i5AKyFzNKrOw9ydzFyMHBJmAh0f1P G6RGREBVYt/syUwgNrOAl8TznTsYQUqEBdwlev7FQpR4SMz4tJwVwnaTuNzVyQ5iswioSFxe t48dpJxXwFfi9zUjiE1NTBL/Xu8Fi3MKBEo8n+4CUs4IdNn3U2ugNolL3HoynwniYgGJJXvO M0PYohIvH/+D+kRJ4seGSywgY5gFNCXW79KHaFWUmNL9EOwCXgFBiZMzn7BMYBSbhWTqLISO WUg6ZiHpWMDIsoqRPTcxMye93GgTIzBSDm75rbqD8c45kUOM0hwsSuK8H946BwkJpCeWpGan phakFsUXleakFh9iZOLglGpg9Lzkn1es0qWWNGs7a2KqsrO6v/ak+3JfD9yTdO3l6njgyRKX /yJgSW7Nxzq1jb0zTmat8liVdlpV/gUve0/2fLGeZbIZ0VynF2/rSZX/cHCmYvTTqkUHnfja +qXl1ILqV2369cfOZ8KnhMALyzIPsDmwpkfy5k91aVdO4vokY3ron4Z37D4lluKMREMt5qLi RAA7IuhlYgIAAA==
Cc: "" <>, Colin Perkins <>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Apr 2014 11:46:28 -0000


>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.



On Wed, Apr 9, 2014 at 9:22 PM, Christer Holmberg <> wrote:

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.



-----Original Message-----
From: rtcweb [] On Behalf Of Colin Perkins
Sent: 9. huhtikuuta 2014 14:01
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-08.txt

On 9 Apr 2014, at 11:02, 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

rtcweb mailing list

rtcweb mailing list