ol for constrained IoT node communica- tions, while in general in the M2M domain HTTP seems to be prevalent (e.g., Open Mobile Alliance (OMA) Converged Personal Network Service (CPNS) uses HTTP). IPv6 over IEEE 802.15.4: The RFC 4944 specifies how IPv6 packets can be transported over IEEE 802.15.4 networks [76]. IPv6 over Bluetooth Low Energy: An Internet-Draft (work in progress) specifies how IPv6 packets can be transported over Bluetooth Low-Energy networks [77]. Compression of IPv6 on IPv6 over Low power Wireless Personal Area Networks (6LoWPANs): RFC 6282 defines how IPv6 packets can be compressed over 6LoW- PANs, with a focus on IEEE 802.15.4 networks, but with a solution that also works with Bluetooth Low-Energy networks [78]. IPv6 Neighbor Discovery Optimizations: RFC 6775 specifies optimizations for Neighbor Discovery Protocol on 6LoWPANs [79]. Routing over low power and lossy networks: A family of RFCs describes a Routing Protocol for Low-power and Lossy Networks (RPL) protocol, the core of which is RFC 6550 [80]. The RPL describes how IPv6 packets can be routed in 6LoWPANs, and the metrics and algorithms needed for the work. See also Section 3.10.4. Mobile Ad hoc NETworking (MANET): The MANET has been a long-term activity in the IETF. The first RFC 2501 from this space was published back in 1999 [81]. RFC Future of IPv6 in 3GPP Networks 2501 recognized the need for low-power operations, but has focus in particular on high mobility of both nodes in the network and the network itself. The MANET includes a set of protocols, currently 12 RFCs, for setting up static and dynamic mesh networks and related routing systems using different routing techniques. Implementation guidance: A recent work has been ongoing to describe implementation guidelines in an attempt to help software developers make as light-weight implemen- tations of the IP suite as possible [82]. OMA Device Management Work The OMA http://www.openmobilealliance.org specifications are already very widely used for device management (see Section 4.7