A Message Header to Identify Subscription Form Mail
draft-levine-mailbomb-header-02

Document Type Active Internet-Draft (individual)
Last updated 2019-11-26
Stream (None)
Intended RFC status (None)
Formats plain text 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                                        J.R. Levine
Internet-Draft                                      Taughannock Networks
Updates: 6376 (if approved)                             26 November 2019
Intended status: Informational                                          
Expires: 29 May 2020

          A Message Header to Identify Subscription Form Mail
                    draft-levine-mailbomb-header-02

Abstract

   Many organizations have web forms that provoke an e-mail confirmation
   to the e-mail address provided in the form.  Malicious entities do
   bulk form submissions with forged addresses, resulting in mail floods
   to the holders of those addresses.  This document defines a message
   header to identify mail sent in response to web forms, so that
   recipient mail systems can better recognize and mitigate the mail
   floods.

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 29 May 2020.

Copyright Notice

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

Levine                     Expires 29 May 2020                  [Page 1]
Internet-DraftA Message Header to Identify Subscription ForNovember 2019

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The Form-Sub header field . . . . . . . . . . . . . . . . . .   3
   4.  Mail flood enhanced status code . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Provisional Message Header Registry . . . . . . . . . . .   4
     6.2.  Enhanced Status Codes . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change log . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Discussion Venue:  For the time being, discussion about this draft is
      directed to the collaboration@mailman.m3aawg.org
      (mailto:collaboration@mailman.m3aawg.org) mailing list.

   Many organizations have web forms that provoke an e-mail confirmation
   to the e-mail address provided in the form.  Malicious entities
   submit multiple forms with forged addresses, resulting in mail floods
   to those addresses.  We define a message header that identifies mail
   sent in response to web forms, so that recipient mail systems can
   better recognize and mitigate the mail floods.

   Mail systems that recognize a mail flood may defer or reject the
   mail.  We also define an SMTP enhanced status code that a mail system
   can use in a message rejection SMTP reponse to alert the sending
   system that the message was rejected due to being part of a mail
   flood.

2.  Conventions

   The terms Message Submission Agent (MSA) and Message Transfer Agent
   (MTA) are defined as in [RFC5598].

   The ABNF [RFC5234] terms CRLF, FWS, and fields are imported from
   [RFC5322].

Levine                     Expires 29 May 2020                  [Page 2]
Internet-DraftA Message Header to Identify Subscription ForNovember 2019

3.  The Form-Sub header field

   A MSA or an initial MTA adds a Form-Sub header field to indicate that
   the message was sent in response to a web form submission.  The
   header consists of a semicolon-separated list of tag=value pairs.
   The first tag-value pair is "v=1" to indicate that the header uses
   the initial version of this specification.  Receivers should ignore
   Form-Sub headers with a v= tag that indicates an unknown version.
Show full document text