draft-ietf-dmarc-eaiauth-01.txt   draft-ietf-dmarc-eaiauth-02.txt 
Network Working Group J. Levine Network Working Group J. Levine
Internet-Draft Taughannock Networks Internet-Draft Taughannock Networks
Updates: 6376, 7208, 7489 (if approved) February 8, 2019 Updates: 6376, 7208, 7489 (if approved) February 22, 2019
Intended status: Standards Track Intended status: Standards Track
Expires: August 12, 2019 Expires: August 26, 2019
E-mail Authentication for Internationalized Mail E-mail Authentication for Internationalized Mail
draft-ietf-dmarc-eaiauth-01 draft-ietf-dmarc-eaiauth-02
Abstract Abstract
SPF, DKIM, and DMARC enable a domain owner to publish e-mail SPF (RFC7208), DKIM (RFC6376), and DMARC (RFC7489) enable a domain
authentication and policy information in the DNS. In owner to publish e-mail authentication and policy information in the
internationalized e-mail, domain names can occur both as U-labels and DNS. In internationalized e-mail, domain names can occur both as
A-labels. The Authentication-Results header reports the result of U-labels and A-labels. The Authentication-Results header reports the
authentication checks made with SPF, DKIM, DMARC, and other schemes. result of authentication checks made with SPF, DKIM, DMARC, and other
This specification clarifies when to use which form of domain names schemes. This specification updates the SPF, DKIM, and DMARC
when using SPF, DKIM, and DMARC and when creating Authentication- specifications to clarify which form of internationalized domain
Results headers. names to use in those specifications, and when creating
Authentication-Results headers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 12, 2019. This Internet-Draft will expire on August 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 26
5. DKIM and internationalized mail . . . . . . . . . . . . . . . 4 5. DKIM and internationalized mail . . . . . . . . . . . . . . . 4
6. DMARC and internationalized mail . . . . . . . . . . . . . . 4 6. DMARC and internationalized mail . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9. Normative References . . . . . . . . . . . . . . . . . . . . 5 9. Normative References . . . . . . . . . . . . . . . . . . . . 5
Appendix A. Change history . . . . . . . . . . . . . . . . . . . 6 Appendix A. Change history . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
SPF, DKIM, and DMARC enable a domain owner to publish e-mail SPF [RFC7208], DKIM [RFC6376], and DMARC [RFC7489] enable a domain
authentication and policy information in the DNS. SPF primarily owner to publish e-mail authentication and policy information in the
publishes information about what host addresses are authorized to DNS. SPF primarily publishes information about what host addresses
send mail for a domain. DKIM places cryptographic signatures on are authorized to send mail for a domain. DKIM places cryptographic
e-mail messages, with the validation keys published in the DNS. signatures on e-mail messages, with the validation keys published in
DMARC publishes policy information related to the domain in the From: the DNS. DMARC publishes policy information related to the domain in
header of e-mail messages. the From: header of e-mail messages.
In conventional e-mail, all domain names are ASCII in all contexts so In conventional e-mail, all domain names are ASCII in all contexts so
there is no question about the representation of the domain names. there is no question about the representation of the domain names.
All internationalized domain names are represented as A-labels All internationalized domain names are represented as A-labels
[RFC5890] in unencoded message bodies, in SMTP sessions, and in the [RFC5890] in unencoded message bodies, in SMTP sessions, and in the
DNS. Internationalized mail [RFC6530] allows U-labels in SMTP DNS. Internationalized mail [RFC6530] allows U-labels in SMTP
sessions [RFC6531] and in message headers [RFC6532]. sessions [RFC6531] and in message headers [RFC6532].
Every U-label is equivalent to an A-label, so in principle the choice Every U-label is equivalent to an A-label, so in principle the choice
of label format should not cause any ambiguities. But in practice, of label format should not cause any ambiguities. But in practice,
consistent use of label formats will make it more likely that mail consistent use of label formats will make it more likely that mail
senders' and receivers' code interoperates. senders' and receivers' code interoperates.
Internationalized mail also allows UTF-8 characters in the local Internationalized mail also allows UTF-8 characters in the local
parts of mailbox names, which were historically only ASCII. parts of mailbox names, which were historically only ASCII.
2. Definitions 2. Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" when "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
written in upper case in in this document are to be interpreted as "OPTIONAL" in this document are to be interpreted as described in BCP
described in [RFC2119] and [RFC8174]. 14 [RFC2119] and [RFC8174]. when they appear in all capitals, as
shown here.
The term IDN, for Internationalized Domain Name, refers to a domain The term IDN, for Internationalized Domain Name, refers to a domain
name containing either U-labels or A-labels. name containing either U-labels or A-labels.
Since DMARC is not currently a standards track protocol, this Since DMARC is not currently a standards track protocol, this
specification offers advice rather than requirements for DMARC. specification offers advice rather than requirements for DMARC.
3. General principles 3. General principles
In headers in EAI mail messages, domain names that were restricted to In headers in EAI mail messages, domain names that were restricted to
skipping to change at page 6, line 25 skipping to change at page 6, line 25
Message Authentication, Reporting, and Conformance Message Authentication, Reporting, and Conformance
(DMARC)", RFC 7489, DOI 10.17487/RFC7489, March 2015, (DMARC)", RFC 7489, DOI 10.17487/RFC7489, March 2015,
<https://www.rfc-editor.org/info/rfc7489>. <https://www.rfc-editor.org/info/rfc7489>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Appendix A. Change history Appendix A. Change history
01 to 02 update references
00 to 01 Relaxed canon, Typos 00 to 01 Relaxed canon, Typos
00 First WG version 00 First WG version
Author's Address Author's Address
John Levine John Levine
Taughannock Networks Taughannock Networks
PO Box 727 PO Box 727
Trumansburg, NY 14886 Trumansburg, NY 14886
 End of changes. 8 change blocks. 
22 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/