[core] Upload of draft-greevenbosch-core-minimum-request-interval
Bert Greevenbosch <Bert.Greevenbosch@huawei.com> Tue, 25 September 2012 09:29 UTC
Return-Path: <Bert.Greevenbosch@huawei.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96BC21F846A for <core@ietfa.amsl.com>; Tue, 25 Sep 2012 02:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level:
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1L20QreLTeCu for <core@ietfa.amsl.com>; Tue, 25 Sep 2012 02:29:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8C91021F85AF for <core@ietf.org>; Tue, 25 Sep 2012 02:29:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJZ60302; Tue, 25 Sep 2012 09:29:46 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 25 Sep 2012 10:28:38 +0100
Received: from SZXEML431-HUB.china.huawei.com (10.72.61.39) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 25 Sep 2012 10:29:25 +0100
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml431-hub.china.huawei.com ([10.72.61.39]) with mapi id 14.01.0323.003; Tue, 25 Sep 2012 17:29:17 +0800
From: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
To: "core@ietf.org" <core@ietf.org>
Thread-Topic: Upload of draft-greevenbosch-core-minimum-request-interval
Thread-Index: Ac2bADtqX7H/qdoNSUydLv3snsRk9w==
Date: Tue, 25 Sep 2012 09:29:17 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB6290D7272@szxeml509-mbs>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.110.143]
Content-Type: multipart/alternative; boundary="_000_46A1DF3F04371240B504290A071B4DB6290D7272szxeml509mbs_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [core] Upload of draft-greevenbosch-core-minimum-request-interval
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 09:29:49 -0000
Hello all, I have uploaded the following document: http://datatracker.ietf.org/doc/draft-greevenbosch-core-minimum-request-interval/ The document replaces draft-greevenbosch-core-block-minimum-time, but since the mechanism is now defined for a broader usage than just block transactions (e.g. the client browses the server), I thought a rename was appropriate. The draft describes a mechanism in which server and client communicate about the request frequency the client is using (or rather, its reciprocal being the request interval). In this way, the server has explicit means to slow down or speed up the client when appropriate. The draft now allows to update the timing during the transaction, whereas draft-...-block-minimum-time fixed the speed at the beginning of the transaction. Comments are welcome! Best regards, Bert
- [core] Upload of draft-greevenbosch-core-minimum-… Bert Greevenbosch