Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define what it means to have implemented DMARC #96

Closed
ietf-svn-bot opened this issue May 3, 2020 · 23 comments
Closed

Define what it means to have implemented DMARC #96

ietf-svn-bot opened this issue May 3, 2020 · 23 comments

Comments

@ietf-svn-bot
Copy link

keyword_clarify owner:todd.herr@valimail.com type_enhancement | by seth@sethblank.com


In particular:

  • What does it mean to implement DMARC as a domain owner? Here, we should specifically define "Enforcement" -- the point at which only authenticated mail can be sent from the domain.

  • What does it mean to implement DMARC as a receiver? Here, that DMARC and ARC are validated and reports are sent?

  • What does it mean to implement DMARC as an intermediary? That DMARC and ARC are validated?


Issue migrated from trac:66 at 2022-01-24 16:17:54 +0000

@ietf-svn-bot
Copy link
Author

@seth@sethblank.com changed status from new to assigned

@ietf-svn-bot
Copy link
Author

@seth@sethblank.com removed owner (was draft-ietf-dmarc-rfc7601bis@ietf.org)

@ietf-svn-bot
Copy link
Author

@seth@sethblank.com changed component from rfc7601bis to dmarc-bis

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed status from assigned to accepted

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com set owner to todd.herr@valimail.com

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com commented


Not sure where to put it, but here's some proposed text:

What Does It Mean To Have Implemented DMARC?

Domain owners, intermediaries, and mail receivers can all claim to implement DMARC, but what that means will depend on their role in the transmission of mail. To remove any ambiguity from the claims, this document specifies the following minimum criteria that must be met for each agent to rightly claim to be "implementing DMARC".

Domain Owner: To implement DMARC, a domain owner MUST configure its domain to request that unauthenticated mail be rejected or at least treated with suspicion. This means that it MUST publish a policy record that:

  • Has a p tag with a value of 'quarantine' or 'reject'
  • Has a rua tag with at least one valid URI
  • If applicable, has an sp tag with a value of 'quarantine' or 'reject'

While 'none' is a syntactically valid value for both the p and sp tags, the practical value of either the p tag or sp tag being 'none' means that the domain owner is still gathering information about mail flows for the domain or sub-domains, and is not yet ready to commit to requesting that unauthenticated mail receive different handling than authenticated mail.

Intermediary: To implement DMARC, an intermediary MUST do the following before passing the message to the next hop or rejecting it as appropriate:

  • Perform DMARC validation checks on inbound mail
  • Perform validation on any ARC header sets present in the message when it arrives
  • Record the results of its authentication checks in a signed and sealed ARC header set

Mail Receiver: To implement DMARC, a mail receiver MUST do the following:

  • Perform DMARC validation checks on inbound mail
  • Perform validation checks on any ARC header sets present in the message when it arrives
  • Send aggregate reports to domain owners at least every 24 hours when a minimum of 100 messages with that domain in the visible From header have been seen during the reporting period

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed status from accepted to started

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com commented


Added proposed text from comment 3 as section 4.4, part of the Overview section

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed _comment0 which not transferred by tractive

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed status from started to closed

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com set resolution to fixed

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com commented


pushed to github and merged to main branch

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed status from closed to new

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com removed resolution (was fixed)

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com commented


Reopening because it makes more sense to put this in Section 8, Minimum Implementations, which was already there.

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com commented


Moved stuff to section 8 as proposed replacement text.

Pushed to github and merged to main branch.

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed status from new to accepted

@ietf-svn-bot
Copy link
Author

@todd.herr@valimail.com changed status from accepted to infoneeded

@toddherr toddherr transferred this issue from ietf-wg-dmarc/dmarc-draftissues Jul 28, 2022
@toddherr
Copy link
Contributor

There are extensive sections, specifically Domain Owner Actions and Mail Receiver Actions, that describe but do not necessarily mandate activities for those roles to participate in DMARC.

There is currently nothing for intermediaries.

@toddherr toddherr transferred this issue from ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis Jul 28, 2022
@toddherr toddherr transferred this issue from ietf-wg-dmarc/draft-ieft-dmarc-ops-deployment Jul 28, 2022
@kitterma
Copy link

kitterma commented Aug 5, 2022

I think once we have the discussion that was started at the meeting on what to say about mailing lists, anything related to intermediaries will naturally be addressed. I don't know that you need to keep an issue open waiting for it.

@toddherr
Copy link
Contributor

I believe there is sufficient text in the document in the Domain Owner Actions and Mail Receiver Actions sections to describe what it means to have implemented DMARC, and I recommend closing this ticket.

@kitterma
Copy link

kitterma commented Feb 28, 2024 via email

@toddherr
Copy link
Contributor

Chair concurs with closing ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants