--- 1/draft-ietf-6lo-lowpan-mib-01.txt 2014-07-26 01:14:30.967660657 -0700 +++ 2/draft-ietf-6lo-lowpan-mib-02.txt 2014-07-26 01:14:31.019661942 -0700 @@ -1,23 +1,23 @@ Internet Engineering Task Force J. Schoenwaelder Internet-Draft A. Sehgal Intended status: Standards Track Jacobs University -Expires: October 10, 2014 T. Tsou +Expires: January 26, 2015 T. Tsou Huawei Technologies (USA) C. Zhou Huawei Technologies - April 8, 2014 + July 25, 2014 Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) - draft-ietf-6lo-lowpan-mib-01 + draft-ietf-6lo-lowpan-mib-02 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs). Status of This Memo @@ -27,60 +27,66 @@ 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 October 10, 2014. + This Internet-Draft will expire on January 26, 2015. Copyright Notice Copyright (c) 2014 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 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2. The Internet-Standard Management Framework . . . . . . . . . . 3 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 2. The Internet-Standard Management Framework . . . . . . . . . 2 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 - 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25 - 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 + 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 + 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 10.2. Informative References . . . . . . . . . . . . . . . . . 25 - Appendix A. JSON Representation . . . . . . . . . . . . . . . . . 26 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing IPv6 over Low-Power Wireless Personal Area 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 For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the @@ -90,20 +96,45 @@ [RFC2580]. 3. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 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 reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer. The objects are defined twice, once to report the global statistics as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN layer statistics. The per interface statistics are optional to implement. The object identifier registration tree has the following structure: ---- lowpanMIB(1.3.6.1.2.1.XXXX) +---- lowpanNotifications(0) @@ -184,22 +215,30 @@ 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 patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) are not considered to be 6LoWPAN datagram by this specification. Other radio technologies may use different mechanisms to identify 6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link Control and Adaptation Protocol uses Channel Identifiers [I-D.ietf-6lo-btle]). - The following diagram illustrates the conceptual relationships - between the counters. + Figure 2 illustrates the conceptual relationships between the + 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 ^ v InDelivers -+- -+- OutRequests | | InDiscards <--+ | | | InCompOKs .-->| |-->. OutCompReqds InCompFails <--| | | +--> OutCompFails InCompReqds `<--+ +<--' OutCompOKs @@ -219,20 +258,22 @@ | | .<--+ OutMeshRequests | `-->| | OutMeshForwds | `-->| OutMeshTransmits | | InHdrErrors <--+ +--> OutDiscards | | InReceives -+- -+- OutTransmits ^ v interface layer + Figure 2: Conceptual Relationship between LOWPAN-MIB Counters + The fragmentation related counters have been modeled after the fragmentation related counters of the IP-MIB [RFC4293]. The discard 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 reason not covered by the other counters. The compression related counters provide insights into compression requests and in particular also compression related failures. Note that the diagram is conceptual in the sense that compression happens after reassembly for incoming 6LoWPAN datagrams and compression @@ -243,36 +284,36 @@ The mesh header processing related counters do not have an explicit discard counter. Implementations that do not support mesh forwarding MUST count the number of received 6LoWPAN datagrams with a MESH header (lowpanInMeshReceives) but they MUST NOT increment the lowpanInMeshReceives and lowpanInMeshDelivers counters if these 6LoWPAN datagrams are dropped. 5. Relationship to Other MIB Modules - The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], SNMPv2- - CONF [RFC2580], and IF-MIB [RFC2863]. + The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], + SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863]. 6. Definitions LOWPAN-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF -- RFC 2580 ifIndex FROM IF-MIB; -- RFC 2863 lowpanMIB MODULE-IDENTITY - LAST-UPDATED "201404080000Z" + LAST-UPDATED "201407250000Z" ORGANIZATION "Jacobs University Bremen" CONTACT-INFO "Juergen Schoenwaelder Jacobs University Bremen Email: j.schoenwaelder@jacobs-university.de Anuj Sehgal Jacobs University Bremen Email: s.anuj@jacobs-university.de @@ -292,21 +333,21 @@ Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info)." - REVISION "201404080000Z" + REVISION "201407250000Z" DESCRIPTION "Initial version, published as RFC XXXX." -- RFC Ed.: replace XXXX with RFC number and remove this note ::= { mib-2 XXXX } -- object definitions lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } @@ -1109,122 +1150,66 @@ [RFC4293]. Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, a Network of Excellence project (ICT-318488) supported by the European Commission under its Seventh Framework Programme. 10. References 10.1. Normative References - [RFC2119] Bradner, S., "Key words for use in - RFCs to Indicate Requirement Levels", - BCP 14, RFC 2119, March 1997. + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, March 1997. - [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., - and J. Schoenwaelder, Ed., "Structure - of Management Information Version 2 - (SMIv2)", STD 58, RFC 2578, - April 1999. + [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. + Schoenwaelder, Ed., "Structure of Management Information + Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. - [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., - and J. Schoenwaelder, Ed., "Textual - Conventions for SMIv2", STD 58, - RFC 2579, April 1999. + [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. + Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD + 58, RFC 2579, April 1999. - [RFC2580] McCloghrie, K., Perkins, D., and J. - Schoenwaelder, "Conformance Statements - for SMIv2", STD 58, RFC 2580, + [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, + "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. - [RFC4944] Montenegro, G., Kushalnagar, N., Hui, - J., and D. Culler, "Transmission of - IPv6 Packets over IEEE 802.15.4 + [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, + "Transmission of IPv6 Packets over IEEE 802.15.4 Networks", RFC 4944, September 2007. - [RFC2863] McCloghrie, K. and F. Kastenholz, "The - Interfaces Group MIB", RFC 2863, - June 2000. + [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group + MIB", RFC 2863, June 2000. 10.2. Informative References - [RFC3410] Case, J., Mundy, R., Partain, D., and - B. Stewart, "Introduction and - Applicability Statements for Internet- - Standard Management Framework", - RFC 3410, December 2002. - - [RFC4293] Routhier, S., "Management Information - Base for the Internet Protocol (IP)", - RFC 4293, April 2006. + [RFC2013] McCloghrie, K., "SNMPv2 Management Information Base for + the User Datagram Protocol using SMIv2", RFC 2013, + November 1996. - [RFC6643] Schoenwaelder, J., "Translation of - Structure of Management Information - Version 2 (SMIv2) MIB Modules to YANG - Modules", RFC 6643, July 2012. + [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, + "Introduction and Applicability Statements for Internet- + Standard Management Framework", RFC 3410, December 2002. - [I-D.ietf-6lo-btle] Nieminen, J., Savolainen, T., Isomaki, - M., Patil, B., Shelby, Z., and C. - Gomez, "Transmission of IPv6 Packets - over BLUETOOTH Low Energy", - draft-ietf-6lo-btle-00 (work in - progress), November 2013. + [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April + 2006. - [I-D.lhotka-netmod-yang-json] Lhotka, L., "Modeling JSON Text with - YANG", - draft-lhotka-netmod-yang-json-02 (work - in progress), September 2013. + [RFC4293] Routhier, S., "Management Information Base for the + Internet Protocol (IP)", RFC 4293, April 2006. -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 - module can be translated to YANG. Using the JSON representation of - data modeled in YANG defined in [I-D.lhotka-netmod-yang-json], the - objects defined in the MIB module can be represented in JSON as shown - below. The compact representation without any white space uses 468 - 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 - } - } - } + [I-D.ietf-6lo-btle] + Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., + Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets + over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-02 + (work in progress), June 2014. Authors' Addresses Juergen Schoenwaelder Jacobs University Campus Ring 1 Bremen 28759 Germany EMail: j.schoenwaelder@jacobs-university.de