Standards
What Atlas does with each standard.
One row per document, and one of four relationships per row. Implements means Atlas speaks it on the wire or produces its format. Follows means Atlas uses its classification or vocabulary without implementing the protocol. Borrows the idea means the mechanism is ours and the insight is the document’s. Departs from means Atlas deliberately does it differently, and the design page says why. The list is generated from one manifest and every link on it is checked on every build.
| Standard | Defines | Relationship | In Atlas | Where |
|---|---|---|---|---|
| Noise Protocol Framework Noise IK handshake pattern | A framework of authenticated key-agreement handshakes built from Diffie–Hellman, a hash and an AEAD. | Implements | Every session is a Noise IK handshake; the primitive set behind it is a build-time choice. | Cryptography |
| RFC 7748 Elliptic Curves for Security (X25519) | Defines the X25519 and X448 Diffie–Hellman functions. | Implements | Key agreement in every handshake. | Cryptography |
| RFC 8439 ChaCha20 and Poly1305 for IETF Protocols | The ChaCha20 stream cipher and Poly1305 authenticator as an AEAD. | Implements | Authenticated encryption of every datagram and of the end-to-end seal. | Cryptography |
| RFC 7693 The BLAKE2 Cryptographic Hash | BLAKE2b and BLAKE2s hash and message authentication functions. | Implements | The hash in the handshake and in key derivation. | Cryptography |
| RFC 8489 Session Traversal Utilities for NAT (STUN) | A protocol for learning a host's reflexive transport address through a NAT. | Implements | Netcheck classifies every link by STUN against the relay's two addresses. | Netcheck |
| RFC 4787 NAT Behavioral Requirements for Unicast UDP | The vocabulary of NAT mapping and filtering behaviours. | Follows | Per-link NAT classification is reported in these terms. | Netcheck |
| RFC 8445 Interactive Connectivity Establishment (ICE) | Candidate gathering, connectivity checks and nomination for NAT traversal. | Departs from | Candidates and checks are exchanged through the mesh's own rendezvous; endpoint-dependent NAT pairs stay relayed instead of attempting port prediction. | Hard NAT pairs · Hole punching |
| RFC 2474 Differentiated Services Field (DSCP) | The six-bit code point in the IP header that marks a packet's class. | Follows | Classification reads CS6/CS7, EF, AF41 and CS1 first. | The six classes |
| RFC 3758 SCTP Partial Reliability Extension | Per-message reliability, including a timed service that abandons a message when its lifetime expires. | Borrows the idea | Deadline delivery is timed reliability per packet, with the budget set per class or derived from the bond's own round trips. | Lineage · Tempo |
| RFC 7496 Additional Policies for PR-SCTP | Limited-retransmission and priority policies for partially reliable delivery. | Borrows the idea | Backlog shedding admits the newcomer and abandons lower-priority backlog, counted per class. | Lineage · Triage |
| RFC 8655 Deterministic Networking Architecture | Bounded latency and loss through resource allocation, packet replication and elimination, and explicit routes. | Borrows the idea | Replication, elimination and explicit routes are borrowed; per-flow reservation is deliberately not. | Lineage · No reservation |
| IEEE 802.1 TSN Time-Sensitive Networking | Layer-2 bounded-latency mechanisms that DetNet extends to IP. | Departs from | Atlas works above the bearers and does not schedule the medium; diversity across bearers is its mechanism. | No reservation |
| RFC 2328 OSPF Version 2 | Link-state routing: flood what you know, hold the whole database, compute shortest paths locally. | Borrows the idea | The mesh floods link-state adverts and runs Dijkstra on every node; the flood is paced per bearer and carries positions and names. | Control plane |
| RFC 1624 Incremental Internet Checksum Update | Recomputing the Internet checksum after changing a header field, without re-reading the packet. | Implements | The interconnect seam repairs IPv4, TCP and UDP checksums this way when it maps addresses. | Interconnect |
| RFC 8446 TLS 1.3 | Negotiated cipher suites and versions between two endpoints. | Departs from | No negotiation on the wire: one suite and one protocol version across a fleet, by decision. | No negotiation |
| RFC 5424 The Syslog Protocol | Structured event messages for collectors. | Implements | Link, session and configuration events are exported as syslog or CEF. | Telemetry |
| RFC 9116 security.txt | A well-known file that names the security contact and policy of a host. | Implements | Every Nexus Atlas website serves one, pointing at the same disclosure policy. | Disclosure |
| CycloneDX Software Bill of Materials | A standard inventory of the components in a release. | Implements | Every release ships one, and the binaries embed their own dependency manifest. | Supply chain |
| SLSA v1.0 Supply-chain Levels for Software Artifacts | Build provenance levels that tie an artifact to its source and build run. | Implements | Releases carry Level 3 provenance beside keyless signatures. | Supply chain |
| FIPS 140-3 Security Requirements for Cryptographic Modules | Validation of cryptographic modules for US federal and allied procurement. | Departs from | The default build runs the Noise suite above; a validated-module build mode is a labelled certification track. | Certification tracks · No negotiation |
| STANAG 4609 / MISB ST 0601 NATO Digital Motion Imagery and KLV metadata | Full-motion video with per-frame telemetry carried as a KLV metadata track. | Follows | Carried unchanged; the design page states why frame-to-record alignment belongs in the stream, not in the transport. | Alignment |
Missing a document you expected? The contact page reaches the engineers who maintain this list.