Anima Workgroup RFCs

Browse Anima Workgroup RFCs by Number

RFC8366 - A Voucher Artifact for Bootstrapping Protocols
This document defines a strategy to securely assign a pledge to an
owner using an artifact signed, directly or indirectly, by the
pledge's manufacturer. This artifact is known as a "voucher". This document defines an artifact format as a YANG-defined JSON
document that has been signed using a Cryptographic Message Syntax
(CMS) structure. Other YANG-derived formats are possible. The
voucher artifact is normally generated by the pledge's manufacturer
(i.e., the Manufacturer Authorized Signing Authority (MASA)). This document only defines the voucher artifact, leaving it to other
documents to describe specialized protocols for accessing it.
RFC8368 - Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)
Operations, Administration, and Maintenance (OAM), as per BCP 161, for data networks is often subject to the problem of circular dependencies when relying on connectivity provided by the network to be managed for the OAM purposes.
Provisioning while bringing up devices and networks tends to be more difficult to automate than service provisioning later on. Changes in core network functions impacting reachability cannot be automated because of ongoing connectivity requirements for the OAM equipment itself, and widely used OAM protocols are not secure enough to be carried across the network without security concerns.
This document describes how to integrate OAM processes with an autonomic control plane in order to provide stable and secure connectivity for those OAM processes. This connectivity is not subject to the aforementioned circular dependencies.