Skip to main content

Experimental Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Extension for Public Suffix Domains
draft-ietf-dmarc-psd-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, alexey.melnikov@isode.com, dmarc-chairs@ietf.org, dmarc@ietf.org, draft-ietf-dmarc-psd@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Document Action: 'Experimental DMARC Extension For Public Suffix Domains' to Experimental RFC (draft-ietf-dmarc-psd-14.txt)

The IESG has approved the following document:
- 'Experimental DMARC Extension For Public Suffix Domains'
  (draft-ietf-dmarc-psd-14.txt) as Experimental RFC

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

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmarc-psd/


Ballot Text

Technical Summary

   Domain-based Message Authentication, Reporting, and Conformance
   (DMARC) permits a domain-controlling organization to express domain-
   level policies and preferences for message validation, disposition,
   and reporting, which a mail-receiving organization can use to improve
   mail handling.

   DMARC distinguishes the portion of a name that is a Public Suffix
   Domain (PSD), below which organizational domain names are created.
   The basic DMARC capability allows organizational domains to specify
   policies that apply to their subdomains, but it does not give that
   capability to PSDs.  This document describes an extension to DMARC to
   fully enable DMARC functionality for PSDs.

   Some implementations of DMARC consider a PSD to be ineligible for
   DMARC enforcement.  This specification addresses that case.

Working Group Summary

   Generally, the working group came to consensus fairly quickly about this proposal because it's fairly minimal, straightforward, and well understood.
   However, see the IESG Note below.

Document Quality

   There are several expressions of interest with respect to implementation.  There is one reference implementation.

Personnel

   Murray Kucherawy wrote the original Document Shepherd writeup, and Alexey Melnikov started IETF Last Call
   as Area Director.  Since then, their roles have swapped; Alexey is the shepherding co-chair, and Murray is the
   Area Director.

RFC Editor Note