draft-ietf-6tisch-enrollment-enhanced-beacon-02.txt   draft-ietf-6tisch-enrollment-enhanced-beacon-03.txt 
6lo Working Group D. Dujovne 6lo 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: September 26, 2019 Sandelman Software Works Expires: March 12, 2020 Sandelman Software Works
March 25, 2019 September 09, 2019
IEEE802.15.4 Informational Element encapsulation of 6tisch Join and IEEE802.15.4 Informational Element encapsulation of 6tisch Join and
Enrollment Information Enrollment Information
draft-ietf-6tisch-enrollment-enhanced-beacon-02 draft-ietf-6tisch-enrollment-enhanced-beacon-03
Abstract Abstract
In TSCH mode of IEEE802.15.4, as described by [RFC8180], In TSCH mode of IEEE802.15.4, as described by [RFC8180],
opportunities for broadcasts are limited to specific times and opportunities for broadcasts are limited to specific times and
specific channels. Nodes in a TSCH network typically frequently send specific channels. Nodes in a TSCH network typically frequently send
Enhanced Beacon (EB) frames to announce the presence of the network. Enhanced Beacon (EB) frames to announce the presence of the network.
This document provides a mechanism by which small details critical This document provides a mechanism by which small details critical
for new nodes (pledges) and long sleeping nodes may be carried within for new nodes (pledges) and long sleeping nodes may be carried within
the Enhanced Beacon. the Enhanced Beacon.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 September 26, 2019. This Internet-Draft will expire on March 12, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Use of BCP 14 Terminology . . . . . . . . . . . . . . . . 2
1.2. Layer-2 Synchronization . . . . . . . . . . . . . . . . . 3 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 . . . . . . . . . . . . . . . . . . . . . 4 2. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . 5
4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Change history . . . . . . . . . . . . . . . . . . . 8 Appendix A. Change history . . . . . . . . . . . . . . . . . . . 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 details in [RFC8180], an (TSCH) mode of [ieee802154]. As further details in [RFC8180], an
Enhanced Beacon is transmitted during a slot designated a broadcast Enhanced Beacon is transmitted during a slot designated a broadcast
slot. slot.
EDNOTE: Explain why broadcasts are rare, and why we need them. What 1.1. Use of BCP 14 Terminology
the Enhanced Beacon is, and what Information Elements are, and how
the IETF has a subtype for that area. Explain what kind of things
could be placed in Information Elements, how big they could be, and
how they could be compressed.
1.1. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 "OPTIONAL" in this document are to be interpreted as described in
[RFC2119] and indicate requirement levels for compliant STuPiD [BCP14] [RFC2119] when, and only when, they appear in all capitals,
implementations. 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 has a As explained in section 6 of [RFC8180], the Enhanced Beacon has a
number of purposes: synchronization of ASN and Join Metric, timeslot number of purposes: synchronization of ASN and Join Metric, timeslot
template identifier, the channel hopping sequence identifier, TSCH template identifier, the channel hopping sequence identifier, TSCH
SlotFrame and Link IE. SlotFrame and Link IE.
skipping to change at page 4, line 8 skipping to change at page 3, line 49
a Router Soliciation that it can use. a Router Soliciation that it can use.
3. a new pledge may listen to many Enhanced Beacons before it can 3. a new pledge may listen to many Enhanced Beacons before it can
pick an appropriate network and/or closest Join Assistant to pick an appropriate network and/or closest Join Assistant to
attach to. If it must listen for a RS as well as find the attach to. If it must listen for a RS as well as find the
Enhanced Beacon, then the process may take a very long time. Enhanced Beacon, then the process may take a very long time.
2. Protocol Definition 2. Protocol Definition
[RFC8137] creates a registry for new IETF IE subtypes. This document [RFC8137] creates a registry for new IETF IE subtypes. This document
allocates a new subtype TBD-XXX. allocates a new subtype.
This document documents a new IE subtype structure is as follows. As The new IE subtype structure is as follows. As explained in
explained in [RFC8137] the length of the Sub-Type Content can be [RFC8137] the length of the Sub-Type Content can be calculated from
calculated from the container, so no length information is necessary. the container, so no length information is necessary.
1 2 3 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TBD-XXX |R|P| res | proxy prio | rank priority | | TBD-XXX |R|P| res | proxy prio | rank priority |
+-+-+-+-+-+-+-+-+-+-------------+-------------+-----------------+ +-+-+-+-+-+-+-+-+-+-------------+-------------+-----------------+
| pan priority | | | pan priority | |
+---------------+ + +---------------+ +
| Join Proxy lower-64 | | Join Proxy lower-64 |
+ (present if P=1) + + (present if P=1) +
skipping to change at page 4, line 36 skipping to change at page 4, line 31
+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+ +
| network ID | | network ID |
+ variable length, up to 16 bytes + + variable length, up to 16 bytes +
~ ~ ~ ~
+ + + +
| | | |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
proxy priority Lower value indicates willing to act as a Join Proxy proxy priority this field indicates the willingness to act as join
as described in [I-D.ietf-6tisch-minimal-security]. Values range proxy. Lower value indicates willing to act as a Join Proxy as
0 (most willing) to 0x7e (least willing). A priority of 0x7f described in [I-D.ietf-6tisch-minimal-security]. Values range 0
(most willing) to 0x7e (least willing). A priority of 0x7f
indicates that the announcer should never be considered as a indicates that the announcer should never be considered as a
viable enrollment proxy. Only unenrolled pledges look at this viable enrollment proxy. Only unenrolled pledges look at this
value. value.
pan priority the pan priority is a value set by the DODAG root to pan priority the pan priority is a value set by the DODAG root to
indicate the relative priority of this LLN compared to those with indicate the relative priority of this LLN compared to those with
different PANIDs. This value may be used as part of the different PANIDs. This value may be used as part of the
enrollment priority, but typically is used by devices which have enrollment priority, but typically is used by devices which have
already enrolled, and need to determine which PAN to pick. already enrolled, and need to determine which PAN to pick.
Unenrolled pledges MAY consider this value when selecting a PAN to Unenrolled pledges MAY consider this value when selecting a PAN to
skipping to change at page 5, line 26 skipping to change at page 5, line 20
unicast Router Solicitation messages. unicast Router Solicitation messages.
P if the Proxy Address P-flag is set, then the lower 64-bits of the P if the Proxy Address P-flag is set, then the lower 64-bits of the
Join Proxy's Link Layer address follows the network ID. If the Join Proxy's Link Layer address follows the network ID. If the
Proxy Address bit is not set, then the Link Layer address of the Proxy Address bit is not set, then the Link Layer address of the
Join Proxy is identical to the Layer-2 8-byte address used to Join Proxy is identical to the Layer-2 8-byte address used to
originate this enhanced beacon. In either case, the layer-2 originate this enhanced beacon. In either case, the layer-2
address of any IPv6 traffic to the originator of this beacon may address of any IPv6 traffic to the originator of this beacon may
use the layer-2 address which was used to originate the beacon. use the layer-2 address which was used to originate the beacon.
join-proxy lower-64 if the P-flag bit is set, then 64 bits (8 bytes) join-proxy interface ID if the P bit is set, then 64 bits (8 bytes)
of address are present. The Link Local address of the Join Proxy of address are present. This field provides the suffix of the
is fe80 (as for any Link Local address), and the bits given in Link-Local address of the Join Proxy. The associated prefix is
this field. well-known as fe80::/64.
network ID this is an variable length field, up to 16-bytes in size network ID this is an variable length field, up to 16-bytes in size
that uniquely identifies this network, potentially among many that uniquely identifies this network, potentially among many
networks that are operating in the same frequencies in overlapping networks that are operating in the same frequencies in overlapping
physical space. The length of this field can be calculated as physical space. The length of this field can be calculated as
being whatever is left in the Information Element. being whatever is left in the Information Element.
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
skipping to change at page 6, line 22 skipping to change at page 6, line 19
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
ID to map out the extend of the mesh network. ID to map out the extend of the mesh network.
5. IANA Considerations 5. IANA Considerations
Allocate a new number TBD-XXX from Registry IETF IE Sub-type ID. Allocate a new number TBD-XXX from Registry IETF IE Sub-type ID.
This entry should be called 6tisch-Join-Info. This entry should be called 6tisch-Join-Info, and should refer to
this document.
6. Acknowledgements 6. Acknowledgements
Thomas Watteyne provided extensive editorial comments on the Thomas Watteyne provided extensive editorial comments on the
document. document.
7. References 7. References
7.1. Normative References 7.1. Normative References
[BCP14] 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>.
[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", draft-ietf-6tisch-architecture-20 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-26 (work
in progress), March 2019. in progress), August 2019.
[I-D.ietf-6tisch-minimal-security] [I-D.ietf-6tisch-minimal-security]
Vucinic, M., Simon, J., Pister, K., and M. Richardson, Vucinic, M., Simon, J., Pister, K., and M. Richardson,
"Minimal Security Framework for 6TiSCH", draft-ietf- "Minimal Security Framework for 6TiSCH", draft-ietf-
6tisch-minimal-security-09 (work in progress), November 6tisch-minimal-security-12 (work in progress), July 2019.
2018.
[ieee802154] [ieee802154]
IEEE Standard, ., "802.15.4-2015 - IEEE Standard for Low- IEEE Standard, ., "802.15.4-2015 - IEEE Standard for Low-
Rate Wireless Personal Area Networks (WPANs)", 2015, Rate Wireless Personal Area Networks (WPANs)", 2015,
<http://standards.ieee.org/findstds/ <http://standards.ieee.org/findstds/
standard/802.15.4-2015.html>. standard/802.15.4-2015.html>.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
 End of changes. 15 change blocks. 
35 lines changed or deleted 34 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/