Opened 12 years ago

Closed 12 years ago

#6 closed protocol defect (wontfix)

Date option text needs update

Reported by: zach@… Owned by: Cullen Jennings <fluffy@…>
Priority: trivial Milestone: coap-02
Component: coap Version:
Severity: - Keywords:


Fix the text of the date option and simplify it.

Change History (3)

comment:1 Changed 12 years ago by zach@…

  • Milestone set to coap-01
  • The current text is a bit too complex and has three different lengths. Current text below, how can we make this a single length? Could someone spin some text? Here is the current text:
3.2.5.  Date Option

   The Date Option indicates the creation time and date of a given
   resource representation.  It MAY be used in response and notify
   messages.  The integer value is the number of seconds, after midnight
   UTC, January 1, 1970.  This time format cannot represent time values
   prior to January 1, 1970.  The latest UTC time value that can be
   represented by a 31 bit integer value is 03:14:07 on January 19,
   2038.  Time values beyond 03:14:07 on January 19, 2038, are
   represented by 39 bit integer values which is sufficient to represent
   dates that should be enough for anyone.  For applications requiring
   more accuracy, a 48-bit integer MAY be included representing this
   value in milliseconds instead of seconds.

  • And a more extreme question, do we really need a Date Option at all in CoAP? Most constrained devices do not keep absolute time.

comment:2 Changed 12 years ago by zach@…

  • Milestone changed from coap-01 to coap-02

Moved to coap-misc for now, to be decided on for coap-02.

comment:3 Changed 12 years ago by zach@…

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.