From ea794f4ede3c8367cfb08baabdbadf79d4c5c82e Mon Sep 17 00:00:00 2001 From: Michael Richardson Date: Mon, 10 Feb 2025 11:31:15 -0500 Subject: [PATCH 1/2] link to Fairhair consortia --- draft-ietf-anima-rfc8366bis.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/draft-ietf-anima-rfc8366bis.md b/draft-ietf-anima-rfc8366bis.md index a7c56d2..be64812 100644 --- a/draft-ietf-anima-rfc8366bis.md +++ b/draft-ietf-anima-rfc8366bis.md @@ -108,6 +108,12 @@ informative: author: - org: Wikipedia date: 2018-02 + fairhair: + target: "https://openconnectivity.org/developer/specifications/fairhair/" + title: 'Fairhair Specification' + author: + - org: Open Connectivity Foundation + date: 2019-11-01 --- abstract @@ -372,7 +378,7 @@ Since then the industry has matured significantly, and the in-the-field activity The focus of {{BRSKI}} was onboarding of ISP and Enterprise owned wired routing and switching equipment, with IoT devices being a less important aspect. {{ZERO-TOUCH}} has focused upon onboarding of CPE equipment like cable modems and other larger IoT devices, again with smaller IoT devices being of less import. -Since {{BRSKI}} was published there is now a mature effort to do application-level onboarding of constrained IoT devices defined by The Thread and Fairhair (now OCF) consortia. +Since {{BRSKI}} was published there is now a mature effort to do application-level onboarding of constrained IoT devices defined by The Thread and Fairhair (now OCF) consortia {{fairhair}}. The {{cBRSKI}} document has defined a version of {{BRSKI}} that is useable over constrained 802.15.4 networks using CoAP and DTLS, while {{?I-D.selander-ace-ake-authz}} provides for using CoAP and EDHOC on even more constrained devices with very constrained networks. {{PRM}} has created a new methodology for onboarding that does not depend upon a synchronous connection between the Pledge and the Registrar. From 06509ba317285dc61db308318a56445771a337ef Mon Sep 17 00:00:00 2001 From: Michael Richardson Date: Mon, 10 Feb 2025 11:39:38 -0500 Subject: [PATCH 2/2] insert two new section headers splitting motification from actual changes --- draft-ietf-anima-rfc8366bis.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/draft-ietf-anima-rfc8366bis.md b/draft-ietf-anima-rfc8366bis.md index be64812..e9f1557 100644 --- a/draft-ietf-anima-rfc8366bis.md +++ b/draft-ietf-anima-rfc8366bis.md @@ -371,6 +371,8 @@ Bearer Voucher: # Changes since RFC8366 +## Attempts and motivation to extend RFC8366 + {{?RFC8366}} was published in 2018 during the development of {{BRSKI}}, {{ZERO-TOUCH}} and other work-in-progress efforts. Since then the industry has matured significantly, and the in-the-field activity which this document supports has become known as _onboarding_ rather than _bootstrapping_. @@ -396,6 +398,8 @@ After some discussion, it was determined that the _augment_ mechanism did not wo After significant discussion the decision was made to simply roll all of the needed extensions up into this document as "RFC8366bis". +## Informational Model changes since RFC8366 + This document therefore represents a merge of YANG definitions from {{RFC8366}}, the voucher-request from {{BRSKI}}, and then extensions to each of these from {{cBRSKI}}, {{CLOUD}} and {{PRM}}. There are some difficulties with this approach: this document does not attempt to establish rigorous semantic definitions for how some attributes are to be used, referring normatively instead to the other relevant documents.