draft-ietf-6lo-lowpan-mib-01.txt   draft-ietf-6lo-lowpan-mib-02.txt 
Internet Engineering Task Force J. Schoenwaelder Internet Engineering Task Force J. Schoenwaelder
Internet-Draft A. Sehgal Internet-Draft A. Sehgal
Intended status: Standards Track Jacobs University Intended status: Standards Track Jacobs University
Expires: October 10, 2014 T. Tsou Expires: January 26, 2015 T. Tsou
Huawei Technologies (USA) Huawei Technologies (USA)
C. Zhou C. Zhou
Huawei Technologies Huawei Technologies
April 8, 2014 July 25, 2014
Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Definition of Managed Objects for IPv6 over Low-Power Wireless Personal
Area Networks (6LoWPANs) Area Networks (6LoWPANs)
draft-ietf-6lo-lowpan-mib-01 draft-ietf-6lo-lowpan-mib-02
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing IPv6 over Low-Power In particular, it defines objects for managing IPv6 over Low-Power
Wireless Personal Area Networks (6LoWPANs). Wireless Personal Area Networks (6LoWPANs).
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 http://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 October 10, 2014. This Internet-Draft will expire on January 26, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.1. Normative References . . . . . . . . . . . . . . . . . . 25 10.1. Normative References . . . . . . . . . . . . . . . . . . 25
10.2. Informative References . . . . . . . . . . . . . . . . . 25 10.2. Informative References . . . . . . . . . . . . . . . . . 25
Appendix A. JSON Representation . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular it defines
objects for managing IPv6 over Low-Power Wireless Personal Area objects for managing IPv6 over Low-Power Wireless Personal Area
Networks (6LoWPANs) [RFC4944]. Networks (6LoWPANs) [RFC4944].
While a MIB module provides a direct binding for accessing data via
the Simple Network Management Protocol (SNMP) [RFC3410], supporting
SNMP may not always be affordable on constrained devices. Other
protocols to access data modeled in MIB modules are possible and
proposals have been made recently to provide bindings to the
Constrained Application Protocol (CoAP) [RFC7252].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 3, line 35 skipping to change at page 3, line 13
[RFC2580]. [RFC2580].
3. Conventions 3. Conventions
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 RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
The left part of Figure 1 provides an overview of the protocols
typically used on constrained devices. The right part lists the MIB
modules providing monitoring and troubleshooting support ([RFC2013],
[RFC4292], [RFC4293], [RFC2863]). The LOWPAN-MIB defined in this
document fills a hole by providing monitoring and troubleshooting
support for the 6LoWPAN layer.
Protocol Layer MIB Modules
+---------------+
| CoAP |
+---------------+ +--------------------------+
| UDP | | UDP-MIB [RFC2013] |
+---------------+ +--------------------------+
| IPv6 | | IP-MIB [RFC4293] |
| ICMPv6 | | IP-FORWARD-MIB [RFC4292] |
+---------------+ +--------------------------+
| 6LoWPAN | | LOWPAN-MIB [RFCXXXX] |
+---------------+ +--------------------------+
| IF-MIB [RFC2863] |
+---------------+ +--------------------------+
| IEEE 802.15.4 |
+---------------+
Figure 1: Protocol Layers and MIB Modules
The LOWPAN-MIB module is primarily a collection of counters that The LOWPAN-MIB module is primarily a collection of counters that
reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer. reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer.
The objects are defined twice, once to report the global statistics The objects are defined twice, once to report the global statistics
as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN
layer statistics. The per interface statistics are optional to layer statistics. The per interface statistics are optional to
implement. The object identifier registration tree has the following implement. The object identifier registration tree has the following
structure: structure:
---- lowpanMIB(1.3.6.1.2.1.XXXX) ---- lowpanMIB(1.3.6.1.2.1.XXXX)
+---- lowpanNotifications(0) +---- lowpanNotifications(0)
skipping to change at page 5, line 32 skipping to change at page 5, line 35
dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a
6LoWPAN datagram is a datagram with a dispatch byte matching the bit 6LoWPAN datagram is a datagram with a dispatch byte matching the bit
patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch
byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame)
are not considered to be 6LoWPAN datagram by this specification. are not considered to be 6LoWPAN datagram by this specification.
Other radio technologies may use different mechanisms to identify Other radio technologies may use different mechanisms to identify
6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link 6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link
Control and Adaptation Protocol uses Channel Identifiers Control and Adaptation Protocol uses Channel Identifiers
[I-D.ietf-6lo-btle]). [I-D.ietf-6lo-btle]).
The following diagram illustrates the conceptual relationships Figure 2 illustrates the conceptual relationships between the
between the counters. counters. Implementations may choose to implement the processing of
6LoWPAN datagrams in a different order.
The generic InDiscards and OutDiscards counters can be incremented
anytime when 6LoWPAN datagrams are discarded due to reasons not
covered by the other more specific counters. For example, an
implementation discarding 6LoWPAN datagrams while all buffers are
used for ongoing packet reassemblies will increment the relevant
InDiscards counters for each discarded 6LoWPAN datagram.
IPv6 layer IPv6 layer
^ v ^ v
InDelivers -+- -+- OutRequests InDelivers -+- -+- OutRequests
| | | |
InDiscards <--+ | InDiscards <--+ |
| | | |
InCompOKs .-->| |-->. OutCompReqds InCompOKs .-->| |-->. OutCompReqds
InCompFails <--| | | +--> OutCompFails InCompFails <--| | | +--> OutCompFails
InCompReqds `<--+ +<--' OutCompOKs InCompReqds `<--+ +<--' OutCompOKs
skipping to change at page 6, line 37 skipping to change at page 6, line 37
| | .<--+ OutMeshRequests | | .<--+ OutMeshRequests
| `-->| | OutMeshForwds | `-->| | OutMeshForwds
| `-->| OutMeshTransmits | `-->| OutMeshTransmits
| | | |
InHdrErrors <--+ +--> OutDiscards InHdrErrors <--+ +--> OutDiscards
| | | |
InReceives -+- -+- OutTransmits InReceives -+- -+- OutTransmits
^ v ^ v
interface layer interface layer
Figure 2: Conceptual Relationship between LOWPAN-MIB Counters
The fragmentation related counters have been modeled after the The fragmentation related counters have been modeled after the
fragmentation related counters of the IP-MIB [RFC4293]. The discard fragmentation related counters of the IP-MIB [RFC4293]. The discard
counters have been placed at the end of the input and output chains counters have been placed at the end of the input and output chains
but they can be bumped any time if a datagram is discarded for a but they can be bumped any time if a datagram is discarded for a
reason not covered by the other counters. reason not covered by the other counters.
The compression related counters provide insights into compression The compression related counters provide insights into compression
requests and in particular also compression related failures. Note requests and in particular also compression related failures. Note
that the diagram is conceptual in the sense that compression happens that the diagram is conceptual in the sense that compression happens
after reassembly for incoming 6LoWPAN datagrams and compression after reassembly for incoming 6LoWPAN datagrams and compression
skipping to change at page 7, line 12 skipping to change at page 7, line 14
The mesh header processing related counters do not have an explicit The mesh header processing related counters do not have an explicit
discard counter. Implementations that do not support mesh forwarding discard counter. Implementations that do not support mesh forwarding
MUST count the number of received 6LoWPAN datagrams with a MESH MUST count the number of received 6LoWPAN datagrams with a MESH
header (lowpanInMeshReceives) but they MUST NOT increment the header (lowpanInMeshReceives) but they MUST NOT increment the
lowpanInMeshReceives and lowpanInMeshDelivers counters if these lowpanInMeshReceives and lowpanInMeshDelivers counters if these
6LoWPAN datagrams are dropped. 6LoWPAN datagrams are dropped.
5. Relationship to Other MIB Modules 5. Relationship to Other MIB Modules
The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], SNMPv2- The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578],
CONF [RFC2580], and IF-MIB [RFC2863]. SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863].
6. Definitions 6. Definitions
LOWPAN-MIB DEFINITIONS ::= BEGIN LOWPAN-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
ifIndex FROM IF-MIB; -- RFC 2863 ifIndex FROM IF-MIB; -- RFC 2863
lowpanMIB MODULE-IDENTITY lowpanMIB MODULE-IDENTITY
LAST-UPDATED "201404080000Z" LAST-UPDATED "201407250000Z"
ORGANIZATION ORGANIZATION
"Jacobs University Bremen" "Jacobs University Bremen"
CONTACT-INFO CONTACT-INFO
"Juergen Schoenwaelder "Juergen Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
Email: j.schoenwaelder@jacobs-university.de Email: j.schoenwaelder@jacobs-university.de
Anuj Sehgal Anuj Sehgal
Jacobs University Bremen Jacobs University Bremen
Email: s.anuj@jacobs-university.de Email: s.anuj@jacobs-university.de
skipping to change at page 8, line 15 skipping to change at page 8, line 15
Copyright (c) 2014 IETF Trust and the persons identified as Copyright (c) 2014 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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 to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)." (http://trustee.ietf.org/license-info)."
REVISION "201404080000Z" REVISION "201407250000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with RFC number and remove this note -- RFC Ed.: replace XXXX with RFC number and remove this note
::= { mib-2 XXXX } ::= { mib-2 XXXX }
-- object definitions -- object definitions
lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 }
lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 }
skipping to change at page 25, line 18 skipping to change at page 25, line 18
[RFC4293]. [RFC4293].
Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo,
a Network of Excellence project (ICT-318488) supported by the a Network of Excellence project (ICT-318488) supported by the
European Commission under its Seventh Framework Programme. European Commission under its Seventh Framework Programme.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
RFCs to Indicate Requirement Levels", Requirement Levels", BCP 14, RFC 2119, March 1997.
BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
and J. Schoenwaelder, Ed., "Structure Schoenwaelder, Ed., "Structure of Management Information
of Management Information Version 2 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
(SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
and J. Schoenwaelder, Ed., "Textual Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
Conventions for SMIv2", STD 58, 58, RFC 2579, April 1999.
RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Schoenwaelder, "Conformance Statements "Conformance Statements for SMIv2", STD 58, RFC 2580,
for SMIv2", STD 58, RFC 2580, April 1999.
April 1999.
[RFC4944] Montenegro, G., Kushalnagar, N., Hui, [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
J., and D. Culler, "Transmission of "Transmission of IPv6 Packets over IEEE 802.15.4
IPv6 Packets over IEEE 802.15.4 Networks", RFC 4944, September 2007.
Networks", RFC 4944, September 2007.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Interfaces Group MIB", RFC 2863, MIB", RFC 2863, June 2000.
June 2000.
10.2. Informative References 10.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and [RFC2013] McCloghrie, K., "SNMPv2 Management Information Base for
B. Stewart, "Introduction and the User Datagram Protocol using SMIv2", RFC 2013,
Applicability Statements for Internet- November 1996.
Standard Management Framework",
RFC 3410, December 2002.
[RFC4293] Routhier, S., "Management Information
Base for the Internet Protocol (IP)",
RFC 4293, April 2006.
[RFC6643] Schoenwaelder, J., "Translation of [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Structure of Management Information "Introduction and Applicability Statements for Internet-
Version 2 (SMIv2) MIB Modules to YANG Standard Management Framework", RFC 3410, December 2002.
Modules", RFC 6643, July 2012.
[I-D.ietf-6lo-btle] Nieminen, J., Savolainen, T., Isomaki, [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April
M., Patil, B., Shelby, Z., and C. 2006.
Gomez, "Transmission of IPv6 Packets
over BLUETOOTH Low Energy",
draft-ietf-6lo-btle-00 (work in
progress), November 2013.
[I-D.lhotka-netmod-yang-json] Lhotka, L., "Modeling JSON Text with [RFC4293] Routhier, S., "Management Information Base for the
YANG", Internet Protocol (IP)", RFC 4293, April 2006.
draft-lhotka-netmod-yang-json-02 (work
in progress), September 2013.
Appendix A. JSON Representation [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", RFC 7252, June 2014.
Using the translation algorithm defined in [RFC6643], the SMIv2 [I-D.ietf-6lo-btle]
module can be translated to YANG. Using the JSON representation of Nieminen, J., Savolainen, T., Isomaki, M., Patil, B.,
data modeled in YANG defined in [I-D.lhotka-netmod-yang-json], the Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets
objects defined in the MIB module can be represented in JSON as shown over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-02
below. The compact representation without any white space uses 468 (work in progress), June 2014.
octets. (Of course, this number depends on the number of octets
needed for the counter values.)
{
"LOWPAN-MIB:LOWPAN-MIB": {
"lowpanStats": {
"lowpanReasmTimeout": 20,
"lowpanInReceives": 42,
"lowpanInHdrErrors": 0,
"lowpanInMeshReceives": 8,
"lowpanInMeshForwds": 0,
"lowpanInMeshDelivers": 0,
"lowpanInReasmReqds": 22,
"lowpanInReasmFails": 2,
"lowpanInReasmOKs": 20,
"lowpanInCompReqds": 16,
"lowpanInCompFails": 2,
"lowpanInCompOKs": 14,
"lowpanInDiscards": 1,
"lowpanInDelivers": 12,
"lowpanOutRequests": 12,
"lowpanOutCompReqds": 0,
"lowpanOutCompFails": 0,
"lowpanOutCompOKs": 0,
"lowpanOutFragReqds": 5,
"lowpanOutFragFails": 0,
"lowpanOutFragOKs": 5,
"lowpanOutFragCreates": 8,
"lowpanOutMeshHopLimitExceeds": 0,
"lowpanOutMeshNoRoutes": 0,
"lowpanOutMeshRequests": 0,
"lowpanOutMeshForwds": 0,
"lowpanOutMeshTransmits": 0,
"lowpanOutDiscards": 0,
"lowpanOutTransmits": 15
}
}
}
Authors' Addresses Authors' Addresses
Juergen Schoenwaelder Juergen Schoenwaelder
Jacobs University Jacobs University
Campus Ring 1 Campus Ring 1
Bremen 28759 Bremen 28759
Germany Germany
EMail: j.schoenwaelder@jacobs-university.de EMail: j.schoenwaelder@jacobs-university.de
 End of changes. 24 change blocks. 
112 lines changed or deleted 97 lines changed or added

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