CoAP Application version of Resource Directory
draft-schaad-core-reef-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-03
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                                          J. Schaad
Internet-Draft                                            August Cellars
Intended status: Experimental                             3 January 2020
Expires: 6 July 2020

             CoAP Application version of Resource Directory
                       draft-schaad-core-reef-00

Abstract

   This is a draft of what I think a CoRE Application should look like.

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 6 July 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
   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.

Schaad                     Expires 6 July 2020                  [Page 1]
Internet-DrafCoAP Application version of Resource Directory January 2020

Table of Contents

   1.  Preamble  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Vocabulary  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Containers  . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Leafs . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Resource Interfaces . . . . . . . . . . . . . . . . . . . . .   5
   5.  Model Objects . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Interop Items . . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  Retrieve Resource Directory Information . . . . . . . . .   7
     6.3.  Registering Endpoints . . . . . . . . . . . . . . . . . .   9
     6.4.  Query Endpoints . . . . . . . . . . . . . . . . . . . . .  13
     6.5.  Query Resources . . . . . . . . . . . . . . . . . . . . .  13
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  15
   Appendix A.  Missing CoRAL things . . . . . . . . . . . . . . . .  16
     A.1.  Rules for doing a FETCH . . . . . . . . . . . . . . . . .  16
     A.2.  Rules for doing a PATCH . . . . . . . . . . . . . . . . .  16
   Appendix B.  Authorization Vocabulary . . . . . . . . . . . . . .  16
     B.1.  Containers  . . . . . . . . . . . . . . . . . . . . . . .  16
     B.2.  Leafs . . . . . . . . . . . . . . . . . . . . . . . . . .  16
     B.3.  ACE Authority Type  . . . . . . . . . . . . . . . . . . .  17
     B.4.  X.509 Authority Type  . . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Preamble

   This document explores how a CoRE Resource Directory
   [I-D.ietf-core-resource-directory] might look if based on [CoRAL].
   This document is not currently intended as something to be
   standardized at this time.

2.  Introduction

   Refer to the introduction of [I-D.ietf-core-resource-directory].
   Concise Binary Object Representation (CBOR) [CBOR] is a compact self-
   describing binary encoding formation that is starting to be used in
   many different applications.  One of the primary uses of CBOR is in
   the Internet of Things where the constrained nature means that having
   minimal size of encodings becomes very important.  The use of the
   Cryptographic Message System (CMS) [CMS] is still one of the most
   common method for providing message-based security, although in many
   cases the CBOR Object Signing and Encryption (COSE) [COSE] message-
   based security system is starting to be used.  Given that CBOR is
   going to be transported using CMS, it makes sense to define CMS

Schaad                     Expires 6 July 2020                  [Page 2]
Internet-DrafCoAP Application version of Resource Directory January 2020
Show full document text