Sieve: Internationalized Email
draft-bosch-sieve-eai-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-21
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           S. Bosch
Internet-Draft                                                Dovecot Oy
Intended status: Standards Track                           21 March 2020
Expires: 22 September 2020

                     Sieve: Internationalized Email
                        draft-bosch-sieve-eai-00

Abstract

   This document defines an extension to the Sieve language called "eai"
   which adds full support for internationalized email.

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 22 September 2020.

Copyright Notice

   Copyright (c) 2020 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 (http://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.

Table of Contents

   1.  Introduction
   2.  Conventions Used in This Document
   3.  Headers
   4.  Addresses
   5.  Modified commands
       5.1.  Test address
       5.2.  Test header
       5.3.  Action redirect
   6.  Modified extensions
       6.1.  Body Extension
       6.2.  Convert Extension
       6.3.  Editheader Extension
       6.4.  Envelope Extension
       6.5.  Enotify Extension
       6.6.  Reject and Extended Reject Extensions
       6.7.  Mime Extension
       6.8.  Replace Extension
       6.9.  Enclose Extension
       6.10.  Other Extensions?
   7.  Downgrading
   8.  Mailing lists
   9.  Examples
   10.  Acknowledgements
   11.  IANA Considerations
   12.  Security Considerations
   13.  References
       13.1.  Normative References
       13.2.  Informative References
   Author's Address

1.  Introduction

   Many parts of the Sieve mail filtering language [SIEVE] such as
   strings and comments are already designed primarily for use with the
   UTF-8 encoding [UTF-8] , thereby supporting all the international
   characters specified by the Unicode standard.  Also, Sieve can
   already work with message header fields that contain UTF-8
   characters, provided these are encoded using MIME encoded-word
   [MIME3].  However, the Sieve language was conceived before the
   Framework for Internationalized Email [RFC6530] was finished, which
   means that filtered email messages are still restricted to the
   conventional Internet Message Format [IMAIL], which mainly means that
   only the conventional US-ASCII email addresses can be used [SMTP].
   This poses problems for using the Sieve language in a mail system
   where internationalized email is to be supported.

   This document defines an extension to the Sieve language called "eai"
   which adds full support for internationalized email.

   [FIXME: Any ideas for a better name for the extension?]

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 [KEYWORDS] [KEYWORDS-UPD] when, and only when, they appear in
   all capitals, as shown here.

3.  Headers

   The "eai" extension presented in this document does not alter the
   handling of conventional Internet messages [IMAIL], which have
   content type "message/rfc822".  For such conventional messages, it
   expects UTF-8 characters in header field values to be encoded using
   MIME encoded-words [MIME3].  In contrast, when the filtered message
   (or message part) has content type "message/global" [RFC6532], the
   header field value can contain UTF-8 characters directly and MIME
   encoded-words SHOULD NOT be interpreted.

   Note that internationalized email header names are still restricted
   to ASCII characters only [RFC6532], which means that the Sieve tests
   in which header fields are evaluated will never match when the
   provided header name contains UTF-8 characters.

4.  Addresses

   Section 2.4.2.3 of [SIEVE] defines a constrained version of the US-
Show full document text