CoRE Working Group -- Overview
draft-bormann-core-overview-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-23
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Informational                              J.J. Jimenez
Expires: 24 September 2020                                      Ericsson
                                                           23 March 2020

                     CoRE Working Group -- Overview
                     draft-bormann-core-overview-00

Abstract

   The IETF "Constrained RESTful Environments" (CoRE) Working Group
   standardizes application layer protocols that can be used by
   resource-constrained devices, as can be found in the Internet of
   Things (IoT).  It is part of a cluster of about a dozen IETF WGs
   defining specifications for these environments.

   This short document provides an overview of the activies of the CoRE
   WG as of end of March, 2020.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 24 September 2020.

Copyright Notice

   Copyright (c) 2020 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

Bormann & Jimenez       Expires 24 September 2020               [Page 1]
Internet-Draft       CoRE Working Group -- Overview           March 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Main Specification  . . . . . . . . . . . . . . . . . . . . .   2
   3.  Security  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Operations and Management . . . . . . . . . . . . . . . . . .   3
   5.  Data Formats  . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Further Information . . . . . . . . . . . . . . . . . . . . .   4
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   4
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The IETF "Constrained RESTful Environments" (CoRE) Working Group
   standardizes application layer protocols that can be used by
   resource-constrained devices, as can be found in the Internet of
   Things (IoT).  It is part of a cluster of about a dozen IETF WGs that
   define networking (e.g., 6Lo), routing (e.g., ROLL), and security
   (e.g., ACE, LAKE, SUIT) for these environments.  This cluster has
   been growing since 2005; ten years ago, on 2010-03-09, CoRE was added
   to it.

2.  Main Specification

   The main specification of CoRE is the Constrained Application
   Protocol (CoAP) [RFC7252].  CoAP is for applications including
   constrained devices what HTTP is for general purpose applications.
   By using UDP as the transport protocol as opposed to HTTP's use of
   TCP, and by removing much of the baggage of of HTTP, CoAP can be run
   on quite simple platforms and with very little power use.  Both
   protocols share the Representational State Transfer (REST)
   architecture, the same set of verbs (GET, PUT, POST, DELETE), and
   quite similar semantics.

   Since CoAP's approval in 2013, further specifications have been added
   to support the Observe pattern of change notifications from a server
   (low-complexity server-push) [RFC7641], to support larger transfers
   [RFC7959], to add verbs (FETCH, PATCH, and idempotent iPATCH
   [RFC8132]), and to enable the use of CoAP over TCP [RFC8323].
   [RFC8768] recently added a way to detect and mitigate loops in a
   proxy configuration, motivated by the requirements of the Distributed
   Denial-of-Service Open Threat Signaling (DOTS
   [I-D.ietf-dots-signal-channel]) specification.

Bormann & Jimenez       Expires 24 September 2020               [Page 2]
Internet-Draft       CoRE Working Group -- Overview           March 2020

Show full document text