draft-ietf-6lo-lowpan-mib-04.txt   rfc7388.txt 
Internet Engineering Task Force J. Schoenwaelder Internet Engineering Task Force (IETF) J. Schoenwaelder
Internet-Draft A. Sehgal Request for Comments: 7388 A. Sehgal
Intended status: Standards Track Jacobs University Category: Standards Track Jacobs University
Expires: March 9, 2015 T. Tsou ISSN: 2070-1721 T. Tsou
Huawei Technologies (USA)
C. Zhou C. Zhou
Huawei Technologies Huawei Technologies
September 5, 2014 October 2014
Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Definition of Managed Objects for
Area Networks (6LoWPANs) IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)
draft-ietf-6lo-lowpan-mib-04
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it defines objects for managing IPv6 over community. In particular, it defines objects for managing IPv6 over
Low-Power Wireless Personal Area Networks (6LoWPANs). Low-Power Wireless Personal Area Networks (6LoWPANs).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on March 9, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7388.
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction ....................................................2
2. The Internet-Standard Management Framework . . . . . . . . . 2 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 . . . . . . . . . . . . . . . . . . . . . 25 8. IANA Considerations ............................................25
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 9. References .....................................................25
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 9.1. Normative References ......................................25
10.1. Normative References . . . . . . . . . . . . . . . . . . 25 9.2. Informative References ....................................26
10.2. Informative References . . . . . . . . . . . . . . . . . 26 Acknowledgements ..................................................27
Authors' Addresses ................................................27
1. Introduction 1. Introduction
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols. In particular it (MIB) for use with network management protocols. In particular it
defines objects for managing IPv6 over Low-Power Wireless Personal defines objects for managing IPv6 over Low-Power Wireless Personal
Area Networks (6LoWPANs) [RFC4944]. Area Networks (6LoWPANs) [RFC4944].
While a MIB module provides a direct binding for accessing data via While a MIB module provides a direct binding for accessing data via
the Simple Network Management Protocol (SNMP) [RFC3410], supporting the Simple Network Management Protocol (SNMP) [RFC3410], supporting
skipping to change at page 3, line 9 skipping to change at page 3, line 9
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This document specifies a Structure of Management Information (SMI). This document specifies a
MIB module that is compliant to the SMIv2, which is described in STD MIB module that is compliant to the SMIv2, which is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580]. 2580 [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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in BCP
2119 [RFC2119]. 14, RFC 2119 [RFC2119].
4. Overview 4. Overview
The left part of Figure 1 provides an overview of the IETF protocols The left part of Figure 1 provides an overview of the IETF protocols
designed for constrained devices. The right part lists the MIB designed for constrained devices. The right part lists the MIB
modules providing monitoring and troubleshooting support ([RFC4113], modules providing monitoring and troubleshooting support ([RFC4113],
[RFC4292], [RFC4293], [RFC2863]). The LOWPAN-MIB defined in this [RFC4292], [RFC4293], and [RFC2863]). The LOWPAN-MIB defined in this
document fills a hole by providing monitoring and troubleshooting document fills a hole by providing monitoring and troubleshooting
support for the 6LoWPAN layer. support for the 6LoWPAN layer.
Protocol Layer MIB Modules Protocol Layer MIB Modules
+--------------------+ +--------------------+
| CoAP [RFC7252] | | CoAP [RFC7252] |
+--------------------+ +--------------------------+ +--------------------+ +--------------------------+
| UDP [RFC0768] | | UDP-MIB [RFC4113] | | UDP [RFC0768] | | UDP-MIB [RFC4113] |
+--------------------+ +--------------------------+ +--------------------+ +--------------------------+
| IPv6 [RFC2460] | | IP-MIB [RFC4293] | | IPv6 [RFC2460] | | IP-MIB [RFC4293] |
| ICMPv6 [RFC4443] | | IP-FORWARD-MIB [RFC4292] | | ICMPv6 [RFC4443] | | IP-FORWARD-MIB [RFC4292] |
+--------------------+ +--------------------------+ +--------------------+ +--------------------------+
| 6LoWPAN [RFC4944] | | LOWPAN-MIB [RFCXXXX] | | 6LoWPAN [RFC4944] | | LOWPAN-MIB [RFC7388] |
+--------------------+ +--------------------------+ +--------------------+ +--------------------------+
| IF-MIB [RFC2863] | | IF-MIB [RFC2863] |
+--------------------+ +--------------------------+ +--------------------+ +--------------------------+
| IEEE 802.15.4, ... | | IEEE 802.15.4, ... |
+--------------------+ +--------------------+
/* RFC Ed.: replace XXXX above with RFC number
and remove this note */
Figure 1: Protocol Layers and MIB Modules 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:
/* RFC Ed.: replace XXXX below with IANA assigned OID number ---- lowpanMIB(1.3.6.1.2.1.226)
and remove this note */
---- lowpanMIB(1.3.6.1.2.1.XXXX)
+---- lowpanNotifications(0) +---- lowpanNotifications(0)
+---- lowpanObjects(1) +---- lowpanObjects(1)
| +---- lowpanStats(1) | +---- lowpanStats(1)
| | +--r- lowpanReasmTimeout(1) Unsigned32 | | +--r- lowpanReasmTimeout(1) Unsigned32
| | +--r- lowpanInReceives(2) Counter32 | | +--r- lowpanInReceives(2) Counter32
| | +--r- lowpanInHdrErrors(3) Counter32 | | +--r- lowpanInHdrErrors(3) Counter32
| | +--r- lowpanInMeshReceives(4) Counter32 | | +--r- lowpanInMeshReceives(4) Counter32
| | +--r- lowpanInMeshForwds(5) Counter32 | | +--r- lowpanInMeshForwds(5) Counter32
| | +--r- lowpanInMeshDelivers(6) Counter32 | | +--r- lowpanInMeshDelivers(6) Counter32
| | +--r- lowpanInReasmReqds(7) Counter32 | | +--r- lowpanInReasmReqds(7) Counter32
skipping to change at page 5, line 29 skipping to change at page 5, line 29
| +--r- lowpanIfOutTransmits(29) Counter32 | +--r- lowpanIfOutTransmits(29) Counter32
+---- lowpanConformance(2) +---- lowpanConformance(2)
+---- lowpanGroups(1) +---- lowpanGroups(1)
| +---- lowpanStatsGroup(1) | +---- lowpanStatsGroup(1)
| +---- lowpanStatsMeshGroup(2) | +---- lowpanStatsMeshGroup(2)
| +---- lowpanIfStatsGroup(3) | +---- lowpanIfStatsGroup(3)
| +---- lowpanIfStatsMeshGroup(4) | +---- lowpanIfStatsMeshGroup(4)
+---- lowpanCompliances(2) +---- lowpanCompliances(2)
+---- lowpanCompliance(1) +---- lowpanCompliance(1)
Figure 2: Object Identifier Registration Tree
The counters defined in the LOWPAN-MIB module provide information The counters defined in the LOWPAN-MIB module provide information
about the 6LoWPAN datagrams received and transmitted and how they are about the 6LoWPAN datagrams received and transmitted and how they are
processed in the 6LoWPAN layer. For link-layers that use the 6LoWPAN processed in the 6LoWPAN layer. For link layers that use the 6LoWPAN
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 datagrams 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]). [IPV6-BTLE]).
The Case Diagram [CASE] in Figure 2 illustrates the conceptual The Case Diagram [CASE] in Figure 3 illustrates the conceptual
relationships between the counters. Implementations may choose to relationships between the counters. Implementations may choose to
implement the processing of 6LoWPAN datagrams in a different order. implement the processing of 6LoWPAN datagrams in a different order.
The generic InDiscards and OutDiscards counters can be incremented The generic InDiscards and OutDiscards counters can be incremented
anytime when 6LoWPAN datagrams are discarded due to reasons not anytime 6LoWPAN datagrams are discarded due to reasons not covered by
covered by the other more specific counters. For example, an the other more specific counters. For example, an implementation
implementation discarding 6LoWPAN datagrams while all buffers are discarding 6LoWPAN datagrams while all buffers are used for ongoing
used for ongoing packet reassemblies will increment the relevant packet reassemblies will increment the relevant InDiscards counters
InDiscards counters for each discarded 6LoWPAN datagram. 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 40
| | .<--+ 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 Figure 3: 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, compression-related failures. Note that
that the diagram is conceptual in the sense that compression happens the diagram is conceptual in the sense that compression happens after
after reassembly for incoming 6LoWPAN datagrams and compression reassembly for incoming 6LoWPAN datagrams, and compression happens
happens before fragmentation for outgoing 6LoWPAN datagrams. before fragmentation for outgoing 6LoWPAN datagrams. Implementations
Implementations may choose to implement things slightly differently. may choose to implement things slightly differently. For example,
For example, implementations may decompress FRAG1 fragments as soon implementations may decompress FRAG1 fragments as soon as they are
as they are received, not waiting for reassembly to complete. received, not waiting for reassembly to complete.
The mesh header processing related counters do not have an explicit The counters related to MESH header processing do not have an
discard counter. Implementations that do not support mesh forwarding explicit discard counter. Implementations that do not support mesh
MUST count the number of received 6LoWPAN datagrams with a MESH forwarding MUST count the number of received 6LoWPAN datagrams with a
header (lowpanInMeshReceives) but they MUST NOT increment the MESH 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], The MIB module imports definitions from SNMPv2-SMI [RFC2578],
SNMPv2-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 "201409050000Z" LAST-UPDATED "201410100000Z" -- October 10, 2014
ORGANIZATION ORGANIZATION
"IETF IPv6 over Networks of Resource-constrained Nodes "IETF IPv6 over Networks of Resource-constrained Nodes
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG Email: 6lo@ietf.org "WG Email: 6lo@ietf.org
WG Web: http://tools.ietf.org/wg/6lo/ WG Web: http://tools.ietf.org/wg/6lo/
Juergen Schoenwaelder Juergen Schoenwaelder
Jacobs University Bremen Jacobs University Bremen
Email: j.schoenwaelder@jacobs-university.de Email: j.schoenwaelder@jacobs-university.de
skipping to change at page 8, line 20 skipping to change at page 8, line 22
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 "201409050000Z" REVISION "201410100000Z" -- October 10, 2014
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC 7388."
-- RFC Ed.: replace XXXX with RFC number and remove this note
::= { mib-2 YYYY } ::= { mib-2 226 }
-- RFC Ed.: replace YYYY with IANA assigned number
-- object definitions -- object definitions
lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 }
lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 }
lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 }
lowpanStats OBJECT IDENTIFIER ::= { lowpanObjects 1 } lowpanStats OBJECT IDENTIFIER ::= { lowpanObjects 1 }
lowpanReasmTimeout OBJECT-TYPE lowpanReasmTimeout OBJECT-TYPE
skipping to change at page 9, line 30 skipping to change at page 9, line 32
DESCRIPTION DESCRIPTION
"The number of received 6LoWPAN datagrams with a MESH "The number of received 6LoWPAN datagrams with a MESH
header." header."
::= { lowpanStats 4 } ::= { lowpanStats 4 }
lowpanInMeshForwds OBJECT-TYPE lowpanInMeshForwds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received 6LoWPAN datagrams requiring MESH "The number of received 6LoWPAN datagrams requiring mesh
forwarding." forwarding."
::= { lowpanStats 5 } ::= { lowpanStats 5 }
lowpanInMeshDelivers OBJECT-TYPE lowpanInMeshDelivers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received 6LoWPAN datagrams with a MESH header "The number of received 6LoWPAN datagrams with a MESH header
delivered to the local system." delivered to the local system."
::= { lowpanStats 6 } ::= { lowpanStats 6 }
lowpanInReasmReqds OBJECT-TYPE lowpanInReasmReqds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received 6LoWPAN fragments that needed to "The number of received 6LoWPAN fragments that needed to
be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN
datagrams." datagrams."
::= { lowpanStats 7 } ::= { lowpanStats 7 }
lowpanInReasmFails OBJECT-TYPE lowpanInReasmFails OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of failures detected by the re-assembly "The number of failures detected by the re-assembly
algorithm (e.g., timeouts). Note that this is not algorithm (e.g., timeouts). Note that this is not
necessarily a count of discarded 6LoWPAN fragments necessarily a count of discarded 6LoWPAN fragments
since implementations can lose track of the number since implementations can lose track of the number
of fragments by combining them as received." of fragments by combining them as received."
::= { lowpanStats 8 } ::= { lowpanStats 8 }
lowpanInReasmOKs OBJECT-TYPE lowpanInReasmOKs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 11, line 10 skipping to change at page 11, line 19
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams where header decompression "The number of 6LoWPAN datagrams where header decompression
was successful." was successful."
::= { lowpanStats 12 } ::= { lowpanStats 12 }
lowpanInDiscards OBJECT-TYPE lowpanInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received 6LoWPAN datagrams for which no "The number of received 6LoWPAN datagrams that were
discarded (e.g., for lack of buffer space) even though no
problems were encountered to prevent their continued problems were encountered to prevent their continued
processing, but were discarded (e.g., for lack of buffer processing. Note that this counter does not include any
space). Note that this counter does not include any
datagrams discarded due to a reassembly failure or a datagrams discarded due to a reassembly failure or a
compression failure." compression failure."
::= { lowpanStats 13 } ::= { lowpanStats 13 }
lowpanInDelivers OBJECT-TYPE lowpanInDelivers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of IPv6 packets successfully delivered "The total number of IPv6 packets successfully delivered
skipping to change at page 12, line 47 skipping to change at page 13, line 7
"The number of IPv6 packets that have been successfully "The number of IPv6 packets that have been successfully
fragmented." fragmented."
::= { lowpanStats 21 } ::= { lowpanStats 21 }
lowpanOutFragCreates OBJECT-TYPE lowpanOutFragCreates OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN fragments that have been "The number of 6LoWPAN fragments that have been
generated as a result of fragmentation. This includes generated as a result of fragmentation. This includes
both FRAG1 and FRAGN 6LoWPAN datagrams." both FRAG1 and FRAGN 6LoWPAN datagrams."
::= { lowpanStats 22 } ::= { lowpanStats 22 }
lowpanOutMeshHopLimitExceeds OBJECT-TYPE lowpanOutMeshHopLimitExceeds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams with a MESH header that "The number of 6LoWPAN datagrams with a MESH header that
were dropped because the hop limit has been exceeded." were dropped because the hop limit was exceeded."
::= { lowpanStats 23 } ::= { lowpanStats 23 }
lowpanOutMeshNoRoutes OBJECT-TYPE lowpanOutMeshNoRoutes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams with a MESH header that "The number of 6LoWPAN datagrams with a MESH header that
were dropped because there was no forwarding information were dropped because there was no forwarding information
available." available."
skipping to change at page 14, line 5 skipping to change at page 14, line 14
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams with a MESH header "The number of 6LoWPAN datagrams with a MESH header
created." created."
::= { lowpanStats 27 } ::= { lowpanStats 27 }
lowpanOutDiscards OBJECT-TYPE lowpanOutDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of IPv6 packets for which no problem was "The number of IPv6 packets that were discarded (e.g.,
for lack of buffer space) even though no problem was
encountered to prevent their transmission to their encountered to prevent their transmission to their
destination, but were discarded (e.g., for lack of destination."
buffer space)."
::= { lowpanStats 28 } ::= { lowpanStats 28 }
lowpanOutTransmits OBJECT-TYPE lowpanOutTransmits OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of 6LoWPAN datagram that this entity "The total number of 6LoWPAN datagram that this entity
supplied to the lower layers for transmission." supplied to the lower layers for transmission."
::= { lowpanStats 29 } ::= { lowpanStats 29 }
lowpanIfStatsTable OBJECT-TYPE lowpanIfStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF LowpanIfStatsEntry SYNTAX SEQUENCE OF LowpanIfStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table providing per interface statistics." "A table providing per-interface statistics."
::= { lowpanObjects 2 } ::= { lowpanObjects 2 }
lowpanIfStatsEntry OBJECT-TYPE lowpanIfStatsEntry OBJECT-TYPE
SYNTAX LowpanIfStatsEntry SYNTAX LowpanIfStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry providing statistics for a specific interface." "An entry providing statistics for a specific interface."
INDEX { ifIndex } INDEX { ifIndex }
::= { lowpanIfStatsTable 1 } ::= { lowpanIfStatsTable 1 }
skipping to change at page 16, line 7 skipping to change at page 16, line 16
"The number of 6LoWPAN datagrams received on this "The number of 6LoWPAN datagrams received on this
interface that were discarded due to errors in interface that were discarded due to errors in
their headers, including unknown dispatch values." their headers, including unknown dispatch values."
::= { lowpanIfStatsEntry 3 } ::= { lowpanIfStatsEntry 3 }
lowpanIfInMeshReceives OBJECT-TYPE lowpanIfInMeshReceives OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams reveived on this "The number of 6LoWPAN datagrams received on this
interface with a MESH header." interface with a MESH header."
::= { lowpanIfStatsEntry 4 } ::= { lowpanIfStatsEntry 4 }
lowpanIfInMeshForwds OBJECT-TYPE lowpanIfInMeshForwds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams received on this "The number of 6LoWPAN datagrams received on this
interface requiring MESH forwarding." interface requiring mesh forwarding."
::= { lowpanIfStatsEntry 5 } ::= { lowpanIfStatsEntry 5 }
lowpanIfInMeshDelivers OBJECT-TYPE lowpanIfInMeshDelivers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams received on this "The number of 6LoWPAN datagrams received on this
interface with a MESH header delivered to the local interface with a MESH header delivered to the local
system." system."
::= { lowpanIfStatsEntry 6 } ::= { lowpanIfStatsEntry 6 }
lowpanIfInReasmReqds OBJECT-TYPE lowpanIfInReasmReqds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN fragments received on this "The number of 6LoWPAN fragments received on this
interface that needed to be reassembled. This interface that needed to be reassembled. This
includes both FRAG1 and FRAGN 6LoWPAN datagrams." includes both FRAG1 and FRAGN 6LoWPAN datagrams."
::= { lowpanIfStatsEntry 7 } ::= { lowpanIfStatsEntry 7 }
lowpanIfInReasmFails OBJECT-TYPE lowpanIfInReasmFails OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of failures detected by the re-assembly "The number of failures detected by the reassembly
algorithm (e.g., timeouts) for datagrams received algorithm (e.g., timeouts) for datagrams received
on this interface. Note that this is not necessarily on this interface. Note that this is not necessarily
a count of discarded 6LoWPAN fragments since a count of discarded 6LoWPAN fragments since
implementations can lose track of the number implementations can lose track of the number
of fragments by combining them as received." of fragments by combining them as received."
::= { lowpanIfStatsEntry 8 } ::= { lowpanIfStatsEntry 8 }
lowpanIfInReasmOKs OBJECT-TYPE lowpanIfInReasmOKs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 49 skipping to change at page 18, line 11
"The number of 6LoWPAN datagrams received on this "The number of 6LoWPAN datagrams received on this
interface where header decompression was successful." interface where header decompression was successful."
::= { lowpanIfStatsEntry 12 } ::= { lowpanIfStatsEntry 12 }
lowpanIfInDiscards OBJECT-TYPE lowpanIfInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams received on this "The number of 6LoWPAN datagrams received on this
interface for which no problems were encountered to interface that were discarded (e.g., for lack of buffer
prevent their continued processing, but were discarded space) even though no problems were encountered to
(e.g., for lack of buffer space). Note that this prevent their continued processing. Note that this
counter does not include any datagrams discarded due counter does not include any datagrams discarded due
to a reassembly failure or a compression failure." to a reassembly failure or a compression failure."
::= { lowpanIfStatsEntry 13 } ::= { lowpanIfStatsEntry 13 }
lowpanIfInDelivers OBJECT-TYPE lowpanIfInDelivers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of IPv6 packets received on this "The total number of IPv6 packets received on this
skipping to change at page 19, line 43 skipping to change at page 20, line 7
interface that have been successfully fragmented." interface that have been successfully fragmented."
::= { lowpanIfStatsEntry 21 } ::= { lowpanIfStatsEntry 21 }
lowpanIfOutFragCreates OBJECT-TYPE lowpanIfOutFragCreates OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN fragments that have been "The number of 6LoWPAN fragments that have been
generated on this interface as a result of generated on this interface as a result of
fragmentation. This includes both FRAG1 and FRAGN fragmentation. This includes both FRAG1 and FRAGN
6LoWPAN datagrams." 6LoWPAN datagrams."
::= { lowpanIfStatsEntry 22 } ::= { lowpanIfStatsEntry 22 }
lowpanIfOutMeshHopLimitExceeds OBJECT-TYPE lowpanIfOutMeshHopLimitExceeds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams to be sent on this "The number of 6LoWPAN datagrams to be sent on this
interface with a MESH header that were dropped interface with a MESH header that were dropped
because the hop limit has been exceeded." because the hop limit was exceeded."
::= { lowpanIfStatsEntry 23 } ::= { lowpanIfStatsEntry 23 }
lowpanIfOutMeshNoRoutes OBJECT-TYPE lowpanIfOutMeshNoRoutes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams to be sent on this "The number of 6LoWPAN datagrams to be sent on this
interface with a MESH header that were dropped interface with a MESH header that were dropped
because there was no forwarding information available." because there was no forwarding information available."
skipping to change at page 20, line 43 skipping to change at page 21, line 10
"The number of 6LoWPAN datagrams to be sent on this "The number of 6LoWPAN datagrams to be sent on this
interface with a MESH header for which suitable interface with a MESH header for which suitable
forwarding information was available." forwarding information was available."
::= { lowpanIfStatsEntry 26 } ::= { lowpanIfStatsEntry 26 }
lowpanIfOutMeshTransmits OBJECT-TYPE lowpanIfOutMeshTransmits OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of 6LoWPAN datagrams to be send on this "The number of 6LoWPAN datagrams to be sent on this
interface with a MESH header created." interface with a MESH header created."
::= { lowpanIfStatsEntry 27 } ::= { lowpanIfStatsEntry 27 }
lowpanIfOutDiscards OBJECT-TYPE lowpanIfOutDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of IPv6 packets to be sent over this "The number of IPv6 packets to be sent over this
interface for which no problem was encountered to interface that were discarded (e.g., for lack of buffer
prevent their transmission to their destination, but space) even though no problem was encountered to
were discarded (e.g., for lack of buffer space)." prevent their transmission to their destination."
::= { lowpanIfStatsEntry 28 } ::= { lowpanIfStatsEntry 28 }
lowpanIfOutTransmits OBJECT-TYPE lowpanIfOutTransmits OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of 6LoWPAN datagrams to be sent on "The total number of 6LoWPAN datagrams to be sent on
this interface that this entity supplied to the lower this interface that this entity supplied to the lower
layers for transmission." layers for transmission."
skipping to change at page 21, line 36 skipping to change at page 21, line 51
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for systems that implement 6LoWPAN." "Compliance statement for systems that implement 6LoWPAN."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
lowpanStatsGroup lowpanStatsGroup
} }
GROUP lowpanStatsMeshGroup GROUP lowpanStatsMeshGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for implementations that process "This group is mandatory for implementations that process
or forward 6LoWPAN datagrams with mesh headers." or forward 6LoWPAN datagrams with a MESH header."
GROUP lowpanIfStatsGroup GROUP lowpanIfStatsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for implementations that expose "This group is mandatory for implementations that expose
per interface statistics." per-interface statistics."
GROUP lowpanIfStatsMeshGroup GROUP lowpanIfStatsMeshGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for implementations that expose "This group is mandatory for implementations that expose
per interface statistics and that process or forward per-interface statistics and that process or forward
6LoWPAN datagrams with mesh headers." 6LoWPAN datagrams with a MESH header."
::= { lowpanCompliances 1 } ::= { lowpanCompliances 1 }
lowpanStatsGroup OBJECT-GROUP lowpanStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lowpanReasmTimeout, lowpanReasmTimeout,
lowpanInReceives, lowpanInReceives,
lowpanInHdrErrors, lowpanInHdrErrors,
lowpanInMeshReceives, lowpanInMeshReceives,
lowpanInReasmReqds, lowpanInReasmReqds,
lowpanInReasmFails, lowpanInReasmFails,
skipping to change at page 22, line 30 skipping to change at page 22, line 44
lowpanOutFragOKs, lowpanOutFragOKs,
lowpanOutFragCreates, lowpanOutFragCreates,
lowpanOutDiscards, lowpanOutDiscards,
lowpanOutTransmits lowpanOutTransmits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information and "A collection of objects providing information and
statistics about the processing of 6LoWPAN datagrams, statistics about the processing of 6LoWPAN datagrams,
excluding counters covering the processing of datagrams excluding counters covering the processing of datagrams
with a mesh headers." with a MESH header."
::= { lowpanGroups 1 } ::= { lowpanGroups 1 }
lowpanStatsMeshGroup OBJECT-GROUP lowpanStatsMeshGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lowpanInMeshForwds, lowpanInMeshForwds,
lowpanInMeshDelivers, lowpanInMeshDelivers,
lowpanOutMeshHopLimitExceeds, lowpanOutMeshHopLimitExceeds,
lowpanOutMeshNoRoutes, lowpanOutMeshNoRoutes,
lowpanOutMeshRequests, lowpanOutMeshRequests,
lowpanOutMeshForwds, lowpanOutMeshForwds,
lowpanOutMeshTransmits lowpanOutMeshTransmits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information and "A collection of objects providing information and
statistics about the processing of 6LoWPAN datagrams statistics about the processing of 6LoWPAN datagrams
with a 6LoWPAN mesh header." with a MESH header."
::= { lowpanGroups 2 } ::= { lowpanGroups 2 }
lowpanIfStatsGroup OBJECT-GROUP lowpanIfStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lowpanIfReasmTimeout, lowpanIfReasmTimeout,
lowpanIfInReceives, lowpanIfInReceives,
lowpanIfInHdrErrors, lowpanIfInHdrErrors,
lowpanIfInMeshReceives, lowpanIfInMeshReceives,
lowpanIfInReasmReqds, lowpanIfInReasmReqds,
lowpanIfInReasmFails, lowpanIfInReasmFails,
skipping to change at page 23, line 29 skipping to change at page 23, line 43
lowpanIfOutCompOKs, lowpanIfOutCompOKs,
lowpanIfOutFragReqds, lowpanIfOutFragReqds,
lowpanIfOutFragFails, lowpanIfOutFragFails,
lowpanIfOutFragOKs, lowpanIfOutFragOKs,
lowpanIfOutFragCreates, lowpanIfOutFragCreates,
lowpanIfOutDiscards, lowpanIfOutDiscards,
lowpanIfOutTransmits lowpanIfOutTransmits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per interface "A collection of objects providing per-interface
information and statistics about the processing information and statistics about the processing
of 6LoWPAN datagrams, excluding counters covering of 6LoWPAN datagrams, excluding counters covering
the processing of datagrams with a mesh headers." the processing of datagrams with a MESH header."
::= { lowpanGroups 3 } ::= { lowpanGroups 3 }
lowpanIfStatsMeshGroup OBJECT-GROUP lowpanIfStatsMeshGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lowpanIfInMeshForwds, lowpanIfInMeshForwds,
lowpanIfInMeshDelivers, lowpanIfInMeshDelivers,
lowpanIfOutMeshHopLimitExceeds, lowpanIfOutMeshHopLimitExceeds,
lowpanIfOutMeshNoRoutes, lowpanIfOutMeshNoRoutes,
lowpanIfOutMeshRequests, lowpanIfOutMeshRequests,
lowpanIfOutMeshForwds, lowpanIfOutMeshForwds,
lowpanIfOutMeshTransmits lowpanIfOutMeshTransmits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per interface "A collection of objects providing per-interface
information and statistics about the processing information and statistics about the processing
of 6LoWPAN datagrams with a 6LoWPAN mesh header." of 6LoWPAN datagrams with a MESH header."
::= { lowpanGroups 4 } ::= { lowpanGroups 4 }
END END
7. Security Considerations 7. Security Considerations
There are no management objects defined in this MIB module that have There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. So, if this a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB intruder can alter or create any management objects of this MIB
skipping to change at page 24, line 24 skipping to change at page 24, line 41
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. the network via SNMP.
The read-only counters provide insights into the amount of 6LoWPAN The read-only counters provide insights into the amount of 6LoWPAN
traffic a node is receiving or transmitting. This might provide traffic a node is receiving or transmitting. This might provide
information whether a device is regularly exchanging information with information regarding whether a device is regularly exchanging
other devices or whether a device is mostly not participating in any information with other devices or whether a device is mostly not
communication (e.g., the device might be "easier" to take away participating in any communication (e.g., the device might be
unnoticed). The reassembly counters could be used to direct denial "easier" to take away unnoticed). The reassembly counters could be
of service attacks on the reassembly mechanism. used to direct denial-of-service attacks on the reassembly mechanism.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], Section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
IANA and RFC Ed.: IANA is requested to assign a value for "YYYY"
under the 'mib-2' subtree and to record the assignment in the SMI
Numbers registry. When the assignment has been made, the RFC Editor
is asked to replace "YYYY" (here and in the MIB module) with the
assigned value and to remove this note.
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
lowpanMIB { mib-2 YYYY } lowpanMIB { mib-2 226 }
9. Acknowledgements
This specification borrows heavily from the IP-MIB defined in
[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 9. References
10.1. Normative References 9.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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
58, RFC 2579, April 1999. 58, RFC 2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999, <http://www.rfc-editor.org/info/rfc2580>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000,
<http://www.rfc-editor.org/info/rfc2863>.
[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
"Transmission of IPv6 Packets over IEEE 802.15.4 "Transmission of IPv6 Packets over IEEE 802.15.4
Networks", RFC 4944, September 2007. Networks", RFC 4944, September 2007,
<http://www.rfc-editor.org/info/rfc4944>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 9.2. Informative References
MIB", RFC 2863, June 2000.
10.2. Informative References [CASE] Case, J. and C. Partridge, "Case Diagrams: A First Step to
Diagrammed Management Information Bases", Computer
Communications Review 19(1), January 1989.
[IPV6-BTLE]
Nieminen, J., Savolainen, T., Isomaki, M., Patil, B.,
Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets
over BLUETOOTH(R) Low Energy", Work in Progress, draft-
ietf-6lo-btle-03, September 2014.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980, <http://www.rfc-editor.org/info/rfc768>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998,
<http://www.rfc-editor.org/info/rfc2460>.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[RFC4113] Fenner, B. and J. Flick, "Management Information Base for [RFC4113] Fenner, B. and J. Flick, "Management Information Base for
the User Datagram Protocol (UDP)", RFC 4113, June 2005. the User Datagram Protocol (UDP)", RFC 4113, June 2005,
<http://www.rfc-editor.org/info/rfc4113>.
[RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April
2006. 2006, <http://www.rfc-editor.org/info/rfc4292>.
[RFC4293] Routhier, S., "Management Information Base for the [RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006. Internet Protocol (IP)", RFC 4293, April 2006,
<http://www.rfc-editor.org/info/rfc4293>.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control [RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet Protocol Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification", RFC 4443, March 2006. Version 6 (IPv6) Specification", RFC 4443, March 2006,
<http://www.rfc-editor.org/info/rfc4443>.
[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", RFC 7252, June 2014. Application Protocol (CoAP)", RFC 7252, June 2014,
<http://www.rfc-editor.org/info/rfc7252>.
[I-D.ietf-6lo-btle] Acknowledgements
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-03
(work in progress), September 2014.
[CASE] Case, J. and C. Partridge, "Case Diagrams: A First Step to This specification borrows heavily from the IP-MIB defined in
Diagrammed Management Information Bases", Computer [RFC4293].
Communications Review 19(1), January 1989.
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.
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
Anuj Sehgal Anuj Sehgal
Jacobs University Jacobs University
skipping to change at page 27, line 21 skipping to change at page 27, line 33
Anuj Sehgal Anuj Sehgal
Jacobs University Jacobs University
Campus Ring 1 Campus Ring 1
Bremen 28759 Bremen 28759
Germany Germany
EMail: s.anuj@jacobs-university.de EMail: s.anuj@jacobs-university.de
Tina Tsou Tina Tsou
Huawei Technologies (USA) Huawei Technologies
2330 Central Expressway 2330 Central Expressway
Santa Clara CA 95050 Santa Clara CA 95050
USA United States
EMail: tina.tsou.zouting@huawei.com EMail: tina.tsou.zouting@huawei.com
Cathy Zhou Cathy Zhou
Huawei Technologies Huawei Technologies
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 Shenzhen 518129
P.R. China China
EMail: cathyzhou@huawei.com EMail: cathyzhou@huawei.com
 End of changes. 85 change blocks. 
167 lines changed or deleted 163 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/