Skip to main content

Operational Considerations for BRSKI Registrar
draft-richardson-anima-registrar-considerations-06

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Michael Richardson , Wei Pan
Last updated 2023-05-11 (Latest revision 2022-11-07)
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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
Wei Pan

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)