idnits 2.17.1 draft-ietf-extra-sieve-action-registry-01.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5228, but the abstract doesn't seem to directly say this. It does mention RFC5228 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5228, updated by this document, for RFC5378 checks: 2005-05-09) -- 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 (3 March 2022) is 784 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: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Melnikov 3 Internet-Draft Isode Ltd 4 Updates: 5228 (if approved) 3 March 2022 5 Intended status: Standards Track 6 Expires: 4 September 2022 8 IANA registry for Sieve actions 9 draft-ietf-extra-sieve-action-registry-01 11 Abstract 13 This document creates a registry of Sieve (RFC 5228) actions in order 14 to help developers and Sieve extension writers track interactions 15 between different extensions. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on 4 September 2022. 34 Copyright Notice 36 Copyright (c) 2022 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Revised BSD License text as 45 described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Revised BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 54 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 55 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 Sieve Email Filtering Language [RFC5228] is a popular email filtering 61 language used upon final mail delivery. Popularity of Sieve resulted 62 in a myriad of Sieve extensions that can interact with each other in 63 wonderful and complex ways. There is currently no easy way to find 64 out all actions defined by Sieve extensions published in RFCs, which 65 make it quite difficult for Sieve extension writers and Sieve 66 implementation developers to forsee interactions between Sieve 67 actions. 69 This document creates a registry of Sieve [RFC5228] actions in order 70 to help developers and Sieve extension writers track interactions 71 between different extensions. 73 2. Conventions Used in This Document 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 77 "OPTIONAL" in this document are to be interpreted as described in BCP 78 14 [RFC2119] [RFC8174] when, and only when, they appear in all 79 capitals, as shown here. 81 3. IANA Considerations 83 IANA is requested to create a new registry for Sieve actions (see 84 Section 2.9 of [RFC5228] for details on Sieve actions). Registration 85 of both actions specified in IETF Stream RFCs and vendor specific 86 actions is allowed and encouraged. The registration template 87 contains 1) name of the action; 2) short description; 3) references: 88 one or more documents describing the action and any significant 89 updates to its definition (this field is REQUIRED for actions 90 described in RFCs and OPTIONAL otherwise); 4) name(s) of Sieve 91 capabilit(ies) associated with the Sieve action being registered; 5) 92 interactions with other Sieve actions, if any; 6) flag specifying 93 whether the action cancels the implicit keep (see Section 2.10.2 of 94 [RFC5228]); 7) whether or not this action can be used with IMAP 95 events in Sieve ([RFC6785]), and 8) optional comment. 97 Registration procedure for this registry is Expert Review. The 98 Designated Expert only checks that the name of the action being 99 registered matches documentation, that the description field is 100 accurate, that the correct documents are referenced and that the list 101 of relevant documents is as complete as possible. The Designated 102 Expert can't reject a registration based on personal dislike of the 103 document defining an action and should always err on the side of 104 registering, even if documentation is not complete. 106 Addition of a new reference to an existing registration or change to 107 the description field goes through the same registration procedure as 108 a new registration. 110 4. Security Considerations 112 The sole purpose of this document is to create a new IANA registry, 113 so it doesn't create new security considerations for Sieve 114 implementations. 116 The new registry should help Sieve extension writers and Sieve 117 implementors track interactions between different Sieve actions, so 118 it might improve quality of specifications and implementations, 119 including security aspects. 121 5. Normative References 123 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 124 Requirement Levels", BCP 14, RFC 2119, 125 DOI 10.17487/RFC2119, March 1997, 126 . 128 [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email 129 Filtering Language", RFC 5228, DOI 10.17487/RFC5228, 130 January 2008, . 132 [RFC6785] Leiba, B., "Support for Internet Message Access Protocol 133 (IMAP) Events in Sieve", RFC 6785, DOI 10.17487/RFC6785, 134 November 2012, . 136 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 137 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 138 May 2017, . 140 Appendix A. Acknowledgements 142 TBD. 144 Author's Address 146 Alexey Melnikov 147 Isode Ltd 148 14 Castle Mews 149 Hampton 150 TW12 2NP 151 United Kingdom 152 Email: Alexey.Melnikov@isode.com