Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)
draft-ietf-6lo-lowpan-mib-03
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7388.
|
|
---|---|---|---|
Authors | Jürgen Schönwälder , Anuj Sehgal , Tina Tsou (Ting ZOU) , Cathy Zhou | ||
Last updated | 2014-09-04 (Latest revision 2014-08-07) | ||
Replaces | draft-schoenw-6lo-lowpan-mib | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
GENART Last Call review
by Martin Thomson
Ready w/nits
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Ulrich Herberg | ||
Shepherd write-up | Show Last changed 2014-08-04 | ||
IESG | IESG state | Became RFC 7388 (Proposed Standard) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Brian Haberman | ||
Send notices to | 6lo-chairs@tools.ietf.org, draft-ietf-6lo-lowpan-mib@tools.ietf.org | ||
IANA | IANA review state | IANA OK - Actions Needed |
draft-ietf-6lo-lowpan-mib-03
lowpanIfOutMeshNoRoutes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 6LoWPAN datagrams to be sent on this interface with a MESH header that were dropped because there was no forwarding information available." ::= { lowpanIfStatsEntry 24 } lowpanIfOutMeshRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 6LoWPAN datagrams to be sent on this interface requiring MESH header encapsulation." ::= { lowpanIfStatsEntry 25 } lowpanIfOutMeshForwds OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 6LoWPAN datagrams to be sent on this interface with a MESH header for which suitable forwarding information was available." ::= { lowpanIfStatsEntry 26 } lowpanIfOutMeshTransmits OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 6LoWPAN datagrams to be send on this interface with a MESH header created." ::= { lowpanIfStatsEntry 27 } lowpanIfOutDiscards OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of IPv6 packets to be sent over this interface for which no problem was encountered to prevent their transmission to their destination, but were discarded (e.g., for lack of buffer space)." ::= { lowpanIfStatsEntry 28 } Schoenwaelder, et al. Expires February 8, 2015 [Page 20] Internet-Draft LOWPAN-MIB August 2014 lowpanIfOutTransmits OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of 6LoWPAN datagrams to be sent on this interface that this entity supplied to the lower layers for transmission." ::= { lowpanIfStatsEntry 29 } -- conformance definitions lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 } lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 } lowpanCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for systems that implement 6LoWPAN." MODULE -- this module MANDATORY-GROUPS { lowpanStatsGroup } GROUP lowpanStatsMeshGroup DESCRIPTION "This group is mandatory for implementations that process or forward 6LoWPAN datagrams with mesh headers." GROUP lowpanIfStatsGroup DESCRIPTION "This group is mandatory for implementations that expose per interface statistics." GROUP lowpanIfStatsMeshGroup DESCRIPTION "This group is mandatory for implementations that expose per interface statistics and that process or forward 6LoWPAN datagrams with mesh headers." ::= { lowpanCompliances 1 } lowpanStatsGroup OBJECT-GROUP OBJECTS { lowpanReasmTimeout, lowpanInReceives, lowpanInHdrErrors, lowpanInMeshReceives, lowpanInReasmReqds, lowpanInReasmFails, lowpanInReasmOKs, lowpanInCompReqds, Schoenwaelder, et al. Expires February 8, 2015 [Page 21] Internet-Draft LOWPAN-MIB August 2014 lowpanInCompFails, lowpanInCompOKs, lowpanInDiscards, lowpanInDelivers, lowpanOutRequests, lowpanOutCompReqds, lowpanOutCompFails, lowpanOutCompOKs, lowpanOutFragReqds, lowpanOutFragFails, lowpanOutFragOKs, lowpanOutFragCreates, lowpanOutDiscards, lowpanOutTransmits } STATUS current DESCRIPTION "A collection of objects providing information and statistics about the processing of 6LoWPAN datagrams, excluding counters covering the processing of datagrams with a mesh headers." ::= { lowpanGroups 1 } lowpanStatsMeshGroup OBJECT-GROUP OBJECTS { lowpanInMeshForwds, lowpanInMeshDelivers, lowpanOutMeshHopLimitExceeds, lowpanOutMeshNoRoutes, lowpanOutMeshRequests, lowpanOutMeshForwds, lowpanOutMeshTransmits } STATUS current DESCRIPTION "A collection of objects providing information and statistics about the processing of 6LoWPAN datagrams with a 6LoWPAN mesh header." ::= { lowpanGroups 2 } lowpanIfStatsGroup OBJECT-GROUP OBJECTS { lowpanIfReasmTimeout, lowpanIfInReceives, lowpanIfInHdrErrors, lowpanIfInMeshReceives, lowpanIfInReasmReqds, lowpanIfInReasmFails, Schoenwaelder, et al. Expires February 8, 2015 [Page 22] Internet-Draft LOWPAN-MIB August 2014 lowpanIfInReasmOKs, lowpanIfInCompReqds, lowpanIfInCompFails, lowpanIfInCompOKs, lowpanIfInDiscards, lowpanIfInDelivers, lowpanIfOutRequests, lowpanIfOutCompReqds, lowpanIfOutCompFails, lowpanIfOutCompOKs, lowpanIfOutFragReqds, lowpanIfOutFragFails, lowpanIfOutFragOKs, lowpanIfOutFragCreates, lowpanIfOutDiscards, lowpanIfOutTransmits } STATUS current DESCRIPTION "A collection of objects providing per interface information and statistics about the processing of 6LoWPAN datagrams, excluding counters covering the processing of datagrams with a mesh headers." ::= { lowpanGroups 3 } lowpanIfStatsMeshGroup OBJECT-GROUP OBJECTS { lowpanIfInMeshForwds, lowpanIfInMeshDelivers, lowpanIfOutMeshHopLimitExceeds, lowpanIfOutMeshNoRoutes, lowpanIfOutMeshRequests, lowpanIfOutMeshForwds, lowpanIfOutMeshTransmits } STATUS current DESCRIPTION "A collection of objects providing per interface information and statistics about the processing of 6LoWPAN datagrams with a 6LoWPAN mesh header." ::= { lowpanGroups 4 } END Schoenwaelder, et al. Expires February 8, 2015 [Page 23] Internet-Draft LOWPAN-MIB August 2014 7. Security Considerations Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: The read-only counters provide insights into the amount of 6LoWPAN traffic a node is receiving or transmitting. This might provide information whether a device is regularly exchanging information with other devices or whether a device is mostly not participating in any communication (e.g., the device might be "easier" to take away unnoticed). The reassembly counters could be used to direct denial of service attacks on the reassembly mechanism. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 8. IANA Considerations IANA is requested to assign a value for "XXXX" under the 'mib-2' subtree and to record the assignment in the SMI Numbers registry. When the assignment has been made, the RFC Editor is asked to replace "XXXX" (here and in the MIB module) with the assigned value and to remove this note. Schoenwaelder, et al. Expires February 8, 2015 [Page 24] Internet-Draft LOWPAN-MIB August 2014 9. Acknowledgements This specification borrows heavily from the IP-MIB defined in [RFC4293]. Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, a Network of Excellence project (ICT-318488) supported by the European Commission under its Seventh Framework Programme. 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks", RFC 4944, September 2007. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. 10.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC4113] Fenner, B. and J. Flick, "Management Information Base for the User Datagram Protocol (UDP)", RFC 4113, June 2005. [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, April 2006. Schoenwaelder, et al. Expires February 8, 2015 [Page 25] Internet-Draft LOWPAN-MIB August 2014 [RFC4293] Routhier, S., "Management Information Base for the Internet Protocol (IP)", RFC 4293, April 2006. [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained Application Protocol (CoAP)", RFC 7252, June 2014. [I-D.ietf-6lo-btle] Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., Shelby, Z., and C. Gomez, "Transmission of IPv6 Packets over BLUETOOTH(R) Low Energy", draft-ietf-6lo-btle-02 (work in progress), June 2014. Authors' Addresses Juergen Schoenwaelder Jacobs University Campus Ring 1 Bremen 28759 Germany EMail: j.schoenwaelder@jacobs-university.de Anuj Sehgal Jacobs University Campus Ring 1 Bremen 28759 Germany EMail: s.anuj@jacobs-university.de Tina Tsou Huawei Technologies (USA) 2330 Central Expressway Santa Clara CA 95050 USA EMail: tina.tsou.zouting@huawei.com Cathy Zhou Huawei Technologies Bantian, Longgang District Shenzhen 518129 P.R. China EMail: cathyzhou@huawei.com Schoenwaelder, et al. Expires February 8, 2015 [Page 26]