RFC 6903: Additional Link Relation Types
In plain English — editorial summary, not part of the RFC
This specification defines a number of additional link relation types that can used for a range of purposes in a variety of applications types.
Document record
- Document ID
- RFC6903
- Published
- March 2013
- Authors
- J. Snell
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6983Models for HTTP-Adaptive-Streaming-Aware Content Distribution Network Interconnection (CDNI)Current
July 2013
- RFC 7089HTTP Framework for Time-Based Access to Resource States -- MementoCurrent
December 2013
- RFC 3507Internet Content Adaptation Protocol (ICAP)Current
April 2003
- RFC 6819OAuth 2.0 Threat Model and Security ConsiderationsUpdated
January 2013
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 6638Scheduling Extensions to CalDAVUpdated
June 2012
- RFC 7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and RoutingObsoleted
June 2014
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?