Operational Considerations for BRSKI Registrar
draft-richardson-anima-registrar-considerations-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Michael Richardson , Jie Yang | ||
| Last updated | 2021-01-30 (latest revision 2020-07-29) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-richardson-anima-registrar-considerations-04.txt
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
(mcr+ietf@sandelman.ca)
Jie Yang
(jay.yang@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)