IEEE802.15.4 Informational Element encapsulation of 6tisch Join and Enrollment Information
draft-ietf-6tisch-enrollment-enhanced-beacon-00
6lo Working Group D. Dujovne
Internet-Draft Universidad Diego Portales
Intended status: Informational M. Richardson
Expires: January 18, 2019 Sandelman Software Works
July 17, 2018
IEEE802.15.4 Informational Element encapsulation of 6tisch Join and
Enrollment Information
draft-ietf-6tisch-enrollment-enhanced-beacon-00
Abstract
In TSCH mode of IEEE802.15.4, as described by [RFC8180],
opportunities for broadcasts are limited to specific times and
specific channels. Nodes in a TSCH network typically frequently send
Enhanced Beacon (EB) frames to announce the presence of the network.
This document provides a mechanism by which small details critical
for new nodes (pledges) and long sleeping nodes may be carried within
the Enhanced Beacon.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 18, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Dujovne & Richardson Expires January 18, 2019 [Page 1]
Internet-Draft IE for ICMPv6 July 2018
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Layer-2 Synchronization . . . . . . . . . . . . . . . . . 3
1.3. Layer-3 synchronization IPv6 Router solicitations and
advertisements . . . . . . . . . . . . . . . . . . . . . 3
2. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 4
2.1. Protocol Example . . . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5
4. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Change history . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
[RFC7554] describes the use of the time-slotted channel hopping
(TSCH) mode of [ieee802154]. As further details in [RFC8180], an
Enhanced Beacon is transmitted during a slot designated a broadcast
slot.
EDNOTE: Explain why broadcasts are rare, and why we need them. What
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",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
[RFC2119] and indicate requirement levels for compliant STuPiD
implementations.
Dujovne & Richardson Expires January 18, 2019 [Page 2]
Internet-Draft IE for ICMPv6 July 2018
1.2. Layer-2 Synchronization
As explained in section 6 of [RFC8180], the Enhanced Beacon has a
number of purposes: synchronization of ASN and Join Metric, timeslot
template identifier, the channel hopping sequence identifier, TSCH
Show full document text