idnits 2.17.1 draft-snell-atompub-tombstones-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 241. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 252. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 259. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 265. 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 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 2, 2008) is 5959 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Snell 3 Internet-Draft January 2, 2008 4 Intended status: Standards Track 5 Expires: July 5, 2008 7 Atom Syndication Format Tombstones 8 draft-snell-atompub-tombstones-03.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on July 5, 2008. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2008). 39 Abstract 41 This specification defines mechanisms by which Atom Feed publishers 42 can explicitly indicate that specific Atom Entries have been removed 43 from an Atom feed. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 49 3. The atom:deleted-entry element . . . . . . . . . . . . . . . . 3 50 4. The Trash Link Relation . . . . . . . . . . . . . . . . . . . . 4 51 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 52 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 53 6.1. The Link Relation Registration "Trash" . . . . . . . . . . 5 54 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 55 8. Normative References . . . . . . . . . . . . . . . . . . . . . 6 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 57 Intellectual Property and Copyright Statements . . . . . . . . . . 7 59 1. Introduction 61 This specification adds a new element to the Atom Syndication Format 62 [RFC4287] that can be used to explicitly indicate that specific Atom 63 entries have been removed from an Atom Feed Document. 65 2. Notational Conventions 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 69 document are to be interpreted as described in BCP 14, [RFC2119] 71 This specification uses XML Namespaces [W3C.REC-xml-names-19990114] 72 to uniquely identify XML element names. It uses the following 73 namespace prefix for the indicated namespace URI; 75 "atom": "http://www.w3.org/2005/Atom" 77 3. The atom:deleted-entry element 79 The atom:deleted-entry element MAY appear as a child of atom:feed to 80 represent an Atom Entry that has been removed from the feed. 82 deletedEntry = element atom:deleted-entry { 83 atomCommonAttributes, 84 ( & atomID, 85 & element atom:when { atomDateConstruct }?, 86 & element atom:by { atomPersonConstruct}?, 87 & element atom:comment {atomTextConstruct}?, 88 & extensionElement* ) 89 } 91 The atom:deleted-entry element MUST contain one atom:id element whose 92 value specifies the atom:id of the entry that has been removed. 94 The atom:deleted-entry element MAY contain one atom:when element 95 whose value is an [RFC3339] "date-time" specifying the instant the 96 entry was deleted. An uppercase "T" character MUST be used to 97 separate date and time, and an uppercase "Z" character MUST be 98 present in the absence of a numeric time zone offset 100 The atom:deleted-entry element MAY contain one atom:by element used 101 to identify the entity that removed the entry from the feed. The 102 atom:by element is an Atom Person Construct as defined by Section 3.2 103 of [RFC4287]. 105 The atom:deleted-entry element MAY contain one atom:comment element 106 whose value provides additional information about the deletion 107 operation. The atom:comment element is an Atom Text Construct as 108 defined by Section 3.1 of [RFC4287]. 110 Atom Feed Documents MAY contain any number of atom:deleted-entry 111 elements. 113 114 ... 115 116 117 tag:example.org,2005:/entries/1 118 120 121 122 tag:example.org,2005:/entries/2 123 2005-11-29T12:11:12Z 124 125 John Doe 126 jdoe@example.org 127 128 Removed comment spam 129 130 ... 131 133 An Atom feed MAY contain atom:entry elements and atom:deleted-entry 134 elements sharing the same atom:id value. Atom processors MUST ignore 135 any atom:deleted-entry elements sharing an atom:id value with an 136 atom:entry whose atom:updated element specifies a date and time more 137 recent than the atom:deleted-entry element's atom:when value. If the 138 atom:deleted-entry element does not contain an atom:when element, the 139 atom:deleted-entry sharing the same atom:id as an entry MUST be 140 ignored. 142 4. The Trash Link Relation 144 When an entry is deleted from one feed, a server can choose to move 145 that entry into another Feed document whose member entries consist 146 entirely of deleted entries. Such "trash" feeds are similar in 147 nature to desktop operating system trash folders that are used to 148 collect, and potentially recover items that have been deleted. 150 This specification registers a new "trash" link relation to the Atom 151 Registry of Link Relations defined in Section 7.1 of [RFC4287]. When 152 appearing on atom:link elements within either the atom:feed or atom: 153 source elements, The "trash" rel attribute value signifies that the 154 IRI in the value of href attribute identifies a resource listing 155 entries that have been deleted from the Feed document. 157 For example, 159 160 ... 161 162 163 ... 164 166 5. Security Considerations 168 As specified in [RFC4287], Atom processors should be aware of the 169 potential for spoofing attacks where an attacker publishes atom:entry 170 or atom:deleted-entry elements using the same atom:id values as 171 entries from other Atom feeds. An attacker may attempt to trick an 172 application into believing that a given entry has either been removed 173 from or added to a feed. To mitigate this issue, Atom processors are 174 advised to ignore atom:deleted-entry elements referencing entries 175 that have not previously appeared within the containing Feed document 176 and should take steps to verify the origin of the Atom feed before 177 considering the entries to be removed. 179 6. IANA Considerations 181 6.1. The Link Relation Registration "Trash" 183 Attribute Value: trash 184 Description: An IRI of a resource listing deleted resources. When 185 appearing within an atom:feed or atom:source elements, signifies 186 that the IRI in the value of the href attribute identifies a 187 resource listing entries that have been deleted from the Feed 188 document. 189 Expected display characteristics: Undefined; this relation can be 190 used for background processing or to provide extended 191 functionality without displaying its value. 192 Security considerations: Automated agents should take care when this 193 relation crosses administrative domains (e.g., the URI has a 194 different authority than the current document). 196 7. Acknowledgements 198 The author gratefully acknowledges the feedback from the members of 199 the Atom Publishing Format and Protocol working group during the 200 development of this specification. 202 8. Normative References 204 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 205 Requirement Levels", BCP 14, RFC 2119, March 1997. 207 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 208 Internet: Timestamps", RFC 3339, July 2002. 210 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom 211 Syndication Format", RFC 4287, December 2005. 213 [W3C.REC-xml-names-19990114] 214 Hollander, D., Layman, A., and T. Bray, "Namespaces in 215 XML", World Wide Web Consortium FirstEdition REC-xml- 216 names-19990114, January 1999, 217 . 219 Author's Address 221 James M Snell 223 Phone: 224 Email: jasnell@gmail.com 225 URI: http://snellspace.com 227 Full Copyright Statement 229 Copyright (C) The IETF Trust (2008). 231 This document is subject to the rights, licenses and restrictions 232 contained in BCP 78, and except as set forth therein, the authors 233 retain all their rights. 235 This document and the information contained herein are provided on an 236 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 237 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 238 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 239 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 240 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 241 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 243 Intellectual Property 245 The IETF takes no position regarding the validity or scope of any 246 Intellectual Property Rights or other rights that might be claimed to 247 pertain to the implementation or use of the technology described in 248 this document or the extent to which any license under such rights 249 might or might not be available; nor does it represent that it has 250 made any independent effort to identify any such rights. Information 251 on the procedures with respect to rights in RFC documents can be 252 found in BCP 78 and BCP 79. 254 Copies of IPR disclosures made to the IETF Secretariat and any 255 assurances of licenses to be made available, or the result of an 256 attempt made to obtain a general license or permission for the use of 257 such proprietary rights by implementers or users of this 258 specification can be obtained from the IETF on-line IPR repository at 259 http://www.ietf.org/ipr. 261 The IETF invites any interested party to bring to its attention any 262 copyrights, patents or patent applications, or other proprietary 263 rights that may cover technology that may be required to implement 264 this standard. Please address the information to the IETF at 265 ietf-ipr@ietf.org. 267 Acknowledgment 269 Funding for the RFC Editor function is provided by the IETF 270 Administrative Support Activity (IASA).