Re: [rtcweb] Comments on draft-ietf-rtcweb-data-channel-07
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Tue, 25 February 2014 22:33 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 8DD221A079F for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 14:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_82=0.6, RP_MATCHES_RCVD=-0.547, SPF_HELO_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 03uOiqLSNQUF for <rtcweb@ietfa.amsl.com>; Tue, 25 Feb 2014 14:33:39 -0800 (PST)
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 DFC691A079D for <rtcweb@ietf.org>; Tue, 25 Feb 2014 14:33:38 -0800 (PST)
Received: from [192.168.1.103] (p508F31B7.dip0.t-ipconnect.de [80.143.49.183]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 3FB631C0E97AE; Tue, 25 Feb 2014 23:33:37 +0100 (CET)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <530C7763.1030105@ericsson.com>
Date: Tue, 25 Feb 2014 23:33:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7592724-79FA-49EE-8920-95CEC1FFF7CA@lurchi.franken.de>
References: <53077E7B.1070900@ericsson.com> <CAN=GVAvYUZ-6H4Xsij2qnOrcAknEFEdpj9Ft4E2Bxr1sq5tvWw@mail.gmail.com> <530C7763.1030105@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/chekujj5lO3lebUvKyo9tE-xDkA
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 22:33:40 -0000
On Feb 25, 2014, at 11:58 AM, 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. OK, I'll use (S)RTP media... Best regards Michael > >> >> 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 > ---------------------------------------------------------------------- > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Comments on draft-ietf-rtcweb-data-chann… Magnus Westerlund
- [rtcweb] Comments on draft-ietf-rtcweb-data-chann… Paul Kyzivat
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Barry Dingle
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Magnus Westerlund
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Barry Dingle
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Randell Jesup
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Michael Tuexen
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-c… Michael Tuexen