CoRE Resource Directory
draft-ietf-core-resource-directory-10
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (core WG)
|
|
Last updated |
|
2017-03-13
(latest revision 2016-10-31)
|
|
Replaces |
|
draft-shelby-core-resource-directory
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
WG Document
(wg milestone:
Mar 2018 - CoRE Resource Direct...
)
|
|
Document shepherd |
|
Jaime Jimenez
|
IESG |
IESG state |
|
AD is watching
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alexey Melnikov
|
|
Send notices to |
|
"Jaime Jimenez" <jaime.jimenez@ericsson.com>
|
CoRE Z. Shelby
Internet-Draft ARM
Intended status: Standards Track M. Koster
Expires: September 14, 2017 SmartThings
C. Bormann
Universitaet Bremen TZI
P. van der Stok
consultant
March 13, 2017
CoRE Resource Directory
draft-ietf-core-resource-directory-10
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 September 14, 2017.
Shelby, et al. Expires September 14, 2017 [Page 1]
Internet-Draft CoRE Resource Directory March 2017
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. Use Case: Cellular M2M . . . . . . . . . . . . . . . . . 6
3.2. Use Case: Home and Building Automation . . . . . . . . . 7
3.3. Use Case: Link Catalogues . . . . . . . . . . . . . . . . 7
4. Finding a Resource Directory . . . . . . . . . . . . . . . . 8
4.1. Resource Directory Address Option (RDAO) . . . . . . . . 9
5. Resource Directory . . . . . . . . . . . . . . . . . . . . . 10
5.1. Content Formats . . . . . . . . . . . . . . . . . . . . . 11
5.2. Base URI Discovery . . . . . . . . . . . . . . . . . . . 11
5.3. Registration . . . . . . . . . . . . . . . . . . . . . . 13
5.3.1. Simple Registration . . . . . . . . . . . . . . . . . 16
5.3.2. Simple publishing to Resource Directory Server . . . 17
5.3.3. Third-party registration . . . . . . . . . . . . . . 17
5.3.4. Plurality of link references in a Registration . . . 18
5.4. Operations on the Registration Resource . . . . . . . . . 18
5.4.1. Registration Update . . . . . . . . . . . . . . . . . 19
5.4.2. Registration Removal . . . . . . . . . . . . . . . . 21
5.4.3. Read Endpoint Links . . . . . . . . . . . . . . . . . 22
5.4.4. Update Endpoint Links . . . . . . . . . . . . . . . . 23
6. RD Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1. Register a Group . . . . . . . . . . . . . . . . . . . . 27
6.2. Group Removal . . . . . . . . . . . . . . . . . . . . . . 29
7. RD Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8. Security Considerations . . . . . . . . . . . . . . . . . . . 35
8.1. Endpoint Identification and Authentication . . . . . . . 35
Show full document text