RFC 9652: The Link-Template HTTP Header Field
In plain English — editorial summary, not part of the RFC
This specification defines the Link-Template HTTP header field, providing a means for describing the structure of a link between two resources so that new links can be generated.
Document record
- Document ID
- RFC9652
- Published
- September 2024
- Authors
- M. Nottingham
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8288Web LinkingCurrent
October 2017
- RFC 5988Web LinkingObsoleted
October 2010
- RFC 9651Structured Field Values for HTTPCurrent
September 2024
- RFC 9653Zero Checksum for the Stream Control Transmission ProtocolCurrent
September 2024
- RFC 9648YANG Data Model for TCPCurrent
October 2024
- RFC 9659Window Sizing for Zstandard Content EncodingCurrent
September 2024
- RFC 9668Using Ephemeral Diffie-Hellman Over COSE (EDHOC) with the Constrained Application Protocol (CoAP) and Object Security for Constrained RESTful Environments (OSCORE)Current
November 2024
- RFC 9628RTP Payload Format for VP9 VideoCurrent
March 2025
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?