Hello all, In the context of the AD review of BRSKI-PRM, we got a comment to provide a separate section on operational considerations focusing on the Registrar-Agent, which was introduced as new component in BRSKI to facilitate situations in which the pledge operates as server component. For the common components in BRSKI, the registrar and the MASA we already discussed operational considerations in two drafts , which are meanwhile expired: Operational considerations for
* Registrar: https://datatracker.ietf.org/doc/draft-richardson-anima-registrar-considerations/ * MASA: https://datatracker.ietf.org/doc/draft-richardson-anima-masa-considerations/ As we meanwhile have several different enhancements to BRSKI with PRM, AE, constraint BRSKI, ... it would be good to bring these documents back to life to capture operational considerations applicable to all variants. To do so, I would propose to provide feedback to the existing (yet expired) drafts to provide an updated version, which can be used to ask WG for adoption. Any thoughts? Best regards Steffen -- Steffen Fries
_______________________________________________ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
