Cancel-Locks in Netnews Articles
RFC 8315
Document | Type |
RFC - Proposed Standard
(February 2018; No errata)
Updates RFC 5537
Was draft-baeuerle-netnews-cancel-lock (individual in art area)
|
|
---|---|---|---|
Author | Michael Bäuerle | ||
Last updated | 2018-02-13 | ||
Replaces | draft-ietf-usefor-cancel-lock | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Julien ÉLIE | ||
Shepherd write-up | Show (last changed 2017-05-30) | ||
IESG | IESG state | RFC 8315 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alexey Melnikov | ||
Send notices to | =?utf-8?q?Julien_=C3=89LIE?= <julien@trigofacile.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) M. Baeuerle Request for Comments: 8315 STZ Elektronik Updates: 5537 February 2018 Category: Standards Track ISSN: 2070-1721 Cancel-Locks in Netnews Articles Abstract This document defines an extension to the Netnews Article Format that may be used to authenticate the withdrawal of existing articles. This document updates RFC 5537. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8315. Copyright Notice Copyright (c) 2018 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 (https://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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Baeuerle Standards Track [Page 1] RFC 8315 Cancel-Locks February 2018 Table of Contents 1. Introduction ....................................................2 1.1. Conventions Used in This Document ..........................3 2. Header Fields ...................................................3 2.1. Cancel-Lock ................................................4 2.2. Cancel-Key .................................................4 3. Use .............................................................5 3.1. Adding an Initial Cancel-Lock Header Field to a Proto-Article ..............................................5 3.2. Extending the Cancel-Lock Header Field of a Proto-Article ..6 3.3. Adding a Cancel-Key Header Field to a Proto-Article ........6 3.4. Extending the Cancel-Key Header Field of a Proto-Article ...7 3.5. Check a Cancel-Key Header Field ............................7 4. Calculating the Key Data ........................................8 5. Examples ........................................................9 5.1. Without UID ................................................9 5.2. With UID ..................................................10 5.3. Other Examples ............................................11 5.4. Manual Checks .............................................12 6. Obsolete Syntax ................................................12 7. Security Considerations ........................................13 8. IANA Considerations ............................................15 8.1. Algorithm Name Registration Procedure .....................16 8.2. Change Control ............................................16 8.3. Registration of the Netnews Cancel-Lock Hash Algorithms ...17 9. References .....................................................18 9.1. Normative References ......................................18 9.2. Informative References ....................................19 Acknowledgements ..................................................20 Author's Address ..................................................20 1. Introduction The authentication system defined in this document is intended to be used as a simple method to verify that the withdrawal of an article is valid; that is to say the poster, posting agent, moderator, or injecting agent that processed the original article has requested to withdraw it via the use of a cancel control article ([RFC5537] Section 5.3) or a Supersedes header field ([RFC5537] Section 5.4). This document defines two new header fields: Cancel-Lock and Cancel-Key. The Cancel-Lock header field contains hashes of secret data. The preimages can later be used in the Cancel-Key header field to authenticate a cancel or supersede request. Baeuerle Standards Track [Page 2] RFC 8315 Cancel-Locks February 2018 One property of this system is that it prevents tracking of individual users.Show full document text