CoAP functionality expected in a LWM2M system
draft-jimenez-t2trg-coap-functionality-lwm2m-00

Document Type Active Internet-Draft (individual)
Last updated 2016-11-01
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)
Network Working Group                                         J. Jimenez
Internet-Draft                                                  Ericsson
Intended status: Informational                          October 31, 2016
Expires: May 4, 2017

             CoAP functionality expected in a LWM2M system
            draft-jimenez-t2trg-coap-functionality-lwm2m-00

Abstract

   This document provides a strawman summary of information that should
   be used for the LWM2M specification [LWM2M].  LWM2M is based on CoAP,
   on top of which it describes certain management interfaces and data
   models that go beyond the CoAP specifications itself.  However LWM2M
   does not describe all behavior that should be expected from
   implementations of the CoAP specifications.  This document attempts
   to clarify what should be present in a LWM2M system beyond what is
   specified in the LWM2M documents.  Additionally, this document also
   adds information about IPSO Objects [IPSO] and their usage with LWM2M
   as application protocol.

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 May 4, 2017.

Copyright 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

Jimenez                    Expires May 4, 2017                  [Page 1]
Internet-Draftdraft-jimenez-t2trg-coap-functionality-lwm2m  October 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Interaction Model . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Device and Manager configuration. . . . . . . . . . . . .   3
     3.2.  Device to Device configuration. . . . . . . . . . . . . .   4
     3.3.  Device to Application configuration.  . . . . . . . . . .   4
   4.  Data Model  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Web Linking . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Collaboration . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The current LWM2M protocol is probably the main Device Management
   protocol based on CoAP today.  It defines the application layer
   communication protocol between a LWM2M Server and a LWM2M Client,
   which is located in a LWM2M Device.

2.  Terminology

   The LWM2M Specification tends to use its own terminology for client,
   server, etc.  In this document, we use the existing terminology from
   [RFC7252].

   For example the use of LWM2M "Client" and "Server" and the roles they
   play has confused developers that are initiating on the protocol,
   mainly because a CoAP server runs on the device, just like a LWM2M
   client does.  Moreover, most LWM2M devices will often work both as
   client and server depending on the interfaces used, it would be good
   to explore the use of terms like "servients" for devices that
   regularly support both.

   Similarly, the reference to existing drafts of RFCs often can mislead
   the reader to believe that the full RFC has been implemented.  It
   would be better to state the support to an IETF CoRE WG document when
   applicable.

   For example, the Registration interface in LWM2M is based on the CoAP
   Resource Directory.  However, it is not sufficient to implement just

Jimenez                    Expires May 4, 2017                  [Page 2]
Show full document text