draft-ietf-roll-mpl-yang-00.txt   draft-ietf-roll-mpl-yang-01.txt 
roll P. van der Stok, Ed. roll P. van der Stok, Ed.
Internet-Draft consultant Internet-Draft consultant
Intended status: Standards Track March 10, 2017 Intended status: Standards Track March 30, 2018
Expires: September 11, 2017 Expires: October 1, 2018
A YANG model for Multicast Protocol for Low power and lossy Networks A YANG model for Multicast Protocol for Low power and lossy Networks
(MPL) (MPL)
draft-ietf-roll-mpl-yang-00 draft-ietf-roll-mpl-yang-01
Abstract Abstract
This document defines a YANG data model for management of Multicast This document defines a YANG data model for management of Multicast
Protocol for Low power and lossy Networks (MPL) implementations. The Protocol for Low power and lossy Networks (MPL) implementations. The
data model includes configuration data and state data. data model includes configuration data and state data.
Note Note
Discussion and suggestions for improvement are requested, and should Discussion and suggestions for improvement are requested, and should
be sent to roll@ietf.org. be sent to roll@ietf.org.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 11, 2017. This Internet-Draft will expire on October 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 3 1.1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 3
2. MPL model . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. MPL model . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. yang-mpl modules . . . . . . . . . . . . . . . . . . . . . . 5 3. SID file generation . . . . . . . . . . . . . . . . . . . . . 5
3.1. yang-mpl-domain module . . . . . . . . . . . . . . . . . 5 4. yang-mpl modules . . . . . . . . . . . . . . . . . . . . . . 8
3.2. yang-mpl-ops module . . . . . . . . . . . . . . . . . . . 8 4.1. yang-mpl-domain module . . . . . . . . . . . . . . . . . 8
3.3. yang-mpl-seeds module . . . . . . . . . . . . . . . . . . 12 4.2. yang-mpl-ops module . . . . . . . . . . . . . . . . . . . 11
3.4. yang-mpl-statistics module . . . . . . . . . . . . . . . 16 4.3. yang-mpl-seeds module . . . . . . . . . . . . . . . . . . 15
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 4.4. yang-mpl-statistics module . . . . . . . . . . . . . . . 19
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
6. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 7. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.1. Normative References . . . . . . . . . . . . . . . . . . 20 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2. Informative References . . . . . . . . . . . . . . . . . 21 8.1. Normative References . . . . . . . . . . . . . . . . . . 23
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21 8.2. Informative References . . . . . . . . . . . . . . . . . 24
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for management of This document defines a YANG [RFC6020] data model for management of
Multicast Protocol for Low power and lossy Networks (MPL) [RFC7731] Multicast Protocol for Low power and lossy Networks (MPL) [RFC7731]
implementations. The data model covers configuration of per- implementations. The data model covers configuration of MPL
interface MPL parameters. It also provides information about which parameters per interface. It also provides information about which
Multicast addresses are operationally used, and the seeds for which Multicast addresses are operationally used, and the seeds of the
packets are forwarded forwarded packets.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The following terms are defined in [RFC6241] and are not redefined The following terms are defined in [RFC6241] and are not redefined
here: here:
skipping to change at page 3, line 16 skipping to change at page 3, line 16
The following terms are defined in [RFC6020] and are not redefined The following terms are defined in [RFC6020] and are not redefined
here: here:
o data model o data model
o data node o data node
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC6020]. [RFC6020].
Terms like domain, seed, I, k, c are defined in [RFC7731]. Terms like message, domain, seed, I, k, c are defined in [RFC7731].
Mutiple copies of a message can be received or sent by a node.
1.1.1. Tree Diagrams 1.1.1. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
the YANG modules specified in this document. The meaning of the the YANG modules specified in this document. The meaning of the
symbols in these diagrams is as follows: symbols in these diagrams is as follows:
Brackets "[" and "]" enclose list keys. Brackets "[" and "]" enclose list keys.
Abbreviations before data node names: "rw" means configuration Abbreviations before data node names: "rw" means configuration
skipping to change at page 3, line 41 skipping to change at page 3, line 43
Parentheses enclose choice and case nodes, and case nodes are also Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
Ellipsis ("...") stands for contents of subtrees that are not Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
2. MPL model 2. MPL model
This document defines the YANG module "ietf-yang-mpl", which This document defines the YANG module "ietf-yang-mpl", which
specifies a data model for MPL servers. The model consists of the specifies a data model for MPL servers. The model is separated into
four modules which can be loaded independently to accommodate the
storage space to the wanted functionality. The model consists of the
following parts: (1) a "mpl-domain" part that describes the MPL- following parts: (1) a "mpl-domain" part that describes the MPL-
domains and associated Multicast addresses and the interfaces on domains and associated Multicast addresses and the interfaces on
which the Multicast addresses are enabled, (2) a "mpl-op" part that which the Multicast addresses are enabled, (2) a "mpl-op" part that
describes the parameters settings per seed, (3) a "mpl-seeds" part describes the parameters settings per seed, (3) a "mpl-seeds" part
that describes the MPL buffer contents and the Trickle timer values, that describes the MPL buffer contents and the Trickle timer values,
and (4) a "mpl-statistics" part that describes the number of lost and and (4) a "mpl-statistics" part that describes the number of lost and
correctly forwarded messages. The data model, divided in four correctly forwarded messages. The data model, divided in four
modules, has the following structure for MPL configuration per node: modules, has the following structure for MPL configuration per node:
module: ietf-yang-mpl-domain module: ietf-yang-mpl-domain
+--rw (single)? +--rw domain
+--:(mpl-domain) +--rw (single)?
| +--rw mpl-domain +--:(mpl-domain)
| +--rw domains* [domainID] | +--rw mpl-domain
| | +--rw domainID uint16 | +--rw domains* [domainID]
| | +--rw MClist* inet:ipv6-address | | +--rw domainID uint16
| +--rw addresses* [MCaddress] | | +--rw MClist* inet:ipv6-address
| +--rw MCaddress inet:ipv6-address | +--rw addresses* [MCaddress]
| +--rw interfaces* string | +--rw MCaddress inet:ipv6-address
+--:(mpl-single) | +--rw interfaces* string
+--rw mpl-single +--:(mpl-single)
+--rw MCaddresses* inet:ipv6-address +--rw mpl-single
+--rw MCaddresses* inet:ipv6-address
module: ietf-yang-mpl-ops module: ietf-yang-mpl-ops
+--rw mpl-ops +--rw mpl-ops
+--rw SE_LIFETIME? uint16 +--rw SE_LIFETIME? uint16
+--rw PROACTIVE_FORWARDING? boolean +--rw PROACTIVE_FORWARDING? boolean
+--rw SEED_SET_ENTRY_LIFETIME? uint64 +--rw SEED_SET_ENTRY_LIFETIME? uint64
+--rw mpl-parameter* [domainID] +--rw mpl-parameter* [domainID]
+--rw domainID uint16 +--rw domainID uint16
+--rw DATA_MESSAGE_IMIN? uint16 +--rw DATA_MESSAGE_IMIN? uint16
+--rw DATA_MESSAGE_IMAX? uint16 +--rw DATA_MESSAGE_IMAX? uint16
+--rw DATA_MESSAGE_K? uint16 +--rw DATA_MESSAGE_K? uint16
+--rw DATA_MESSAGE_TIMER_EXPIRATIONS? uint16 +--rw DATA_MESSAGE_TIMER_EXPIRATIONS? uint16
+--rw CONTROL_MESSAGE_IMIN? uint16 +--rw CONTROL_MESSAGE_IMIN? uint16
+--rw CONTROL_MESSAGE_IMAX? uint16 +--rw CONTROL_MESSAGE_IMAX? uint16
+--rw CONTROL_MESSAGE_K? uint16 +--rw CONTROL_MESSAGE_K? uint16
+--rw CONTROL_MESSAGE_TIMER_EXPIRATIONS? uint16 +--rw CONTROL_MESSAGE_TIMER_EXPIRATIONS? uint16
module: ietf-yang-mpl-seeds module: ietf-yang-mpl-seeds
+--ro mpl-seeds* [seedID domainID] +--ro mpl-seeds* [seedID domainID]
+--ro seedID uint64 +--ro seedID uint64
+--ro domainID uint16 +--ro domainID uint16
+--ro local? boolean +--ro local? boolean
+--ro generate-seqno? uint8 +--ro generate-seqno? uint8
+--ro life-time? uint64 +--ro life-time? uint64
+--ro min-seqno? uint8 +--ro min-seqno? uint8
+--ro data-number? uint8 +--ro data-number? uint8
+--ro control-number? uint8 +--ro control-number? uint8
+--ro buffered-messages* [seqno] +--ro buffered-messages* [seqno]
+--ro seqno uint8 +--ro seqno uint8
+--ro I? uint8 +--ro I? uint8
+--ro c? uint8 +--ro c? uint8
+--ro e? uint8 +--ro e? uint8
+--ro t? uint8 +--ro t? uint8
module: ietf-yang-mpl-statistics module: ietf-yang-mpl-statistics
+--ro mpl-statistics* [seedID domainID] +--ro mpl-statistics* [seedID domainID]
+--ro seedID uint64 +--ro seedID uint64
+--ro domainID uint16 +--ro domainID uint16
+--ro c-too-high? uint64 +--ro c-too-high? uint64
+--ro nr-forwarded? uint64 +--ro nr-forwarded? uint64
+--ro nr-of-messages-received? uint64 +--ro nr-of-messages-received? uint64
+--ro nr-of-copies-received? uint64 +--ro nr-of-copies-received? uint64
+--ro nr-of-messages-forwarded? uint64 +--ro nr-of-messages-forwarded? uint64
+--ro nr-of-copies-forwarded? uint64 +--ro nr-of-copies-forwarded? uint64
+--ro nr-of-refused? uint64 +--ro nr-of-refused? uint64
+--ro nr-of-missed? uint64 +--ro nr-of-missed? uint64
+--ro nr-of-notreceived? uint64 +--ro nr-of-notreceived? uint64
+--ro nr-of-inconsistent-data? uint64 +--ro nr-of-inconsistent-data? uint64
+--ro nr-of-consistent-data? uint64 +--ro nr-of-consistent-data? uint64
+--ro nr-of-consistent-control? uint64 +--ro nr-of-consistent-control? uint64
+--ro nr-of-inconsistent-control? uint64 +--ro nr-of-inconsistent-control? uint64
+--ro statistics-interval? uint64
+---x reset-statistics
3. yang-mpl modules 3. SID file generation
SID are allocated to the identifiers specified in the four modules.
Their values are:
SID Assigned to
--------- --------------------------------------------------
1004050 module ietf-yang-mpl-domain
1004051 data /ietf-yang-mpl-domain:domain
1004052 data /ietf-yang-mpl-domain:domain/mpl-domain
1004053 data /ietf-yang-mpl-domain:domain/mpl-domain/addresses
1004054 data /ietf-yang-mpl-domain:domain/mpl-domain
/addresses/MCaddress
1004055 data /ietf-yang-mpl-domain:domain/mpl-domain
/addresses/interfaces
1004056 data /ietf-yang-mpl-domain:domain/mpl-domain/domains
1004057 data /ietf-yang-mpl-domain:domain/mpl-domain
/domains/MClist
1004058 data /ietf-yang-mpl-domain:domain/mpl-domain
/domains/domainID
1004059 data /ietf-yang-mpl-domain:domain/mpl-single
1004060 data /ietf-yang-mpl-domain:domain/mpl-single
/MCaddresses
File ietf-yang-mpl-domain@2018-03-29.sid created
Number of SIDs available : 50
Number of SIDs used : 11
SID Assigned to
--------- --------------------------------------------------
1004100 module ietf-yang-mpl-ops
1004101 data /ietf-yang-mpl-ops:mpl-ops
1004102 data /ietf-yang-mpl-ops:mpl-ops/PROACTIVE_FORWARDING
1004103 data /ietf-yang-mpl-ops:mpl-ops
/SEED_SET_ENTRY_LIFETIME
1004104 data /ietf-yang-mpl-ops:mpl-ops/SE_LIFETIME
1004105 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
1004106 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/CONTROL_MESSAGE_IMAX
1004107 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/CONTROL_MESSAGE_IMIN
1004108 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/CONTROL_MESSAGE_K
1004109 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/CONTROL_MESSAGE_TIMER_EXPIRATIONS
1004110 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/DATA_MESSAGE_IMAX
1004111 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/DATA_MESSAGE_IMIN
1004112 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/DATA_MESSAGE_K
1004113 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter
/DATA_MESSAGE_TIMER_EXPIRATIONS
1004114 data /ietf-yang-mpl-ops:mpl-ops/mpl-parameter/domainID
File ietf-yang-mpl-ops@2018-03-29.sid created
Number of SIDs available : 50
Number of SIDs used : 15
SID Assigned to
--------- --------------------------------------------------
1004150 module ietf-yang-mpl-seeds
1004151 data /ietf-yang-mpl-seeds:mpl-seeds
1004152 data /ietf-yang-mpl-seeds:mpl-seeds/buffered-messages
1004153 data /ietf-yang-mpl-seeds:mpl-seeds
/buffered-messages/I
1004154 data /ietf-yang-mpl-seeds:mpl-seeds
/buffered-messages/c
1004155 data /ietf-yang-mpl-seeds:mpl-seeds
/buffered-messages/e
1004156 data /ietf-yang-mpl-seeds:mpl-seeds
/buffered-messages/seqno
1004157 data /ietf-yang-mpl-seeds:mpl-seeds
/buffered-messages/t
1004158 data /ietf-yang-mpl-seeds:mpl-seeds/control-number
1004159 data /ietf-yang-mpl-seeds:mpl-seeds/data-number
1004160 data /ietf-yang-mpl-seeds:mpl-seeds/domainID
1004161 data /ietf-yang-mpl-seeds:mpl-seeds/generate-seqno
1004162 data /ietf-yang-mpl-seeds:mpl-seeds/life-time
1004163 data /ietf-yang-mpl-seeds:mpl-seeds/local
1004164 data /ietf-yang-mpl-seeds:mpl-seeds/min-seqno
1004165 data /ietf-yang-mpl-seeds:mpl-seeds/seedID
File ietf-yang-mpl-seeds@2018-03-29.sid created
Number of SIDs available : 50
Number of SIDs used : 16
SID Assigned to
--------- --------------------------------------------------
1004200 module ietf-yang-mpl-statistics
1004201 data /ietf-yang-mpl-statistics:mpl-statistics
1004202 data /ietf-yang-mpl-statistics:mpl-statistics
/c-too-high
1004203 data /ietf-yang-mpl-statistics:mpl-statistics
/domainID
1004204 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-forwarded
1004205 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-consistent-control
1004206 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-consistent-data
1004207 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-copies-forwarded
1004208 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-copies-received
1004209 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-inconsistent-control
1004210 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-inconsistent-data
1004211 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-messages-forwarded
1004212 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-messages-received
1004213 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-missed
1004214 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-notreceived
1004215 data /ietf-yang-mpl-statistics:mpl-statistics
/nr-of-refused
1004216 data /ietf-yang-mpl-statistics:mpl-statistics
/reset-statistics
1004217 data /ietf-yang-mpl-statistics:mpl-statistics/seedID
1004218 data /ietf-yang-mpl-statistics:mpl-statistics
/statistics-interval
File ietf-yang-mpl-statistics@2018-03-29.sid created
Number of SIDs available : 50
Number of SIDs used : 19
4. yang-mpl modules
This section describes four yang modules. The model is based on the This section describes four yang modules. The model is based on the
MPL specification published in [RFC7731] and the specification of MPL specification published in [RFC7731] and the specification of
[RFC6206]. The identification of the interfaces follows the [RFC6206]. The identification of the interfaces follows the
specification of ietf-interfaces of [RFC7223]. specification of ietf-interfaces of [RFC7223].
The data model allows to set values to the parameters of the MPL The data model allows to set values to the parameters of the MPL
algorithm. This approach requires an active manager process to set algorithm. This approach requires an active manager process to set
the values without use of DHCP as described in: [RFC7774]. the values without use of DHCP as described in: [RFC7774].
The names of the four modules are: yang-mpl-domain, yang-mpl-ops, The names of the four modules are: yang-mpl-domain, yang-mpl-ops,
yang-mpl-seeds, and yang-mpl-statistics, described in subsections yang-mpl-seeds, and yang-mpl-statistics, described in subsections
with the same name. with the same name.
3.1. yang-mpl-domain module 4.1. yang-mpl-domain module
This modules describes (1) the MPL domains and the associated This module describes (1) the MPL domains and the associated
multicast addresses, and (2) the interfaces and the multicast multicast addresses, and (2) the interfaces and the multicast
addresses for which they are enabled. addresses for which they are enabled.
The model features a choice such that for constrained devices with The model features a choice such that for constrained devices with
only one "single" interface and only one "single" domain, the model only one "single" interface and only one "single" domain, the model
specifies a list of MC addresses for which the single interface is specifies a list of MC addresses for which the single interface is
enabled. enabled.
<CODE BEGINS>file "ietf-yang-mpl-domain@2016-10-25.yang" <CODE BEGINS>file "ietf-yang-mpl-domain@2018-03-29.yang"
module ietf-yang-mpl-domain { module ietf-yang-mpl-domain {
yang-version 1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-yang-mpl-domain"; "urn:ietf:params:xml:ns:yang:ietf-yang-mpl-domain";
prefix mpl; prefix mpl;
import ietf-inet-types{ import ietf-inet-types{
prefix inet; prefix inet;
} }
skipping to change at page 6, line 50 skipping to change at page 9, line 44
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2016-10-25" { revision "2018-03-29" {
description "Initial revision."; description "Initial revision.";
reference reference
"I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast "I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast
Protocol for Low power and lossy Networks (MPL)"; Protocol for Low power and lossy Networks (MPL)";
} }
container domain { container domain {
description description
"High level container containing the choice statement."; "High level container containing the choice statement.";
choice single { choice single {
skipping to change at page 8, line 30 skipping to change at page 11, line 23
"list of MC addresses belonging to one single "list of MC addresses belonging to one single
domain and interface."; domain and interface.";
} }
} // container mpl-simple } // container mpl-simple
} // choice simple } // choice simple
} // container module } // container module
} //module ietf-yang-mpl-domain } //module ietf-yang-mpl-domain
<CODE ENDS> <CODE ENDS>
3.2. yang-mpl-ops module 4.2. yang-mpl-ops module
This module models the operational aspects of MPL. Per domain MPL This module models the operational aspects of MPL. Per domain MPL
specifies four parameters I_MAX, I_MIN, K, and TIMER_EXPIRATIONs for specifies four parameters I_MAX, I_MIN, K, and TIMER_EXPIRATIONs for
data and control messages. The value of the MPL intervals are data and control messages. The value of the MPL intervals are
expressed in TUNIT. The entry SE_LIFETIME taken over from [RFC7774] expressed in TUNIT. The entry SE_LIFETIME taken over from [RFC7774]
fixes TUNIT to milliseconds. For very constrained devices with only fixes TUNIT to milliseconds. For very constrained devices with only
one domain there can be only one instance of mpl-parameter list. one domain there can be only one instance of mpl-parameter list.
<CODE BEGINS>file "ietf-yang-mpl-ops@2016-10-25.yang" <CODE BEGINS>file "ietf-yang-mpl-ops@2018-03-29.yang"
module ietf-yang-mpl-ops { module ietf-yang-mpl-ops {
yang-version 1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-yang-mpl-ops"; "urn:ietf:params:xml:ns:yang:ietf-yang-mpl-ops";
prefix mpl; prefix mpl;
organization organization
"IETF ROLL (Routing over Low power and lossy networks) "IETF ROLL (Routing over Low power and lossy networks)
Working Group"; Working Group";
contact contact
"WG Web: http://tools.ietf.org/wg/roll/ "WG Web: http://tools.ietf.org/wg/roll/
WG List: mailto:roll@ietf.org WG List: mailto:roll@ietf.org
WG Chair: Peter van der Stok WG Chair: Peter van der Stok
mailto:consultancy@vanderstok.org mailto:consultancy@vanderstok.org
WG Chair: Ines Robles WG Chair: Ines Robles
mailto:maria.ines.robles@ericsson.com mailto:maria.ines.robles@ericsson.com
Editor: Peter van der Stok Editor: Peter van der Stok
mailto:consultancy@vanderstok.org"; mailto:consultancy@vanderstok.org";
description description
skipping to change at page 9, line 39 skipping to change at page 12, line 31
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2016-10-25" { revision "2018-03-29" {
description "Initial revision."; description "Initial revision.";
reference reference
"I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast "I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast
Protocol for Low power and lossy Networks (MPL)"; Protocol for Low power and lossy Networks (MPL)";
} }
container mpl-ops { container mpl-ops {
description description
"Parameter settings for each MPL server and for each "Parameter settings for each MPL server and for each
individual domain of the server."; individual domain of the server.";
skipping to change at page 11, line 20 skipping to change at page 14, line 11
default 1; default 1;
description description
"The redundancy constant, as defined in [RFC6206], for "The redundancy constant, as defined in [RFC6206], for
MPL Data Message transmissions."; MPL Data Message transmissions.";
} }
leaf DATA_MESSAGE_TIMER_EXPIRATIONS{ leaf DATA_MESSAGE_TIMER_EXPIRATIONS{
type uint16; type uint16;
default 3; default 3;
description description
"The number of Trickle timer expirations that occur "The number of Trickle timer expirations, as defined
in [RFC7731], that occur
before terminating the Trickle algorithm's before terminating the Trickle algorithm's
retransmission of a given MPL Data Message."; retransmission of a given MPL Data Message.";
} }
leaf CONTROL_MESSAGE_IMIN{ leaf CONTROL_MESSAGE_IMIN{
type uint16; type uint16;
description description
"The minimum Trickle timer interval, as defined "The minimum Trickle timer interval, as defined
in [RFC6206], for MPL Control Message in [RFC6206], for MPL Control Message
transmissions."; transmissions.";
skipping to change at page 12, line 4 skipping to change at page 14, line 45
default 1; default 1;
description description
"The redundancy constant, as defined in [RFC6206], "The redundancy constant, as defined in [RFC6206],
for MPL Control Message transmissions."; for MPL Control Message transmissions.";
} }
leaf CONTROL_MESSAGE_TIMER_EXPIRATIONS{ leaf CONTROL_MESSAGE_TIMER_EXPIRATIONS{
type uint16; type uint16;
default 10; default 10;
description description
"The number of Trickle time expirations that occur "The number of Trickle time expirations,
as defined in [RFC7731], that occur
before terminating the Trickle algorithm before terminating the Trickle algorithm
for MPL Control Message transmissions."; for MPL Control Message transmissions.";
} }
} // list MPL-parameter } // list MPL-parameter
} // container MPL-ops } // container MPL-ops
} // module ietf-yang-mpl-ops } // module ietf-yang-mpl-ops
<CODE ENDS> <CODE ENDS>
3.3. yang-mpl-seeds module 4.3. yang-mpl-seeds module
This module specifies the current values of the operation of the MPL This module specifies the current values of the operation of the MPL
forwarder. The values are acquired by the client and set by the forwarder. The values are acquired by the client and set by the
server. The module specifies a set of message buffers, with a buffer server. The module specifies a set of message buffers, with a buffer
per seed and domain. In constrained devices there will be only one per seed and domain. In constrained devices there will be only one
domain, but probably multiple seeds. domain, but probably multiple seeds.
The message buffer contains a set of messages where each message is The message buffer contains a set of messages where each message is
uniquely identified by its sequence number and seed. The associated uniquely identified by its sequence number and seed. The associated
I, c, e, and t values indicate the progress of MPL with respect to I, c, e, and t values indicate the progress of MPL with respect to
this message, as specified in [RFC7731]. A forwarder sends and this message, as specified in [RFC7731]. A forwarder sends and
receives multiple copies of a message. When a forwarder has sent receives multiple copies of a message. When a forwarder has sent
(received) a copy of a message, the forwarder has sent (received) (received) a copy of a message, the forwarder has sent (received)
that message. that message.
For forwarders which are seeds, local has value true and seqno is the For forwarders which are seeds, local has value true and seqno is the
sequence number of the next message to send. sequence number of the next message to send.
<CODE BEGINS>file "ietf-yang-mpl-seeds@2016-10-25.yang" <CODE BEGINS>file "ietf-yang-mpl-seeds@2018-03-29.yang"
module ietf-yang-mpl-seeds { module ietf-yang-mpl-seeds {
yang-version 1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-yang-mpl-seeds"; "urn:ietf:params:xml:ns:yang:ietf-yang-mpl-seeds";
prefix mpl; prefix mpl;
organization organization
"IETF ROLL (Routing over Low power and lossy networks) "IETF ROLL (Routing over Low power and lossy networks)
Working Group"; Working Group";
skipping to change at page 13, line 34 skipping to change at page 16, line 29
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2016-10-25" { revision "2018-03-29" {
description "Initial revision."; description "Initial revision.";
reference reference
"I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast "I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast
Protocol for Low power and lossy Networks (MPL)"; Protocol for Low power and lossy Networks (MPL)";
} }
list mpl-seeds{ list mpl-seeds{
key "seedID domainID"; key "seedID domainID";
config false; config false;
description description
skipping to change at page 14, line 9 skipping to change at page 17, line 4
Seed information contains the message buffer contents and the Seed information contains the message buffer contents and the
operational values of I, c, sequence number and the life-times operational values of I, c, sequence number and the life-times
per message."; per message.";
leaf seedID{ leaf seedID{
type uint64; type uint64;
description description
"value uniquely identifies the MPL Seed within a MPL "value uniquely identifies the MPL Seed within a MPL
domain."; domain.";
} }
leaf domainID{ leaf domainID{
type uint16; type uint16;
description description
"together with seedID uniquely identifies buffer set."; "together with seedID uniquely identifies buffer set.";
} }
leaf local { leaf local {
type boolean; type boolean;
description description
"When local == TRUE, seed is located in this forwarder. "When local == TRUE, seed originated in this forwarder.
WHEN local == false, seed is located in different WHEN local == false, seed originated in different
forwarder."; forwarder.";
} }
leaf generate-seqno { leaf generate-seqno {
type uint8; type uint8;
description description
"Sequence number of next message to be generated by "Sequence number of next message to be generated by
this local seed."; this local seed.";
} }
skipping to change at page 15, line 30 skipping to change at page 18, line 24
leaf I{ leaf I{
type uint8; type uint8;
description description
"Current Trickle timer interval size in SE-LIFETIME "Current Trickle timer interval size in SE-LIFETIME
units."; units.";
} }
leaf c{ leaf c{
type uint8; type uint8;
description description
"number of times that copy of this message has been "number of times that a copy of this message has been
received in this interval."; received in this interval.";
} }
leaf e{ leaf e{
type uint8; type uint8;
description description
"number of Trickle time expirations since last "number of Trickle time expirations since last
Trickle timer reset."; Trickle timer reset.";
} }
skipping to change at page 16, line 4 skipping to change at page 18, line 44
leaf t{ leaf t{
type uint8; type uint8;
description description
" Time expressed in SE-LIFETIME units " Time expressed in SE-LIFETIME units
that message will be (is) forwarded"; that message will be (is) forwarded";
} }
} // list seed-timers } // list seed-timers
} // list MPL-seeds } // list MPL-seeds
} // module ietf-yang-mpl-seeds } // module ietf-yang-mpl-seeds
<CODE ENDS> <CODE ENDS>
3.4. yang-mpl-statistics module 4.4. yang-mpl-statistics module
This module specifies the operation of the MPL forwarder expressed in This module specifies the operation of the MPL forwarder expressed in
number of messages and copies. The values are acquired by the client number of messages and copies. The values are acquired by the client
and set by the server. Statistics are specified per seed and domain. and set by the server. Statistics are specified per seed and domain.
In constrained devices there will be only one domain, but probably In constrained devices there will be only one domain, but probably
multiple seeds. multiple seeds.
The parameter k determines how many copies of a message can be The parameter k determines how many copies of a message can be
forwarded. The counters c-too-high, nr-forwarded, and nr-not- forwarded. The counters c-too-high, nr-forwarded, and nr-not-
forwarded give insight in the consequences of the current value of k. forwarded give insight in the consequences of the current value of k.
The other counters give insight in the loss of messages caused by the The other counters give insight in the loss of messages caused by the
medium or forwarding delays. The inconsistent/consistent counters medium or forwarding delays. The inconsistent/consistent counters
indicate when consistent or inconsistent messages were received indicate when consistent or inconsistent messages were received
according to the definition of consistent in [RFC7731]. according to the definition of consistent in [RFC7731].
<CODE BEGINS>file "ietf-yang-mpl-statistics@2016-10-25.yang" <CODE BEGINS>file "ietf-yang-mpl-statistics@2018-03-29.yang"
module ietf-yang-mpl-statistics { module ietf-yang-mpl-statistics {
yang-version 1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-yang-mpl-statistics"; "urn:ietf:params:xml:ns:yang:ietf-yang-mpl-statistics";
prefix mpl; prefix mpl;
organization organization
"IETF ROLL (Routing over Low power and lossy networks) "IETF ROLL (Routing over Low power and lossy networks)
Working Group"; Working Group";
skipping to change at page 17, line 26 skipping to change at page 20, line 23
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2016-10-25" { revision "2018-03-29" {
description "Initial revision."; description "Initial revision.";
reference reference
"I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast "I-D:draft-ietf-roll-mpl-yang: A YANG model for Multicast
Protocol for Low power and lossy Networks (MPL)"; Protocol for Low power and lossy Networks (MPL)";
} }
list mpl-statistics{ list mpl-statistics{
key "seedID domainID"; key "seedID domainID";
config false; config false;
skipping to change at page 18, line 26 skipping to change at page 21, line 23
leaf nr-forwarded { leaf nr-forwarded {
type uint64; type uint64;
description description
"number of times copies are forwarded, while c <= k."; "number of times copies are forwarded, while c <= k.";
} }
leaf nr-of-messages-received{ leaf nr-of-messages-received{
type uint64; type uint64;
description description
"number of messages (one or more copies) received, "number of messages received,
must be smaller than or equal to seqno."; must be smaller than or equal to seqno.";
} }
leaf nr-of-copies-received{ leaf nr-of-copies-received{
type uint64; type uint64;
description description
"total number of message copies received."; "total number of message copies received.";
} }
leaf nr-of-messages-forwarded{ leaf nr-of-messages-forwarded{
type uint64; type uint64;
skipping to change at page 19, line 7 skipping to change at page 22, line 4
description description
"number of forwarded copies, can be larger than "number of forwarded copies, can be larger than
number-of-copies-received."; number-of-copies-received.";
} }
leaf nr-of-refused{ leaf nr-of-refused{
type uint64; type uint64;
description description
"number of refused copies because seqno too small."; "number of refused copies because seqno too small.";
} }
leaf nr-of-missed{ leaf nr-of-missed{
type uint64; type uint64;
description description
"number of messages that were not received "number of messages that were not received
(derived from gaps in received seqno's.)"; is equal to the number of empty message buffers
seqno < min-seqno.";
} }
leaf nr-of-notreceived{ leaf nr-of-notreceived{
type uint64; type uint64;
description description
"number of messages that were not received "number of messages that were not received
according to control message."; according to control message.";
} }
leaf nr-of-inconsistent-data{ leaf nr-of-inconsistent-data{
skipping to change at page 19, line 45 skipping to change at page 22, line 42
type uint64; type uint64;
description description
"number of consistent control messages."; "number of consistent control messages.";
} }
leaf nr-of-inconsistent-control{ leaf nr-of-inconsistent-control{
type uint64; type uint64;
description description
"number of inconsistent control messages."; "number of inconsistent control messages.";
} }
leaf statistics-interval{
type uint64;
description
"Interval, expressed in seconds, during which
the statistics are collected.";
}
action reset-statistics{
description
"set all statistics counters and
statistics-interval to zero.";
}
} // list mpl statistics } // list mpl statistics
} // module ietf-yang-mpl-statistics } // module ietf-yang-mpl-statistics
<CODE ENDS> <CODE ENDS>
4. IANA Considerations 5. IANA Considerations
This specification has no consequences for IANA. This specification has no consequences for IANA.
5. Acknowledgements 6. Acknowledgements
Andy Bierman has commented on the use of YANG for mpl. YANG doctors Andy Bierman has commented on the use of YANG for mpl. YANG doctors
pointed out a wrong use of config. pointed out a wrong use of config.
6. Changelog 7. Changelog
Changes from version 00 to version 01 Changes from version 00 to version 01
o config false in "statistics" and "seeds" modules o config false in "statistics" and "seeds" modules
o separated into 4 modules o separated into 4 modules
o inserted choice in domain modules o inserted choice in domain modules
o more explanatory text
o renamed some parameters o renamed some parameters
o Introduced section per module o Introduced section per module
7. References o reset of statistics is added
7.1. Normative References 8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<http://www.rfc-editor.org/info/rfc7223>. <https://www.rfc-editor.org/info/rfc7223>.
[RFC7731] Hui, J. and R. Kelsey, "Multicast Protocol for Low-Power [RFC7731] Hui, J. and R. Kelsey, "Multicast Protocol for Low-Power
and Lossy Networks (MPL)", RFC 7731, DOI 10.17487/RFC7731, and Lossy Networks (MPL)", RFC 7731, DOI 10.17487/RFC7731,
February 2016, <http://www.rfc-editor.org/info/rfc7731>. February 2016, <https://www.rfc-editor.org/info/rfc7731>.
7.2. Informative References 8.2. Informative References
[RFC6206] Levis, P., Clausen, T., Hui, J., Gnawali, O., and J. Ko, [RFC6206] Levis, P., Clausen, T., Hui, J., Gnawali, O., and J. Ko,
"The Trickle Algorithm", RFC 6206, DOI 10.17487/RFC6206, "The Trickle Algorithm", RFC 6206, DOI 10.17487/RFC6206,
March 2011, <http://www.rfc-editor.org/info/rfc6206>. March 2011, <https://www.rfc-editor.org/info/rfc6206>.
[RFC7774] Doi, Y. and M. Gillmore, "Multicast Protocol for Low-Power [RFC7774] Doi, Y. and M. Gillmore, "Multicast Protocol for Low-Power
and Lossy Networks (MPL) Parameter Configuration Option and Lossy Networks (MPL) Parameter Configuration Option
for DHCPv6", RFC 7774, DOI 10.17487/RFC7774, March 2016, for DHCPv6", RFC 7774, DOI 10.17487/RFC7774, March 2016,
<http://www.rfc-editor.org/info/rfc7774>. <https://www.rfc-editor.org/info/rfc7774>.
Author's Address Author's Address
Peter van der Stok (editor) Peter van der Stok (editor)
consultant consultant
Phone: +31-492474673 (Netherlands), +33-966015248 (France) Phone: +31-492474673 (Netherlands), +33-966015248 (France)
Email: consultancy@vanderstok.org Email: consultancy@vanderstok.org
URI: www.vanderstok.org URI: www.vanderstok.org
 End of changes. 59 change blocks. 
125 lines changed or deleted 285 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/