draft-ietf-6lo-btle-16.txt   draft-ietf-6lo-btle-17.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: January 24, 2016 Nokia Expires: February 5, 2016 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
July 23, 2015 August 4, 2015
IPv6 over BLUETOOTH(R) Low Energy IPv6 over BLUETOOTH(R) Low Energy
draft-ietf-6lo-btle-16 draft-ietf-6lo-btle-17
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 48 skipping to change at page 1, line 48
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 January 24, 2016. This Internet-Draft will expire on February 5, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 10, line 50 skipping to change at page 10, line 50
Figure 5: Isolated Bluetooth LE network Figure 5: Isolated Bluetooth LE network
3.2.2. Stateless address autoconfiguration 3.2.2. Stateless address autoconfiguration
At network interface initialization, both 6LN and 6LBR SHALL generate At network interface initialization, both 6LN and 6LBR SHALL generate
and assign to the Bluetooth LE network interface IPv6 link-local and assign to the Bluetooth LE network interface IPv6 link-local
addresses [RFC4862] based on the 48-bit Bluetooth device addresses addresses [RFC4862] based on the 48-bit Bluetooth device addresses
(see Section 2.3) that were used for establishing the underlying (see Section 2.3) that were used for establishing the underlying
Bluetooth LE connection. A 6LN and a 6LBR are RECOMMENDED to use Bluetooth LE connection. A 6LN and a 6LBR are RECOMMENDED to use
random Bluetooth device addresses. A 6LN SHOULD pick a different private Bluetooth device addresses. A 6LN SHOULD pick a different
Bluetooth device address for every Bluetooth LE connection with a Bluetooth device address for every Bluetooth LE connection with a
6LBR, and a 6LBR SHOULD periodically change its random Bluetooth 6LBR, and a 6LBR SHOULD periodically change its random Bluetooth
device address. Following the guidance of [RFC7136], a 64-bit device address. Following the guidance of [RFC7136], a 64-bit
Interface Identifier (IID) is formed from the 48-bit Bluetooth device Interface Identifier (IID) is formed from the 48-bit Bluetooth device
address by inserting two octets, with hexadecimal values of 0xFF and address by inserting two octets, with hexadecimal values of 0xFF and
0xFE in the middle of the 48-bit Bluetooth device address as shown in 0xFE in the middle of the 48-bit Bluetooth device address as shown in
Figure 6. In the Figure letter 'b' represents a bit from the Figure 6. In the Figure letter 'b' represents a bit from the
Bluetooth device address, copied as is without any changes on any Bluetooth device address, copied as is without any changes on any
bit. This means that no bit in the IID indicates whether the bit. This means that no bit in the IID indicates whether the
underlying Bluetooth device address is public or random. underlying Bluetooth device address is public or random.
skipping to change at page 12, line 18 skipping to change at page 12, line 18
After link-local address configuration, the 6LN sends Router After link-local address configuration, the 6LN sends Router
Solicitation messages as described in [RFC4861] Section 6.3.7. Solicitation messages as described in [RFC4861] Section 6.3.7.
For non-link-local addresses, 6LNs SHOULD NOT be configured to embed For non-link-local addresses, 6LNs SHOULD NOT be configured to embed
the Bluetooth device address in the IID by default. Alternative the Bluetooth device address in the IID by default. Alternative
schemes such as Cryptographically Generated Addresses (CGA) schemes such as Cryptographically Generated Addresses (CGA)
[RFC3972], privacy extensions [RFC4941], Hash-Based Addresses (HBA, [RFC3972], privacy extensions [RFC4941], Hash-Based Addresses (HBA,
[RFC5535]), DHCPv6 [RFC3315], or static, semantically opaque addreses [RFC5535]), DHCPv6 [RFC3315], or static, semantically opaque addreses
[RFC7217] SHOULD be used by default. In situations where the [RFC7217] SHOULD be used by default. In situations where the
Bluetooth device address is known to be a random device address (i.e. Bluetooth device address is known to be a private device address and/
a static or private device address) and/or the header compression or the header compression benefits of embedding the device address in
benefits of embedding the device address in the IID are required to the IID are required to support deployment constraints, 6LNs MAY form
support deployment constraints, 6LNs MAY form a 64-bit IID by a 64-bit IID by utilizing the 48-bit Bluetooth device address. The
utilizing the 48-bit Bluetooth device address. The non-link-local non-link-local addresses that a 6LN generates MUST be registered with
addresses that a 6LN generates MUST be registered with the 6LBR as the 6LBR as described in Section 3.2.3.
described in Section 3.2.3.
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 3.2.1) the 6LBR MUST the link model of the Bluetooth LE (see Section 3.2.1) 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
in Neighbor Discovery messages[RFC4861] (see Section 3.2.3). This in Neighbor Discovery messages[RFC4861] (see Section 3.2.3). This
will cause 6LNs to always send packets to the 6LBR, including the will cause 6LNs to always send packets to the 6LBR, including the
case when the destination is another 6LN using the same prefix. case when the destination is another 6LN using the same prefix.
 End of changes. 6 change blocks. 
12 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/