idnits 2.17.1 draft-ietf-6lo-lowpan-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 date (September 5, 2014) is 3521 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCXXXX' is mentioned on line 123, but not defined -- Obsolete informational reference (is this intentional?): RFC 2460 (Obsoleted by RFC 8200) == Outdated reference: A later version (-17) exists of draft-ietf-6lo-btle-03 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Schoenwaelder 3 Internet-Draft A. Sehgal 4 Intended status: Standards Track Jacobs University 5 Expires: March 9, 2015 T. Tsou 6 Huawei Technologies (USA) 7 C. Zhou 8 Huawei Technologies 9 September 5, 2014 11 Definition of Managed Objects for IPv6 over Low-Power Wireless Personal 12 Area Networks (6LoWPANs) 13 draft-ietf-6lo-lowpan-mib-04 15 Abstract 17 This document defines a portion of the Management Information Base 18 (MIB) for use with network management protocols in the Internet 19 community. In particular, it defines objects for managing IPv6 over 20 Low-Power Wireless Personal Area Networks (6LoWPANs). 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on March 9, 2015. 39 Copyright Notice 41 Copyright (c) 2014 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. The Internet-Standard Management Framework . . . . . . . . . 2 58 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 61 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 63 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 64 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 65 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 66 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 67 10.2. Informative References . . . . . . . . . . . . . . . . . 26 69 1. Introduction 71 This document defines a portion of the Management Information Base 72 (MIB) for use with network management protocols. In particular it 73 defines objects for managing IPv6 over Low-Power Wireless Personal 74 Area Networks (6LoWPANs) [RFC4944]. 76 While a MIB module provides a direct binding for accessing data via 77 the Simple Network Management Protocol (SNMP) [RFC3410], supporting 78 SNMP may not always be affordable on constrained devices. Other 79 protocols to access data modeled in MIB modules are possible and 80 proposals have been made recently to provide bindings to the 81 Constrained Application Protocol (CoAP) [RFC7252]. 83 2. The Internet-Standard Management Framework 85 For a detailed overview of the documents that describe the current 86 Internet-Standard Management Framework, please refer to section 7 of 87 RFC 3410 [RFC3410]. 89 Managed objects are accessed via a virtual information store, termed 90 the Management Information Base or MIB. MIB objects are generally 91 accessed through the Simple Network Management Protocol (SNMP). 92 Objects in the MIB are defined using the mechanisms defined in the 93 Structure of Management Information (SMI). This document specifies a 94 MIB module that is compliant to the SMIv2, which is described in STD 95 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 96 2580 [RFC2580]. 98 3. Conventions 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 102 "OPTIONAL" in this document are to be interpreted as described in RFC 103 2119 [RFC2119]. 105 4. Overview 107 The left part of Figure 1 provides an overview of the IETF protocols 108 designed for constrained devices. The right part lists the MIB 109 modules providing monitoring and troubleshooting support ([RFC4113], 110 [RFC4292], [RFC4293], [RFC2863]). The LOWPAN-MIB defined in this 111 document fills a hole by providing monitoring and troubleshooting 112 support for the 6LoWPAN layer. 114 Protocol Layer MIB Modules 115 +--------------------+ 116 | CoAP [RFC7252] | 117 +--------------------+ +--------------------------+ 118 | UDP [RFC0768] | | UDP-MIB [RFC4113] | 119 +--------------------+ +--------------------------+ 120 | IPv6 [RFC2460] | | IP-MIB [RFC4293] | 121 | ICMPv6 [RFC4443] | | IP-FORWARD-MIB [RFC4292] | 122 +--------------------+ +--------------------------+ 123 | 6LoWPAN [RFC4944] | | LOWPAN-MIB [RFCXXXX] | 124 +--------------------+ +--------------------------+ 125 | IF-MIB [RFC2863] | 126 +--------------------+ +--------------------------+ 127 | IEEE 802.15.4, ... | 128 +--------------------+ 130 /* RFC Ed.: replace XXXX above with RFC number 131 and remove this note */ 133 Figure 1: Protocol Layers and MIB Modules 135 The LOWPAN-MIB module is primarily a collection of counters that 136 reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer. 137 The objects are defined twice, once to report the global statistics 138 as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN 139 layer statistics. The per interface statistics are optional to 140 implement. The object identifier registration tree has the following 141 structure: 143 /* RFC Ed.: replace XXXX below with IANA assigned OID number 144 and remove this note */ 146 ---- lowpanMIB(1.3.6.1.2.1.XXXX) 147 +---- lowpanNotifications(0) 148 +---- lowpanObjects(1) 149 | +---- lowpanStats(1) 150 | | +--r- lowpanReasmTimeout(1) Unsigned32 151 | | +--r- lowpanInReceives(2) Counter32 152 | | +--r- lowpanInHdrErrors(3) Counter32 153 | | +--r- lowpanInMeshReceives(4) Counter32 154 | | +--r- lowpanInMeshForwds(5) Counter32 155 | | +--r- lowpanInMeshDelivers(6) Counter32 156 | | +--r- lowpanInReasmReqds(7) Counter32 157 | | +--r- lowpanInReasmFails(8) Counter32 158 | | +--r- lowpanInReasmOKs(9) Counter32 159 | | +--r- lowpanInCompReqds(10) Counter32 160 | | +--r- lowpanInCompFails(11) Counter32 161 | | +--r- lowpanInCompOKs(12) Counter32 162 | | +--r- lowpanInDiscards(13) Counter32 163 | | +--r- lowpanInDelivers(14) Counter32 164 | | +--r- lowpanOutRequests(15) Counter32 165 | | +--r- lowpanOutCompReqds(16) Counter32 166 | | +--r- lowpanOutCompFails(17) Counter32 167 | | +--r- lowpanOutCompOKs(18) Counter32 168 | | +--r- lowpanOutFragReqds(19) Counter32 169 | | +--r- lowpanOutFragFails(20) Counter32 170 | | +--r- lowpanOutFragOKs(21) Counter32 171 | | +--r- lowpanOutFragCreates(22) Counter32 172 | | +--r- lowpanOutMeshHopLimitExceeds(23) Counter32 173 | | +--r- lowpanOutMeshNoRoutes(24) Counter32 174 | | +--r- lowpanOutMeshRequests(25) Counter32 175 | | +--r- lowpanOutMeshForwds(26) Counter32 176 | | +--r- lowpanOutMeshTransmits(27) Counter32 177 | | +--r- lowpanOutDiscards(28) Counter32 178 | | +--r- lowpanOutTransmits(29) Counter32 179 | +---- lowpanIfStatsTable(2) 180 | +---- lowpanIfStatsEntry(1) [ifIndex] 181 | +--r- lowpanIfReasmTimeout(1) Unsigned32 182 | +--r- lowpanIfInReceives(2) Counter32 183 | +--r- lowpanIfInHdrErrors(3) Counter32 184 | +--r- lowpanIfInMeshReceives(4) Counter32 185 | +--r- lowpanIfInMeshForwds(5) Counter32 186 | +--r- lowpanIfInMeshDelivers(6) Counter32 187 | +--r- lowpanIfInReasmReqds(7) Counter32 188 | +--r- lowpanIfInReasmFails(8) Counter32 189 | +--r- lowpanIfInReasmOKs(9) Counter32 190 | +--r- lowpanIfInCompReqds(10) Counter32 191 | +--r- lowpanIfInCompFails(11) Counter32 192 | +--r- lowpanIfInCompOKs(12) Counter32 193 | +--r- lowpanIfInDiscards(13) Counter32 194 | +--r- lowpanIfInDelivers(14) Counter32 195 | +--r- lowpanIfOutRequests(15) Counter32 196 | +--r- lowpanIfOutCompReqds(16) Counter32 197 | +--r- lowpanIfOutCompFails(17) Counter32 198 | +--r- lowpanIfOutCompOKs(18) Counter32 199 | +--r- lowpanIfOutFragReqds(19) Counter32 200 | +--r- lowpanIfOutFragFails(20) Counter32 201 | +--r- lowpanIfOutFragOKs(21) Counter32 202 | +--r- lowpanIfOutFragCreates(22) Counter32 203 | +--r- lowpanIfOutMeshHopLimitExceeds(23) Counter32 204 | +--r- lowpanIfOutMeshNoRoutes(24) Counter32 205 | +--r- lowpanIfOutMeshRequests(25) Counter32 206 | +--r- lowpanIfOutMeshForwds(26) Counter32 207 | +--r- lowpanIfOutMeshTransmits(27) Counter32 208 | +--r- lowpanIfOutDiscards(28) Counter32 209 | +--r- lowpanIfOutTransmits(29) Counter32 210 +---- lowpanConformance(2) 211 +---- lowpanGroups(1) 212 | +---- lowpanStatsGroup(1) 213 | +---- lowpanStatsMeshGroup(2) 214 | +---- lowpanIfStatsGroup(3) 215 | +---- lowpanIfStatsMeshGroup(4) 216 +---- lowpanCompliances(2) 217 +---- lowpanCompliance(1) 219 The counters defined in the LOWPAN-MIB module provide information 220 about the 6LoWPAN datagrams received and transmitted and how they are 221 processed in the 6LoWPAN layer. For link-layers that use the 6LoWPAN 222 dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a 223 6LoWPAN datagram is a datagram with a dispatch byte matching the bit 224 patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch 225 byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) 226 are not considered to be 6LoWPAN datagram by this specification. 227 Other radio technologies may use different mechanisms to identify 228 6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link 229 Control and Adaptation Protocol uses Channel Identifiers 230 [I-D.ietf-6lo-btle]). 232 The Case Diagram [CASE] in Figure 2 illustrates the conceptual 233 relationships between the counters. Implementations may choose to 234 implement the processing of 6LoWPAN datagrams in a different order. 236 The generic InDiscards and OutDiscards counters can be incremented 237 anytime when 6LoWPAN datagrams are discarded due to reasons not 238 covered by the other more specific counters. For example, an 239 implementation discarding 6LoWPAN datagrams while all buffers are 240 used for ongoing packet reassemblies will increment the relevant 241 InDiscards counters for each discarded 6LoWPAN datagram. 243 IPv6 layer 244 ^ v 245 InDelivers -+- -+- OutRequests 246 | | 247 InDiscards <--+ | 248 | | 249 InCompOKs .-->| |-->. OutCompReqds 250 InCompFails <--| | | +--> OutCompFails 251 InCompReqds `<--+ +<--' OutCompOKs 252 | | 253 | +-->. OutFragReqds 254 InReasmOKs .-->| | +--> OutFragFails 255 InReasmFails <--| | | -+- OutFragOKs 256 InReasmReqds `<--+ +<--' OutFragCreates 257 | | 258 | | 259 InMeshDelivers |<--. | 260 InMeshForwds | |-->. | 261 InMeshReceives +-->' | | 262 | +--> | OutMeshHopLimitExceeds 263 | +--> | OutMeshNoRoutes 264 | | | 265 | | .<--+ OutMeshRequests 266 | `-->| | OutMeshForwds 267 | `-->| OutMeshTransmits 268 | | 269 InHdrErrors <--+ +--> OutDiscards 270 | | 271 InReceives -+- -+- OutTransmits 272 ^ v 273 interface layer 275 Figure 2: Conceptual Relationship between LOWPAN-MIB Counters 277 The fragmentation related counters have been modeled after the 278 fragmentation related counters of the IP-MIB [RFC4293]. The discard 279 counters have been placed at the end of the input and output chains 280 but they can be bumped any time if a datagram is discarded for a 281 reason not covered by the other counters. 283 The compression related counters provide insights into compression 284 requests and in particular also compression related failures. Note 285 that the diagram is conceptual in the sense that compression happens 286 after reassembly for incoming 6LoWPAN datagrams and compression 287 happens before fragmentation for outgoing 6LoWPAN datagrams. 288 Implementations may choose to implement things slightly differently. 289 For example, implementations may decompress FRAG1 fragments as soon 290 as they are received, not waiting for reassembly to complete. 292 The mesh header processing related counters do not have an explicit 293 discard counter. Implementations that do not support mesh forwarding 294 MUST count the number of received 6LoWPAN datagrams with a MESH 295 header (lowpanInMeshReceives) but they MUST NOT increment the 296 lowpanInMeshReceives and lowpanInMeshDelivers counters if these 297 6LoWPAN datagrams are dropped. 299 5. Relationship to Other MIB Modules 301 The MIB module imports definitions from SNMPv2-SMI [RFC2578], 302 SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863]. 304 6. Definitions 306 LOWPAN-MIB DEFINITIONS ::= BEGIN 308 IMPORTS 309 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 310 FROM SNMPv2-SMI -- RFC 2578 311 OBJECT-GROUP, MODULE-COMPLIANCE 312 FROM SNMPv2-CONF -- RFC 2580 313 ifIndex FROM IF-MIB; -- RFC 2863 315 lowpanMIB MODULE-IDENTITY 316 LAST-UPDATED "201409050000Z" 317 ORGANIZATION 318 "IETF IPv6 over Networks of Resource-constrained Nodes 319 Working Group" 320 CONTACT-INFO 321 "WG Email: 6lo@ietf.org 322 WG Web: http://tools.ietf.org/wg/6lo/ 324 Juergen Schoenwaelder 325 Jacobs University Bremen 326 Email: j.schoenwaelder@jacobs-university.de 328 Anuj Sehgal 329 Jacobs University Bremen 330 Email: s.anuj@jacobs-university.de 332 Tina Tsou 333 Huawei Technologies 334 Email: tina.tsou.zouting@huawei.com 336 Cathy Zhou 337 Huawei Technologies 338 Email: cathyzhou@huawei.com" 340 DESCRIPTION 341 "The MIB module for monitoring nodes implementing the IPv6 342 over Low-Power Wireless Personal Area Networks (6LoWPAN) 343 protocol. 345 Copyright (c) 2014 IETF Trust and the persons identified as 346 authors of the code. All rights reserved. 348 Redistribution and use in source and binary forms, with or 349 without modification, is permitted pursuant to, and subject 350 to the license terms contained in, the Simplified BSD 351 License set forth in Section 4.c of the IETF Trust's 352 Legal Provisions Relating to IETF Documents 353 (http://trustee.ietf.org/license-info)." 355 REVISION "201409050000Z" 356 DESCRIPTION 357 "Initial version, published as RFC XXXX." 358 -- RFC Ed.: replace XXXX with RFC number and remove this note 360 ::= { mib-2 YYYY } 361 -- RFC Ed.: replace YYYY with IANA assigned number 363 -- object definitions 365 lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } 366 lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } 367 lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } 369 lowpanStats OBJECT IDENTIFIER ::= { lowpanObjects 1 } 371 lowpanReasmTimeout OBJECT-TYPE 372 SYNTAX Unsigned32 373 UNITS "seconds" 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The maximum number of seconds that received fragments are 378 held while they are awaiting reassembly at this entity." 379 ::= { lowpanStats 1 } 381 lowpanInReceives OBJECT-TYPE 382 SYNTAX Counter32 383 MAX-ACCESS read-only 384 STATUS current 385 DESCRIPTION 386 "The total number of 6LoWPAN datagrams received, including 387 those received in error." 389 ::= { lowpanStats 2 } 391 lowpanInHdrErrors OBJECT-TYPE 392 SYNTAX Counter32 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "The number of received 6LoWPAN datagrams discarded due to 397 errors in their headers, including unknown dispatch values." 398 ::= { lowpanStats 3 } 400 lowpanInMeshReceives OBJECT-TYPE 401 SYNTAX Counter32 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "The number of received 6LoWPAN datagrams with a MESH 406 header." 407 ::= { lowpanStats 4 } 409 lowpanInMeshForwds OBJECT-TYPE 410 SYNTAX Counter32 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The number of received 6LoWPAN datagrams requiring MESH 415 forwarding." 416 ::= { lowpanStats 5 } 418 lowpanInMeshDelivers OBJECT-TYPE 419 SYNTAX Counter32 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "The number of received 6LoWPAN datagrams with a MESH header 424 delivered to the local system." 425 ::= { lowpanStats 6 } 427 lowpanInReasmReqds OBJECT-TYPE 428 SYNTAX Counter32 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The number of received 6LoWPAN fragments that needed to 433 be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN 434 datagrams." 435 ::= { lowpanStats 7 } 437 lowpanInReasmFails OBJECT-TYPE 438 SYNTAX Counter32 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "The number of failures detected by the re-assembly 443 algorithm (e.g., timeouts). Note that this is not 444 necessarily a count of discarded 6LoWPAN fragments 445 since implementations can lose track of the number 446 of fragments by combining them as received." 447 ::= { lowpanStats 8 } 449 lowpanInReasmOKs OBJECT-TYPE 450 SYNTAX Counter32 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "The number of IPv6 packets successfully reassembled." 455 ::= { lowpanStats 9 } 457 lowpanInCompReqds OBJECT-TYPE 458 SYNTAX Counter32 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The number of 6LoWPAN datagrams requiring header 463 decompression." 464 ::= { lowpanStats 10 } 466 lowpanInCompFails OBJECT-TYPE 467 SYNTAX Counter32 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The number of 6LoWPAN datagrams where header decompression 472 failed (e.g., because the necessary context information was 473 not available)." 474 ::= { lowpanStats 11 } 476 lowpanInCompOKs OBJECT-TYPE 477 SYNTAX Counter32 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 "The number of 6LoWPAN datagrams where header decompression 482 was successful." 483 ::= { lowpanStats 12 } 485 lowpanInDiscards OBJECT-TYPE 486 SYNTAX Counter32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The number of received 6LoWPAN datagrams for which no 491 problems were encountered to prevent their continued 492 processing, but were discarded (e.g., for lack of buffer 493 space). Note that this counter does not include any 494 datagrams discarded due to a reassembly failure or a 495 compression failure." 496 ::= { lowpanStats 13 } 498 lowpanInDelivers OBJECT-TYPE 499 SYNTAX Counter32 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The total number of IPv6 packets successfully delivered 504 to the IPv6 layer." 505 ::= { lowpanStats 14 } 507 lowpanOutRequests OBJECT-TYPE 508 SYNTAX Counter32 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The total number of IPv6 packets supplied by the IPv6 513 layer." 514 ::= { lowpanStats 15 } 516 lowpanOutCompReqds OBJECT-TYPE 517 SYNTAX Counter32 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The total number of IPv6 packets for which header 522 compression was attempted." 523 ::= { lowpanStats 16 } 525 lowpanOutCompFails OBJECT-TYPE 526 SYNTAX Counter32 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The total number of IPv6 packets for which header 531 compression failed." 532 ::= { lowpanStats 17 } 534 lowpanOutCompOKs OBJECT-TYPE 535 SYNTAX Counter32 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The total number of IPv6 packets for which header 540 compression was successful." 541 ::= { lowpanStats 18 } 543 lowpanOutFragReqds OBJECT-TYPE 544 SYNTAX Counter32 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "The number of IPv6 packets that required fragmentation 549 in order to be transmitted." 550 ::= { lowpanStats 19 } 552 lowpanOutFragFails OBJECT-TYPE 553 SYNTAX Counter32 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The number of IPv6 packets that have been discarded because 558 fragmentation failed." 559 ::= { lowpanStats 20 } 561 lowpanOutFragOKs OBJECT-TYPE 562 SYNTAX Counter32 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The number of IPv6 packets that have been successfully 567 fragmented." 568 ::= { lowpanStats 21 } 570 lowpanOutFragCreates OBJECT-TYPE 571 SYNTAX Counter32 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The number of 6LoWPAN fragments that have been 576 generated as a result of fragmentation. This includes 577 both FRAG1 and FRAGN 6LoWPAN datagrams." 578 ::= { lowpanStats 22 } 580 lowpanOutMeshHopLimitExceeds OBJECT-TYPE 581 SYNTAX Counter32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The number of 6LoWPAN datagrams with a MESH header that 586 were dropped because the hop limit has been exceeded." 587 ::= { lowpanStats 23 } 589 lowpanOutMeshNoRoutes OBJECT-TYPE 590 SYNTAX Counter32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The number of 6LoWPAN datagrams with a MESH header that 595 were dropped because there was no forwarding information 596 available." 597 ::= { lowpanStats 24 } 599 lowpanOutMeshRequests OBJECT-TYPE 600 SYNTAX Counter32 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "The number of 6LoWPAN datagrams requiring MESH header 605 encapsulation." 606 ::= { lowpanStats 25 } 608 lowpanOutMeshForwds OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The number of 6LoWPAN datagrams with a MESH header for 614 which suitable forwarding information was available." 615 ::= { lowpanStats 26 } 617 lowpanOutMeshTransmits OBJECT-TYPE 618 SYNTAX Counter32 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The number of 6LoWPAN datagrams with a MESH header 623 created." 624 ::= { lowpanStats 27 } 626 lowpanOutDiscards OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The number of IPv6 packets for which no problem was 632 encountered to prevent their transmission to their 633 destination, but were discarded (e.g., for lack of 634 buffer space)." 635 ::= { lowpanStats 28 } 637 lowpanOutTransmits OBJECT-TYPE 638 SYNTAX Counter32 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "The total number of 6LoWPAN datagram that this entity 643 supplied to the lower layers for transmission." 644 ::= { lowpanStats 29 } 646 lowpanIfStatsTable OBJECT-TYPE 647 SYNTAX SEQUENCE OF LowpanIfStatsEntry 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "A table providing per interface statistics." 652 ::= { lowpanObjects 2 } 654 lowpanIfStatsEntry OBJECT-TYPE 655 SYNTAX LowpanIfStatsEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "An entry providing statistics for a specific interface." 660 INDEX { ifIndex } 661 ::= { lowpanIfStatsTable 1 } 663 LowpanIfStatsEntry ::= SEQUENCE { 664 lowpanIfReasmTimeout Unsigned32, 665 lowpanIfInReceives Counter32, 666 lowpanIfInHdrErrors Counter32, 667 lowpanIfInMeshReceives Counter32, 668 lowpanIfInMeshForwds Counter32, 669 lowpanIfInMeshDelivers Counter32, 670 lowpanIfInReasmReqds Counter32, 671 lowpanIfInReasmFails Counter32, 672 lowpanIfInReasmOKs Counter32, 673 lowpanIfInCompReqds Counter32, 674 lowpanIfInCompFails Counter32, 675 lowpanIfInCompOKs Counter32, 676 lowpanIfInDiscards Counter32, 677 lowpanIfInDelivers Counter32, 678 lowpanIfOutRequests Counter32, 679 lowpanIfOutCompReqds Counter32, 680 lowpanIfOutCompFails Counter32, 681 lowpanIfOutCompOKs Counter32, 682 lowpanIfOutFragReqds Counter32, 683 lowpanIfOutFragFails Counter32, 684 lowpanIfOutFragOKs Counter32, 685 lowpanIfOutFragCreates Counter32, 686 lowpanIfOutMeshHopLimitExceeds Counter32, 687 lowpanIfOutMeshNoRoutes Counter32, 688 lowpanIfOutMeshRequests Counter32, 689 lowpanIfOutMeshForwds Counter32, 690 lowpanIfOutMeshTransmits Counter32, 691 lowpanIfOutDiscards Counter32, 692 lowpanIfOutTransmits Counter32 693 } 695 lowpanIfReasmTimeout OBJECT-TYPE 696 SYNTAX Unsigned32 697 UNITS "seconds" 698 MAX-ACCESS read-only 699 STATUS current 700 DESCRIPTION 701 "The maximum number of seconds that received fragments are 702 held while they are awaiting reassembly at this interface." 703 ::= { lowpanIfStatsEntry 1 } 705 lowpanIfInReceives OBJECT-TYPE 706 SYNTAX Counter32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The total number of 6LoWPAN datagrams received on this 711 interface, including those received in error." 712 ::= { lowpanIfStatsEntry 2 } 714 lowpanIfInHdrErrors OBJECT-TYPE 715 SYNTAX Counter32 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "The number of 6LoWPAN datagrams received on this 720 interface that were discarded due to errors in 721 their headers, including unknown dispatch values." 722 ::= { lowpanIfStatsEntry 3 } 724 lowpanIfInMeshReceives OBJECT-TYPE 725 SYNTAX Counter32 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "The number of 6LoWPAN datagrams reveived on this 730 interface with a MESH header." 731 ::= { lowpanIfStatsEntry 4 } 733 lowpanIfInMeshForwds OBJECT-TYPE 734 SYNTAX Counter32 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "The number of 6LoWPAN datagrams received on this 739 interface requiring MESH forwarding." 740 ::= { lowpanIfStatsEntry 5 } 742 lowpanIfInMeshDelivers OBJECT-TYPE 743 SYNTAX Counter32 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The number of 6LoWPAN datagrams received on this 748 interface with a MESH header delivered to the local 749 system." 750 ::= { lowpanIfStatsEntry 6 } 752 lowpanIfInReasmReqds OBJECT-TYPE 753 SYNTAX Counter32 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The number of 6LoWPAN fragments received on this 758 interface that needed to be reassembled. This 759 includes both FRAG1 and FRAGN 6LoWPAN datagrams." 760 ::= { lowpanIfStatsEntry 7 } 762 lowpanIfInReasmFails OBJECT-TYPE 763 SYNTAX Counter32 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "The number of failures detected by the re-assembly 768 algorithm (e.g., timeouts) for datagrams received 769 on this interface. Note that this is not necessarily 770 a count of discarded 6LoWPAN fragments since 771 implementations can lose track of the number 772 of fragments by combining them as received." 773 ::= { lowpanIfStatsEntry 8 } 775 lowpanIfInReasmOKs OBJECT-TYPE 776 SYNTAX Counter32 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "The number of IPv6 packets successfully reassembled 781 from fragments received on this interface." 782 ::= { lowpanIfStatsEntry 9 } 784 lowpanIfInCompReqds OBJECT-TYPE 785 SYNTAX Counter32 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "The number of 6LoWPAN datagrams received on this 790 interface requiring header decompression." 791 ::= { lowpanIfStatsEntry 10 } 793 lowpanIfInCompFails OBJECT-TYPE 794 SYNTAX Counter32 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "The number of 6LoWPAN datagrams received on this 799 interface where header decompression failed (e.g., 800 because the necessary context information was 801 not available)." 802 ::= { lowpanIfStatsEntry 11 } 804 lowpanIfInCompOKs OBJECT-TYPE 805 SYNTAX Counter32 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The number of 6LoWPAN datagrams received on this 810 interface where header decompression was successful." 811 ::= { lowpanIfStatsEntry 12 } 813 lowpanIfInDiscards OBJECT-TYPE 814 SYNTAX Counter32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The number of 6LoWPAN datagrams received on this 819 interface for which no problems were encountered to 820 prevent their continued processing, but were discarded 821 (e.g., for lack of buffer space). Note that this 822 counter does not include any datagrams discarded due 823 to a reassembly failure or a compression failure." 824 ::= { lowpanIfStatsEntry 13 } 826 lowpanIfInDelivers OBJECT-TYPE 827 SYNTAX Counter32 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The total number of IPv6 packets received on this 832 interface that were successfully delivered to the 833 IPv6 layer." 834 ::= { lowpanIfStatsEntry 14 } 836 lowpanIfOutRequests OBJECT-TYPE 837 SYNTAX Counter32 838 MAX-ACCESS read-only 839 STATUS current 840 DESCRIPTION 841 "The total number of IPv6 packets supplied by the IPv6 842 layer to be sent over this interface." 843 ::= { lowpanIfStatsEntry 15 } 845 lowpanIfOutCompReqds OBJECT-TYPE 846 SYNTAX Counter32 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The total number of IPv6 packets to be sent over 851 this interface for which header compression was 852 attempted." 853 ::= { lowpanIfStatsEntry 16 } 855 lowpanIfOutCompFails OBJECT-TYPE 856 SYNTAX Counter32 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "The total number of IPv6 packets to be sent over 861 this interface for which header compression failed." 862 ::= { lowpanIfStatsEntry 17 } 864 lowpanIfOutCompOKs OBJECT-TYPE 865 SYNTAX Counter32 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The total number of IPv6 packets to be sent over 870 this interface for which header compression was 871 successful." 872 ::= { lowpanIfStatsEntry 18 } 874 lowpanIfOutFragReqds OBJECT-TYPE 875 SYNTAX Counter32 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The number of IPv6 packets to be sent over this 880 interface that required fragmentation in order 881 to be transmitted." 882 ::= { lowpanIfStatsEntry 19 } 884 lowpanIfOutFragFails OBJECT-TYPE 885 SYNTAX Counter32 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "The number of IPv6 packets to be sent over this 890 interface that have been discarded because 891 fragmentation failed." 892 ::= { lowpanIfStatsEntry 20 } 894 lowpanIfOutFragOKs OBJECT-TYPE 895 SYNTAX Counter32 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The number of IPv6 packets to be sent over this 900 interface that have been successfully fragmented." 901 ::= { lowpanIfStatsEntry 21 } 903 lowpanIfOutFragCreates OBJECT-TYPE 904 SYNTAX Counter32 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The number of 6LoWPAN fragments that have been 909 generated on this interface as a result of 910 fragmentation. This includes both FRAG1 and FRAGN 911 6LoWPAN datagrams." 912 ::= { lowpanIfStatsEntry 22 } 914 lowpanIfOutMeshHopLimitExceeds OBJECT-TYPE 915 SYNTAX Counter32 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 "The number of 6LoWPAN datagrams to be sent on this 920 interface with a MESH header that were dropped 921 because the hop limit has been exceeded." 922 ::= { lowpanIfStatsEntry 23 } 924 lowpanIfOutMeshNoRoutes OBJECT-TYPE 925 SYNTAX Counter32 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "The number of 6LoWPAN datagrams to be sent on this 930 interface with a MESH header that were dropped 931 because there was no forwarding information available." 932 ::= { lowpanIfStatsEntry 24 } 934 lowpanIfOutMeshRequests OBJECT-TYPE 935 SYNTAX Counter32 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The number of 6LoWPAN datagrams to be sent on this 940 interface requiring MESH header encapsulation." 941 ::= { lowpanIfStatsEntry 25 } 943 lowpanIfOutMeshForwds OBJECT-TYPE 944 SYNTAX Counter32 945 MAX-ACCESS read-only 946 STATUS current 947 DESCRIPTION 948 "The number of 6LoWPAN datagrams to be sent on this 949 interface with a MESH header for which suitable 950 forwarding information was available." 951 ::= { lowpanIfStatsEntry 26 } 953 lowpanIfOutMeshTransmits OBJECT-TYPE 954 SYNTAX Counter32 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "The number of 6LoWPAN datagrams to be send on this 959 interface with a MESH header created." 960 ::= { lowpanIfStatsEntry 27 } 962 lowpanIfOutDiscards OBJECT-TYPE 963 SYNTAX Counter32 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "The number of IPv6 packets to be sent over this 968 interface for which no problem was encountered to 969 prevent their transmission to their destination, but 970 were discarded (e.g., for lack of buffer space)." 971 ::= { lowpanIfStatsEntry 28 } 973 lowpanIfOutTransmits OBJECT-TYPE 974 SYNTAX Counter32 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "The total number of 6LoWPAN datagrams to be sent on 979 this interface that this entity supplied to the lower 980 layers for transmission." 981 ::= { lowpanIfStatsEntry 29 } 983 -- conformance definitions 985 lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 } 986 lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 } 988 lowpanCompliance MODULE-COMPLIANCE 989 STATUS current 990 DESCRIPTION 991 "Compliance statement for systems that implement 6LoWPAN." 992 MODULE -- this module 993 MANDATORY-GROUPS { 994 lowpanStatsGroup 995 } 996 GROUP lowpanStatsMeshGroup 997 DESCRIPTION 998 "This group is mandatory for implementations that process 999 or forward 6LoWPAN datagrams with mesh headers." 1000 GROUP lowpanIfStatsGroup 1001 DESCRIPTION 1002 "This group is mandatory for implementations that expose 1003 per interface statistics." 1004 GROUP lowpanIfStatsMeshGroup 1005 DESCRIPTION 1006 "This group is mandatory for implementations that expose 1007 per interface statistics and that process or forward 1008 6LoWPAN datagrams with mesh headers." 1009 ::= { lowpanCompliances 1 } 1011 lowpanStatsGroup OBJECT-GROUP 1012 OBJECTS { 1013 lowpanReasmTimeout, 1014 lowpanInReceives, 1015 lowpanInHdrErrors, 1016 lowpanInMeshReceives, 1017 lowpanInReasmReqds, 1018 lowpanInReasmFails, 1019 lowpanInReasmOKs, 1020 lowpanInCompReqds, 1021 lowpanInCompFails, 1022 lowpanInCompOKs, 1023 lowpanInDiscards, 1024 lowpanInDelivers, 1025 lowpanOutRequests, 1026 lowpanOutCompReqds, 1027 lowpanOutCompFails, 1028 lowpanOutCompOKs, 1029 lowpanOutFragReqds, 1030 lowpanOutFragFails, 1031 lowpanOutFragOKs, 1032 lowpanOutFragCreates, 1033 lowpanOutDiscards, 1034 lowpanOutTransmits 1035 } 1036 STATUS current 1037 DESCRIPTION 1038 "A collection of objects providing information and 1039 statistics about the processing of 6LoWPAN datagrams, 1040 excluding counters covering the processing of datagrams 1041 with a mesh headers." 1042 ::= { lowpanGroups 1 } 1044 lowpanStatsMeshGroup OBJECT-GROUP 1045 OBJECTS { 1046 lowpanInMeshForwds, 1047 lowpanInMeshDelivers, 1048 lowpanOutMeshHopLimitExceeds, 1049 lowpanOutMeshNoRoutes, 1050 lowpanOutMeshRequests, 1051 lowpanOutMeshForwds, 1052 lowpanOutMeshTransmits 1053 } 1054 STATUS current 1055 DESCRIPTION 1056 "A collection of objects providing information and 1057 statistics about the processing of 6LoWPAN datagrams 1058 with a 6LoWPAN mesh header." 1059 ::= { lowpanGroups 2 } 1061 lowpanIfStatsGroup OBJECT-GROUP 1062 OBJECTS { 1063 lowpanIfReasmTimeout, 1064 lowpanIfInReceives, 1065 lowpanIfInHdrErrors, 1066 lowpanIfInMeshReceives, 1067 lowpanIfInReasmReqds, 1068 lowpanIfInReasmFails, 1069 lowpanIfInReasmOKs, 1070 lowpanIfInCompReqds, 1071 lowpanIfInCompFails, 1072 lowpanIfInCompOKs, 1073 lowpanIfInDiscards, 1074 lowpanIfInDelivers, 1075 lowpanIfOutRequests, 1076 lowpanIfOutCompReqds, 1077 lowpanIfOutCompFails, 1078 lowpanIfOutCompOKs, 1079 lowpanIfOutFragReqds, 1080 lowpanIfOutFragFails, 1081 lowpanIfOutFragOKs, 1082 lowpanIfOutFragCreates, 1083 lowpanIfOutDiscards, 1084 lowpanIfOutTransmits 1085 } 1086 STATUS current 1087 DESCRIPTION 1088 "A collection of objects providing per interface 1089 information and statistics about the processing 1090 of 6LoWPAN datagrams, excluding counters covering 1091 the processing of datagrams with a mesh headers." 1092 ::= { lowpanGroups 3 } 1094 lowpanIfStatsMeshGroup OBJECT-GROUP 1095 OBJECTS { 1096 lowpanIfInMeshForwds, 1097 lowpanIfInMeshDelivers, 1098 lowpanIfOutMeshHopLimitExceeds, 1099 lowpanIfOutMeshNoRoutes, 1100 lowpanIfOutMeshRequests, 1101 lowpanIfOutMeshForwds, 1102 lowpanIfOutMeshTransmits 1103 } 1104 STATUS current 1105 DESCRIPTION 1106 "A collection of objects providing per interface 1107 information and statistics about the processing 1108 of 6LoWPAN datagrams with a 6LoWPAN mesh header." 1109 ::= { lowpanGroups 4 } 1111 END 1113 7. Security Considerations 1115 There are no management objects defined in this MIB module that have 1116 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1117 MIB module is implemented correctly, then there is no risk that an 1118 intruder can alter or create any management objects of this MIB 1119 module via direct SNMP SET operations. 1121 Some of the readable objects in this MIB module (i.e., objects with a 1122 MAX-ACCESS other than not-accessible) may be considered sensitive or 1123 vulnerable in some network environments. It is thus important to 1124 control even GET and/or NOTIFY access to these objects and possibly 1125 to even encrypt the values of these objects when sending them over 1126 the network via SNMP. 1128 The read-only counters provide insights into the amount of 6LoWPAN 1129 traffic a node is receiving or transmitting. This might provide 1130 information whether a device is regularly exchanging information with 1131 other devices or whether a device is mostly not participating in any 1132 communication (e.g., the device might be "easier" to take away 1133 unnoticed). The reassembly counters could be used to direct denial 1134 of service attacks on the reassembly mechanism. 1136 SNMP versions prior to SNMPv3 did not include adequate security. 1137 Even if the network itself is secure (for example by using IPsec), 1138 even then, there is no control as to who on the secure network is 1139 allowed to access and GET/SET (read/change/create/delete) the objects 1140 in this MIB module. 1142 It is RECOMMENDED that implementers consider the security features as 1143 provided by the SNMPv3 framework (see [RFC3410], section 8), 1144 including full support for the SNMPv3 cryptographic mechanisms (for 1145 authentication and privacy). 1147 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1148 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1149 enable cryptographic security. It is then a customer/operator 1150 responsibility to ensure that the SNMP entity giving access to an 1151 instance of this MIB module is properly configured to give access to 1152 the objects only to those principals (users) that have legitimate 1153 rights to indeed GET or SET (change/create/delete) them. 1155 8. IANA Considerations 1157 IANA and RFC Ed.: IANA is requested to assign a value for "YYYY" 1158 under the 'mib-2' subtree and to record the assignment in the SMI 1159 Numbers registry. When the assignment has been made, the RFC Editor 1160 is asked to replace "YYYY" (here and in the MIB module) with the 1161 assigned value and to remove this note. 1163 The MIB module in this document uses the following IANA-assigned 1164 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1166 Descriptor OBJECT IDENTIFIER value 1167 ---------- ----------------------- 1168 lowpanMIB { mib-2 YYYY } 1170 9. Acknowledgements 1172 This specification borrows heavily from the IP-MIB defined in 1173 [RFC4293]. 1175 Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, 1176 a Network of Excellence project (ICT-318488) supported by the 1177 European Commission under its Seventh Framework Programme. 1179 10. References 1181 10.1. Normative References 1183 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1184 Requirement Levels", BCP 14, RFC 2119, March 1997. 1186 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1187 Schoenwaelder, Ed., "Structure of Management Information 1188 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1190 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1191 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1192 58, RFC 2579, April 1999. 1194 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1195 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1196 April 1999. 1198 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 1199 "Transmission of IPv6 Packets over IEEE 802.15.4 1200 Networks", RFC 4944, September 2007. 1202 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1203 MIB", RFC 2863, June 2000. 1205 10.2. Informative References 1207 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 1208 August 1980. 1210 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1211 (IPv6) Specification", RFC 2460, December 1998. 1213 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1214 "Introduction and Applicability Statements for Internet- 1215 Standard Management Framework", RFC 3410, December 2002. 1217 [RFC4113] Fenner, B. and J. Flick, "Management Information Base for 1218 the User Datagram Protocol (UDP)", RFC 4113, June 2005. 1220 [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April 1221 2006. 1223 [RFC4293] Routhier, S., "Management Information Base for the 1224 Internet Protocol (IP)", RFC 4293, April 2006. 1226 [RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control 1227 Message Protocol (ICMPv6) for the Internet Protocol 1228 Version 6 (IPv6) Specification", RFC 4443, March 2006. 1230 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 1231 Application Protocol (CoAP)", RFC 7252, June 2014. 1233 [I-D.ietf-6lo-btle] 1234 Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., 1235 Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets 1236 over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-03 1237 (work in progress), September 2014. 1239 [CASE] Case, J. and C. Partridge, "Case Diagrams: A First Step to 1240 Diagrammed Management Information Bases", Computer 1241 Communications Review 19(1), January 1989. 1243 Authors' Addresses 1244 Juergen Schoenwaelder 1245 Jacobs University 1246 Campus Ring 1 1247 Bremen 28759 1248 Germany 1250 EMail: j.schoenwaelder@jacobs-university.de 1252 Anuj Sehgal 1253 Jacobs University 1254 Campus Ring 1 1255 Bremen 28759 1256 Germany 1258 EMail: s.anuj@jacobs-university.de 1260 Tina Tsou 1261 Huawei Technologies (USA) 1262 2330 Central Expressway 1263 Santa Clara CA 95050 1264 USA 1266 EMail: tina.tsou.zouting@huawei.com 1268 Cathy Zhou 1269 Huawei Technologies 1270 Bantian, Longgang District 1271 Shenzhen 518129 1272 P.R. China 1274 EMail: cathyzhou@huawei.com