Version: v0.0.16 Pre-Draft Date: August 11, 2022 License: CC BY 4.0 Author: Dave Huseby dave@cryptid.tech Reference Implementation: https://github.com/cryptidtech/cde Copyright: (c) CryptID Technologies, Inc. 2021--2022 This cryptographic data encoding (CDE) proposal is for encoding of cryptographic data into a self-describing format using a method that simplifies both ASCII (base 64) and binary (base 2) serialization/deserialization. It has some additional novel properties (e.g. easy visual inspection of ASCII, simple parsing in binary) that makes it especially useful for encoding cryptographic data. The primary, and most important, goal is that the ASCII representation of every construct begins with easy-to-learn characters associated with the different classes (e.g. cryptographic keys) and sub-classes (e.g. Ed25519 keys) to aid in debugging and visual inspection. Since most cryptographic constructs have three levels of classification (i.e. key -> algorithm -> variant/bit length) the type tags for CDE have three layers of classification: class, sub-class, and sub-sub-class. The secondary goal is that the binary representation of every construct has an easily parsed type tag to simplify serialization and deserializtion.

Version: v0.0.3 Pre-Draft Date: July 7, 2021 License: CC BY 4.0 Author: Dave Huseby dwh@trustframe.com Copyright: (c) TrustFrame, Inc. 2021 Data Expressions There are only two forms that these expressions may take: regular and type-define. The regular form is an s-expression: (<label> <data>)

By David Huseby This document is licensed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. This specification documents the new protocol Git uses when interacting with cryptographic signing and verification tools. The protocol takes is inspired by the Assuan Protocol used by GPG to link its component executables together.