draft-ietf-6tisch-enrollment-enhanced-beacon-11.txt   draft-ietf-6tisch-enrollment-enhanced-beacon-12.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: 17 August 2020 Sandelman Software Works Expires: 18 August 2020 Sandelman Software Works
14 February 2020 15 February 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-11 draft-ietf-6tisch-enrollment-enhanced-beacon-12
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 transmit Enhanced Beacon (EB) frames to network typically frequently transmit 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 information critical for new nodes (pledges) and mechanism by which information 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 17 August 2020. This Internet-Draft will expire on 18 August 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 49 skipping to change at page 2, line 49
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.
The EB is used by nodes already part of a TSCH network to announce An EB announces the existence of a TSCH network, and of the nodes
their existence. Receiving an EB allows a Joining Node (pledge) to already joined to that network. Receiving an EB allows a Joining
learn about the network and synchronize to it. The EB may also be Node (pledge) to learn about the network and synchronize to it.
used as a means for a node already part of the network to re-
synchronize [RFC7554]. The EB may also be used as a means for a node already part of the
network to re-synchronize [RFC7554].
There are a limited number of timeslots designated as broadcast slots There are a limited number of timeslots designated as broadcast slots
by each router in the network. Considering 10ms slots and a slot- by each router in the network. Considering 10ms slots and a slot-
frame length of 100, these slots are rare and could result in only 1 frame length of 100, these slots are rare and could result in only 1
slot per second for broadcasts, which needs to be used for the slot per second for broadcasts, which needs to be used for the
beacon. Additional broadcasts for Router Advertisements, or Neighbor beacon. Additional broadcasts for Router Advertisements, or Neighbor
Discovery could even more scarce. Discovery could even more scarce.
1.3. Layer-3 synchronization: IPv6 Router Solicitations and 1.3. Layer-3 synchronization: IPv6 Router Solicitations and
Advertisements Advertisements
skipping to change at page 3, line 47 skipping to change at page 3, line 48
2. It may require many seconds of on-time before a new pledge 2. It may require many seconds of on-time before a new pledge
receives a Router Advertisement (RA) that it can use. receives a Router Advertisement (RA) that it can use.
3. A new pledge may have to receive many Enhanced Beacons (EB) 3. A new pledge may have to receive many Enhanced Beacons (EB)
before it can pick an appropriate network and/or closest Join before it can pick an appropriate network and/or closest Join
Assistant to attach to. If it must remain in the receive state Assistant to attach to. If it must remain in the receive state
for an RA as well as find the Enhanced Beacon (EB), then the for an RA as well as find the Enhanced Beacon (EB), then the
process may take a very long time. process may take a very long time.
This document defines a new IETF IE subtype to provide join and This document defines a new IETF Information Element (IE) subtype to
enrollment information to prospective pledges in a more efficient provide join and enrollment information to prospective pledges in a
way. more efficient way.
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. allocates a new subtype.
The new IE subtype structure is as follows. As explained in The new IE subtype structure is as follows. As explained in
[RFC8137] the length of the Sub-Type Content can be calculated from [RFC8137] the length of the Sub-Type Content can be calculated from
the container, so no length information is necessary. the container, so no length information is necessary.
 End of changes. 5 change blocks. 
12 lines changed or deleted 13 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/