RFC 5988: Web Linking
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8288.
Current version: RFC 8288 — Web Linking
In plain English — editorial summary, not part of the RFC
This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5988
- Published
- October 2010
- Authors
- M. Nottingham
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 23
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6249Metalink/HTTP: Mirrors and HashesCurrent
June 2011
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 7034HTTP Header Field X-Frame-OptionsCurrent
October 2013
- RFC 4918HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Updated
June 2007
- RFC 7540Hypertext Transfer Protocol Version 2 (HTTP/2)Obsoleted
May 2015
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 8307Well-Known URIs for the WebSocket ProtocolCurrent
January 2018
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?