[core] Fwd: New Version Notification for draft-hartke-core-pending-02.txt
peter van der Stok <stokcons@xs4all.nl> Mon, 26 February 2018 10:54 UTC
Return-Path: <stokcons@xs4all.nl>
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 E9BD9126DCA for <core@ietfa.amsl.com>; Mon, 26 Feb 2018 02:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 R7Boumi3F99z for <core@ietfa.amsl.com>; Mon, 26 Feb 2018 02:54:22 -0800 (PST)
Received: from lb1-smtp-cloud9.xs4all.net (lb1-smtp-cloud9.xs4all.net [194.109.24.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8EC1126CB6 for <core@ietf.org>; Mon, 26 Feb 2018 02:54:22 -0800 (PST)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:215]) by smtp-cloud9.xs4all.net with ESMTPA id qGQFeBFNSwC4EqGQFeAUir; Mon, 26 Feb 2018 11:54:19 +0100
Received: from AMontpellier-654-1-186-134.w92-145.abo.wanadoo.fr ([92.145.165.134]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 26 Feb 2018 11:54:19 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 Feb 2018 11:54:19 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: Core <core@ietf.org>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <151963922478.31478.9450242369979488900.idtracker@ietfa.amsl.com>
References: <151963922478.31478.9450242369979488900.idtracker@ietfa.amsl.com>
Message-ID: <7dbaebcd27310388dd4fd0e2e3968609@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfJThgGM06znsCmajYa/SfGa6zBR7LFo2QFzBbs/1LKaxd3bjGwFrKmU2nXTZodhdJj21ECbHFpQ22BRrRm9VU3rrwBYV6FWhtrQ5bbgzW/Kd5suIIZ37 w82BFeNxjtzQbVgWemk6OleYg5UpqKPK+T9hVRY/x+7YacHw4XBjszeQWjGswFUWI2wVFzV6/4gglRc6CiTPNS/Vxslr5sEmEiM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/0qacCrn2NE4u5J9CcULM-m188dE>
Subject: [core] Fwd: New Version Notification for draft-hartke-core-pending-02.txt
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, 26 Feb 2018 10:54:25 -0000
Hi Core, a new version of the pending draft is submitted. The current version does not try to extend one already dedicated response code or create a new one. Klaus and Peter A new version of I-D, draft-hartke-core-pending-02.txt has been successfully submitted by Klaus Hartke and posted to the IETF repository. Name: draft-hartke-core-pending Revision: 02 Title: "Pending" Responses for the Constrained Application Protocol (CoAP) Document date: 2018-02-26 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-hartke-core-pending-02.txt Status: https://datatracker.ietf.org/doc/draft-hartke-core-pending/ Htmlized: https://tools.ietf.org/html/draft-hartke-core-pending-02 Htmlized: https://datatracker.ietf.org/doc/html/draft-hartke-core-pending-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-hartke-core-pending-02 Abstract: This document proposes a new type of response for the Constrained Application Protocol (CoAP) called a "Pending" response. A CoAP server can use a Pending response to indicate that it has accepted a request but has not yet started processing it or that processing the request will take longer than a client is typically willing to wait for a response. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- [core] Fwd: New Version Notification for draft-ha… peter van der Stok
- Re: [core] Fwd: New Version Notification for draf… Carsten Bormann
- Re: [core] Fwd: New Version Notification for draf… Klaus Hartke