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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-08
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
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
Intended status: Standards Track                              T. Herkula
Expires: January 9, 2017                                     optivo GmbH
                                                            July 8, 2016

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

Abstract

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

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 January 9, 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 January 9, 2017                [Page 1]
Internet-Draft            One click unsubscribe                July 2016

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  High-Level Goals  . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Out of Scope  . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Mail senders  . . . . . . . . . . . . . . . . . . . . . .   3
     5.2.  Mail receivers  . . . . . . . . . . . . . . . . . . . . .   3
   6.  Additional Requirements . . . . . . . . . . . . . . . . . . .   4
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Simple  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.2.  Complex . . . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   An [RFC2369] email header can contain HTTP or HTTPS URIs.  In a List-
   Unsubscribe Header the HTTP or HTTPS URI should unsubscribe the
   recipient of the email from the list.  But anti-spam software often
   fetches all resources in mail headers automatically, without any
   action by the user.  As a result of this unintended malicious
   behavior, senders implement landing pages with a confirmation step to
   finish the unsubscribe request.  This document addresses this part of
   the problem, with a POST action for receivers that can be
   distinguished by senders from other requests and therefore handled as
   a one-click unsubscription.

2.  Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP14, [RFC2119].

   One-click describes an action that directly triggers a change in a
   system's state, intended to be applied only with a user's intent.

3.  High-Level Goals

   This document has several goals.

Levine & Herkula         Expires January 9, 2017                [Page 2]
Internet-Draft            One click unsubscribe                July 2016

      Allow email senders to signal "One-Click" functionality for
      specific HTTP and HTTPS URIs used in [RFC2369] email headers.

      Allow MUA designers to implement independent user interface
      features for a better user experience.
Show full document text