[tram] Question about scope of TRAM

Harald Alvestrand <harald@alvestrand.no> Wed, 23 April 2014 12:33 UTC

Return-Path: <harald@alvestrand.no>
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 3AB021A01C3 for <tram@ietfa.amsl.com>; Wed, 23 Apr 2014 05:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 8aUwloEWMk3q for <tram@ietfa.amsl.com>; Wed, 23 Apr 2014 05:33:55 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id ACB621A0357 for <tram@ietf.org>; Wed, 23 Apr 2014 05:33:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 5C2217C5370 for <tram@ietf.org>; Wed, 23 Apr 2014 14:33:49 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kh3YuC7HW0mz for <tram@ietf.org>; Wed, 23 Apr 2014 14:33:48 +0200 (CEST)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by mork.alvestrand.no (Postfix) with ESMTPSA id 393217C536E for <tram@ietf.org>; Wed, 23 Apr 2014 14:33:48 +0200 (CEST)
Message-ID: <5357B32B.3070700@alvestrand.no>
Date: Wed, 23 Apr 2014 14:33:47 +0200
From: Harald Alvestrand <harald@alvestrand.no>
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
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/vAwxWWjVxROa_M-QBvGUOaArjQ8
Subject: [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 12:33:57 -0000

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?

         Harald