Network Working Group                                        A. Melnikov
Internet-Draft                                                 Isode Ltd
Updates: 5228 (if approved)                               19 August 2021                                 3 March 2022
Intended status: Standards Track
Expires: 20 February 4 September 2022

                    IANA registry for Sieve actions
               draft-ietf-extra-sieve-action-registry-00
               draft-ietf-extra-sieve-action-registry-01

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 20 February 4 September 2022.

Copyright Notice

   Copyright (c) 2021 2022 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 Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
   3.
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3   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.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  IANA Considerations

   IANA is requested to create a new registry for Sieve actions (see
   Section 2.9 of [RFC5228] for details on Sieve actions).  Registration
   of both actions specified in IETF Stream RFCs and vendor specific
   actions is allowed and encouraged.  The registration template
   contains 1) name of the action; 2) short description; 3) references:
   one or more documents describing the action and any significant
   updates to its definition (this field is REQUIRED for actions
   described in RFCs and optional OPTIONAL otherwise); 4) name(s) of Sieve
   capabilit(ies) associated with the Sieve action being registered; 5)
   interactions with other Sieve actions, if any; 6) flag specifying
   whether the action cancels the implicit keep (see Section 2.10.2 of
   [RFC5228]); 7) whether or not this action can be used with IMAP
   events in Sieve ([RFC6785]), and 8) optional comment.

   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.

   Addition of a new reference to an existing registration or change to
   the description field goes through the same registration procedure as
   a new registration.

3.

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
   implementations.

   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.

4.

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>.

   [RFC6785]  Leiba, B., "Support for Internet Message Access Protocol
              (IMAP) Events in Sieve", RFC 6785, DOI 10.17487/RFC6785,
              November 2012, <https://www.rfc-editor.org/info/rfc6785>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

Appendix A.  Acknowledgements

   TBD.

Author's Address

   Alexey Melnikov
   Isode Ltd
   14 Castle Mews
   Hampton
   TW12 2NP
   United Kingdom
   Email: Alexey.Melnikov@isode.com