Multicast Email (MULE) over Allied Communications Publication (ACP) 142
draft-melnikov-email-over-pmul-08

Document Type Active Internet-Draft (individual)
Last updated 2018-10-10 (latest revision 2018-09-01)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf html bibtex
IETF conflict review conflict-review-melnikov-email-over-pmul
Stream ISE state Sent to the RFC Editor
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2018-08-19)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state IANA - Not OK
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
Network Working Group                                          D. Wilson
Internet-Draft                                          A. Melnikov, Ed.
Intended status: Informational                                 Isode Ltd
Expires: March 5, 2019                                 September 1, 2018

Multicast Email (MULE) over Allied Communications Publication (ACP) 142
                   draft-melnikov-email-over-pmul-08

Abstract

   Allied Communications Publication (ACP) 142 defines P_MUL, which is a
   protocol for reliable multicast suitable for bandwidth constrained
   and delayed acknowledgement (Emissions Control or "EMCON")
   environments running over UDP.  This document defines an application
   protocol called MULE (Multicast Email) for transferring of Internet
   Mail messages (as described in RFC 5322) over P_MUL (as defined in
   ACP 142A).  MULE enables Message Transfer Agent (MTA) to MTA transfer
   and doesn't provide a service similar to SMTP Submission (as
   described in RFC 6409).

   This document explains how MULE can be used in conjunction with
   Simple Mail Transfer Protocol (SMTP, RFC 5321), including some common
   SMTP extensions, to provide an alternate MTA to MTA transfer
   mechanism.

   This is not an IETF specification, but describes an existing
   implementation.  It is provided in order to facilitate interoperable
   implementations and third-party diagnostics.

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 March 5, 2019.

Wilson & Melnikov         Expires March 5, 2019                 [Page 1]
Internet-Draft             Email over ACP 142             September 2018

Copyright Notice

   Copyright (c) 2018 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 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
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   4
   3.  MULE  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  BSMTP-like Payload construction . . . . . . . . . . . . .   5
     3.2.  Payload compression . . . . . . . . . . . . . . . . . . .   7
     3.3.  Error handling  . . . . . . . . . . . . . . . . . . . . .   9
   4.  Gatewaying from Internet Mail to MULE . . . . . . . . . . . .   9
     4.1.  Use of BDAT . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  Gatewaying from MULE to Internet Mail . . . . . . . . . . . .  10
     5.1.  Handling of ESMTP extensions and Error handling . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  SMTP Extension Support in MULE  . . . . . . . . . . . . .  11
     6.2.  SMTP Extension Support in MULE  . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   P_MUL [ACP142A] is a transport protocol for reliable multicast in
   bandwidth constrained and delayed acknowledgement environments
   running on top of UDP.  This document defines an application protocol
   called MULE for transferring Internet Mail messages [RFC5322] over
   ACP 142 P_MUL.  The objectives of MULE are first to take advantage of
   the bandwidth saving feature of using the multicast service as
   supported by modern computer networks and second to allow message
   transfer under EMCON (Emission Control) conditions.  EMCON or "Radio

Wilson & Melnikov         Expires March 5, 2019                 [Page 2]
Show full document text