The Document Shepherd for this document is Paul Kincaid-Smith. The responsible Area Director is Alexey Melnikov.
This document describes a method for signaling a one-click function for the List-Unsubscribe email header. The proposed method will reduce accidental unsubscribes that occur when some mail software fetches URLs in mail headers, thereby accidentally triggering unintended unsubscriptions.
2. Review and Consensus
This document represents the consensus of a M3AAWG.org working group and has incorporated recommendations made on the IETF dispatch list. All technical issues raised have been resolved. I have no concerns about the level of review this document has received.
The following two questions were discussed in detail on the dispatch list. The latter was incorporated into Draft 04.
Question #1: Should JSON be used to structure the arguments to the unsubscribe request?
Answer: To simplify implementation (and thus adoption of this proposed RFC) the unsubscribe arguments will be passed as simple tags and strings (which are set by the bulk sender anyway, and it’s their servers that will process these tags and strings.)
Resolution: Don’t use JSON to pass unsubscribe arguments because it’ll increase the complexity of the server-side implementation required by bulk mail providers.
Question #2: Why does the POST need a content-type of application/x-www-form-urlencoded?
Answer: multipart/form-data is an option
Resolution: Draft 04 adopts the recommendation a content-type of multipart/form-data
At least one major webmail provider intends to implement the List-Unsubscribe-Post mechanism described in this document in 2016, and expressed support on the IETF dispatch list.
3. Intellectual Property
Each author has confirmed conformance with BCPs 78 and 79.
4. Other Points
There are no “downward references” in this document. All normative RFCs referenced are either established standards or are on the standards track.