A Data-centric Deployment Option for CoAP
draft-gundogan-core-icncoap-00
TODO Working Group C. Gündoğan
Internet-Draft HAW Hamburg
Intended status: Informational C. Amsüss
Expires: 26 August 2021
TC. Schmidt
HAW Hamburg
M. Waehlisch
link-lab & FU Berlin
22 February 2021
A Data-centric Deployment Option for CoAP
draft-gundogan-core-icncoap-00
Abstract
The information-centric networking (ICN) paradigm offers replication
of autonomously verifiable content throughout a network, in which
content is bound to names instead of hosts. This has proven
beneficial in particular for the constrained IoT. Several
approaches, the most prominent of which being Content-Centric
Networking (CCNx) and Named-Data Networking (NDN), propose access to
named content directly on the network layer. Independently, the CoRe
WG developed mechanisms that support autonomous content processing,
on-path caching, and content object security using CoAP proxies and
OSCORE.
This document describes a data-centric deployment option using
standard CoAP features to replicate information-centric properties
and benefits to the host-centric IoT world.
Discussion Venues
This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the Constrained RESTful
Environments Working Group mailing list (core@ietf.org), which is
archived at https://mailarchive.ietf.org/arch/browse/core/.
Source for this draft and an issue tracker can be found at
https://github.com/inetrg/draft-core-icncoap.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Gündoğan, et al. Expires 26 August 2021 [Page 1]
Internet-Draft Data-centric CoAP February 2021
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 26 August 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Data-centric Deployment Option for CoAP . . . . . . . . . . . 3
3.1. Stateful Forwarding . . . . . . . . . . . . . . . . . . . 3
3.2. Content Caching . . . . . . . . . . . . . . . . . . . . . 4
3.3. Corrective Actions . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
Gündoğan, et al. Expires 26 August 2021 [Page 2]
Internet-Draft Data-centric CoAP February 2021
1. Introduction
Information-Centric Networking (ICN) introduced the idea to turn
named content objects into first class citizens of the Internet
ecosystem. This paradigm gave rise to (i) a decoupling of content
from hosts and the ability of ubiquitous content caching without
content delivery networks (CDNs), and (ii) serverless routing on
Show full document text