draft-ietf-6lo-lowpan-mib-03.txt | draft-ietf-6lo-lowpan-mib-04.txt | |||
---|---|---|---|---|
Internet Engineering Task Force J. Schoenwaelder | Internet Engineering Task Force J. Schoenwaelder | |||
Internet-Draft A. Sehgal | Internet-Draft A. Sehgal | |||
Intended status: Standards Track Jacobs University | Intended status: Standards Track Jacobs University | |||
Expires: February 8, 2015 T. Tsou | Expires: March 9, 2015 T. Tsou | |||
Huawei Technologies (USA) | Huawei Technologies (USA) | |||
C. Zhou | C. Zhou | |||
Huawei Technologies | Huawei Technologies | |||
August 7, 2014 | September 5, 2014 | |||
Definition of Managed Objects for IPv6 over Low-Power Wireless Personal | Definition of Managed Objects for IPv6 over Low-Power Wireless Personal | |||
Area Networks (6LoWPANs) | Area Networks (6LoWPANs) | |||
draft-ietf-6lo-lowpan-mib-03 | draft-ietf-6lo-lowpan-mib-04 | |||
Abstract | Abstract | |||
This memo defines a portion of the Management Information Base (MIB) | This document defines a portion of the Management Information Base | |||
for use with network management protocols in the Internet community. | (MIB) for use with network management protocols in the Internet | |||
In particular, it defines objects for managing IPv6 over Low-Power | community. In particular, it defines objects for managing IPv6 over | |||
Wireless Personal Area Networks (6LoWPANs). | Low-Power Wireless Personal Area Networks (6LoWPANs). | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on February 8, 2015. | This Internet-Draft will expire on March 9, 2015. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 2, line 18 | skipping to change at page 2, line 18 | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
2. The Internet-Standard Management Framework . . . . . . . . . 2 | 2. The Internet-Standard Management Framework . . . . . . . . . 2 | |||
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 | 5. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 | |||
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 | 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 | |||
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 | 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 | |||
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 | 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 | |||
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 | 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 | |||
10.1. Normative References . . . . . . . . . . . . . . . . . . 25 | 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 | |||
10.2. Informative References . . . . . . . . . . . . . . . . . 25 | 10.2. Informative References . . . . . . . . . . . . . . . . . 26 | |||
1. Introduction | 1. Introduction | |||
This memo defines a portion of the Management Information Base (MIB) | This document defines a portion of the Management Information Base | |||
for use with network management protocols. In particular it defines | (MIB) for use with network management protocols. In particular it | |||
objects for managing IPv6 over Low-Power Wireless Personal Area | defines objects for managing IPv6 over Low-Power Wireless Personal | |||
Networks (6LoWPANs) [RFC4944]. | Area Networks (6LoWPANs) [RFC4944]. | |||
While a MIB module provides a direct binding for accessing data via | While a MIB module provides a direct binding for accessing data via | |||
the Simple Network Management Protocol (SNMP) [RFC3410], supporting | the Simple Network Management Protocol (SNMP) [RFC3410], supporting | |||
SNMP may not always be affordable on constrained devices. Other | SNMP may not always be affordable on constrained devices. Other | |||
protocols to access data modeled in MIB modules are possible and | protocols to access data modeled in MIB modules are possible and | |||
proposals have been made recently to provide bindings to the | proposals have been made recently to provide bindings to the | |||
Constrained Application Protocol (CoAP) [RFC7252]. | Constrained Application Protocol (CoAP) [RFC7252]. | |||
2. The Internet-Standard Management Framework | 2. The Internet-Standard Management Framework | |||
For a detailed overview of the documents that describe the current | For a detailed overview of the documents that describe the current | |||
Internet-Standard Management Framework, please refer to section 7 of | Internet-Standard Management Framework, please refer to section 7 of | |||
RFC 3410 [RFC3410]. | RFC 3410 [RFC3410]. | |||
Managed objects are accessed via a virtual information store, termed | Managed objects are accessed via a virtual information store, termed | |||
the Management Information Base or MIB. MIB objects are generally | the Management Information Base or MIB. MIB objects are generally | |||
accessed through the Simple Network Management Protocol (SNMP). | accessed through the Simple Network Management Protocol (SNMP). | |||
Objects in the MIB are defined using the mechanisms defined in the | Objects in the MIB are defined using the mechanisms defined in the | |||
Structure of Management Information (SMI). This memo specifies a MIB | Structure of Management Information (SMI). This document specifies a | |||
module that is compliant to the SMIv2, which is described in STD 58, | MIB module that is compliant to the SMIv2, which is described in STD | |||
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 | 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC | |||
[RFC2580]. | 2580 [RFC2580]. | |||
3. Conventions | 3. Conventions | |||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
"OPTIONAL" in this document are to be interpreted as described in RFC | "OPTIONAL" in this document are to be interpreted as described in RFC | |||
2119 [RFC2119]. | 2119 [RFC2119]. | |||
4. Overview | 4. Overview | |||
The left part of Figure 1 provides an overview of the protocols | The left part of Figure 1 provides an overview of the IETF protocols | |||
typically used on constrained devices. The right part lists the MIB | designed for constrained devices. The right part lists the MIB | |||
modules providing monitoring and troubleshooting support ([RFC4113], | modules providing monitoring and troubleshooting support ([RFC4113], | |||
[RFC4292], [RFC4293], [RFC2863]). The LOWPAN-MIB defined in this | [RFC4292], [RFC4293], [RFC2863]). The LOWPAN-MIB defined in this | |||
document fills a hole by providing monitoring and troubleshooting | document fills a hole by providing monitoring and troubleshooting | |||
support for the 6LoWPAN layer. | support for the 6LoWPAN layer. | |||
Protocol Layer MIB Modules | Protocol Layer MIB Modules | |||
+---------------+ | +--------------------+ | |||
| CoAP | | | CoAP [RFC7252] | | |||
+---------------+ +--------------------------+ | +--------------------+ +--------------------------+ | |||
| UDP | | UDP-MIB [RFC4113] | | | UDP [RFC0768] | | UDP-MIB [RFC4113] | | |||
+---------------+ +--------------------------+ | +--------------------+ +--------------------------+ | |||
| IPv6 | | IP-MIB [RFC4293] | | | IPv6 [RFC2460] | | IP-MIB [RFC4293] | | |||
| ICMPv6 | | IP-FORWARD-MIB [RFC4292] | | | ICMPv6 [RFC4443] | | IP-FORWARD-MIB [RFC4292] | | |||
+---------------+ +--------------------------+ | +--------------------+ +--------------------------+ | |||
| 6LoWPAN | | LOWPAN-MIB [RFCXXXX] | | | 6LoWPAN [RFC4944] | | LOWPAN-MIB [RFCXXXX] | | |||
+---------------+ +--------------------------+ | +--------------------+ +--------------------------+ | |||
| IF-MIB [RFC2863] | | | IF-MIB [RFC2863] | | |||
+---------------+ +--------------------------+ | +--------------------+ +--------------------------+ | |||
| IEEE 802.15.4 | | | IEEE 802.15.4, ... | | |||
+---------------+ | +--------------------+ | |||
/* RFC Ed.: replace XXXX above with RFC number | /* RFC Ed.: replace XXXX above with RFC number | |||
and remove this note */ | and remove this note */ | |||
Figure 1: Protocol Layers and MIB Modules | Figure 1: Protocol Layers and MIB Modules | |||
The LOWPAN-MIB module is primarily a collection of counters that | The LOWPAN-MIB module is primarily a collection of counters that | |||
reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer. | reflect how 6LoWPAN datagrams are processed by the 6LoWPAN layer. | |||
The objects are defined twice, once to report the global statistics | The objects are defined twice, once to report the global statistics | |||
as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN | as seen by the 6LoWPAN layer and once to report per interface 6LoWPAN | |||
skipping to change at page 5, line 42 | skipping to change at page 5, line 42 | |||
dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a | dispatch byte as defined in [RFC4944] (e.g., IEEE 802.15.4), a | |||
6LoWPAN datagram is a datagram with a dispatch byte matching the bit | 6LoWPAN datagram is a datagram with a dispatch byte matching the bit | |||
patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch | patterns 01xxxxxx, 10xxxxxx, or 11xxxxxx. Datagrams with a dispatch | |||
byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) | byte matching the bit pattern 00xxxxxx (NALP - not a LoWPAN frame) | |||
are not considered to be 6LoWPAN datagram by this specification. | are not considered to be 6LoWPAN datagram by this specification. | |||
Other radio technologies may use different mechanisms to identify | Other radio technologies may use different mechanisms to identify | |||
6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link | 6LoWPAN datagrams (e.g., the BLUETOOTH Low Energy Logical Link | |||
Control and Adaptation Protocol uses Channel Identifiers | Control and Adaptation Protocol uses Channel Identifiers | |||
[I-D.ietf-6lo-btle]). | [I-D.ietf-6lo-btle]). | |||
Figure 2 illustrates the conceptual relationships between the | The Case Diagram [CASE] in Figure 2 illustrates the conceptual | |||
counters. Implementations may choose to implement the processing of | relationships between the counters. Implementations may choose to | |||
6LoWPAN datagrams in a different order. | implement the processing of 6LoWPAN datagrams in a different order. | |||
The generic InDiscards and OutDiscards counters can be incremented | The generic InDiscards and OutDiscards counters can be incremented | |||
anytime when 6LoWPAN datagrams are discarded due to reasons not | anytime when 6LoWPAN datagrams are discarded due to reasons not | |||
covered by the other more specific counters. For example, an | covered by the other more specific counters. For example, an | |||
implementation discarding 6LoWPAN datagrams while all buffers are | implementation discarding 6LoWPAN datagrams while all buffers are | |||
used for ongoing packet reassemblies will increment the relevant | used for ongoing packet reassemblies will increment the relevant | |||
InDiscards counters for each discarded 6LoWPAN datagram. | InDiscards counters for each discarded 6LoWPAN datagram. | |||
IPv6 layer | IPv6 layer | |||
^ v | ^ v | |||
skipping to change at page 7, line 14 | skipping to change at page 7, line 14 | |||
The mesh header processing related counters do not have an explicit | The mesh header processing related counters do not have an explicit | |||
discard counter. Implementations that do not support mesh forwarding | discard counter. Implementations that do not support mesh forwarding | |||
MUST count the number of received 6LoWPAN datagrams with a MESH | MUST count the number of received 6LoWPAN datagrams with a MESH | |||
header (lowpanInMeshReceives) but they MUST NOT increment the | header (lowpanInMeshReceives) but they MUST NOT increment the | |||
lowpanInMeshReceives and lowpanInMeshDelivers counters if these | lowpanInMeshReceives and lowpanInMeshDelivers counters if these | |||
6LoWPAN datagrams are dropped. | 6LoWPAN datagrams are dropped. | |||
5. Relationship to Other MIB Modules | 5. Relationship to Other MIB Modules | |||
The MIB module IMPORTS definitions from SNMPv2-SMI [RFC2578], | The MIB module imports definitions from SNMPv2-SMI [RFC2578], | |||
SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863]. | SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863]. | |||
6. Definitions | 6. Definitions | |||
LOWPAN-MIB DEFINITIONS ::= BEGIN | LOWPAN-MIB DEFINITIONS ::= BEGIN | |||
IMPORTS | IMPORTS | |||
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 | MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, mib-2 | |||
FROM SNMPv2-SMI -- RFC 2578 | FROM SNMPv2-SMI -- RFC 2578 | |||
OBJECT-GROUP, MODULE-COMPLIANCE | OBJECT-GROUP, MODULE-COMPLIANCE | |||
FROM SNMPv2-CONF -- RFC 2580 | FROM SNMPv2-CONF -- RFC 2580 | |||
ifIndex FROM IF-MIB; -- RFC 2863 | ifIndex FROM IF-MIB; -- RFC 2863 | |||
lowpanMIB MODULE-IDENTITY | lowpanMIB MODULE-IDENTITY | |||
LAST-UPDATED "201408070000Z" | LAST-UPDATED "201409050000Z" | |||
ORGANIZATION | ORGANIZATION | |||
"Jacobs University Bremen" | "IETF IPv6 over Networks of Resource-constrained Nodes | |||
Working Group" | ||||
CONTACT-INFO | CONTACT-INFO | |||
"Juergen Schoenwaelder | "WG Email: 6lo@ietf.org | |||
WG Web: http://tools.ietf.org/wg/6lo/ | ||||
Juergen Schoenwaelder | ||||
Jacobs University Bremen | Jacobs University Bremen | |||
Email: j.schoenwaelder@jacobs-university.de | Email: j.schoenwaelder@jacobs-university.de | |||
Anuj Sehgal | Anuj Sehgal | |||
Jacobs University Bremen | Jacobs University Bremen | |||
Email: s.anuj@jacobs-university.de | Email: s.anuj@jacobs-university.de | |||
Tina Tsou | Tina Tsou | |||
Huawei Technologies | Huawei Technologies | |||
Email: tina.tsou.zouting@huawei.com | Email: tina.tsou.zouting@huawei.com | |||
skipping to change at page 8, line 15 | skipping to change at page 8, line 20 | |||
Copyright (c) 2014 IETF Trust and the persons identified as | Copyright (c) 2014 IETF Trust and the persons identified as | |||
authors of the code. All rights reserved. | authors of the code. All rights reserved. | |||
Redistribution and use in source and binary forms, with or | Redistribution and use in source and binary forms, with or | |||
without modification, is permitted pursuant to, and subject | without modification, is permitted pursuant to, and subject | |||
to the license terms contained in, the Simplified BSD | to the license terms contained in, the Simplified BSD | |||
License set forth in Section 4.c of the IETF Trust's | License set forth in Section 4.c of the IETF Trust's | |||
Legal Provisions Relating to IETF Documents | Legal Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info)." | (http://trustee.ietf.org/license-info)." | |||
REVISION "201408070000Z" | REVISION "201409050000Z" | |||
DESCRIPTION | DESCRIPTION | |||
"Initial version, published as RFC XXXX." | "Initial version, published as RFC XXXX." | |||
-- RFC Ed.: replace XXXX with RFC number and remove this note | -- RFC Ed.: replace XXXX with RFC number and remove this note | |||
::= { mib-2 XXXX } | ::= { mib-2 YYYY } | |||
-- RFC Ed.: replace YYYY with IANA assigned number | ||||
-- object definitions | -- object definitions | |||
lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } | lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 } | |||
lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } | lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 } | |||
lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } | lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 } | |||
lowpanStats OBJECT IDENTIFIER ::= { lowpanObjects 1 } | lowpanStats OBJECT IDENTIFIER ::= { lowpanObjects 1 } | |||
lowpanReasmTimeout OBJECT-TYPE | lowpanReasmTimeout OBJECT-TYPE | |||
skipping to change at page 24, line 7 | skipping to change at page 24, line 9 | |||
DESCRIPTION | DESCRIPTION | |||
"A collection of objects providing per interface | "A collection of objects providing per interface | |||
information and statistics about the processing | information and statistics about the processing | |||
of 6LoWPAN datagrams with a 6LoWPAN mesh header." | of 6LoWPAN datagrams with a 6LoWPAN mesh header." | |||
::= { lowpanGroups 4 } | ::= { lowpanGroups 4 } | |||
END | END | |||
7. Security Considerations | 7. Security Considerations | |||
There are no management objects defined in this MIB module that have | ||||
a MAX-ACCESS clause of read-write and/or read-create. So, if this | ||||
MIB module is implemented correctly, then there is no risk that an | ||||
intruder can alter or create any management objects of this MIB | ||||
module via direct SNMP SET operations. | ||||
Some of the readable objects in this MIB module (i.e., objects with a | Some of the readable objects in this MIB module (i.e., objects with a | |||
MAX-ACCESS other than not-accessible) may be considered sensitive or | MAX-ACCESS other than not-accessible) may be considered sensitive or | |||
vulnerable in some network environments. It is thus important to | vulnerable in some network environments. It is thus important to | |||
control even GET and/or NOTIFY access to these objects and possibly | control even GET and/or NOTIFY access to these objects and possibly | |||
to even encrypt the values of these objects when sending them over | to even encrypt the values of these objects when sending them over | |||
the network via SNMP. These are the tables and objects and their | the network via SNMP. | |||
sensitivity/vulnerability: | ||||
The read-only counters provide insights into the amount of 6LoWPAN | The read-only counters provide insights into the amount of 6LoWPAN | |||
traffic a node is receiving or transmitting. This might provide | traffic a node is receiving or transmitting. This might provide | |||
information whether a device is regularly exchanging information with | information whether a device is regularly exchanging information with | |||
other devices or whether a device is mostly not participating in any | other devices or whether a device is mostly not participating in any | |||
communication (e.g., the device might be "easier" to take away | communication (e.g., the device might be "easier" to take away | |||
unnoticed). The reassembly counters could be used to direct denial | unnoticed). The reassembly counters could be used to direct denial | |||
of service attacks on the reassembly mechanism. | of service attacks on the reassembly mechanism. | |||
SNMP versions prior to SNMPv3 did not include adequate security. | SNMP versions prior to SNMPv3 did not include adequate security. | |||
skipping to change at page 24, line 44 | skipping to change at page 25, line 7 | |||
Further, deployment of SNMP versions prior to SNMPv3 is NOT | Further, deployment of SNMP versions prior to SNMPv3 is NOT | |||
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | |||
enable cryptographic security. It is then a customer/operator | enable cryptographic security. It is then a customer/operator | |||
responsibility to ensure that the SNMP entity giving access to an | responsibility to ensure that the SNMP entity giving access to an | |||
instance of this MIB module is properly configured to give access to | instance of this MIB module is properly configured to give access to | |||
the objects only to those principals (users) that have legitimate | the objects only to those principals (users) that have legitimate | |||
rights to indeed GET or SET (change/create/delete) them. | rights to indeed GET or SET (change/create/delete) them. | |||
8. IANA Considerations | 8. IANA Considerations | |||
IANA is requested to assign a value for "XXXX" under the 'mib-2' | IANA and RFC Ed.: IANA is requested to assign a value for "YYYY" | |||
subtree and to record the assignment in the SMI Numbers registry. | under the 'mib-2' subtree and to record the assignment in the SMI | |||
When the assignment has been made, the RFC Editor is asked to replace | Numbers registry. When the assignment has been made, the RFC Editor | |||
"XXXX" (here and in the MIB module) with the assigned value and to | is asked to replace "YYYY" (here and in the MIB module) with the | |||
remove this note. | assigned value and to remove this note. | |||
The MIB module in this document uses the following IANA-assigned | ||||
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: | ||||
Descriptor OBJECT IDENTIFIER value | ||||
---------- ----------------------- | ||||
lowpanMIB { mib-2 YYYY } | ||||
9. Acknowledgements | 9. Acknowledgements | |||
This specification borrows heavily from the IP-MIB defined in | This specification borrows heavily from the IP-MIB defined in | |||
[RFC4293]. | [RFC4293]. | |||
Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, | Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, | |||
a Network of Excellence project (ICT-318488) supported by the | a Network of Excellence project (ICT-318488) supported by the | |||
European Commission under its Seventh Framework Programme. | European Commission under its Seventh Framework Programme. | |||
skipping to change at page 25, line 42 | skipping to change at page 26, line 10 | |||
[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, | [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, | |||
"Transmission of IPv6 Packets over IEEE 802.15.4 | "Transmission of IPv6 Packets over IEEE 802.15.4 | |||
Networks", RFC 4944, September 2007. | Networks", RFC 4944, September 2007. | |||
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group | [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group | |||
MIB", RFC 2863, June 2000. | MIB", RFC 2863, June 2000. | |||
10.2. Informative References | 10.2. Informative References | |||
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, | ||||
August 1980. | ||||
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | ||||
(IPv6) Specification", RFC 2460, December 1998. | ||||
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, | [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, | |||
"Introduction and Applicability Statements for Internet- | "Introduction and Applicability Statements for Internet- | |||
Standard Management Framework", RFC 3410, December 2002. | Standard Management Framework", RFC 3410, December 2002. | |||
[RFC4113] Fenner, B. and J. Flick, "Management Information Base for | [RFC4113] Fenner, B. and J. Flick, "Management Information Base for | |||
the User Datagram Protocol (UDP)", RFC 4113, June 2005. | the User Datagram Protocol (UDP)", RFC 4113, June 2005. | |||
[RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April | [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April | |||
2006. | 2006. | |||
[RFC4293] Routhier, S., "Management Information Base for the | [RFC4293] Routhier, S., "Management Information Base for the | |||
Internet Protocol (IP)", RFC 4293, April 2006. | Internet Protocol (IP)", RFC 4293, April 2006. | |||
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control | ||||
Message Protocol (ICMPv6) for the Internet Protocol | ||||
Version 6 (IPv6) Specification", RFC 4443, March 2006. | ||||
[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained | [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained | |||
Application Protocol (CoAP)", RFC 7252, June 2014. | Application Protocol (CoAP)", RFC 7252, June 2014. | |||
[I-D.ietf-6lo-btle] | [I-D.ietf-6lo-btle] | |||
Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., | Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., | |||
Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets | Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets | |||
over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-02 | over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-03 | |||
(work in progress), June 2014. | (work in progress), September 2014. | |||
Authors' Addresses | [CASE] Case, J. and C. Partridge, "Case Diagrams: A First Step to | |||
Diagrammed Management Information Bases", Computer | ||||
Communications Review 19(1), January 1989. | ||||
Authors' Addresses | ||||
Juergen Schoenwaelder | Juergen Schoenwaelder | |||
Jacobs University | Jacobs University | |||
Campus Ring 1 | Campus Ring 1 | |||
Bremen 28759 | Bremen 28759 | |||
Germany | Germany | |||
EMail: j.schoenwaelder@jacobs-university.de | EMail: j.schoenwaelder@jacobs-university.de | |||
Anuj Sehgal | Anuj Sehgal | |||
Jacobs University | Jacobs University | |||
End of changes. 26 change blocks. | ||||
54 lines changed or deleted | 84 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |