CoRE Resource Directory
draft-ietf-core-resource-directory-17

Document Type Active Internet-Draft (core WG)
Last updated 2018-10-22
Replaces draft-shelby-core-resource-directory
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Mar 2018 - CoRE Resource Direct... )
Document shepherd Jaime Jimenez
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alexey Melnikov
Send notices to "Jaime Jimenez" <jaime.jimenez@ericsson.com>
CoRE                                                           Z. Shelby
Internet-Draft                                                       ARM
Intended status: Standards Track                               M. Koster
Expires: April 26, 2019                                      SmartThings
                                                              C. Bormann
                                                 Universitaet Bremen TZI
                                                         P. van der Stok
                                                              consultant
                                                         C. Amsuess, Ed.
                                                        October 23, 2018

                        CoRE Resource Directory
                 draft-ietf-core-resource-directory-17

Abstract

   In many M2M applications, direct discovery of resources is not
   practical due to sleeping nodes, disperse networks, or networks where
   multicast traffic is inefficient.  These problems can be solved by
   employing an entity called a Resource Directory (RD), which hosts
   registrations of resources held on other servers, allowing lookups to
   be performed for those resources.  This document specifies the web
   interfaces that a Resource Directory supports for web servers to
   discover the RD and to register, maintain, lookup and remove resource
   descriptions.  Furthermore, new link attributes useful in conjunction
   with an RD are defined.

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 April 26, 2019.

Shelby, et al.           Expires April 26, 2019                 [Page 1]
Internet-Draft           CoRE Resource Directory            October 2018

Copyright Notice

   Copyright (c) 2018 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Architecture and Use Cases  . . . . . . . . . . . . . . . . .   6
     3.1.  Principles  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  RD Content Model  . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Use Case: Cellular M2M  . . . . . . . . . . . . . . . . .  12
     3.5.  Use Case: Home and Building Automation  . . . . . . . . .  13
     3.6.  Use Case: Link Catalogues . . . . . . . . . . . . . . . .  13
   4.  Finding a Resource Directory  . . . . . . . . . . . . . . . .  14
     4.1.  Resource Directory Address Option (RDAO)  . . . . . . . .  15
   5.  Resource Directory  . . . . . . . . . . . . . . . . . . . . .  17
     5.1.  Payload Content Formats . . . . . . . . . . . . . . . . .  17
     5.2.  URI Discovery . . . . . . . . . . . . . . . . . . . . . .  17
     5.3.  Registration  . . . . . . . . . . . . . . . . . . . . . .  20
       5.3.1.  Simple Registration . . . . . . . . . . . . . . . . .  25
       5.3.2.  Third-party registration  . . . . . . . . . . . . . .  27
       5.3.3.  RD-Groups . . . . . . . . . . . . . . . . . . . . . .  28
   6.  RD Lookup . . . . . . . . . . . . . . . . . . . . . . . . . .  29
     6.1.  Resource lookup . . . . . . . . . . . . . . . . . . . . .  29
     6.2.  Lookup filtering  . . . . . . . . . . . . . . . . . . . .  30
     6.3.  Resource lookup examples  . . . . . . . . . . . . . . . .  32
   7.  Security policies . . . . . . . . . . . . . . . . . . . . . .  35
     7.1.  Secure RD discovery . . . . . . . . . . . . . . . . . . .  36
     7.2.  Secure RD filtering . . . . . . . . . . . . . . . . . . .  37
     7.3.  Secure endpoint Name assignment . . . . . . . . . . . . .  37
Show full document text