Re: [rtcweb] Some language on "prioritization"

Simon Perreault <simon.perreault@viagenie.ca> Tue, 22 April 2014 13:46 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 08CF71A041A for <rtcweb@ietfa.amsl.com>; Tue, 22 Apr 2014 06:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 0Dm_dlTBRZ7A for <rtcweb@ietfa.amsl.com>; Tue, 22 Apr 2014 06:46:36 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D99A11A0430 for <rtcweb@ietf.org>; Tue, 22 Apr 2014 06:46:30 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:349d:fe5f:bc57:89]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 4185B40221; Tue, 22 Apr 2014 09:46:25 -0400 (EDT)
Message-ID: <535672B0.5030900@viagenie.ca>
Date: Tue, 22 Apr 2014 09:46:24 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Karl Stahl <karl.stahl@intertex.se>, "'Pal Martinsen (palmarti)'" <palmarti@cisco.com>, 'Harald Alvestrand' <harald@alvestrand.no>, 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
References: <5339A120.3040909@alvestrand.no> <CABkgnnVUHUx+3wY3Dsi=UvNkUw_Es1apeMSonq7DtEg_3UKRNg@mail.gmail.com> <FBA84C78-FE8E-4FEF-8AD3-CAF24C57E512@lurchi.franken.de>, <5339AA58.9070301@alvestrand.no> <834D5209-5EEA-4001-B8ED-3835FC4D05FB@skype.net> <00af01cf4f59$fa617b90$ef2472b0$@stahl@intertex.se> <020501cf5d5b$117e9830$347bc890$@stahl@intertex.se>
In-Reply-To: <020501cf5d5b$117e9830$347bc890$@stahl@intertex.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/s2GQQ43XbZnmvin4gShZs85gYfY
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Some language on "prioritization"
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, 22 Apr 2014 13:46:41 -0000

Le 2014-04-21 08:13, Karl Stahl a écrit :
> 1) AVOIDING SELF DESTRUCTING PRIORITAZATION FROM FILE TRANSFER IN DATA
> CHANNEL
> 
> Simon,
> 
> I saw you are an author of TURN-TCP RFC6062. Doesn't that RFC allow a 
> webrtc file transfer channel (separate from the rtcweb data channel) 
> to be created, using TLS file transfer P2P? ICE/STUN/TURN would set 
> it up, NOT BUNDLED with chunk data and RTP media.

RFC6062 knows nothing about WebRTC or TLS inside the peer connection
payload. So it doesn't explicitly "allow" what you suggest. But I guess
it doesn't prevent it either. It doesn't care.

> Freeing the current rtcweb data channel from file transfer would remedy 
> the self destruction of prioritization/QoS for data chunks and RTP media 
> as explained in (A), (B) and (C) below.
> 
> I also think it would be much better for a web programmer to have a 
> separate p2p file transfer channel (that is not and cannot be prioritized) 
> than pouring files into the data channel.

Why do you think using a separate channel would eliminate the issue of
prioritization? We would end up with multiple channels contending for
the same bandwidth. You have just moved the problem one level up. And
made things needlessly more complex, IMHO.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca