Using CoAP with IPsec
draft-bormann-core-ipsec-for-coap-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Carsten Bormann | ||
Last updated | 2013-06-09 (Latest revision 2012-12-06) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
CoAP is a RESTful transfer protocol for constrained nodes and networks. Security for the protocol can be supplied in a number of ways. The mandatory-to-implement security mode for CoAP makes use of DTLS. Other applications may want to use IPsec. This document will discuss considerations for the use of IPsec with CoAP. It will be advanced on a timescale separate from the main CoAP specification, as most experience in securing CoAP so far has been made with DTLS. The current version of this specification is a placeholder, built out of text extracted from draft-ietf-core-coap-12. It is meant to pick up http://trac.tools.ietf.org/wg/core/trac/ticket/262 and provide a home for its considerations. It might be merged with other documents later.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)