> Servers and peers MUST follow the guidance provided in > [I-D.ietf-lamps-rfc7030-csrattrs] when creating the CSR-Attributes
https://www.ietf.org/archive/id/draft-ietf-lamps-rfc7030-csrattrs-06.html#name-alternative-use-of-csr-temp ( https://youtu.be/biGtfqj7zgM?t=1640 ) describes a new, simpler way to to CSR Attributes, basically with a fill-in-the-blanks CSR. Doing ONLY this method would seem very attractive for protocols which might be greenfields: that is no implementations out there yet. This question to the group is whether or not there are any RFC7170 implementations ("Peers" or servers) which currently implement this at all, and if not, then would the group like to recommend only using this newer, simpler method? [(b) - since the CSRattrs document is normatively referenced, additional review would be very welcome and very timely. I expect to put out an 07 by next week with some ASN.1 editorial fixes] -- Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
