Re: [rtcweb] Comments on draft-ietf-rtcweb-data-channel-07

Magnus Westerlund <magnus.westerlund@ericsson.com> Tue, 25 February 2014 10:58 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 5DA061A01B0 for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 02:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level:
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_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 G_JaoBjk9RQ3 for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 02:58:47 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 49AFD1A03F9 for <rtcweb@ietf.org>; Tue, 25 Feb 2014 02:58:47 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-2a-530c77659d78
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id B5.ED.23809.5677C035; Tue, 25 Feb 2014 11:58:45 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.59) with Microsoft SMTP Server id 14.2.347.0; Tue, 25 Feb 2014 11:58:43 +0100
Message-ID: <530C7763.1030105@ericsson.com>
Date: Tue, 25 Feb 2014 11:58:43 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Barry Dingle <btdingle@gmail.com>
References: <53077E7B.1070900@ericsson.com> <CAN=GVAvYUZ-6H4Xsij2qnOrcAknEFEdpj9Ft4E2Bxr1sq5tvWw@mail.gmail.com>
In-Reply-To: <CAN=GVAvYUZ-6H4Xsij2qnOrcAknEFEdpj9Ft4E2Bxr1sq5tvWw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUyM+JvjW5qOU+wwYYVohaP79taXJ2xhNli 7b92dgdmj52z7rJ7LFnyk8njy+XPbAHMUVw2Kak5mWWpRfp2CVwZr2fuYClYJFjR/7eVpYHx DW8XIyeHhICJxLwF35ghbDGJC/fWs3UxcnEICRxilGiZdhTKWc4ocWfOPzaQKl4BbYm3q+Yy gdgsAqoSx2++ZgGx2QQsJG7+aASrERUIlth54DcjRL2gxMmZT8BqRIDq982eDNbLLBAl8fHu BaB6Dg5hAWeJ6bfNQMJCAgUSSz98ASvnFAiU2N+wGKxEQkBcoqcxCKJTU6J1+292CFteonnr bGaIVm2JhqYO1gmMQrOQLJ6FpGUWkpYFjMyrGNlzEzNz0suNNjECQ/fglt+qOxjvnBM5xCjN waIkzvvhrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkbNf3f4wz+Y9d5snNeu86vU4ErK 8VP605z/uayZFsRx5YSwU8ur5Ws07qibu/+JlalijBH5fnfvWx4eSzetrR927FQsc+f5ufWW seyqlnOuvT03Tqo/VmvceH3pi+U1ss0ckxce3R/6MaXnzBHbh66ZxRVbJynk5IR52jHErzh8 26tKrlP41nElluKMREMt5qLiRADQeDKQKwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/nuBWRuxVdrLouWNlepBr9-0g9Eg
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, draft-ietf-rtcweb-data-channel@tools.ietf.org
Subject: Re: [rtcweb] Comments on draft-ietf-rtcweb-data-channel-07
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: Tue, 25 Feb 2014 10:58:49 -0000

On 2014-02-23 10:54, Barry Dingle wrote:
> In reference to your first _Section 1 comments_, I agree that we need to
> clearly differentiate the SRTP media and the SCTP media. (Note - SRTP -
> not RTP !)

So SRTP is an extension of RTP, in fact it is a profile, or rather two
(RTP/SAVP or RTP/SAVPF). I wrote RTP because I meant no specific RTP
configuration here, it can be any of the profiles and any of the
extensions. I know and fully support that RTCWEB uses RTP/SAVPF for RTP
transported media, however in the wider context and possible other usage
of the defined mechanism this may or may not be true. Therefore I see a
need to be generic in that discussion. If one want to emphasize the SRTP
part, then use (S)RTP.

> 
> I agree that there could be real-time media that can be sent over SCTP
> Channels are still meet the criteria for 'real-time' as being 'received
> within a few hundred milliseconds of being generated' - see WebRTC
> Overview section 2.4.
> 
> Maybe we need to differentiate the Channel types - and then refer to the
> data going over those Channels. For instance,if we define "SRTP
> Channels" and "SCTP Channels", we could then refer to 'SRTP Channel
> media' which would have a specific meaning.

Well, around RTP we aren't discussing "channels" at all. Thus, this
becomes very ambiguous to what it means, unless you have a definition to
go along with it.

In the context of a PeerConnection we can have one or more RTP session.

Also, I don't know what an SCTP channel is. There is an SCTP
association, which is something between two endpoints. On top of this we
have the SCTP Data channels. So what are you missing or want from these
definitions?


Cheers

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