Opened 11 years ago

Closed 11 years ago

#184 closed editorial (fixed)

Add implementation note to 3.5 about careless GETs

Reported by: cabo@… Owned by: draft-ietf-core-observe@…
Priority: minor Milestone:
Component: observe Version:
Severity: Active WG Document Keywords:
Cc:

Description

When an implementation is careless, it might tear down an observation relationship carelessly by carelessly sending a GET without Observe on the same transport address on which it has the observation relationship. This does not occur in client that implement caching with complete mediation, as any industrial-strength implementation is likely to do. It might occur in more careless environments, such as shell scripts.

So maybe we should add some editorial explanation that clients that (1) want to keep up observation relationships and (2) still send GETs carelessly to the same resource for implementation expediency should (3) not do the latter from the same source address/port their observation relationships run on.

While it could be argued the same kind of implementation note would need to be added about other state attached to a transport address pair, such as MID or Token use, these can be partitioned off in a more obvious way (e.g., use odd MIDs and Tokens for careless requests).

Change History (2)

comment:1 Changed 11 years ago by hartke@…

At the end of section 3.5, add:

Implementation note: A client that does not mediate all its requests through its cache might inadvertantly cancel an observation relationship by sending an unrelated GET to the same resource. To avoid this, without incurring a need for synchronization, such clients can use a different source transport address for these unrelated GET requests.

comment:2 Changed 11 years ago by hartke@…

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

Done.

Note: See TracTickets for help on using tickets.