Re: [tram] Question about scope of TRAM
Simon Perreault <simon.perreault@viagenie.ca> Wed, 23 April 2014 13:09 UTC
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA2F1A039B for <tram@ietfa.amsl.com>; Wed, 23 Apr 2014 06:09:47 -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 1BIs6vbkdiZD for <tram@ietfa.amsl.com>; Wed, 23 Apr 2014 06:09:45 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 93A481A0394 for <tram@ietf.org>; Wed, 23 Apr 2014 06:09:45 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:15b:212f:d481:de2b]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B7B57413C6 for <tram@ietf.org>; Wed, 23 Apr 2014 09:09:39 -0400 (EDT)
Message-ID: <5357BB93.1040206@viagenie.ca>
Date: Wed, 23 Apr 2014 09:09:39 -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: tram@ietf.org
References: <5357B32B.3070700@alvestrand.no>
In-Reply-To: <5357B32B.3070700@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/55WZSGrrePNOwufp4pxGwfBo4AM
Subject: Re: [tram] Question about scope of TRAM
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 13:09:47 -0000
Le 2014-04-23 08:33, Harald Alvestrand a écrit : > On the RTCWEB list, the following claim was made: > >> Here, in TRAM we want to go beyond Level 4 QoS (already available and >> working as good as it can on the Internet), to give quality demanding >> WebRTC >> real-time traffic better QoE by: >> a. Forcing real-time traffic into IP-pipes having Level 2 QoS (using >> auto-discovered TURN servers) >> or >> b. Forcing real-time traffic into IP-pipes having Level 3 QoS (using >> auto-discovered TURN servers). Here we must have traffic shaping >> mechanisms >> working, and with correct and sufficient information to do the job. >> This is >> why we in TRAM discuss DISCUSS/MALICE, >> draft-thomson-tram-turn-bandwidth-00.txt attributes and recreating the >> payload type (PT) idea/intent in RTP packets (by now conveying >> bandwidth and >> traffic type in the RTP extension header >> http://www.ietf.org/mail-archive/web/rtcweb/current/msg09129.html. >> > > Before reacting to that, I want to check: > > Is it the opinion of the TRAM chairs that this is a fair description of > a subject that is being actively discussed in the TRAM WG? QoS is out of TRAM's scope. 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
- [tram] Question about scope of TRAM Harald Alvestrand
- Re: [tram] Question about scope of TRAM Simon Perreault
- Re: [tram] Question about scope of TRAM Karl Stahl