On Tuesday, March 29, 2016, Hal Murray <[email protected]> wrote:
> > [email protected] <javascript:;> said: > > We have to be careful here. I agree that at least some cipher suites > should > > be specified as a minimal subset in the draft but we also need > flexibility > > as new ciphers come out and older ones are found to be vunerable. > Otherwise > > we will need to create new RFC's to update the RFC for either of these > > scenarios. I'm sure that there are other implementations that have run > into > > this problem and we should see how they handle it. > > Is there any group in the IETF keeping track of which cyphers are > good/weak? > > I think the CFRG is the right place to go. If not, I'm sure they can point to the right place. https://datatracker.ietf.org/rg/cfrg/charter/ > It would be nice if there were something like the assigned numbers role, > but > this is more complicated that just assigning and keeping track of what has > been > Thanks. Sharon -- Sharon Goldberg Computer Science, Boston University http://www.cs.bu.edu/~goldbe
_______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
