|Network Working Group||E. Allman|
|Internet Draft||Sendmail, Inc.|
|Intended status: Standards Track||Cisco Systems, Inc.|
|Expires: January 2009||M. Delany|
|July 9, 2008|
DKIM Author Domain Signing Practices (ADSP)
By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
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”.
The list of current Internet-Drafts can be accessed at <http://www.ietf.org/ietf/1id-abstracts.txt>.
The list of Internet-Draft Shadow Directories can be accessed at <http://www.ietf.org/shadow.html>.
This Internet-Draft will expire in January 2009.
DomainKeys Identified Mail (DKIM) defines a domain-level authentication framework for email to permit verification of the source and contents of messages. This document specifies an adjunct mechanism to aid in assessing messages that do not contain a DKIM signature for the domain used in the author's address. It defines a record that can advertise whether they sign their outgoing mail, and how other hosts can access those records.
DomainKeys Identified Mail (DKIM) defines a mechanism by which email messages can be cryptographically signed, permitting a signing domain to claim responsibility for the introduction of a message into the mail stream. Message recipients can verify the signature by querying the signer's domain directly to retrieve the appropriate public key, and thereby confirm that the message was attested to by a party in possession of the private key for the signing domain.
However, the legacy of the Internet is such that not all messages will be signed, and the absence of a signature on a message is not an a priori indication of forgery. In fact, during early phases of deployment it is very likely that most messages will remain unsigned. However, some domains might decide to sign all of their outgoing mail, for example, to protect their brand names. It is desirable for such domains to be able to advertise that fact to other hosts. This is the topic of Author Domain Signing Practices (ADSP).
Hosts implementing this specification can inquire what Author Signing Practices a domain advertises. This inquiry is called an Author Signing Practices check.
The basic requirements for ADSP are given in [RFC5016]. This document refers extensively to [RFC4871] and assumes the reader is familiar with it.
Some terminology used herein is derived directly from [RFC4871]. In several cases, references in that document to Sender have been changed to Author here, to emphasize the relationship to the Author address(es) in the From: header field described in [RFC2822]. Briefly,
A "Valid Signature" is any signature on a message which correctly verifies using the procedure described in section 6.1 of [RFC4871].
An "Author Address" is an email address in the From header field of a message [RFC2822]. If the From header field contains multiple addresses, the message has multiple Author Addresses.
An "Author Domain" is everything to the right of the "@" in an Author Address (excluding the "@" itself).
An "Alleged Author" is an Author Address of a message; it is "alleged" because it has not yet been verified.
"Author Domain Signing Practices" (or just "practices") consist of a machine-readable record published by the domain of an Alleged Author which includes statements about the domain's practices with respect to mail it sends with its domain in the From: line.
An "Author Signature" is any Valid Signature where the identity of the user or agent on behalf of which the message is signed (listed in the i= tag or its default value from the d= tag) matches an Author Address in the message. When the identity of the user or agent includes a Local-part, the identities match if the Local-parts are the same string, and the domains are the same string. Otherwise, the identities match if the domains are the same string. Following [RFC2821], Local-part comparisons are case sensitive, domain comparisons are case insensitive.
For example, if a message has a Valid Signature, with the DKIM-Signature field containing email@example.com, then domain.example is asserting that it takes responsibility for the message. If the message's From: field contains the address firstname.lastname@example.org and an ADSP query produces a dkim=all or dkim=discardable result, that would mean that the message does not have a valid Author Signature. Even though the message is signed by the same domain, it fails to satisfy ADSP.
Domain owners can publish ADSP information via a query mechanism such as the Domain Name System; specific details are given in Section 4.1.
Hosts can look up the ADSP information of the domain(s) specified by the Author Address(es) as described in Section 4.3. If a message has multiple Author Addresses the ADSP lookups SHOULD be performed independently on each address. This standard does not address the process a host might use to combine the lookup results.
ADSP as defined in this document is bound to DNS. For this reason, ADSP is applicable only to Author Domains with appropriate DNS records (see Note below). The handling of other Author Domains is outside the scope of this document. However, attackers may use such domain names in a deliberate attempt to sidestep an organization's ADSP policy statements. It is up to the ADSP verifier implementation to return an appropriate error result for Author Domains outside the scope of ADSP.
Depending on the Author Domain(s) and the signatures in a message, a recipient gets varying amounts of useful information from each ADSP lookup.
An ADSP lookup for an Author Address produces one of four possible results:
ADSP records are published using the DNS TXT resource record type.
The RDATA for ADSP resource records is textual in format, with specific syntax and semantics relating to their role in describing ADSP. The "Tag=Value List" syntax described in section 3.2 of [RFC4871] is used. Records not in compliance with that syntax or the syntax of individual tags described in Section 4.3 MUST be ignored (considered equivalent to a NODATA result) for purposes of ADSP, although they MAY cause the logging of warning messages via an appropriate system logging mechanism. If the RDATA contains multiple character strings, the strings are logically concatenated with no delimiters between the strings.
The ADSP record for a domain is published at a location in the domain's DNS hierarchy prefixed by _adsp._domainkey.; e.g., the ADSP record for example.com would be a TXT record that is published at _adsp._domainkey.example.com. A domain MUST NOT publish more than one ADSP record; the semantics of an ADSP lookup that returns multiple ADSP records for a single domain are undefined. (Note that example.com and mail.example.com are different domains.)
ADSP is intended to apply to all mail sent using the domain name string of an Alleged Author.
Wildcards within a domain publishing ADSP records pose a particular problem. This is discussed in more detail in Section 6.3.
ADSP records use the "tag=value" syntax described in section 3.2 of [RFC4871].
Tags used in ADSP records are described below. Unrecognized tags MUST be ignored. In the ABNF below, the FWS token is imported from [RFC4871]. The ALPHA and DIGIT tokens are imported from [RFC5234].
adsp-dkim-tag = %x64.6b.69.6d *FWS "=" *FWS ("unknown" / "all" / "discardable")
Hosts doing an ADSP lookup MUST produce a result that is semantically equivalent to applying the following steps in the order listed below. In practice, these steps can be performed in parallel in order to improve performance. However, implementations SHOULD avoid doing unnecessary DNS lookups.
For the purposes of this section a "valid ADSP record" is one that is both syntactically and semantically correct; in particular, it matches the ABNF for a tag-list and includes a defined dkim= tag.
ADSP adds the following namespaces to the IANA registry. In all cases, new values are assigned only for values that have been documented in a published RFC that has IETF Consensus [RFC2434].
An ADSP record provides for a list of specification tags. IANA has established the ADSP Specification Tag Registry for specification tags that can be used in ADSP fields.
The initial entry in the registry is:
+------+-----------------+ | TYPE | REFERENCE | +------+-----------------+ | dkim | (this document) | +------+-----------------+
ADSP Specification Tag Registry Initial Values
The dkim= tag spec, defined in Section 4.2.1, provides for a value specifying Outbound Signing Practices. IANA has established the ADSP Outbound Signing Practices Registry for Outbound Signing Practices.
The initial entries in the registry comprise:
+-------------+-----------------+ | TYPE | REFERENCE | +-------------+-----------------+ | unknown | (this document) | | all | (this document) | | discardable | (this document) | +-------------+-----------------+
ADSP Outbound Signing Practices Registry Initial Values
Security considerations in the ADSP are mostly related to attempts on the part of malicious senders to represent themselves as authors for whom they are not authorized to send mail, often in an attempt to defraud either the recipient or an Alleged Author.
Additional security considerations regarding Author Domain Signing Practices are found in the DKIM threat analysis [RFC4686].
Email recipients often have a core set of content authors that they already trust. Common examples include financial institutions with which they have an existing relationship and Internet web transaction sites with which they conduct business.
Email abuse often seeks to exploit a legitimate email author's name-recognition among recipients, by using the author's domain name in the From: header field. Especially since many popular MUAs do not display the author's email address, there is no empirical evidence of the extent that this particular unauthorized use of a domain name contributes to recipient deception or that eliminating it will have significant effect.
However, closing this exploit could facilitate some types of optimized processing by receive-side message filtering engines, since it could permit them to maintain higher-confidence assertions about From: header field uses of a domain, when the occurrence is authorized.
Unauthorized uses of domain names occur elsewhere in messages, as do unauthorized uses of organizations' names. These attacks are outside the scope of this specification.
ADSP does not provide any benefit--nor, indeed, have any effect at all--unless an external system acts upon the verdict, either by treating the message differently during the delivery process or by showing some indicator to the end recipient. Such a system is out of scope for this specification.
ADSP checkers may perform multiple DNS lookups per Alleged Author Domain. Since these lookups are driven by domain names in email message headers of possibly fraudulent email, legitimate ADSP checkers can become participants in traffic multiplication attacks.
An attacker might attack the DNS infrastructure in an attempt to impersonate ADSP records to influence a receiver's decision on how it will handle mail. However, such an attacker is more likely to attack at a higher level, e.g., redirecting A or MX record lookups in order to capture traffic that was legitimately intended for the target domain. These DNS security issues are addressed by DNSSEC [RFC4033].
Because ADSP operates within the framework of the legacy e-mail system, the default result in the absence of an ADSP record is that the domain does not sign all of its messages. It is therefore important that the ADSP clients distinguish a DNS failure such as SERVFAIL from other DNS errors so that appropriate actions can be taken.
If a domain contains wildcards, then any name that matches the wildcard according to [RFC4592] is potentially a valid mail domain eligible for ADSP. It is possible to add a wildcard TXT record alongside a wildcard MX that will provide suitable ADSP records for any domain chosen by an attacker, since if the wildcard synthesizes chosen-name.example.com IN MX, it will then also synthesize _adsp._domainkey.chosen-name.example.com IN TXT. However multiple wildcard TXT records produce an undefined ADSP result, which means you cannot also publish both ADSP records and records for any other TXT-using protocol (such as SPF) for a wildcard domain.
|[RFC2119]||Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997.|
|[RFC2434]||Narten, T. and H.T. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs”, BCP 26, RFC 2434, October 1998.|
|[RFC2822]||Resnick, P., “Internet Message Format”, RFC 2822, April 2001.|
|[RFC4033]||Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, “DNS Security Introduction and Requirements”, RFC 4033, March 2005.|
|[RFC4686]||Fenton, J., “Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)”, RFC 4686, September 2006.|
|[RFC4871]||Allman, E., Callas, J., Delany, M., Libbey, M., Fenton, J., and M. Thomas, “DomainKeys Identified Mail (DKIM) Signatures”, RFC 4871, May 2007.|
|[RFC5234]||Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF”, STD 68, RFC 5234, January 2008.|
|[RFC2821]||Klensin, J., “Simple Mail Transfer Protocol”, RFC 2821, April 2001.|
|[RFC5016]||Thomas, M., “Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol”, RFC 5016, October 2007.|
These examples are intended to illustrate typical uses of ADSP. They are not intended to be exhaustive, nor to apply to every domain's or mail system's individual situation.
Domain managers are advised to consider the ways that mail processing can modify messages in ways that will invalidate an existing DKIM signature, such as mailing lists, courtesy forwarders, and other paths that could add or modify headers, or modify the message body. In that case, if the modifications invalidate the DKIM signature, recipient hosts will consider the mail not to have an Author Signature, even though the signature was present when the mail was originally sent.
A common mail system configuration handles all of a domain's users' incoming and outgoing mail through a single MTA or group of MTAs. In that case, the MTA(s) can be configured to sign outgoing mail with an Author Signature.
In this situation it might be appropriate to publish an ADSP record for the domain containing "all", depending on whether the users also send mail through other paths that do not apply an Author Signature. Such paths could include MTAs at hotels or hotspot networks used by travelling users, or web sites that provide "mail an article" features.
Another common configuration uses a domain solely for bulk or broadcast mail, with no individual human users, again typically sending all the mail through a single MTA or group of MTAs that can apply an Author Signature. In this case, the domain's management can be confident that all of its outgoing mail will be sent through the signing MTA. Lacking individual users, the domain is unlikely to participate in mailing lists, but could still send mail through other paths that might invalidate signatures.
Domain owners often use specialist mailing providers to send their bulk mail. In that case, the mailing provider needs access to a suitable signing key in order to apply an Author Signature. One possible route would be for the domain owner to generate the key and give it to the mailing provider. Another would be for the domain to delegate a subdomain to the mailing provider, for example, bigbank.example might delegate email.bigbank.example to such a provider. In that case, the provider can generate the keys and DKIM DNS records itself and use the subdomain in the Author address in the mail.
Regardless of the DNS and key management strategy chosen, whoever maintains the DKIM records for the domain could also install an ADSP record containing "all".
In some cases, a domain might sign all of its outgoing mail with an Author Signature, but prefer that recipient systems discard mail without a valid Author Signature to avoid confusion from mail sent from sources that do not apply an Author Signature. (This latter kind of mail is sometimes loosely called "forgeries".) In that case, it might be appropriate to publish an ADSP record containing "discardable". Note that a domain SHOULD NOT publish a "discardable" record if it wishes to maximize the likelihood that mail from the domain is delivered, since it could cause some fraction of the mail the domain sends to be discarded.
Another common use case is for a third party to enter into an agreement whereby that third party will send bulk or other mail on behalf of a designated author or author domain, using that domain in the RFC2822 From: or other headers. Due to the many and varied complexities of such agreements, third party signing is not addressed in this specification.
If a domain sends no mail at all, it can safely publish a "discardable" ADSP record, since any mail with an author address in the domain is a forgery.
This document greatly benefited from comments by Steve Atkins, Jon Callas, Dave Crocker, JD Falk, Arvel Hathcock, Ellen Siegel, Michael Thomas, and Wietse Venema.
NOTE TO RFC EDITOR: This section may be removed upon publication of this document as an RFC.
From a "diff" perspective, the changes are extensive. Semantically, the changes are:
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at <http://www.ietf.org/ipr>.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at email@example.com.