SDMP

Versioning

Updates to the specifications will follow Semantic Versioning 2.0.0.

Note:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

Overview

• 0.x: Development stage. In progress!
• 1.0: Stable and verified as usable in multiple languages.
• 2.0: Changes after real-world users play with it.

Details

0.x In progress!

During the development stage, backwards compatability between versions is not guaranteed.

0.12 Completed!

• Make the crypto and hashing specs clear and complete.
• Make the container object clear, and list all extensions.
• List all extensions and make them standardized.
• The session key exchange should be clear and complete.
• Roadmap/Milestones.
• Contributing guidelines.
• Discussion of why this protocol and not some other existing protocol.

0.13

• Crypto specs have been written and validated as usable in multiple languages.
• Crypto specs need to be clear enough to be implemented in any language.
• Possible defense of RSA and Diffie-Hellman?

0.14

• TCP implementation has been finished.
• Other possible implementations.

0.15

• Additional polish of the website.
• Possibly getting a professional designer to help.
• Any other final issues in prep for 1.0 release.

1.0

This version will have been verified as usable by a command line implementation, and will have had several people read through it to make sure it is reasonable. However, it will not have been through much "real world" user testing.

• Containers and all schemas are clearly specified.
• Public/private key pairs are well defined.
• How to establish session keys is well defined.
• Basic TCP specs are functional, but may not be optimized for efficiency.
• Example modules and libraries will have been written in at least a few common programming languages.

1.1

After the 1.0 release, work is planned for a GUI which will make the protocol easier to use for normal people: things like finding users and verifying keys.

The 1.1 release will include changes that are proposed during the development of various applications.

Changes between 1.0 and 1.1 will be non-breaking.

1.2+

After the 1.1 release, additional releases may be made if there is enough request for them, but these releases will all be non-breaking.

2.0

After many applications have been developed, a request for comments will be made, asking for more detailed discussion on limitations and problems encountered with the protocol.

Changes to the protocol will be proposed and reviewed, and a new version of the protocol will be released.

Although attempts will be made for backwards compatability, changes between 1.x and 2.0 may be breaking.