--- 1/draft-ietf-dmarc-arc-usage-07.txt 2019-10-22 02:13:23.394641488 -0700 +++ 2/draft-ietf-dmarc-arc-usage-08.txt 2019-10-22 02:13:23.438642604 -0700 @@ -1,19 +1,19 @@ DMARC Working Group S. Jones, Ed. Internet-Draft DMARC.org Intended status: Informational K. Andersen -Expires: October 25, 2019 LinkedIn - April 23, 2019 +Expires: April 24, 2020 LinkedIn + October 22, 2019 Recommended Usage of the Authenticated Received Chain (ARC) - draft-ietf-dmarc-arc-usage-07 + draft-ietf-dmarc-arc-usage-08 Abstract The Authentication Received Chain (ARC) provides an authenticated "chain of custody" for a message, allowing each entity that handles the message to see what entities handled it before, and to see what the message's authentication assessment was at each step in the handling. But the specification does not indicate how the entities handling these messages should interpret or utilize ARC results in making decisions about message disposition. This document will @@ -27,21 +27,21 @@ 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 https://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 October 25, 2019. + This Internet-Draft will expire on April 24, 2020. Copyright Notice Copyright (c) 2019 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -345,21 +345,21 @@ the message they received had passed authentication checks. 3.8. What about ARC chains where some intermediaries are known and others are not? Validators may choose to build reputation models for ARC message handlers they have observed. Generally speaking it is more feasible to accrue positive reputation to intermediaries when they consistently send messages that are evaluated positively in terms of content and ARC chains. When messages are received with ARC chains - that are not intact, it is very difficult identify which + that are not intact, it is very difficult to identify which intermediaries may have manipulated the message or injected bad content. 3.9. What should message handlers do when they detect malicious content in messages where ARC is present? Message handlers should do what they normally do when they detect malicious content in a message - hopefully that means quarantining or discarding the message. ARC information should never make malicious content acceptable. @@ -606,49 +606,49 @@ [RFC7601] Kucherawy, M., "Message Header Field for Indicating Message Authentication Status", RFC 7601, DOI 10.17487/RFC7601, August 2015, . 7.2. Informative References [ARC] Andersen, K., Long, B., Blank, S., and M. Kucherawy, "Authenticated Received Chain (ARC) Protocol", December - 2018, . + 2018, . [ARC-MULTI] Andersen, K., Blank, S., and J. Levine, "Using Multiple Signing Algorithms with ARC", June 2018, - . + . [draft-levine-eaiauth] Levine, J., "E-mail Authentication for Internationalized - Mail", August 2018, . + Mail", August 2018, . [ENHANCED-STATUS] "IANA SMTP Enhanced Status Codes", n.d., . [I-D-7601bis] Kucherawy, M., "Message Header Field for Indicating Message Authentication Status", February 2018, - . + . [OAR] Chew, M. and M. Kucherawy, "Original-Authentication- Results Header Field", February 2012, - . + . [RFC6376] Crocker, D., Ed., Hansen, T., Ed., and M. Kucherawy, Ed., "DomainKeys Identified Mail (DKIM) Signatures", STD 76, RFC 6376, DOI 10.17487/RFC6376, September 2011, . [RFC7208] Kitterman, S., "Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1", RFC 7208, DOI 10.17487/RFC7208, April 2014, . @@ -845,19 +845,19 @@ [10] mailing list at http://lists.dmarc.org/mailman/listinfo/arc- discuss [11]. Authors' Addresses Steven M Jones (editor) DMARC.org 2419 McGee Avenue Berkeley, California 94703 USA - Email: smj@crash.com + Email: smj@dmarc.org Kurt Andersen LinkedIn 2029 Stierlin Ct. Mountain View, California 94043 USA Email: kurta@linkedin.com