<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-anima-registrar-considerations" target="https://datatracker.ietf.org/doc/html/draft-ietf-anima-registrar-considerations-03">
   <front>
      <title>Operational Considerations for BRSKI Registrar</title>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>Sandelman Software Works</organization>
      </author>
      <author initials="T." surname="Werner" fullname="Thomas Werner">
         <organization>Siemens AG</organization>
      </author>
      <author initials="P. C." surname="Liu" fullname="Peter Chunchi Liu">
         <organization>Huawei</organization>
      </author>
      <date month="March" day="26" year="2026" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-anima-registrar-considerations-03" />
   
</reference>
