Hello, Based on the discussion in the ANIMA WG last week, I would like to proceed with the discussion on the author's proposal to split the current BRSKI-AE draft (https://datatracker.ietf.org/doc/html/draft-ietf-anima-brski-async-enroll-03) to separate the contained use cases as they have developed differently. We did not finish the discussion during the meeting during lack of time, but for the way forward I would like to ask for support from the chairs to find the decision. I included this question also as open issue in the ANIMA github (https://github.com/anima-wg/anima-brski-async-enroll/issues/19)
- Use Case 1 targets the definition of requirements for a communication architecture using the existing BRSKI components and call model (pledge-initiator-mode, formerly PULL) to enable the use of alternative enrollment protocols for certificate enrollment (voucher handling untouched). - Use Case 2 targets the specification of a reversed call model (pledge-responder-mode, formerly PUSH) in which the pledge has no or only limited connectivity to a registrar or cannot initiate requests to a registrar. To facilitate the interaction between pledge and registrar, the registrar-agent component is established. The interaction between pledge and registrar-agent results in new or enhanced data objects (voucher-request-trigger, voucher-request, voucher, enrollment-request-trigger, enrollment-request). Exchanges between registrar-agent and registrar follows BRSKI (RFC8995) and EST (RFC7030), with the enhanced objects. Declaration of conformity to "AE" is difficult, as the use cases have developed in different directions. Therefore the proposal to split the draft into two separate documents for use case 1 and use case 2. We may also discuss, what the target for each document would be (informational / standard RFC). If the WG is in favor of the split, the expectation would be that the resulting document would proceed as WG documents. Please let us know what you think. Best regards Steffen -- Steffen Fries Siemens AG T RDA CST
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
