draft-ietf-6lo-btle-02.txt   draft-ietf-6lo-btle-03.txt 
6Lo Working Group J. Nieminen 6Lo Working Group J. Nieminen
Internet-Draft T. Savolainen Internet-Draft T. Savolainen
Intended status: Standards Track M. Isomaki Intended status: Standards Track M. Isomaki
Expires: December 13, 2014 Nokia Expires: March 5, 2015 Nokia
B. Patil B. Patil
AT&T AT&T
Z. Shelby Z. Shelby
Arm Arm
C. Gomez C. Gomez
Universitat Politecnica de Catalunya/i2CAT Universitat Politecnica de Catalunya/i2CAT
June 11, 2014 September 1, 2014
Transmission of IPv6 Packets over BLUETOOTH(R) Low Energy Transmission of IPv6 Packets over BLUETOOTH(R) Low Energy
draft-ietf-6lo-btle-02 draft-ietf-6lo-btle-03
Abstract Abstract
Bluetooth Smart is the brand name for the Bluetooth low energy Bluetooth Smart is the brand name for the Bluetooth low energy
feature in the Bluetooth specification defined by the Bluetooth feature in the Bluetooth specification defined by the Bluetooth
Special Interest Group. The standard Bluetooth radio has been widely Special Interest Group. The standard Bluetooth radio has been widely
implemented and available in mobile phones, notebook computers, audio implemented and available in mobile phones, notebook computers, audio
headsets and many other devices. The low power version of Bluetooth headsets and many other devices. The low power version of Bluetooth
is a specification that enables the use of this air interface with is a specification that enables the use of this air interface with
devices such as sensors, smart meters, appliances, etc. The low devices such as sensors, smart meters, appliances, etc. The low
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 December 13, 2014. This Internet-Draft will expire on March 5, 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 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology and Requirements Language . . . . . . . . . . 3 1.1. Terminology and Requirements Language . . . . . . . . . . 3
2. Bluetooth Low Energy . . . . . . . . . . . . . . . . . . . . 3 2. Bluetooth Low Energy . . . . . . . . . . . . . . . . . . . . 3
2.1. Bluetooth LE stack . . . . . . . . . . . . . . . . . . . 4 2.1. Bluetooth LE stack . . . . . . . . . . . . . . . . . . . 4
2.2. Link layer roles and topology . . . . . . . . . . . . . . 5 2.2. Link layer roles and topology . . . . . . . . . . . . . . 5
2.3. Bluetooth LE device addressing . . . . . . . . . . . . . 5 2.3. Bluetooth LE device addressing . . . . . . . . . . . . . 5
2.4. Bluetooth LE packets sizes and MTU . . . . . . . . . . . 6 2.4. Bluetooth LE packets sizes and MTU . . . . . . . . . . . 6
3. Specification of IPv6 over Bluetooth Low Energy . . . . . . . 6 3. Specification of IPv6 over Bluetooth Low Energy . . . . . . . 6
3.1. Protocol stack . . . . . . . . . . . . . . . . . . . . . 6 3.1. Protocol stack . . . . . . . . . . . . . . . . . . . . . 7
3.2. Link model . . . . . . . . . . . . . . . . . . . . . . . 7 3.2. Link model . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.1. Stateless address autoconfiguration . . . . . . . . . 8 3.2.1. Stateless address autoconfiguration . . . . . . . . . 8
3.2.2. Neighbor discovery . . . . . . . . . . . . . . . . . 8 3.2.2. Neighbor discovery . . . . . . . . . . . . . . . . . 9
3.2.3. Header compression . . . . . . . . . . . . . . . . . 9 3.2.3. Header compression . . . . . . . . . . . . . . . . . 10
3.2.3.1. Remote destination example . . . . . . . . . . . 10 3.2.3.1. Remote destination example . . . . . . . . . . . 11
3.2.4. Unicast and Multicast address mapping . . . . . . . . 11 3.2.4. Unicast and Multicast address mapping . . . . . . . . 12
3.3. Internet connectivity scenarios . . . . . . . . . . . . . 11 3.3. Internet connectivity scenarios . . . . . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. Additional contributors . . . . . . . . . . . . . . . . . . . 13 6. Additional contributors . . . . . . . . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Bluetooth low energy (LE) is a radio technology targeted for devices Bluetooth low energy (LE) is a radio technology targeted for devices
that operate with coin cell batteries or minimalistic power sources, that operate with coin cell batteries or minimalistic power sources,
which means that low power consumption is essential. Bluetooth LE is which means that low power consumption is essential. Bluetooth LE is
an especially attractive technology for Internet of Things an especially attractive technology for Internet of Things
applications, such as health monitors, environmental sensing, applications, such as health monitors, environmental sensing,
proximity applications and many others. proximity applications and many others.
skipping to change at page 3, line 44 skipping to change at page 3, line 44
Bluetooth LE is designed for transferring small amounts of data Bluetooth LE is designed for transferring small amounts of data
infrequently at modest data rates at a very low cost per bit. infrequently at modest data rates at a very low cost per bit.
Bluetooth Special Interest Group (Bluetooth SIG) has introduced two Bluetooth Special Interest Group (Bluetooth SIG) has introduced two
trademarks, Bluetooth Smart for single-mode devices (a device that trademarks, Bluetooth Smart for single-mode devices (a device that
only supports Bluetooth LE) and Bluetooth Smart Ready for dual-mode only supports Bluetooth LE) and Bluetooth Smart Ready for dual-mode
devices (devices that support both Bluetooth and Bluetooth LE). In devices (devices that support both Bluetooth and Bluetooth LE). In
the rest of the document, the term Bluetooth LE refers to both types the rest of the document, the term Bluetooth LE refers to both types
of devices. of devices.
Bluetooth LE was introduced in Bluetooth 4.0 and further enhanced in Bluetooth LE was introduced in Bluetooth 4.0 and further enhanced in
Bluetooth 4.1 [BTCorev4.1]. Bluetooth SIG will also publish Internet Bluetooth 4.1 [BTCorev4.1]. Bluetooth SIG has also published
Protocol Support Profile (IPSP) [IPSP], which includes Internet Internet Protocol Support Profile (IPSP) [IPSP], which includes
Protocol Support Service (IPSS) and that enables discovery of IP- Internet Protocol Support Service (IPSS). The IPSP enables discovery
enabled devices and establishment of link-layer connection for of IP-enabled devices and establishment of link-layer connection for
transporting IPv6 packets. IPv6 over Bluetooth LE is dependent on transporting IPv6 packets. IPv6 over Bluetooth LE is dependent on
both Bluetooth 4.1 and IPSP. both Bluetooth 4.1 and IPSP 1.0 or newer.
Devices such as mobile phones, notebooks, tablets and other handheld Devices such as mobile phones, notebooks, tablets and other handheld
computing devices which will include Bluetooth 4.1 chipsets will also computing devices which will include Bluetooth 4.1 chipsets will also
have the low-energy functionality of Bluetooth. Bluetooth LE will have the low-energy functionality of Bluetooth. Bluetooth LE will
also be included in many different types of accessories that also be included in many different types of accessories that
collaborate with mobile devices such as phones, tablets and notebook collaborate with mobile devices such as phones, tablets and notebook
computers. An example of a use case for a Bluetooth LE accessory is computers. An example of a use case for a Bluetooth LE accessory is
a heart rate monitor that sends data via the mobile phone to a server a heart rate monitor that sends data via the mobile phone to a server
on the Internet. on the Internet.
skipping to change at page 5, line 47 skipping to change at page 5, line 47
2.3. Bluetooth LE device addressing 2.3. Bluetooth LE device addressing
Every Bluetooth LE device is identified by a 48-bit device address. Every Bluetooth LE device is identified by a 48-bit device address.
The Bluetooth specification describes the device address of a The Bluetooth specification describes the device address of a
Bluetooth LE device as:"Devices are identified using a device Bluetooth LE device as:"Devices are identified using a device
address. Device addresses may be either a public device address or a address. Device addresses may be either a public device address or a
random device address." [BTCorev4.1]. The public device addresses random device address." [BTCorev4.1]. The public device addresses
are based on the IEEE 802-2001 standard [IEEE802-2001]. The random are based on the IEEE 802-2001 standard [IEEE802-2001]. The random
device addresses are generated as defined in the Bluetooth device addresses are generated as defined in the Bluetooth
specification. The device addresses are always unique within a specification. These random device addresses have a very small
Bluetooth LE piconet, but the random addresses are not guaranteed to chance of being in conflict, as Bluetooth LE does not support random
be globally unique. device address collision avoidance or detection.
2.4. Bluetooth LE packets sizes and MTU 2.4. Bluetooth LE packets sizes and MTU
Optimal MTU defined for L2CAP fixed channels over Bluetooth LE is 27 Optimal MTU defined for L2CAP fixed channels over Bluetooth LE is 27
bytes including the L2CAP header of four bytes. Default MTU for bytes including the L2CAP header of four bytes. Default MTU for
Bluetooth LE is hence defined to be 27 bytes. Therefore, excluding Bluetooth LE is hence defined to be 27 bytes. Therefore, excluding
L2CAP header of four bytes, protocol data unit (PDU) size of 23 bytes L2CAP header of four bytes, protocol data unit (PDU) size of 23 bytes
is available for upper layers. In order to be able to transmit IPv6 is available for upper layers. In order to be able to transmit IPv6
packets of 1280 bytes or larger, link layer fragmentation and packets of 1280 bytes or larger, link layer fragmentation and
reassembly solution is provided by the L2CAP layer. The IPSP defines reassembly solution is provided by the L2CAP layer. The IPSP defines
skipping to change at page 6, line 26 skipping to change at page 6, line 26
is negotiated separately for each direction. Implementations that is negotiated separately for each direction. Implementations that
require single link-layer MTU value SHALL use the smallest of the require single link-layer MTU value SHALL use the smallest of the
possibly different MTU values. possibly different MTU values.
3. Specification of IPv6 over Bluetooth Low Energy 3. Specification of IPv6 over Bluetooth Low Energy
Before any IP-layer communications can take place over Bluetooth LE, Before any IP-layer communications can take place over Bluetooth LE,
Bluetooth LE enabled nodes such as 6LNs and 6LBRs have to find each Bluetooth LE enabled nodes such as 6LNs and 6LBRs have to find each
other and establish a suitable link-layer connection. The discovery other and establish a suitable link-layer connection. The discovery
and Bluetooth LE connection setup procedures are documented by and Bluetooth LE connection setup procedures are documented by
Bluetooth SIG in the IPSP specification [IPSP], and hence are out of Bluetooth SIG in the IPSP specification [IPSP]. In the rare case of
scope of this document. The IPSP depends on Bluetooth version 4.1, Bluetooth LE random device address conflict, the 6LBR can detect
and hence both Bluetooth version 4.1 or newer and IPSP are required multiple 6LNs with the same Bluetooth LE device address. The 6LBR
for IPv6 communications. MUST have at most one connection for a given Bluetooth LE device
address at any given moment. This will avoid addressing conflicts
within a Bluetooth LE network. The IPSP depends on Bluetooth version
4.1, and hence both Bluetooth version 4.1, or newer, and IPSP version
1.0, or newer, are required for IPv6 communications.
Bluetooth LE technology sets strict requirements for low power Bluetooth LE technology sets strict requirements for low power
consumption and thus limits the allowed protocol overhead. 6LoWPAN consumption and thus limits the allowed protocol overhead. 6LoWPAN
standards [RFC6775], and [RFC6282] provide useful functionality for standards [RFC6775], and [RFC6282] provide useful functionality for
reducing overhead which can be applied to Bluetooth LE. This reducing overhead which can be applied to Bluetooth LE. This
functionality comprises of link-local IPv6 addresses and stateless functionality comprises of link-local IPv6 addresses and stateless
IPv6 address autoconfiguration (see Section 3.2.1), Neighbor IPv6 address autoconfiguration (see Section 3.2.1), Neighbor
Discovery (see Section 3.2.2) and header compression (see Discovery (see Section 3.2.2) and header compression (see
Section 3.2.3). Section 3.2.3).
skipping to change at page 7, line 37 skipping to change at page 7, line 45
a link as "a communication facility or medium over which nodes can a link as "a communication facility or medium over which nodes can
communicate at the link layer, i.e., the layer immediately below communicate at the link layer, i.e., the layer immediately below
IPv6." IPv6."
In the case of Bluetooth LE, 6LoWPAN layer is adapted to support In the case of Bluetooth LE, 6LoWPAN layer is adapted to support
transmission of IPv6 packets over Bluetooth LE. The IPSP defines all transmission of IPv6 packets over Bluetooth LE. The IPSP defines all
steps required for setting up the Bluetooth LE connection over which steps required for setting up the Bluetooth LE connection over which
6LoWPAN can function [IPSP], including handling the link-layer 6LoWPAN can function [IPSP], including handling the link-layer
fragmentation required on Bluetooth LE, as described in Section 2.4. fragmentation required on Bluetooth LE, as described in Section 2.4.
This specification also assumes the IPv6 header compression format While Bluetooth LE protocols, such as L2CAP, utilize little-endian
specified in RFC 6282 is used [RFC6282]. It is also assumed that the byte orderering, IPv6 packets MUST be transmitted in big endian order
IPv6 payload length can be inferred from the L2CAP header length and (network byte order).
the IID value inferred from the link-layer address with help of
Neighbor Cache, if elided from compressed packet header. This specification requires IPv6 header compression format specified
in RFC 6282 to be used [RFC6282]. It is assumed that the IPv6
payload length can be inferred from the L2CAP header length and the
IID value inferred from the link-layer address with help of Neighbor
Cache, if elided from compressed packet header.
Bluetooth LE connections used to build a star topology are point-to- Bluetooth LE connections used to build a star topology are point-to-
point in nature, as Bluetooth broadcast features are not used for point in nature, as Bluetooth broadcast features are not used for
IPv6 over Bluetooth LE. 6LN-to-6LN communications, e.g. using link- IPv6 over Bluetooth LE. 6LN-to-6LN communications, e.g. using link-
local addresses, need to be bridged by the 6LBR. The 6LBR ensures local addresses, need to be bridged by the 6LBR. The 6LBR ensures
address collisions do not occur (see Section 3.2.2). address collisions do not occur (see Section 3.2.2).
After the peripheral and central have connected at the Bluetooth LE After the peripheral and central have connected at the Bluetooth LE
level, the link can be considered up and IPv6 address configuration level, the link can be considered up and IPv6 address configuration
and transmission can begin. and transmission can begin.
3.2.1. Stateless address autoconfiguration 3.2.1. Stateless address autoconfiguration
A Bluetooth LE 6LN performs stateless address autoconfiguration as At network interface initialization, both 6LN and 6LBR SHALL generate
per RFC 4862 [RFC4862]. A 64-bit Interface identifier (IID) for a and assign to the Bluetooth LE network interface IPv6 link-local
Bluetooth LE interface MAY be formed by utilizing the 48-bit addresses [RFC4862] based on the 48-bit Bluetooth device addresses
Bluetooth device address (see Section 2.3) as defined in RFC 2464 (see Section 2.3) that were used for establishing underlying
"IPv6 over Ethernet" specification [RFC2464]. Alternatively, a Bluetooth LE connection. A 64-bit Interface Identifier (IID) is
randomly generated IID (see Section 3.2.2) can be used instead, for formed from 48-bit device address as defined in RFC 2464 [RFC2464].
example, as discussed in [I-D.ietf-6man-default-iids]. In the case The IID is then appended with prefix fe80::/64, as described in RFC
of randomly generated IID or randomly generated Bluetooth device 4291 [RFC4291] and as depicted in Figure 4. The same link-local
address, the "Universal/Local" bit MUST be set to 0 [RFC4291]. Only address SHALL be used for the lifetime of the Bluetooth LE L2CAP
if the Bluetooth device address is known to be a public address the channel. (After Bluetooth LE logical link has been established, it
"Universal/Local" bit can be set to 1. is referenced with a Connection Handle in HCI. Thus possibly
changing device addresses do not impact data flows within existing
As defined in RFC 4291 [RFC4291], the IPv6 link-local address for a L2CAP channel. Hence there is no need to change IPv6 link-local
Bluetooth LE node is formed by appending the IID, to the prefix addresses even if devices change their random device addresses during
FE80::/64, as depicted in Figure 4. L2CAP channel lifetime).
10 bits 54 bits 64 bits 10 bits 54 bits 64 bits
+----------+-----------------+----------------------+ +----------+-----------------+----------------------+
|1111111010| zeros | Interface Identifier | |1111111010| zeros | Interface Identifier |
+----------+-----------------+----------------------+ +----------+-----------------+----------------------+
Figure 4: IPv6 link-local address in Bluetooth LE Figure 4: IPv6 link-local address in Bluetooth LE
A 6LN MUST join the all-nodes multicast address. There is no need
for 6LN to join the solicited-node multicast address, since 6LBR will
know device addresses and hence link-local addresses of all connected
6LNs. The 6LBR will ensure no two devices with the same Bluetooth LE
device address are connected at the same time. Effectively duplicate
address detection for link-local addresses is performed by the 6LBR's
software responsible of discovery of IP-enabled Bluetooth LE nodes
and of starting Bluetooth LE connection establishment procedures.
This approach increases complexity of 6LBR, but reduces power
consumption on both 6LN and 6LBR at link establishment phase by
reducing number of mandatory packet transmissions.
After link-local address configuration, 6LN sends Router Solicitation
messages as described in [RFC4861] Section 6.3.7.
For non-link-local addresses a 64-bit IID MAY be formed by utilizing
the 48-bit Bluetooth device address. Alternatively, a randomly
generated IID (see Section 3.2.2) can be used instead, for example,
as discussed in [I-D.ietf-6man-default-iids]. The non-link-local
addresses 6LN generates must be registered with 6LBR as described in
Section 3.2.2.
Only if the Bluetooth device address is known to be a public address
the "Universal/Local" bit can be set to 1 [RFC4291].
The tool for a 6LBR to obtain an IPv6 prefix for numbering the The tool for a 6LBR to obtain an IPv6 prefix for numbering the
Bluetooth LE network is out of scope of this document, but can be, Bluetooth LE network is out of scope of this document, but can be,
for example, accomplished via DHCPv6 Prefix Delegation [RFC3633] or for example, accomplished via DHCPv6 Prefix Delegation [RFC3633] or
by using Unique Local IPv6 Unicast Addresses (ULA) [RFC4193]. Due to by using Unique Local IPv6 Unicast Addresses (ULA) [RFC4193]. Due to
the link model of the Bluetooth LE (see Section 2.2) the 6LBR MUST the link model of the Bluetooth LE (see Section 2.2) the 6LBR MUST
set the "on-link" flag (L) to zero in the Prefix Information Option set the "on-link" flag (L) to zero in the Prefix Information Option
[RFC4861]. This will cause 6LNs to always send packets to the 6LBR, [RFC4861]. This will cause 6LNs to always send packets to the 6LBR,
including the case when the destination is another 6LN using the same including the case when the destination is another 6LN using the same
prefix. prefix.
skipping to change at page 9, line 5 skipping to change at page 9, line 44
'Neighbor Discovery Optimization for IPv6 over Low-Power Wireless 'Neighbor Discovery Optimization for IPv6 over Low-Power Wireless
Personal Area Networks (6LoWPANs)' [RFC6775] describes the neighbor Personal Area Networks (6LoWPANs)' [RFC6775] describes the neighbor
discovery approach as adapted for use in several 6LoWPAN topologies, discovery approach as adapted for use in several 6LoWPAN topologies,
including the mesh topology. Bluetooth LE does not support mesh including the mesh topology. Bluetooth LE does not support mesh
networks and hence only those aspects that apply to a star topology networks and hence only those aspects that apply to a star topology
are considered. are considered.
The following aspects of the Neighbor Discovery optimizations The following aspects of the Neighbor Discovery optimizations
[RFC6775] are applicable to Bluetooth LE 6LNs: [RFC6775] are applicable to Bluetooth LE 6LNs:
1. A Bluetooth LE 6LN MUST register its addresses with the 6LBR by 1. A Bluetooth LE 6LN MUST register its non-link-local addresses
sending a Neighbor Solicitation (NS) message with the Address with the 6LBR by sending a Neighbor Solicitation (NS) message with
Registration Option (ARO) and process the Neighbor Advertisement (NA) the Address Registration Option (ARO) and process the Neighbor
accordingly. The NS with the ARO option MUST be sent irrespective of Advertisement (NA) accordingly. The NS with the ARO option MUST be
the method used to generate the IID. The 6LN MUST register only one sent irrespective of the method used to generate the IID. The 6LN
IPv6 address per IPv6 prefix available on a link. MUST register only one IPv6 address per IPv6 prefix available on a
link.
2. For sending Router Solicitations and processing Router 2. For sending Router Solicitations and processing Router
Advertisements the Bluetooth LE 6LNs MUST, respectively, follow Advertisements the Bluetooth LE 6LNs MUST, respectively, follow
Sections 5.3 and 5.4 of the [RFC6775]. Sections 5.3 and 5.4 of the [RFC6775].
3.2.3. Header compression 3.2.3. Header compression
Header compression as defined in RFC 6282 [RFC6282], which specifies Header compression as defined in RFC 6282 [RFC6282], which specifies
the compression format for IPv6 datagrams on top of IEEE 802.15.4, is the compression format for IPv6 datagrams on top of IEEE 802.15.4, is
REQUIRED in this document as the basis for IPv6 header compression on REQUIRED in this document as the basis for IPv6 header compression on
skipping to change at page 9, line 40 skipping to change at page 10, line 33
case of Bluetooth LE, the field SHALL be filled with the 48-bit case of Bluetooth LE, the field SHALL be filled with the 48-bit
device address used by the Bluetooth LE node converted into 64-bit device address used by the Bluetooth LE node converted into 64-bit
Modified EUI-64 format [RFC4291]. Modified EUI-64 format [RFC4291].
To enable efficient header compression, the 6LBR MUST include 6LoWPAN To enable efficient header compression, the 6LBR MUST include 6LoWPAN
Context Option (6CO) [RFC6775] for all prefixes the 6LBR advertises Context Option (6CO) [RFC6775] for all prefixes the 6LBR advertises
in Router Advertisements for use in stateless address in Router Advertisements for use in stateless address
autoconfiguration. autoconfiguration.
When a 6LN is sending a packet to or through a 6LBR, it MUST fully When a 6LN is sending a packet to or through a 6LBR, it MUST fully
elide the source address it has registered with ARO to the 6LBR for elide the source address if it is a link-local address or a non-link-
the indicated prefix. That is, if SAC=0 and SAM=11 the 6LN MUST have local address 6LN has registered with ARO to the 6LBR for the
registered the source link-local IPv6 address it is using using ARO, indicated prefix. That is, if SAC=0 and SAM=11 the 6LN MUST be using
the link-local IPv6 address derived from Bluetooth LE device address,
and if SAC=1 and SAM=11 the 6LN MUST have registered the source IPv6 and if SAC=1 and SAM=11 the 6LN MUST have registered the source IPv6
address with the prefix related to compression context identified address with the prefix related to compression context identified
with Context Identifier Extension. The destination IPv6 address MUST with Context Identifier Extension. The destination IPv6 address MUST
be fully elided if the destination address is the same address to be fully elided if the destination address is the same address to
which the 6LN has succesfully registered its source IPv6 address with which the 6LN has succesfully registered its source IPv6 address with
ARO (set DAC=0, DAM=11). The destination IPv6 address MUST be fully ARO (set DAC=0, DAM=11). The destination IPv6 address MUST be fully
or partially elided if context has been set up for the destination or partially elided if context has been set up for the destination
address. For example, DAC=0 and DAM=01 when destination prefix is address. For example, DAC=0 and DAM=01 when destination prefix is
link-local, and DAC=1 and DAM=01 with Context Identifier Extension if link-local, and DAC=1 and DAM=01 with Context Identifier Extension if
compression context has been configured for the used destination compression context has been configured for the used destination
skipping to change at page 12, line 25 skipping to change at page 13, line 25
Figure 6: Isolated Bluetooth LE network Figure 6: Isolated Bluetooth LE network
It is also possible to have point-to-point connection between two It is also possible to have point-to-point connection between two
6LNs, one of which being central and another being peripheral. 6LNs, one of which being central and another being peripheral.
Similarly, it is possible to have point-to-point connections between Similarly, it is possible to have point-to-point connections between
two 6LBRs, one of which being central and another being peripheral. two 6LBRs, one of which being central and another being peripheral.
At this point in time mesh networking with Bluetooth LE is not At this point in time mesh networking with Bluetooth LE is not
specified. specified.
In the isolated network scenario communications between 6LN and 6LBR
can use IPv6 link-local methodology, but for communications between
different 6LNs, the 6LBR has to number the network with ULA prefix
[RFC4193], and route packets between 6LNs.
4. IANA Considerations 4. IANA Considerations
There are no IANA considerations related to this document. There are no IANA considerations related to this document.
5. Security Considerations 5. Security Considerations
The transmission of IPv6 over Bluetooth LE links has similar The transmission of IPv6 over Bluetooth LE links has similar
requirements and concerns for security as for IEEE 802.15.4. requirements and concerns for security as for IEEE 802.15.4.
Bluetooth LE Link Layer security considerations are covered by the Bluetooth LE Link Layer security considerations are covered by the
IPSP [IPSP]. IPSP [IPSP].
skipping to change at page 13, line 5 skipping to change at page 13, line 47
using the Counter with CBC-MAC (CCM) mechanism [RFC3610] and a using the Counter with CBC-MAC (CCM) mechanism [RFC3610] and a
128-bit AES block cipher. Upper layer security mechanisms may 128-bit AES block cipher. Upper layer security mechanisms may
exploit this functionality when it is available. (Note: CCM does not exploit this functionality when it is available. (Note: CCM does not
consume bytes from the maximum per-packet L2CAP data size, since the consume bytes from the maximum per-packet L2CAP data size, since the
link layer data unit has a specific field for them when they are link layer data unit has a specific field for them when they are
used.) used.)
Key management in Bluetooth LE is provided by the Security Manager Key management in Bluetooth LE is provided by the Security Manager
Protocol (SMP), as defined in [BTCorev4.1]. Protocol (SMP), as defined in [BTCorev4.1].
The IPv6 link-local address configuration described in Section 3.2.1
strictly binds the privacy level of IPv6 link-local address to the
privacy level device has selected for the Bluetooth LE. This means
that a device using Bluetooth privacy features will retain the same
level of privacy with generated IPv6 link-local addresses.
Respectively, device not using privacy at Bluetooth level will not
have privacy at IPv6 link-local address either. For non-link local
addresses implementations have a choice to support
[I-D.ietf-6man-default-iids].
6. Additional contributors 6. Additional contributors
Kanji Kerai, Jari Mutikainen, David Canfeng-Chen and Minjun Xi from Kanji Kerai, Jari Mutikainen, David Canfeng-Chen and Minjun Xi from
Nokia have contributed significantly to this document. Nokia have contributed significantly to this document.
7. Acknowledgements 7. Acknowledgements
The Bluetooth, Bluetooth Smart and Bluetooth Smart Ready marks are The Bluetooth, Bluetooth Smart and Bluetooth Smart Ready marks are
registred trademarks owned by Bluetooth SIG, Inc. registred trademarks owned by Bluetooth SIG, Inc.
Samita Chakrabarti, Erik Nordmark, and Marcel De Kogel have provided Samita Chakrabarti, Erik Nordmark, Marcel De Kogel, Dave Thaler, and
valuable feedback for this draft. Brian Haberman have provided valuable feedback for this draft.
Authors would like to give special acknowledgements for Krishna Authors would like to give special acknowledgements for Krishna
Shingala, Frank Berntsen, and Bluetooth SIG's Internet Working Group Shingala, Frank Berntsen, and Bluetooth SIG's Internet Working Group
for providing significant feedback and improvement proposals for this for providing significant feedback and improvement proposals for this
document. document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[BTCorev4.1] [BTCorev4.1]
Bluetooth Special Interest Group, "Bluetooth Core Bluetooth Special Interest Group, "Bluetooth Core
Specification Version 4.1", December 2013. Specification Version 4.1", December 2013.
[IPSP] Bluetooth Special Interest Group, "Bluetooth Internet [IPSP] Bluetooth Special Interest Group, "Bluetooth Internet
Protocol Support Profile Specification - REFERENCE TO BE Protocol Support Profile Specification Version 1.0", NOT
UPDATED ONCE IPSP IS PUBLISHED", 2014. YET PUBLISHED.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", RFC 2464, December 1998. Networks", RFC 2464, December 1998.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
skipping to change at page 14, line 45 skipping to change at page 16, line 4
December 2003. December 2003.
[RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", RFC 4193, October 2005. Addresses", RFC 4193, October 2005.
[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.
Authors' Addresses Authors' Addresses
Johanna Nieminen Johanna Nieminen
Nokia Nokia
Itamerenkatu 11-13
Helsinki 00180
Finland
Email: johannamaria.nieminen@gmail.com Email: johannamaria.nieminen@gmail.com
Teemu Savolainen Teemu Savolainen
Nokia Nokia
Hermiankatu 12 D Visiokatu 3
Tampere 33720 Tampere 33720
Finland Finland
Email: teemu.savolainen@nokia.com Email: teemu.savolainen@nokia.com
Markus Isomaki Markus Isomaki
Nokia Nokia
Keilalahdentie 2-4 Otaniementie 19
Espoo 02150 Espoo 02150
Finland Finland
Email: markus.isomaki@nokia.com Email: markus.isomaki@nokia.com
Basavaraj Patil Basavaraj Patil
AT&T AT&T
1410 E. Renner Road 1410 E. Renner Road
Richardson, TX 75082 Richardson, TX 75082
USA USA
 End of changes. 24 change blocks. 
74 lines changed or deleted 112 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/