In case anyone’s interested in spending the weekend hacking together some 
(rough) code against some of the proposed DKIM2 specs to see what works and 
expose potential issues, a few folks will be gathering in Montreal during the 
IETF 124 Hackathon.

Here’s the information that can also be found on the hackathon wiki:

——
DKIM2

  *   Champions
     *   Allen Robinson ([email protected]<mailto:[email protected]>)
     *   Bron Gondwana ([email protected]<mailto:[email protected]>)
     *   John Levine ([email protected]<mailto:[email protected]>)
     *   Richard Clayton 
([email protected]<mailto:[email protected]>) [Remote]
     *   Wei Chuang ([email protected]<mailto:[email protected]>) [Remote]
  *

  *
Project Info
To build multiple DKIM2 implementations creating and validating signatures on 
flat file messages shared through the Github repository. We’ve decided that 
SMTP transaction support is out of scope for this first hackathon activity. We 
hope to have a small handful of common scenarios to cover during testing. The 
goal is to just validate assumptions being made in the design phase and try to 
surface any gaps.
  *

  *
Participation Details
     *   Chatroom: 
https://zulip.ietf.org/#narrow/channel/366-dkim/topic/ietf-124-hackathon/
     *   Video / Voice: https://meet.google.com/sbv-rjxh-vaq
     *   GitHub Repo: https://github.com/dkim2wg/interop
  *

  *
Project Files
     *   https://datatracker.ietf.org/wg/dkim/documents/
     *   https://datatracker.ietf.org/doc/draft-ietf-dkim-dkim2-motivation/
     *   https://datatracker.ietf.org/doc/draft-gondwana-dkim2-header/
     *   https://datatracker.ietf.org/doc/draft-clayton-dkim2-spec/
     *   https://www.cl.cam.ac.uk/~rnc1/draft-clayton-dkim2-spec.html

Code and samples at https://github.com/dkim2wg/interop

——



--

J. Trent Adams

Director, Ecosystem Security

Proofpoint



[email protected]

https://www.linkedin.com/in/jtrentadams


_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to