Implementing Draft & Release and Draft & Review in Internet Mail
draft-melnikov-email-draft-and-release-03

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                   A. Melnikov, Ed.
Internet-Draft                                                 Isode Ltd
Intended status: Informational                          October 31, 2016
Expires: May 4, 2017

    Implementing Draft & Release and Draft & Review in Internet Mail
               draft-melnikov-email-draft-and-release-03

Abstract

   This document describes how draft messages intended for Draft &
   Release and Draft & Review environments can be represented in
   Internet 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 http://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 May 4, 2017.

Copyright Notice

   Copyright (c) 2016 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.

Melnikov                   Expires May 4, 2017                  [Page 1]
Internet-Draft       Draft & Release email messages         October 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   2
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Structure of a draft message  . . . . . . . . . . . . . . . .   3
   4.  Structure of a confirmation message . . . . . . . . . . . . .   3
   5.  Message-Draft header field  . . . . . . . . . . . . . . . . .   4
   6.  Registration of new IMAP Keywords . . . . . . . . . . . . . .   4
   7.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  The Message-Draft Header Field registration . . . . . . .   5
     8.2.  $DraftAuthorized IMAP keyword registration  . . . . . . .   6
     8.3.  $DraftRejected IMAP keyword registration  . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   In some environments email messages can't be released to the MTS
   (Mail Transfer System) and, thus delivered to recipients, unless they
   are authorized by one or more authorizing users (e.g.  Releasing
   Officers or Release Authorities).  This document describes how such
   Draft messages can be represented as Internet Email [RFC5322] MIME
   objects [RFC2045].

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   The formal syntax uses the Augmented Backus-Naur Form (ABNF)
   [RFC5234] notation including the core rules defined in Appendix B of
   RFC 5234 [RFC5234].  Terms not defined in this document are taken
   from [RFC5322].

2.1.  Terminology

   Drafter: Any email user that composes a message (Draft Message)
   needing authorisation before it is released to its intended
   recipients.

   Authorizing User (also Releaser or Authorizer): The mailbox of a user
   or a group of users that must inspect and authorise the release of
   Draft Message before it can be sent.  An organization may require

Melnikov                   Expires May 4, 2017                  [Page 2]
Internet-Draft       Draft & Release email messages         October 2016
Show full document text