Mailing Lists and non-ASCII Addresses
draft-ietf-eai-mailinglistbis-04

The information below is for an old version of the document
Document Type Active Internet-Draft (eai WG)
Last updated 2012-07-13
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state AD is watching
Telechat date
Responsible AD Pete Resnick
Send notices to eai-chairs@tools.ietf.org, draft-ietf-eai-mailinglistbis@tools.ietf.org
EAI                                                            J. Levine
Internet-Draft                                      Taughannock Networks
Intended status: Informational                                R. Gellens
Expires: December 31, 2012                         Qualcomm Incorporated
                                                               July 2012

                 Mailing Lists and non-ASCII Addresses
                    draft-ietf-eai-mailinglistbis-04

Abstract

   This document describes considerations for mailing lists with the
   introduction of non-ASCII UTF-8 email addresses.  It outlines some
   possible scenarios for handling lists with mixtures of non-ASCII and
   traditional addresses, but does not specify protocol changes or offer
   implementation or deployment advice.

   *NOTE TO REVIEWERS: Missing or odd-looking references between
   sections are due to bugs in xml2rfc.  The XML is OK, and the HTML
   output looks reasonable.*

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 December 31, 2012.

Copyright Notice

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

Levine & Gellens       Expires December 31, 2012                [Page 1]
Internet-Draft   Mailing Lists and non-ASCII Addresses         July 2012

   extracted from this document must 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
     1.1.  Mailing list header additions and modifications  . . . . .  3
     1.2.  Non-ASCII email addresses  . . . . . . . . . . . . . . . .  3
   2.  Scenarios Involving Mailing Lists  . . . . . . . . . . . . . .  4
     2.1.  Fully SMTPUTF8 lists . . . . . . . . . . . . . . . . . . .  4
     2.2.  Mixed SMTPUTF8 and ASCII lists . . . . . . . . . . . . . .  5
     2.3.  SMTP issues  . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  List headers . . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  SMTPUTF8 list headers  . . . . . . . . . . . . . . . . . .  6
     3.2.  Downgrading list headers . . . . . . . . . . . . . . . . .  7
     3.3.  Subscribers' addresses in downgraded headers . . . . . . .  8
   4.  Security considerations  . . . . . . . . . . . . . . . . . . .  8
   5.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     5.1.  Normative References . . . . . . . . . . . . . . . . . . .  8
     5.2.  Informative References . . . . . . . . . . . . . . . . . .  8
   Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . .  9
     Appendix A.1.  Change from -03 to -04  . . . . . . . . . . . . .  9
     Appendix A.2.  Change from -02 to -03  . . . . . . . . . . . . .  9
     Appendix A.3.  Changes up to -02 . . . . . . . . . . . . . . . .  9
     Appendix A.4.  Changes up to -00 . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

1.  Introduction

   This document describes considerations for mailing lists with the
   introduction of non-ASCII UTF-8 email addresses.  The usage of such
   addresses is described in [RFC6530].

   Mailing lists are an important part of email usage and collaborative
   communications.  The introduction of internationalized email
   addresses affects mailing lists in three main areas: (1) transport
   (receiving and sending messages); (2) message headers of received and
   retransmitted messages; and (3) mailing list operational policies.

   A mailing list is a mechanism that distributes a message to multiple
   recipients when the originator sends it to a single address.  An
   agent, usually software rather than a person, at that single address
Show full document text