datatracker.ietf.org
Sign in
Version 5.3.1, 2014-04-16
Report a bug

The Require-Recipient-Valid-Since Header Field and SMTP Service Extension
draft-ietf-appsawg-rrvs-header-field-11

Document type: Active Internet-Draft (appsawg WG)
Document stream: IETF
Last updated: 2014-04-21 (latest revision 2014-04-19)
Intended RFC status: Proposed Standard
Other versions: plain text, xml, pdf, html

IETF State: Submitted to IESG for Publication Jan 2014
Consensus: Yes
Document shepherd: Trent Adams
Shepherd Write-Up: Last changed 2014-01-28

IESG State: RFC Ed Queue
IANA Action State: RFC-Ed-Ack
RFC Editor State: EDIT
Responsible AD: Barry Leiba
Send notices to: appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-rrvs-header-field@tools.ietf.org, jtrentadams@gmail.com

Network Working Group                                           W. Mills
Internet-Draft                                               Yahoo! Inc.
Intended status: Standards Track                            M. Kucherawy
Expires: October 21, 2014                                 Facebook, Inc.
                                                          April 19, 2014

    The Require-Recipient-Valid-Since Header Field and SMTP Service
                               Extension
                draft-ietf-appsawg-rrvs-header-field-11

Abstract

   This document defines an extension for the Simple Mail Transfer
   Protocol called RRVS, to provide a method for senders to indicate to
   receivers a point in time when the the ownership of the target
   mailbox was known to the sender.  This can be used to detect changes
   of mailbox ownership, and thus prevent mail from being delivered to
   the wrong party.  This document also defines a header field called
   Require-Recipient-Valid-Since that can be used to tunnel the request
   through servers that do not support the extension.

   The intended use of these facilities is on automatically generated
   messages, such as account statements or password change instructions,
   that might contain sensitive information, though it may also be
   useful in other applications.

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 October 21, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Mills & Kucherawy       Expires October 21, 2014                [Page 1]
Internet-Draft        Require-Recipient-Valid-Since           April 2014

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Description  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  The 'RRVS' SMTP Extension  . . . . . . . . . . . . . . . .  5
     3.2.  The 'Require-Recipient-Valid-Since' Header Field . . . . .  6
     3.3.  Timestamps . . . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Use By Generators  . . . . . . . . . . . . . . . . . . . . . .  6
   5.  Handling By Receivers  . . . . . . . . . . . . . . . . . . . .  7
     5.1.  SMTP Extension Used  . . . . . . . . . . . . . . . . . . .  8
       5.1.1.  Relays . . . . . . . . . . . . . . . . . . . . . . . .  9
     5.2.  Header Field Used  . . . . . . . . . . . . . . . . . . . .  9
       5.2.1.  Design Choices . . . . . . . . . . . . . . . . . . . . 10
     5.3.  Clock Synchronization  . . . . . . . . . . . . . . . . . . 11
   6.  Relaying Without RRVS Support  . . . . . . . . . . . . . . . . 11
     6.1.  Header Field Conversion  . . . . . . . . . . . . . . . . . 12
   7.  Header Field with Multiple Recipients  . . . . . . . . . . . . 13
   8.  Special Use Addresses  . . . . . . . . . . . . . . . . . . . . 13
     8.1.  Mailing Lists  . . . . . . . . . . . . . . . . . . . . . . 14
     8.2.  Single-Recipient Aliases . . . . . . . . . . . . . . . . . 14
     8.3.  Multiple-Recipient Aliases . . . . . . . . . . . . . . . . 14
     8.4.  Confidential Forwarding Addresses  . . . . . . . . . . . . 15
     8.5.  Suggested Mailing List Enhancements  . . . . . . . . . . . 15
   9.  Continuous Ownership . . . . . . . . . . . . . . . . . . . . . 15
   10. Digital Signatures . . . . . . . . . . . . . . . . . . . . . . 16
   11. Authentication-Results Definitions . . . . . . . . . . . . . . 16
   12. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     12.1. SMTP Extension Example . . . . . . . . . . . . . . . . . . 17

[include full document text]