draft-ietf-extra-sieve-action-registry-00.txt   draft-ietf-extra-sieve-action-registry-01.txt 
Network Working Group A. Melnikov Network Working Group A. Melnikov
Internet-Draft Isode Ltd Internet-Draft Isode Ltd
Updates: 5228 (if approved) 19 August 2021 Updates: 5228 (if approved) 3 March 2022
Intended status: Standards Track Intended status: Standards Track
Expires: 20 February 2022 Expires: 4 September 2022
IANA registry for Sieve actions IANA registry for Sieve actions
draft-ietf-extra-sieve-action-registry-00 draft-ietf-extra-sieve-action-registry-01
Abstract Abstract
This document creates a registry of Sieve (RFC 5228) actions in order This document creates a registry of Sieve (RFC 5228) actions in order
to help developers and Sieve extension writers track interactions to help developers and Sieve extension writers track interactions
between different extensions. between different extensions.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 20 February 2022. This Internet-Draft will expire on 4 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions Used in This Document . . . . . . . . . . . . . . 2
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
4. Normative References . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. Normative References . . . . . . . . . . . . . . . . . . . . 3
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
Sieve Email Filtering Language [RFC5228] is a popular email filtering Sieve Email Filtering Language [RFC5228] is a popular email filtering
language used upon final mail delivery. Popularity of Sieve resulted language used upon final mail delivery. Popularity of Sieve resulted
in a myriad of Sieve extensions that can interact with each other in 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 wonderful and complex ways. There is currently no easy way to find
out all actions defined by Sieve extensions published in RFCs, which out all actions defined by Sieve extensions published in RFCs, which
make it quite difficult for Sieve extension writers and Sieve make it quite difficult for Sieve extension writers and Sieve
implementation developers to forsee interactions between Sieve implementation developers to forsee interactions between Sieve
actions. actions.
This document creates a registry of Sieve [RFC5228] actions in order This document creates a registry of Sieve [RFC5228] actions in order
to help developers and Sieve extension writers track interactions to help developers and Sieve extension writers track interactions
between different extensions. between different extensions.
2. IANA Considerations 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 IANA is requested to create a new registry for Sieve actions (see
Section 2.9 of [RFC5228] for details on Sieve actions). Registration Section 2.9 of [RFC5228] for details on Sieve actions). Registration
of both actions specified in IETF Stream RFCs and vendor specific of both actions specified in IETF Stream RFCs and vendor specific
actions is allowed and encouraged. The registration template actions is allowed and encouraged. The registration template
contains 1) name of the action; 2) short description; 3) references: contains 1) name of the action; 2) short description; 3) references:
one or more documents describing the action and any significant one or more documents describing the action and any significant
updates to its definition (this field is REQUIRED for actions updates to its definition (this field is REQUIRED for actions
described in RFCs and optional otherwise); 4) name(s) of Sieve described in RFCs and OPTIONAL otherwise); 4) name(s) of Sieve
capabilit(ies) associated with the Sieve action being registered; 5) capabilit(ies) associated with the Sieve action being registered; 5)
interactions with other Sieve actions, if any; 6) flag specifying interactions with other Sieve actions, if any; 6) flag specifying
whether the action cancels implicit keep (see Section 2.10.2 of 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 [RFC5228]); 7) whether or not this action can be used with IMAP
events in Sieve ([RFC6785]), and 8) optional comment. events in Sieve ([RFC6785]), and 8) optional comment.
Registration procedure for this registry is Expert Review. The Registration procedure for this registry is Expert Review. The
Designated Expert only checks that the name of the action being Designated Expert only checks that the name of the action being
registered matches documentation, that the description field is registered matches documentation, that the description field is
accurate, that the correct documents are referenced and that the list accurate, that the correct documents are referenced and that the list
of relevant documents is as complete as possible. The Designated of relevant documents is as complete as possible. The Designated
Expert can't reject a registration based on personal dislike of the Expert can't reject a registration based on personal dislike of the
document defining an action and should always err on the side of document defining an action and should always err on the side of
registering, even if documentation is not complete. registering, even if documentation is not complete.
Addition of a new reference or change to the description field goes Addition of a new reference to an existing registration or change to
through the same registration procedure as a new registration. the description field goes through the same registration procedure as
a new registration.
3. Security Considerations 4. Security Considerations
The sole purpose of this document is to create a new IANA registry, The sole purpose of this document is to create a new IANA registry,
so it doesn't create new security considerations for Sieve so it doesn't create new security considerations for Sieve
implementations. implementations.
The new registry should help Sieve extension writers and Sieve The new registry should help Sieve extension writers and Sieve
implementors track interactions between different Sieve actions, so implementors track interactions between different Sieve actions, so
it might improve quality of specifications and implementations, it might improve quality of specifications and implementations,
including security aspects. including security aspects.
4. Normative References 5. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email
Filtering Language", RFC 5228, DOI 10.17487/RFC5228, Filtering Language", RFC 5228, DOI 10.17487/RFC5228,
January 2008, <https://www.rfc-editor.org/info/rfc5228>. January 2008, <https://www.rfc-editor.org/info/rfc5228>.
[RFC6785] Leiba, B., "Support for Internet Message Access Protocol [RFC6785] Leiba, B., "Support for Internet Message Access Protocol
(IMAP) Events in Sieve", RFC 6785, DOI 10.17487/RFC6785, (IMAP) Events in Sieve", RFC 6785, DOI 10.17487/RFC6785,
November 2012, <https://www.rfc-editor.org/info/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 Appendix A. Acknowledgements
TBD. TBD.
Author's Address Author's Address
Alexey Melnikov Alexey Melnikov
Isode Ltd Isode Ltd
14 Castle Mews 14 Castle Mews
Hampton Hampton
 End of changes. 15 change blocks. 
19 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/