Why standards exist

One shared document replaces thousands of private agreements

ABCDEFNo standardevery pair negotiatesits own agreement6 vendors: 15 agreementsABCDEFdocOne standardeach implements thesame document6 vendors: 6 implementationsno standard4,950one standard100agreements needed among 100 vendors, to scaleA standard turns a web of private agreements into one shared document that anyone can implement.The price is a slow committee: years from first draft to final text. The gain is permissionless interoperability: a new browsercan ship next week without negotiating with every server on the internet.

A standard is a document that independent implementations agree to follow, so strangers can interoperate.

Why standards exist · Going deeper · 1 of 2

The cost of disagreement versus the cost of agreement No standard Standard 5 vendors · 10 bilateral agreements N vendors · N(N-1)/2 connections Spec 5 vendors · 1 document · N connections

The cost of disagreeing

The cost of disagreement is interop failure: a page that renders in one browser only, a USB-C cable that delivers 100 W to one laptop and 5 W to another. Open standards buy permissionless interoperability; closed protocols such as iMessage cannot be implemented by a third party at all.

Why standards exist · Going deeper · 2 of 2

Standards bodies by scope and territory Internet Web platform Industry Domain IETF IANA ICANN RFCs · protocols registries · numbers names · roots WHATWG W3C TC39 (ECMA) HTML · DOM · Fetch SVG · ARIA · WCAG JavaScript ISO / IEC IEEE NIST 27001 · 9001 · C++ 802.3 · 802.11 · 754 FIPS · SP 800-53 Khronos OASIS Unicode Vulkan · WebGPU SAML · MQTT UTF-8 · CLDR Linux Foundation CNCF (Kubernetes, OpenTelemetry) · OpenSSF (sigstore, SLSA) · OpenJS · Hyperledger · LF AI & Data

Who writes which rules

The IETF writes internet protocols (IP, TCP, TLS, HTTP, DNS). W3C and WHATWG split the web platform. IEEE covers Ethernet (802.3), Wi-Fi (802.11) and floating point (754). ISO covers C, C++ and ISO 27001. NIST publishes cryptographic baselines such as AES. ECMA’s TC39 owns JavaScript; the Unicode Consortium owns text.

How internet standards are made

Internet standards: rough consensus and running code

Internet-Draftexpires after 6 monthsWorking-group call2 weeksIETF last call4 weeks, open to allIESG reviewevery block is resolvedtypically 2 to 5 years; HTTP/3 took 6RFCnumbered, never editedRFC 5246TLS 1.2replaced byRFC 8446TLS 1.3a revision is a new document; the old text stays as it wasRFCs publishedover 9,500 since 1969full Internet Standardabout 100“We reject kings, presidents, and voting. We believe in rough consensus and running code.” David Clark, 1992Internet standards are settled by rough consensus and running code, not by votes.Anyone may take part; there is no membership. A draft with two independent implementations that talk to each other carriesmore weight than elegant prose. ISO, by contrast, votes by national body, and WHATWG keeps living documents with no versions.

An RFC is reviewed in the open, published under a number, and never edited afterwards.

How internet standards are made · Going deeper

The IETF document lifecycle from Internet-Draft to published RFC Internet-Draft Working Group WG Last Call IETF Last Call expires 6 mo rough consensus 2-week review 4-week review IESG review RFC Editor DISCUSS · approve number · publish RFC NNNN timeline · 2–5 years end to end

The life of an RFC

Not every RFC is a standard: the status field distinguishes Standards Track, Best Current Practice, Informational, Experimental and Historic. Rough consensus means the chair judges that no unresolved technical objection remains, not that a majority voted. Errata can be filed, but the published text is immutable.

Ambiguity in specs

What a spec leaves open is where systems disagree

MUSTrequired: break it andyou do not conformSHOULDrecommended: deviate onlywith a good reasonMAYoptional: eachimplementer decidesThe JSON specification does not say what a repeated key means. So:{ "a": 1, "a": 2 }parser A keeps the last: a = 2parser B keeps the first: a = 1parser C reports an errorAll three conform to the spec.Two systems that both “support JSON”can read one message two ways.In a specification MUST, SHOULD and MAY are exact terms. What the text leaves open is where systems disagree.The key words are themselves defined by a standard, RFC 2119. When you rely on a format, read what it does not promiseand test against other implementations. The nine-page JSON spec takes ten minutes to skim and a week to implement faithfully.

In a spec, MUST, SHOULD and MAY have exact meanings. Gaps in the text become differences in behaviour.

Ambiguity in specs · Going deeper

The anatomy of a typical Standards Track RFC Header · Status · Abstract 1. Introduction 2. Terminology · RFC 2119 incantation 3–N. Protocol body · message formats · state machines · ABNF N+1. Conformance N+2. IANA Considerations N+3. Security Considerations · N+4. Privacy Considerations References (normative + informative) · Appendices · Authors what is this for, who approved it problem statement, scope MUST / SHOULD / MAY definitions the bulk of the document what counts as a conforming implementation new registries, new values, allocation policy threat model, attacks, residual risk other RFCs cited as required or context

Anatomy of a specification

Key words come from RFC 2119. Grammar is given in ABNF. A conformance section says what counts as conforming, and IANA Considerations says how new values, such as status codes, are registered. Skimmers read the abstract and security considerations; implementers read everything, then the errata and test suites.

Check yourself

{ "role": "user", "role": "admin" }gateway: keeps firstbackend: keeps last

A gateway and a backend both parse this message. The gateway keeps the first value of a repeated key, the backend the last. What happens?

Semantic versioning

A version number is a promise about what can break

2MAJOR.4MINOR.1PATCHsomething that workedmay now breaknew features;old code still worksbug fixes only;nothing else changes2.3.52.3.6safe: fixes only2.3.52.4.0safe: additions only2.3.53.0.0read the notes; expect to change your codeA rule of thumb for authorsIf you can name three ways a change couldbreak someone’s production: it is MAJOR.A wrong MAJOR costs one line in the notes.A wrong MINOR costs somebody an outage.A version number is a promise about what an upgrade can break: MAJOR may; MINOR and PATCH must not.This is Semantic Versioning. Tools rely on it to upgrade dependencies automatically, which works only if authors keep thepromise. Calendar versions such as Ubuntu 25.04 tell you when it was released, and nothing about what breaks.

Semantic Versioning: MAJOR for breaking changes, MINOR for additions, PATCH for fixes.

Hyrum’s law

Users depend on everything you do, not just what you promised

what thedocs promiseeverything callerscan observethe order results happen to come back inhow long a call usually takesthe exact wording of an error messagean undocumented default: cache size 100Somebody’s code now depends on:DefencesRandomise what is not promisedGo shuffles map order on purposeDeprecate before removingwarn for a version, then removeTest the contractnot the implementation’s quirksWith enough users, every observable behaviour is depended on by someone, whatever the documentation says.This is Hyrum’s Law. Raising an undocumented default cache from 100 to 1,000 breaks no promise, and still takes down thecaller running hundreds of connections, who runs out of memory. Compatibility is judged by what breaks, not by what was promised.

Hyrum’s Law: with enough users, every observable behaviour becomes part of the interface.

Hyrum’s law · Going deeper

Hyrum's Law — the documented API versus what callers depend on Documented contract undocumented · observable precision · ordering · timing error message text · log format field order in serialisation side-channel cache hits thread-scheduling artefacts

Hyrum’s Law in practice

Observed by Hyrum Wright at Google, where refactors that were safe under the documented contract kept breaking callers. On the web, feature detection and polyfills are the compatibility tools: check whether a capability exists before using it, or supply it on older browsers.

Check yourself

docsresults came back sortedsolid: what was promiseddashed: what callers could observe

The docs say “result order is not guaranteed”, but for five years results came back sorted. You release a faster version that returns them unsorted. What should you expect?

Conformance testing

A standard is proven by two implementations passing one test suite

Specificationthe documentImplementation Awritten from the textImplementation Bwritten independentlyConformance teststhe same suite, run on bothtwo implementations that pass the same tests can talk to each otherWeb Platform Tests: over 2 million checks, run against every major browser.A standard is real only when independent implementations pass the same tests and work together.With three browser engines, the HTML document decides. With one dominant implementation the code becomes the standard andthe document merely describes it: Linux for POSIX, CPython for Python. Passing the tests is necessary, not sufficient.

Conformance tests turn a document into something checkable. Independent implementations keep it honest.

Conformance testing · Going deeper

Spec to conformance — three points on a triangle Spec document Implementation A Implementation B reads · implements reads · implements connects · interoperates Conformance suite

Specification, implementation, tests

IETF hackathons put implementers in one room to connect their code; disagreements become errata. The annual Interop effort has browser vendors commit to passing agreed test areas. Passing the suite is necessary, not sufficient: production exposes middleboxes and timeouts the spec never anticipated. The healthiest state is one primary spec with two or more maintained implementations.

Check yourself

Specificationsilent on this pointThe one implementationused by everyone

A protocol has a written spec, but everyone uses the same single implementation. That implementation changes a behaviour the spec left open. What is the standard now?

Compliance

Compliance means proving, with evidence, that you followed the rules

A SOC 2 Type II audit, month by monthReadinesswrite policies, close gapsObservation windowthe controls must actually operate, and leave evidenceAudit and reportsample, question, signmonth 03912Evidence, collected the whole timeevery login used MFAevery change was revieweda backup restore was testedauditor checks 25 at randomSOC 2US, software vendorsISO 2700193 controls, worldwidePCI-DSSanyone handling card dataGDPREU: fines to 4% of turnoverEU AI Actfour tiers of riskCompliance attaches an auditor to a standard: you must show evidence that controls ran, month after month.The audit is the cheap part. The hard part is operating the controls consistently: every change reviewed, every access checked.It rarely changes what good teams already do. It makes the evidence trail formal enough for a third party to confirm.

A compliance framework is a set of controls plus an audit. The work is operating the controls, not passing the audit.

Compliance · Going deeper

Compliance frameworks by jurisdiction and scope US-led EU / international SOC 2 Type II FedRAMP HIPAA PCI-DSS v4.0 attestation · five Trust Service Criteria · 6–12 mo window authorisation · 800-53 baselines · Low / Mod / High regulation · health data · Security Rule contract · card networks · 12 requirements ISO/IEC 27001:2022 GDPR EU AI Act EAA / WCAG 2.2 AA certification · ISMS · 93 controls in 4 themes regulation · personal data · Art. 32 + Art. 25 regulation · risk tiers · high-risk conformity assessment regulation · accessibility · June 2025 deadline

Frameworks by territory

SOC 2 is an attestation, an auditor’s opinion; ISO 27001 is a certification issued by an accredited registrar; FedRAMP is a government authorisation taking 12 to 18 months. PCI-DSS is contractual, through the card networks. GDPR requires breach notice within 72 hours, with fines up to 4% of global turnover or €20 million. The EU AI Act sorts systems into four risk tiers.

Accessibility standards

Accessibility is a written, testable standard, and often the law

AAA: 28 more criteriacontrast 7 : 1 · sign-language versions · aspirationalAA: about 20 more criteriacontrast 4.5 : 1 · visible keyboard focus · text resizes to 200%A: about 30 criteria, the minimumevery image has a text alternativeeverything works from the keyboardaudio has captionsFour principlesPerceivablecan everyone sense the content?Operablecan everyone work the controls?Understandableis it readable and predictable?Robustcan assistive tools parse it?The law points at AA: the ADA and Section 508in the US, the European Accessibility Act in the EU.Accessibility has a written standard, WCAG, with three nested levels, and the law points at the middle one.That turns “make it accessible” from a matter of taste into criteria you can test: a contrast ratio, a keyboard path, a textalternative. Level AAA is not required as a general policy because some content cannot meet it.

WCAG defines accessibility as testable criteria in three levels. Level AA is the usual legal requirement.

Accessibility standards · Going deeper

WCAG 2.2 conformance levels — cumulative criteria Level A alt text · captions keyboard accessible no keyboard trap no seizure triggers page title · language link purpose · bypass blocks Level AA · +A contrast 4.5:1 resize 200 % reflow · zoom focus visible consistent navigation target size · drag alternatives Level AAA · +AA +A contrast 7:1 sign language extended audio descriptions reading level (lower secondary) no timing-dependent activity section identifiers · pronunciation AA is the practical target. AAA is aspirational and not recommended as a blanket policy.

WCAG 2.2 and its neighbours

WCAG 2.2 was published in October 2023; version 3.0 is in development. WAI-ARIA defines the attributes that expose custom widgets to screen readers. EN 301 549 is the European harmonised standard. The next lesson covers how to build to these criteria.

Spec drift

Specs and reality drift apart in three ways

The spec follows the codecodespecFetch, async/await: shipped,then written downhealthy, if they convergeThe code never followscodespecHTTP/2 Push, XHTML 2.0;IPv6 still mid-transition in 2026a finished document nobody shipsOne vendor forks itvendorstandardprivate extensions that userscome to depend onthe costly one: lock-intime →Specs and implementations drift apart. The defence is several independent implementations and public tests.A living standard such as HTML has no version: the document is whatever it says today. ISO standards are dated editions.Fewer engines and vendors mean fewer independent checks on any one of them.

Code can lead the spec, ignore it, or fork it. Multiple implementations and public tests limit the damage.

Spec drift · Going deeper

Three patterns of standards drift Spec lags reality Reality lags spec Reality forks spec implementation ships spec catches up spec spec spec ships implementations catch up (maybe) impl impl spec vendor A vendor B

Three patterns of drift

Living standards (HTML, DOM, URL, Fetch) are updated continuously and have no version to cite; ISO and IEEE publish dated editions. “Embrace, extend, extinguish” was documented in the 1990s. Recent years show convergence too: coordinated browser interop work, and AI providers settling on compatible API shapes.

Summary

Between systems, correct means written, implemented twice, tested

Who writes itIETF, W3C, ISO, IEEE, NISTThe documentMUST, SHOULD, MAYImplementationsat least two, independentShared testsprove they agreeOver timeversions promise what an upgrade may break; behaviour drifts anywayWhen it is mandatoryauditors and law turn SHOULD into MUST: SOC 2, GDPR, WCAG AABetween systems, “correct” means what was written down, implemented more than once, and tested.The mathematics of cryptography is true whoever reads it. A status code or a file format is true only by agreement.

Bodies, documents, implementations, tests, versions, audits. Next: interfaces, where systems meet people.

Summary · Going deeper

The standards landscape — bodies, process, document, conformance Bodies Process Conformance who writes the rules how they get to "done" how reality enforces them IETF · W3C ISO · IEEE NIST · ECMA WHATWG · LF the net and the web industry-wide baselines and JS living standards Internet-Draft Working group Last call · IESG RFC published draft-* expires 6 months rough consensus + code technical sign-off numbered, immutable RFC 2119 verbs Test suites SemVer · compat Audits · law MUST · SHOULD · MAY WPT · POSIX · Khronos deprecation windows SOC 2 · GDPR · EAA Implementations browsers · OS kernels · libraries · client SDKs · cloud platforms two implementations interoperate when both read the same document the same way

The standards landscape

A standard is a document. The bodies write it, the process gets them to done, and conformance is how reality decides whether the document was clear enough.

Lesson complete

You finished “Standards and Compatibility”

Answer the questions along the way to see your score here.

Open in a new tab