IEEE 802.15.4 Information Element encapsulation of 6TiSCH Join and Enrollment Information
draft-ietf-6tisch-enrollment-enhanced-beacon-06

Document Type Active Internet-Draft (6tisch WG)
Last updated 2019-11-04
Replaces draft-richardson-6tisch-enrollment-enhanced-beacon
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Pascal Thubert
Shepherd write-up Show (last changed 2019-09-17)
IESG IESG state AD Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to Pascal Thubert <pthubert@cisco.com>
6lo Working Group                                             D. Dujovne
Internet-Draft                                Universidad Diego Portales
Intended status: Standards Track                           M. Richardson
Expires: May 7, 2020                            Sandelman Software Works
                                                       November 04, 2019

   IEEE 802.15.4 Information Element encapsulation of 6TiSCH Join and
                         Enrollment Information
            draft-ietf-6tisch-enrollment-enhanced-beacon-06

Abstract

   In TSCH mode of IEEE STD 802.15.4, 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 May 7, 2020.

Copyright Notice

   Copyright (c) 2019 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
   to this document.  Code Components extracted from this document must

Dujovne & Richardson       Expires May 7, 2020                  [Page 1]
Internet-Draft                IE for ICMPv6                November 2019

   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.  Use of BCP 14 Terminology . . . . . . . . . . . . . . . .   2
     1.2.  Layer-2 Synchronization . . . . . . . . . . . . . . . . .   2
     1.3.  Layer-3 synchronization: IPv6 Router Solicitations and
           Advertisements  . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Definition . . . . . . . . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   4.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   [RFC7554] describes the use of the time-slotted channel hopping
   (TSCH) mode of [ieee802154].  As further detailed in [RFC8180], an
   Enhanced Beacon (EB) is transmitted during a slot designated a
   broadcast slot.

1.1.  Use of BCP 14 Terminology

   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
   [BCP14] [RFC2119] when, and only when, they appear in all capitals,
   as shown here.

   Other terminology can be found in [I-D.ietf-6tisch-architecture] in
   section 2.1.

1.2.  Layer-2 Synchronization

   As explained in section 6 of [RFC8180], the Enhanced Beacon (EB) has
   a number of purposes: synchronization of ASN and Join Metric,
   carrying timeslot template identifier, carrying the channel hopping
   sequence identifier, and indicating the TSCH SlotFrame.

   The EB is used by nodes already part of a TSCH network to annouce its
   existence.  Receiving an EB allows a Joining Node (pledge) to learn

Dujovne & Richardson       Expires May 7, 2020                  [Page 2]
Internet-Draft                IE for ICMPv6                November 2019

   about the network and synchronize to it.  The EB may also be used as
   a means for a node already part of the network to re-synchronize
   [RFC7554].

   There is a limited number of timeslots designated as a broadcast slot
Show full document text