| RFC 9122 | IANA Registry for Sieve Actions | June 2023 |
| Melnikov & Murchison | Standards Track | [Page] |
The Sieve Email Filtering Language (RFC 5228) is a popular email filtering language used upon final mail delivery. This document creates a registry for Sieve actions to help developers and Sieve extension writers track interactions between different extensions.¶
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/rfc9122.¶
Copyright (c) 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Sieve Email Filtering Language [RFC5228] is a popular email filtering language used upon final mail delivery. The popularity of Sieve resulted in a myriad of Sieve extensions that can interact with each other in wonderful and complex ways. Currently, there is no easy way to find out all actions defined by Sieve extensions published in RFCs, which makes it quite difficult for Sieve extension writers and Sieve implementation developers to foresee interactions between Sieve actions.¶
This document creates a registry for Sieve [RFC5228] actions in order to help developers and Sieve extension writers track interactions between different extensions.¶
IANA has created the "Sieve Actions" registry (see Section 2.9 of [RFC5228] for details on Sieve actions). Registration of actions specified in both RFCs and vendor-specific documentation is allowed and encouraged. The registration template contains the following:¶
The registration procedure is Expert Review [RFC8126]. The designated expert only checks that the name of the action being registered matches documentation, the description field is accurate, the correct documents are referenced, and the list of relevant documents is as complete as possible. The designated expert can't reject a registration because of a personal dislike for the document defining an action and should always err on the side of approving the registration, even if documentation is not complete.¶
The same registration procedure is used to add a new reference or to change the description field of an existing registration.¶
The following registrations are used to initialize the "Sieve Actions" registry. Note that when the relevant "Action Interactions" entry is marked "N/A", it means that there is no restriction on use of the corresponding action with any other action; however, implementors still need to read the one or more corresponding specifications to determine if there are any surprising behaviors. Also note that the "Comments" field of the IANA registration template is omitted from these registrations, as none of them currently have any comments.¶
The sole purpose of this document is to create the "Sieve Actions" registry; therefore, it doesn't create new security considerations for Sieve implementations.¶
The new registry should help Sieve extension writers and Sieve implementors track interactions between different Sieve actions; therefore, it might improve the quality of specifications and implementations, including security aspects.¶
For security considerations related to particular actions, see the one or more RFCs referenced for the action in question in the "Sieve Actions" registry (Section 2.2).¶
Thank you to Barry Leiba, Donald Eastlake, Yoshiro Yoneya, and Murray Kucherawy for reviews and feedback on this document.¶