Re: [Cfrg] Requesting removal of CFRG co-chair

[Stephen Farrell <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 12/24/2013 02:15 AM, Tao Effect wrote:
> Here's one from Stephen Farrell, it can be summarized entirely
> like so: "Oh FFS. Please cut the crap."
> 
> Here's one from John Bradley: "+1 Stephen's comment"
> 
> Some substance, gentlemen, please?

So I'm willing to bet that you don't know that the entire IAB
met with Kevin to review the CFRG in Vancouver, as is commonly
done with one IRTF RG each IETF meeting. Its quite reasonable
that level of detail is not common knowledge but it is not
reasonable for what might be a substantive discussion about
how CFRG ought deal with snowdonia to be turned into a
kindergarten side-show based on apparently total ignorance as
to how the IRTF and IETF actually do business.

If you (and others who've very recently turned up on this list)
actually care about pervasive monitoring, you should desist
from this kind of nonsense and think more about how to mitigate
the problem.  Or at the very least, ask questions about how things
are, and don't start off by making stupid insinuations. The
entire discussion calling for Kevin to stand down or be removed
is IMO just a distraction from what ought be a real debate on
this list.

That real debate would consider how to more quickly spot that
the ECC DBRG reports were worth serious consideration, how to
deal with nothing-up-my-sleeve parameters, and how to deal with
a future where NIST are no longer the gold-standard for vendors
of important systems and we'll need to have some way to deal
with the likes of 25519. And perhaps whether the status-quo
dividing line between CFRG and the IETF is correctly drawn
at ciphers and modes of operation.

The guilt-by-association drama that we've been seeing is
entirely getting in the way of that much more important debate.

S.

PS: Yes, my language above is immoderate. Frankly, I am quite
pissed off that this side-show is distracting from more real
progress on mitigating pervasive monitoring.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQEcBAEBAgAGBQJSuPMFAAoJEC88hzaAX42ieAcIALq8+fdTFHI7AtOAlGc/DsLE
5BMMi2rbzZvEfxKLPzgYjkBycsDorz7FPNwRjC8rs8Zy3v/pjKHuijyOAaghlRHs
cuSdYukPIVk4HINhOnGi5rIlfQW+kJuBJ2Gv3VMD+ux5Bvm2yu5Bwt78fY0r3fT2
Jq7hxC3PO5syTFFLAtKWrFr9Zc3gh4k0pJ5vJUU782tq4VgGlle3S+5ZfclwVd9J
88PMHhTPH3L0xdmh7PMDaWso0RvXok1yOucgSFEMaNSdlFeN1u081Gfuol18qI1f
4oLSwlzh9F+1MewGJD4dbiMPlYxB/WA/W4giCfTr3kZ7oSQS/tj8xDiOdwJl4iE=
=S0nA
-----END PGP SIGNATURE-----