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

Barry Dingle <btdingle@gmail.com> Tue, 25 February 2014 12:55 UTC

Return-Path: <btdingle@gmail.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 AF1D71A06DB for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 04:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_82=0.6, 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 r2Wcf3fM9Eke for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 04:55:37 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5661A03F2 for <rtcweb@ietf.org>; Tue, 25 Feb 2014 04:55:37 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hm4so4427068wib.2 for <rtcweb@ietf.org>; Tue, 25 Feb 2014 04:55:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6SSABJY1sNIWaaExGKspBdO3E/EybO7pt+4jla2iRho=; b=NNc4MV05iBYs2ices5vl0rTEnMyMjQ0fpBQtL+XALx/nnbah25U3O18tvgOecBjq6b 1fFun4vfbHewLRFfetDW9AKEUDX40dIPkx6V3EhONLSVAtWxLp6+tdxTsVKvi0ncUZhF 5M5pCWeVC5J8RoqK2VT+Yr1Cih/woFFDQRrpfrLci0zr/OLpSeOIEaMkYBYvjEjN2oV9 6QX/Ayn//ofAK9+fdkwwF6lQKCpZUsMz/04CkvIoTg2hyjdyv1m4fMGJCfISH1n3zpjt /x97hhx+FHrxDNI6y6aL+/04JMlpBqrub/k4hfLZ9xirJ2sJ17DrphNAst9Yu+VSN+cM HhsA==
X-Received: by 10.194.109.68 with SMTP id hq4mr24789579wjb.12.1393332935623; Tue, 25 Feb 2014 04:55:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.87.165 with HTTP; Tue, 25 Feb 2014 04:55:15 -0800 (PST)
In-Reply-To: <530C7763.1030105@ericsson.com>
References: <53077E7B.1070900@ericsson.com> <CAN=GVAvYUZ-6H4Xsij2qnOrcAknEFEdpj9Ft4E2Bxr1sq5tvWw@mail.gmail.com> <530C7763.1030105@ericsson.com>
From: Barry Dingle <btdingle@gmail.com>
Date: Tue, 25 Feb 2014 23:55:15 +1100
Message-ID: <CAN=GVAskK_U_c0HZQBzQEWX06B6WVEm1mGCDYdt4SynGjyzyHg@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary="089e0102e6daae89c704f33a9a98"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/d1hjVfaDq8DydfyKGiGjR55LoVc
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 12:55:39 -0000

On Tue, Feb 25, 2014 at 9:58 PM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> 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 see your point about being generic - and it is consistent with
draft-ietf-rtcweb-rtp-usage.


 >
> > 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?
>
> I was trying to find a way to identify
(a) 'all the SCTP Streams' (or maybe "all the SCTP Channels") as well as
(b) "all the (S)RTP Streams".

As you suggested, the term "SCTP Association" seems to work for (a). Does
"RTP Session" work for (b) ??

Cheers,
/Barry Dingle

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