Signalling one-click functionality for list email headers
draft-levine-herkula-oneclick-06

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in art area)
Last updated 2016-09-20
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd Paul Kincaid-Smith
Shepherd write-up Show (last changed 2016-09-12)
IESG IESG state In Last Call (ends 2016-10-10)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to "Paul Kincaid-Smith" <paulkincaidsmith@gmail.com>
IANA IANA review state IANA - Review Needed
Network Working Group                                          J. Levine
Internet-Draft                                      Taughannock Networks
Intended status: Standards Track                              T. Herkula
Expires: March 24, 2017                                      optivo GmbH
                                                      September 20, 2016

       Signalling one-click functionality for list email headers
                    draft-levine-herkula-oneclick-06

Abstract

   This document describes a method for signaling a one-click function
   for the list-unsubscribe email header field.  The need for this
   arises out of the actuality that mail software sometimes fetches URLs
   in mail header fields, and thereby accidentally triggers
   unsubscriptions in the case of the list-unsubscribe header field.

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 March 24, 2017.

Copyright Notice

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

Levine & Herkula         Expires March 24, 2017                 [Page 1]
Internet-Draft            One click unsubscribe           September 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction and Motivation . . . . . . . . . . . . . . . . .   2
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Mail senders  . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Mail receivers  . . . . . . . . . . . . . . . . . . . . .   5
   4.  Additional Requirements . . . . . . . . . . . . . . . . . . .   5
   5.  Header Syntax . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Simple  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.2.  Complex . . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   8
     A.1.  Changes from -05 to -06 . . . . . . . . . . . . . . . . .   8
     A.2.  Changes from -04 to -05 . . . . . . . . . . . . . . . . .   8
     A.3.  Changes from -03 to -04 . . . . . . . . . . . . . . . . .   8
     A.4.  Changes from -02 to -03 . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction and Motivation

   An [RFC2369] email header field can contain HTTPS [RFC7230] URIs.  In
   a List-Unsubscribe header field the HTTPS URI is intended to
   unsubscribe the recipient of the email from the list.  But anti-spam
   software often fetches all resources in mail header fields
   automatically, without any action by the user, and there is no
   mechanical way for a sender to tell a request made automatically by
   anti-spam software from one manually requested by a user.  To prevent
   accidental unsubscriptions, senders return landing pages with a
   confirmation step to finish the unsubscribe request that a live user
   would recognize and act on, but an automated system would not.  This
   makes the unsubscription process more complex than a single click.

   Operators of broadcast marketing lists tend to be primarily concerned
   about deliverability of their mail: whether the mail is delivered to
   the recipients and how the messages are presented, e.g., whether in
   the primary inbox or in a junk folder.  Many mail systems allow
   recipients to report mail as spam or junk, and mail from senders with
   a lot of junk reports often has poor deliverability.  Hence the
Show full document text