[
https://issues.apache.org/jira/browse/JDKIM-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18084288#comment-18084288
]
Felix commented on JDKIM-50:
----------------------------
Firstly, it's nice to see that there is already something happening :)
Regarding the standard: RFC 8463 is a proposed standard. This is the stage in
which most RFCs remain in the standardization process. Note that there are only
125 ["Internet
Standards"|https://www.rfc-editor.org/search/?status=Internet+Standard]. Even
RFC 5321 (SMTP) is only a "Draft Standard". [RFC 7127 (a Best Current
Practice)|https://datatracker.ietf.org/doc/html/rfc7127#section-3.1] states
that "A Proposed Standard specification is stable, has resolved known design
choices, has received significant community review, and appears to enjoy enough
community interest to be considered valuable." What they may be missing is an
implementation, so I would argue that the state as a proposed standard should
encourage people to implement it, not prevent it ;)
> Support for RFC 8463
> --------------------
>
> Key: JDKIM-50
> URL: https://issues.apache.org/jira/browse/JDKIM-50
> Project: James jDKIM
> Issue Type: New Feature
> Reporter: Felix
> Priority: Minor
>
> RFC 8463 mandates that verifiers must support verification of Ed25519 DKIM
> signatures. Additionally, it would be nice if James would also support
> creating Ed25519 DKIM signatures.
>
> If I understand the source code correctly, James currently only supports RSA
> for both.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
