RFC 9264: Linkset: Media Types and a Link Relation Type for Link Sets
In plain English — editorial summary, not part of the RFC
This specification defines two formats and associated media types for representing sets of links as standalone documents. One format is based on JSON, and the other is aligned with the format for representing links in the HTTP "Link" header field. This specification also introduces a link relation type to support the discovery of sets of links.
Document record
- Document ID
- RFC9264
- Published
- July 2022
- Authors
- E. Wilde; H. Van de Sompel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9457Problem Details for HTTP APIsCurrent
July 2023
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 7396JSON Merge PatchCurrent
October 2014
- RFC 7386JSON Merge PatchObsoleted
October 2014
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9176Constrained RESTful Environments (CoRE) Resource DirectoryCurrent
April 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?