Constrained Application Protocol (CoAP) over Bundle Protocol (BP)
draft-gomez-core-coap-bp-04
| Document | Type |
Replaced Internet-Draft
(core WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Carles Gomez , Anna Calveras | ||
| Last updated | 2025-08-29 (Latest revision 2025-07-02) | ||
| Replaced by | draft-ietf-core-coap-bp | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-core-coap-bp | |
| Consensus boilerplate | Unknown | ||
| 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
The Bundle Protocol (BP) was designed to enable end-to-end communication in challenged networks. The Constrained Application Protocol (CoAP), which was designed for constrained-node networks, may be a suitable application-layer protocol for the scenarios where BP is used. This document specifies how CoAP is carried over BP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)