Opened 10 years ago

Closed 10 years ago

#227 closed protocol enhancement (wontfix)

Make aborting the previous transaction optional

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


Section 4.5 requires a server implementation to stop an old transmission and carry the retransmit count over to the new transaction.

Cullen Jennings notes (msg03073h) that this is hard to implement in some cases and a minor optimization for an edge case.

He proposes that a server implementation can choose if it wants to abort the previous transaction or run two transactions in parallel.

  • If it aborts the previous transaction, then it needs to copy over the retransmit state to the new transaction.
  • If it doesn't cancel the old transaction, the device still finds out the device is gone.

Change History (1)

comment:1 Changed 10 years ago by hartke@…

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

Congestion control limits the number of parallel transactions (typically to 1). When the maximum number of parallel transactions has been reached and the resource changes its state, then the server MUST NOT start yet another transaction, but wait for the running attempts to fail or complete first. For the best-effort and eventual-consistency goals, the server also SHOULD NOT try to get an outdated representation to the client anyway. So, besides the issue raised in ticket #242 and the ongoing congestion control work, I think this ticket can be closed.

Note: See TracTickets for help on using tickets.