Opened 10 years ago

Closed 10 years ago

#262 closed other technical (fixed)

Split out IPsec details into a separate draft

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

Description

Cullen Jennings notes (msg03072c):

Section 10.2

I'm wondering what parts of text around IPSec really need to be in the draft? I'm having a hard time finding anywhere where it has any normative impact.

(This is now section 9.2 in coap-12.)

Proposal:

From the point of view of CoAP, there is indeed little normative text that interfaces to IPsec at this point.
There is some work to do, e.g. msg03024, and there is little implementation experience.
The remaining issues might receive better attention when they are exposed in their own draft instead of buried in the main CoAP specification.

Change History (1)

comment:1 Changed 10 years ago by cabo@…

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

Fixed in [1099]:

Close #262.
Close #247.
Close #260 (for now).

Note: See TracTickets for help on using tickets.