Additional Link Relation Types
RFC 6903

Document Type RFC - Informational (March 2013; No errata)
Last updated 2013-03-20
Stream ISE
Formats plain text pdf html
IETF conflict review conflict-review-snell-additional-link-relations
Stream ISE state Published RFC
Document shepherd No shepherd assigned
IESG IESG state RFC 6903 (Informational)
Telechat date
Responsible AD Barry Leiba
Send notices to jasnell@gmail.com, draft-snell-additional-link-relations@ietf.org
Independent Submission                                          J. Snell
Request for Comments: 6903                                    March 2013
Category: Informational
ISSN: 2070-1721

                     Additional Link Relation Types

Abstract

   This specification defines a number of additional link relation types
   that can used for a range of purposes in a variety of applications
   types.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6903.

Copyright Notice

   Copyright (c) 2013 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
   (http://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.

Snell                         Informational                     [Page 1]
RFC 6903                Additional Link Relations             March 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  "about" . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  "preview" . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  "privacy-policy"  . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  The "privacy-policy" Link Relation and P3P  . . . . . . .   4
   5.  "terms-of-service"  . . . . . . . . . . . . . . . . . . . . .   4
   6.  "type"  . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The fundamental model for web links and the "Link Relations" registry
   are established by [RFC5988].  This specification defines and adds
   the following additional link relation types to the registry:
   "about", "preview", "privacy-policy", "terms-of-service", and "type".

2.  "about"

   The "about" link relation can be used to refer to a resource that is
   the subject or topic of the link's context.  Multiple subjects can be
   indicated through the use of multiple "about" link relations.

   For example, if the context resource is a review about a particular
   product, the "about" link can be used to reference the URL of the
   product:

     HTTP/1.1 200 OK
     Content-Type: application/json
     Link: <http://store.example.org/product/abc>; rel="about"

     {...}

3.  "preview"

   The "preview" link relation can be used to refer to a resource that
   serves as a preview of the link's context, likely with reduced
   quality or limited content.  For instance, the preview link might
   reference a screen capture of a video, a brief snippet of audio from
   a song, or a thumbnail representation of an image.

Snell                         Informational                     [Page 2]
RFC 6903                Additional Link Relations             March 2013

   For example, issuing an HTTP HEAD request to a URI representing a
   large video or image file might return a link to a short or lower-
   quality preview of the original:

     HTTP/1.1 200 OK
     Content-Text: video/mpeg
     Link: <http://example.org/preview/10-second-preview.mpg>;
       rel="preview"; type="video/mpeg"

4.  "privacy-policy"

   The "privacy-policy" link relation can be used to refer to a resource
   describing the privacy policy associated with the link's context.
   The privacy policy can be any resource that discloses what personal
Show full document text