idnits 2.17.1
draft-snell-atompub-tombstones-00.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 14.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 289.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 266.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 273.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 279.
** This document has an original RFC 3978 Section 5.4 Copyright Line,
instead of the newer IETF Trust Copyright according to RFC 4748.
** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
of the newer disclaimer which includes the IETF Trust according to RFC
4748.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
== No 'Intended status' indicated for this document; assuming Proposed
Standard
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack separate sections for Informative/Normative
References. All references will be assumed normative when checking for
downward references.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 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 (November 2005) is 6736 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: 4 errors (**), 0 flaws (~~), 3 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 November 2005
4 Expires: May 5, 2006
6 Atom Syndication Format Tombstones
7 draft-snell-atompub-tombstones-00.txt
9 Status of this Memo
11 By submitting this Internet-Draft, each author represents that any
12 applicable patent or other IPR claims of which he or she is aware
13 have been or will be disclosed, and any of which he or she becomes
14 aware will be disclosed, in accordance with Section 6 of BCP 79.
16 Internet-Drafts are working documents of the Internet Engineering
17 Task Force (IETF), its areas, and its working groups. Note that
18 other groups may also distribute working documents as Internet-
19 Drafts.
21 Internet-Drafts are draft documents valid for a maximum of six months
22 and may be updated, replaced, or obsoleted by other documents at any
23 time. It is inappropriate to use Internet-Drafts as reference
24 material or to cite them other than as "work in progress."
26 The list of current Internet-Drafts can be accessed at
27 http://www.ietf.org/ietf/1id-abstracts.txt.
29 The list of Internet-Draft Shadow Directories can be accessed at
30 http://www.ietf.org/shadow.html.
32 This Internet-Draft will expire on May 5, 2006.
34 Copyright Notice
36 Copyright (C) The Internet Society (2005).
38 Abstract
40 This specification defines mechanisms by which Atom Feed publishers
41 may explicitly indicate that specific Atom Entries have been deleted
42 or archived.
44 Table of Contents
46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
47 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3
48 3. The 'deleted-entry' element . . . . . . . . . . . . . . . . . . 3
49 4. The 'archived-entry' element . . . . . . . . . . . . . . . . . 4
50 5. The 'by' Element . . . . . . . . . . . . . . . . . . . . . . . 6
51 6. The 'comment' Element . . . . . . . . . . . . . . . . . . . . . 6
52 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
53 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
54 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
55 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
57 Intellectual Property and Copyright Statements . . . . . . . . . . 9
59 1. Introduction
61 This specification defines mechanisms in the form of Atom Format
62 [RFC4287] extensions that Atom Feed publishers can use to explicitly
63 indicate that specific Atom Entries have been removed from a feed due
64 to deletion or archiving.
66 2. Notational Conventions
68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
70 document are to be interpreted as described in BCP 14, [RFC2119]
72 This specification uses XML Namespaces [W3C.REC-xml-names-19990114]
73 to uniquely identify XML element names. It uses the following
74 namespace prefix for the indicated namespace URI;
76 {Ed. Note: this namespace MUST be changed to a proper IETF namespace
77 scheme prior to publication}
79 "at": "http://purl.org/atompub/tombstones/1.0"
81 3. The 'deleted-entry' element
83 The 'deleted-entry' element MAY appear as a child of atom:feed to
84 represent an Atom Entry that has been removed from the feed due to
85 deletion. The element consists of a required 'id' attribute whose
86 value specifies the universally unique atom:id value of the deleted
87 entry and an optional 'when' attribute whose value is an Atom Date
88 Construct specifying the instant the entry was deleted.
90 deletedEntry = element at:deleted-entry {
91 atomCommonAttributes,
92 & attribute id { atomURI },
93 & attribute when { atomDateConstruct }?,
94 ( by?,
95 & comment*,
96 & undefinedContent )
97 }
99 Atom Processors MUST ignore 'deleted-entry' elements whose 'id'
100 attributes reference Atom Entries that have not previously appeared
101 within the Atom Feed document.
103 The 'deleted-entry' element MAY contain a 'by' element that
104 identifies the entity that deleted the entry.
106 The 'deleted-entry' element MAY contain zero or more 'comment'
107 elements whose content provides additional information about the
108 deletion operation.
110 Atom Feed Documents MAY contain any number of 'deleted-entry'
111 elements.
113
114 ...
115
118
119 John Doe
120 jdoe@example.org
121
122 Removed comment spam
123
124
127
128 John Doe
129 jdoe@example.org
130
131 Removed comment spam
132
133 ...
134
136 4. The 'archived-entry' element
138 The 'archived-entry' element MAY appear as a child of atom:feed to
139 represent an Atom Entry that has been removed from the feed due to
140 archiving. The element consists of a required 'id' attrubute whose
141 value specifies the universally unique atom:id value of the archived
142 entry, a required 'href' attribute whose value specifies the IRI from
143 which the archived Atom Entry Document MAY be retrieved, and an
144 optional 'when' attribute whose value is an Atom Date Construct
145 specifying the instant the entry was archived.
147 archivedEntry = element at:archived-entry {
148 atomCommonAttributes,
149 & attribute id { atomURI },
150 & attribute href { atomURI },
151 & attribute when { atomDateConstruct }?,
152 ( by?,
153 & comment*,
154 & undefinedContent )
155 }
157 The 'archived-entry' element MAY contain a 'by' element that
158 identifies the entity that archived the entry.
160 The 'archived-entry' element MAY contain zero or more 'comment'
161 elements whose content provides additional information about the
162 archival operation.
164 Atom Processors MUST ignore 'archived-entry' elements whose 'id'
165 attributes reference Atom Entries that have not previously appeared
166 within the Atom Feed document.
168 Atom Feed Documents MAY contain any number of 'archived-entry'
169 elements.
171
172 ...
173
177
178 Automated Archive Process
179
180
181
185
186 Automated Archive Process
187
188
189 ...
190
192 5. The 'by' Element
194 The 'by' element is an Atom Person Construct that is used to identify
195 the entity that performed a deletion or archive operation on an
196 entry.
198 by = element at:by { atomPersonConstruct }
200 6. The 'comment' Element
202 The 'comment' element in an Atom Text Construct that is used to
203 provide additional human readable information about a deletion or
204 archive operation on an entry.
206 comment = element at:comment { atomTextConstruct }
208 7. Security Considerations
210 As specified in [RFC4287], Atom processors should be aware of the
211 potential for spoofing attacks where an attacked publishes atom:entry
212 elements with the same atom:id value of entries from other Atom
213 feeds. The same potential exists with the mechanisms defined here in
214 that an attacker may attempt to spoof an application into believing
215 that a given entry has been removed from a feed. To mitigate this
216 issue, Atom processors MUST ignore 'deleted-entry' and 'archived-
217 entry' elements referencing entries that have not previously appeared
218 within the containing Feed document and should take steps to verify
219 the origin of the Atom feed before considering the entries to be
220 removed.
222 8. IANA Considerations
224 There are no IANA considerations introduced by this specification.
226 9. Acknowledgements
228 The author gratefully acknowledges the feedback from the members of
229 the Atom Publishing Format and Protocol working group during the
230 development of this specification.
232 10. References
234 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
235 Requirement Levels", BCP 14, RFC 2119, March 1997.
237 [RFC4287] Nottingham, M. and R. Sayre, "The Atom Syndication
238 Format", RFC 4287, December 2005.
240 [W3C.REC-xml-infoset-20040204]
241 Tobin, R. and J. Cowan, "XML Information Set (Second
242 Edition)", W3C REC REC-xml-infoset-20040204,
243 February 2004.
245 [W3C.REC-xml-names-19990114]
246 Hollander, D., Bray, T., and A. Layman, "Namespaces in
247 XML", W3C REC REC-xml-names-19990114, January 1999.
249 Author's Address
251 James M Snell
253 Phone:
254 Email: jasnell@gmail.com
255 URI: http://snellspace.com
257 Intellectual Property Statement
259 The IETF takes no position regarding the validity or scope of any
260 Intellectual Property Rights or other rights that might be claimed to
261 pertain to the implementation or use of the technology described in
262 this document or the extent to which any license under such rights
263 might or might not be available; nor does it represent that it has
264 made any independent effort to identify any such rights. Information
265 on the procedures with respect to rights in RFC documents can be
266 found in BCP 78 and BCP 79.
268 Copies of IPR disclosures made to the IETF Secretariat and any
269 assurances of licenses to be made available, or the result of an
270 attempt made to obtain a general license or permission for the use of
271 such proprietary rights by implementers or users of this
272 specification can be obtained from the IETF on-line IPR repository at
273 http://www.ietf.org/ipr.
275 The IETF invites any interested party to bring to its attention any
276 copyrights, patents or patent applications, or other proprietary
277 rights that may cover technology that may be required to implement
278 this standard. Please address the information to the IETF at
279 ietf-ipr@ietf.org.
281 Disclaimer of Validity
283 This document and the information contained herein are provided on an
284 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
285 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
286 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
287 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
288 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
289 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
291 Copyright Statement
293 Copyright (C) The Internet Society (2005). This document is subject
294 to the rights, licenses and restrictions contained in BCP 78, and
295 except as set forth therein, the authors retain all their rights.
297 Acknowledgment
299 Funding for the RFC Editor function is currently provided by the
300 Internet Society.