Web Linking
RFC 8288
| Document | Type |
RFC - Proposed Standard
(October 2017; Errata)
Obsoletes RFC 5988
Was draft-nottingham-rfc5988bis (individual in art area)
|
|
|---|---|---|---|
| Last updated | 2017-10-25 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Barry Leiba | ||
| Shepherd write-up | Show (last changed 2017-05-02) | ||
| IESG | IESG state | RFC 8288 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alexey Melnikov | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Nottingham
Request for Comments: 8288 October 2017
Obsoletes: 5988
Category: Standards Track
ISSN: 2070-1721
Web Linking
Abstract
This specification defines a model for the relationships between
resources on the Web ("links") and the type of those relationships
("link relation types").
It also defines the serialisation of such links in HTTP headers with
the Link header field.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8288.
Nottingham Standards Track [Page 1]
RFC 8288 Web Linking October 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Nottingham Standards Track [Page 2]
RFC 8288 Web Linking October 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 4
1.2. Conformance and Error Handling . . . . . . . . . . . . . 4
2. Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Link Relation Types . . . . . . . . . . . . . . . . . . . 6
2.1.1. Registered Relation Types . . . . . . . . . . . . . . 6
2.1.2. Extension Relation Types . . . . . . . . . . . . . . 8
2.2. Target Attributes . . . . . . . . . . . . . . . . . . . . 9
3. Link Serialisation in HTTP Headers . . . . . . . . . . . . . 9
3.1. Link Target . . . . . . . . . . . . . . . . . . . . . . . 10
3.2. Link Context . . . . . . . . . . . . . . . . . . . . . . 10
3.3. Relation Type . . . . . . . . . . . . . . . . . . . . . . 11
3.4. Target Attributes . . . . . . . . . . . . . . . . . . . . 11
3.4.1. Serialisation-Defined Attributes . . . . . . . . . . 11
3.4.2. Extension Attributes . . . . . . . . . . . . . . . . 13
3.5. Link Header Field Examples . . . . . . . . . . . . . . . 13
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
4.1. Link HTTP Header Field Registration . . . . . . . . . . . 14
4.2. Link Relation Type Registry . . . . . . . . . . . . . . . 14
4.3. Link Relation Application Data Registry . . . . . . . . . 15
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. Internationalisation Considerations . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Normative References . . . . . . . . . . . . . . . . . . 16
7.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Notes on Other Link Serialisations . . . . . . . . . 19
A.1. Link Serialisation in HTML . . . . . . . . . . . . . . . 19
A.2. Link Serialisation in Atom . . . . . . . . . . . . . . . 19
Appendix B. Algorithms for Parsing Link Header Fields . . . . . 20
Show full document text