Re: [core] "Too Many Requests Response Code for CoAP" draft (draft-keranen-core-too-many-reqs-00)
Klaus Hartke <hartke@projectcool.de> Mon, 05 March 2018 17:52 UTC
Return-Path: <hartke@projectcool.de>
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 196C112DA19 for <core@ietfa.amsl.com>; Mon, 5 Mar 2018 09:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 fj05ntQwsIOW for <core@ietfa.amsl.com>; Mon, 5 Mar 2018 09:52:38 -0800 (PST)
Received: from wp382.webpack.hosteurope.de (wp382.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8597::]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72A3B12DA14 for <core@ietf.org>; Mon, 5 Mar 2018 09:52:38 -0800 (PST)
Received: from mail-qt0-f174.google.com ([209.85.216.174]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1esuHs-0008PH-Cm; Mon, 05 Mar 2018 18:52:36 +0100
Received: by mail-qt0-f174.google.com with SMTP id a23so21355542qtn.0 for <core@ietf.org>; Mon, 05 Mar 2018 09:52:36 -0800 (PST)
X-Gm-Message-State: AElRT7Ek1zF/CVRRLsWwaWuEfAbIW6LDH6k+V7Jg4F4SfNUH4VlLzFTT 4sJs4g3MqQt2sYbrimmxalE0EuMNhgBEHVXQaAA=
X-Google-Smtp-Source: AG47ELuZcI75SfzKxVHiRNQsbFK/DmTEhccAhkZ6XrEUrFkmxu42puD+kQoyrP39kw2xZg/RYrRdcjs/Uiip3Or2x8M=
X-Received: by 10.200.81.84 with SMTP id h20mr24733918qtn.340.1520272355364; Mon, 05 Mar 2018 09:52:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.134.195 with HTTP; Mon, 5 Mar 2018 09:51:54 -0800 (PST)
In-Reply-To: <2599BFCF-9A26-40BE-95E1-FBFF6B1ECDD4@gmail.com>
References: <152025806136.14652.11784946748337213501.idtracker@ietfa.amsl.com> <225023B8-B663-482A-93E6-8DD054606A79@ericsson.com> <CAAzbHvYBycMA48UBA=J_ZZBUf9fjsam8uaQPpwpe_02swhQp4Q@mail.gmail.com> <2599BFCF-9A26-40BE-95E1-FBFF6B1ECDD4@gmail.com>
From: Klaus Hartke <hartke@projectcool.de>
Date: Mon, 05 Mar 2018 18:51:54 +0100
X-Gmail-Original-Message-ID: <CAAzbHvazO6zRPG5tdJnDWNdFqpQatZB2-wzTJM3q5gAsqF4QzQ@mail.gmail.com>
Message-ID: <CAAzbHvazO6zRPG5tdJnDWNdFqpQatZB2-wzTJM3q5gAsqF4QzQ@mail.gmail.com>
To: Michael Koster <michaeljohnkoster@gmail.com>
Cc: Ari Keränen <ari.keranen@ericsson.com>, core <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1520272358; a42cabf8;
X-HE-SMSGID: 1esuHs-0008PH-Cm
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/CDOM7H2EM5d7Ya5SVYGbd5eEuEA>
Subject: Re: [core] "Too Many Requests Response Code for CoAP" draft (draft-keranen-core-too-many-reqs-00)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 05 Mar 2018 17:52:40 -0000
Michael Koster wrote: > We are proposing a code in Pub/Sub for the case of a broker where the topic > exists but there is not a valid data value. This sounds strangely familiar: https://tools.ietf.org/html/draft-hartke-core-pending-02 > We thought that an equivalent to the HTTP 204 "No Content" could be used but > the code conflicts with 2.04 in CoAP, so we propose 2.07 We had that in the -01 version of the draft, but that didn't seem to gain traction, so we've switched to a new content-format to indicate this status. Would this work for pub/sub? Klaus
- [core] "Too Many Requests Response Code for CoAP"… Ari Keränen
- Re: [core] "Too Many Requests Response Code for C… Klaus Hartke
- Re: [core] "Too Many Requests Response Code for C… Michael Koster
- Re: [core] "Too Many Requests Response Code for C… Klaus Hartke
- Re: [core] "Too Many Requests Response Code for C… Ari Keränen
- [core] "No Content" CoAP option (was Re: "Too Man… Ari Keränen
- Re: [core] "Too Many Requests Response Code for C… Klaus Hartke
- Re: [core] "No Content" CoAP option (was Re: "Too… Klaus Hartke
- Re: [core] "No Content" CoAP option (was Re: "Too… peter van der Stok