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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Wed, 09 April 2014 14:20 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 35BF21A0380 for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.823
X-Spam-Level:
X-Spam-Status: No, score=-1.823 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.272, SPF_HELO_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 1c1ZOBKAn1kZ for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 07:20:44 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 1614F1A032F for <rtcweb@ietf.org>; Wed, 9 Apr 2014 07:20:43 -0700 (PDT)
Received: from [192.168.1.103] (p508F0BDC.dip0.t-ipconnect.de [80.143.11.220]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 83C801C1047E4; Wed, 9 Apr 2014 16:20:41 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org>
Date: Wed, 9 Apr 2014 16:20:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A05F0177-568C-4B19-AD48-9F415A4C008B@lurchi.franken.de>
References: <20140409100258.9712.74771.idtracker@ietfa.amsl.com> <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/DcLAm3ymvZgLTHHLUn08s0e6Rzc
Cc: rtcweb@ietf.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 14:20:48 -0000

On 09 Apr 2014, at 13:00, Colin Perkins <csp@csperkins.org> wrote:

> 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.
Hi Colin,

The (S)RTP notion goes back to a comment from Magnus. If I remember it correctly he considers
SRTP a profile of RTP. Since I don't wanted to just use RTP, I ended up with (S)RTP based
on a discussion with Magnus.

However, I'm fine with changing it to SRTP...

Magnus: Any comment?

Best regards
Michael

> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>