Internet DRAFT - draft-daniel-6lowpan-mib
draft-daniel-6lowpan-mib
Network Working Group K. Kim
Internet-Draft picosNet Corp/Ajou Univ.
Intended status: Standards Track H. Mukhtar, Ed.
Expires: April 29, 2010 S. Joo
ETRI
S. Yoo
Ajou University
S. Daniel Park
SAMSUNG Electronics
October 26, 2009
6LoWPAN Management Information Base
draft-daniel-6lowpan-mib-01.txt
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 29, 2010.
Kim, et al. Expires April 29, 2010 [Page 1]
Internet-Draft 6LoWPAN Management Information Base October 2009
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This draft defines a portion of the Management Information Base
(MIB), the lowpan MIB for use with network management protocols. In
particular it defines objects for managing functions related to a
6LoWPAN entity.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. IPv6 over Wireless PAN (6LoWPAN) . . . . . . . . . . . . . 3
5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 3
5.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 4
5.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 4
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
11.1. Normative References . . . . . . . . . . . . . . . . . . . 16
11.2. Informative References . . . . . . . . . . . . . . . . . . 18
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 20
Kim, et al. Expires April 29, 2010 [Page 2]
Internet-Draft 6LoWPAN Management Information Base October 2009
1. Introduction
This draft defines a portion of the Management Information Base
(MIB), the lowpan MIB for use with network management protocols.In
particular it defines objects for managing functions related to a
6LoWPAN entity.
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
Structure of Management Information (SMI). This memo specifies a MIB
module that compliant to the SMIv2, which is described in STD 58, RFC
2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[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
4.1. IPv6 over Wireless PAN (6LoWPAN)
Low-power wireless personal area networks (LoWPANs) comprise devices
that conform to the IEEE 802.15.4-2003 standard by the IEEE
[IEEE802.15.4]. IEEE 802.15.4 devices are characterized by short
range, low bit rate, low power and low cost. Many of the devices
employing IEEE 802.15.4 radios will be limited in their computational
power, memory, and/or energy availability.
This document defines a set of managed objects (MOs) that can be used
to monitor and control 6LoWPAN entities.
5. Relationship to Other MIB Modules
Some management objects defined in other MIB modules are applicable
to an entity implementing this MIB. In particular, it is assumed
that an entity implementing the 6LoWPAN-MIB module will also
implement the 'system' group of the SNMPv2-MIB [RFC3418] and the
Kim, et al. Expires April 29, 2010 [Page 3]
Internet-Draft 6LoWPAN Management Information Base October 2009
'interfaces' group of the IF-MIB [RFC2863]. The description of how
certain objects in the IF-MIB are used is TBD.
5.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The 6LoWPAN-MIB does not
duplicate those objects.
5.2. MIB modules required for IMPORTS
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579] and SNMPv2-CONF [RFC2580]
6. Definitions
LOWPAN-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI;
-- definition of textual conventions
lowpanTCMIB MODULE-IDENTITY
LAST-UPDATED "200909260012Z"
ORGANIZATION "IETF 6LoWPAN Working Group"
CONTACT-INFO "Ki-Hyung Kim
picosNet Corp/Ajou Univ.
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-749
KOREA
Phone: +82 31 219 2433
Email: kkim86@picosnet.com
Hamid Mukhtar, Editor
USN Research Division, ETRI
161 Gajeong-dong, Yuseong-gu,
Daejeon, 305-350
KOREA
Kim, et al. Expires April 29, 2010 [Page 4]
Internet-Draft 6LoWPAN Management Information Base October 2009
Phone: +82 42 860 5435
Email: hamid@etri.re.kr
Seong-Soon Joo
USN Research Division, ETRI
161 Gajeong-dong, Yuseong-gu,
Daejeon, 305-350
KOREA
Phone: +82 42 860 6333
Email: ssjoo@etri.re.kr
Seung Wha Yoo
Ajou University
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-749
KOREA
Phone: +82 31 219 1603
Email: swyoo@ajou.ac.kr
Soohong Daniel Park
Mobile Platform Laboratory, SAMSUNG Electronics
416 Maetan-3dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 442-742
KOREA
Phone: +82 31 200 4508
Email: soohong.park@samsung.com
Support Group E-mail: 6lowpan@ietf.org"
DESCRIPTION "A MIB module containing textual conventions
for 6LoWPAN data types. This module
addresses an immediate need for data types not
directly supported in the SMIv2.
Copyright (C) The Internet Society 2007. This
version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices."
-- RFC Ed.: replace XXXX with actual RFC number & remove this note
REVISION "200909260012Z"
DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number & remove this note
Kim, et al. Expires April 29, 2010 [Page 5]
Internet-Draft 6LoWPAN Management Information Base October 2009
::= { mib-2 XXX } -- will be assigned by IANA
-- IANA Reg.: Please assign a value for "XXX" under the 'mib-2'
-- subtree and record the assignment in the SMI Numbers registry.
-- RFC Ed.: When the above assignment has been made, please
-- remove the above note
-- replace "XXX" here with the assigned value and
-- remove this note.
LowpanIEEEEUI64Address ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"The IEEE defined 64-bit extended unique
identifier (EUI-64) is a concatenation of the
24-bit company_id value by the IEEE Registration
Authority and a 40-bit extension identifier
assigned by the organization with that company_id
assignment."
REFERENCE
"IEEE 64-BIT GLOBAL IDENTIFIER (EUI64)"
SYNTAX OCTET STRING (SIZE (8))
LowpanShortAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"The 16-bit Short Address used for 802.15.4
networks."
REFERENCE
"IEEE Std 802.15.4 specifications"
SYNTAX OCTET STRING (SIZE (2))
END
6LOWPAN-MIB DEFINITIONS ::= BEGIN
IMPORTS
TruthValue
FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32,mib-2
FROM SNMPv2-SMI
LowpanIEEEEUI64Address, LowpanShortAddress
FROM LOWPAN-TC-MIB;
Kim, et al. Expires April 29, 2010 [Page 6]
Internet-Draft 6LoWPAN Management Information Base October 2009
6lowpanMIB MODULE-IDENTITY
LAST-UPDATED "200909260012Z"
ORGANIZATION "IETF 6LoWPAN Working Group"
CONTACT-INFO "Ki-Hyung Kim
picosNet Corp/Ajou Univ.
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-749
KOREA
Phone: +82 31 219 2433
Email: kkim86@ajou.ac.kr
Hamid Mukhtar, Editor
USN Research Division, ETRI
161 Gajeong-dong, Yuseong-gu,
Daejeon, 305-350
KOREA
Phone: +82 42 860 5435
Email: hamid@etri.re.kr
Seong-Soon Joo
USN Research Division, ETRI
161 Gajeong-dong, Yuseong-gu,
Daejeon, 305-350
KOREA
Phone: +82 42 860 6333
Email: ssjoo@etri.re.kr
Seung Wha Yoo
Ajou University
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-749
KOREA
Phone: +82 31 219 1603
Email: swyoo@ajou.ac.kr
Soohong Daniel Park
Mobile Platform Laboratory, SAMSUNG Electronics
416 Maetan-3dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 442-742
KOREA
Kim, et al. Expires April 29, 2010 [Page 7]
Internet-Draft 6LoWPAN Management Information Base October 2009
Phone: +82 31 200 4508
Email: soohong.park@samsung.com
Support Group E-mail: 6lowpan@ietf.org"
DESCRIPTION "The MIB module for monitoring 6LoWPAN
entities.
Copyright (C) The Internet Society 2007. This
version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices."
-- RFC Ed.: replace XXXX with actual RFC number & remove this note
REVISION "200909260012Z"
DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number & remove this note
::= { mib-2 YYY } -- will be assigned by IANA
-- IANA Reg.: Please assign a value for "YYY" under the 'mib-2'
-- subtree and record the assignment in the SMI Numbers registry.
-- RFC Ed.: When the above assignment has been made, please
-- remove the above note
-- replace "YYY" here with the assigned value and
-- remove this note.
-- The major groups
lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 }
lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 }
lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 }
lowpanDeviceRole OBJECT-TYPE
SYNTAX INTEGER { PAN Coordinator ( 0 ) , 6LoWPAN
Router ( 1 ) , 6LoWPAN Mesh Node ( 3 ),
6LoWPAN Host ( 2 ) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The device in 6LoWPAN can play four roles.
coordinator(0) indicates that the device is a
PAN Coordinator which is the primary controller
of the PAN. It MAY initiate the synchronization
of the entire 6LoWPAN by transmitting beacons.
6LoWPAN Router(1) A LoWPAN node that forwards
datagrams between arbitrary source- destination
pairs using a single 6LoWPAN interface
Kim, et al. Expires April 29, 2010 [Page 8]
Internet-Draft 6LoWPAN Management Information Base October 2009
performing IP routing on that interface.
6LoWPAN Mesh Node (2) A LoWPAN node that
forwards data between arbitrary source-
destination pairs using link addresses (and
thus only exist in Mesh Under LoWPANs).
6LoWPAN Host(3) indicates a node that only
sources or sinks IPv6 datagrams.
::= { lowpanObjects 1 }
lowpanDeviceCapabilities OBJECT-TYPE
SYNTAX BITS { alternatePANcoordinator ( 0 ) ,
deviceType ( 1 ) , powerSource ( 2 ) ,
recieverOnWhenIdle ( 3 ) , securityCapability
( 6 ) , allocateAddress ( 7 ) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION "alternatePANcoordinator(0)- The alternate PAN
coordinator subfield shall be set to 1 if the
device is capable of becoming a PAN
coordinator. Otherwise, the alternate PAN
coordinator subfield shall be set to 0.
deviceType(1) -The device type subfield shall
be set to 1 if the device is an FFD.
Otherwise, the device type subfield shall be
set to 0 to indicate an RFD.
powerSource(2)- The power source subfield
shall be set to 1 if the device is receiving
power from the alternating current mains.
Otherwise, the power source subfield shall
be set to 0.
recieverOnWhenIdle(3) - The receiver on when
idle shall be set to 1 if the device does not
disable its receiver to conserve power
during idle periods. Otherwise, the receiver
on when idle subfield shall be set to 0.
securityCapability(6)- The security capability
subfield shall be set to 1 if the device is
capable of sending and receiving MAC frames
secured using the security suite. Otherwise
the security capability subfield shall be
set to 0.
allocateAddress(7)- The allocate address
subfield shall be set to 1 if the device
Kim, et al. Expires April 29, 2010 [Page 9]
Internet-Draft 6LoWPAN Management Information Base October 2009
wishes the coordinator to allocate a short
address as a result of the association
procedure. If this subfield is set to 0, the
special short address of 0 x fffe shall be
allocated to the device and returned through
the association response command. In this
case, the device shall communicate on the
PAN using only its 64 bit extended address.
BITS 4-5 are reserved"
REFERENCE "IEEE Std 802.15.4 specifications section
7.3.1.1.2"
::= { lowpanObjects 2 }
lowpanRoutingProtocol OBJECT-TYPE
SYNTAX INTEGER { RPL ( 0 ), DADR ( 1 ), DV ( 2 ),
dymoLow ( 3 ), hiLow ( 4 ) , load ( 5 ), Other
Other ( 6 ) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION "6LoWPAN Router Over and Mesh Under currently
have three protocols each.
RPL(0) - Routing Protocol for Low Power and
Lossy Networks
DADR (1)- Distributed Autonomous Depth-first
Routing Protocol in LLN
DV (2)- A Distance Vector Protocol for Routing
Over Low Power and Lossy Networks
dymoLow(3) - Dynamic MANET On-demand routing
for 6LoWPAN
hiLow(4) - Hierarchical Routing over 6LoWPAN
load(5) -Ad Hoc On-Demand Distance Vector
Routing for 6LoWPAN"
REFERENCE "draft-ietf-roll-rpl (Work in progress),
draft-iwao-roll-dadr (Work in progress),
draft-goyal-roll-dv (Work in progress),
draft-daniel-6lowpan-load-adhoc-routing
(Work in progress),
draft-montenegro-6lowpan-dymo-low-routing
(Work in progress),
draft-daniel-6lowpan-hilow-hierarchical-routing
(Work in progress)"
::= { lowpanObjects 3 }
lowpanRoutingTable OBJECT-TYPE
SYNTAX SEQUENCE OF LowpanRoutingEntry
MAX-ACCESS not-accessible
STATUS current
Kim, et al. Expires April 29, 2010 [Page 10]
Internet-Draft 6LoWPAN Management Information Base October 2009
DESCRIPTION "The routing table entries of a device"
::= { lowpanObjects 4 }
lowpanRoutingEntry OBJECT-TYPE
SYNTAX LowpanRoutingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "This entry represents a conceptual row in the
routing table. It represents a single routing
entry."
INDEX { lowpanRouteDestAddress }
::= { lowpanRoutingTable 1 }
LowpanRoutingEntry ::= SEQUENCE {
lowpanRouteDestAddress LowpanShortAddress,
lowpanRouteNextHopAddress LowpanShortAddress,
}
lowpanRouteDestAddress OBJECT-TYPE
SYNTAX LowpanShortAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The 16-bit short address of destination of this
route"
::= { lowpanRoutingEntry 1 }
lowpanRouteNextHopAddress OBJECT-TYPE
SYNTAX LowpanShortAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The short address of the next hop which leads
to the destination"
::= { lowpanRoutingEntry 2 }
lowpanNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF LowpanNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The neighbor table entries of a device"
::= { lowpanObjects 5 }
lowpanNeighborEntry OBJECT-TYPE
SYNTAX LowpanNeighborEntry
MAX-ACCESS not-accessible
STATUS current
Kim, et al. Expires April 29, 2010 [Page 11]
Internet-Draft 6LoWPAN Management Information Base October 2009
DESCRIPTION "This entry represents a conceptual row in the
neighbor table. It represents a single
neighbor table entry."
INDEX { lowpanNeighborEUI64Address }
::= { lowpanNeighborTable 1 }
LowpanNeighborEntry ::= SEQUENCE {
lowpanNeighborPanID Unsigned32,
lowpanNeighborEUI64Address LowpanIEEEEUI64Address,
lowpanNeighborShortAddress LowpanShortAddress,
lowpanNeighborDeviceType INTEGER,
lowpanNeighborIsParent TruthValue
}
lowpanNeighborPanID OBJECT-TYPE
SYNTAX Unsigned32 (0..65536)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The Personal area network Identifier
(PanID) of the neighbor entry"
::= { lowpanNeighborEntry 1 }
lowpanNeighborEUI64Address OBJECT-TYPE
SYNTAX LowpanIEEEEUI64Address
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The EUI64 bit address of the neighbor
entry."
::= { lowpanNeighborEntry 2 }
lowpanNeighborShortAddress OBJECT-TYPE
SYNTAX LowpanShortAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The 16-bit short address of the neighbor
entry."
::= { lowpanNeighborEntry 3 }
lowpanNeighborDeviceType OBJECT-TYPE
SYNTAX INTEGER { coordinator ( 0 ) , router ( 1 ) ,
endDevice ( 2 )}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The device type of the neighbor entry."
::= { lowpanNeighborEntry 4 }
Kim, et al. Expires April 29, 2010 [Page 12]
Internet-Draft 6LoWPAN Management Information Base October 2009
lowpanNeighborIsParent OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The value 'true(1)' indicates that the
neighbor is a topological parent of the
device."
::= { lowpanNeighborEntry 5 }
lowpanUseHierarchicalRouting OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The value 'true(1)' indicates that the
entity uses tree based routing. 'false(2)'
indicates that entity is not using
tree based routing."
::= { lowpanObjects 6 }
lowpanBroadcastSequenceNumber OBJECT-TYPE
SYNTAX Unsigned32 (0..65536)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The last value of the sequence number
that was added to the 6LoWPAN broadcast or
multicast frame."
REFERENCE "RFC4944"
::= { lowpanObjects 7 }
lowpanAckTimeout OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milli-seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The maximum time allowed for retransmission
of a broadcast message"
::= { lowpanObjects 8 }
lowpanBroadcastRetries OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The maximum number of retries allowed for a
broadcast message."
::= { lowpanObjects 9 }
-- Conformance information
Kim, et al. Expires April 29, 2010 [Page 13]
Internet-Draft 6LoWPAN Management Information Base October 2009
lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 }
lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 }
lowpanGeneralGroup OBJECT-GROUP
OBJECTS { lowpanDeviceCapabilities,
lowpanRouteNextHopAddress,
lowpanRouteNextHopAddress,
lowpanRoutingProtocol}
STATUS current
DESCRIPTION "A collection of objects for basic 6LoWPAN
monitoring"
::= { lowpanGroups 1 }
lowpanCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the LOWPAN-MIB."
MODULE -- this module
MANDATORY-GROUPS { lowpanGeneralGroup }
::= { lowpanCompliances 1 }
lowpanCoreReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the LOWPAN-MIB without support
for read-write (i.e. in read-only mode) .
"
MODULE -- this module
MANDATORY-GROUPS { lowpanGeneralGroup }
OBJECT lowpanAckTimeout
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lowpanBroadcastRetries
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { lowpanCompliances 2 }
END
Kim, et al. Expires April 29, 2010 [Page 14]
Internet-Draft 6LoWPAN Management Information Base October 2009
7. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the objects and their sensitivity/
vulnerability:
o The vulnerabilities for lowpanAckTimeout object will be discussed
in the next version of the draft
o The vulnerabilities for lowpanBroadcastRetries object will be
discussed in the next version of the draft
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
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. The vulnerabilities will be discussed in next
versions on this draft
SNMP versions prior to SNMPv3 did not include adequate security.
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
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
Kim, et al. Expires April 29, 2010 [Page 15]
Internet-Draft 6LoWPAN Management Information Base October 2009
8. IANA Considerations
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
lowpanTCMIB { mib-2 XXX }
lowpanMIB { mib-2 YYY }
9. Contributors
Thanks to the contribution from 6LoWPAN WG MIB Doctor, Juergen
Schoenwaelder for the review and useful discussion for writing this
document
10. Acknowledgements
Thanks to Ali Hammad Akbar, Shafique Ahmed Choadry, Chae-Seong Lim,
Seong-Soon Joo, and Geoff Mulligan for their useful discussion and
support for writing this document and to Glenn M. Keeni for reviewing
the MIB module.
11. References
11.1. Normative References
[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.
[RFC2579] McCloghrie, K., Ed.,
Kim, et al. Expires April 29, 2010 [Page 16]
Internet-Draft 6LoWPAN Management Information Base October 2009
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,
April 1999.
[RFC3418] Presuhn, R.,
"Management
Information Base
(MIB) for the Simple
Network Management
Protocol (SNMP)",
STD 62, RFC 3418,
December 2002.
[RFC2863] McCloghrie, K. and
F. Kastenholz, "The
Interfaces Group
MIB", RFC 2863,
June 2000.
[RFC4944] Montenegro, G.,
Kushalnagar, N.,
Hui, J., and D.
Culler,
"Transmission of
IPv6 Packets over
IEEE 802.15.4
Networks", RFC 4944,
September 2007.
[IEEE802.15.4] 802.15.4-2003, IEEE
Standard., "Wireless
medium access
control and physical
layer specifications
for low-rate
Kim, et al. Expires April 29, 2010 [Page 17]
Internet-Draft 6LoWPAN Management Information Base October 2009
wireless personal
area networks.",
May 2003.
11.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.
[RFC4919] Kushalnagar, N.,
Montenegro, G., and
C. Schumacher, "IPv6
over Low-Power
Wireless Personal
Area Networks
(6LoWPANs):
Overview,
Assumptions, Problem
Statement, and
Goals", RFC 4919,
August 2007.
[EUI64] 802.15.4-2003, IEEE
Standard.,
"GUIDELINES FOR 64-
BIT GLOBAL
IDENTIFIER (EUI-64)
REGISTRATION
AUTHORITY".
[I-D.draft-ietf-roll-rpl] Winter, T., Thubert,
P., and ROLL. Design
Team, "RPL: Routing
Protocol for Low
Power and Lossy
Networks", (Work in
progress),
October 2009.
Kim, et al. Expires April 29, 2010 [Page 18]
Internet-Draft 6LoWPAN Management Information Base October 2009
[I-D.draft-iwao-roll-dadr] Iwao, T.,
"Distributed
Autonomous Depth-
first Routing
Protocol in LLN",
(Work in progress),
July 2009.
[I-D.draft-goyal-roll-dv] Goyal, M., "A
Distance Vector
Protocol for Routing
Over Low Power and
Lossy Networks",
(Work in progress),
July 2009.
[I-D.montenegro-6lowpan-dymo-low-routing] Kim, K., Montenegro,
G., Daniel Park, S.,
Chakeres, I., and S.
Yoo, "Dynamic MANET
On-demand for
6LoWPAN (DYMO-low)
Routing", (Work in
progress),
December 2007.
[I-D.daniel-6lowpan-hilow-hierarchical-routing] Kim, K., Yoo, S.,
Park, J., Daniel
Park, S., and J.
Lee, "Hierarchical
Routing over 6LoWPAN
(HiLow)", (Work in
progress),
December 2007.
[I-D.daniel-6lowpan-load-adhoc-routing] Kim, K., Daniel
Park, S.,
Montenegro, G., Yoo,
S., and Kushalnagar.
N., "6LoWPAN Ad Hoc
On-Demand Distance
Vector Routing
(LOAD)", (Work in
progress),
December 2007.
Kim, et al. Expires April 29, 2010 [Page 19]
Internet-Draft 6LoWPAN Management Information Base October 2009
Appendix A. Open Issues
SNMP based access to 802.15.4 PHY/MAC PIBs should also be provided by
assigning them object identifiers.
Authors' Addresses
Kim Ki Hyung
picosNet Corp/Ajou Univ.
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-749
KOREA
Phone: +82 31 219 2433
EMail: kkim86@picosnet.com
Hamid Mukhtar (editor)
ETRI
USN Research Division, ETRI, 161 Gajeong-dong, Yuseong-gu,
Daejeon 305-350
KOREA
Phone: +82 42 860 5435
EMail: hamid@etri.re.kr
Seong-Soon Joo
ETRI
USN Research Division, ETRI, 161 Gajeong-dong, Yuseong-gu,
Daejeon 305-350
KOREA
Phone: +82 42 860 6333
EMail: ssjoo@etri.re.kr
Seung Wha Yoo
Ajou University
San 5 Wonchun-dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 443-749
KOREA
Phone: +82 31 219 1603
EMail: swyoo@ajou.ac.kr
Kim, et al. Expires April 29, 2010 [Page 20]
Internet-Draft 6LoWPAN Management Information Base October 2009
Soohong Daniel Park
SAMSUNG Electronics
Mobile Platform Laboratory,
SAMSUNG Electronics 416 Maetan-3dong, Yeongtong-gu
Suwon-si, Gyeonggi-do 442-742
KOREA
Phone: +82 31 200 4508
EMail: soohong.park@samsung.com
Kim, et al. Expires April 29, 2010 [Page 21]
