I've included selections and test cases for supporting Ed25519. My reasoning for only including Ed25519 and not Ed448 is that the later requires inclusion of support for cSHAKE XOFs. I did start writing test cases and requirements for cSHAKE, but if we were to include that, it would only be a stop-gap measure. It's best to include support for the full SHA-3 family of hash functions in one go rather than to implement a piece-meal approach. This should be left to a future version of the NDcPP.
I have discussed this approach with @dundiddat, and we are both in agreement that this would be the best way forward.
I've included selections and test cases for supporting Ed25519. My reasoning for only including Ed25519 and not Ed448 is that the later requires inclusion of support for cSHAKE XOFs. I did start writing test cases and requirements for cSHAKE, but if we were to include that, it would only be a stop-gap measure. It's best to include support for the full SHA-3 family of hash functions in one go rather than to implement a piece-meal approach. This should be left to a future version of the NDcPP.
I have discussed this approach with @dundiddat, and we are both in agreement that this would be the best way forward.