[core] Fw: New Version Notification for draft-tcs-coap-no-response-option-15.txt

[Abhijan Bhattacharyya <[e-mail]>]

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: [e-mail]
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:   [e-mail]
To:     "Soma Bandyopadhyay" <[e-mail]>, "Abhijan 
Bhattacharyya" <[e-mail]>, "Arpan Pal" 
<[e-mail]>, "Tulika Bose" <[e-mail]>
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