IETF Logo Mail Archive

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

Michael Hammer <michael.hammer@yaanatech.com> Thu, 20 February 2014 19:13 UTC

Return-Path: <michael.hammer@yaanatech.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 866DB1A024A for <tram@ietfa.amsl.com>; Thu, 20 Feb 2014 11:13:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 c5lveQyDKUeU for <tram@ietfa.amsl.com>; Thu, 20 Feb 2014 11:12:58 -0800 (PST)
Received: from email1.corp.yaanatech.com (webmail10.yaanatech.com [63.128.177.10]) by ietfa.amsl.com (Postfix) with ESMTP id BC8F91A0243 for <tram@ietf.org>; Thu, 20 Feb 2014 11:12:58 -0800 (PST)
Received: from SC9-EX2K10MB1.corp.yaanatech.com ([fe80::149d:c2e1:8065:2a47]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.03.0123.003; Thu, 20 Feb 2014 11:12:56 -0800
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "yoakum@avaya.com" <yoakum@avaya.com>, "mom040267@gmail.com" <mom040267@gmail.com>, "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>
Thread-Topic: [tram] Fwd: I-D Action: draft-thomson-tram-turn-bandwidth-00.txt
Thread-Index: AQHPLBx+/w69jI7P3kSEjcKKvn9TyZq+N0pvgAC84wCAABR3AP//fjww
Date: Thu, 20 Feb 2014 19:12:55 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3BBF3175B@sc9-ex2k10mb1.corp.yaanatech.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> <93BEDDC39A54294B9E78C7860516FA4724AA4422@AZ-US1EXMB06.global.avaya.com>
In-Reply-To: <93BEDDC39A54294B9E78C7860516FA4724AA4422@AZ-US1EXMB06.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.163]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0215_01CF2E45.D908D6D0"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/dmuphx4v7ohMAQC8Hkf3sZG1vIo
Cc: "karl.stahl@intertex.se" <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 19:13:01 -0000

Perhaps one thing TRAM signaling can return to the client is a link to an
API for doing QoS control.

Then whatever QoS control protocol you want to use could be patched in.

Might make this a little more future proof.

 

Michael Hammer

Principal Engineer

 <mailto:michael.hammer@yaanatech.com> michael.hammer@yaanatech.com

Mobile: +1 408-202-9291

500 Yosemite Drive Suite 120

Milpitas, CA 95035 USA

 

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

 

+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>
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