Opened 11 years ago

Last modified 10 years ago

#230 closed protocol defect

Multiple Location options need to be processed as a unit — at Version 1

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

Description (last modified by cabo@…)

Before the location in a response was split into multiple options, there was only one Location Option which was defined to be "elective". This worked well, because a client that doesn't recognize the option could ignore it without harm.

However, with the Location-Path and Location-Query options (and possible future Location-Host and Location-Port options), the client must either understand or ignore all of them. Expressing such interdependencies is currently not possible in CoAP.

->

Solution to be defined. Focus on the problem right now.
(One solution would be to use an envelope "Location" option to contain all Location-* options, so they are ignored or used as a whole.
Reserve space in the envelope option so possible future Location-Host and Location-Port options appear before Location-Path and Location-Query options in a message.)

Change History (1)

comment:1 Changed 11 years ago by cabo@…

  • Description modified (diff)
  • Summary changed from Put Location options in an envelope to Multiple Location options need to be processed as a unit
Note: See TracTickets for help on using tickets.