HTTP Link and Unlink Methods
draft-snell-link-method-08
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2013-12-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Individual Submission J. Snell
Internet-Draft
Intended status: Standards Track December 4, 2013
Expires: June 7, 2014
HTTP Link and Unlink Methods
draft-snell-link-method-08
Abstract
This specification defines the semantics of the LINK and UNLINK HTTP
methods.
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 7, 2014.
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 Expires June 7, 2014 [Page 1]
Internet-Draft HTTP Link and Unlink Methods December 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Link Relationships . . . . . . . . . . . . . . . . . . . . . 2
3. LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. UNLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Relationship to other HTTP Methods and Discoverability of
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informational References . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
This specification updates the HTTP LINK and UNLINK methods
originally defined in [RFC2068].
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in [RFC2119].
2. Link Relationships
The LINK and UNLINK methods are used to manage relationships between
resources. Those relationships are defined using the Link model
established in Section 3 of [RFC5988]. For every individual link,
the context IRI, link relation type, target IRI, and optional
collection of target attributes MUST be considered; that is, for any
effective request URI, there can exist at most one Link relationship
between any context and target IRI pairing with any given combination
of link relation type and target attributes.
Within LINK and UNLINK requests, a [RFC5988] Link header field is
used to describe a Link relationship to be managed. Any single LINK
or UNLINK request MAY contain multiple Link header fields, each of
which describes a separate relationship between a context IRI and
target IRI. When a LINK request contains multiple Link header
fields, the server MUST create all of the specified relationships or
not create any of them. Likewise, when an UNLINK request contains
multiple Link header fields, the server MUST either remove all the
specified relationship or not remove any of them.
Snell Expires June 7, 2014 [Page 2]
Internet-Draft HTTP Link and Unlink Methods December 2013
The target and context IRIs of a Link relationship are determined
following the requirements specified in Sections 5.1 and 5.2 of
[RFC5988].
When determining whether or not a relationship already exists between
a context IRI and target IRI, implementations will need to compare
the given IRIs with other, previously established relationships. To
do so, the implementation MUST first resolve the IRIs as required by
[RFC5988] and then compare on a case-sensitive, character-by-
character basis. For instance, the IRIs "http://example.org/foo" and
"http://example.org/Foo" MUST NOT be considered to be equivalent.
3. LINK
Show full document text