Hi authors, The Fairhair folk would like some clarity on the following statement in Section 3.1.7:
> Functionality to provide generic "configuration" information is > supported. The parsing of this data and any subsequent use of the > data, for example communications with a Network Management System is > out of scope but is expected to occur after bootstrapping enrollment > is complete. Many of us this, but we need to know how to hook in. Specifically we're aiming to provide the address of the resource directory, preferably in a way that is signed by the registrar. Also, we're wondering what effort it would be to move to CBOR for transactions. Eliot
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
