RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format

JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming…

Read RFC 8259 on the RFC Editor

Outgoing relationships (4 related RFCs)

Obsoletes, Informative reference — RFC 7159: The JavaScript Object Notation (JSON) Data Interchange Format
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Informative reference — RFC 4627: The application/json Media Type for JavaScript Object Notation (JSON)

Incoming relationships (66 related RFCs)

Showing 50 of 66 related RFCs.

Normatively referenced by — RFC 8725: JSON Web Token Best Current Practices
Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9711: The Entity Attestation Token (EAT)
Normatively referenced by — RFC 8844: Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
Normatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Normatively referenced by — RFC 9126: OAuth 2.0 Pushed Authorization Requests
Normatively referenced by — RFC 9201: Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)
Normatively referenced by — RFC 9224: Finding the Authoritative Registration Data Access Protocol (RDAP) Service
Normatively referenced by — RFC 9240: An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
Normatively referenced by — RFC 9254: Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)
Normatively referenced by — RFC 8896: Application-Layer Traffic Optimization (ALTO) Cost Calendar
Normatively referenced by — RFC 9140: Nimble Out-of-Band Authentication for EAP (EAP-NOOB)
Normatively referenced by — RFC 9241: Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)
Normatively referenced by — RFC 9535: JSONPath: Query Expressions for JSON
Normatively referenced by — RFC 9635: Grant Negotiation and Authorization Protocol (GNAP)
Normatively referenced by — RFC 9782: Entity Attestation Token (EAT) Media Types
Normatively referenced by — RFC 8295: EST (Enrollment over Secure Transport) Extensions
Normatively referenced by — RFC 8416: Simplified Local Internet Number Resource Management with the RPKI (SLURM)
Normatively referenced by — RFC 8908: Captive Portal API
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8936: Poll-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 9073: Event Publishing Extensions to iCalendar
Normatively referenced by — RFC 9264: Linkset: Media Types and a Link Relation Type for Link Sets
Normatively referenced by — RFC 9439: Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
Normatively referenced by — RFC 9493: Subject Identifiers for Security Event Tokens
Normatively referenced by — RFC 9555: JSContact: Converting from and to vCard
Normatively referenced by — RFC 8727: JSON Binding of the Incident Object Description Exchange Format
Normatively referenced by — RFC 8927: JSON Type Definition
Normatively referenced by — RFC 8977: Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging
Normatively referenced by — RFC 9178: Building Power-Efficient Constrained Application Protocol (CoAP) Devices for Cellular Networks
Normatively referenced by — RFC 9246: URI Signing for Content Delivery Network Interconnection (CDNI)
Normatively referenced by — RFC 9512: YAML Media Type
Normatively referenced by — RFC 9537: Redacted Fields in the Registration Data Access Protocol (RDAP) Response
Normatively referenced by — RFC 9569: The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)
Normatively referenced by — RFC 9578: Privacy Pass Issuance Protocols
Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Normatively referenced by — RFC 9767: Grant Negotiation and Authorization Protocol Resource Server Connections
Normatively referenced by — RFC 9770: Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) Framework
Normatively referenced by — RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data
Normatively referenced by — RFC 9996: Media Types for Protocol Buffers
Informatively referenced by — RFC 8949: Concise Binary Object Representation (CBOR)
Informatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 8941: Structured Field Values for HTTP
Informatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Informatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Informatively referenced by — RFC 8747: Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
Informatively referenced by — RFC 9641: A YANG Data Model for a Truststore