CoAP Requirements and Features
draft-shelby-core-coap-req-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian Frank , Don Sturek , Michael Stuber , Richard Kelsey , Zach Shelby | ||
| Last updated | 2011-05-02 | ||
| 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
This document considers the requirements for the design of the Constrained Application Protocol (CoAP). The goal of the document is to provide a basis for protocol design and related discussion.
Authors
Brian Frank
Don Sturek
Michael Stuber
Richard Kelsey
Zach Shelby
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)