On 31.05.18 20:43, Toerless Eckert wrote: > Thanks, Eliot > > Good point, forgot to ask/mention this point in my previous emails. > > As an ANIMA contributor, i would love for a draft/->RFC like BRSKI to > mention known existing implementations, especially open source, even if just > PoC. > > But i have no idea if and/or how thats seen to be appropriate by IETF > standards. Traditionally i think it was not done, but then again, > with the amount of focus (not to say hype ;-) the IETF does around > open source and hackathons, it almost sounds absurd to me not to mention such > code. > > I am only aware of github.com/cisco/libest, but would love to see > any known code be mentioned. Single sentence with references to > appropriate URLs to those implementations would suffice IMHO. > What do others think/know about BCP in IETF protocol RFC re such mentioned of > known code ?
I don't mind that pointer being listed, though we should *always* check with the code developers before doing so. In this case we can check with them to be sure. The 2nd piece of code is not open source and not by Cisco. Eliot
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
