Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds

[Scott Kitterman <[e-mail]>]

On June 9, 2017 11:04:00 PM EDT, John Levine <[e-mail]> wrote:
>In article <[e-mail]> you
>write:
>>>Given that we are nowhere close to deciding what elliptic
>algorithm(s)
>>>to add, it seems kind of premature to me.
>>
>>Why would that matter?  This draft just gets rid of the obsolete
>cruft.  It clears the deck for adding a new
>>algorithm, but in no way requires we have that sorted out.
>
>I had the perhaps overoptimistic hope that we could wrap up the new
>algorithm reasonably quickly and update DKIM once rather than twice.
>
>There is a significant cost to each RFC, both in what it costs to
>produce it, and to people's attention in the future.  The more places
>you spread around the spec, the more likely it is that people will
>miss part of it.
>
>If it's going to take us another year to decide which elliptic curve
>to use and whether to add key hashes, then OK, we can push this out
>now, but I hope we can do better than that.

I think it will take awhile.  This particular discussion is the one I thought we'd already had when the group agreed to split this out into a separate draft.

This particular draft is already roughly five years late.

If we don't get something that rips out the obsolete crypto soon, then ARC is either going to have to wait or have a separate crypto specification from DKIM.  I don't see a new protocol with rsa-sha1 512 bits getting approved.  Neither of those options is good.

Scott K