Re: [Cfrg] malicious DH base points [was Re: should the CFRG really strive for consensus?]

On 01/01/15 17:14, Christoph Anton Mitterer wrote:
> On Thu, 2015-01-01 at 13:39 +0100, Adam Back wrote: 
>> Seems like on
>> topic and to the point, not spam.
> plus: it seems kinda dangerous to me, if certain topics are more or
> less... well not forbidden, but at least "moderated to silence".
> 
> CFRG should be really open, even if this includes more wood and less
> trees,... trust is very important and if people feel that some
> topics/questions/concerns might have been suppressed, CFRG will have the
> same problems as NIST.

Maybe a little more explanation is warranted then. Dan's mail
accused someone of bad faith by saying that that person did
thing x "in the guise" of doing thing y. That is always
inappropriate no matter what provocation and no matter who
says it. By itself that is sufficient to call out the message
as inappropriate for any IETF or IRTF list. And that is why
I agree with the chairs on this.

For me, it's just about appropriate list behaviour that is
more likely to result in the RG making sound technical choices
in a useful time-frame and is nothing to do with silencing
anyone. Inappropriate list behaviour simply makes it much
harder to get done.

As I said before Dan is by no means the only one who's
strayed beyond what's acceptable on this topic by my
reading. But I hope the group put this behind us all and
move on to at least finish up the work on the 128 bit
work factor key agreement topic in the very near future.

>From my pov I think that work is 99% done and should be easy
to finish up, based on the assumption that there's no
remaining security difference, nor significant performance
difference and there is a reasonable amount of running
code for one set of options. It's that kind of discussion
and not who makes what point for what reason that is
important.

And once that is out of the way then moving on to signatures
and other work factors should be much easier.

So add my voice to those saying: let's just get that part
done now please and where there's no other basis on which
to distinguish, the running code should be fine to go
with.

S.

> 
> 
> Cheers,
> Chris.
> 
> 
> 
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg
> 