6lowpan 4
6lowpan 4
6lowpan 4
Low power Storage Periodic sleep Simplicity (CPU Periodic sleep aware
limitations, low aware routing, usage), low management, low
(1-2 years lifetime on overhead low overhead overhead overhead
batteries)
Low cost Stateless address Small or no Ease of Use, Space constraints
generation routing tables simple
(<$10/unit) bootstrapping
High density Large address Scalable and Robust Easy to use and
space IPv6 routable to *a scalable
(<2-4? units/sq ft) node*
IP network interaction Address routable Seamless IP Work end to end Compatible with
from IP world routing from IP network SNMP, etc
Subtleties of IEEE 802.15.4
Small packet size 128 byte including
MAC, 103 bytes of payload
Uses 64 bit MAC addresses, but has
provisions for 16 bit short addresses
Support for multiple topologies
Supports AES block cypher in several
modes (AES-CCM-64 mandatory)
Data rates between 20kbps to 250kbps
Range between 10m to 30m
Why IP?
Most of the IP based technologies
already exist, well known and proven to
be working.
The pervasive nature of IP networks
allows use of existing infrastructure.
Intellectual property conditions for IP
networking technology is either more
favorable or at least better understood
than proprietary and newer solutions.
Why IPv6?
Pros
More suitable for higher density (futuristically 2 orders of
magnitude larger than traditional networks)
Statelessness mandated
No NAT necessary (adds extra cost to the cost prohibitive WSN)
Possibility of adding innovative techniques such as
location aware addressing
Cons
Larger address width (Having efficient address compression
schemes may alleviate this con)
Complying to IPv6 node requirements (IPSec is mandated)
Why not IPv4?
Limited address space
NAT functionality needs gateways, etc
leads to more cost
Statelessness not mandated
Gab/Geoff . any more ideas?
Goals
Protocol data units may be as small as 81 bytes, far below IP and above
In all cases, reuse existing protocols before creating new ones
Address mismatch between MTU sizes of LoWPANs and IPv6
Support stateless auto configuration of IPv6 addressing (location aware?)
Specify header compression (use of existing and/or new techniques eg.
header reconstruction, header short circuiting, etc)
Define security mechanisms, security configuration and bootstrapping
Specify network management (SNMP?)
Specify routing suitable for LoWPAN networks (MANET?, topology
aware, Below L3 or above L3?, etc)
Specify methods to enable and disable IPv6 over LoWPAN.
Specify hooks within routing layer to enable in network processing
Specify light weight discovery mechanisms
Specify any changes needed for L3 + layers
Specify implementation considerations and BKMs of an IPv6 stack
Drafts of 6LoWPAN
Define a *shim* layer below IP
Fragmentation/Reassembly to satisfy IPv6 MTU of 1280 bytes
Routing including mesh
Header compression mechanisms
Header reconstruction for intra PAN communication
Header short circuiting
Header configuration to enable/disable IPv6
Define a IPv6 LoWPAN Profile
Address IPv6 node requirements
Define
L2/L3 interface mechanism
Appropriate security services
Routing considerations
Network management with SNMP
Implementation considerations
Miscellaneous (may be subsequent drafts)
Hooks from L3 for in network processing (especially critical for WSN)
Transport layer (UDP / TCP)
Security configuration
Light weight discovery mechanisms
More?