Scenarios for CoAP on non-UDP Transports
draft-becker-core-transport-scenarios-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Markus Becker , Thomas Poetsch , Koojana Kuladinithi | ||
| Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
| 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
Several drafts in the CoRE WG are discussing the usage of CoAP on non-UDP/IP transports already. There are various use cases for non- UDP/IP transports. In order to structure the discussion, this draft introduces new terminology and transport scenarios.
Authors
Markus Becker
Thomas Poetsch
Koojana Kuladinithi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)