RFC 7960 on Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows

rfc-editor@rfc-editor.org Thu, 29 September 2016 23:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACCC12B09C; Thu, 29 Sep 2016 16:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGOEpiaP09W7; Thu, 29 Sep 2016 16:40:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2860212B268; Thu, 29 Sep 2016 16:40:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2066BB810F9; Thu, 29 Sep 2016 16:40:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7960 on Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160929234004.2066BB810F9@rfc-editor.org>
Date: Thu, 29 Sep 2016 16:40:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Qx3FqmYUexWjDqQZrXjDcOE3q9A>
Cc: drafts-update-ref@iana.org, dmarc@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 23:40:06 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7960

        Title:      Interoperability Issues between Domain-based Message 
                    Authentication, Reporting, and Conformance (DMARC) and 
                    Indirect Email Flows 
        Author:     F. Martin, Ed.,
                    E. Lear, Ed.,
                    T. Draegen. Ed.,
                    E. Zwicky, Ed., 
                    K. Andersen, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    fmartin@linkedin.com, 
                    lear@cisco.com, 
                    tim@dmarcian.com,
                    zwicky@yahoo-inc.com, 
                    kandersen@linkedin.com
        Pages:      27
        Characters: 58739
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmarc-interoperability-18.txt

        URL:        https://www.rfc-editor.org/info/rfc7960

        DOI:        http://dx.doi.org/10.17487/RFC7960

Domain-based Message Authentication, Reporting, and Conformance
(DMARC) introduces a mechanism for expressing domain-level policies
and preferences for email message validation, disposition, and
reporting.  However, the DMARC mechanism enables potentially
disruptive interoperability issues when messages do not flow directly
from the author's administrative domain to the final Recipients.
Collectively, these email flows are referred to as "indirect email
flows".  This document describes these interoperability issues and
presents possible methods for addressing them.

This document is a product of the Domain-based Message Authentication, Reporting & Conformance Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC