Network Working Group A. Melnikov Internet-Draft Isode Ltd Updates: 5228 (if approved) March 22, 2021 Intended status: Standards Track Expires: September 23, 2021 IANA registry for Sieve actions draft-melnikov-extra-sieve-action-registry-00 Abstract This document creates a registry of Sieve (RFC 5228) actions in order to help developers and Sieve extension writers track interactions between different extensions. Status of This Memo This Internet-Draft is submitted 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 https://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 September 23, 2021. Copyright Notice Copyright (c) 2021 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. Melnikov Expires September 23, 2021 [Page 1]
Internet-Draft IANA registry for Sieve actions March 2021 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 3. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction Sieve Email Filtering Language [RFC5228] is a popular email filtering language used upon final mail delivery. Popularity of Sieve resulted in a myriad of Sieve extensions that can interact with each other in wonderful and complex ways. There is currently no easy way to find out all actions defined by Sieve extensions published in RFCs, which make it quite difficult for Sieve extension writers and Sieve implementation developers to forsee interactions between Sieve actions. This document creates a registry of Sieve [RFC5228] actions in order to help developers and Sieve extension writers track interactions between different extensions. 2. IANA Considerations IANA is requested to create a new registry for Sieve actions (see Section 2.9 of [RFC5228]). The registration template contains 1) name of the action, 2) short description, 3) one of more document describing it and any significant updates (references), 4) name(s) of Sieve capabilit(ies) associated with the Sieve action being registered, 5) interactions with other Sieve actions, if any and 6) flag specifying whether the action cancels implicit keep (see Section 2.10.2 of [RFC5228]). [[Optional "comment" field?]] Registration procedure for this registry is Expert Review. The Designated Expert only checks that the name of the action being registered matches documentation, that the description field is accurate, that the correct documents are referenced and that the list of relevant documents is as complete as possible. The Designated Expert can't reject a registration based on personal dislike of the document defining an action and should always err on the side of registering, even if documentation is not complete. Melnikov Expires September 23, 2021 [Page 2]
Internet-Draft IANA registry for Sieve actions March 2021 Addition of a new reference or change to the description field goes through the same registration procedure as a new registration. 3. Open Issues [[This section should be empty before publication]] Should we include information for IMAP Sieve (RFC 6785)? Shall vendor specific actions be allowed to be registered? 4. Security Considerations The sole purpose of this document is to create a new IANA registry, so it doesn't create new security considerations for Sieve. The new registry should help Sieve extension writers and Sieve implementors track interactions between different Sieve actions, so it might improve quality of specifications and implementations, including security aspects. 5. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email Filtering Language", RFC 5228, DOI 10.17487/RFC5228, January 2008, <https://www.rfc-editor.org/info/rfc5228>. Melnikov Expires September 23, 2021 [Page 3]
Internet-Draft IANA registry for Sieve actions March 2021 Appendix A. Acknowledgements TBD. Author's Address Alexey Melnikov Isode Ltd 14 Castle Mews Hampton, Middlesex TW12 2NP UK EMail: Alexey.Melnikov@isode.com Melnikov Expires September 23, 2021 [Page 4]