draft-ietf-6tisch-enrollment-enhanced-beacon-07.txt   draft-ietf-6tisch-enrollment-enhanced-beacon-08.txt 
6tisch Working Group D. Dujovne 6tisch Working Group D. Dujovne
Internet-Draft Universidad Diego Portales Internet-Draft Universidad Diego Portales
Intended status: Standards Track M. Richardson Intended status: Standards Track M. Richardson
Expires: 19 July 2020 Sandelman Software Works Expires: 21 July 2020 Sandelman Software Works
16 January 2020 18 January 2020
IEEE 802.15.4 Information Element encapsulation of 6TiSCH Join and IEEE 802.15.4 Information Element encapsulation of 6TiSCH Join and
Enrollment Information Enrollment Information
draft-ietf-6tisch-enrollment-enhanced-beacon-07 draft-ietf-6tisch-enrollment-enhanced-beacon-08
Abstract Abstract
In TSCH mode of IEEE STD 802.15.4, opportunities for broadcasts are In TSCH mode of IEEE STD 802.15.4, opportunities for broadcasts are
limited to specific times and specific channels. Nodes in a TSCH limited to specific times and specific channels. Nodes in a TSCH
network typically frequently send Enhanced Beacon (EB) frames to network typically frequently send Enhanced Beacon (EB) frames to
announce the presence of the network. This document provides a announce the presence of the network. This document provides a
mechanism by which small details critical for new nodes (pledges) and mechanism by which small details critical for new nodes (pledges) and
long sleeping nodes may be carried within the Enhanced Beacon. long sleeping nodes may be carried within the Enhanced Beacon.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 19 July 2020. This Internet-Draft will expire on 21 July 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 14 skipping to change at page 2, line 14
as described in Section 4.e of the Trust Legal Provisions and are as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Use of BCP 14 Terminology . . . . . . . . . . . . . . . . 2 1.1. Use of BCP 14 Terminology . . . . . . . . . . . . . . . . 2
1.2. Layer-2 Synchronization . . . . . . . . . . . . . . . . . 2 1.2. Layer-2 Synchronization . . . . . . . . . . . . . . . . . 2
1.3. Layer-3 synchronization: IPv6 Router Solicitations and 1.3. Layer-3 synchronization: IPv6 Router Solicitations and
Advertisements . . . . . . . . . . . . . . . . . . . . . 3 Advertisements . . . . . . . . . . . . . . . . . . . . . 3
2. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 3 2. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
[RFC7554] describes the use of the time-slotted channel hopping [RFC7554] describes the use of the time-slotted channel hopping
(TSCH) mode of [ieee802154]. As further detailed in [RFC8180], an (TSCH) mode of [ieee802154]. As further detailed in [RFC8180], an
Enhanced Beacon (EB) is transmitted during a slot designated a Enhanced Beacon (EB) is transmitted during a slot designated a
broadcast slot. broadcast slot.
1.1. Use of BCP 14 Terminology 1.1. Use of BCP 14 Terminology
::boilerplate bcp14 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Other terminology can be found in [I-D.ietf-6tisch-architecture] in Other terminology can be found in [I-D.ietf-6tisch-architecture] in
section 2.1. section 2.1.
1.2. Layer-2 Synchronization 1.2. Layer-2 Synchronization
As explained in section 6 of [RFC8180], the Enhanced Beacon (EB) has As explained in section 6 of [RFC8180], the Enhanced Beacon (EB) has
a number of purposes: synchronization of ASN and Join Metric, a number of purposes: synchronization of ASN and Join Metric,
carrying timeslot template identifier, carrying the channel hopping carrying timeslot template identifier, carrying the channel hopping
sequence identifier, and indicating the TSCH SlotFrame. sequence identifier, and indicating the TSCH SlotFrame.
skipping to change at page 5, line 44 skipping to change at page 6, line 8
In a 6tisch network, where RPL [RFC6550] is used as the mesh routing In a 6tisch network, where RPL [RFC6550] is used as the mesh routing
protocol, the network ID can be constructed from a SHA256 hash of the protocol, the network ID can be constructed from a SHA256 hash of the
prefix (/64) of the network. That is just a suggestion for a default prefix (/64) of the network. That is just a suggestion for a default
value. In some LLNs where multiple PANIDs may lead to the same value. In some LLNs where multiple PANIDs may lead to the same
management device (the JRC), then a common value that is the same management device (the JRC), then a common value that is the same
across all PANs MUST be configured. across all PANs MUST be configured.
3. Security Considerations 3. Security Considerations
All of the contents of this Information Element are sent in the All of the contents of this Information Element are sent in the
clear. The containing Enhanced Beacon is not encrypted. clear. The containing Enhanced Beacon is not encrypted. This is a
restriction in the cryptographic architecture of the TSCH mechanism.
In order to decrypt or do integrity checking of layer-2 frames in
TSCH, the TSCH Absolute Slot Number (ASN) is needed. The Enhanced
Beacon provides the ASN to new (and long-sleeping) nodes.
The Enhanced Beagon is authenticated at the layer-2 level using The Enhanced Beagon is authenticated at the layer-2 level using
802.15.4 mechanisms using the network-wide keying material. Nodes 802.15.4 mechanisms using the network-wide keying material. Nodes
which are enrolled will have the network-wide keying material and can which are enrolled will have the network-wide keying material and can
validate the beacon. validate the beacon, providing them with a trusted
Pledges which have not yet enrolled are unable to authenticate the Pledges which have not yet enrolled are unable to authenticate the
beacons. beacons, and will be forced to temporarily take the contents on
faith. After enrollment, a newly enrolled node will be able to
return to the beacon and validate it.
In addition to the enrollment and join information described in this
document, the Enhanced Beacon contains a description of the TSCH
schedule to be used by the transmitter of this packet. The schedule
can provide an attacker with a list of channels and frequencies on
which communication will occur. Knowledge of this can help an
attacker to more efficiently jam communications, although there is
future work being considered to make some of the schedule less
visible.
4. Privacy Considerations 4. Privacy Considerations
The use of a network ID may reveal information about the network. The use of a network ID may reveal information about the network.
The use of a SHA256 hash of the DODAGID, rather than using the The use of a SHA256 hash of the DODAGID, rather than using the
DODAGID directly provides some cover the addresses used within the DODAGID directly provides some cover the addresses used within the
network. The DODAGID is usually the IPv6 address of the root of the network. The DODAGID is usually the IPv6 address of the root of the
RPL mesh. RPL mesh.
An interloper with a radio sniffer would be able to use the network An interloper with a radio sniffer would be able to use the network
skipping to change at page 7, line 25 skipping to change at page 8, line 9
[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
Bormann, "Neighbor Discovery Optimization for IPv6 over Bormann, "Neighbor Discovery Optimization for IPv6 over
Low-Power Wireless Personal Area Networks (6LoWPANs)", Low-Power Wireless Personal Area Networks (6LoWPANs)",
RFC 6775, DOI 10.17487/RFC6775, November 2012, RFC 6775, DOI 10.17487/RFC6775, November 2012,
<https://www.rfc-editor.org/info/rfc6775>. <https://www.rfc-editor.org/info/rfc6775>.
[RFC8137] Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information [RFC8137] Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information
Element for the IETF", RFC 8137, DOI 10.17487/RFC8137, May Element for the IETF", RFC 8137, DOI 10.17487/RFC8137, May
2017, <https://www.rfc-editor.org/info/rfc8137>. 2017, <https://www.rfc-editor.org/info/rfc8137>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References 7.2. Informative References
[I-D.ietf-6tisch-architecture] [I-D.ietf-6tisch-architecture]
Thubert, P., "An Architecture for IPv6 over the TSCH mode Thubert, P., "An Architecture for IPv6 over the TSCH mode
of IEEE 802.15.4", Work in Progress, Internet-Draft, of IEEE 802.15.4", Work in Progress, Internet-Draft,
draft-ietf-6tisch-architecture-28, 29 October 2019, draft-ietf-6tisch-architecture-28, 29 October 2019,
<http://www.ietf.org/internet-drafts/draft-ietf-6tisch- <http://www.ietf.org/internet-drafts/draft-ietf-6tisch-
architecture-28.txt>. architecture-28.txt>.
[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
 End of changes. 10 change blocks. 
14 lines changed or deleted 37 lines changed or added

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