[core] Fwd: New Version Notification for draft-hartke-coap-observe-00

[Carsten Bormann <[e-mail]>]

Klaus Hartke and I have just submitted a draft on issue #1/#2.

http://datatracker.ietf.org/doc/draft-hartke-coap-observe/

We believe it is not meaningful to discuss requirements without an
idea to what kind of design they might lead, so we provided a design
as well.  In effect, we tried to liberate ourselves from the
publish/subscribe/notify terminology and went back to the actual base
requirement behind charter objective 2: being able to observe a resource.

We tried to stick to the REST model as much as possible, but we extend
the existing HTTP methods by a method for explicitly *observing* a
resource.  This does not necessarily require the resource to implement
new methods, only the server offering its representations has to.
There is some new state, but it is not much different from the
conversation state that we already have in HTTP.

Enjoy!

Gruesse, Klaus and Carsten


Begin forwarded message:

> From: IETF I-D Submission Tool <[e-mail]>
> Date: June 22, 2010 22:35:27 +0200
> To: [e-mail]
> Cc: [e-mail]
> Subject: New Version Notification for draft-hartke-coap-observe-00 
> 
> 
> A new version of I-D, draft-hartke-coap-observe-00.txt has been successfully submitted by Carsten Bormann and posted to the IETF repository.
> 
> Filename:	 draft-hartke-coap-observe
> Revision:	 00
> Title:		 Observing Resources in CoAP
> Creation_date:	 2010-06-21
> WG ID:		 Independent Submission
> Number_of_pages: 23
> 
> Abstract:
> The state of a resource can change over time.  We want to give
> clients of the CoRE WG CoAP protocol the ability to observe this
> change.  This short I-D provides an example design for such an
> addition to CoAP, in order to be able to discuss the design
> alternatives in specific terms.
> 
> 
> 
> The IETF Secretariat.
>