Nice Email Addresses for SMTPUTF8
draft-gulbrandsen-smtputf8-nice-addresses-01
Document | Type |
Replaced Internet-Draft
(mailmaint WG)
Expired & archived
|
|
---|---|---|---|
Authors | Arnt Gulbrandsen , Jiankang Yao | ||
Last updated | 2024-11-22 (Latest revision 2024-09-18) | ||
Replaced by | draft-ietf-mailmaint-interoperable-addresses | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Associated WG milestones |
|
||
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-mailmaint-interoperable-addresses | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies rules for email addresses that are flexible enough to express the addresses typically used with SMTPUTF8, while avoiding confusing or risky elements. This is one of a pair of documents: this contains recommendations for what addresses humans should use, such address provisioning sytems can restrain themselves to addresses that email valdidators accept. (This set can also be described in other ways, including "simple to cut-and-paste".) Its companion defines simpler rules, accepts more addresses, and is intended for software like MTAs. NOTE: The term 'nice' is not ideal here, and must be reconsidered or replaced before this is issued as an RFC. "Well-formed" is a candidate. "Nice" will do for now: better to argue about substance than wording.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)