CoRE                                                           Z. Shelby
Internet-Draft                                                       ARM
Intended status: Standards Track                               M. Koster
Expires: January 4, May 3, 2018                                         SmartThings
                                                              C. Bormann
                                                 Universitaet Bremen TZI
                                                         P. van der Stok
                                                              consultant
                                                         C. Amsuess, Ed.
                                             Energy Harvesting Solutions
                                                           July 03,
                                                        October 30, 2017

                        CoRE Resource Directory
                 draft-ietf-core-resource-directory-11
                 draft-ietf-core-resource-directory-12

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
   descriptions 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 in order 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 http://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 January 4, May 3, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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  . . . . . . . . . . . . . . . . .   5
     3.1.  Principles  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   5   6
     3.3.  Content model . . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Use Case: Cellular M2M  . . . . . . . . . . . . . . . . .   7
     3.4.  11
     3.5.  Use Case: Home and Building Automation  . . . . . . . . .   8
     3.5.  12
     3.6.  Use Case: Link Catalogues . . . . . . . . . . . . . . . .   8  12
   4.  Finding a Resource Directory  . . . . . . . . . . . . . . . .   9  13
     4.1.  Resource Directory Address Option (RDAO)  . . . . . . . .  10  14
   5.  Resource Directory  . . . . . . . . . . . . . . . . . . . . .  11  15
     5.1.  Content Formats . . . . . . . . . . . . . . . . . . . . .  12  16
     5.2.  URI Discovery . . . . . . . . . . . . . . . . . . . . . .  12  16
     5.3.  Registration  . . . . . . . . . . . . . . . . . . . . . .  14  18
       5.3.1.  Simple Registration . . . . . . . . . . . . . . . . .  17  22
       5.3.2.  Simple publishing to Resource Directory Server  . . .  18
       5.3.3.  Third-party registration  . . . . . . . . . . . . . .  18
       5.3.4.  Plurality of link references in a Registration  . . .  19  23
     5.4.  Operations on the Registration Resource . . . . . . . . .  19  23
       5.4.1.  Registration Update . . . . . . . . . . . . . . . . .  20  24
       5.4.2.  Registration Removal  . . . . . . . . . . . . . . . .  22  26
       5.4.3.  Read Endpoint Links . . . . . . . . . . . . . . . . .  23  27
       5.4.4.  Update Endpoint Links . . . . . . . . . . . . . . . .  24  28
   6.  RD Groups . . . . . . . . . . . . . . . . . . . . . . . . . .  28  29
     6.1.  Register a Group  . . . . . . . . . . . . . . . . . . . .  28  29
     6.2.  Group Removal . . . . . . . . . . . . . . . . . . . . . .  30  31
   7.  RD Lookup . . . . . . . . . . . . . . . . . . . . . . . . . .  31
     7.1.  Resource lookup . . . . . . . . . . . . . . . . . . . . .  32
     7.2.  Endpoint and group lookup . . . . . . . . . . . . . . . .  33
     7.3.  Lookup filtering  . . . . . . . . . . . . . . . . . . . .  33
     7.4.  Lookup examples . . . . . . . . . . . . . . . . . . . . .  35
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  36  38
     8.1.  Endpoint Identification and Authentication  . . . . . . .  36  38
     8.2.  Access Control  . . . . . . . . . . . . . . . . . . . . .  36  39
     8.3.  Denial of Service Attacks . . . . . . . . . . . . . . . .  37  39
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  37  39
     9.1.  Resource Types  . . . . . . . . . . . . . . . . . . . . .  37  40
     9.2.  IPv6 ND Resource Directory Address Option . . . . . . . .  37  40
     9.3.  RD Parameter Registry . . . . . . . . . . . . . . . . . .  37  40
       9.3.1.  Full description of the "Endpoint Type" Registration
               Parameter . . . . . . . . . . . . . . . . . . . . . .  42
     9.4.  "Endpoint Type" (et=) RD Parameter values . . . . . . . .  42
   10. Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  38  42
     10.1.  Lighting Installation  . . . . . . . . . . . . . . . . .  38  43
       10.1.1.  Installation Characteristics . . . . . . . . . . . .  39  43
       10.1.2.  RD entries . . . . . . . . . . . . . . . . . . . . .  40  44
     10.2.  OMA Lightweight M2M (LWM2M) Example  . . . . . . . . . .  43  47
       10.2.1.  The LWM2M Object Model . . . . . . . . . . . . . . .  43  47
       10.2.2.  LWM2M Register Endpoint  . . . . . . . . . . . . . .  45  49
       10.2.3.  LWM2M Update Endpoint Registration . . . . . . . . .  46  50
       10.2.4.  LWM2M De-Register Endpoint . . . . . . . . . . . . .  47  51
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  47  51
   12. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .  47  51
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  51  56
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  51  56
     13.2.  Informative References . . . . . . . . . . . . . . . . .  52
   Authors' Addresses  57
   Appendix A.  Web links and the Resource Directory . . . . . . . .  58
     A.1.  A simple example  . . . . . . . . . . . . . . .  53

1.  Introduction

   The work on Constrained RESTful . . . . .  58
       A.1.1.  Resolving the URIs  . . . . . . . . . . . . . . . . .  59
       A.1.2.  Interpreting attributes and relations . . . . . . . .  59
     A.2.  A slightly more complex example . . . . . . . . . . . . .  59
     A.3.  Enter the Resource Directory  . . . . . . . . . . . . . .  60
     A.4.  A note on differences between link-format and Link
           headers . . . . . . . . . . . . . . . . . . . . . . . . .  62
   Appendix B.  Syntax examples for Protocol Negotiation . . . . . .  62
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  63

1.  Introduction

   The work on Constrained RESTful Environments (CoRE) aims at realizing
   the REST architecture in a suitable form for the most constrained
   nodes (e.g., 8-bit microcontrollers with limited RAM and ROM) and
   networks (e.g. 6LoWPAN).  CoRE is aimed at machine-to-machine (M2M)
   applications such as smart energy and building automation.

   The discovery of resources offered by a constrained server is very
   important in machine-to-machine applications where there are no
   humans in the loop and static interfaces result in fragility.  The
   discovery of resources provided by an HTTP Web Server is typically
   called Web Linking [RFC5988].  The use of Web Linking for the
   description and discovery of resources hosted by constrained web
   servers is specified by the CoRE Link Format [RFC6690].  However,
   [RFC6690] only describes how to discover resources from the web
   server that hosts them by requesting querying "/.well-known/core".  In many M2M
   scenarios, 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 descriptions 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 in order for web servers to discover the RD and to register,
   maintain, lookup and remove resource descriptions.  Furthermore, new
   link attributes useful in conjunction with a Resource Directory are
   defined.  Although the examples in this document show the use of
   these interfaces with CoAP [RFC7252], they can be applied in an
   equivalent manner to HTTP [RFC7230].

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].  The term "byte" is used in its now customary sense as a
   synonym for "octet".

   This specification requires readers to be familiar with all the terms
   and concepts that are discussed in [RFC5988] and [RFC6690].  Readers
   should also be familiar with the terms and concepts discussed in
   [RFC7252].  To describe the REST interfaces defined in this
   specification, the URI Template format is used [RFC6570].

   This specification makes use of the following additional terminology:

   Resource Directory
      A web entity that stores information about web resources and
      implements the REST interfaces defined in this specification for
      registration and lookup of those resources.

   Domain
      In the context of a Resource Directory, a domain is a logical
      grouping of endpoints.  This specification assumes that the list
      of Domains supported by an RD is pre-configured by that RD.  When
      a domain is exported to DNS, the domain value equates to the DNS
      domain name.

   Group
      In the context of a Resource Directory, a group is a logical
      grouping of endpoints for the purpose of group communications.
      All groups within a domain are unique. have unique names.

   Endpoint
      Endpoint (EP) is a term used to describe a web server or client in
      [RFC7252].  In the context of this specification an endpoint is
      used to describe a web server that registers resources to the
      Resource Directory.  An endpoint is identified by its endpoint
      name, which is included during registration, and is has a unique name
      within the associated domain of the registration.

   Context
      When registering links to a Resource Directory, the
      A Context refers
      to the scheme, address, port, and is a base path for all the links
      registered on behalf of an endpoint, of the general form
      scheme://host:port/path/ where the client may explicitly set the URL that gives scheme and host, and may supply the port and path as optional
      parameters.  When the context (typically)
      authority information about an Endpoint.  The Context of a an
      Endpoint is provided at registration time, and is explicitly set, used by the URI resolution rules in [RFC3986] MUST be applied.
      Resource Directory to resolve relative references inside the
      registration into absolute URIs.

   Directory Resource
      A resource in the Resource Directory (RD) containing registration
      resources.

   Group Resource
      A resource in the RD containing registration resources of the
      Endpoints that form a group.

   Registration Resource
      A resource in the RD that contains information about an Endpoint
      and its links.

   Commissioning Tool
      Commissioning Tool (CT) is a device that assists during the
      installation of the network by assigning values to parameters,
      naming endpoints and groups, or adapting the installation to the
      needs of the applications.

   RDAO
      Resource Directory Address Option.

3.  Architecture and Use Cases

3.1.  Principles

   The Resource Directory is primarily a tool to make discovery
   operations more efficient than querying /.well-known/core on all
   connected device, or across boundaries that would be limiting those
   operations.

   It provides a cache (in the high-level sense, not as defined in
   [RFC7252]/[RFC2616]) of data that could otherwise only be obtained by
   directly querying the /.well-known/core resource on the target
   device, or by accessing those resources with a multicast request.

   From that, it follows that no information should be stored in the
   resource directory that cannot be discovered from querying the
   described device's /.well-known/core resource directly.

   It also follows that data in the resource directory can only be
   provided by the device whose descriptions are cached or a dedicated
   Commissioning Tool (CT).  These CTs are thought to act on behalf
   agents too constrained, or generally unable, to present that
   information themselves.  No other client can modify data in the
   resource directory or even expect those changes to propagate back to
   its source.

3.2.  Architecture

   The resource directory architecture is illustrated in Figure 1.  A
   Resource Directory (RD) is used as a repository for Web Links
   [RFC5988] about resources hosted on other web servers, which are
   called endpoints (EP).  An endpoint is a web server associated with a
   scheme, IP address and port (called Context), port, thus a physical node may host one or
   more endpoints.  The RD implements a set of REST interfaces for
   endpoints to register and maintain sets of Web Links (called resource
   directory registration entries), and for clients to lookup resources
   from the RD or maintain groups.  Endpoints themselves can also act as
   clients.  An RD can be logically segmented by the use of Domains.
   The domain an endpoint is associated with can be defined by the RD or
   configured by an outside entity.  This information hierarchy is shown
   in Figure 2.

   A mechanism to discover an RD using CoRE Link Format [RFC6690] is
   defined.

   Endpoints proactively register and maintain resource directory
   registration entries on the RD, which are soft state and need to be
   periodically refreshed.

   An endpoint is provided with interfaces to register, update and
   remove a resource directory registration entry.  It is also possible
   for an RD to fetch Web Links from endpoints and add them as resource
   directory registration entries.

   At the first registration of a set of entries, a "registration
   resource" is created, the location of which is returned to the
   registering endpoint.  The registering endpoint uses this
   registration resource to manage the contents of the registration
   entry.

   A lookup interface for discovering any of the Web Links held in the
   RD is provided using the CoRE Link Format.

                Registration     Lookup, Group
                 Interface        Interfaces
     +----+          |                 |
     | EP |----      |                 |
     +----+    ----  |                 |
                   --|-    +------+    |
     +----+          | ----|      |    |     +--------+
     | EP | ---------|-----|  RD  |----|-----| Client |
     +----+          | ----|      |    |     +--------+
                   --|-    +------+    |
     +----+    ----  |                 |
     | EP |----      |                 |
     +----+

              Figure 1: The resource directory architecture.

                  +------------+
                  |   Domain   | <-- Name
                  +------------+
                       |     |
                       |   +------------+
                       |   |   Group    | <-- Name, Scheme, IP, Port
                       |   +------------+
                       |     |
                  +------------+
                  |  Endpoint  |  <-- Name, Scheme, IP, Port
                  +------------+
                        |
                        |
                  +------------+
                  |  Resource  |  <-- Target, Parameters
                  +------------+

          Figure 2: The resource directory information hierarchy.

3.3.  Use Case: Cellular M2M

   Over the last few years, mobile operators around  Content model

   The Entity-Relationship (ER) models shown in Figure 3 and Figure 4
   model the world have
   focused on development contents of M2M solutions /.well-known/core and the resource directory
   respectively, with entity-relationship diagrams [ER].  Entities
   (rectangles) are used for concepts that exist independently.
   Attributes (ovals) are used for concepts that exist only in order
   connection with a related entity.  Relations (diamonds) give a
   semantic meaning to expand the
   business to relation between entities.  Numbers specify
   the new type cardinality of users: machines.  The machines the relations.

   Some of the attribute values are
   connected directly to a mobile network using an appropriate embedded
   air interface (GSM/GPRS, WCDMA, LTE) or via a gateway providing short URIs.  Those values are always full
   URIs and wide range wireless interfaces.  From never relative references in the system design point information model.  They
   can, however, be expressed as relative references in serializations,
   and often are.

   These models provide an abstract view of
   view, the ambition is to design horizontal solutions that can enable
   utilization of machines information expressed in different applications depending on their
   current availability
   link-format documents and capabilities as well as application
   requirements, thus avoiding silo like solutions.  One of a Resource Directory.  They cover the crucial
   enablers
   concepts, but not necessarily all details of such design is the ability an RD's operation; they
   are meant to discover resources
   (machines -- endpoints) capable of providing required information at give an overview, and not be a given time or acting on instructions from the end users.

   In a typical scenario, during a boot-up procedure (and periodically
   afterwards), the machines (endpoints) register with a Resource
   Directory (for example EPs installed on vehicles enabling tracking of
   their position template for fleet management purposes and monitoring
   environment parameters) hosted by
   implementations.

                       +----------------------+
                       |   /.well-known/core  |
                       +----------------------+
                                  |
                                  | 1
                          ////////\\\\\\\
                         <    contains   >
                          \\\\\\\\///////
                                  |
                                  | 0+
                        +--------------------+
                        |      link          |
                        +--------------------+
                                  |
                                  |  1   oooooooo
                                  +-----o target o
                               0+ |      oooooooo
             oooooooooooo         |
            o    target  o--------+
            o  attribute o        | 0+   oooooo
             oooooooooooo         +-----o rel  o
                                  |      oooooo
                                  |
                                  | 1    ooooooooo
                                  +-----o context o
                                         ooooooooo

          Figure 3: E-R Model of the mobile operator or somewhere
   else content of /.well-known/core

   The model shown in Figure 3 models the network, periodically a description contents of its own
   capabilities.  Due to the usual network configuration /.well-known/core
   which contains:

   o  a set of mobile
   networks, the EPs attached links belonging to the mobile network may not always be
   efficiently reachable.  Therefore, a remote server host

   The host is usually used free to
   provide proxy access choose links it deems appropriate to the EPs.  The address of each (proxy)
   endpoint on this server is included in the resource description
   stored be exposed
   in its ".well-known/core".  Typically, the RD.  The users, for example mobile applications for
   environment monitoring, contact the RD, look up links describe resources
   that are served by the endpoints capable
   of providing information about host, but the environment using appropriate set
   of link parameters, obtain information can also contain links to
   resources on how other servers (see examples in [RFC6690] page 14).  The
   set does not necessarily contain links to contact them (URLs
   of all resources served by the proxy server) and then initiate interaction to obtain
   information that is finally processed, displayed on
   host.

   A link has the screen and
   usually stored in following attributes:

   o  Zero or more link relations: They describe a database.  Similarly, fleet management systems
   provide relations between the appropriate
      link parameters to the RD to look up for EPs
   deployed on the vehicles the application is responsible for.

3.4.  Use Case: Home and Building Automation

   Home context and commercial building automation systems can benefit from the
   use of M2M web services.  The discovery requirements of these
   applications link target.

      In link-format serialization, they are demanding.  Home automation usually relies on run-
   time discovery to commission the system, whereas expressed as space-
      separated values in building
   automation a combination of professional commissioning and run-time
   discovery is used.  Both home and building automation involve peer-
   to-peer interactions between endpoints, the "rel" attribute, and involve battery-powered
   sleeping devices.

3.5.  Use Case: Link Catalogues

   Resources may be shared through data brokers that have no knowledge
   beforehand default to "hosts".

   o  A link context URI: It defines the source of who the relation, eg.
      _who_ "hosts" something.

      In link-format serialization, it is going to consume expressed in the data.  Resource Directory "anchor"
      attribute.  There, it can be used to hold links about resources and services hosted
   anywhere to make them discoverable by a general class relative reference, in which case
      it gets resolved against the URI of
   applications.

   For example, environmental and weather sensors the ".well-known/core"
      document it was obtained from . It defaults to that generate data document's
      URI.

      In the serialization, the context also serves as the Base URI for
   public consumption may provide
      resolving the data to an intermediary server, or
   broker.  Sensor data are published to target reference.

   o  A link target URI: It defines the intermediary upon changes
   or at regular intervals.  Descriptions destination of the sensors that resolve to
   links to sensor data may be published to a Resource Directory.
   Applications wishing to consume the data can use RD Lookup to
   discover relation (eg.
      _what_ is hosted), and resolve links to is the desired resources and endpoints.
   The Resource Directory service need not be coupled with the data
   intermediary service.  Mapping topic of Resource Directories to data
   intermediaries may be many-to-many.

   Metadata in web link formats like [RFC6690] are supplied by Resource
   Directories, which may be internally stored as triples, or relation/
   attribute pairs providing metadata about resource links.  External
   catalogs that are represented in other formats may be converted to
   common web linking formats for storage and access by Resource
   Directories.  Since all target attributes.

   In link-format serialization, it is common practice for these to be URN
   encoded, simple expressed between angular
   brackets, and lossless structural transforms should generally
   be sufficient to store external metadata in Resource Directories.

   The sometimes called the "href".  If it is a relative URI,
   it gets resolved against the link context URI.

   o  Other target attributes (eg. resource type (rt), interface (if),
      cor content-type (ct)).  These provide additional features information
      about the target URI.

                +----------------------+
                |  resource-directory  |
                +----------------------+
                           |
                           |         oooooooooooo  0-1
                           |        o MC address o---+
                           |         oooooooooooo    |
                           |                         |
                      //////\\\\             0+  +--------+
                     < contains >----------------| group  |
                      \\\\\/////                 +--------+
                           |                         |
                       0-n |                         | 1+
    ooooooo     1  +---------------+          ///////\\\\\\
   o  con  o-------|  registration |---------< composed of >
    ooooooo        +---------------+          \\\\\\\//////
                       |       |
                       |       +--------------+
          oooooooo   1 |                      |
         o  loc   o----+                 /////\\\\
          oooooooo     |                < contains >
                       |                 \\\\\/////
          oooooooo   1 |                      |
         o   ep   o----+                      | 0+
          oooooooo     |             +------------------+
                       |             |      link        |
          oooooooo 0-1 |             +------------------+
         o    d   o----+                      |
          oooooooo     |                      |  1   oooooooo
                       |                      +-----o target o
          oooooooo 0-1 |                      |      oooooooo
         o   lt   o----+     ooooooooooo   0+ |
          oooooooo     |    o  target   o-----+
                       |    o attribute o     | 0+   oooooo
       ooooooooooo 0+  |     ooooooooooo      +-----o rel  o
      o  endpoint o----+                      |      oooooo
      o attribute o                           |
       ooooooooooo                            | 1   ooooooooo
                                              +----o context o
                                                    ooooooooo

       Figure 4: E-R Model of the content of the Resource Directory allow domains to be
   defined

   The model shown in Figure 4 models the contents of the resource
   directory which contains in addition to enable access /.well-known/core:

   o  0 to a particular set n Registration (entries),
   o  0 or more Groups

   A Group has no or one Multicast address attribute and is composed of resources from
   particular applications.  This provides isolation and protection of
   sensitive data when needed.  Resource groups may defined to allow
   batched reads from multiple resources.

4.  Finding a Resource Directory

   Several mechanisms
   0 or more endpoints.  A registration is associated with one endpoint
   (ep).  An endpoint can be employed for discovering the RD, including
   assuming a default location (e.g. on an Edge Router in a LoWPAN),
   assigning an anycast address to the RD, using DHCP, part of 0 or discovering
   the RD using .well-known/core and hyperlinks as specified in CoRE
   Link Format [RFC6690].  Endpoints that want to contact a Resource
   Directory can obtain candidate IP addresses for such servers in more Groups . A registration
   defines a
   number set of ways.

   In a 6LoWPAN, good candidates can be taken from: links as defined for /.well-known/core.  A
   Registration has six attributes:

   o  specific static configuration (e.g., anycast addresses), if any,  one ep (endpoint with a unique name)

   o  one con (a string describing the ABRO option of 6LoWPAN-ND [RFC6775],

   o  other ND options that happen to point to servers (such as RDNSS), scheme://authority part)

   o  DHCPv6 options that might be defined later.  one lt (lifetime),

   o  The IPv6 Neighbor Discovery Resource Directory Address Option
      described  one loc (location in the RD)

   o  optional one d (domain for query filtering),

   o  optional additional endpoint attributes (from Section 4.1

   In networks with more inexpensive use 9.3)

   The cardinality of multicast, the candidate IP
   address may be con is currently 1.  Its value is used as a well-known multicast address, i.e. directory servers
   are found by simply sending GET requests to that well-known multicast
   address (see Section 5.2).

   Constrained nodes configured Base
   URI when resolving URIs in large batches may be configured for
   an anycast address for the RD.  Each target network environment links contained in
   which some of these preconfigured nodes the endpoint.

   Links are modelled as they are in Figure 3.

3.4.  Use Case: Cellular M2M

   Over the last few years, mobile operators around the world have
   focused on development of M2M solutions in order to be brought up is then
   configured with a route for this anycast address that leads to an RD
   that is appropriate for expand the environment.

   As some
   business to the new type of these sources users: machines.  The machines are just (more
   connected directly to a mobile network using an appropriate embedded
   wireless interface (GSM/GPRS, WCDMA, LTE) or less educated) guesses,
   endpoints MUST make use via a gateway providing
   short and wide range wireless interfaces.  From the system design
   point of any error messages to very strictly rate-
   limit requests view, the ambition is to candidate IP addresses design horizontal solutions that don't work out.  For
   example, an ICMP Destination Unreachable message (and,
   can enable utilization of machines in particular, different applications
   depending on their current availability and capabilities as well as
   application requirements, thus avoiding silo like solutions.  One of
   the port unreachable code for this message) may indicate crucial enablers of such design is the lack ability to discover
   resources (machines -- endpoints) capable of providing required
   information at a CoAP server given time or acting on instructions from the candidate host, or end
   users.

   Imagine a CoAP error response code
   such as 4.05 "Method Not Allowed" may indicate unwillingness scenario where endpoints installed on vehicles enable
   tracking of a
   CoAP server to act as a directory server.

4.1.  Resource Directory Address Option (RDAO)

   The Resource Directory Option (RDAO) using IPv6 neighbor Discovery
   (ND) carries information about the address position of these vehicles for fleet management
   purposes and allow monitoring of environment parameters.  During the Resource Directory
   (RD).  This information is needed when endpoints cannot discover the
   Resource Directory
   boot-up process endpoints register with link-local multicast address because a Resource Directory, which
   is hosted by the
   endpoint and mobile operator or somewhere in the RD cloud.

   Periodically, these endpoints update their registration and may
   modify resources they offer.

   When endpoints are separated by not always connected, for example because they
   enter a border Router (6LBR).  In many
   circumstances sleep mode, a remote server is usually used to provide proxy
   access to the availability endpoints.  Mobile apps or web applications for
   environment monitoring contact the RD, look up the endpoints capable
   of DHCP cannot be guaranteed either
   during commissioning providing information about the environment using appropriate set
   of link parameters, obtain information on how to contact them (URLs
   of the network.  The presence proxy server) and then initiate interaction to obtain
   information that is finally processed, displayed on the screen and
   usually stored in a database.  Similarly, fleet management systems
   provide the use of appropriate link parameters to the RD is essential during commissioning.

   It is possible to send multiple RDAO options in one message,
   indicating as many resource directory addresses.

   The lifetime 0x0 means that look up for EPs
   deployed on the RD address vehicles the application is invalid responsible for.

3.5.  Use Case: Home and to be
   removed. Building Automation

   Home and commercial building automation systems can benefit from the
   use of M2M web services.  The RDAO format is:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |  Length = 3   |       Valid Lifetime          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Reserved                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                          RD Address                           +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Type:                   38

   Length:                 8-bit unsigned integer.  The length of
                           the option in units of 8 bytes.
                           Always 3.

   Valid Lifetime:         16-bit unsigned integer.  The length discovery requirements of these
   applications are demanding.  Home automation usually relies on run-
   time in units of 60 seconds (relative discovery to commission the time the packet system, whereas in building
   automation a combination of professional commissioning and run-time
   discovery is received) used.  Both home and building automation involve peer-
   to-peer interactions between endpoints, and involve battery-powered
   sleeping devices.

3.6.  Use Case: Link Catalogues

   Resources may be shared through data brokers that
                           this Resource Directory address is valid.
                           A value have no knowledge
   beforehand of all zero bits (0x0) indicates
                           that this who is going to consume the data.  Resource Directory address
                           is not valid anymore.

   Reserved:               This field is unused.  It MUST
   can be
                           initialized used to zero by the sender hold links about resources and
                           MUST be ignored services hosted
   anywhere to make them discoverable by the receiver.

   RD Address:             IPv6 address a general class of
   applications.

   For example, environmental and weather sensors that generate data for
   public consumption may provide the RD.

                Figure 3: Resource Directory Address Option

5.  Resource Directory

   This section defines data to an intermediary server, or
   broker.  Sensor data are published to the required set intermediary upon changes
   or at regular intervals.  Descriptions of REST interfaces between a
   Resource Directory (RD) and endpoints.  Although the examples
   throughout this section assume sensors that resolve to
   links to sensor data may be published to a Resource Directory.
   Applications wishing to consume the use of CoAP [RFC7252], these REST
   interfaces data can also be realized using HTTP [RFC7230].  In all
   definitions in this section, both CoAP response codes (with dot
   notation) and HTTP response codes (without dot notation) are shown.

   An use RD implementing this specification MUST support Lookup to
   discover and resolve links to the discovery,
   registration, update, lookup, desired resources and removal interfaces defined in this
   section.

5.1.  Content Formats endpoints.
   The Resource Directory implementations using this specification MUST
   support service need not be coupled with the application/link-format content format (ct=40). data
   intermediary service.  Mapping of Resource Directories implementing this specification MAY support
   additional content formats.

   Any additional content format supported to data
   intermediaries may be many-to-many.

   Metadata in web link formats like [RFC6690] are supplied by a Resource Directory
   implementing this specification MUST have an equivalent serialization
   Directories, which may be internally stored as triples, or relation/
   attribute pairs providing metadata about resource links.  External
   catalogs that are represented in the application/link-format content format.

5.2.  URI Discovery

   Before an endpoint can make use of an RD, it must first know the RD's
   address and port, and the URI path information other formats may be converted to
   common web linking formats for its REST APIs.
   This section defines discovery of the RD storage and its URIs using the well-
   known interface of the CoRE Link Format [RFC6690].  It access by Resource
   Directories.  Since it is however
   expected that RDs will also common practice for these to be discoverable via other methods
   depending on the deployment.

   Discovery URN
   encoded, simple and lossless structural transforms should generally
   be sufficient to store external metadata in Resource Directories.

   The additional features of the RD registration URI path is performed by sending
   either a multicast or unicast GET request Resource Directory allow domains to be
   defined to enable access to "/.well-known/core" and
   including a particular set of resources from
   particular applications.  This provides isolation and protection of
   sensitive data when needed.  Resource Type (rt) parameter [RFC6690] with the value
   "core.rd" in the query string.  Likewise, groups may defined to allow
   batched reads from multiple resources.

4.  Finding a Resource Type parameter
   value of "core.rd-lookup*" is used Directory

   A device coming up may want to discover the URIs for RD Lookup
   operations, and "core.gp" is used find one or more resource directories
   to discover the URI path make itself known with.

   The device may be pre-configured to exercise specific mechanisms for RD
   Group operations.  Upon success,
   finding the response will contain a payload resource directory:

   o  It may be configured with a link format entry specific IP address for each RD function discovered, indicating
   the URI path of the RD function returned and the corresponding
   Resource Type.  When performing multicast discovery, the multicast RD.  That
      IP address used will depend on the scope required and the multicast
   capabilities of the network.

   A Resource Directory MAY provide hints about the content-formats it
   supports in the links it exposes or registers, using may also be an anycast address, allowing the "ct" link
   attribute, as shown network to
      forward RD requests to an RD that is topologically close; each
      target network environment in the example below.  Clients MAY use which some of these
   hints preconfigured
      nodes are to select alternate content-formats for interaction be brought up is then configured with the
   Resource Directory.

   HTTP does not support a route for
      this anycast address that leads to an appropriate RD.  (Instead of
      using an anycast address, a multicast and consequently only unicast
   discovery address can also be supported using HTTP.  Links to Resource Directories
   MAY be registered in other Resource Directories, and well-known entry
   points SHOULD be provided to enable the bootstrapping of unicast
   discovery.

   An RD implementation of this specification MUST support query
   filtering for the rt parameter as defined in [RFC6690].
      preconfigured.  The discovery request interface is specified as follows:

   Interaction:  EP -> RD

   Method:  GET

   URI Template:  /.well-known/core{?rt}

   URI Template Variables:

      rt :=  Resource Type (optional).  MAY contain directory servers then need to configure
      one of the values
         "core.rd", "core.rd-lookup*", "core.rd-lookup-d", "core.rd-
         lookup-res", "core.rd-lookup-ep", "core.rd-lookup-gp",
         "core.rd-group" or "core.rd*"

   Content-Format:  application/link-format (if any)

   Content-Format:  application/link-format+json (if any)

   Content-Format:  application/link-format+cbor (if any)

   The following response codes are defined for their interfaces with this interface:

   Success:  2.05 "Content" or 200 "OK" multicast address.)

   o  It may be configured with an application/link-format,
      application/link-format+json, or application/link-format+cbor
      payload containing one or more matching entries a DNS name for the RD
      resource.

   Failure:  4.04 "Not Found" or 404 "Not Found" is returned in case no
      matching entry is found for and a unicast request.

   Failure:  4.00 "Bad Request" or 400 "Bad Request" is returned in case
      of resource-
      record type to look up under this name; it can find a malformed request DNS server
      to perform the lookup using the usual mechanisms for a unicast request.

   Failure:  No error response finding DNS
      servers.

   o  It may be configured to use a multicast request.

   HTTP support :  YES (Unicast only) service discovery mechanism such as
      DNS-SD [RFC6763].  The following example shows an endpoint discovering an RD using this
   interface, thus learning that present specification suggests configuring
      the RD registration resource is, in
   this example, at /rd, and that service with name rd._sub._coap._udp, preferably within the content-format delivered by
      domain of the
   server hosting querying nodes.

   For cases where the resource is application/link-format (ct=40).  Note
   that it device is up to the RD not specifically configured with a way
   to choose its RD find a resource paths.

   Req: GET coap://[ff02::1]/.well-known/core?rt=core.rd*

   Res: 2.05 Content
   </rd>;rt="core.rd";ct=40,
   </rd-lookup/ep>;rt="core.rd-lookup-ep";ct=40,
   </rd-lookup/res>;rt="core.rd-lookup-res";ct=40,
   </rd-lookup/gp>;rt="core.rd-lookup-gp";ct=40,
   </rd-lookup/d>;rt="core.rd-lookup-d";ct=40,
   </rd-group>;rt="core.rd-group";ct=40

                   Figure 4: Example discovery exchange

   The following example shows directory, the way of indicating that a client network may
   request alternate content-formats.  The Content-Format code attribute
   "ct" MAY include want to provide a space-separated sequence of Content-Format codes
   as specified in Section 7.2.1
   suitable default.

   o  If the address configuration of [RFC7252], indicating that multiple
   content-formats are available.  The example below shows the required
   Content-Format 40 (application/link-format) indicated as well as a
   more application-specific content format (picked as 65225 in this
   example; network is performed via
      SLAAC, this is in the experimental space, not an assigned value).
   The RD resource paths /rd, /rd-lookup, and /rd-group are example
   values.  This server only implements some of provided by the interfaces described
   in this document.

   Req: GET coap://[ff02::1]/.well-known/core?rt=core.rd*

   Res: 2.05 Content
   </rd>;rt="core.rd";ct="40 65225",
   </rd-lookup/res>;rt="core.rd-lookup-res";ct="40 65225",
   </rd-lookup/ep>;rt="core.rd-lookup-ep";ct="40 65225",
   </rd-group>;rt="core.rd-group";ct="40 65225"

5.3.  Registration

   After discovering RDAO option Section 4.1.

   o  If the location address configuration of an RD, an endpoint MAY register its
   resources using the registration interface.  This interface accepts network is performed via DHCP,
      this could be provided via a
   POST from an endpoint containing DHCP option (no such option is
      defined at the list time of resources to be added to writing).

   Finally, if neither the directory device nor the network offer any specific
   configuration, the device may want to employ heuristics to find a
   suitable resource directory.

   The present specification does not fully define these heuristics, but
   suggests a number of candidates:

   o  In a 6LoWPAN, just assume the Edge Router (6LBR) can act as a
      resource directory (using the message payload in ABRO option to find that [RFC6775]).
      Confirmation can be obtained by sending a Unicast to
      "coap://[6LBR]/.well-known/core?rt=core.rd*".

   o  In a network that supports multicast well, discovering the RD
      using a multicast query for /.well-known/core as specified in CoRE
      Link Format
   [RFC6690], JSON CoRE Link Format (application/link-format+json), or
   CBOR CoRE Link Format (application/link-format+cbor)
   [I-D.ietf-core-links-json], along with query parameters indicating
   the name of [RFC6690]: Sending a Multicast GET to
      "coap://[ff02::1]/.well-known/core?rt=core.rd*".  RDs within the endpoint, and optionally its domain and
      multicast scope will answer the lifetime query.

   As some of the registration.  It is expected that other specifications will
   define further parameters (see Section 9.3).  The RD then creates a
   new registration resource in addresses obtained by the RD and returns its location.  An
   endpoint methods listed here are
   just (more or less educated) guesses, endpoints MUST make use of any
   error messages to very strictly rate-limit requests to candidate IP
   addresses that location when refreshing registrations using
   this interface.  Endpoint resources don't work out.  For example, an ICMP Destination
   Unreachable message (and, in particular, the RD are kept active for the
   period indicated by the lifetime parameter.  The endpoint is
   responsible port unreachable code
   for refreshing the entry within this period using either message) may indicate the registration lack of a CoAP server on the
   candidate host, or update interface.  The registration interface
   MUST be implemented a CoAP error response code such as 4.05 "Method
   Not Allowed" may indicate unwillingness of a CoAP server to be idempotent, so that registering twice with act as a
   directory server.

4.1.  Resource Directory Address Option (RDAO)

   The Resource Directory Option (RDAO) using IPv6 neighbor Discovery
   (ND) carries information about the same endpoint parameters ep and d does not create multiple RD
   entries.  A new registration may be created at any time to supersede
   an existing registration, replacing address of the registration parameters and
   links.

   The registration request interface is specified as follows:

   Interaction:  EP -> RD

   Method:  POST

   URI Template:  {+rd}{?ep,d,et,lt,con}

   URI Template Variables:

      rd :=  RD registration URI (mandatory). Resource Directory
   (RD).  This information is needed when endpoints cannot discover the location of
   Resource Directory with link-local multicast address because the RD, as obtained from discovery.

      ep :=  Endpoint name (mandatory).  The endpoint name is an
         identifier that MUST be unique within a domain.  The maximum
         length of this parameter is 63 bytes.

      d :=  Domain (optional).  The domain to which this
   endpoint
         belongs.  The maximum length of this parameter is 63 bytes.
         When this parameter is elided, and the RD MAY associate the
         endpoint with are separated by a configured default domain.

      et :=  Endpoint Type (optional).  The semantic type of border Router (6LBR).  In many
   circumstances the
         endpoint.  This parameter SHOULD availability of DHCP cannot be less than 63 bytes.

      lt :=  Lifetime (optional).  Lifetime guaranteed either
   during commissioning of the registration in
         seconds.  Range of 60-4294967295.  If no lifetime is included
         in network.  The presence and the initial registration, a default value use of 86400 (24
         hours) SHOULD be assumed.  If the lt parameter
   RD is not included essential during commissioning.

   It is possible to send multiple RDAO options in a registration refresh or update operation, one message,
   indicating as many resource directory addresses.

   The lifetime 0x0 means that the most
         recently supplied value SHALL RD address is invalid and to be re-used.

      con :=  Context (optional).  This parameter sets
   removed.

   The RDAO format is:

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |  Length = 3   |       Valid Lifetime          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Reserved                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                          RD Address                           +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Fields:

   Type:                   38

   Length:                 8-bit unsigned integer.  The length of
                           the scheme,
         address, port and path at which this server is available option in units of 8 bytes.
                           Always 3.

   Valid Lifetime:         16-bit unsigned integer.  The length of
                           time in units of 60 seconds (relative to
                           the
         form scheme://host:port/path.  In time the absence packet is received) that
                           this Resource Directory address is valid.
                           A value of all zero bits (0x0) indicates
                           that this parameter Resource Directory address
                           is not valid anymore.

   Reserved:               This field is unused.  It MUST be
                           initialized to zero by the scheme of sender and
                           MUST be ignored by the protocol, source receiver.

   RD Address:             IPv6 address and source port of the register request are assumed. RD.

                Figure 5: Resource Directory Address Option

5.  Resource Directory

   This parameter is mandatory
         when section defines the directory is filled by required set of REST interfaces between a third party such as an
         commissioning tool.  When con is used, scheme
   Resource Directory (RD) and host are
         mandatory and port and path parameters are optional.  If the
         endpoint uses an ephemeral port to register with, it MUST
         include the con: parameter in the registration to provide a
         valid network path.  If the endpoint which is located behind a
         NAT gateway is registering with a Resource Directory which is
         on the network service side of endpoints.  Although the NAT gateway, examples
   throughout this section assume the endpoint
         MUST use a persistent port for the outgoing registration of CoAP [RFC7252], these REST
   interfaces can also be realized using HTTP [RFC7230].  In all
   definitions in
         order to provide the NAT gateway with a valid network address
         for replies this section, both CoAP response codes (with dot
   notation) and incoming requests.

   Content-Format:  application/link-format

   Content-Format:  application/link-format+json

   Content-Format:  application/link-format+cbor

   The following HTTP response codes (without dot notation) are defined for shown.
   An RD implementing this interface:

   Success:  2.01 "Created" or 201 "Created".  The Location header
      option specification MUST be included support the discovery,
   registration, update, lookup, and removal interfaces defined in this
   section.

   All operations on the response when a new registration
      resource is created.  This Location contents of the Resource Directory MUST be a stable identifier
      generated by
   atomic and idempotent.

   A resource directory MAY make the RD as information submitted to it is used for all subsequent operations on
      this registration resource.
   available to further directories, if it can ensure that a loop does
   not form.  The registration resource location
      thus returned protocol used between directories to ensure loop-free
   operation is for the purpose of updating outside the lifetime scope of this document.

5.1.  Content Formats

   Resource Directory implementations using this specification MUST
   support the
      registration and for maintaining the application/link-format content of the registered
      links, including updating and deleting links.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.09 "Conflict" or 409 "Conflict".  Attempt to update the
      registration format (ct=40).

   Resource Directories implementing this specification MAY support
   additional content with links resulting formats.

   Any additional content format supported by a Resource Directory
   implementing this specification MUST have an equivalent serialization
   in plurality of
      references; see Section 5.3.4.

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support:  YES

   The following example shows application/link-format content format.

5.2.  URI Discovery

   Before an endpoint with the name "node1"
   registering two resources to can make use of an RD, it must first know the RD's
   address and port, and the URI path information for its REST APIs.
   This section defines discovery of the RD and its URIs using this interface.  The
   location "/rd" is an example the well-
   known interface of the CoRE Link Format [RFC6690].  A complete set of
   RD location discovered discovery methods is described in a request
   similar to Figure Section 4.

   Req: POST coap://rd.example.com/rd?ep=node1
   Content-Format: 40
   Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/light>;ct=41;rt="light-lux";if="sensor"

   Res: 2.01 Created
   Location: /rd/4521

   A Resource Directory may optionally support HTTP.  Here is an example

   Discovery of the same RD registration operation above, when done using HTTP.

   Req: POST /rd?ep=node1&con=http://[2001:db8::1:1] HTTP/1.1
   Host : example.com
   Content-Type: application/link-format
   Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/light>;ct=41;rt="light-lux";if="sensor"

   Res: 201 Created
   Location: /rd/4521

5.3.1.  Simple Registration

   Not all endpoints hosting resources are expected to know how to
   upload links URI path is performed by sending
   either a multicast or unicast GET request to "/.well-known/core" and
   including a RD as described in Section 5.3.  Instead, simple
   endpoints can implement Resource Type (rt) parameter [RFC6690] with the Simple Registration approach described value
   "core.rd" in
   this section.  An RD implementing this specification MUST implement
   Simple Registration.  However, there may be security reasons why this
   form of directory discovery would be disabled.

   This approach requires that the endpoint makes available the hosted
   resources that it wants to be discovered, as links on its "/.well-
   known/core" interface as specified in [RFC6690].

   The endpoint then finds one or more addresses query string.  Likewise, a Resource Type parameter
   value of "core.rd-lookup*" is used to discover the directory server
   as described in Section 4.

   An endpoint can send (a selection of) hosted resources URIs for RD Lookup
   operations, and "core.rd-group" is used to discover the URI path for
   RD Group operations.  Upon success, the response will contain a directory
   server
   payload with a link format entry for publication as described in Section 5.3.2.

   The directory server integrates each RD function discovered,
   indicating the information it received this way
   into its resource directory.  It MAY make URI path of the information available
   to further directories, if it can ensure that a loop does not form.
   The protocol RD function returned and the
   corresponding Resource Type.  When performing multicast discovery,
   the multicast IP address used between directories to ensure loop-free operation
   is outside will depend on the scope required and
   the multicast capabilities of this document.

5.3.2.  Simple publishing to the network.

   A Resource Directory Server

   An endpoint that wants to make itself discoverable occasionally sends
   a POST request to MAY provide hints about the "/.well-known/core" URI of any candidate
   directory server that content-formats it finds.  The body of
   supports in the POST request is
   empty, which triggers links it exposes or registers, using the resource directory server "ct" link
   attribute, as shown in the example below.  Clients MAY use these
   hints to perform GET
   requests at select alternate content-formats for interaction with the requesting server's default
   Resource Directory.

   HTTP does not support multicast and consequently only unicast
   discovery URI can be supported using HTTP.  Links to obtain
   the link-format payload Resource Directories
   MAY be registered in other Resource Directories, and well-known entry
   points SHOULD be provided to register.

   The endpoint enable the bootstrapping of unicast
   discovery.

   An RD implementation of this specification MUST include support query
   filtering for the endpoint name and rt parameter as defined in [RFC6690].

   The discovery request interface is specified as follows:

   Interaction:  EP -> RD

   Method:  GET

   URI Template:  /.well-known/core{?rt}

   URI Template Variables:

      rt :=  Resource Type (optional).  MAY include contain one of the
   registration parameters d, lt, and et, in values
         "core.rd", "core.rd-lookup*", "core.rd-lookup-res", "core.rd-
         lookup-ep", "core.rd-lookup-gp", "core.rd-group" or "core.rd*"

   Content-Format:  application/link-format (if any)

   Content-Format:  application/link-format+json (if any)

   Content-Format:  application/link-format+cbor (if any)

   The following response codes are defined for this interface:

   Success:  2.05 "Content" or 200 "OK" with an application/link-format,
      application/link-format+json, or application/link-format+cbor
      payload containing one or more matching entries for the POST RD
      resource.

   Failure:  4.00 "Bad Request" or 400 "Bad Request" is returned in case
      of a malformed request as per
   Section 5.3. for a unicast request.

   Failure:  No error response to a multicast request.

   HTTP support :  YES (Unicast only)
   The following example shows an endpoint using simple publishing, by
   simply sending discovering an empty POST to a resource directory.

   Req:(to RD using this
   interface, thus learning that the directory resource is, in this
   example, at /rd, and that the content-format delivered by the server from [ff02::1])
   POST coap://rd.example.com/.well-known/core?lt=6000;ep=node1

   Content-Format: 40

   payload:

   (empty payload)

   Res: 2.04 Changed

   (later)

   Req: (from
   hosting the resource is application/link-format (ct=40).  Note that
   it is up to the RD server to [ff02::1]) choose its RD resource paths.

   Req: GET coap://[ff02::1]/.well-known/core

   Accept: 40 coap://[ff02::1]/.well-known/core?rt=core.rd*

   Res: 2.05 Content

   payload:

   </sen/temp>

5.3.3.  Third-party registration

   For some applications, even Simple Registration may be too taxing for
   certain very constrained devices, in particular if the security
   requirements become too onerous.

   In a controlled environment (e.g. building control),
   </rd>;rt="core.rd";ct=40,
   </rd-lookup/ep>;rt="core.rd-lookup-ep";ct=40,
   </rd-lookup/res>;rt="core.rd-lookup-res";ct=40,
   </rd-lookup/gp>;rt="core.rd-lookup-gp";ct=40,
   </rd-group>;rt="core.rd-group";ct=40

                   Figure 6: Example discovery exchange

   The following example shows the Resource
   Directory can be filled by a third device, called way of indicating that a commissioning
   tool. client may
   request alternate content-formats.  The commissioning tool can fill the Resource Directory from Content-Format code attribute
   "ct" MAY include a
   database or other means.  For space-separated sequence of Content-Format codes
   as specified in Section 7.2.1 of [RFC7252], indicating that purpose multiple
   content-formats are available.  The example below shows the scheme, IP address required
   Content-Format 40 (application/link-format) indicated as well as the
   the CBOR and
   port JSON representation of the registered device link format.  The RD resource
   paths /rd, /rd-lookup, and /rd-group are example values.

   [ The RFC editor is indicated in the Context parameter asked to replace these and later occurrences of
   TBD64 and TBD504 with the registration described numeric ID values assigned by IANA to
   application/link-format+cbor and application/link-format+json,
   respectively, as they are defined in Section I-D.ietf-core-links-json. ]

   Req: GET coap://[ff02::1]/.well-known/core?rt=core.rd*

   Res: 2.05 Content
   </rd>;rt="core.rd";ct="40 65225",
   </rd-lookup/res>;rt="core.rd-lookup-res";ct="40 TBD64 TBD504",
   </rd-lookup/ep>;rt="core.rd-lookup-ep";ct="40 TBD64 TBD504",
   </rd-lookup/gp>;rt="core.rd-lookup-gp";ct=40 TBD64 TBD504",
   </rd-group>;rt="core.rd-group";ct="40 TBD64 TBD504"

5.3.

5.3.4.  Plurality of link references in a  Registration

   Plurality

   After discovering the location of link references within an RD, an endpoint MAY register its
   resources using the registration interface.  This interface accepts a Registration (registration
   resource) is
   POST from an indication endpoint containing the list of some error condition and should not be
   allowed.

   Plurality of link references exists if, and only if, two or more
   links in a Registration contain identical context, target, and
   relation values.  This condition would resources to be likely added to arise if there
   were multiple co-ordinators
   the directory as the message payload in the CoRE Link Format
   [RFC6690], JSON CoRE Link Format (application/link-format+json), or configuration tools, each
   CBOR CoRE Link Format (application/link-format+cbor)

   [I-D.ietf-core-links-json], along with a
   different set of configuration values for query parameters indicating
   the same resource.

   A Resource Directory SHOULD reject a registration, or an operation on
   a registration, which would result in a plurality name of link references
   within the endpoint, and optionally its domain and the context lifetime
   of the registration.  There  It is no requirement
   in this document for expected that other specifications will
   define further parameters (see Section 9.3).  The RD then creates a
   new registration resource directory to check for plurality of
   reference between different registrations.  Resource Directory
   operations which are rejected due to reference plurality SHOULD be
   returned the "Conflict" code, indicating that there is someting wrong
   with the request.

5.4.  Operations on the Registration Resource

   After in the initial registration, an RD and returns its location.  An
   endpoint should retain the
   returned MUST use that location of the Registration Resource for further
   operations, including when refreshing the registration registrations using
   this interface.  Registration resources in order to extend the lifetime and "keep-alive" RD are kept active for
   the registration.  If period indicated by the lifetime of parameter.  The endpoint is
   responsible for refreshing the registration expires, the RD SHOULD NOT respond to discovery
   queries with information from resource within this
   period using either the endpoint. registration or update interface.  The RD SHOULD continue
   to provide access
   registration interface MUST be implemented to be idempotent, so that
   registering twice with the Registration Resource after a registration
   time-out occurs in order to enable the registering same endpoint to
   eventually refresh the registration.  The RD MAY eventually remove
   the parameters ep and d does not
   create multiple registration resources.  A new registration resource for the purpose of resource recovery and
   garbage collection.  If the Registration Resource is removed, the
   endpoint will need to re-register.

   The Registration Resource
   may also be used created at any time to inspect the
   registration resource using GET, update supersede an existing registration,
   replacing the registration parameters and links.

   An empty payload is considered a malformed request.

   The posted link-format document can (and typically does) contain
   relative references both in its link
   contents using PATCH (as introduced targets and in [RFC8132]), its anchors, or cancel the
   registration using DELETE.

   These operations are described
   contain empty anchors.  The RD server needs to resolve these
   references in this section.

   In accordance with Section 5.3.4, operations which would result order to faithfully represent them in
   plural link references within lookups.  The
   Base URI against which they are resolved is the context of a registration resource
   SHOULD be rejected using the "Conflict" result code.

5.4.1.  Registration Update

   The update interface
   registration, which is used by an endpoint to refresh or update its
   registration with an RD.  To use the interface, the endpoint sends a
   POST request to the registration resource returned in the Location
   header option provided either explicitly in the response returned "con"
   parameter or constructed implicitly from the intial registration
   operation.

   An update MAY update requester's network
   address.  When resolving relative target references, the server first
   resolves the lifetime or context registration parameters
   "lt", "con" as in Section 5.3 ) if of that link, and then interprets the previous settings are target as
   a reference relative to be
   retained.  Parameters that are not being changed changed SHOULD NOT
   be included in an update.  Adding parameters that have not changed
   increases context (see Appendix A.4).

   The registration request interface is specified as follows:

   Interaction:  EP -> RD

   Method:  POST

   URI Template:  {+rd}{?ep,d,lt,con,extra-attrs*}

   URI Template Variables:

      rd :=  RD registration URI (mandatory).  This is the size location of
         the message but does not have any other
   implications.  Parameters MUST be included as query parameters in an
   update operation RD, as in Section 5.3.

   Upon receiving an update request, obtained from discovery.

      ep :=  Endpoint name (mostly mandatory).  The endpoint name is an RD
         identifier that MUST reset be unique within a domain.  The maximum
         length of this parameter is 63 bytes.  If the RD is configured
         to recognize the timeout for
   that endpoint and update (eg. based on its security context),
         the scheme, IP address and port of endpoint can elide the
   endpoint, using endpoint name, and assign one based
         on the source address configuration.

      d :=  Domain (optional).  The domain to which this endpoint
         belongs.  The maximum length of the update, or the context
   ("con") this parameter if present.  If the lifetime is 63 bytes.
         When this parameter "lt" is
   included in the received update request, elided, the RD MUST update MAY associate the
   lifetime
         endpoint with a configured default domain.

      lt :=  Lifetime (optional).  Lifetime of the registration and set the timeout equal to the new
   lifetime. in
         seconds.  Range of 60-4294967295.  If the no lifetime parameter is not included
         in the
   registration update, the most recent setting is re-used for initial registration, a default value of 86400 (24
         hours) SHOULD be assumed.

      con :=  Context (optional).  This parameter sets the next
   registration time-out period.

   An update MAY optionally add or replace links for Default Base
         URI under which the endpoint by
   including those request's links in the payload of the update as are to be interpreted.  The
         URI MUST NOT have a CoRE Link
   Format document.  A link is replaced only if all path component of the target URI
   and relation type (if present) and anchor value (if present) match.

   If the link payload is included, it SHOULD its own, but MUST be checked for reference
   plurality
         suitable as described in Section 5.3.4 and rejected with a
   "Conflict" result if there are plural link references detected.

   In addition to the use of POST, as described in this section, there
   is an alternate way base URI to add, replace, and delete links using PATCH as
   described resolve any relative references given
         in Section 5.4.4.

   The update registration request interface is specified as follows:

   Interaction:  EP -> RD

   Method:  POST
   URI Template:  {+location}{?lt,con}

   URI Template Variables:

      location :=  This is the Location returned by the RD as a result
         of a successful earlier registration.

      lt :=  Lifetime (optional).  Lifetime of the registration in
         seconds.  Range of 60-4294967295.  If no lifetime is included,
         the previous last lifetime set on a previous update or the
         original registration (falling back to 86400) SHOULD be used.

      con :=  Context (optional).  This  The parameter sets the scheme,
         address and port at which this server is available in therefore of the form
         scheme://host:port/path. shape
         "scheme://authority" for HTTP and CoAP URIs.  In the absence of
         this parameter the scheme of the protocol, source address and
         source port of the
         register registration request are assumed.  This
         parameter is mandatory when the directory is filled by a third
         party such as an commissioning tool.  When  If the endpoint uses an
         ephemeral port to register with, it MUST include the con
         parameter in the registration to provide a valid network path.
         If the endpoint which is used, scheme and host are
         mandatory and located behind a NAT gateway is
         registering with a Resource Directory which is on the network
         service side of the NAT gateway, the endpoint MUST use a
         persistent port and path parameters are optional.

   Content-Format:  application/link-format (mandatory)

   Content-Format: for the outgoing registration in order to
         provide the NAT gateway with a valid network address for
         replies and incoming requests.

      extra-attrs :=  Additional registration attributes (optional).
         The endpoint can pass any parameter registered at Section 9.3
         to the directory.  If the RD is aware of the parameter's
         specified semantics, it processes it accordingly.  Otherwise,
         it MUST store the unknown key and its value(s) as an endpoint
         attribute for further lookup.

   Content-Format:  application/link-format

   Content-Format:  application/link-format+json (optional)

   Content-Format:  application/link-format+cbor (optional)

   The following response codes are defined for this interface:

   Success:  2.04 "Changed"  2.01 "Created" or 204 "No Content" if 201 "Created".  The Location header
      option MUST be included in the update was
      successfully processed. response when a new registration
      resource is created.  This Location MUST be a stable identifier
      generated by the RD as it is used for all subsequent operations on
      this registration resource.  The registration resource location
      thus returned is for the purpose of updating the lifetime of the
      registration and for maintaining the content of the registered
      links, including updating and deleting links.  A registration with
      an already registered ep and d value pair responds with the same
      success code and Location as the original registration; the set of
      links registered with the endpoint is replaced with the links from
      the payload.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Registration does not
      exist (e.g. may have expired).

   Failure:  4.09 "Conflict" or 409 "Conflict".  Attempt to update the
      registration content with links resulting in plurality of
      references; see Section 5.3.4.

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support:  YES

   The following example shows an endpoint updating its registration at with the name "node1"
   registering two resources to an RD using this interface with the interface.  The
   location "/rd" is an example RD location value: /rd/4521. discovered in a request
   similar to Figure 6.

   Req: POST /rd/4521 coap://rd.example.com/rd?ep=node1
   Content-Format: 40
   Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/light>;ct=41;rt="light-lux";if="sensor"

   Res: 2.04 Changed

   The following example shows an endpoint updating its registration
   with a new lifetime and context, changing 2.01 Created
   Location: /rd/4521

   A Resource Directory may optionally support HTTP.  Here is an existing link, and
   adding a new link using this interface with the example location
   value /rd/4521.  With
   of almost the initial same registration operation above, when done using HTTP
   and the client set the
   following values:

   o  lifetime (lt)=500

   o  context (con)=coap://local-proxy-old.example.com:5683

   o  resource= </sensors/temp>;ct=41;rt="foobar";if="sensor" JSON Link Format.

Req: POST /rd/4521?lt=600&con="coap://local-proxy.example.com:5683"
   Content-Format: 40 /rd?ep=node1&con=http://[2001:db8:1::1] HTTP/1.1
Host : example.com
Content-Type: application/link-format+json
Payload:
   </sensors/temp>;ct=41;rt="temperature-f";if="sensor",
   </sensors/door>;ct=41;rt="door";if="sensor"
[
{"href": "/sensors/temp", "ct": "41", "rt": "temperature-c", "if": "sensor"},
{"href": "/sensors/light", "ct": "41", "rt": "light-lux", "if": "sensor"}
]

Res: 2.04 Changed

5.4.2. 201 Created
Location: /rd/4521
5.3.1.  Simple Registration Removal

   Although

   Not all endpoints hosting resources are expected to know how to
   upload links to a RD entries have soft state and will eventually timeout after
   their lifetime, an endpoint SHOULD explicitly remove its entry from as described in Section 5.3.  Instead, simple
   endpoints can implement the Simple Registration approach described in
   this section.  An RD if it knows it will no longer implementing this specification MUST implement
   Simple Registration.  However, there may be available (for example on
   shut-down). security reasons why this
   form of directory discovery would be disabled.

   This is accomplished using a removal interface on the RD
   by performing a DELETE on approach requires that the endpoint resource.

   The removal request makes available the hosted
   resources that it wants to be discovered, as links on its "/.well-
   known/core" interface is specified as follows:

   Interaction:  EP -> RD

   Method:  DELETE

   URI Template:  {+location}

   URI Template Variables:

      location :=  This is the Location returned by specified in [RFC6690].

   The endpoint then finds one or more addresses of the RD directory server
   as a result
         of a successful earlier registration.

   The following responses codes are defined for this interface:

   Success:  2.02 "Deleted" or 204 "No Content" upon successful deletion

   Failure:  4.00 "Bad Request" or 400 "Bad request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Registration does not
      exist (e.g. may have expired).

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support: YES

   The following examples shows successful removal of the described in Section 4.

   An endpoint from finally asks the RD with example location value /rd/4521.

   Req: DELETE /rd/4521

   Res: 2.02 Deleted

5.4.3.  Read Endpoint Links

   Some endpoints may wish directory server to manage their links probe it for
   resources and publish them as follows:

   It sends (and regularly refreshes with) a collection, and
   may need POST request to read the current set
   "/.well-known/core" URI of links stored in the registration
   resource, in order to determine link maintenance operations.

   One or more links MAY be selected by using query filtering as
   specified in [RFC6690] Section 4.1

   If no links are selected, the Resource Directory SHOULD return an
   empty payload. directory server of choice.  The read body
   of the POST request interface is specified as follows:

   Interaction:  EP -> RD

   Method: empty, which triggers the resource directory
   server to perform GET requests at the requesting server's default
   discovery URI Template:  {+location}{?href,rel,rt,if,ct}

   URI Template Variables:

      location :=  This is to obtain the Location returned by link-format payload to register.

   The endpoint includes the RD same registration parameters in the POST
   request as a result it would per Section 5.3.  The context of a successful earlier registration.

      href,rel,rt,if,ct := link relations and attributes specified in the query in order to select particular links based on their
      relations and attributes. "href" denotes the URI target of registration
   is taken from the
      link.  See [RFC6690] Sec. 4.1 requesting server's URI.

   The following responses codes are defined for this interface:

   Success:  2.05 "Content" or 200 "OK" upon success with an
      "application/link-format", "application/link-format+cbor", or
      "application/link-format+json" payload.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Registration does not
      exist (e.g. may have expired).

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform endpoints MUST be deleted after the operation.

   HTTP support: YES expiration of their lifetime.
   Additional operations cannot be executed because no registration
   location is returned.

   The following examples show successful read of the example shows an endpoint links using Simple Registration, by
   simply sending an empty POST to a resource directory.

   Req:(to RD server from the RD, with example location value /rd/4521. [2001:db8:2::1])
   POST /.well-known/core?lt=6000&ep=node1
   Content-Format: 40
   No payload

   Res: 2.04 Changed

   (later)

   Req: (from RD server to [2001:db8:2::1])
   GET /rd/4521 /.well-known/core
   Accept: 40

   Res: 2.01 2.05 Content
   Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/light>;ct=41;rt="light-lux";if="sensor"

5.4.4.  Update Endpoint Links

   A PATCH update adds, removes or changes links for the endpoint by
   including link update information in the payload of the update as a
   merge-patch+json format [RFC7396] document.

   Other PATCH document formats
   </sen/temp>

5.3.2.  Third-party registration

   For some applications, even Simple Registration may be used as appropriate too taxing for patching
   certain very constrained devices, in particular if the array of objects format of a Registration Resource. security
   requirements become too onerous.

   In
   particular, a select-merge patch document format could combine controlled environment (e.g. building control), the
   function of link selection query and link attribute replacement
   values.

   One or more links are selected for update Resource
   Directory can be filled by using query filtering as
   specified in [RFC6690] Section 4.1 a third device, called a commissioning
   tool.  The query filter selects commissioning tool can fill the links to be modified Resource Directory from a
   database or deleted, by
   matching the query parameter values to other means.  For that purpose the values scheme, IP address and
   port of the link
   attributes.

   When registered device is indicated in the query parameters are not present Context parameter
   of the registration described in Section 5.3.

5.4.  Operations on the request, Registration Resource

   After the payload
   specifies links to be added to initial registration, an endpoint should retain the target document.  When
   returned location of the query
   parameters are present, Registration Resource for further
   operations, including refreshing the attribute names and values registration in the query
   parameters select one or more links on which order to apply extend
   the PATCH
   operation.

   If no links are selected by lifetime and "keep-alive" the query parameters, registration.  When the PATCH operation lifetime of
   the registration has expired, the RD SHOULD NOT update the state of any resource, and respond to discovery
   queries concerning this endpoint.  The RD SHOULD return a
   reply of "Changed".

   If an attribute name specified in continue to provide
   access to the PATCH document exists Registration Resource after a registration time-out
   occurs in any
   the set of selected links, all occurrences of order to enable the attribute value in registering endpoint to eventually
   refresh the target document MUST be updated using registration.  The RD MAY eventually remove the value from
   registration resource for the PATCH
   payload. purpose of resource recovery and
   garbage collection.  If the attribute name Registration Resource is not present in any selected links, removed, the attribute MUST be added to
   endpoint will need to re-register.

   The Registration Resource may also be used to inspect the links.

   If
   registration resource using GET, update the PATCH payload contains plural registration link references,
   contents, or processing cancel the PATCH payload would result registration using DELETE.

   These operations are described in plural link references, this section.

5.4.1.  Registration Update

   The update interface is used by an endpoint to refresh or update its
   registration with an RD.  To use the interface, the endpoint sends a
   POST request to the registration resource returned in the Location
   header option in the response returned from the initial registration
   operation.

   An update MAY update the lifetime- or the context- registration
   parameters "lt", "con" as in Section 5.3.  Parameters that are not
   being changed SHOULD NOT be rejected with included in an update.  Adding parameters
   that have not changed increases the size of the message but does not
   have any other implications.  Parameters MUST be included as query
   parameters in an update operation as in Section 5.3.

   A registration update resets the timeout of the registration to the
   (possibly updated) lifetime of the registration, independent of
   whether a "Conflict" result. "lt" parameter was given.

   If the PATCH payload results context of the registration is changed in an update explicitly
   or implicitly, relative references submitted in the original
   registration or later updates are resolved anew against the new
   context (like in the original registration).

   This operation only describes the use of POST with an empty payload.
   As with modification of link target,
   context, or relation values, that is "href", "rel", individual using iPATCH or "anchor", PATCH as proposed
   in Section 5.4.4, future standards might describe the
   request SHOULD be rejected semantics of
   using content formats and payloads with the POST method to update the
   links of a "Conflict" result code. registration.

   The update registration request interface is specified as follows:

   Interaction:  EP -> RD

   Method:  PATCH  POST

   URI Template:  {+location}{?href,rel,rt,if,ct}  {+location}{?lt,con,extra-attrs*}

   URI Template Variables:

      location :=  This is the Location returned by the RD as a result
         of a successful earlier registration.

      href,rel,rt,if,ct

      lt := link relations and attributes specified in
      the query  Lifetime (optional).  Lifetime of the registration in order
         seconds.  Range of 60-4294967295.  If no lifetime is included,
         the previous last lifetime set on a previous update or the
         original registration (falling back to select particular 86400) SHOULD be used.

      con :=  Context (optional).  This parameter updates the context
         established in the original registration to a new value.  If
         the parameter is set in an update, it is stored by the RD as
         the new Base URI under which to interpret the links based on their
      relations of the
         registration, following the same restrictions as in the
         registration.  If the parameter is not set and attributes. "href" denotes was set
         explicitly before, the URI target previous context value is kept
         unmodified.  If the parameter is not set and was not set
         explicitly before either, the source address and source port of
         the
      link.  See [RFC6690] Sec. 4.1 update request are stored as the context.

      extra-attrs :=  Additional registration attributes (optional).  As
         with the registration, the RD processes them if it knows their
         semantics.  Otherwise, unknown attributes are stored as
         endpoint attributes, overriding any previously stored endpoint
         attributes of the same key.

   Content-Format:  application/merge-patch+json (mandatory)  none (no payload)

   The following response codes are defined for this interface:

   Success:  2.04 "Changed" 0r or 204 "No Content" in if the update was
      successfully processed.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Registration resource does not
      exist (e.g. may have expired).

   Failure:  4.09 "Conflict" or 409 "Conflict".  Attempt to update the
      registration content with links resulting in plurality of
      references; see Section 5.3.4.

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support:  YES

   The following examples show example shows an endpoint adding </sensors/humid>,
   modifying </sensors/temp>, and removing </sensors/light> links in updating its registration
   resource at an RD using the Update Endpoint Links function this interface with the example location
   value
   value: /rd/4521.

   The Registration Resource initial state is:

   Req: GET POST /rd/4521

   Res: 2.01 Content
   Payload:
   </sensors/temp>;ct=41;rt="temperature",
   </sensors/light>;ct=41;rt="light-lux";if="sensor" 2.04 Changed

   The following example shows an EP adding the link </sensors/
   humid>;ct=41;rt="humid-s";if="sensor" to the collection of links endpoint updating its registration
   resource at an RD using this interface with the example location
   value: /rd/4521.

   Req: PATCH /rd/4521

   Payload:
   [{"href":"/sensors/humid","ct": 41, "rt": "humid-s", "if": "sensor"}]

   Content-Format:
   application/merge-patch+json

   Res: 2.04 Changed
   Req: GET /rd/4521

   Res: 2.01 Content
   Payload:
   </sensors/temp>;ct=41;rt="temperature",
   </sensors/light>;ct=41;rt="light-lux";if="sensor",
   </sensors/humid>;ct=41;rt="humid-s";if="sensor"  The following example shows an EP modifying all links at the example
   location /rd/4521 which are identified by href="/sensors/temp", from
   the initial link-value of </sensors/temp>;rt="temperature" to the new
   link-value </sensors/temp>;rt="temperature-c";if="sensor" registration by changing
   the value of the link attribute "rt" and adding client set the link attribute
   if="sensor" using
   following values:

   o  endpoint name (ep)=endpoint1

   o  lifetime (lt)=500

   o  context (con)=coap://local-proxy-old.example.com:5683

   The initial state of the PATCH operation with Resource Directory is reflected in the supplied merge-
   patch+json document payload.

   Req: PATCH /rd/4521?href=/sensors/temp

   Payload:
   {"rt": "temperature-c", "if": "sensor"},

   Content-Format:
   application/merge-patch+json

   Res: 2.04 Changed
   following request:

Req: GET /rd/4521 /rd-lookup/res?ep=endpoint1

Res: 2.01 Content
Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/light>;ct=41;rt="light-lux";if="sensor",
   </sensors/humid>;ct=41;rt="humid-s";if="sensor"

   This
</sensors/temp>;ct=41;rt="temperature";anchor="coap://local-proxy-old.example.com:5683",
</sensors/light>;ct=41;rt="light-lux";if="sensor";anchor="coap://local-proxy-old.example.com:5683"

   The following example shows an EP removing all links at changing the example location
   /rd/4521 which are identified by href="/sensors/light". context to
   "coaps://new.example.com:5684":

   Req: PATCH /rd/4521?href=/sensors/light

   Payload:
   {}

   Content-Format:
   application/merge-patch+json POST /rd/4521?con=coaps://new.example.com:5684

   Res: 2.04 Changed

   The consecutive query returns:

Req: GET /rd/4521 /rd-lookup/res?ep=endpoint1

Res: 2.01 Content
Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/humid>;ct=41;rt="humid-s";if="sensor"

6.
</sensors/temp>;ct=41;rt="temperature";anchor="coaps://new.example.com:5684",
</sensors/light>;ct=41;rt="light-lux";if="sensor";anchor="coaps://new.example.com:5684",

5.4.2.  Registration Removal

   Although RD Groups

   This section defines the REST API for the creation, management, and
   lookup of endpoints for group operations.  Similar to endpoint
   registration entries in the RD, groups may be created or removed.
   However unlike have soft state and will eventually timeout after
   their lifetime, an endpoint entry, a group SHOULD explicitly remove its entry consists of a list of
   endpoints and does not have a lifetime associated with it.  In order
   to make use of multicast requests with CoAP, a group MAY have a
   multicast address associated with it.

6.1.  Register a Group

   In order to create a group, a commissioning tool (CT) used to
   configure groups, makes from
   the RD if it knows it will no longer be available (for example on
   shut-down).  This is accomplished using a request to removal interface on the RD indicating
   by performing a DELETE on the name of endpoint resource.

   Removed endpoints are implicitly removed from the group groups to create (or update), optionally the domain the group
   belongs to, and optionally the multicast address of the group.  The
   registration message includes the list of endpoints that belong to
   that group.

   All the endpoints in the group MUST be registered with the RD before
   registering a group.  If an endpoint is not yet registered to the RD
   before registering the group, the registration message returns an
   error.  The RD sends a blank target URI for every endpoint link when
   registering the group.

   Configuration of the endpoints themselves is out of scope of this
   specification.  Such an interface for managing the group membership
   of an endpoint has been defined in [RFC7390]. which
   they belong.

   The registration removal request interface is specified as follows:

   Interaction:  CT  EP -> RD

   Method:  POST  DELETE

   URI Template:  {+rd-group}{?gp,d,con}  {+location}

   URI Template Variables:

      rd-group

      location :=  RD Group URI (mandatory).  This is the location of Location returned by the RD Group REST API.

      gp :=  Group Name (mandatory).  The name of the group to be
         created or replaced, unique within that domain.  The maximum
         length as a result
         of this parameter is 63 bytes.

      d :=  Domain (optional). a successful earlier registration.

   The domain to which following responses codes are defined for this group belongs. interface:

   Success:  2.02 "Deleted" or 204 "No Content" upon successful deletion

   Failure:  4.00 "Bad Request" or 400 "Bad request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Registration does not
      exist (e.g. may have expired).

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support: YES

   The maximum length following examples shows successful removal of this parameter is 63 bytes.  Optional.
         When this parameter is elided, the RD MAY associate the endpoint from
   the RD with example location value /rd/4521.

   Req: DELETE /rd/4521

   Res: 2.02 Deleted

5.4.3.  Read Endpoint Links

   Some endpoints may wish to manage their links as a configured default domain.

      con :=  Context (optional).  This parameter sets the scheme,
         address collection, and port at which this server is available in the form
         scheme://host:port/path.  In the absence of this parameter
   may need to read the
         scheme current set of links stored in the protocol, source address and source port of registration
   resource, in order to determine link maintenance operations.

   One or more links MAY be selected by using query filtering as
   specified in [RFC6690] Section 4.1

   If no links are selected, the
         register Resource Directory SHOULD return an
   empty payload.

   The read request are assumed. interface is specified as follows:

   Interaction:  EP -> RD
   Method:  GET

   URI Template:  {+location}{?href,rel,rt,if,ct}

   URI Template Variables:

      location :=  This parameter is mandatory when the directory is filled Location returned by a third party such the RD as an
         commissioning tool.  When con is used, scheme and host are
         mandatory a result
         of a successful earlier registration.

      href,rel,rt,if,ct := link relations and port attributes specified in
      the query in order to select particular links based on their
      relations and path parameters are optional.

   Content-Format:  application/link-format

   Content-Format:  application/link-format+json

   Content-Format:  application/link-format+cbor attributes. "href" denotes the URI target of the
      link.  See [RFC6690] Sec. 4.1

   The following response responses codes are defined for this interface:

   Success:  2.01 "Created"  2.05 "Content" or 201 "Created".  The Location header
      option MUST be returned in response to a successful group CREATE
      operation.  This Location MUST be a stable identifier generated by
      the RD as it is used for delete operations of the group
      registration resource.

   Failure:  4.00 200 "OK" upon success with an
      "application/link-format", "application/link-format+cbor", or
      "application/link-format+json" payload.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  An Endpoint is  Registration does not
      registered in the RD
      exist (e.g. may have expired).

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support: YES

   The following examples show successful read of the endpoint links
   from the RD, with example shows an EP registering location value /rd/4521.

   Req: GET /rd/4521

   Res: 2.01 Content
   Payload:
   </sensors/temp>;ct=41;rt="temperature-c";if="sensor",
   </sensors/light>;ct=41;rt="light-lux";if="sensor"

5.4.4.  Update Endpoint Links

   An iPATCH (or PATCH) update [RFC8132] adds, removes or changes links
   of a group registration by including link update information in the payload
   of the update with a media type that still needs to be defined.

6.  RD Groups

   This section defines the name
   "lights" which has two REST API for the creation, management, and
   lookup of endpoints for group operations.  Similar to endpoint
   registration entries in the RD, groups may be created or removed.
   However unlike an RD using this interface.  The
   RD endpoint entry, a group path /rd-group is an example RD location discovered in entry consists of a
   request similar list of
   endpoints and does not have a lifetime associated with it.  In order
   to Figure 4.

   Req: POST coap://rd.example.com/rd-group?gp=lights
   Content-Format: 40
   Payload:
   <>;ep="node1",
   <>;ep="node2"

   Res: 2.01 Created
   Location: /rd-group/12

6.2.  Group Removal

   A make use of multicast requests with CoAP, a group can be removed simply by sending MAY have a removal message
   multicast address associated with it.

6.1.  Register a Group

   In order to create a group, a commissioning tool (CT) used to
   configure groups, makes a request to the
   location RD indicating the name of
   the group registration resource which was returned when
   intially registering to create (or update), optionally the domain the group.  Removing a group MUST NOT remove
   belongs to, and optionally the
   endpoints multicast address of the group from the RD. group.  The removal
   registration message is a list of links to registration resources of
   the endpoints that belong to that group.

   The commissioning tool SHOULD not send any target attributes with the
   links to the registration resources, and the resource directory
   SHOULD ignore any attributes that are set.

   Configuration of the endpoints themselves is out of scope of this
   specification.  Such an interface for managing the group membership
   of an endpoint has been defined in [RFC7390].

   The registration request interface is specified as follows:

   Interaction:  CT -> RD

   Method:  DELETE  POST

   URI Template:  {+location}  {+rd-group}{?gp,d,con}

   URI Template Variables:

      location

      rd-group :=  RD Group URI (mandatory).  This is the Location returned by location of
         the RD as a result Group REST API.

      gp :=  Group Name (mandatory).  The name of a successful the group registration. to be
         created or replaced, unique within that domain.  The maximum
         length of this parameter is 63 bytes.

      d :=  Domain (optional).  The domain to which this group belongs.
         The maximum length of this parameter is 63 bytes.  Optional.
         When this parameter is elided, the RD MAY associate the
         endpoint with a configured default domain.

      con :=  Context (optional).  This parameter sets the scheme,
         address and port of the multicast address associated with the
         group.  When con is used, scheme and host are mandatory and
         port parameter is optional.

   Content-Format:  application/link-format

   Content-Format:  application/link-format+json

   Content-Format:  application/link-format+cbor

   The following responses response codes are defined for this interface:

   Success:  2.02 "Deleted"  2.01 "Created" or 204 "No Content" upon 201 "Created".  The Location header
      option MUST be returned in response to a successful deletion group CREATE
      operation.  This Location MUST be a stable identifier generated by
      the RD as it is used for delete operations of the group resource.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Group does not exist.  An Endpoint is not
      registered in the RD (e.g. may have expired).

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support:  YES

   The following example shows an EP registering a group with the name
   "lights" which has two endpoints.  The RD group path /rd-group is an
   example RD location discovered in a request similar to Figure 6.

   Req: POST coap://rd.example.com/rd-group?gp=lights
                                     &con=coap://[ff35:30:2001:db8::1]
   Content-Format: 40
   Payload:
   </rd/4521>,
   </rd/4522>

   Res: 2.01 Created
   Location: /rd-group/12

   The href value is the path to the registration resource of the
   Endpoint.

6.2.  Group Removal

   A group can be removed simply by sending a removal message to the
   location of the group registration resource which was returned when
   initially registering the group.  Removing a group MUST NOT remove
   the endpoints of the group from the RD.

   The removal request interface is specified as follows:

   Interaction:  CT -> RD

   Method:  DELETE

   URI Template:  {+location}

   URI Template Variables:

      location :=  This is the path of the group resource returned by
         the RD as a result of a successful group registration.

   The following responses codes are defined for this interface:

   Success:  2.02 "Deleted" or 204 "No Content" upon successful deletion

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  4.04 "Not Found" or 404 "Not Found".  Group does not exist.

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support:  YES

   The following examples shows successful removal of the group from the
   RD with the example location value /rd-group/12.

   Req: DELETE /rd-group/12

   Res: 2.02 Deleted

7.  RD Lookup

   In order for an RD to be used for discovering

   To discover the resources registered with it, an optional the RD, a lookup interface may
   must be provided.  This lookup interface is defined as a default, and
   it is assumed that RDs may also support lookups to return resource
   descriptions in alternative formats (e.g.  Atom or HTML Link) or
   using more advanced interfaces (e.g. supporting context or semantic
   based lookup).

   RD Lookup allows lookups for domains, groups, endpoints and resources using
   attributes defined in this document and for use with the CoRE Link
   Format.  The result of a lookup request is the list of links (if any)
   corresponding to the type of lookup.  Thus, a domain lookup MUST
   return a list of domains, a group lookup MUST
   return a list of groups, an endpoint lookup MUST return a list of
   endpoints and a resource lookup MUST return a list of links to
   resources.

   RD Lookup does not expose registration resources directly, but
   returns link content from registration resource entries which satisfy
   RD Lookup queries.

   The lookup type is selected by a URI endpoint, which is indicated by
   a Resource Type as per Table 1 below:

             +-------------+--------------------+-----------+
             | Lookup Type | Resource Type      | Mandatory |
             +-------------+--------------------+-----------+
             | Resource    | core.rd-lookup-res | Mandatory |
             | Endpoint    | core.rd-lookup-ep  | Mandatory |
             | Domain      | core.rd-lookup-d   | Optional  |
             | Group       | core.rd-lookup-gp  | Optional  |
             +-------------+--------------------+-----------+

                           Table 1: Lookup Types

   Each endpoint and resource

7.1.  Resource lookup result returns respectively

   Resource lookup results in links that are semantically equivalent to
   the
   scheme (IP address links submitted to the RD if they were accessed on the endpoint
   itself.  The links and port) followed link parameters returned are equal to the
   submitted ones except for anchor, which was resolved by the path part of server
   against the endpoint's context.

   Links that did not have an anchor attribute are therefore returned
   with the (explicitly or implicitly set) context URI of
   every endpoint and resource inside angle brackets ("<>") and followed
   by the other parameters.
   registration as the anchor.  Links whose anchor was submitted as an
   absolute URI are returned as they were registered.  The target hrefs of these
   links SHOULD can always be served as they were submitted; the actual location server MAY
   return relative references in absolute form in to resource lookups,
   but that results in needlessly verbose responses.

   Above rules allow the client to interpret the response as links
   without any further knowledge of what the
   domain, endpoint or resource, but RD does.  The Resource
   Directory MAY be an replace the contexts with a configured intermediate proxy
   proxy, e.g. in the case of an HTTP lookup interface for CoAP
   endpoints.

   The domain lookup returns every lookup domain with a base RD resource
   value (e.g. "/rd") encapsulated within angle brackets.

   In case that a group does not implement any multicast address, the

7.2.  Endpoint and group lookup returns every

   Endpoint and group lookup with a lookups result in links to registration resources
   and group base resource
   value encapsulated within angle brackets (e.g. "/rd/look-up").
   Otherwise, the resources, respectively.  Endpoint registration resources
   are annotated with their endpoint names (ep), domains (d, if
   present), context (con) and lifetime (lt, if present).  Additional
   endpoint attributes are added as link attributes to their endpoint
   link unless their specification says otherwise.  Group resources are
   annotated with their group lookup returns the names (gp), domain (d, if present) and
   multicast address of the
   group inside angle brackets.

   Using (con, if present).

   While Endpoint Lookup does expose the Accept Option, registration resources, the RD
   does not need to make them accessible to clients.  Clients SHOULD NOT
   attempt to dereference or manipulate them.

7.3.  Lookup filtering

   Using the Accept Option, the requester can control whether this list
   is returned in CoRE Link Format ("application/link-format", default)
   or its alternate content-formats ("application/link-format+json" or
   "application/link-format+cbor").

   The page and count parameters are used to obtain lookup results in
   specified increments using pagination, where count specifies how many
   links to return and page specifies which subset of links organized in
   sequential pages, each containing 'count' links, starting with link
   zero and page zero.  Thus, specifying count of 10 and page of 0 will
   return the first 10 links in the result set (links 0-9).  Count = 10
   and page = 1 will return the next 'page' containing links 10-19, and
   so on.

   Multiple query parameters search criteria MAY be included in a lookup, all lookup.  All included
   parameters
   criteria MUST match for a resource link to be returned.  The
   character'*' MAY be included at the end

   A link matches a search criterion if it has an attribute of the same
   name and the same value, allowing for a parameter value trailing "*" wildcard
   operator as in Section 4.1 of [RFC6690].  Attributes that are defined
   as "link-type" match if the search value matches any of their values
   (see Section 4.1 of [RFC6690]; eg. "?if=core.s" matches ";if="abc
   core.s";").  A link also matches a
   wildcard operator.

   RD Lookup requests MAY use search criterion if the link that
   would be produced for any set of query parameters to its containing entities would match the
   registered attributes and relations.  In addition, this interface MAY
   be used with queries that specify domains, endpoints,
   criterion: A search criterion matches an endpoint if it matches the
   endpoint itself or any of the groups it is contained in, and groups.
   For example, a domain lookup filtering one on groups would return a list
   resource if it matches the resource, the resource's endpoint, or any
   of domains that contain the specified endpoint's groups.  An endpoint lookup
   filtering

   Note that "href" is also a valid search criterion and matches target
   references.  Like all search criteria, on groups would return a list resource lookup it can
   match the target reference of endpoints that are in the
   specified groups. resource link itself, but also the
   registration resource of the endpoint that registered it, or any
   group resource that endpoint is contained in.

   Clients that are interested in a lookup result repeatedly or
   continuously can use mechanisms like ETag caching, resource
   observation ([RFC7641]), or any future mechanism that might allow
   more efficient observations of collections.  These are advertised,
   detected and used according to their own specifications and can be
   used with the lookup interface as with any other resource.

   The lookup interface is specified as follows:

   Interaction:  Client -> RD

   Method:  GET

   URI Template:  {+type-lookup-
      location}{?d,res,ep,gp,et,rt,page,count,resource-param}  {+type-lookup-location}{?page,count,search*}

   URI Template Variables:

      type-lookup-location :=  RD Lookup URI for a given lookup type
         (mandatory).  The address is discovered as described in
         Section 5.2.

      ep :=  Endpoint name (optional).  Used for endpoint, group and
         resource lookups.

      d

      search :=  Domain (optional).  Used  Search criteria for domain, group, endpoint and
         resource lookups.

      res :=  resource limiting the number of results
         (optional).  Used for domain, group, endpoint and
         resource lookups.

      gp

      page := Group name (optional).  Used for endpoint, group and
      resource lookups.

      page :=  Page  Page (optional).  Parameter can not be used without the
         count parameter.  Results are returned from result set in pages
         that contain 'count' links starting from index (page * count).
         Page numbering starts with zero.

      count :=  Count (optional).  Number of results is limited to this
         parameter value.  If the page parameter is also present, the
         response MUST only include 'count' links starting with the
         (page * count) link in the result set from the query.  If the
         count parameter is not present, then the response MUST return
         all matching links in the result set.  Link numbering starts
         with zero.

      rt :=  Resource type (optional).  Used for group, endpoint and
         resource lookups.

      et :=  Endpoint type (optional).  Used for group, endpoint and
         resource lookups.

      resource-param :=  Link attribute parameters (optional).  Any link
         target attribute as defined in Section 4.1 of [RFC6690], used
         for resource lookups.

      Content-Format:  application/link-format (optional)

      Content-Format:  application/link-format+json (optional)

      Content-Format:  application/link-format+cbor (optional)

   The following responses codes are defined for this interface:

   Success:  2.05 "Content" or 200 "OK" with an "application/link-
      format", "application/link-format+cbor", or "application/link-
      format+json" payload containing matching entries for the lookup.

   Failure:  4.04 "Not Found"
      The payload can contain zero links (which is an empty payload,
      "80" (hex) or 404 "Not Found" "[]" in case the respective content format), indicating
      that no matching
      entry is found for a unicast entities matched the request.

   Failure:  No error response to a multicast request.

   Failure:  4.00 "Bad Request" or 400 "Bad Request".  Malformed
      request.

   Failure:  5.03 "Service Unavailable" or 503 "Service Unavailable".
      Service could not perform the operation.

   HTTP support:  YES

7.4.  Lookup examples

   The examples in this section assume CoAP hosts with a default CoAP
   port 61616.  HTTP hosts are possible and do not change the nature of
   the examples.

   The following example shows a client performing a resource lookup
   with the example resource look-up locations discovered in Figure 4: 6:

   Req: GET /rd-lookup/res?rt=temperature

   Res: 2.05 Content
   <coap://[FDFD::123]:61616/temp>;rt="temperature"
   </temp>;rt="temperature";anchor="coap://[2001:db8:3::123]:61616"

   The following example shows a same lookup using the CBOR Link Format media type:

Req: GET /rd-lookup/res?rt=temperature
Accept: TBD64

Res: 2.05 Content
Content-Format: TBD64
Payload in Hex notation:
81A301652F74656D70096B74656D706572617475726503781E636F61703A2F2F5B323030
313A6462383A333A3A3132335D3A3631363136
Decoded payload:
[{1: "/temp", 9: "temperature", 3: "coap://[2001:db8:3::123]:61616"}]

   A client performing an endpoint type
   lookup: that wants to be notified of new resources as they show up
   can use observation:

   Req: GET /rd-lookup/ep?et=power-node /rd-lookup/res?rt=light
   Observe: 0

   Res: 2.05 Content
   <coap://[FDFD::127]:61616>;ep="node5",
   <coap://[FDFD::129]:61616>;ep="node7"
   Observe: 23
   Payload: empty

   (at a later point in time)

   Res: 2.05 Content
   Observe: 24
   Payload:
   </west>;rt="light";anchor="coap://[2001:db8:3::124]",
   </south>;rt="light";anchor="coap://[2001:db8:3::124]",
   </east>;rt="light";anchor="coap://[2001:db8:3::124]"

   The following example shows a client performing a domain an endpoint type
   lookup:

   Req: GET /rd-lookup/d /rd-lookup/ep?et=power-node

   Res: 2.05 Content
   <>;d="domain1",
   <>;d="domain2"
   </rd/1234>;con="coap://[2001:db8:3::127]:61616";ep="node5";
   et="power-node";ct="40";lt="600",
   </rd/4521>;con="coap://[2001:db8:3::129]:61616";ep="node7";
   et="power-node";ct="40";lt="600";d="floor-3"

   The following example shows a client performing a group lookup for
   all groups:

Req: GET /rd-lookup/gp

Res: 2.05 Content
   <>;gp="lights1";d="example.com"
   <>;gp="lights2";d="ecample.com"
</rd-group/1>;gp="lights1";d="example.com";con="coap://[ff35:30:2001:db8::1]",
</rd-group/2>;gp="lights2";d="example.com";con="coap://[ff35:30:2001:db8::2]"

   The following example shows a client performing a lookup for all
   endpoints in a particular group:

Req: GET /rd-lookup/ep?gp=lights1

Res: 2.05 Content
   <coap://[FDFD::123]:61616>;ep="node1",
   <coap://[FDFD::124]:61616>;ep="node2"
</rd/abcd>;con="coap://[2001:db8:3::123]:61616";ep="node1";et="power-node";ct="40";lt="600",
</rd/efgh>;con="coap://[2001:db8:3::124]:61616";ep="node2";et="power-node";ct="40";lt="600"

   The following example shows a client performing a lookup for all
   groups an the endpoint "node1" belongs to:

   Req: GET /rd-lookup/gp?ep=node1

   Res: 2.05 Content
   <>;gp="lights1"
   </rd-group/1>;gp="lights1"

   The following example shows a client performing a paginated resource
   lookup

   Req: GET /rd-lookup/res?page=0&count=5

   Res: 2.05 Content
   <coap://[FDFD::123]:61616/res/0>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/1>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/2>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/3>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/4>;rt=sensor;ct=60
   </res/0>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/1>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/2>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/3>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/4>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616"

   Req: GET /rd-lookup/res?page=1&count=5

   Res: 2.05 Content
   <coap://[FDFD::123]:61616/res/5>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/6>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/7>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/8>;rt=sensor;ct=60
   <coap://[FDFD::123]:61616/res/9>;rt=sensor;ct=60
   </res/5>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/6>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/7>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/8>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616",
   </res/9>;rt=sensor;ct=60;anchor="coap://[2001:db8:3::123]:61616"

   The following example shows a client performing a lookup of all
   resources from endpoints of a given endpoint type.  It assumes that
   two endpoints (with endpoint names "sensor1" and "sensor2") have
   previously registered with their respective addresses
   "coap://sensor1.example.com" and "coap://sensor2.example.com", and
   posted the very payload of the 6th request of section 5 of [RFC6690].

   It demonstrates how the link targets stay unmodified, but the anchors
   get constructed by the resource directory:

  Req: GET /rd-lookup/res?et=sensor-node

  </sensors>;ct=40;title="Sensor Index";
      anchor="coap://sensor1.example.com",
  </sensors/temp>;rt="temperature-c";if="sensor";
      anchor="coap://sensor1.example.com",
  </sensors/light>;rt="light-lux";if="sensor";
      anchor="coap://sensor1.example.com",
  <http://www.example.com/sensors/t123>;rel="describedby";
      anchor="coap://sensor1.example.com/sensors/temp",
  </t>;rel="alternate";anchor="coap://sensor1.example.com/sensors/temp",
  </sensors>;ct=40;title="Sensor Index";
      anchor="coap://sensor2.example.com",
  </sensors/temp>;rt="temperature-c";if="sensor";
      anchor="coap://sensor2.example.com",
  </sensors/light>;rt="light-lux";if="sensor";
      anchor="coap://sensor2.example.com",
  <http://www.example.com/sensors/t123>;rel="describedby";
      ;anchor="coap://sensor2.example.com/sensors/temp",
  </t>;rel="alternate";anchor="coap://sensor2.example.com/sensors/temp"

8.  Security Considerations

   The security considerations as described in Section 7 of [RFC5988]
   and Section 6 of [RFC6690] apply.  The "/.well-known/core" resource
   may be protected e.g. using DTLS when hosted on a CoAP server as
   described in [RFC7252].  DTLS or TLS based security SHOULD be used on
   all resource directory interfaces defined in this document.

8.1.  Endpoint Identification and Authentication

   An Endpoint is determined to be unique by within (the domain of) an RD
   by the Endpoint identifier parameter included during Registration,
   and any associated TLS or DTLS security bindings.  An Endpoint MUST
   NOT be identified by its protocol, port or IP address as these may
   change over the lifetime of an Endpoint.

   Every operation performed by an Endpoint or Client on a resource
   directory SHOULD be mutually authenticated using Pre-Shared Key, Raw
   Public Key or Certificate based security.  Endpoints using a
   Certificate MUST include the Endpoint identifier as the Subject of
   the Certificate,

   Consider te following threat: two devices A and this identifier MUST be checked B are managed by a resource
   directory
   single server.  Both devices have unique, per-device credentials for
   use with DTLS to match the Endpoint identifier included in the
   Registration message.

8.2.  Access Control make sure that only parties with authorization to
   access A or B can do so.

   Now, imagine that a malicious device A wants to sabotage the device
   B.  It uses its credentials during the TLS exchange.  Then, it puts
   the endpoint name of device B.  If the server does not check whether
   the identifier provided in the DTLS handshake matches the identifier
   used at the CoAP layer then it may be inclined to use the endpoint
   name for looking up what information to provision to the malicious
   device.

   Therfore, Endpoints MUST include the Endpoint identifier in the
   message, and this identifier MUST be checked by a resource directory
   to match the Endpoint identifier included in the Registration
   message.

8.2.  Access Control

   Access control SHOULD be performed separately for the RD
   registration, Lookup, and group API paths, as different endpoints may
   be authorized to register with an RD from those authorized to lookup
   endpoints from the RD.  Such access control SHOULD be performed in as
   fine-grained a level as possible.  For example access control for
   lookups could be performed either at the domain, endpoint or resource
   level.

8.3.  Denial of Service Attacks

   Services that run over UDP unprotected are vulnerable to unknowingly
   become part of a DDoS attack as UDP does not require return
   routability check.  Therefore, an attacker can easily spoof the
   source IP of the target entity and send requests to such a service
   which would then respond to the target entity.  This can be used for
   large-scale DDoS attacks on the target.  Especially, if the service
   returns a response that is order of magnitudes larger than the
   request, the situation becomes even worse as now the attack can be
   amplified.  DNS servers have been widely used for DDoS amplification
   attacks.  There is also a danger that NTP Servers could become
   implicated in denial-of-service (DoS) attacks since they run on
   unprotected UDP, there is no return routability check, and they can
   have a large amplification factor.  The responses from the NTP server
   were found to be 19 times larger than the request.  A Resource
   Directory (RD) which responds to wild-card lookups is potentially
   vulnerable if run with CoAP over UDP.  Since there is no return
   routability check and the responses can be significantly larger than
   requests, RDs can unknowingly become part of a DDoS amplification
   attack.

9.  IANA Considerations
9.1.  Resource Types

   "core.rd", "core.rd-group", "core.rd-lookup-ep", "core.rd-lookup-
   res", "core.rd-lookup-d", and "core.rd-lookup-gp" resource types need to be registered
   with the resource type registry defined by [RFC6690].

9.2.  IPv6 ND Resource Directory Address Option

   This document registers one new ND option type under the subregistry
   "IPv6 Neighbor Discovery Option Formats":

   o  Resource Directory address Option (38)

9.3.  RD Parameter Registry

   This specification defines a new sub-registry for registration and
   lookup parameters called "RD Parameters" under "CoRE Parameters".
   Although this specification defines a basic set of parameters, it is
   expected that other standards that make use of this interface will
   define new ones.

   Each entry in the registry must include * the human readable name of
   the parameter, * the short name as used in query parameter, parameters or link
   attributes, * indication of whether it can be passed as a query
   parameter at registration of endpoints or groups, as a query
   parameter in lookups, or be expressed as a link attribute, * validity
   requirements if any any, and * a description.

   The query parameter MUST be both a valid URI query key
   [RFC3986]. [RFC3986] and
   a parmname as used in [RFC5988].

   The description must give details on which registrations they apply
   to (Endpoint, group registrations or both?  Can they be updated?),
   and how they are to be processed in lookups.

   The mechanisms around new RD parameters should be designed in such a
   way that they tolerate RD implementations that are unaware of the
   parameter and expose any parameter passed at registration or updates
   on in endpoint lookups.  (For example, if a parameter used at
   registration were to be confidential, the registering endpoint should
   be instructed to only set that parameter if the RD advertises support
   for keeping it confidential at the discovery step.)

   Initial entries in this sub-registry are as follows:

   +----------+-------+---------------+--------------------------------+

   +----------+-------+---------------+-----+--------------------------+
   | Name Full     | Query Short | Validity      | Use | Description              |
   +----------+-------+---------------+--------------------------------+
   | name     |       |               |     |                          |
   +----------+-------+---------------+-----+--------------------------+
   | Endpoint | ep    |               | RLA | Name of the endpoint, max 63    |
   | Name     |       |               |     | max 63 bytes             |
   | Lifetime | lt    | 60-4294967295 | RLA | Lifetime of the registration          |
   |          |       |               |     | registration in seconds  |
   | Domain   | d     |               | RLA | Domain to which this endpoint     |
   |          |       |               |     | endpoint belongs         |
   | Endpoint | et    |               | Semantic name of the endpoint  |
   | Type     |       |               |                                |
   | Context  | con   | URI           | RLA | The scheme, address and port  |
   |          |       |               |     | port and path at which this server   |
   |          |       |               |     | this server is available |
   | Resource | res   |               | Name of the resource           |
   | Name     |       |               |                                |
   | Group    | gp    |               | RLA | Name of a group in the RD   |
   | Name     |       |               |     | RD                       |
   | Page     | page  | Integer       | L   | Used for pagination      |
   | Count    | count | Integer       | L   | Used for pagination      |
   +----------+-------+---------------+--------------------------------+
   | Endpoint | et    |               | RLA | Semantic name of the     |
   | Type     |       |               |     | endpoint (see Section    |
   |          |       |               |     | 9.4)                     |
   +----------+-------+---------------+-----+--------------------------+

                          Table 2: RD Parameters

   (Short: Short name used in query parameters or link attributes.  Use:
   R = used at registration, L = used at lookup, A = expressed in link
   attribute

   The descriptions for the options defined in this document are only
   summarized here.  To which registrations they apply and when they are
   to be shown is described in the respective sections of this document.

   The IANA policy for future additions to the sub-registry is "Expert
   Review" as described in [RFC5226].

10.  Examples

   Two examples are presented: a Lighting Installation example in
   Section 10.1 and a LWM2M example in Section 10.2.

10.1.  Lighting Installation

   This example shows a simplified lighting installation which makes use [RFC8126].  The evaluation should consider
   formal criteria, duplication of functionality (Is the Resource Directory (RD) new entry
   redundant with a CoAP interface to facilitate an existing one?), topical suitability (Eg. is the installation and start up
   described property actually a property of the application code in the lights endpoint and sensors.  In particular, the example leads to the definition of not a
   group and the enabling of the corresponding multicast address.  No
   conclusions must be drawn on the realization of actual installation
   or naming procedures, because the example only "emphasizes" some
   property of a particular resource, in which case it should go into
   the issues that may influence the use payload of the RD registration and does need not pretend
   to be normative.

10.1.1.  Installation Characteristics

   The example assumes that registered?), and the installation is managed.  That means
   that a Commissioning Tool (CT) is
   potential for conflict with commonly used to authorize the addition of
   nodes, name them, and name their services.  The CT can link attributes (For
   example, "if" could be connected used as a parameter for conditional
   registration if it were not to the installation in many ways: the CT can be part of the
   installation network, connected by WiFi to the installation network,
   or connected via GPRS link, used in lookup or other method.

   It is assumed that there are two naming authorities attributes, but
   would make a bad parameter for lookup, because a resource lookup with
   an "if" query parameter could ambiguously filter by the
   installation: (1) registered
   endpoint property or the network manager that [RFC6690] link attribute).  It is responsible for the
   correct operation of the network and the connected interfaces, and
   (2) the lighting manager expected
   that is responsible for the correct
   functioning of networked lights registry will receive between 5 and sensors.  The result is 50 registrations in
   total over the
   existence next years.

9.3.1.  Full description of two naming schemes coming from the two managing
   entities.

   The example installation consists of one presence sensor, and two
   luminaries, luminary1 and luminary2, each "Endpoint Type" Registration Parameter

   An endpoint registering at an RD can describe itself with their own wireless
   interface.  Each luminary contains three lamps: left, right and
   middle.  Each luminary is accessible through one endpoint.  For each
   lamp a resource exists endpoint
   types, similar to modify the settings of a lamp how resources are described with Resource Types in
   [RFC6690].  An endpoint type is expressed as a
   luminary.  The purpose string, which can be
   either a URI or one of the installation is that the presence
   sensor notifies values defined in the presence of persons to a group of lamps.  The
   group of lamps consists of: middle and left lamps of luminary1 and
   right lamp Endpoint Type
   subregistry.  Endpoint types can be passed in the "et" query
   parameter as part of luminary2.

   Before commissioning by extra-attrs at the lighting manager, Registration step, are shown
   on endpoint lookups using the network is
   installed "et" target attribute, and access to can be
   filtered for using "et" as a search criterion in resource and
   endpoint lookup.  Multiple endpoint types are given as separate query
   parameters or link attributes.

   Note that Endpoint Type differs from Resource Type in that it uses
   multiple attributes rather than space separated values.  As a result,
   Resource Directory implementations automatically support correct
   filtering in the lookup interfaces is proven to work by the
   network manager.

   At from the moment rules for unknown
   endpoint attributes.

9.4.  "Endpoint Type" (et=) RD Parameter values

   This specification establishes a new sub-registry under "CoRE
   Parameters" called '"Endpoint Type" (et=) RD Parameter values'.  The
   registry properties (required policy, requirements, template) are
   identical to those of installation, the network under installation Resource Type parameters in [RFC6690], in
   short:

   The review policy is not
   necessarily connected IETF Review for values starting with "core", and
   Specification Required for others.

   The requirements to the DNS infra structure.  Therefore, SLAAC
   IPv6 addresses are assigned be enforced are:

   o  The values MUST be related to CT, RD, luminaries and sensor shown the purpose described in
   Table 3 below:

                   +--------------------+--------------+
                   | Name               | IPv6 address |
                   +--------------------+--------------+
                   | luminary1          | FDFD::ABCD:1 |
                   | luminary2          | FDFD::ABCD:2 |
                   | Presence sensor    | FDFD::ABCD:3 |
                   | Resource directory | FDFD::ABCD:0 |
                   +--------------------+--------------+

                    Table 3: interface SLAAC addresses

   In
      Section 10.1.2 9.3.1.

   o  The registered values MUST conform to the use ABNF reg-rel-type
      definition of resource directory during installation
   is presented.

10.1.2.  RD entries [RFC6690] and MUST NOT be a URI.

   o  It is assumed that access recommended to use the DNS infrastructure period "." character for
      segmentation.

   The registry is not always
   possible during installation.  Therefore, the SLAAC addresses initially empty.

10.  Examples

   Two examples are
   used presented: a Lighting Installation example in this section.

   For discovery,
   Section 10.1 and a LWM2M example in Section 10.2.

10.1.  Lighting Installation

   This example shows a simplified lighting installation which makes use
   of the resource types (rt) Resource Directory (RD) with a CoAP interface to facilitate
   the installation and start up of the devices are important.
   The lamps application code in the luminaries have rt: light, lights
   and sensors.  In particular, the presence sensor
   has rt: p-sensor.  The endpoints have names which are relevant example leads to the
   light installation manager.  In this case luminary1, luminary2, definition of a
   group and the presence sensor are located in room 2-4-015, where luminary1 is
   located at enabling of the window and luminary2 and corresponding multicast address.  No
   conclusions must be drawn on the presence sensor are
   located at realization of actual installation
   or naming procedures, because the door.  The endpoint names reflect this physical
   location.  The middle, left example only "emphasizes" some of
   the issues that may influence the use of the RD and right lamps are accessed via path
   /light/middle, /light/left, does not pretend
   to be normative.

10.1.1.  Installation Characteristics

   The example assumes that the installation is managed.  That means
   that a Commissioning Tool (CT) is used to authorize the addition of
   nodes, name them, and /light/right respectively. name their services.  The
   identifiers relevant CT can be connected
   to the Resource Directory are shown installation in Table 4
   below:

   +----------------+------------------+---------------+---------------+
   | Name           | endpoint         | resource path | resource type |
   +----------------+------------------+---------------+---------------+
   | luminary1      | lm_R2-4-015_wndw | /light/left   | light         |
   | luminary1      | lm_R2-4-015_wndw | /light/middle | light         |
   | luminary1      | lm_R2-4-015_wndw | /light/right  | light         |
   | luminary2      | lm_R2-4-015_door | /light/left   | light         |
   | luminary2      | lm_R2-4-015_door | /light/middle | light         |
   | luminary2      | lm_R2-4-015_door | /light/right  | light         |
   | Presence       | ps_R2-4-015_door | /ps           | p-sensor      |
   | sensor         |                  |               |               |
   +----------------+------------------+---------------+---------------+

                  Table 4: Resource Directory identifiers

   It is assumed that many ways: the CT knows can be part of the RD's address, and has
   performed URI discovery on it
   installation network, connected by WiFi to the installation network,
   or connected via GPRS link, or other method.

   It is assumed that gave a response like there are two naming authorities for the one in
   installation: (1) the Section 5.2 example.

   The CT inserts network manager that is responsible for the endpoints
   correct operation of the luminaries network and the sensor in the
   RD using the Context parameter (con) to specify the interface
   address:

   Req: POST coap://[FDFD::ABCD:0]/rd
     ?ep=lm_R2-4-015_wndw&con=coap://[FDFD::ABCD:1]&d=R2-4-015
   Payload:
   </light/left>;rt="light",
   </light/middle>;rt="light",
   </light/right>;rt="light"

   Res: 2.01 Created
   Location: /rd/4521

   Req: POST coap://[FDFD::ABCD:0]/rd
     ?ep=lm_R2-4-015_door&con=coap://[FDFD::ABCD:2]&d=R2-4-015
   Payload:
   </light/left>;rt="light",
   </light/middle>;rt="light",
   </light/right>;rt="light"

   Res: 2.01 Created
   Location: /rd/4522

   Req: POST coap://[FDFD::ABCD:0]/rd
     ?ep=ps_R2-4-015_door&con=coap://[FDFD::ABCD:3]d&d=R2-4-015
   Payload:
   </ps>;rt="p-sensor"

   Res: 2.01 Created
   Location: /rd/4523

   The domain name d=R2-4-015 has been added for an efficient lookup
   because filtering on "ep" name is more awkward.  The same domain name
   is communicated to the two luminaries connected interfaces, and
   (2) the presence sensor by the
   CT.

   The group lighting manager that is specified in responsible for the RD. correct
   functioning of networked lights and sensors.  The Context parameter result is set to the site-local multicast address allocated to the group.  In the POST
   in
   existence of two naming schemes coming from the two managing
   entities.

   The example below, these installation consists of one presence sensor, and two endpoints
   luminaries, luminary1 and luminary2, each with their own wireless
   interface.  Each luminary contains three lamps: left, right and
   middle.  Each luminary is accessible through one endpoint.  For each
   lamp a resource exists to modify the endpoint settings of a lamp in a
   luminary.  The purpose of the installation is that the presence
   sensor are registered as members of the group.

   Req: POST coap://[FDFD::ABCD:0]/rd-group
   ?gp=grp_R2-4-015&con=coap://[FF05::1]
   Payload:
   <>;ep=lm_R2-4-015_wndw,
   <>;ep=lm_R2-4-015_door,
   <>;ep=ps_R2-4-015_door

   Res: 2.01 Created
   Location: /rd-group/501

   After notifies the filling presence of the RD by the CT, the application in the
   luminaries can learn persons to which groups they belong, and enable their
   interface for the multicast address. a group of lamps.  The luminary, knowing its domain, queries the RD for the endpoint
   with rt=light
   group of lamps consists of: middle and d=R2-4-015.  The RD returns all endpoints in the
   domain.

   Req: GET coap://[FDFD::ABCD:0]/rd-lookup/ep
     ?d=R2-4-015;rt=light

   Res: 2.05 Content
   <coap://[FDFD::ABCD:1]>;
     ep="lm_R2-4-015_wndw",
   <coap://[FDFD::ABCD:2]>;
      ep="lm_R2-4-015_door"

   Knowing its own IPv6 address, the luminary discovers its endpoint
   name.  With the endpoint name left lamps of luminary1 and
   right lamp of luminary2.

   Before commissioning by the luminary queries lighting manager, the RD for all
   groups network is
   installed and access to which the endpoint belongs.

   Req: GET coap://[FDFD::ABCD:0]/rd-lookup/gp
     ?ep=lm_R2-4-015_wndw

   Res: 2.05 Content
   <coap://[FF05::1]>;gp="grp_R2-4-015"

   From the context parameter value, interfaces is proven to work by the luminary learns
   network manager.

   At the multicast
   address moment of installation, the multicast group.

   Alternatively, the CT can communicate the multicast address directly network under installation is not
   necessarily connected to the DNS infra structure.  Therefore, SLAAC
   IPv6 addresses are assigned to CT, RD, luminaries by using the "coap-group" resource specified and sensor shown in
   [RFC7390].

   Req: POST //[FDFD::ABCD:1]/coap-group
             Content-Format: application/coap-group+json
          { "a": "[FF05::1]",
             "n": "grp_R2-4-015"}

   Res: 2.01 Created
   Location-Path: /coap-group/1

   Dependent on the situation, only the address, "a", or the name, "n",
   is specified in the coap-group resource.

10.2.  OMA Lightweight M2M (LWM2M) Example

   This example shows how
   Table 3 below:

                  +--------------------+----------------+
                  | Name               | IPv6 address   |
                  +--------------------+----------------+
                  | luminary1          | 2001:db8:4::1  |
                  | luminary2          | 2001:db8:4::2  |
                  | Presence sensor    | 2001:db8:4::3  |
                  | Resource directory | 2001:db8:4::ff |
                  +--------------------+----------------+

                    Table 3: interface SLAAC addresses

   In Section 10.1.2 the OMA LWM2M specification makes use of
   Resource Directory (RD).

   OMA LWM2M is a profile for device services based on CoAP(OMA Name
   Authority).  LWM2M defines a simple object model and a number of
   abstract interfaces and operations for device management and device
   service enablement.

   An LWM2M server resource directory during installation
   is an instance of an LWM2M middleware service layer,
   containing a Resource Directory along with other LWM2M interfaces
   defined by the LWM2M specification.

   CoRE Resource Directory (RD) presented.

10.1.2.  RD entries

   It is used assumed that access to provide the LWM2M
   Registration interface.

   LWM2M does not provide for registration domains and does DNS infrastructure is not
   currently use always
   possible during installation.  Therefore, the rd-group or rd-lookup interfaces.

   The LWM2M specification describes a set of interfaces and a resource
   model used between a LWM2M device and an LWM2M server.  Other
   interfaces, proxies, and applications SLAAC addresses are currently out
   used in this section.

   For discovery, the resource types (rt) of scope for
   LWM2M. the devices are important.
   The location of lamps in the LWM2M Server luminaries have rt: light, and RD URI path is provided by the
   LWM2M Bootstrap process, so no dynamic discovery of the RD is used.
   LWM2M Servers and presence sensor
   has rt: p-sensor.  The endpoints have names which are not required relevant to implement the /.well-
   known/core resource.

10.2.1.  The LWM2M Object Model

   The OMA LWM2M object model is based on a simple 2 level class
   hierarchy consisting of Objects
   light installation manager.  In this case luminary1, luminary2, and Resources.

   An LWM2M Resource is a REST endpoint, allowed to be a single value or
   an array of values of
   the same data type.

   An LWM2M Object presence sensor are located in room 2-4-015, where luminary1 is a resource template
   located at the window and luminary2 and container type that
   encapsulates a set of related resources.  An LWM2M Object represents
   a specific type of information source; for example, there is a LWM2M
   Device Management object that represents a network connection,
   containing resources that represent individual properties like radio
   signal strength.

   Since there may potentially be more than one of a given type object,
   for example more than one network connection, LWM2M defines instances
   of objects that contain the resources that represent a specific presence sensor are
   located at the door.  The endpoint names reflect this physical thing.
   location.  The URI template for LWM2M consists of a base URI followed by Object,
   Instance, middle, left and Resource IDs:

   {/base-uri}{/object-id}{/object-instance}{/resource-id}{/resource-
   instance}

   The five variables given here right lamps are strings.  base-uri can also have
   the special value "undefined" (sometimes called "null" in RFC 6570).
   Each of the variables object-instance, resource-id, accessed via path
   /light/middle, /light/left, and resource-
   instance can be the special value "undefined" only if /light/right respectively.  The
   identifiers relevant to the values
   behind it in this sequence also Resource Directory are "undefined".  As a special case,
   object-instance can be "empty" (which is different from "undefined")
   if resource-id is not "undefined".

   base-uri := Base URI for LWM2M resources or "undefined" for default
   (empty) base URI

   object-id := OMNA (OMA Name Authority) registered object ID (0-65535)

   object-instance := Object instance identifier (0-65535) or
   "undefined"/"empty" (see above)) to refer to all instances of an
   object ID

   resource-id := OMNA (OMA shown in Table 4
   below:

   +----------------+------------------+---------------+---------------+
   | Name Authority) registered           | endpoint         | resource ID
   (0-65535) or "undefined" to refer to all resources within an instance

   resource-instance := path | resource type |
   +----------------+------------------+---------------+---------------+
   | luminary1      | lm_R2-4-015_wndw | /light/left   | light         |
   | luminary1      | lm_R2-4-015_wndw | /light/middle | light         |
   | luminary1      | lm_R2-4-015_wndw | /light/right  | light         |
   | luminary2      | lm_R2-4-015_door | /light/left   | light         |
   | luminary2      | lm_R2-4-015_door | /light/middle | light         |
   | luminary2      | lm_R2-4-015_door | /light/right  | light         |
   | Presence       | ps_R2-4-015_door | /ps           | p-sensor      |
   | sensor         |                  |               |               |
   +----------------+------------------+---------------+---------------+

                  Table 4: Resource instance identifier or "undefined" to
   refer to single instance Directory identifiers

   It is assumed that the CT knows of a resource

   LWM2M IDs are 16 bit unsigned integers represented in decimal (no
   leading zeroes except for the value 0) by RD's address, and has
   performed URI format strings.  For
   example, discovery on it that gave a LWM2M URI might be:

   /1/0/1
   The base uri is empty, the Object ID is 1, response like the instance ID is 0, one in
   the
   resource ID is 1, Section 5.2 example.

   The CT inserts the endpoints of the luminaries and the resource instance is "undefined".  This
   example URI points sensor in the
   RD using the Context parameter (con) to internal resource 1, which represents specify the
   registration lifetime configured, in instance 0 of a type 1 object
   (LWM2M Server Object).

10.2.2.  LWM2M Register Endpoint

   LWM2M defines a registration interface based
   address:

   Req: POST coap://[2001:db8:4::ff]/rd
     ?ep=lm_R2-4-015_wndw&con=coap://[2001:db8:4::1]&d=R2-4-015
   Payload:
   </light/left>;rt="light",
   </light/middle>;rt="light",
   </light/right>;rt="light"

   Res: 2.01 Created
   Location: /rd/4521

   Req: POST coap://[2001:db8:4::ff]/rd
     ?ep=lm_R2-4-015_door&con=coap://[2001:db8:4::2]&d=R2-4-015
   Payload:
   </light/left>;rt="light",
   </light/middle>;rt="light",
   </light/right>;rt="light"

   Res: 2.01 Created
   Location: /rd/4522

   Req: POST coap://[2001:db8:4::ff]/rd
     ?ep=ps_R2-4-015_door&con=coap://[2001:db8:4::3]d&d=R2-4-015
   Payload:
   </ps>;rt="p-sensor"

   Res: 2.01 Created
   Location: /rd/4523

   The domain name d=R2-4-015 has been added for an efficient lookup
   because filtering on the REST API,
   described in Section 5. "ep" name is more awkward.  The RD registration URI path of same domain name
   is communicated to the LWM2M
   Resource Directory two luminaries and the presence sensor by the
   CT.

   The group is specified in the RD.  The Context parameter is set to be "/rd".

   LWM2M endpoints register object IDs, for example </1>,
   the site-local multicast address allocated to indicate
   that a particular object type is supported, and register object
   instances, for the group.  In the POST
   in the example </1/0>, to indicate that a particular instance below, these two endpoints and the endpoint of that object type exists.

   Resources within the LWM2M object instance
   presence sensor are not registered with as members of the RD, but may be discovered group.

   Req: POST coap://[2001:db8:4::ff]/rd-group
   ?gp=grp_R2-4-015&con=coap://[ff05::1]
   Payload:
   </rd/4521>,
   </rd/4522>,
   </rd/4523>

   Res: 2.01 Created
   Location: /rd-group/501

   After the filling of the RD by reading the resource links from CT, the
   object instance using GET with a CoAP Content-Format of application/
   link-format.  Resources may also be read as a structured object by
   performing a GET application in the
   luminaries can learn to which groups they belong, and enable their
   interface for the object instance multicast address.

   The luminary, knowing its domain, queries the RD for the endpoint
   with a Content-Format rt=light and d=R2-4-015.  The RD returns all endpoints in the
   domain.

   Req: GET coap://[2001:db8:4::ff]/rd-lookup/ep
     ?d=R2-4-015;rt=light

   Res: 2.05 Content
   </rd/4521>;con="coap://[2001:db8:4::1]",
     ep="lm_R2-4-015_wndw",
   </rd/4522>;con="coap://[2001:db8:4::2]",
      ep="lm_R2-4-015_door"

   Knowing its own IPv6 address, the luminary discovers its endpoint
   name.  With the endpoint name the luminary queries the RD for all
   groups to which the endpoint belongs.

   Req: GET coap://[2001:db8:4::ff]/rd-lookup/gp
     ?ep=lm_R2-4-015_wndw

   Res: 2.05 Content
   </rd-group/501>;gp="grp_R2-4-015";con="coap://[ff05::1]"

   From the context parameter value, the luminary learns the multicast
   address of
   senml+json.

   When an LWM2M object the multicast group.

   Alternatively, the CT can communicate the multicast address directly
   to the luminaries by using the "coap-group" resource specified in
   [RFC7390].

   Req: POST //[2001:db8:4::1]/coap-group
             Content-Format: application/coap-group+json
          { "a": "[ff05::1]",
             "n": "grp_R2-4-015"}

   Res: 2.01 Created
   Location-Path: /coap-group/1

   Dependent on the situation, only the address, "a", or instance the name, "n",
   is registered, this indicates to specified in the
   LWM2M server that coap-group resource.

10.2.  OMA Lightweight M2M (LWM2M) Example

   This example shows how the OMA LWM2M specification makes use of
   Resource Directory (RD).

   OMA LWM2M is a profile for device services based on CoAP(OMA Name
   Authority).  LWM2M defines a simple object model and its resources are available a number of
   abstract interfaces and operations for device management and device
   service enablement (REST API) operations. enablement.

   An LWM2M endpoints may use the following RD registration parameters as
   defined in Table 2 :

   ep - Endpoint Name
   lt - registration lifetime

   Endpoint Name server is mandatory, all other registration parameters are
   optional.

   Additional optional an instance of an LWM2M registration parameters are defined:

   +------------+-------+-------------------------------+--------------+
   | Name       | Query | Validity                      | Description  |
   +------------+-------+-------------------------------+--------------+
   | Protocol   | b     | {"U",UQ","S","SQ","US","UQS"} | Available    |
   | Binding    |       |                               | Protocols    |
   |            |       |                               |              |
   | middleware service layer,
   containing a Resource Directory along with other LWM2M      | ver   | 1.0                           | Spec Version |
   | Version    |       |                               |              |
   |            |       |                               |              |
   | SMS Number | sms   |                               | MSISDN       |
   +------------+-------+-------------------------------+--------------+

             Table 5: interfaces
   defined by the LWM2M specification.

   CoRE Resource Directory (RD) is used to provide the LWM2M Additional
   Registration Parameters

   The following RD interface.

   LWM2M does not provide for registration parameters are domains and does not
   currently specified
   for use in LWM2M:

   et - Endpoint Type
   con - Context the rd-group or rd-lookup interfaces.

   The endpoint registration must include LWM2M specification describes a payload containing links to
   all supported objects set of interfaces and a resource
   model used between a LWM2M device and existing object instances, optionally
   including the appropriate link-format relations.

   Here is an example LWM2M registration payload:

   </1>,</1/0>,</3/0>,</5>

   This link format payload indicates that object ID 1 (LWM2M server.  Other
   interfaces, proxies, and applications are currently out of scope for
   LWM2M.

   The location of the LWM2M Server
   Object) is supported, with a single instance 0 existing, object ID 3
   (LWM2M Device object) is supported, with a single instance 0
   existing, and object 5 (LWM2M Firmware Object) RD URI path is supported, with no
   existing instances.

10.2.3. provided by the
   LWM2M Update Endpoint Registration

   An Bootstrap process, so no dynamic discovery of the RD is used.
   LWM2M Registration update proceeds as described in Section 5.4.1, Servers and adds some optional parameter updates:

   lt - Registration Lifetime
   b - Protocol Binding
   sms - MSISDN
   link payload - new or modified links

   A Registration update is also specified to be used endpoints are not required to update the
   LWM2M server whenever implement the endpoint's UDP port or IP address are
   changed.

10.2.4. /.well-
   known/core resource.

10.2.1.  The LWM2M De-Register Endpoint Object Model

   The OMA LWM2M allows for de-registration using the delete method object model is based on the
   returned location from the initial registration operation.  LWM2M de-
   registration proceeds as described in Section 5.4.2.

11.  Acknowledgments

   Oscar Novo, Srdjan Krco, Szymon Sasin, Kerry Lynn, Esko Dijk, Anders
   Brandt, Matthieu Vial, Mohit Sethi, Sampo Ukkola, Linyi Tian,
   Chistian Amsuss, and Jan Newmarch have provided helpful comments,
   discussions and ideas to improve and shape this document.  Zach would
   also like to thank his colleagues from the EU FP7 SENSEI project,
   where many a simple 2 level class
   hierarchy consisting of the resource directory concepts were originally
   developed.

12.  Changelog

   changes from -09 to -10

   o  removed "ins" Objects and "exp" link-format extensions.

   o  removed all text concerning DNS-SD.

   o  removed inconsistency in RDAO text.

   o  suggestions taken over from various sources

   o  replaced "Function Set" with "REST API", "base URI", "base path"

   o  moved simple registration to registration section

   changes from -08 Resources.

   An LWM2M Resource is a REST endpoint, allowed to -09

   o  clarified the "example use" be a single value or
   an array of values of the base RD same data type.

   An LWM2M Object is a resource values /rd,
      /rd-lookup, template and /rd-group.

   o  changed "ins" ABNF notation.

   o  various editorial improvements, including in examples

   o  clarifications container type that
   encapsulates a set of related resources.  An LWM2M Object represents
   a specific type of information source; for RDAO

   changes from -07 to -08

   o  removed link target value returned from domain and group lookup
      types

   o  Maximum length example, there is a LWM2M
   Device Management object that represents a network connection,
   containing resources that represent individual properties like radio
   signal strength.

   Since there may potentially be more than one of domain parameter 63 bytes a given type object,
   for consistency with
      group

   o  removed option example more than one network connection, LWM2M defines instances
   of objects that contain the resources that represent a specific
   physical thing.

   The URI template for simple POST LWM2M consists of link data, don't require a
      .well-known/core resource to accept POST data base URI followed by Object,
   Instance, and handle Resource IDs:

   {/base-uri}{/object-id}{/object-instance}{/resource-id}{/resource-
   instance}

   The five variables given here are strings.  base-uri can also have
   the special value "undefined" (sometimes called "null" in RFC 6570).
   Each of the variables object-instance, resource-id, and resource-
   instance can be the special value "undefined" only if the values
   behind it in this sequence also are "undefined".  As a special way; we already have /rd case,
   object-instance can be "empty" (which is different from "undefined")
   if resource-id is not "undefined".

   base-uri := Base URI for that

   o  add IPv6 ND Option LWM2M resources or "undefined" for discovery default
   (empty) base URI

   object-id := OMNA (OMA Name Authority) registered object ID (0-65535)

   object-instance := Object instance identifier (0-65535) or
   "undefined"/"empty" (see above)) to refer to all instances of an RD

   o  clarify group configuration section 6.1 that endpoints must be
   object ID

   resource-id := OMNA (OMA Name Authority) registered before including them in a group

   o  removed resource ID
   (0-65535) or "undefined" to refer to all superfluous client-server diagrams

   o  simplified lighting example

   o  introduced Commissioning Tool

   o  RD-Look-up text is extended.

   changes from -06 resources within an instance

   resource-instance := Resource instance identifier or "undefined" to -07

   o  added text
   refer to single instance of a resource

   LWM2M IDs are 16 bit unsigned integers represented in decimal (no
   leading zeroes except for the discovery section to allow content value 0) by URI format hints
      to be exposed in strings.  For
   example, a LWM2M URI might be:

   /1/0/1
   The base uri is empty, the discovery link attributes

   o  editorial updates to section 9

   o  update author information

   o  minor text corrections

   Changes from -05 to -06

   o  added note that Object ID is 1, the PATCH section instance ID is contingent on 0, the progress of
   resource ID is 1, and the PATCH method

   changes from -04 resource instance is "undefined".  This
   example URI points to -05

   o  added Update Endpoint Links using PATCH

   o  http access made explicit internal resource 1, which represents the
   registration lifetime configured, in instance 0 of a type 1 object
   (LWM2M Server Object).

10.2.2.  LWM2M Register Endpoint

   LWM2M defines a registration interface specification

   o  Added http examples

   Changes from -03 based on the REST API,
   described in Section 5.  The RD registration URI path of the LWM2M
   Resource Directory is specified to -04:

   o  Added http response codes
   o  Clarified endpoint name usage

   o  Add application/link-format+cbor content-format

   Changes from -02 to -03:

   o  Added an example for lighting and DNS integration

   o  Added an example for RD use in OMA be "/rd".

   LWM2M

   o  Added Read Links operation for link inspection by endpoints

   o  Expanded DNS-SD section

   o  Added draft authors Peter van der Stok and Michael Koster

   Changes from -01 register object IDs, for example </1>, to -02:

   o  Added indicate
   that a catalogue use case.

   o  Changed the registration update particular object type is supported, and register object
   instances, for example </1/0>, to indicate that a POST particular instance
   of that object type exists.

   Resources within the LWM2M object instance are not registered with optional link
      format payload.  Removed
   the endpoint type update RD, but may be discovered by reading the resource links from the update.

   o  Additional examples section added for more complex use cases.

   o  New DNS-SD mapping section.

   o  Added text on endpoint identification and authentication.

   o  Error code 4.04 added to Registration Update and Delete requests.

   o  Made 63 bytes
   object instance using GET with a SHOULD rather than CoAP Content-Format of application/
   link-format.  Resources may also be read as a MUST for endpoint name and
      resource type parameters.

   Changes from -00 structured object by
   performing a GET to -01:

   o  Removed the ETag validation feature.

   o  Place holder for the DNS-SD mapping section.

   o  Explicitly disabled GET object instance with a Content-Format of
   senml+json.

   When an LWM2M object or POST on returned Location.

   o  New registry for RD parameters.

   o  Added support for the JSON Link Format.

   o  Added reference instance is registered, this indicates to the Groupcomm WG draft.

   Changes from -05 to WG Document -00:

   o  Updated the version and date.

   Changes from -04 to -05:

   o  Restricted Update to parameter updates.

   o  Added pagination support for
   LWM2M server that the Lookup interface.

   o  Minor editing, bug fixes object and reference updates.

   o  Added group support.

   o  Changed rt to et its resources are available for the registration
   management and update interface.

   Changes from -03 to -04:

   o  Added the ins= parameter back for the DNS-SD mapping.

   o  Integrated the Simple Directory Discovery from Carsten.

   o  Editorial improvements.

   o  Fixed the service enablement (REST API) operations.

   LWM2M endpoints may use of ETags.

   o  Fixed tickets 383 and 372

   Changes from -02 to -03:

   o  Changed the endpoint name back to a single registration parameter
      ep= and removed the h= and ins= parameters.

   o  Updated REST interface descriptions to use RFC6570 URI Template
      format.

   o  Introduced an improved following RD Lookup design as its own function set.

   o  Improved the security considerations section.

   o  Made the POST registration interface idempotent by requiring the
      ep= parameter to be present.

   Changes from -01 to -02:

   o  Added a terminology section.

   o  Changed the inclusion of an ETag parameters as
   defined in Table 2 :

   ep - Endpoint Name
   lt - registration or update to a
      MAY.

   o  Added the concept of an RD Domain lifetime

   Endpoint Name, Lifetime, and a registration parameter LWM2M Version are mandatory parameters
   for
      it.

   o  Recommended the Location returned from a register operation, all other registration to be
      stable, allowing for endpoint and Domain information to be changed
      during updates.

   o  Changed the lookup interface to accept endpoint parameters are
   optional.

   Additional optional LWM2M registration parameters are defined:

   +-----------+-------+-------------------------------+---------------+
   | Name      | Query | Validity                      | Description   |
   +-----------+-------+-------------------------------+---------------+
   | Binding   | b     | {"U",UQ","S","SQ","US","UQS"} | Available     |
   | Mode      |       |                               | Protocols     |
   |           |       |                               |               |
   | LWM2M     | ver   | 1.0                           | Spec Version  |
   | Version   |       |                               |               |
   |           |       |                               |               |
   | SMS       | sms   |                               | MSISDN        |
   | Number    |       |                               |               |
   +-----------+-------+-------------------------------+---------------+

             Table 5: LWM2M Additional Registration Parameters

   The following RD registration parameters are not currently specified
   for use in LWM2M:

   et - Endpoint Type
   con - Context

   The endpoint registration must include a payload containing links to
   all supported objects and existing object instances, optionally
   including the appropriate link-format relations.

   Here is an example LWM2M registration payload:

   </1>,</1/0>,</3/0>,</5>

   This link format payload indicates that object ID 1 (LWM2M Server
   Object) is supported, with a single instance 0 existing, object ID 3
   (LWM2M Device object) is supported, with a single instance 0
   existing, and object 5 (LWM2M Firmware Object) is supported, with no
   existing instances.

10.2.3.  LWM2M Update Endpoint Registration

   The LwM2M update is really very similar to the registration update as
   described in Section 5.4.1, with the only difference that there are
   more parameters defined and available.  All the parameters listed in
   that section are also available with the initial registration but are
   all optional:

   lt - Registration Lifetime
   b - Protocol Binding
   sms - MSISDN
   link payload - new or modified links
   A Registration update is also specified to be used to update the
   LWM2M server whenever the endpoint's UDP port or IP address are
   changed.

10.2.4.  LWM2M De-Register Endpoint

   LWM2M allows for de-registration using the delete method on the
   returned location from the initial registration operation.  LWM2M de-
   registration proceeds as described in Section 5.4.2.

11.  Acknowledgments

   Oscar Novo, Srdjan Krco, Szymon Sasin, Kerry Lynn, Esko Dijk, Anders
   Brandt, Matthieu Vial, Jim Schaad, Mohit Sethi, Hauke Petersen,
   Hannes Tschofenig, Sampo Ukkola, Linyi Tian, and Jan Newmarch have
   provided helpful comments, discussions and ideas to improve and shape
   this document.  Zach would also like to thank his colleagues from the
   EU FP7 SENSEI project, where many of the resource directory concepts
   were originally developed.

12.  Changelog

   changes from -11 to -12

   o  added Content Model section, including ER diagram

   o  removed domain lookup interface; domains are now plain attributes
      of groups and endpoints

   o  updated chapter "Finding a Resource Directory"; now distinguishes
      configuration-provided, network-provided and heuristic sources

   o  improved text on: atomicity, idempotency, lookup with multiple
      parameters, endpoint removal, simple registration

   o  updated LWM2M description

   o  clarified where relative references are resolved, and how context
      and anchor interact

   o  new appendix on the interaction with RFCs 6690, 5988 and 3986

   o  lookup interface: group and endpoint lookup return group and
      registration resources as link targets

   o  lookup interface: search parameters work the same across all
      entities

   o  removed all methods that modify links in an existing registration
      (POST with payload, PATCH and iPATCH)

   o  removed plurality definition (was only needed for link
      modification)

   o  enhanced IANA registry text

   o  More examples and improved text

   changes from -09 to -10

   o  removed "ins" and "exp" link-format extensions.

   o  removed all text concerning DNS-SD.

   o  removed inconsistency in RDAO text.

   o  suggestions taken over from various sources

   o  replaced "Function Set" with "REST API", "base URI", "base path"

   o  moved simple registration to registration section

   changes from -08 to -09

   o  clarified the "example use" of the base RD resource values /rd,
      /rd-lookup, and /rd-group.

   o  changed "ins" ABNF notation.

   o  various editorial improvements, including in examples

   o  clarifications for RDAO

   changes from -07 to -08

   o  removed link target value returned from domain and group lookup
      types

   o  Maximum length of domain parameter 63 bytes for consistency with
      group

   o  removed option for simple POST of link data, don't require a
      .well-known/core resource to accept POST data and handle it in a
      special way; we already have /rd for that

   o  add IPv6 ND Option for discovery of an RD
   o  clarify group configuration section 6.1 that endpoints must be
      registered before including them in a group

   o  removed all superfluous client-server diagrams

   o  simplified lighting example

   o  introduced Commissioning Tool

   o  RD-Look-up text is extended.

   changes from -06 to -07

   o  added text in the discovery section to allow content format hints
      to be exposed in the discovery link attributes

   o  editorial updates to section 9

   o  update author information

   o  minor text corrections

   Changes from -05 to -06

   o  added note that the PATCH section is contingent on the progress of
      the PATCH method

   changes from -04 to -05

   o  added Update Endpoint Links using PATCH

   o  http access made explicit in interface specification

   o  Added http examples

   Changes from -03 to -04:

   o  Added http response codes

   o  Clarified endpoint name usage

   o  Add application/link-format+cbor content-format

   Changes from -02 to -03:

   o  Added an example for lighting and DNS integration

   o  Added an example for RD use in OMA LWM2M
   o  Added Read Links operation for link inspection by endpoints

   o  Expanded DNS-SD section

   o  Added draft authors Peter van der Stok and Michael Koster

   Changes from -01 to -02:

   o  Added a catalogue use case.

   o  Changed the registration update to a POST with optional link
      format payload.  Removed the endpoint type update from the update.

   o  Additional examples section added for more complex use cases.

   o  New DNS-SD mapping section.

   o  Added text on endpoint identification and authentication.

   o  Error code 4.04 added to Registration Update and Delete requests.

   o  Made 63 bytes a SHOULD rather than a MUST for endpoint name and
      resource type parameters.

   Changes from -00 to -01:

   o  Removed the ETag validation feature.

   o  Place holder for the DNS-SD mapping section.

   o  Explicitly disabled GET or POST on returned Location.

   o  New registry for RD parameters.

   o  Added support for the JSON Link Format.

   o  Added reference to the Groupcomm WG draft.

   Changes from -05 to WG Document -00:

   o  Updated the version and date.

   Changes from -04 to -05:

   o  Restricted Update to parameter updates.

   o  Added pagination support for the Lookup interface.

   o  Minor editing, bug fixes and reference updates.

   o  Added group support.

   o  Changed rt to et for the registration and update interface.

   Changes from -03 to -04:

   o  Added the ins= parameter back for the DNS-SD mapping.

   o  Integrated the Simple Directory Discovery from Carsten.

   o  Editorial improvements.

   o  Fixed the use of ETags.

   o  Fixed tickets 383 and 372

   Changes from -02 to -03:

   o  Changed the endpoint name back to a single registration parameter
      ep= and removed the h= and ins= parameters.

   o  Updated REST interface descriptions to use RFC6570 URI Template
      format.

   o  Introduced an improved RD Lookup design as its own function set.

   o  Improved the security considerations section.

   o  Made the POST registration interface idempotent by requiring the
      ep= parameter to be present.

   Changes from -01 to -02:

   o  Added a terminology section.

   o  Changed the inclusion of an ETag in registration or update to a
      MAY.

   o  Added the concept of an RD Domain and a registration parameter for
      it.

   o  Recommended the Location returned from a registration to be
      stable, allowing for endpoint and Domain information to be changed
      during updates.

   o  Changed the lookup interface to accept endpoint and Domain as
      query string parameters to control the scope of a lookup.

13.  References

13.1.  Normative References

   [I-D.ietf-core-links-json]
              Li, K., Rahman, A., and C. Bormann, "Representing
              Constrained RESTful Environments (CoRE) Link Format in
              JSON and CBOR", draft-ietf-core-links-json-09 (work in
              progress), July 2017.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
              editor.org/info/rfc2119>.

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, DOI 10.17487/RFC3986, January 2005,
              <https://www.rfc-editor.org/info/rfc3986>.

   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988,
              DOI 10.17487/RFC5988, October 2010, <https://www.rfc-
              editor.org/info/rfc5988>.

   [RFC6570]  Gregorio, J., Fielding, R., Hadley, M., Nottingham, M.,
              and D. Orchard, "URI Template", RFC 6570,
              DOI 10.17487/RFC6570, March 2012, <https://www.rfc-
              editor.org/info/rfc6570>.

   [RFC6690]  Shelby, Z., "Constrained RESTful Environments (CoRE) Link
              Format", RFC 6690, DOI 10.17487/RFC6690, August 2012,
              <https://www.rfc-editor.org/info/rfc6690>.

   [RFC6763]  Cheshire, S. and M. Krochmal, "DNS-Based Service
              Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013,
              <https://www.rfc-editor.org/info/rfc6763>.

   [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", BCP 26,
              RFC 8126, DOI 10.17487/RFC8126, June 2017,
              <https://www.rfc-editor.org/info/rfc8126>.

   [RFC8132]  van der Stok, P., Bormann, C., and A. Sehgal, "PATCH and
              FETCH Methods for the Constrained Application Protocol
              (CoAP)", RFC 8132, DOI 10.17487/RFC8132, April 2017,
              <https://www.rfc-editor.org/info/rfc8132>.

13.2.  Informative References

   [ER]       Chen, P., "The entity-relationship model---toward a
              unified view of data", ACM Transactions on Database
              Systems Vol. 1, pp. 9-36, DOI 10.1145/320434.320440, March
              1976.

   [I-D.arkko-core-dev-urn]
              Arkko, J., Jennings, C., and Z. Shelby, "Uniform Resource
              Names for Device Identifiers", draft-arkko-core-dev-urn-04
              (work in progress), July 2017.

   [I-D.nottingham-rfc5988bis]
              Nottingham, M., "Web Linking", draft-nottingham-
              rfc5988bis-08 (work in progress), August 2017.

   [I-D.silverajan-core-coap-protocol-negotiation]
              Silverajan, B. and M. Ocak, "CoAP Protocol Negotiation",
              draft-silverajan-core-coap-protocol-negotiation-07 (work
              in progress), October 2017.

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616,
              DOI 10.17487/RFC2616, June 1999, <https://www.rfc-
              editor.org/info/rfc2616>.

   [RFC6775]  Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
              Bormann, "Neighbor Discovery Optimization for IPv6 over
              Low-Power Wireless Personal Area Networks (6LoWPANs)",
              RFC 6775, DOI 10.17487/RFC6775, November 2012,
              <https://www.rfc-editor.org/info/rfc6775>.

   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
              Protocol (HTTP/1.1): Message Syntax and Routing",
              RFC 7230, DOI 10.17487/RFC7230, June 2014,
              <https://www.rfc-editor.org/info/rfc7230>.

   [RFC7252]  Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
              Application Protocol (CoAP)", RFC 7252,
              DOI 10.17487/RFC7252, June 2014, <https://www.rfc-
              editor.org/info/rfc7252>.

   [RFC7390]  Rahman, A., Ed. and E. Dijk, Ed., "Group Communication for
              the Constrained Application Protocol (CoAP)", RFC 7390,
              DOI 10.17487/RFC7390, October 2014, <https://www.rfc-
              editor.org/info/rfc7390>.

   [RFC7641]  Hartke, K., "Observing Resources in the Constrained
              Application Protocol (CoAP)", RFC 7641,
              DOI 10.17487/RFC7641, September 2015, <https://www.rfc-
              editor.org/info/rfc7641>.

Appendix A.  Web links and the Resource Directory

   Understanding the semantics of a link-format document and its URI
   references is a journey through different documents ([RFC3986]
   defining URIs, [RFC6690] defining link-format documents based on
   [RFC5988] which defines link headers, and [RFC7252] providing the
   transport).  This appendix summarizes the mechanisms and semantics at
   play from an entry in ".well-known/core" to a resource lookup.

   This text is primarily aimed at people entering the field of
   Constrained Restful Environments from applications that previously
   did not use web mechanisms.

A.1.  A simple example

   Let's start this example with a very simple host, "2001:db8:f0::1".
   A client that follows classical CoAP Discovery ([RFC7252] Section 7),
   sends the following multicast request to learn about neighbours
   supporting resources with resource-type "temperature".

   The client sends a link-local multicast:

   GET coap://[ff02::fd]:5683/.well-known/core?rt=temperature

   RES 2.05 Content
   </temp>;rt=temperature;ct=0

   where the response is sent by the server, "[2001:db8:f0::1]:5683".

   While the client - on the practical or implementation side - can just
   go ahead and create a new request to "[2001:db8:f0::1]:5683" with
   Uri-Path: "temp", the full resolution steps without any shortcuts
   are:

A.1.1.  Resolving the URIs

   The client parses the single returned record.  The link's target
   (sometimes called "href") is ""/temp"", which is a relative URI that
   needs resolving.  The Base URI to resolve that against is, in absence
   of an "anchor" parameter, the URI of the requested resource as
   described in [RFC6690] Section 2.1.

   The URI of the requested resource can be composed by following the
   steps of [RFC7252] section 6.5 (with an addition at the end of 8.2)
   into ""coap://[2001:db8:f0::1]/.well-known/core"".

   The record's target is resolved by replacing the path ""/.well-known/
   core"" from the Base URI (section 5.2 [RFC3986]) with the relative
   target URI ""/temp"" into ""coap://[2001:db8:f0::1]/temp"".

A.1.2.  Interpreting attributes and relations

   Some more information but the record's target can be obtained from
   the payload: the resource type of the target is "temperature", and
   its content type is text/plain (ct=0).

   A relation in a web link is a three-part statement that the context
   resource has a named relation to the target resource, like "_This
   page_ has _its table of contents_ at _/toc.html_".  In [RFC6690]
   link-format documents, there is an implicit "host relation" specified
   with default parameter: rel="hosts".

   In our example, the context of the link is the URI of the requested
   document itself.  A full English expression of the "host relation"
   is:

   '"coap://[2001:db8:f0::1]/.well-known/core" is hosting the resource
   "coap://[2001:db8:f0::1]/temp", which is of the resource type
   "temperature" and can be accessed using the text/plain content
   format.'

A.2.  A slightly more complex example

   Omitting the "rt=temperature" filter, the discovery query would have
   given some more records in the payload:

   </temp>;rt=temperature;ct=0,
   </light>;rt=light-lux;ct=0,
   </t>;anchor="/sensors/temp";rel=alternate,
   <http://www.example.com/sensors/t123>;anchor="/sensors/temp";
       rel=describedby,
   <t123.pdf>;rel=alternate;ct=65001;
       anchor="http://www.example.com/sensors/t123"

   Parsing the third record, the client encounters the "anchor"
   parameter.  It is a URI relative to the document's Base URI and is
   thus resolved to ""coap://[2001:db8:f0::1]/sensors/temp"".  That is
   the context resource of the link, so the "rel" statement is not about
   the target and the document Base URI any more, but about the target
   and that address.

   Thus, the third record could be read as
   ""coap://[2001:db8:f0::1]/sensors/temp" has an alternate
   representation at "coap://[2001:db8:f0::1]/t"".

   The fourth record can be read as ""coap://[2001:db8:f0::1]/sensors/
   temp" is described by "http://www.example.com/sensors/t123""

   In the last example the anchor is absolute, where a ""t123.pdf"" is
   resolved relative to ""http://www.example.com/sensors/t123"", which
   gives a statement that ""http://www.example.com/sensors/t123/
   t123.pdf" is an alternate representation to
   ""http://www.example.com/sensors/t123" of which the content type is
   PDF".

A.3.  Enter the Resource Directory

   The resource directory tries to carry the semantics obtainable by
   classical CoAP discovery over to the resource lookup interface as
   faithfully as possible.

   For the following queries, we will assume that the simple host has
   used Simple Registration to register at the resource directory that
   was announced to it, sending this request from its UDP port
   "[2001:db8:f0::1]:6553":

   POST coap://[2001:db8:f01::ff]/.well-known/core?ep-simple-host1

   The resource directory would have accepted the registration, and Domain
   queried the simple host's ".well-known/core" by itself.  As a result,
   the host is registered as an endpoint in the RD with the name
   "simple-host1".  The registration is active for 86400 seconds, and
   the endpoint registration Base URI is ""coap://[2001:db8:f0::1]/""
   because that is the address the registration was sent from (and no
   explicit "con=" was given).

   If the client now queries the RD as it would previously have issued a
   multicast request, it would go through the RD discovery steps by
   fetching "coap://[2001:db8:f0::ff]/.well-known/core?rt=core.rd-
   lookup-res", obtain "coap://[2001:db8:f0::ff]/rd-lookup/res" as the
   resource lookup endpoint, and issue a request to
   "coap://[2001:db8:f0::ff]/rd-lookup/res?rt=temperature" to receive
   the following data:

       </temp>;rt=temperature;ct=0;anchor="coap://[2001:db8:f0::1]"

   This is not _literally_ the same response that it would have received
   from a multicast request, but it would contain the (almost) same
   statement:

   '"coap://[2001:db8:f0::1]" is hosting the resource
   "coap://[2001:db8:f0::1]/temp", which is of the resource type
   "temperature" and can be accessed using the text/plain content
   format.'

   (The difference is whether "/" or "/.well-known/core" hosts the
   resources, which is subject of ongoing discussion about RFC6690).

   To complete the examples, the client could also query string parameters all resources
   hosted at the endpoint with the known endpoint name "simple-host1".
   A request to control "coap://[2001:db8:f0::ff]/rd-lookup/res?ep=simple-host1"
   would return

   </temp>;rt=temperature;ct=0;anchor="coap://[2001:db8:f0::1]",
   </light>;rt=light-lux;ct=0;anchor="coap://[2001:db8:f0::1]",
   </t>;anchor="coap://[2001:db8:f0::1]/sensors/temp";rel=alternate,
   <http://www.example.com/sensors/t123>;
       anchor="coap://[2001:db8:f0::1]/sensors/temp";rel=describedby,
   <t123.pdf>;rel=alternate;ct=65001;
       anchor="http://www.example.com/sensors/t123"

   Note that the last link was not modified at all because its anchor
   was already an absolute reference.

   Had the simple host registered with an explicit context (eg.
   "?ep=simple-host1&con=coap+tcp://simple-host1.example.com"), that
   context would have been used to resolve the scope of a lookup.

13.  References

13.1.  Normative References

   [I-D.ietf-core-links-json]
              Li, K., Rahman, A., relative anchor values
   instead, giving

</temp>;rt=temperature;ct=0;anchor="coap+tcp://simple-host1.example.com"
   and analogous records.

A.4.  A note on differences between link-format and C. Bormann, "Representing
              Constrained RESTful Environments (CoRE) Link Format in
              JSON headers

   While link-format and CBOR", draft-ietf-core-links-json-08 (work in
              progress), April 2017.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC3986]  Berners-Lee, T., Fielding, R., Link headers look very similar and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, DOI 10.17487/RFC3986, January 2005,
              <http://www.rfc-editor.org/info/rfc3986>.

   [RFC5226]  Narten, T. are based on
   the same model of typed links, there are some differences between
   [RFC6690] and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", RFC 5226,
              DOI 10.17487/RFC5226, May 2008,
              <http://www.rfc-editor.org/info/rfc5226>. [RFC5988]  Nottingham, M., "Web Linking", RFC 5988,
              DOI 10.17487/RFC5988, October 2010,
              <http://www.rfc-editor.org/info/rfc5988>.

   [RFC6570]  Gregorio, J., Fielding, R., Hadley, M., Nottingham, M., that should be kept in mind when using or
   implementing a Resource Directory:

   o  There is no percent encoding in link-format documents.

      A link-format document is a UTF-8 encoded string of Unicode
      characters and D. Orchard, "URI Template", RFC 6570,
              DOI 10.17487/RFC6570, March 2012,
              <http://www.rfc-editor.org/info/rfc6570>.

   [RFC6690]  Shelby, Z., "Constrained RESTful Environments (CoRE) does not have percent encoding, while Link
              Format", RFC 6690, DOI 10.17487/RFC6690, August 2012,
              <http://www.rfc-editor.org/info/rfc6690>.

   [RFC7396]  Hoffman, P. and J. Snell, "JSON Merge Patch", RFC 7396,
              DOI 10.17487/RFC7396, October 2014,
              <http://www.rfc-editor.org/info/rfc7396>.

   [RFC8132]  van der Stok, P., Bormann, C., and A. Sehgal, "PATCH and
              FETCH Methods headers
      are practically ASCII strings that use percent encoding for non-
      ASCII characters, stating the encoding explictly when required.

      For example, while a Link header in a page about a Swedish city
      might read

      "Link: </temperature/Malm%C3%B6>;rel="live-environment-data""

      a link-format document from the same source might describe the
      link as

      "</temperature/Malmoe>;rel="live-environment-data""

   o  In a link-format document, if the anchor attribute is present, the
      link target reference is resolved by using the the (resolved)
      anchor value as Base URI for that link, while in Link headers, it
      is resolved against the Constrained Application Protocol
              (CoAP)", RFC 8132, DOI 10.17487/RFC8132, April 2017,
              <http://www.rfc-editor.org/info/rfc8132>.

13.2.  Informative References

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616,
              DOI 10.17487/RFC2616, June 1999,
              <http://www.rfc-editor.org/info/rfc2616>.

   [RFC6775]  Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
              Bormann, "Neighbor Discovery Optimization URI of the requested document.

      This is explicit in [RFC6690] section 2.1 for IPv6 over
              Low-Power Wireless Personal Area Networks (6LoWPANs)",
              RFC 6775, DOI 10.17487/RFC6775, November 2012,
              <http://www.rfc-editor.org/info/rfc6775>.

   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
              Protocol (HTTP/1.1): Message Syntax and Routing",
              RFC 7230, DOI 10.17487/RFC7230, June 2014,
              <http://www.rfc-editor.org/info/rfc7230>.

   [RFC7252]  Shelby, Z., Hartke, K., link-format, and C. Bormann, "The Constrained
              Application Protocol (CoAP)", RFC 7252,
              DOI 10.17487/RFC7252, June 2014,
              <http://www.rfc-editor.org/info/rfc7252>.

   [RFC7390]  Rahman, A., Ed.
      spelled out in section B.2 of [I-D.nottingham-rfc5988bis] , which
      obsoletes the older [RFC5988].  [RFC6690] is based on [RFC5988]
      and E. Dijk, Ed., "Group Communication has not been updated with clarifications from
      [I-D.nottingham-rfc5988bis].

Appendix B.  Syntax examples for
              the Constrained Application Protocol (CoAP)", RFC 7390,
              DOI 10.17487/RFC7390, October 2014,
              <http://www.rfc-editor.org/info/rfc7390>.

   [RFC7641]  Hartke, K., "Observing Resources Negotiation

   [ This appendix should not show up in a published version of this
   document. ]

   The protocol negotiation that is being worked on in
   [I-D.silverajan-core-coap-protocol-negotiation] makes use of the Constrained
              Application Protocol (CoAP)", RFC 7641,
              DOI 10.17487/RFC7641, September 2015,
              <http://www.rfc-editor.org/info/rfc7641>.
   Resource Directory.

   Until that document is update to use the latest resource-directory
   specification, here are some examples of protocol negotiation with
   the current Resource Directory:

   An endpoint could register as follows:

   Req: POST coap://rd.example.com/rd?ep=node1
       &at=coap+tcp://[2001:db8:f1::2]
       &at=coap://[2001:db8:f1::2]
   Content-Format: 40
   Payload:
   </temperature>;ct=0;rt="temperature";if="core.s"

   Res: 2.01 Created
   Location: /rd/1234

   A UDP client would then query:

   Req: GET /rd-lookup/res?rt=temperature

   Res: 2.05 Content
   </temperature>;ct=0;rt="temperature";if="core.s";
       anchor="coap://[2001:db8:f1::2]"

   while a TCP capable client could say:

   Req: GET /rd-lookup/res?rt=temperature&tt=tcp

   Res: 2.05 Content
   </temperature>;ct=0;rt="temperature";if="core.s";
       anchor="coap+tcp://[2001:db8:f1::2]"

Authors' Addresses

   Zach Shelby
   ARM
   150 Rose Orchard
   San Jose  95134
   USA

   Phone: +1-408-203-9434
   Email: zach.shelby@arm.com
   Michael Koster
   SmartThings
   665 Clyde Avenue
   Mountain View  94043
   USA

   Phone: +1-707-502-5136
   Email: Michael.Koster@smartthings.com

   Carsten Bormann
   Universitaet Bremen TZI
   Postfach 330440
   Bremen  D-28359
   Germany

   Phone: +49-421-218-63921
   Email: cabo@tzi.org

   Peter van der Stok
   consultant

   Phone: +31-492474673 (Netherlands), +33-966015248 (France)
   Email: consultancy@vanderstok.org
   URI:   www.vanderstok.org

   Christian Amsuess (editor)
   Energy Harvesting Solutions
   Hollandstr. 12/4
   1020
   Austria

   Phone: +43-664-9790639
   Email: c.amsuess@energyharvesting.at