On Mon, Nov 12, 2018 at 07:16 +0000, Patrick Brunschwig wrote: pbrunschwig approved this pull request. Fine with me. @r10s The Level is an overall concept, whereas the version is the revision of the document.
however, saying "Level 1.1 client" is easier and will be chosen often over "a Level 1 client as specified with revision 1.1" or so ;)
The typical way that i'd expect such a change to happen in a protocol doc with wider adoption is to require support for handling the new crypto primitives (when seen from communications peers) in version X+1, and then mandate generation of the new key types in version X+2.
Perhaps we're small enough and we have a wide enough canvas already that we can just jump ahead, though it makes me slightly nervous. PGPy still doesn't support cv25519 and ed25519, for instance, though perhaps its current stagnation is a warning about that library itself. :(
I'm open to the idea, though -- i definitely like the size improvements we're seeing with the ECC keys.
This change should not be merged without updates to the appendix, though -- the example keys and messages should all be re-created using 25519.