IETF Logo Mail Archive

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

Oleg Moskalenko <mom040267@gmail.com> Thu, 20 February 2014 19:25 UTC

Return-Path: <mom040267@gmail.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 B698D1A027F for <tram@ietfa.amsl.com>; Thu, 20 Feb 2014 11:25:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 4CRDjoLw13ay for <tram@ietfa.amsl.com>; Thu, 20 Feb 2014 11:25:31 -0800 (PST)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 292881A0279 for <tram@ietf.org>; Thu, 20 Feb 2014 11:25:31 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so2202368pde.41 for <tram@ietf.org>; Thu, 20 Feb 2014 11:25:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hMyk0G1TdpFaNlQAPPuhx3BokNjyxgKDD09LXlyqhKA=; b=JKO1pNRnFbDPoOGKXvk5URtvy1g12zRx1z7PtTA8LpiGXF2a4vIW/6+V3Ki0kF+09F yMIlbCt9bAABOnnTPhwKMYonOco6mr7pG7DtUBuNZ1pFMVGsBwEjIgJHXDbXaiJtFSJq lo3mzRijlS17AjaPiDXqSEVO4ZGGFTqOojeL0/6hKnc5kGK3rB8MD/dAM1X4J2ZOKNhl p5jrxZiTDuWY4VRkCJaLWtRzLY9SvzjkFcDtoMe7BtAL2iyQHyvLs9R3IgmNGNOxyDIP XI/uz4qAaqB62RVUVGyitGNkRuozQbUNP6vSW30C7ej2i8swQspebdaq9+yoZrDg3fJD SWKg==
MIME-Version: 1.0
X-Received: by 10.68.170.66 with SMTP id ak2mr4058526pbc.5.1392924327631; Thu, 20 Feb 2014 11:25:27 -0800 (PST)
Received: by 10.68.147.131 with HTTP; Thu, 20 Feb 2014 11:25:27 -0800 (PST)
In-Reply-To: <530655DF.6080604@alum.mit.edu>
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> <00C069FD01E0324C9FFCADF539701DB3BBF3175B@sc9-ex2k10mb1.corp.yaanatech.com> <530655DF.6080604@alum.mit.edu>
Date: Thu, 20 Feb 2014 11:25:27 -0800
Message-ID: <CALDtMrLnURRgxAm34TwV5yUyfUCNDGC440AJnHvo96gmj0V9+Q@mail.gmail.com>
From: Oleg Moskalenko <mom040267@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="047d7b86d55cbf609d04f2db771a"
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/pclNLnyb1WLwvv67by_VvJ1NGrs
Cc: "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:25:32 -0000

Obviously, a "link to API" means here "a URL/URI to REST API to QoS".

I am not sure that such  web-based API exist. May be, a custom proprietary
implementation can be used.

But I'd postpone any discussion on that matter.




On Thu, Feb 20, 2014 at 11:22 AM, Paul Kyzivat <pkyzivat@alum.mit.edu>wrote:

> On 2/20/14 2:12 PM, Michael Hammer wrote:
>
>> 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.
>>
>
> "A link to an API"?????
>
> AFAIK that doesn't make sense.
>
> A link that identifies a target and protocol to control QoS makes some
> sense to me. But then how do you know the client will support the protocol
> you are offering?
>
>         Thanks,
>         Paul
>
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>

v2.23.0 | Report a Bug | By Email