[jira] [Commented] (JDKIM-50) Support for RFC 8463

    [ https://issues.apache.org/jira/browse/JDKIM-50?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D180842=
88#comment-18084288 ]=20

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 a=
re only 125 ["Internet Standards"|https://www.rfc-editor.org/search/?status=
=3DInternet+Standard]. Even=C2=A0RFC 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 sta=
ble, has resolved known design choices, has received significant community =
review, and appears to enjoy enough community interest to be considered val=
uable." What they may be missing is an implementation, so I would argue tha=
t 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 DKI=
M signatures. Additionally, it would be nice if James would also support cr=
eating Ed25519 DKIM signatures.
> =C2=A0
> 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)