Re: [secdir] a few new algs and a bunch of deprecation

I'm following Curve25519/Ed25519 use in IETF protocols and is
interested in helping that effort.  It seems the intersection between
this putative WG and existing WGs needs to be carefully explained
though, it isn't clear to me how it could be done.  Isn't deprecating
crypto parts of a protocol up to each protocol community to think
about?  We've seen with TLS, OpenPGP, Secure Shell and PKIX that
adding Curve25519/Ed25519 is highly protocol specific and requires
domain knowledge.

/Simon

> 
> Hiya,
> 
> At the secdir lunch we spoke about needing a bit of organisation
> around adding new curves and about deprecating some old algs (e.g.
> sha1). There's a scattered set of stuff that'll need doing some
> of which is in progress (e.g. drafts allocating OIDs for new
> curves), others of which may not yet be. One possibility would be
> to try do this as a WG with a charter that tightly defines which
> new things can be added but allows for deprecating anything
> that should be deprecated. (The putative WG here would not I
> think tackle items where we have a current WG active, e.g. TLS
> can handle defining codepoints for TLS.)
> 
> As a separate but related thing, Alexey said he'd create a cfrg
> wiki page where folks could add the names of drafts that are
> defining things related to new curves. That might feed into the
> positive parts of chartering.
> 
> FWIW, if this is something people supported and found useful,
> Kathleen and I are happy to help it happen. Next step would likely
> be to send a mail like this to saag then if nothing bad happens, to
> start a mailing list for this and see if there's enough energy
> to get stuff going. (If there is, I doubt a BoF would be needed.)
> 
> Thoughts?
> 
> S.
> 
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
> wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview