Re: [core] AD review of draft-ietf-core-too-many-reqs-04

Michael Koster <michaeljohnkoster@gmail.com> Thu, 16 August 2018 14:57 UTC

Return-Path: <michaeljohnkoster@gmail.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 00675130E91 for <core@ietfa.amsl.com>; Thu, 16 Aug 2018 07:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 s9b-qt8ZII_P for <core@ietfa.amsl.com>; Thu, 16 Aug 2018 07:57:44 -0700 (PDT)
Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 369B11277C8 for <core@ietf.org>; Thu, 16 Aug 2018 07:57:44 -0700 (PDT)
Received: by mail-yb0-x229.google.com with SMTP id l16-v6so714193ybk.11 for <core@ietf.org>; Thu, 16 Aug 2018 07:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yiGmUuW3eGWnVg3Gc3Y3Z74WDzD9iUEv8Qu5j7ZI3ag=; b=V2k9JahcP7U5iZ5rqmGXMQUEmlsJ96a4teAOPZ4CLF0QfPmccxYWvUdX3K/vM/HAMA 1Ah0ksOamNf564xnX7wE9uoULoK2VagrjkFOJZLQ/FSBKOuH6YEGXPFyXqo0WQfDs/T5 hl5aDO43Eyou1pRdFQjA9wDAcNkH2ma7aVQuCfUBCJdKCyJIpD9TRM8mCABfs8VOChW7 7V1YIA3xeDRvW+QxUysnjH/PcdDexCMHS2jJl8tVngvTFO0RU67OJeBfhaQx0Kr5p1sR fdtXTBza9GedWnqvhhMR5IcJlsKJ+m3VYm7WtWiPIDsh5F6xS5law4rey69OqEvu33Wk 0H5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yiGmUuW3eGWnVg3Gc3Y3Z74WDzD9iUEv8Qu5j7ZI3ag=; b=qrokPVlbE8ZBY6fmTNaFd+5vJof1b+YQPqGuGoqvCeqCQUWUwAxMYuNutZyX+uTURO nWSZTvQLMwqk9oqb6D7fngaGxg539Xm4HIISB9XoC54Yb3wFyNWCsUhfiUWe1xePGgbA X6adtfL/51iVu1yNayWLDJnRD7UK9ClS1WGvrd8P07SW/2WDpCDEKMZpVYIIlCc3eaq5 p6Y5f9dhAoN1sHYNSBJDD0lAYKAzwc4gE0qNqLv6V0CBA7CybklT0Z8XKO1tNZa/dg9d uGARUedOV8QMtJ0dyy7n/rW8069tyYWqoUEyhygH9dRfpZ57g+LUs4HIC3T98sSpvFv1 dJ8g==
X-Gm-Message-State: AOUpUlEvoGaVvOa7kUd/OdfiPFSwE/6LDUAplYBTDerAJqPL5/kdBhWt dVb0URZ22ji14Deeb9Z/fk9fQKVW
X-Google-Smtp-Source: AA+uWPwp6F/e9MRfNzfBljYPSYZ0vKZal8rjlXa0HZotN/ySSXM0kzLbBWM5dIbptMK6BXf+k4Jfrg==
X-Received: by 2002:a25:e649:: with SMTP id d70-v6mr17871290ybh.273.1534431463326; Thu, 16 Aug 2018 07:57:43 -0700 (PDT)
Received: from [10.0.0.18] (108-201-184-41.lightspeed.sntcca.sbcglobal.net. [108.201.184.41]) by smtp.gmail.com with ESMTPSA id h10-v6sm7025087ywa.35.2018.08.16.07.57.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Aug 2018 07:57:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Michael Koster <michaeljohnkoster@gmail.com>
In-Reply-To: <3b397c15-d016-a281-3b0a-3b956a982a80@isode.com>
Date: Thu, 16 Aug 2018 07:57:39 -0700
Cc: "core@ietf.org" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB7F46D6-7CF5-4C31-A8CB-30AC914DE550@gmail.com>
References: <3b397c15-d016-a281-3b0a-3b956a982a80@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/kdw0PTxWZLhzkoVWD0SR7vv0xQI>
Subject: Re: [core] AD review of draft-ietf-core-too-many-reqs-04
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 16 Aug 2018 14:57:46 -0000

Good point. I apologize if there was discussion I missed on this. 

For CoRE Pub/Sub, we are already using max-age for data lifetime. 

Thus it may be preferable to have a new option for retry-after. 

It also may make implementation of a common transfer layer easier.

Best regards,

Michael

> On Aug 16, 2018, at 7:52 AM, Alexey Melnikov <alexey.melnikov@isode.com>; wrote:
> 
> Hi,
> 
> This is a straightforward document, as it tracks HTTP functionality defined in RFC 6585.
> 
> I have one main question about the document: when comparing this document with its HTTP counterpart, the HTTP version is using the Retry-After header field, while this document is reusing the Max-Age option. (HTTP has both Retry-After and Age header fields)
> 
> RFC 7252 defines Max-Age as follows:
> 
> 5.10.5.  Max-Age
> 
>    The Max-Age Option indicates the maximum time a response may be
>    cached before it is considered not fresh (see Section 5.6.1).
> 
>    The option value is an integer number of seconds between 0 and
>    2**32-1 inclusive (about 136.1 years).  A default value of 60 seconds
>    is assumed in the absence of the option in a response.
> 
>    The value is intended to be current at the time of transmission.
>    Servers that provide resources with strict tolerances on the value of
>    Max-Age SHOULD update the value before each retransmission. (See
>    also Section 5.7.1.)
> 
> So my question is: why is it Ok to reuse Max-Age option and not define a new one, which is closer to the desired semantics? If this was already discussed on the mailing list, please kindly point me to the relevant thread(s).
> 
> Thank you,
> 
> Alexey
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core