SenML Base Name Prefix Indication
draft-keranen-core-senml-base-prefix-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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                                         A. Keranen
Internet-Draft                                                  Ericsson
Intended status: Standards Track                              C. Amsuess
Expires: January 23, 2020                                  July 22, 2019

                   SenML Base Name Prefix Indication
                draft-keranen-core-senml-base-prefix-00

Abstract

   The Sensor Measurement Lists (SenML) media type uses globally unique
   names to facilitate information exchange across systems.  This
   requirement often leads to long names and hence large amount of data
   to be transmitted with each SenML Pack.  This document defines an
   efficient mechanism to indicate a globally unique prefix for names.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 23, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Keranen & Amsuess       Expires January 23, 2020                [Page 1]
Internet-Draft      SenML Base Name Prefix Indication          July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Indicating base name prefix . . . . . . . . . . . . . . . . .   3
     3.1.  IP address  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Request Base URI  . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Public key fingerprint  . . . . . . . . . . . . . . . . .   4
     3.4.  TLS PSK Identity  . . . . . . . . . . . . . . . . . . . .   5
     3.5.  CoRE Resource Directory endpoint ID . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The Sensor Measurement Lists (SenML) media type [RFC8428] indicates
   sources of information with globally unique names.  A SenML Pack can
   indicate "base names" ("bn" field) that are prefixed to all names
   ("n" fields) in the SenML Records where the "bn" appears and all
   subsequent records until a new base name is indicated.  Example of a
   SenML Pack with two sources of measurement data that share a base
   name is shown in Figure 1.

      [
        {"bn":"2001:db8:1234:5678::1/",
         "n":"temperature", "u":"Cel", "v":25.2},
        {"n":"humidity", "u":"%RH", "v":30}
      ]

           Figure 1: SenML Pack with two sources of measurements

   The base name construct enables indicating the globally unique part
   of the name only once for a set of Records.  However, the globally
   unique part still needs to be indicated in each Pack.  Since base
   name is often relatively long, in some scenarios it would be useful
   to be able to further compress or omit this information.

   Since the sender and receiver of a SenML Pack often share context
   information beyond what is in the SenML Pack, e.g., request URI when
   a RESTful protocol is used, sender IP address, or security
   association information.  This information can be used to assist
   constructing the globally unique part of a name.  However, the sender
   of the Pack needs to be able to indicate unambiguously what

Keranen & Amsuess       Expires January 23, 2020                [Page 2]
Internet-Draft      SenML Base Name Prefix Indication          July 2019

   information is used and how the name is generated from that
Show full document text