Skip to content
sovm.io

References

Normative

Section titled “Normative”
  • [RFC 2119] — Bradner, S. “Key words for use in RFCs to Indicate Requirement Levels.” BCP 14, RFC 2119.
  • [RFC 8174] — Leiba, B. “Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words.” BCP 14, RFC 8174.
  • [RFC 8949] — Bormann, C., Hoffman, P. “Concise Binary Object Representation (CBOR).” STD 94, RFC 8949. Section 4.2.1 supplies the deterministic encoding.
  • [RFC 9052] — Schaad, J. “CBOR Object Signing and Encryption (COSE): Structures and Process.” STD 96, RFC 9052.
  • [RFC 9053] — Schaad, J. “CBOR Object Signing and Encryption (COSE): Initial Algorithms.” RFC 9053.
  • [RFC 8032] — Josefsson, S., Liusvaara, I. “Edwards-Curve Digital Signature Algorithm (EdDSA).” RFC 8032.
  • [RFC 7748] — Langley, A., Hamburg, M., Turner, S. “Elliptic Curves for Security.” RFC 7748.
  • [RFC 5869] — Krawczyk, H., Eronen, P. “HMAC-based Extract-and-Expand Key Derivation Function (HKDF).” RFC 5869.
  • [RFC 6234] — Eastlake, D., Hansen, T. “US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF).” RFC 6234. Referenced via HKDF-SHA256.
  • BLAKE3 — O’Connor, J., Aumasson, J-P., Neves, S., Wilcox-O’Hearn, Z. “BLAKE3: One function, fast everywhere.”

Informative

Section titled “Informative”
  • [RFC 9420] — Barnes, R., et al. “The Messaging Layer Security (MLS) Protocol.” RFC 9420. Relevant where SOP/1 is deployed.
  • [RFC 9750] — Beurdouche, B., et al. “The Messaging Layer Security (MLS) Architecture.” RFC 9750. The Delivery Service abstraction that the mailbox contract aligns with.
  • [RFC 7250] — Wouters, P., et al. “Using Raw Public Keys in Transport Layer Security (TLS).” RFC 7250. The authentication shape of the default binding profile.
  • [SOP/1] — The Sovereign Object Plane, the layer above this one.

A note on what is not cited

Section titled “A note on what is not cited”

A predecessor mesh synchronization protocol informed this document’s data model, merge algebra and pairing ceremony. It is not cited as a normative reference because it is unpublished, and a public specification cannot depend normatively on a document a reader cannot obtain.

Where SSP/1 departs from that predecessor, the departures and their reasons are listed in limitations.