IETF Logo Mail Archive

[Spud] One bit for latency bandwidth tradeoff

Youjianjie <youjianjie@huawei.com> Tue, 26 January 2016 07:30 UTC

Return-Path: <youjianjie@huawei.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97DFE1A6F47; Mon, 25 Jan 2016 23:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 DEabALuj4Tpo; Mon, 25 Jan 2016 23:30:36 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F3171A6F49; Mon, 25 Jan 2016 23:30:35 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CDL54950; Tue, 26 Jan 2016 07:30:32 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 26 Jan 2016 07:30:30 +0000
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.62]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0235.001; Tue, 26 Jan 2016 15:30:25 +0800
From: Youjianjie <youjianjie@huawei.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "spud@ietf.org" <spud@ietf.org>
Thread-Topic: One bit for latency bandwidth tradeoff
Thread-Index: AdFYC2ufEvZMvnA6QRuvgZ56n6lDIQ==
Date: Tue, 26 Jan 2016 07:30:24 +0000
Message-ID: <F6C28B32DA084644BB6C8D0BD65B669DBBED91@NKGEML515-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.78.235]
Content-Type: multipart/alternative; boundary="_000_F6C28B32DA084644BB6C8D0BD65B669DBBED91NKGEML515MBSchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.56A72099.0054, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.5.62, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 60752dacd129d1fb7f98335c7d1ae800
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/uMwqyErZjomk-Giunbeg1A35la4>
Subject: [Spud] One bit for latency bandwidth tradeoff
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2016 07:30:38 -0000

Hi,


Existing work shows that having a latency-bandwidth trade-off decision would be useful.

For example: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=923942

http://people.networks.imdea.org/~sergey_gorinsky/pdf/RD_Services_SIGCOMM_2008.pdf



SPUD describes this as one of its use cases.

https://tools.ietf.org/html/draft-kuehlewind-spud-use-cases-00#section-4



We wonder: how should this be specified? Could we, for example, use the DSCP? If so, how - can we use an existing value, or should we define a new one?

Regards,
Jianjie

v2.23.0 | Report a Bug | By Email