Hi Michael, hi Eliot, > Eliot Lear <[email protected]> wrote: > > I think we had a lengthy conversation about BRSKI next steps, and that > we > > should expect to spend some time on this in ANIMA. I think I count at > least > > four drafts that are worth considering, and Michael might have more in > mind: > > > * Draft-vanderstock-anima-constrained-join-proxy > > * Draft-lear-eap-teap-brski > > * Draft-ietf-6tisch-{…} > > > * Draft-fries-anima-brski-async-enroll > {Eliot: Does this document include Oskar's requirements?} > > Additional documents that call on BRSKI: > > * draft-richardson-anima-smarkaklink (formerly > draft-richardson-anima-smartpledge) > -> I have revised slides, and I walk to talka bout them. > I believe that it solves draft-fries-anima-brski-async-enroll as well, > but I haven't read the entire document yet. I just read across draft-richardson-anima-smarkaklink and to my understanding it focuses on the voucher exchange in situations where the domain registrar is only temporary available. The voucher exchange is currently only touched in draft-fries-anima-brski-async-enroll for the voucher exchange, while the main focus is on the certification request/response exchange. It is based on a self-contained object binding the initial pledge authentication to the certification request allowing to perform the authorization of the certification request in a different component than a local domain registrar. In that aspect it has a different scope than draft-richardson-anima-smarkaklink.
Best regards Steffen > > * draft-reddy-dprive-bootstrap-dns-server > * draft-boucadair-dots-server-discovery > --> some details are still TBD. > > -- > Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 > IoT consulting =- _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
