RFC 7668: IPv6 over BLUETOOTH(R) Low Energy
In plain English — editorial summary, not part of the RFC
Bluetooth Smart is the brand name for the Bluetooth low energy feature in the Bluetooth specification defined by the Bluetooth Special Interest Group. The standard Bluetooth radio has been widely implemented and available in mobile phones, notebook computers, audio headsets, and many other devices. The low-power version of Bluetooth is a specification that enables the use of this air interface with devices such as sensors, smart meters, appliances, etc. The low-power variant of Bluetooth has been standardized since revision 4.0 of the Bluetooth specifications, although version 4.1 or newer is required for IPv6. This document describes how IPv6 is transported over Bluetooth low energy using IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) techniques.
Document record
- Document ID
- RFC7668
- Published
- October 2015
- Authors
- J. Nieminen; T. Savolainen; M. Isomaki; B. Patil; Z. Shelby; C. Gomez
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9159IPv6 Mesh over BLUETOOTH(R) Low Energy Using the Internet Protocol Support Profile (IPSP)Current
December 2021
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 9006TCP Usage Guidance in the Internet of Things (IoT)Current
March 2021
- RFC 9011Static Context Header Compression and Fragmentation (SCHC) over LoRaWANCurrent
April 2021
- RFC 9428Transmission of IPv6 Packets over Near Field CommunicationCurrent
July 2023
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7676IPv6 Support for Generic Routing Encapsulation (GRE)Current
October 2015
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?