idnits 2.17.1 draft-daniel-6lowpan-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 26, 2009) is 5295 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4944' is defined on line 766, but no explicit reference was found in the text == Unused Reference: 'RFC4919' is defined on line 800, but no explicit reference was found in the text == Unused Reference: 'EUI64' is defined on line 813, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-ietf-roll-rpl' is defined on line 821, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-iwao-roll-dadr' is defined on line 830, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-goyal-roll-dv' is defined on line 838, but no explicit reference was found in the text == Unused Reference: 'I-D.montenegro-6lowpan-dymo-low-routing' is defined on line 846, but no explicit reference was found in the text == Unused Reference: 'I-D.daniel-6lowpan-hilow-hierarchical-routing' is defined on line 856, but no explicit reference was found in the text == Unused Reference: 'I-D.daniel-6lowpan-load-adhoc-routing' is defined on line 865, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.15.4' Summary: 1 error (**), 0 flaws (~~), 12 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Kim 3 Internet-Draft picosNet Corp/Ajou Univ. 4 Intended status: Standards Track H. Mukhtar, Ed. 5 Expires: April 29, 2010 S. Joo 6 ETRI 7 S. Yoo 8 Ajou University 9 S. Daniel Park 10 SAMSUNG Electronics 11 October 26, 2009 13 6LoWPAN Management Information Base 14 draft-daniel-6lowpan-mib-01.txt 16 Status of This Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. This document may contain material 20 from IETF Documents or IETF Contributions published or made publicly 21 available before November 10, 2008. The person(s) controlling the 22 copyright in some of this material may not have granted the IETF 23 Trust the right to allow modifications of such material outside the 24 IETF Standards Process. Without obtaining an adequate license from 25 the person(s) controlling the copyright in such materials, this 26 document may not be modified outside the IETF Standards Process, and 27 derivative works of it may not be created outside the IETF Standards 28 Process, except to format it for publication as an RFC or to 29 translate it into languages other than English. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire on April 29, 2010. 49 Copyright Notice 51 Copyright (c) 2009 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents in effect on the date of 56 publication of this document (http://trustee.ietf.org/license-info). 57 Please review these documents carefully, as they describe your rights 58 and restrictions with respect to this document. 60 Abstract 62 This draft defines a portion of the Management Information Base 63 (MIB), the lowpan MIB for use with network management protocols. In 64 particular it defines objects for managing functions related to a 65 6LoWPAN entity. 67 Table of Contents 69 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 2. The Internet-Standard Management Framework . . . . . . . . . . 3 71 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 72 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 73 4.1. IPv6 over Wireless PAN (6LoWPAN) . . . . . . . . . . . . . 3 74 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 3 75 5.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 4 76 5.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 4 77 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 78 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 79 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 80 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16 81 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 82 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 83 11.1. Normative References . . . . . . . . . . . . . . . . . . . 16 84 11.2. Informative References . . . . . . . . . . . . . . . . . . 18 85 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 20 87 1. Introduction 89 This draft defines a portion of the Management Information Base 90 (MIB), the lowpan MIB for use with network management protocols.In 91 particular it defines objects for managing functions related to a 92 6LoWPAN entity. 94 2. The Internet-Standard Management Framework 96 For a detailed overview of the documents that describe the current 97 Internet-Standard Management Framework, please refer to section 7 of 98 RFC 3410 [RFC3410]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. MIB objects are generally 102 accessed through the Simple Network Management Protocol (SNMP). 103 Objects in the MIB are defined using the mechanisms defined in the 104 Structure of Management Information (SMI). This memo specifies a MIB 105 module that compliant to the SMIv2, which is described in STD 58, RFC 106 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 107 [RFC2580]. 109 3. Conventions 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in RFC 2119 [RFC2119]. 115 4. Overview 117 4.1. IPv6 over Wireless PAN (6LoWPAN) 119 Low-power wireless personal area networks (LoWPANs) comprise devices 120 that conform to the IEEE 802.15.4-2003 standard by the IEEE 121 [IEEE802.15.4]. IEEE 802.15.4 devices are characterized by short 122 range, low bit rate, low power and low cost. Many of the devices 123 employing IEEE 802.15.4 radios will be limited in their computational 124 power, memory, and/or energy availability. 126 This document defines a set of managed objects (MOs) that can be used 127 to monitor and control 6LoWPAN entities. 129 5. Relationship to Other MIB Modules 131 Some management objects defined in other MIB modules are applicable 132 to an entity implementing this MIB. In particular, it is assumed 133 that an entity implementing the 6LoWPAN-MIB module will also 134 implement the 'system' group of the SNMPv2-MIB [RFC3418] and the 135 'interfaces' group of the IF-MIB [RFC2863]. The description of how 136 certain objects in the IF-MIB are used is TBD. 138 5.1. Relationship to the SNMPv2-MIB 140 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 141 mandatory for all systems, and the objects apply to the entity as a 142 whole. The 'system' group provides identification of the management 143 entity and certain other system-wide data. The 6LoWPAN-MIB does not 144 duplicate those objects. 146 5.2. MIB modules required for IMPORTS 148 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 149 SNMPv2-TC [RFC2579] and SNMPv2-CONF [RFC2580] 151 6. Definitions 153 LOWPAN-TC-MIB DEFINITIONS ::= BEGIN 154 IMPORTS 155 TEXTUAL-CONVENTION 156 FROM SNMPv2-TC 157 MODULE-IDENTITY, mib-2 158 FROM SNMPv2-SMI; 160 -- definition of textual conventions 162 lowpanTCMIB MODULE-IDENTITY 163 LAST-UPDATED "200909260012Z" 164 ORGANIZATION "IETF 6LoWPAN Working Group" 165 CONTACT-INFO "Ki-Hyung Kim 166 picosNet Corp/Ajou Univ. 167 San 5 Wonchun-dong, Yeongtong-gu 168 Suwon-si, Gyeonggi-do 443-749 169 KOREA 171 Phone: +82 31 219 2433 172 Email: kkim86@picosnet.com 174 Hamid Mukhtar, Editor 175 USN Research Division, ETRI 176 161 Gajeong-dong, Yuseong-gu, 177 Daejeon, 305-350 178 KOREA 179 Phone: +82 42 860 5435 180 Email: hamid@etri.re.kr 182 Seong-Soon Joo 183 USN Research Division, ETRI 184 161 Gajeong-dong, Yuseong-gu, 185 Daejeon, 305-350 186 KOREA 188 Phone: +82 42 860 6333 189 Email: ssjoo@etri.re.kr 191 Seung Wha Yoo 192 Ajou University 193 San 5 Wonchun-dong, Yeongtong-gu 194 Suwon-si, Gyeonggi-do 443-749 195 KOREA 197 Phone: +82 31 219 1603 198 Email: swyoo@ajou.ac.kr 200 Soohong Daniel Park 201 Mobile Platform Laboratory, SAMSUNG Electronics 202 416 Maetan-3dong, Yeongtong-gu 203 Suwon-si, Gyeonggi-do 442-742 204 KOREA 206 Phone: +82 31 200 4508 207 Email: soohong.park@samsung.com 209 Support Group E-mail: 6lowpan@ietf.org" 211 DESCRIPTION "A MIB module containing textual conventions 212 for 6LoWPAN data types. This module 213 addresses an immediate need for data types not 214 directly supported in the SMIv2. 216 Copyright (C) The Internet Society 2007. This 217 version of this MIB module is part of RFC XXXX; 218 see the RFC itself for full legal notices." 219 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 221 REVISION "200909260012Z" 222 DESCRIPTION "Initial version, published as RFC XXXX." 223 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 224 ::= { mib-2 XXX } -- will be assigned by IANA 226 -- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' 227 -- subtree and record the assignment in the SMI Numbers registry. 229 -- RFC Ed.: When the above assignment has been made, please 230 -- remove the above note 231 -- replace "XXX" here with the assigned value and 232 -- remove this note. 234 LowpanIEEEEUI64Address ::= TEXTUAL-CONVENTION 235 DISPLAY-HINT "1x:" 236 STATUS current 237 DESCRIPTION 238 "The IEEE defined 64-bit extended unique 239 identifier (EUI-64) is a concatenation of the 240 24-bit company_id value by the IEEE Registration 241 Authority and a 40-bit extension identifier 242 assigned by the organization with that company_id 243 assignment." 244 REFERENCE 245 "IEEE 64-BIT GLOBAL IDENTIFIER (EUI64)" 246 SYNTAX OCTET STRING (SIZE (8)) 248 LowpanShortAddress ::= TEXTUAL-CONVENTION 249 DISPLAY-HINT "1x:" 250 STATUS current 251 DESCRIPTION 252 "The 16-bit Short Address used for 802.15.4 253 networks." 254 REFERENCE 255 "IEEE Std 802.15.4 specifications" 256 SYNTAX OCTET STRING (SIZE (2)) 258 END 260 6LOWPAN-MIB DEFINITIONS ::= BEGIN 261 IMPORTS 262 TruthValue 263 FROM SNMPv2-TC 264 OBJECT-GROUP, MODULE-COMPLIANCE 265 FROM SNMPv2-CONF 266 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32,mib-2 267 FROM SNMPv2-SMI 268 LowpanIEEEEUI64Address, LowpanShortAddress 269 FROM LOWPAN-TC-MIB; 271 6lowpanMIB MODULE-IDENTITY 272 LAST-UPDATED "200909260012Z" 273 ORGANIZATION "IETF 6LoWPAN Working Group" 274 CONTACT-INFO "Ki-Hyung Kim 275 picosNet Corp/Ajou Univ. 276 San 5 Wonchun-dong, Yeongtong-gu 277 Suwon-si, Gyeonggi-do 443-749 278 KOREA 280 Phone: +82 31 219 2433 281 Email: kkim86@ajou.ac.kr 283 Hamid Mukhtar, Editor 284 USN Research Division, ETRI 285 161 Gajeong-dong, Yuseong-gu, 286 Daejeon, 305-350 287 KOREA 289 Phone: +82 42 860 5435 290 Email: hamid@etri.re.kr 292 Seong-Soon Joo 293 USN Research Division, ETRI 294 161 Gajeong-dong, Yuseong-gu, 295 Daejeon, 305-350 296 KOREA 298 Phone: +82 42 860 6333 299 Email: ssjoo@etri.re.kr 301 Seung Wha Yoo 302 Ajou University 303 San 5 Wonchun-dong, Yeongtong-gu 304 Suwon-si, Gyeonggi-do 443-749 305 KOREA 307 Phone: +82 31 219 1603 308 Email: swyoo@ajou.ac.kr 310 Soohong Daniel Park 311 Mobile Platform Laboratory, SAMSUNG Electronics 312 416 Maetan-3dong, Yeongtong-gu 313 Suwon-si, Gyeonggi-do 442-742 314 KOREA 315 Phone: +82 31 200 4508 316 Email: soohong.park@samsung.com 318 Support Group E-mail: 6lowpan@ietf.org" 320 DESCRIPTION "The MIB module for monitoring 6LoWPAN 321 entities. 323 Copyright (C) The Internet Society 2007. This 324 version of this MIB module is part of RFC XXXX; 325 see the RFC itself for full legal notices." 326 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 328 REVISION "200909260012Z" 329 DESCRIPTION "Initial version, published as RFC XXXX." 330 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 332 ::= { mib-2 YYY } -- will be assigned by IANA 334 -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2' 335 -- subtree and record the assignment in the SMI Numbers registry. 337 -- RFC Ed.: When the above assignment has been made, please 338 -- remove the above note 339 -- replace "YYY" here with the assigned value and 340 -- remove this note. 342 -- The major groups 344 lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } 345 lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } 346 lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } 348 lowpanDeviceRole OBJECT-TYPE 349 SYNTAX INTEGER { PAN Coordinator ( 0 ) , 6LoWPAN 350 Router ( 1 ) , 6LoWPAN Mesh Node ( 3 ), 351 6LoWPAN Host ( 2 ) } 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION "The device in 6LoWPAN can play four roles. 356 coordinator(0) indicates that the device is a 357 PAN Coordinator which is the primary controller 358 of the PAN. It MAY initiate the synchronization 359 of the entire 6LoWPAN by transmitting beacons. 360 6LoWPAN Router(1) A LoWPAN node that forwards 361 datagrams between arbitrary source- destination 362 pairs using a single 6LoWPAN interface 363 performing IP routing on that interface. 364 6LoWPAN Mesh Node (2) A LoWPAN node that 365 forwards data between arbitrary source- 366 destination pairs using link addresses (and 367 thus only exist in Mesh Under LoWPANs). 368 6LoWPAN Host(3) indicates a node that only 369 sources or sinks IPv6 datagrams. 370 ::= { lowpanObjects 1 } 372 lowpanDeviceCapabilities OBJECT-TYPE 373 SYNTAX BITS { alternatePANcoordinator ( 0 ) , 374 deviceType ( 1 ) , powerSource ( 2 ) , 375 recieverOnWhenIdle ( 3 ) , securityCapability 376 ( 6 ) , allocateAddress ( 7 ) } 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION "alternatePANcoordinator(0)- The alternate PAN 380 coordinator subfield shall be set to 1 if the 381 device is capable of becoming a PAN 382 coordinator. Otherwise, the alternate PAN 383 coordinator subfield shall be set to 0. 385 deviceType(1) -The device type subfield shall 386 be set to 1 if the device is an FFD. 387 Otherwise, the device type subfield shall be 388 set to 0 to indicate an RFD. 390 powerSource(2)- The power source subfield 391 shall be set to 1 if the device is receiving 392 power from the alternating current mains. 393 Otherwise, the power source subfield shall 394 be set to 0. 396 recieverOnWhenIdle(3) - The receiver on when 397 idle shall be set to 1 if the device does not 398 disable its receiver to conserve power 399 during idle periods. Otherwise, the receiver 400 on when idle subfield shall be set to 0. 402 securityCapability(6)- The security capability 403 subfield shall be set to 1 if the device is 404 capable of sending and receiving MAC frames 405 secured using the security suite. Otherwise 406 the security capability subfield shall be 407 set to 0. 409 allocateAddress(7)- The allocate address 410 subfield shall be set to 1 if the device 411 wishes the coordinator to allocate a short 412 address as a result of the association 413 procedure. If this subfield is set to 0, the 414 special short address of 0 x fffe shall be 415 allocated to the device and returned through 416 the association response command. In this 417 case, the device shall communicate on the 418 PAN using only its 64 bit extended address. 420 BITS 4-5 are reserved" 421 REFERENCE "IEEE Std 802.15.4 specifications section 422 7.3.1.1.2" 423 ::= { lowpanObjects 2 } 425 lowpanRoutingProtocol OBJECT-TYPE 426 SYNTAX INTEGER { RPL ( 0 ), DADR ( 1 ), DV ( 2 ), 427 dymoLow ( 3 ), hiLow ( 4 ) , load ( 5 ), Other 428 Other ( 6 ) } 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION "6LoWPAN Router Over and Mesh Under currently 432 have three protocols each. 433 RPL(0) - Routing Protocol for Low Power and 434 Lossy Networks 435 DADR (1)- Distributed Autonomous Depth-first 436 Routing Protocol in LLN 437 DV (2)- A Distance Vector Protocol for Routing 438 Over Low Power and Lossy Networks 439 dymoLow(3) - Dynamic MANET On-demand routing 440 for 6LoWPAN 441 hiLow(4) - Hierarchical Routing over 6LoWPAN 442 load(5) -Ad Hoc On-Demand Distance Vector 443 Routing for 6LoWPAN" 444 REFERENCE "draft-ietf-roll-rpl (Work in progress), 445 draft-iwao-roll-dadr (Work in progress), 446 draft-goyal-roll-dv (Work in progress), 447 draft-daniel-6lowpan-load-adhoc-routing 448 (Work in progress), 449 draft-montenegro-6lowpan-dymo-low-routing 450 (Work in progress), 451 draft-daniel-6lowpan-hilow-hierarchical-routing 452 (Work in progress)" 453 ::= { lowpanObjects 3 } 455 lowpanRoutingTable OBJECT-TYPE 456 SYNTAX SEQUENCE OF LowpanRoutingEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION "The routing table entries of a device" 460 ::= { lowpanObjects 4 } 462 lowpanRoutingEntry OBJECT-TYPE 463 SYNTAX LowpanRoutingEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION "This entry represents a conceptual row in the 467 routing table. It represents a single routing 468 entry." 469 INDEX { lowpanRouteDestAddress } 470 ::= { lowpanRoutingTable 1 } 472 LowpanRoutingEntry ::= SEQUENCE { 473 lowpanRouteDestAddress LowpanShortAddress, 474 lowpanRouteNextHopAddress LowpanShortAddress, 475 } 477 lowpanRouteDestAddress OBJECT-TYPE 478 SYNTAX LowpanShortAddress 479 MAX-ACCESS not-accessible 480 STATUS current 481 DESCRIPTION "The 16-bit short address of destination of this 482 route" 483 ::= { lowpanRoutingEntry 1 } 485 lowpanRouteNextHopAddress OBJECT-TYPE 486 SYNTAX LowpanShortAddress 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION "The short address of the next hop which leads 490 to the destination" 491 ::= { lowpanRoutingEntry 2 } 493 lowpanNeighborTable OBJECT-TYPE 494 SYNTAX SEQUENCE OF LowpanNeighborEntry 495 MAX-ACCESS not-accessible 496 STATUS current 497 DESCRIPTION "The neighbor table entries of a device" 498 ::= { lowpanObjects 5 } 500 lowpanNeighborEntry OBJECT-TYPE 501 SYNTAX LowpanNeighborEntry 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION "This entry represents a conceptual row in the 505 neighbor table. It represents a single 506 neighbor table entry." 507 INDEX { lowpanNeighborEUI64Address } 508 ::= { lowpanNeighborTable 1 } 510 LowpanNeighborEntry ::= SEQUENCE { 511 lowpanNeighborPanID Unsigned32, 512 lowpanNeighborEUI64Address LowpanIEEEEUI64Address, 513 lowpanNeighborShortAddress LowpanShortAddress, 514 lowpanNeighborDeviceType INTEGER, 515 lowpanNeighborIsParent TruthValue 516 } 518 lowpanNeighborPanID OBJECT-TYPE 519 SYNTAX Unsigned32 (0..65536) 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION "The Personal area network Identifier 523 (PanID) of the neighbor entry" 524 ::= { lowpanNeighborEntry 1 } 526 lowpanNeighborEUI64Address OBJECT-TYPE 527 SYNTAX LowpanIEEEEUI64Address 528 MAX-ACCESS not-accessible 529 STATUS current 530 DESCRIPTION "The EUI64 bit address of the neighbor 531 entry." 532 ::= { lowpanNeighborEntry 2 } 534 lowpanNeighborShortAddress OBJECT-TYPE 535 SYNTAX LowpanShortAddress 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION "The 16-bit short address of the neighbor 539 entry." 540 ::= { lowpanNeighborEntry 3 } 542 lowpanNeighborDeviceType OBJECT-TYPE 543 SYNTAX INTEGER { coordinator ( 0 ) , router ( 1 ) , 544 endDevice ( 2 )} 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION "The device type of the neighbor entry." 548 ::= { lowpanNeighborEntry 4 } 550 lowpanNeighborIsParent OBJECT-TYPE 551 SYNTAX TruthValue 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION "The value 'true(1)' indicates that the 555 neighbor is a topological parent of the 556 device." 557 ::= { lowpanNeighborEntry 5 } 559 lowpanUseHierarchicalRouting OBJECT-TYPE 560 SYNTAX TruthValue 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION "The value 'true(1)' indicates that the 564 entity uses tree based routing. 'false(2)' 565 indicates that entity is not using 566 tree based routing." 567 ::= { lowpanObjects 6 } 569 lowpanBroadcastSequenceNumber OBJECT-TYPE 570 SYNTAX Unsigned32 (0..65536) 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION "The last value of the sequence number 574 that was added to the 6LoWPAN broadcast or 575 multicast frame." 576 REFERENCE "RFC4944" 577 ::= { lowpanObjects 7 } 579 lowpanAckTimeout OBJECT-TYPE 580 SYNTAX Unsigned32 581 UNITS "milli-seconds" 582 MAX-ACCESS read-write 583 STATUS current 584 DESCRIPTION "The maximum time allowed for retransmission 585 of a broadcast message" 586 ::= { lowpanObjects 8 } 588 lowpanBroadcastRetries OBJECT-TYPE 589 SYNTAX Unsigned32 590 MAX-ACCESS read-write 591 STATUS current 592 DESCRIPTION "The maximum number of retries allowed for a 593 broadcast message." 594 ::= { lowpanObjects 9 } 596 -- Conformance information 598 lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 } 599 lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 } 601 lowpanGeneralGroup OBJECT-GROUP 602 OBJECTS { lowpanDeviceCapabilities, 603 lowpanRouteNextHopAddress, 604 lowpanRouteNextHopAddress, 605 lowpanRoutingProtocol} 606 STATUS current 607 DESCRIPTION "A collection of objects for basic 6LoWPAN 608 monitoring" 609 ::= { lowpanGroups 1 } 611 lowpanCoreCompliance MODULE-COMPLIANCE 612 STATUS current 613 DESCRIPTION 614 "The compliance statement for SNMP entities 615 which implement the LOWPAN-MIB." 616 MODULE -- this module 617 MANDATORY-GROUPS { lowpanGeneralGroup } 619 ::= { lowpanCompliances 1 } 621 lowpanCoreReadOnlyCompliance MODULE-COMPLIANCE 622 STATUS current 623 DESCRIPTION 624 "The compliance statement for SNMP entities 625 which implement the LOWPAN-MIB without support 626 for read-write (i.e. in read-only mode) . 627 " 628 MODULE -- this module 629 MANDATORY-GROUPS { lowpanGeneralGroup } 631 OBJECT lowpanAckTimeout 632 MIN-ACCESS read-only 633 DESCRIPTION 634 "Write access is not required." 636 OBJECT lowpanBroadcastRetries 637 MIN-ACCESS read-only 638 DESCRIPTION 639 "Write access is not required." 641 ::= { lowpanCompliances 2 } 643 END 644 7. Security Considerations 646 There are a number of management objects defined in this MIB module 647 with a MAX-ACCESS clause of read-write and/or read-create. Such 648 objects may be considered sensitive or vulnerable in some network 649 environments. The support for SET operations in a non-secure 650 environment without proper protection can have a negative effect on 651 network operations. These are the objects and their sensitivity/ 652 vulnerability: 654 o The vulnerabilities for lowpanAckTimeout object will be discussed 655 in the next version of the draft 657 o The vulnerabilities for lowpanBroadcastRetries object will be 658 discussed in the next version of the draft 660 Some of the readable objects in this MIB module (i.e., objects with a 661 MAX-ACCESS other than not-accessible) may be considered sensitive or 662 vulnerable in some network environments. It is thus important to 663 control even GET and/or NOTIFY access to these objects and possibly 664 to even encrypt the values of these objects when sending them over 665 the network via SNMP. The vulnerabilities will be discussed in next 666 versions on this draft 668 SNMP versions prior to SNMPv3 did not include adequate security. 669 Even if the network itself is secure (for example by using IPSec), 670 even then, there is no control as to who on the secure network is 671 allowed to access and GET/SET (read/change/create/delete) the objects 672 in this MIB module. 674 It is RECOMMENDED that implementers consider the security features as 675 provided by the SNMPv3 framework (see [RFC3410], section 8), 676 including full support for the SNMPv3 cryptographic mechanisms (for 677 authentication and privacy). 679 Further, deployment of SNMP versions prior to SNMPv3 is NOT 680 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 681 enable cryptographic security. It is then a customer/operator 682 responsibility to ensure that the SNMP entity giving access to an 683 instance of this MIB module is properly configured to give access to 684 the objects only to those principals (users) that have legitimate 685 rights to indeed GET or SET (change/create/delete) them. 687 8. IANA Considerations 689 The MIB module in this document uses the following IANA-assigned 690 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 692 Descriptor OBJECT IDENTIFIER value 693 ---------- ----------------------- 695 lowpanTCMIB { mib-2 XXX } 696 lowpanMIB { mib-2 YYY } 698 9. Contributors 700 Thanks to the contribution from 6LoWPAN WG MIB Doctor, Juergen 701 Schoenwaelder for the review and useful discussion for writing this 702 document 704 10. Acknowledgements 706 Thanks to Ali Hammad Akbar, Shafique Ahmed Choadry, Chae-Seong Lim, 707 Seong-Soon Joo, and Geoff Mulligan for their useful discussion and 708 support for writing this document and to Glenn M. Keeni for reviewing 709 the MIB module. 711 11. References 713 11.1. Normative References 715 [RFC2119] Bradner, S., "Key 716 words for use in 717 RFCs to Indicate 718 Requirement Levels", 719 BCP 14, RFC 2119, 720 March 1997. 722 [RFC2578] McCloghrie, K., Ed., 723 Perkins, D., Ed., 724 and J. 725 Schoenwaelder, Ed., 726 "Structure of 727 Management 728 Information Version 729 2 (SMIv2)", STD 58, 730 RFC 2578, 731 April 1999. 733 [RFC2579] McCloghrie, K., Ed., 734 Perkins, D., Ed., 735 and J. 736 Schoenwaelder, Ed., 737 "Textual Conventions 738 for SMIv2", STD 58, 739 RFC 2579, 740 April 1999. 742 [RFC2580] McCloghrie, K., 743 Perkins, D., and J. 744 Schoenwaelder, 745 "Conformance 746 Statements for 747 SMIv2", STD 58, 748 RFC 2580, 749 April 1999. 751 [RFC3418] Presuhn, R., 752 "Management 753 Information Base 754 (MIB) for the Simple 755 Network Management 756 Protocol (SNMP)", 757 STD 62, RFC 3418, 758 December 2002. 760 [RFC2863] McCloghrie, K. and 761 F. Kastenholz, "The 762 Interfaces Group 763 MIB", RFC 2863, 764 June 2000. 766 [RFC4944] Montenegro, G., 767 Kushalnagar, N., 768 Hui, J., and D. 769 Culler, 770 "Transmission of 771 IPv6 Packets over 772 IEEE 802.15.4 773 Networks", RFC 4944, 774 September 2007. 776 [IEEE802.15.4] 802.15.4-2003, IEEE 777 Standard., "Wireless 778 medium access 779 control and physical 780 layer specifications 781 for low-rate 782 wireless personal 783 area networks.", 784 May 2003. 786 11.2. Informative References 788 [RFC3410] Case, J., Mundy, R., 789 Partain, D., and B. 790 Stewart, 791 "Introduction and 792 Applicability 793 Statements for 794 Internet-Standard 795 Management 796 Framework", 797 RFC 3410, 798 December 2002. 800 [RFC4919] Kushalnagar, N., 801 Montenegro, G., and 802 C. Schumacher, "IPv6 803 over Low-Power 804 Wireless Personal 805 Area Networks 806 (6LoWPANs): 807 Overview, 808 Assumptions, Problem 809 Statement, and 810 Goals", RFC 4919, 811 August 2007. 813 [EUI64] 802.15.4-2003, IEEE 814 Standard., 815 "GUIDELINES FOR 64- 816 BIT GLOBAL 817 IDENTIFIER (EUI-64) 818 REGISTRATION 819 AUTHORITY". 821 [I-D.draft-ietf-roll-rpl] Winter, T., Thubert, 822 P., and ROLL. Design 823 Team, "RPL: Routing 824 Protocol for Low 825 Power and Lossy 826 Networks", (Work in 827 progress), 828 October 2009. 830 [I-D.draft-iwao-roll-dadr] Iwao, T., 831 "Distributed 832 Autonomous Depth- 833 first Routing 834 Protocol in LLN", 835 (Work in progress), 836 July 2009. 838 [I-D.draft-goyal-roll-dv] Goyal, M., "A 839 Distance Vector 840 Protocol for Routing 841 Over Low Power and 842 Lossy Networks", 843 (Work in progress), 844 July 2009. 846 [I-D.montenegro-6lowpan-dymo-low-routing] Kim, K., Montenegro, 847 G., Daniel Park, S., 848 Chakeres, I., and S. 849 Yoo, "Dynamic MANET 850 On-demand for 851 6LoWPAN (DYMO-low) 852 Routing", (Work in 853 progress), 854 December 2007. 856 [I-D.daniel-6lowpan-hilow-hierarchical-routing] Kim, K., Yoo, S., 857 Park, J., Daniel 858 Park, S., and J. 859 Lee, "Hierarchical 860 Routing over 6LoWPAN 861 (HiLow)", (Work in 862 progress), 863 December 2007. 865 [I-D.daniel-6lowpan-load-adhoc-routing] Kim, K., Daniel 866 Park, S., 867 Montenegro, G., Yoo, 868 S., and Kushalnagar. 869 N., "6LoWPAN Ad Hoc 870 On-Demand Distance 871 Vector Routing 872 (LOAD)", (Work in 873 progress), 874 December 2007. 876 Appendix A. Open Issues 878 SNMP based access to 802.15.4 PHY/MAC PIBs should also be provided by 879 assigning them object identifiers. 881 Authors' Addresses 883 Kim Ki Hyung 884 picosNet Corp/Ajou Univ. 885 San 5 Wonchun-dong, Yeongtong-gu 886 Suwon-si, Gyeonggi-do 443-749 887 KOREA 889 Phone: +82 31 219 2433 890 EMail: kkim86@picosnet.com 892 Hamid Mukhtar (editor) 893 ETRI 894 USN Research Division, ETRI, 161 Gajeong-dong, Yuseong-gu, 895 Daejeon 305-350 896 KOREA 898 Phone: +82 42 860 5435 899 EMail: hamid@etri.re.kr 901 Seong-Soon Joo 902 ETRI 903 USN Research Division, ETRI, 161 Gajeong-dong, Yuseong-gu, 904 Daejeon 305-350 905 KOREA 907 Phone: +82 42 860 6333 908 EMail: ssjoo@etri.re.kr 910 Seung Wha Yoo 911 Ajou University 912 San 5 Wonchun-dong, Yeongtong-gu 913 Suwon-si, Gyeonggi-do 443-749 914 KOREA 916 Phone: +82 31 219 1603 917 EMail: swyoo@ajou.ac.kr 918 Soohong Daniel Park 919 SAMSUNG Electronics 920 Mobile Platform Laboratory, 921 SAMSUNG Electronics 416 Maetan-3dong, Yeongtong-gu 922 Suwon-si, Gyeonggi-do 442-742 923 KOREA 925 Phone: +82 31 200 4508 926 EMail: soohong.park@samsung.com