[core] Fw: New Version Notification for draft-tcs-coap-no-response-option-15.txt
Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com> Mon, 04 April 2016 11:56 UTC
Return-Path: <prvs=895b499ec=abhijan.bhattacharyya@tcs.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 A57AE12D5B4 for <core@ietfa.amsl.com>; Mon, 4 Apr 2016 04:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.046
X-Spam-Level:
X-Spam-Status: No, score=-4.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DRUGS_MUSCLE=0.164, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Xv3bBaf6fH29 for <core@ietfa.amsl.com>; Mon, 4 Apr 2016 04:56:54 -0700 (PDT)
Received: from inkolg01.tcs.com (inkolg01.tcs.com [121.241.215.10]) by ietfa.amsl.com (Postfix) with ESMTP id 733D812D563 for <core@ietf.org>; Mon, 4 Apr 2016 04:56:51 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2DOAQAgVgJX/wQXEqxdhAp9h2GzRgENgXIXAQuFaoFrFAEBAQEBAQGBDIRBAQEBex0HBgQDAQIoTQcCGQgbiBqqLQEBAZIZKoR3Z4UMhCc4DYIbS4JDBY1Nc4lBgVKEIYl9ToN/iFqPGh4BAYQxZAGIJQEBAQ
X-IPAS-Result: A2DOAQAgVgJX/wQXEqxdhAp9h2GzRgENgXIXAQuFaoFrFAEBAQEBAQGBDIRBAQEBex0HBgQDAQIoTQcCGQgbiBqqLQEBAZIZKoR3Z4UMhCc4DYIbS4JDBY1Nc4lBgVKEIYl9ToN/iFqPGh4BAYQxZAGIJQEBAQ
X-IronPort-AV: E=Sophos;i="5.24,440,1454956200"; d="scan'208";a="70754493"
To: core@ietf.org
MIME-Version: 1.0
X-KeepSent: 0DBE139D:396C10DC-65257F8B:004137DA; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0 March 08, 2013
Message-ID: <OF0DBE139D.396C10DC-ON65257F8B.004137DA-65257F8B.00419458@tcs.com>
From: Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com>
Date: Mon, 04 Apr 2016 17:26:19 +0530
X-MIMETrack: Serialize by Router on INKOLM102/TCS(Release 9.0.1FP4HF926 | March 31, 2016) at 04/04/2016 17:26:21, Serialize complete at 04/04/2016 17:26:21
Content-Type: multipart/alternative; boundary="=_alternative 0041945865257F8B_="
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/gBMOURg_v4jSXJI89J7wbBlM_Tk>
Subject: [core] Fw: New Version Notification for draft-tcs-coap-no-response-option-15.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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, 04 Apr 2016 11:56:56 -0000
Dear list, A new version of the No-Response draft has been submitted addressing the final review comments received through the RFC editor's desk. This document is now in RFC editor's queue through the individual submission track. Thanks to Matthias for the review comments. Regards Abhijan Bhattacharyya Associate Consultant Scientist, Innovation Lab, Kolkata, India Tata Consultancy Services Mailto: abhijan.bhattacharyya@tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ ----- Forwarded by Abhijan Bhattacharyya/KOL/TCS on 04/04/2016 05:22 PM ----- From: internet-drafts@ietf.org To: "Soma Bandyopadhyay" <soma.bandyopadhyay@tcs.com>, "Abhijan Bhattacharyya" <abhijan.bhattacharyya@tcs.com>, "Arpan Pal" <arpan.pal@tcs.com>, "Tulika Bose" <tulika.bose@tcs.com> Date: 04/04/2016 05:18 PM Subject: New Version Notification for draft-tcs-coap-no-response-option-15.txt A new version of I-D, draft-tcs-coap-no-response-option-15.txt has been successfully submitted by Abhijan Bhattacharyya and posted to the IETF repository. Name: draft-tcs-coap-no-response-option Revision: 15 Title: CoAP option for no server-response Document date: 2016-04-04 Group: Individual Submission Pages: 18 URL: https://www.ietf.org/internet-drafts/draft-tcs-coap-no-response-option-15.txt Status: https://datatracker.ietf.org/doc/draft-tcs-coap-no-response-option/ Htmlized: https://tools.ietf.org/html/draft-tcs-coap-no-response-option-15 Diff: https://www.ietf.org/rfcdiff?url2=draft-tcs-coap-no-response-option-15 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. 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 =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
- [core] Fw: New Version Notification for draft-tcs… Abhijan Bhattacharyya
- Re: [core] Fw: New Version Notification for draft… Klaus Hartke
- Re: [core] Fw: New Version Notification for draft… Abhijan Bhattacharyya
- Re: [core] Fw: New Version Notification for draft… Klaus Hartke