idnits 2.17.1 draft-snell-more-link-relations-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 12, 2014) is 3697 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3986' is defined on line 125, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 5988 (Obsoleted by RFC 8288) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J.M. Snell 3 Internet-Draft March 12, 2014 4 Intended status: Informational 5 Expires: September 13, 2014 7 Additional Link Relation Registrations 8 draft-snell-more-link-relations-04 10 Abstract 12 This specification registers a handful of new RFC 5988 Link Relation 13 types. 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on September 13, 2014. 32 Copyright Notice 34 Copyright (c) 2014 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 47 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 48 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 49 4. Informative References . . . . . . . . . . . . . . . . . . . 3 50 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 3 51 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 53 1. Introduction 55 This specification defines and adds the following additional link 56 relation types to the IANA Registry of Link Relations established by 57 [RFC5988]: to, bto, cc, bcc, from, bfrom, source, scope, generator, 58 provider, location, alias and mentioned-by. 60 Note that this document is a work-in-progress draft specification 61 that does not yet represent a "standard". It is the intention of 62 this specification to propose a few new ideas and openly solicit 63 feedback on their definition and use. While this document might 64 eventually evolve into an RFC the ideas described herein have not yet 65 been broadly implemented and have definitions that may evolve through 66 successive iterations of this draft. 68 2. IANA Considerations 70 The following Link Relations are added to the IANA Registry of Link 71 Relations: 73 +----------------+--------------------------------------------------+ 74 | Name | Description | 75 +----------------+--------------------------------------------------+ 76 | id | Specifies an IRI [RFC3987] or URI | 77 | | [RFC3986]considered to represent the identity of | 78 | | the link context. | 79 | to | Refers to a resource that is considered to be | 80 | | part of the public primary audience of the | 81 | | link's context. | 82 | bto | Refers to a resource that is considered to be | 83 | | part of the private primary audience of the | 84 | | link's context. | 85 | cc | Refers to a resource that is considered to be | 86 | | part of the public secondary audience of the | 87 | | link's context. | 88 | bcc | Refers to a resource that is considered to be | 89 | | part of the private secondary audience of the | 90 | | link's context. | 91 | from | Refers to a resource that is publicly considered | 92 | | to be the originator of the link's context. | 93 | bfrom | Refers to a resource that is privately | 94 | | considered to be the orignator of the link's | 95 | | context. | 96 | scope | Refers to a resource that identifies the total | 97 | | population of entities for which the context is | 98 | | considered relevant. | 99 | source | Refers to the original source of information | 100 | | contained by the context resource. | 101 | provider | Refers to the resource that provided the context | 102 | | resource. Typically, this would be used to | 103 | | identify the entity publishing the resource. | 104 | generator | Refers to the resource that generated the | 105 | | context resource. Typically, this would be used | 106 | | to identify the software application that | 107 | | created the context resource. | 108 | mentioned-by | Refers to a resource that mentions the context | 109 | | resource in some fashion. This, for example, | 110 | | would be used when an article mentions another | 111 | | article, or a social status update mentions a | 112 | | particular user, etc. | 113 | location | References an IRI or URI representing a physical | 114 | | or logical location with which the context | 115 | | resource is associated. | 116 +----------------+--------------------------------------------------+ 118 3. Security Considerations 120 There are no additional security concerns introduced by this 121 document. 123 4. Informative References 125 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 126 Resource Identifier (URI): Generic Syntax", STD 66, RFC 127 3986, January 2005. 129 [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource 130 Identifiers (IRIs)", RFC 3987, January 2005. 132 [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. 134 Appendix A. Examples 136 Using targeting link relations and the urn:social namespace: 138 POST /alerts HTTP/1.1 139 Host: example.org 140 Content-Type: text/plain 141 Authorization: Basic {Base64 Credentials} 142 Link: ; rel="to" 143 Link: ; rel="cc" 144 Link: ; rel="bfrom" 145 Link: ; rel="scope" 147 Test message 149 Using the targeting link relations with urn:social:role: 151 POST /alerts HTTP/1.1 152 Host: example.org 153 Content-Type: text/plain 154 Authorization: Basic {Base64 Credentials} 155 Link: ; rel="to" 156 Link: ; rel="cc" 158 Test message 160 Using publication link relations: 162 163 164 ... 165 168 171 174 ... 175 176 ... 177 179 Using the location relation: 181 Link: ; rel="location" 183 Using the mentioned-by relation: 185 LINK /articles/1 HTTP/1.1 186 Host: example.org 187 Link: ; rel="mentioned-by" 189 Author's Address 191 James M Snell 193 Email: jasnell@gmail.com