IETF Logo Mail Archive

Re: [tram] Fwd: I-D Action: draft-thomson-tram-turn-bandwidth-00.txt

"Yoakum, John H (John)" <yoakum@avaya.com> Thu, 20 February 2014 18:56 UTC

Return-Path: <yoakum@avaya.com>
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 1D1821A01CE for <tram@ietfa.amsl.com>; Thu, 20 Feb 2014 10:56:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] 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 COPgs1bvKo70 for <tram@ietfa.amsl.com>; Thu, 20 Feb 2014 10:56:00 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id B87591A00EC for <tram@ietf.org>; Thu, 20 Feb 2014 10:55:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak4FABhPBlOHCzIm/2dsb2JhbABWA4JCIyE4V8AOgRAWdIIlAQEBAQMSGzoSEAIBCA0BAwQBAQsdByERFAkIAgQBDQUIGodPAxEBokukCg2HUheMT4FkIRAGARGDE4EUBJZDAYhbhW+FRoMtgio
X-IronPort-AV: E=Sophos; i="4.97,513,1389762000"; d="scan'208,217"; a="50368607"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 20 Feb 2014 13:55:55 -0500
Received: from unknown (HELO AZ-US1EXHC01.global.avaya.com) ([135.11.85.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 20 Feb 2014 13:42:55 -0500
Received: from AZ-US1EXMB06.global.avaya.com ([fe80::38da:dafb:7358:e6f5]) by AZ-US1EXHC01.global.avaya.com ([135.11.85.12]) with mapi id 14.03.0174.001; Thu, 20 Feb 2014 13:55:53 -0500
From: "Yoakum, John H (John)" <yoakum@avaya.com>
To: Oleg Moskalenko <mom040267@gmail.com>, Alan Johnston <alan.b.johnston@gmail.com>
Thread-Topic: [tram] Fwd: I-D Action: draft-thomson-tram-turn-bandwidth-00.txt
Thread-Index: AQHPLmMlcJtLqkuUgEmVgUSRCLyaepq+efWA
Date: Thu, 20 Feb 2014 18:55:52 +0000
Message-ID: <93BEDDC39A54294B9E78C7860516FA4724AA4422@AZ-US1EXMB06.global.avaya.com>
References: <20140214030712.30321.21888.idtracker@ietfa.amsl.com> <CAKhHsXGzA=ZTFGTK7ht9hQbfG70iqKrDtxrZCdQNNMzBYZCk8A@mail.gmail.com> <530604ea.c5bf440a.5cfd.ffffde18SMTPIN_ADDED_BROKEN@mx.google.com> <CAKhHsXGsp6ma6Ko9op+YFRqSGM_Ex-jFo_fjz69rN0SEHfNK2A@mail.gmail.com> <CALDtMrKb3_38Rs0vaGnpEvNvTYz8YUTo89STvLJNXfkfdipDSQ@mail.gmail.com>
In-Reply-To: <CALDtMrKb3_38Rs0vaGnpEvNvTYz8YUTo89STvLJNXfkfdipDSQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.11.85.50]
Content-Type: multipart/alternative; boundary="_000_93BEDDC39A54294B9E78C7860516FA4724AA4422AZUS1EXMB06glob_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/XZNORKXJLjnv8z4jdULXk4M7hKc
Cc: Karl Stahl <karl.stahl@intertex.se>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] Fwd: I-D Action: draft-thomson-tram-turn-bandwidth-00.txt
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: Thu, 20 Feb 2014 18:56:02 -0000

+1
I fully agree with the comments that QOS should be a low priority for the initial focus of the TRAM efforts.  There are other groups doing QOS work and frankly I engage in WebRTC multimedia interactions daily over the Internet, enterprise VPNs, and various combinations and seldom suffer egregious quality issues.  I am more concerned about carriers doing things to regulate or degrade WebRTC flows than a failure of existing Internet mechanisms to enable them.

Significant focus on QOS before we better enable TURN to be easily used in a browser environment taking advantage or normal web characteristics (as opposed to historic telephony constructs) would seem to be highly distracting at this point.


Cheers,
John

AVAYA
1.919.425.8446

From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Oleg Moskalenko
Sent: Thursday, February 20, 2014 12:43 PM
To: Alan Johnston
Cc: Karl Stahl; tram@ietf.org
Subject: Re: [tram] Fwd: I-D Action: draft-thomson-tram-turn-bandwidth-00.txt



On Thu, Feb 20, 2014 at 6:26 AM, Alan Johnston <alan.b.johnston@gmail.com<mailto:alan.b.johnston@gmail.com>> wrote:



Personally, I am not sure how much QoS is actually in scope for TRAM. Have you been following RMCAT where congestion avoidance for RTP is being developed?  I see some overlap in your goals and the goals of that work.
-


I'd concentrate on the TURN application-level functionality, for now, and I'd leave QoS for the future discussions.

v2.23.0 | Report a Bug | By Email