Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

link to Fairhair consortia and split history #69

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

link to Fairhair consortia and split history #69

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ea794f4
link to Fairhair consortia
mcr Feb 10, 2025
06509ba
insert two new section headers splitting motification from actual cha…
mcr Feb 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion draft-ietf-anima-rfc8366bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -365,14 +371,16 @@ 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_.

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.
Expand All @@ -390,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.

Expand Down
Loading