Opened 10 years ago

Closed 10 years ago

#214 closed protocol enhancement (fixed)

Adopt vendor-defined option into core-coap

Reported by: cabo@… 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

Alper Yegin (http://www.ietf.org/mail-archive/web/core/current/msg02958.html):

I recommend we migrate Section 3. Vendor-defined Options of coap-misc I-D into core-coap I-D.


This would then become 5.10.11.

Change History (6)

comment:1 Changed 10 years ago by fluffy@…

Carsten proposal: reserved a option number that first 2 bytes of data is an code point that is allocated by IANA. reserver another options for 3 bytes, 1 byte, etc. Need two sets of these numbers - one for critical and one for elective.

Action: Carsten will write up in COAP misc.

comment:2 Changed 10 years ago by hartke@…

We may need vendor options for all meaningful combinations of "(not) safe to be forwarded without knowing it" and "(not) part of the cache key".

comment:3 Changed 10 years ago by cabo@…

Text in section 3 of coap-misc-18, to be moved over to core-coap.

comment:4 Changed 10 years ago by zach@…

Consensus from the Vancouver WG meeting was:

  • Adopt the Jump feature from Section 3.2.1 of coap-misc-20
  • Adopt the new IANA policy from Section 3.2.4 however 2048 -> should also go through a light designated expert review to make sure the option is categorized correctly (critical, elective, safe, cache key)
  • Remove the current Fencepost mechanism from the draft

comment:5 Changed 10 years ago by zach@…

The "Option Jump" feature has now been added, and "Fenceposting" removed in coap-12.

comment:6 Changed 10 years ago by zach@…

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