search

core-wg / corrclar

Corrections and Clarifications to CoRE standards
Other
0 stars 0 forks source link

Processing Location-* options when unrecognized #3

Open ektrah opened 5 years ago

ektrah commented 5 years ago

Errata ID: 4949 Type: Technical Reported By: Klaus Hartke Date Reported: 2017-02-22

Section 5.10.7 says/should say:

 If any
 of these reserved option numbers occurs in addition to Location-Path
-and/or Location-Query and are not supported, then a 4.02 (Bad Option)
-error MUST be returned.
+and/or Location-Query and are not supported, then the response MUST
+be rejected (Sections 4.2 and 4.3).

The Location-* options are used in responses. A client cannot return a 4.02 (Bad Option) response in reply to a response. The correct behavior is to reject the response.

cabo commented 5 years ago

There cannot be a response to a response, so sending 4.02 does not work.
Note that 4.2 of 7252 says "Rejecting an Acknowledgement or Reset message (including the case where the Acknowledgement carries a request or a code with a reserved class, or the Reset message is not Empty) is effected by silently ignoring it." So the approach would work, and we should accept the errata report and include the correction in the document.

ektrah commented 5 years ago

Cf. Section 5.4.1:

   o  Unrecognized options of class "critical" that occur in a
      Confirmable response, or piggybacked in an Acknowledgement, MUST
      cause the response to be rejected (Section 4.2).

   o  Unrecognized options of class "critical" that occur in a Non-
      confirmable message MUST cause the message to be rejected
      (Section 4.3).