Operational Considerations for BRSKI Registrar
draft-ietf-anima-registrar-considerations-03
| Document | Type |
Expired Internet-Draft
(anima WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Richardson , Thomas Werner , Peter Chunchi Liu | ||
| Last updated | 2026-09-27 (Latest revision 2026-03-26) | ||
| Replaces | draft-richardson-anima-registrar-considerations | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a number of operational modes that a BRSKI Registration Authority (Registrar) may take on. Each mode is defined, and then each mode is given a relevance within an over applicability of what kind of organization the Registrar is deployed into. This document does not change any protocol mechanisms. This document includes operational advice about avoiding unwanted consequences.
Authors
Michael Richardson
Thomas Werner
Peter Chunchi Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)