Opened 9 years ago

Closed 9 years ago

#333 closed protocol defect (fixed)

Consistent sequence numbers across requests

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


observe-09 requires:

The client MUST specify a token in its GET request that is currently
not in use for the client/server pair, as the sequence numbers
provide an order only among the notifications resulting from the same

This requirement is not implementable if we assume that a client can reboot anytime and thereby forget which tokens were in use up to this point. If the client is still interested in a resource after a reboot, it will register again, potentially reusing a token that is still in use by the server.

The problem can be solved by requiring that sequence numbers do not only provide an order among the notifications resulting from one request, but among all notifications resulting from all requests of one client for the same resource.

Of course, a server can reboot anytime and thereby forget the state of its sequence number generator. When a server cannot provide consistent sequence numbers between two notifications, these notifications need to be at least 128 seconds apart.

Change History (1)

comment:1 Changed 9 years ago by hartke@…

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

Done in -10.

Note: See TracTickets for help on using tickets.