Re: [core] draft-tcs-coap-no-response-option-07 : Call for WG adoption

"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Wed, 06 August 2014 14:38 UTC

Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CFB184.1FED70B0"
Date: Wed, 06 Aug 2014 10:38:43 -0400
Message-ID: <D60519DB022FFA48974A25955FFEC08C05DC01F8@SAM.InterDigital.com>
In-Reply-To: <OF3540B968.49C27697-ON65257D2C.00396B83-65257D2C.0039E65B@tcs.com>
Thread-Topic: [core] draft-tcs-coap-no-response-option-07 : Call for WG adoption
Thread-Index: Ac+xYb0VX+BB1rfERx6J3uzzSFDW3gAIjiyg
References: <20140806101420.2243.22999.idtracker@ietfa.amsl.com> <OF3540B968.49C27697-ON65257D2C.00396B83-65257D2C.0039E65B@tcs.com>
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com>, core@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/core/HrVyMJjJw9tnPmgLzLN0ZKH119I
Cc: Arpan Pal <arpan.pal@tcs.com>
Subject: Re: [core] draft-tcs-coap-no-response-option-07 : Call for WG adoption
Precedence: list

Hi Abhijan,

 

 

+1

 

As I said in IETF-Toronto, I think that this is a nice value added
feature to have in CoAP.

 

 

Best Regards,

 

 

Akbar

 

From: core [mailto:core-bounces@ietf.org] On Behalf Of Abhijan
Bhattacharyya
Sent: Wednesday, August 06, 2014 6:32 AM
To: core@ietf.org
Cc: Arpan Pal
Subject: [core] draft-tcs-coap-no-response-option-07 : Call for WG
adoption

 

Hi,

We have submitted a new version of the No-Response draft. Several
editorial corrections have been made. The references have been updated
and enhanced. A number for the option has been suggested for IANA
consideration .

As there has been continuity of interest in the mailing list discussions
and also during the last three WG meetings, may we now ask for the
opinion of the Working Group on adoption of the draft please. 


Regards
Abhijan Bhattacharyya
Associate Consultant
Scientist, Innovation Lab, Kolkata, India
Tata Consultancy Services Limited
Mailto: abhijan.bhattacharyya@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________



-----internet-drafts@ietf.org wrote: -----

To: Soma Bandyopadhyay <soma.bandyopadhyay@tcs.com>, "Abhijan
Bhattacharyya" <abhijan.bhattacharyya@tcs.com>, "Arpan Pal"
<arpan.pal@tcs.com>, Arpan Pal <arpan.pal@tcs.com>, "Soma Bandyopadhyay"
<soma.bandyopadhyay@tcs.com>, Abhijan Bhattacharyya
<abhijan.bhattacharyya@tcs.com>
From: internet-drafts@ietf.org
Date: 08/06/2014 03:44PM
Subject: New Version Notification for
draft-tcs-coap-no-response-option-07.txt

A new version of I-D, draft-tcs-coap-no-response-option-07.txt
has been successfully submitted by Abhijan Bhattacharyya and posted to
the
IETF repository.

Name: draft-tcs-coap-no-response-option
Revision: 07
Title: CoAP option for no server-response
Document date: 2014-08-05
Group: Individual Submission
Pages: 18
URL:
http://www.ietf.org/internet-drafts/draft-tcs-coap-no-response-option-07
.txt
Status:
https://datatracker.ietf.org/doc/draft-tcs-coap-no-response-option/
Htmlized:
http://tools.ietf.org/html/draft-tcs-coap-no-response-option-07
Diff:
http://www.ietf.org/rfcdiff?url2=draft-tcs-coap-no-response-option-07

Abstract:
   There can be typical M2M scenarios where responses from the data
   sink to the data source against request from the source might be
   considered redundant. This kind of open-loop exchange (with no
   reverse path from the sink to the source) may be desired while
   updating resources in constrained systems looking for maximized
   throughput with minimized resource consumption. CoAP already
   provides a non-confirmable (NON) mode of exchange where the
   receiving end-point does not respond with ACK. However, the
   receiving end-point responds the sender with a status code
   indicating "the result of the attempt to understand and satisfy the
   request".

   This draft introduces a header option: 'No-Response' to suppress
   responses from the receiver and discusses exemplary use cases which
   motivated this proposition based on real experience. This option
   also provides granularity by allowing suppression of a typical class
   or a combination of classes of responses. This option may be
   effective for both unicast and multicast scenarios.

 



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] draft-tcs-coap-no-response-option-07 : Cal… Abhijan Bhattacharyya
Re: [core] draft-tcs-coap-no-response-option-07 :… Rahman, Akbar
Re: [core] draft-tcs-coap-no-response-option-07 :… Abhijan Bhattacharyya
Re: [core] draft-tcs-coap-no-response-option-07 :… Likepeng
Re: [core] draft-tcs-coap-no-response-option-07 :… Abhijan Bhattacharyya
Re: [core] draft-tcs-coap-no-response-option-07 :… Abhijan Bhattacharyya