Re: [core] I-D Action: draft-greevenbosch-core-minimum-request-interval-01.txt
Carsten Bormann <cabo@tzi.org> Fri, 26 April 2013 10:36 UTC
Return-Path: <cabo@tzi.org>
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 974D321F989F for <core@ietfa.amsl.com>; Fri, 26 Apr 2013 03:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0Jim1NoQ8DX for <core@ietfa.amsl.com>; Fri, 26 Apr 2013 03:36:51 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id BC97821F982F for <core@ietf.org>; Fri, 26 Apr 2013 03:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r3QAag9H023705 for <core@ietf.org>; Fri, 26 Apr 2013 12:36:42 +0200 (CEST)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 905633B9F; Fri, 26 Apr 2013 12:36:42 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20130426092352.870.74099.idtracker@ietfa.amsl.com>
Date: Fri, 26 Apr 2013 12:36:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6352EA2-8EB9-4D3D-9A4C-B461DF9FF16F@tzi.org>
References: <20130426092352.870.74099.idtracker@ietfa.amsl.com>
To: "core@ietf.org (core@ietf.org)" <core@ietf.org>
X-Mailer: Apple Mail (2.1503)
Subject: Re: [core] I-D Action: draft-greevenbosch-core-minimum-request-interval-01.txt
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: Fri, 26 Apr 2013 10:36:51 -0000
Bert: Thanks for updating this. I referred to the -00 in my reply to Martin Stiemerling's IESG comments. There were some comments in the Orlando meeting that people didn't quite know when to use such an Option and how to find a good value to put in it. (I think we need to check whether there is a better metric to use for throttling/load shedding than the elapsed time between two requests.) It would probably help to look at the use cases in some more detail. What specifically is a server trying to achieve by limiting the request interval? What kind of metric aligns best with such an objective? Just to build a very rough strawman for such an alternative metric: A server could ask a client to send the next request only after twice the time it took the client to obtain the previous response. (This would figure in network load in a way that the server on its own cannot do.) Another issue is the scope of the throttling: Is it for a single resource, this endpoint, the IP address, a prefix (say, a /64)? (Wider scopes have more security implications.) Grüße, Carsten On Apr 26, 2013, at 11:23, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : CoAP Minimum Request Interval > Author(s) : Bert Greevenbosch > Filename : draft-greevenbosch-core-minimum-request-interval-01.txt > Pages : 8 > Date : 2013-04-26 > > Abstract: > This document defines an "Minimum-Request-Interval" option for CoAP, > which can be used to negotiate the minimum time between two > subsequent requests within a single client and server pair. It can > be used for flow and congestion control, reducing the consumption of > server and network resources when needed. > > Note > > Discussion and suggestions for improvement are requested, and should > be sent to core@ietf.org. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-greevenbosch-core-minimum-request-interval > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-greevenbosch-core-minimum-request-interval-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-greevenbosch-core-minimum-request-interval-01 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >
- Re: [core] I-D Action: draft-greevenbosch-core-mi… Carsten Bormann
- Re: [core] I-D Action: draft-greevenbosch-core-mi… Bert Greevenbosch
- Re: [core] I-D Action: draft-greevenbosch-core-mi… Zach Shelby