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

Document Type Active Internet-Draft (individual)
Last updated 2017-10-05
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                                          J. Levine
Internet-Draft                                      Taughannock Networks
Updates: 6376 (if approved)                              October 5, 2017
Intended status: Informational
Expires: April 8, 2018

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

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 April 8, 2018.

Copyright Notice

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

Levine                    Expires April 8, 2018                 [Page 1]
Internet-Draft                                              October 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The Form-Sub header field . . . . . . . . . . . . . . . . . .   3
   4.  Mail flood enhanced status code . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Provisional Message Header Registry . . . . . . . . . . .   4
     6.2.  Enhanced Status Codes . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   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 [1] 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 April 8, 2018                 [Page 2]
Internet-Draft                                              October 2017

3.  The Form-Sub header field

   A MSA or an initial MTA adds a Form-Sub header field to indicate that
Show full document text