Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#207 closed editorial (fixed)

Add advice on default values for critical options

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:


Klaus Hartke points out that the guidelines for registration of new options could include a check for an essential property of any default values for new critical options.

in 11.2, a change for the registration information could be:

o The default value, if any.


o The default value, if any. For a critical option with a default value, a discussion how the default value enables processing by implementations not implementing the critical option (Section 5.4.3).

In 5.4.3, add at the end:

Where a critical option has a default value, this is chosen in such a way that the absence of the option in a message can be processed properly both by implementations unaware of the critical option and by implementations that interpret this absence as the presence of the default value for the option.

Some wordsmithing may be required.

Change History (2)

comment:1 Changed 10 years ago by zach@…

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

Change made in r686.

comment:2 Changed 10 years ago by hartke@…

  • Version set to coap-09
Note: See TracTickets for help on using tickets.