I-D Action: draft-tcs-coap-no-response-option-15.txt
internet-drafts@ietf.org Mon, 04 April 2016 11:46 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 05FDD12D5B1 for <i-d-announce@ietf.org>; Mon, 4 Apr 2016 04:46:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-tcs-coap-no-response-option-15.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.18.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160404114640.15606.65247.idtracker@ietfa.amsl.com>
Date: Mon, 04 Apr 2016 04:46:40 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/i-d-announce/My-_XpNSoxQis6IjAJmVSpw61fk>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Apr 2016 11:46:40 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : CoAP option for no server-response Authors : Abhijan Bhattacharyya Soma Bandyopadhyay Arpan Pal Tulika Bose Filename : draft-tcs-coap-no-response-option-15.txt Pages : 18 Date : 2016-04-04 Abstract: There can be M2M scenarios where responses from a server against requests from client are redundant. This kind of open-loop exchange (with no response path from the server to the client) may be desired to minimize resource consumption in constrained systems while updating a bulk of resources simultaneously, or updating a resource with a very high frequency. CoAP already provides Non-confirmable (NON) messages that are not acknowledged by the recipient. However, the request/response semantics still require the server to respond with a status code indicating "the result of the attempt to understand and satisfy the request". This specification introduces a CoAP option called 'No-Response'. Using this option the client can explicitly tell the server to suppress all responses against the particular request. This option also provides granular control to enable suppression of a particular class of response or a combination of response-classes. This option may be effective for both unicast and multicast requests. This document also discusses a few exemplary applications which benefit from this option. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-tcs-coap-no-response-option/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-tcs-coap-no-response-option-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-tcs-coap-no-response-option-15 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- I-D Action: draft-tcs-coap-no-response-option-15.… internet-drafts