Htmlized: https://datatracker.ietf.org/doc/html/draft-richardson-enrollment-roadmap-01 diff: https://www.ietf.org/rfcdiff?url2=draft-richardson-enrollment-roadmap-01
I posted an -01 of the enrollment roadmap document. The intro says: There are numerous mechanisms being proposed to solve the problem of securely introducing a new devices into an existing managed network. This document provides an overview of the different mechanisms showing what technologies are common. The document starts with a diagram showing the various components and how they go together to form five enrollment scenarios. The work crosses many groups, but does not fit into any of them. The document might be good as a way to keep track of things, but may not be worth publishing. Yes, could go the wiki way, but I find it significantly less satisfying. In particular I'd like to include guidance on why one process vs another, which I think would be worth preserving. On the other hand, there are sections explaining which documents are of cross-WG interest, and if they have been adopted in any place (or not!!). That's really ephermeral information that doesn't belong in an RFC until it's been resolved. It would also be nice to have a different name than "Transition to Constrained Enrollment" that more accurately reflected the interests of that group of deployers (it includes Lighting/Fairhair, and electricity-AMI/Itron/Cisco.) If there are those who want to review/contribute to it, https://github.com/anima-wg/enrollment-roadmap.git might be the best place to send pull requests. I'm personally not enthralled by using github issues for discussion (I prefer email lists), but I don't object to it. If there is interest in publishing it, my suggestion is to use iot-dir to get some beef into it, and then submit as an AD-sponsored document. Alternatively saag. I think that the document should expand by about 4 pages of discussion, and then sit in stasis for awhile. The most significant change in -01 is that I changed how the boxes around the ascii art diagram are rendered. I hope that it is more readable that way. {If you haven't tried "asciio", I suggest you try it out.} Other than that, more text in the sections. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
