Opened 10 years ago

Closed 10 years ago

#236 closed other technical (fixed)

Clarify the semantics of the "obs" link target attribute

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:


Klaus Hartke notes (msg03053):

Section 7

Do we really need the "obs" link attribute?


As the second paragraph of section 7, insert:

The presence of this attribute can for example be used to indicate,
via a graphical representation in a user interface, that this resource
is changing its value and useful for monitoring.

Note that the presence of this attribute is not a promise that the
Observe Option can actually be used to perform this observation. A
client may need to resort to polling the resource if the Observe
Option is not returned in the reply to the GET request.

[This attribute might as well be defined in -core or in -link-format.
We are keeping it here to keep it simple. But see also discussion in]

Change History (1)

comment:1 Changed 10 years ago by hartke@…

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

Fixed in [974]:

Closes #236: Done in observe-07

Note: See TracTickets for help on using tickets.