YANG Object Universal Parsing Interface
draft-petrov-t2trg-youpi-01

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Yang Validation 8 errors, 3 warnings.
Additional URLs
- Yang catalog entry for youpi@2019-07-22.yang
- Yang impact analysis for draft-petrov-t2trg-youpi
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                                     I. Petrov, Ed.
Internet-Draft                                                    Acklio
Intended status: Informational                         November 04, 2019
Expires: May 7, 2020

                YANG Object Universal Parsing Interface
                    draft-petrov-t2trg-youpi-01

Abstract

   YANG Object Universal Parsing Interface (YOUPI) specification
   describes generic way to encode and decode binary data based on a
   YANG model for use of constrainted devices.  YOUPI is a generic
   mechanism designed for great flexibility, so that it can be adapted
   for any of the constainted devices.

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

Petrov                     Expires May 7, 2020                  [Page 1]
Internet-Draft                    YOUPI                    November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  YOUPI . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  YANG extentions . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Position  . . . . . . . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Bit positions . . . . . . . . . . . . . . . . . . . .   5
       2.2.2.  Cursor  . . . . . . . . . . . . . . . . . . . . . . .   5
       2.2.3.  Absolute position . . . . . . . . . . . . . . . . . .   5
       2.2.4.  Relative position . . . . . . . . . . . . . . . . . .   5
     2.3.  FieldIndex  . . . . . . . . . . . . . . . . . . . . . . .   6
     2.4.  Multiplier  . . . . . . . . . . . . . . . . . . . . . . .   6
     2.5.  Offset  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.6.  Units-subject . . . . . . . . . . . . . . . . . . . . . .   6
     2.7.  Data definitions  . . . . . . . . . . . . . . . . . . . .   6
       2.7.1.  Supported built-in type . . . . . . . . . . . . . . .   6
       2.7.2.  Leafs . . . . . . . . . . . . . . . . . . . . . . . .   7
       2.7.3.  Type min/max values . . . . . . . . . . . . . . . . .   7
       2.7.4.  Type fraction digits  . . . . . . . . . . . . . . . .   7
       2.7.5.  Containers  . . . . . . . . . . . . . . . . . . . . .   8
       2.7.6.  Condition . . . . . . . . . . . . . . . . . . . . . .   8
       2.7.7.  Lists . . . . . . . . . . . . . . . . . . . . . . . .   9
       2.7.8.  Enumerations as mappings  . . . . . . . . . . . . . .  10
       2.7.9.  Groupings . . . . . . . . . . . . . . . . . . . . . .  10
       2.7.10. Typedefs  . . . . . . . . . . . . . . . . . . . . . .  10
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  11
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .  11
   Appendix A.  Complete examples  . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   A huge number of very constraint IoT devices are expected to be
   coming to the market.  They are very constraint in terms of the MTU
   (sometimes as small as 10b per message).  As they are expected to be
   running for many years without the need for external energy, energy
   efficiency which is directly linked to the size of the payloads that
   need to be sent, is also very important.  For those devices JSON and
   even CBOR formats might be too wasteful in terms of payload size.
Show full document text