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

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 09 April 2014 15:02 UTC

Return-Path: <magnus.westerlund@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 A6F0E1A030F for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 08:02: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 4FplBGlv3IJ9 for <rtcweb@ietfa.amsl.com>; Wed, 9 Apr 2014 08:02:02 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1D71A02C5 for <rtcweb@ietf.org>; Wed, 9 Apr 2014 08:01:54 -0700 (PDT)
X-AuditID: c1b4fb32-b7fe98e0000034f3-30-534560e13733
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id CD.DF.13555.1E065435; Wed, 9 Apr 2014 17:01:53 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.53) with Microsoft SMTP Server id 14.3.174.1; Wed, 9 Apr 2014 17:01:05 +0200
Message-ID: <534560B1.2050900@ericsson.com>
Date: Wed, 9 Apr 2014 17:01:05 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Colin Perkins <csp@csperkins.org>
References: <20140409100258.9712.74771.idtracker@ietfa.amsl.com> <F09BCD44-1060-4DCB-A796-7A31F1C634DE@csperkins.org> <A05F0177-568C-4B19-AD48-9F415A4C008B@lurchi.franken.de> <02F2BCF4-70B5-47A4-ACE6-C0CCCAB11A50@csperkins.org> <9889BAD9-D9A7-42F2-A0DC-632C26696345@lurchi.franken.de> <73C21E05-E36C-4899-98A4-9D762B75FCE4@csperkins.org> <6C2B5FD8-D9A8-4889-8483-046B4ACC75EC@lurchi.franken.de>
In-Reply-To: <6C2B5FD8-D9A8-4889-8483-046B4ACC75EC@lurchi.franken.de>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUyM+Jvje7DBNdgg4uLzSyWvzzBaHGxaQmj xdp/7ewOzB7T7t9n81iy5CeTx4aWHUwBzFFcNimpOZllqUX6dglcGVO+P2Qv2ClV8fjuYbYG xkbRLkZODgkBE4n9c66wQdhiEhfurQeyuTiEBE4ySkztnsoO4SxjlFh18hEzSBWvgLbEs/cX 2EFsFgEViR8tb1hBbDYBC4mbPxrBJokKBEssnbOYBaJeUOLkzCdANgeHiECUxNwbWSBhZgFR iVcPp4CNFBZwlzj6fDnUri5miQsND8Dmcwq4Srw+tIUNpFdCQFyipzEIotdA4siiOawQtrxE 89bZYHOEgE5raOpgncAoNAvJ5llIWmYhaVnAyLyKUbI4tbg4N93IQC83PbdEL7UoM7m4OD9P rzh1EyMwxA9u+W20g/HkHvtDjNIcLErivNdZa4KEBNITS1KzU1MLUovii0pzUosPMTJxcEo1 MLaW/9ghWXhddYJpkNbH748dN9x0Yv6TxvfmplDzTiZW0TkFL6+yFJYqzlv5/93544s8OwNe tYYf/TJ1fVlx373ak6/8Zp9VduQXcV/w55efpfjiO3qPvNJXHXtSy3Iy22zGUXXT2YeP3zuu En9dTntBhdAXhlfnD0zc6+PdzGAlrHVzM6N6gooSS3FGoqEWc1FxIgCUnz6NPwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/cyIrOM_2tsCFm88z-vaILii2tVI
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 15:02:06 -0000

On 2014-04-09 16:47, Michael Tuexen wrote:
> 
> On 09 Apr 2014, at 16:39, Colin Perkins <csp@csperkins.org> wrote:
> 
>> On 9 Apr 2014, at 15:33, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote:
>>> On 09 Apr 2014, at 16:25, Colin Perkins <csp@csperkins.org> wrote:
>>>> On 9 Apr 2014, at 15:20, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote:
>>>>> 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...
>>>>
>>>> SRTP is an RTP profile. My comment was that if this is for WebRTC only, then  only SRTP can be used, and not plain RTP. Using “(S)RTP” rather than “SRTP” in this draft suggests that the secure profile is optional, which isn’t the case in WebRTC. If this is for more general use than WebRTC, then “(S)RTP” is fine.
>>> It is clear that in WebRTC only SRTP is used...
>>
>> I don’t believe your draft is clear on that, due to the use of “(S)RTP” terminology. That’s why I commented.
> I'm happy to change it to SRTP... Let's see what Magnus thinks...

I am fine with that!

/Magnus

> 
> Best regards
> Michael
>>
>> -- 
>> Colin Perkins
>> http://csperkins.org/
>>
>>
>>
>>
> 
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------