6LoWPAN: High-impact Technology - What You Need to Know: Definitions, Adoptions, Impact, Benefits, Maturity, Vendors

Kevin Roebuck

Description

6LoWPAN is an acronym of IPv6 over Low power Wireless Personal Area Networks. 6lowpan is the name of a working group in the internet area of the IETF.

The 6LoWPAN concept originated from the idea that ""the Internet Protocol could and should be applied even to the smallest devices,"" and that low-power devices with limited processing capabilities should be able to participate in the Internet of Things.

The 6lowpan group has defined encapsulation and header compression mechanisms that allow IPv6 packets to be sent to and received from over IEEE 802.15.4 based networks. IPv4 and IPv6 are the work horses for data delivery for local-area networks, metropolitan area networks, and wide-area networks such as the Internet. Likewise, IEEE 802.15.4 devices provide sensing communication-ability in the wireless domain. The inherent natures of the two networks though, is different.

This book is your ultimate resource for 6LoWPAN. Here you will find the most up-to-date information, analysis, background and everything you need to know.

In easy to read chapters, with extensive references and links to get you to know all there is to know about 6LoWPAN right away, covering: 6LoWPAN, 6bone, 6over4, Ad-Hoc Configuration Protocol, AICCU, Anycast, China Next Generation Internet, Comparison of IPv6 application support, Comparison of IPv6 support by major transit providers, Comparison of IPv6 support in operating systems, Comparison of IPv6 support in routers, Cryptographically Generated Address, DHCPv6, DirectAccess, DoD IPv6 Product Certification, Hurricane Electric, ICMPv6, IPv4 address exhaustion, IPv6, IPv6 address, IPv6 brokenness and DNS whitelisting, IPv6 deployment, IPv6 packet, IPv6 subnetting reference, IPv6 transition mechanisms, ISATAP, NAT64, Neighbor Discovery Protocol, Next Generation Internet Program, OCCAID, Radvd, SATSIX, Secure Neighbor Discovery Protocol, Site Multihoming by IPv6 Intermediation, Solicited-node multicast address, Transformational Satellite Communications System, Tunnel broker, List of IPv6 tunnel brokers, Tunnel Setup Protocol, Unique local address, Where-Are-You, World IPv6 Day, HiperLAN, HiperMAN, IEEE 1900.4, IEEE 802.15, IEEE 802.15.4, IEEE 802.15.4a, IEEE 802.16, IEEE 802.20, IEEE 802.22, IEEE P1900, ONE-NET, WLAN Authentication and Privacy Infrastructure

This book explains in-depth the real drivers and workings of 6LoWPAN. It reduces the risk of your technology, time and resources investment decisions by enabling you to compare your understanding of 6LoWPAN with the objectivity of experienced professionals.

Sujets

• Computers
• Informatique

Informations

• Publié par: Emereo Publishing
• Date de parution: 24 octobre 2012
• Nombre de lectures: 0
• EAN13: 9781743045985
• Langue: English
• Poids de l'ouvrage: 4 Mo

Extrait

Topic relevant selected content from the highest rated entries, typeset, printed and shipped.

Combine the advantages of up-to-date and in-depth knowledge with the convenience of printed books.

A portion of the proceeds of each book will be donated to the Wikimedia Foundation to support their mission: to empower and engage people around the world to collect and develop educational content under a free license or in the public domain, and to disseminate it effectively and globally.

The content within this book was generated collaboratively by volunteers. Please be advised that nothing found here has necessarily been reviewed by people with the expertise required to provide you with complete, accurate or reliable information. Some information in this book maybe misleading or simply wrong. The publisher does not guarantee the validity of the information found here. If you need speciîc advice (for example, medical, legal, înancial, or risk management) please seek a professional who is licensed or knowledgeable in that area.

Sources, licenses and contributors of the articles and images are listed in the section entitled “References”. Parts of the books may be licensed under the GNU Free Documentation License. A copy of this license is included in the section entitled “GNU Free Documentation License”

All used third-party trademarks belong to their respective owners.

Contents

Articles 6LoWPAN 6bone 6over4 Ad-Hoc Configuration Protocol AICCU Anycast China Next Generation Internet Comparison of IPv6 application support Comparison of IPv6 support by major transit providers Comparison of IPv6 support in operating systems Comparison of IPv6 support in routers Cryptographically Generated Address DHCPv6 DirectAccess

DoD IPv6 Product Certification Hurricane Electric ICMPv6 IPv4 address exhaustion IPv6 IPv6 address IPv6 brokenness and DNS whitelisting IPv6 deployment IPv6 packet IPv6 subnetting reference IPv6 transition mechanisms ISATAP NAT64 Neighbor Discovery Protocol Next Generation Internet Program OCCAID radvd SATSIX Secure Neighbor Discovery Protocol Site Multihoming by IPv6 Intermediation

1 3 4 5 6 8 12 13 18 20 22 24 24 26 28 30 32 34 43 56 68 70 78 85 86 90 91 92 93 94 95 96 100 101

Solicited-node multicast address Transformational Satellite Communications System Tunnel broker List of IPv6 tunnel brokers Tunnel Setup Protocol Unique local address Where-Are-You World IPv6 Day HiperLAN HiperMAN IEEE 1900.4 IEEE 802.15 IEEE 802.15.4 IEEE 802.15.4a IEEE 802.16 IEEE 802.20 IEEE 802.22 IEEE P1900 ONE-NET WLAN Authentication and Privacy Infrastructure

References Article Sources and Contributors Image Sources, Licenses and Contributors

Article Licenses License

102 103 106 107 109 110 112 112 113 114 115 116 119 124 125 129 131 134 135 138

141 144

145

6LoWPAN

6LoWPAN

6lowpanis an acronym ofIPv6 over Low power Wireless Personal Area Networks. 6lowpan is the name of a working group in the internet area of the IETF. The 6lowpan group has defined encapsulation and header compression mechanisms that allow IPv6 packets to be sent to and received from over IEEE 802.15.4 based networks. IPv4 and IPv6 are the work horses for data delivery for local-area networks, metropolitan area networks, and wide-area networks such as the Internet. Likewise, IEEE 802.15.4 devices provide sensing communication-ability in the wireless domain. The inherent natures of the two networks though, is different. The base specification developed by the 6lowpan IETF group is RFC 4944. The problem statement document is RFC 4919.

Application areas The target for IP networking for low-power radio communication are the applications that need wireless internet connectivity at lower data rates for devices with very limited form factor. Examples could include, but are not limited to: automation and entertainment applications in home, office and factory environments. The header compression mechanisms standardized in RFC4944 can be used to provide header compression of IPv6 packets over such networks. IPv6 is also in use on the Smart Grid enabling smart meters and other devices to build a micro mesh network before sending the data back to the billing system using the IPv6 backbone. Some of these networks run over 802.15.4 radios, and therefore use the header compression and fragmentation as specified by RFC4944.

Functions As with all link-layer mappings of IP, RFC4944 provide a number of functions. Beyond the usual differences between L2 and L3 networks, mapping from the IPv6 network to the IEEE802.15.4 network poses additional design challenges (see RFC 4919 for an overview).

Adapting the packet sizes of the two networks IPv6 requires the maximum transmission unit (MTU) to be at least 1280 Bytes. In contrast, IEEE802.15.4's standard packet size is 127 octets. A maximum frame overhead of 25 octets spares 102 octets at the media access control layer. An optional but highly recommended security feature at the link layer poses an additional overhead. For example, 21 octets are consumed for AES-CCM-128 leaving only 81 octets for upper layers.

Address resolution IPv6 nodes are assigned 128 bit IP addresses in a hierarchical manner, through an arbitrary length network prefix. IEEE 802.15.4 devices may use either of IEEE 64 bit extended addresses or, after an association event, 16 bit addresses that are unique within a PAN. There is also a PAN-ID for a group of physically collocated IEEE802.15.4 devices.

Differing device designs IEEE802.15.4 devices are intentionally constrained in form factor to reduce costs (allowing for large-scale network of many devices), reduce power consumption (allowing battery powered devices) and allow flexibility of installation (e.g. small devices for body-worn networks). On the other hand, wired nodes in the IP domain are not constrained in this way; they can be larger and make use of mains power supplies.

1

6LoWPAN

Differing focus on parameter optimization IPv6 nodes are geared towards attaining high speeds. Algorithms and protocols implemented at the higher layers such as TCP kernel of the TCP/IP are optimized to handle typical network problems such as congestion. In IEEE802.15.4-compliant devices, energy conservation and code-size optimization remain at the top of the agenda.

Adaptation layer for interoperability and packet formats An adaptation mechanism to allow interoperability between IPv6 domain and the IEEE 802.15.4 can best be viewed as a layer problem. Identifying the functionality of this layer and defining newer packet formats, if needed, is an enticing research area. RFC 4944 proposes an adaptation layer to allow the transmission of IPv6 datagrams over IEEE 802.15.4 networks.

Addressing management mechanisms The management of addresses for devices that communicate across the two dissimilar domains of IPv6 and IEEE802.15.4 is cumbersome, if not exhaustingly complex.

Routing considerations and protocols for mesh topologies in 6lowpans Routing per se is a two phased problem that is being considered for low-power IP networking: • Mesh routing in the personal area network (PAN) space. • The routability of packets between the IPv6 domain and the PAN domain.

Device and service discovery Since IP-enabled devices may require the formation of ad hoc networks, the current state of neighboring devices and the services hosted by such devices will need to be known. IPv6 neighbour discovery extensions is an internet draft proposed as a contribution in this area.

Further reading [1] • Interoperability of 6LoWPAN [2] • 6LoWPAN Ad Hoc On-Demand Distance Vector Routing (LOAD) [3] • Dynamic MANET On-demand for 6LoWPAN (DYMO-low) Routing [4] • Hierarchical Routing over 6LoWPAN (HiLow) [5] • LowPan Neighbor Discovery Extensions [6] • Serial forwarding approach to connecting TinyOS-based sensors to IPv6 Internet

External links [7] • Internet Engineering Task Force (IETF) [8] • 6lowpan Working Group [9] • 6lowpan.tzi.org [10] • 6lowpan blog [11] • The book "6LoWPAN: The Wireless Embedded Internet" [12] • Jonathan Hui's research at UC Berkeley

2

6LoWPAN

References [1] http://tools.ietf.org/html/draft-daniel-6lowpan-interoperability-01 [2] http://tools.ietf.org/html/draft-daniel-6lowpan-load-adhoc-routing-03 [3] http://tools.ietf.org/html/draft-montenegro-6lowpan-dymo-low-routing-03 [4] http://tools.ietf.org/html/draft-daniel-6lowpan-hilow-hierarchical-routing-01 [5] http://tools.ietf.org/html/draft-chakrabarti-6lowpan-ipv6-nd-05 [6] http://tools.ietf.org/html/draft-sarikaya-6lowpan-forwarding-00 [7] http://www.ietf.org/ [8] http://www.ietf.org/dyn/wg/charter/6lowpan-charter.html [9] http://6lowpan.tzi.org [10] http://6lowpan.net [11] http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0470747994.html [12] http://www.cs.berkeley.edu/~jwhui/6lowpan.html

6bone

The6bonewas a testbed for Internet Protocol version 6; it was an outgrowth of the IETF IPng project that created the IPv6 protocols intended to eventually replace the current Internet network layer protocols known as IPv4. The 6bone was started outside the official IETF process at the March 1996 IETF meetings, and became a worldwide informal collaborative project, with eventual oversight from the "NGtrans" (IPv6 Transition) Working Group of the IETF. The original mission of the 6bone was to establish a network to foster the development, testing, and deployment of IPv6 using a model to be based upon the experiences from the Mbone, hence the name‘’6bone’’.

The 6bone started as a virtual network (using IPv6 over IPv4 tunneling/encapsulation) operating over the IPv4-based Internet to support IPv6 transport, and slowly added native links specifically for IPv6 transport. Although the initial 6bone focus was on testing of standards and implementations, the eventual focus became more on testing of transition and operational procedures, as well as actual IPv6 network usage.

The 6bone operated under the IPv6 Testing Address Allocation (see RFC 2471), which specified the 3FFE::/16 IPv6 prefix for 6bone testing purposes.

At its peak in mid-2003, over 150 6bone top level 3FFE::/16 network prefixes were routed, interconnecting over 1000 sites in more than 50 countries. When it became obvious that the availability of IPv6 top level production prefixes was assured, and that commercial and private IPv6 networks were being operated outside the 6bone using these prefixes, a plan was developed to phase out the 6bone (see RFC 3701).

The phaseout plan called for a halt to new 6bone prefix allocations on 1 January 2004 and the complete cessation of 6bone operation and routing over the 6bone testing prefixes on 6 June 2006. Addresses within the 6bone testing prefix have now reverted to the IANA, and should no longer be used.

3

6bone

Related RFCs •RFC 2471IPv6 Testing Address Allocation •RFC 37016bone (IPv6 Testing Address Allocation) Phaseout

External links [1] • Archive of 6bone official web site

References [1] http://go6.net/ipv6-6bone/

6over4

6over4is an IPv6 transition mechanism meant to transmit IPv6 packets between dual-stack nodes on top of a multicast-enabled IPv4 network. IPv4 is used as a virtual data link layer (virtual Ethernet) on which IPv6 can be run.

How 6over4 works 6over4 defines a trivial method for generating a link-local IPv6 address from an IPv4 address, and a mechanism to perform Neighbor Discovery on top of IPv4.

Link-local address generation Any host wishing to participate in 6over4 over a given IPv4 network can set up a virtual IPv6 network interface. The link-local address is determined as follows : • it starts with fe80:0000:0000:0000:0000:0000, or fe80:: for short, • the lower-order 32 bits to the binary value must be that of the IPv4 address of the host. For example, host 192.0.2.142 would use fe80:0000:0000:0000:0000:0000:c000:028e as its link-local IPv6 address (192.0.2.142 is c000028e in hexadecimal notation). A shortened notation would be fe80::c000:28e.

Multicast Address Mapping To perform ICMPv6 Neighbor Discovery, multicast must be used. Any IPv6 multicast packet gets encapsulated in an IPv4 multicast packet with destination 239.192.x.y, where x and y are the penultimate and last bytes of the IPv6 multicast address respectively.

Neighbor Discovery Given a link-local address and a multicast addresses mapping, a host can use ICMPv6 to discover its on-link neighbors and routers, and usually perform stateless autoconfiguration, as it would do on top of, e.g. Ethernet.

4

6over4

Limit of 6over4 6over4 relies on IPv4 multicast availability, which is not very widely supported by IPv4 networking infrastructure (multicast is almost as recent as IPv6), 6over4 is of limited practical use, and is not supported by the most common operating systems. To connect IPv6 hosts on different physical links, IPv4 multicast routing must be enabled on the routers connecting the links. ISATAP is a more complex alternative to 6over4 which does not rely on IPv4 multicast.

References • B. Carpenter & C. JungTransmission of IPv6 over IPv4 Domains without Explicit TunnelsRFC 2529, March 1999.

Ad-Hoc Configuration Protocol

TheAd-Hoc Configuration Protocol(AHCP) is an autoconfiguration protocol for IPv6 and dual-stack IPv6/IPv4 networks designed to be used in place of router discovery and DHCP on networks where it is difficult or impossible to configure a server within every link-layer broadcast domain, for example mobile ad-hoc networks. AHCP will automatically configure IPv4 and IPv6 addresses, name servers and NTP servers. It will not configure default routes, since it is designed to be run together with a routing protocol (such as Babel or OLSR). External links : [1] • AHCP development home page [2] • Internet draft for the Ad Hoc Configuration Protocol

References [1] http://www.pps.jussieu.fr/~jch/software/ahcp/ [2] http://www.pps.jussieu.fr/~jch/software/ahcp/draft-chroboczek-ahcp-00.html

5

AICCU

AICCU

Initial release

Stable release

Preview release

Written in

AICCU

Operating system

Available in

Type

License

Website

[1] 1 August 2004 (beta1)

[2] (March 15, 2008) [ +/−] [3] internal betas [ +/−] C

Cross-platform

English

Internet

3-clause BSD

[4] [4]

[5] AICCUcross-platform utility for automatically(Automatic IPv6 Connectivity Client Utility) is a popular configuring an IPv6 tunnel. It is free software available under a BSD license. The utility is originally provided for the SixXS Tunnel Broker but it can also be used by a variety of other tunnel brokers.

History and development AICCU is written and maintained by Jeroen Massar. Various patches from other persons have been incorporated, [6] these persons are acknowledged in the field for their contributions. AICCU is the successor of the Windows-only and Linux/BSD-variety of the Heartbeat tool that was provided by SixXS, solely to use the Heartbeat protocol. When the AYIYA protocol came into existence it was decided that to support this new protocol it would be better to merge the Windows and Unix trees into one program and give it a bit flashier appearance. The name of the Heartbeat tool was then changed to reflect that it did more than providing mere support for the heartbeats.

Award of excellence AICCU has won the Award of Excellence in the Implementation Category of the 2004 Edition of the IPv6 [7] Application Contest .

Supported protocols The following tunneling protocols are currently supported: • 6in4 - Standard IPv6 in IPv4 tunnels using protocol 41 in the IPv4 protocol header. • AYIYA - For IPv6 over IPv4 UDP in a secure manner and being able to work through a NAT. • 6in4 Heartbeat - used for dynamic 6in4 tunnels AICCU primarily uses the TIC protocol to retrieve the configuration parameters of the tunnel automatically that the user wants to have configured.

6

AICCU

Support for other tunnel brokers [8] AICCU finds available tunnel brokers by looking up the TXT DNS records from "_aiccu.sixxs.net" . The latter allows a local network to add their own tunnel broker(s) by adding records in the domains configured in their search path. Non-local tunnel brokers can be added by requesting the SixXS staff to add an entry to the global DNS records.

Supported platforms The following operating systems/platforms/distributions are supported by AICCU: • IBM AIX • DragonFlyBSD • FreeBSD • PC-BSD • NetBSD • OpenBSD • Linux • Mac OS X • Sun Solaris (no AYIYA support) • Windows [9] [10] [11] [12] [13] [14] [15] Various distributions have an AICCU package included in their distribution .

References [1] http://www.sixxs.net/tools/aiccu/history/ [2] http://en.wikipedia.org/wiki/Template%3Alatest_stable_software_release%2Faiccu?action=edit&preload=Template:LSR/syntax [3] http://en.wikipedia.org/wiki/Template%3Alatest_preview_software_release%2Faiccu?action=edit&preload=Template:LSR/syntax [4] http://www.sixxs.net/tools/aiccu/ [5] SixXS Usage (http://www.sixxs.net/misc/usage/#Tunnels) showing the number of tunnels of the SixXS service, most are using AICCU to set the tunnel up [6] AICCU - Changelog (http://www.sixxs.net/tools/aiccu/history/) [7] 2004 Edition of the IPv6 Application Contest (http://www.v6pc.jp/apc2004/en/awards.html#01) [8] AICCU - Tunnelbroker Support (http://www.sixxs.net/tools/aiccu/brokers/) [9] Debian AICCU package (http://packages.debian.org/unstable/net/aiccu) [10] Gentoo AICCU package (http://www.gentoo-portage.com/net-misc/aiccu) [11] Ubuntu 10.04 LTS (Lucid) AICCU package (http://packages.ubuntu.com/lucid/aiccu) [12] OpenWRT AICCU package (https://dev.openwrt.org/browser/packages/ipv6/aiccu) [13] Red Hat AICCU package (http://download.fedora.redhat.com/pub/epel/5/i386/repoview/aiccu.html) [14] FreeBSD AICCU package (http://www.freebsd.org/cgi/ports.cgi?query=sixxs-aiccu) [15] NetBSD AICCU package (ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/net/aiccu/)

External links • The AICCU Homepage (http://www.sixxs.net/tools/aiccu/) • SixXS Tunnel Broker (http://www.sixxs.net/)

7