Delivered-To Email Header Field
draft-crocker-email-deliveredto-02

Document Type Active Internet-Draft (individual in art area)
Author Dave Crocker 
Last updated 2021-02-21
Stream Internent Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd John Levine
IESG IESG state AD Evaluation::AD Followup
Action Holders
(None)
Consensus Boilerplate Yes
Telechat date
Responsible AD Murray Kucherawy
Send notices to johnl@taugh.com
Network Working Group                                    D. Crocker, Ed.
Internet-Draft                               Brandenburg InternetWorking
Intended status: Standards Track                       February 21, 2021
Expires: August 25, 2021

                    Delivered-To Email Header Field
                   draft-crocker-email-deliveredto-02

Abstract

   The address to which email is delivered might be different than any
   of the addresses shown in any of the content header fields that were
   created by the author.  The address used by the mail transport
   service is provided separately, through an envelope SMTP "RCPT TO"
   command.  Before final delivery, handling can entail a sequence of
   addresses that lead to the recipient.  It can be helpful for a
   message to have a common way to record each delivery in such a
   sequence, and to include each address used for that recipient.  This
   specification defines a header field for this information.

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 August 25, 2021.

Copyright Notice

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

Crocker                  Expires August 25, 2021                [Page 1]
Internet-Draft                    react                    February 2021

   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.  Framework & Terminology . . . . . . . . . . . . . . . . . . .   2
   3.  Delivered-To: . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Multi-hop Example . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The address to which email is delivered might be different than any
   of the addresses shown in any of the content header fields [Mail-Fmt]
   that were created by the author's Mail User Agent (MUA) [Mail-Arch].
   The address used by the Message Handling Service (MHS) is provided
   separately, through an envelope "RCPT TO" command [SMTP].

   Delivery is the final processing of an envelope address, with a
   transition of responsibility from the MHS, over to an agent
   responsible for that address (Section 4.3.3 [Mail-Arch]).  After this
   transition there might be further, fresh processing of the message,
   before reaching a final destination.  Each transition of
   responsibility, from the MHS to an agent of the addressee,
   constitutes a delivery.

   Given aliasing, mailing lists, and the like, the transit of a message
   from its author to a final recipient might include a series of
   submission/delivery events.  It can be helpful for a message to have
   a common way of indicating each delivery in the handling sequence,
   and to include each address that led to the final delivery.  One use
   can be for detecting a delivery sequence loop.

2.  Framework & Terminology

   Unless otherwise indicated, basic architecture and terminology used
   in this specification are taken from:

   o  [Mail-Arch]

Crocker                  Expires August 25, 2021                [Page 2]
Internet-Draft                    react                    February 2021

   o  [SMTP]

   o  [Mail-Fmt]

   and syntax is specified with:

   o  [ABNF]

   Normative language, per [RFC8174]:
Show full document text