CoAP Delegated Observe
draft-cao-core-delegated-observe-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-27
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CORE WG                                                           Z. Cao
INTERNET-DRAFT                                                 R. Jadhav
Intended Status: Informational                                    Huawei
Expires: April 26, 2016                                                 
                                                        October 27, 2016

                         CoAP Delegated Observe
                  draft-cao-core-delegated-observe-00

Abstract

   This document discusses the scenarios for "delegated observe", in
   which a subscriber needs to register some resources on behalf of some
   other entities.   This document also presents a CoAP protocol
   extension for the delegated observe operation. 

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

 

Zhen Cao, et al.        Expires <April 26, 2016>                [Page 1]
INTERNET DRAFT      draft-cao-core-delegated-observe        <Issue Date>

Copyright and License Notice

   Copyright (c) 2016 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 Scenarios for Delegated Observe  . . . . . . . . . . . . . . . .  3
     2.1 Multiple Devices . . . . . . . . . . . . . . . . . . . . . .  3
     2.2 Delegation to Cloud  . . . . . . . . . . . . . . . . . . . .  3
     2.3 Multicast  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3 Overview of Delegated Observe  . . . . . . . . . . . . . . . . .  4
   4 The Delegated Observe Option . . . . . . . . . . . . . . . . . .  5
   5  Handling Delegated Observe  . . . . . . . . . . . . . . . . . .  6
   6  Security Considerations . . . . . . . . . . . . . . . . . . . .  6
   7  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  6
   7  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
   Appendix A.  Examples  . . . . . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

 

Zhen Cao, et al.        Expires <April 26, 2016>                [Page 2]
INTERNET DRAFT      draft-cao-core-delegated-observe        <Issue Date>

1  Introduction

   CoAP [RFC7252] is a light-weight application protocol for constrained
   networks.  To avoid keeping polling devices, CoAP supports the
   'observe' operation defined in [RFC7641], in which a subscriber can
   register its interest to certain resources and then be updated with
   their representation.  However, in the current "observe" protocol,
   the subscriber can only register interests on behalf of itself, and
   therefore, updated information of the represented resources could not
   be notified to any parties other than the one who sends the observe
   request.

   This document discusses the scenarios for "delegated observation", in
   which a subscriber needs to register some resources on behalf of
   other entities or a group of entities including itself.   This
   document also presents a CoAP protocol extension for the delegated
   observe operation. 

2 Scenarios for Delegated Observe

   This section describes scenarios that needs delegated observe. 

2.1 Multiple Devices 

   In a typical smart home network setup, a user with multiple devices
   wants to observe some sensor resource (e.g., thermometer, bulbs). 
Show full document text