Opened 10 years ago

Closed 10 years ago

#220 closed protocol enhancement (wontfix)

Should observe support time series data?

Reported by: cabo@… Owned by: draft-ietf-core-observe@…
Priority: minor Milestone: post-WGLC-1
Component: observe Version: observe-05
Severity: In WG Last Call Keywords:

Description (last modified by cabo@…)

Jeroen Hoebeke notes (msg02900):

There is a difference between the following:

  1. informing a client about every change of the state of a resource: this is what one would expect when just reading the abstract of the draft
  1. delivering a client an always fresh representation of a resource (even if the resource did not change): this is what the draft actually implements through the max-age option

Having both makes a lot of sense. Draft observe could fulfill both purposes (and would be a good place to do so). If draft observe is only about 1) and the abstract clarifies this, an extension to observe (introducing pledge) for case 2) seems an obvious step. Personally, I am in favor of having this in a single draft.


Observe currently is about 2 (eventual consistency). What kinds of mechanisms would we need to add to support time series data as in 1? Is the resulting set of changes a desirable addition?

(see also #219)

Change History (2)

comment:1 Changed 10 years ago by cabo@…

  • Description modified (diff)
  • Summary changed from Should observer support time series data? to Should observe support time series data?

comment:2 Changed 10 years ago by hartke@…

  • Resolution set to wontfix
  • Status changed from new to closed

In the interim meeting, Jeroen clarified that this ticket is misinterpreting his comment and that the item raised is really about notifications with a Max-Age of zero which will be resolved in ticket #204.

Note: See TracTickets for help on using tickets.