Technical Summary
This document provides a series of examples that align RFC6553
with the recent changes in processing described in RFC8200. In other
words, the examples are intended to be normative explanation of the
results of executing that language.
Existing deployed networks may experience a flag day as a result of
some of the suggested changes, and this document provides a way
to mitigate such an occurrence.
Working Group Summary
There was clear consensus in the ROLL WG that this document was
needed. The extensive subject, involving many details, has led to
lengthy discussions about terminology, and coverage of all cases.
This document already went through IESG Evaluation, and -31 was
approved. It was later removed from the RFC Editor's Queue for the
WG to address a couple of issues, mostly related to
draft-ietf-roll-unaware-leaves and MOP 7. The WG was very involved
in the discussion. The latest version (-42) went through a new IETF LC.
Document Quality
The document is of special value to the the 6tisch WG.
There are no known implementations by manufacturers, but
comments have been incorporated from people who needed to
address a subset of the cases discussed in the document.
The drafts ietf-anima-bootstrapping-keyinfra and
ietf-6tisch-dtsecurity-secure-join rely on the cases discussed
in this document.
Personnel
Document Shepherd is Peter van der Stok
Responsible Area Director is Alvaro Retana