Hi Murray & Elizabeth, thanks for wrestling this through the process. The Working Group can now adopt this as input.
/goes off to figure out which buttons need to be pushed =- Tim > On Mar 18, 2015, at 4:08 PM, Murray S. Kucherawy <[email protected]> wrote: > > FYI: > > ---------- Forwarded message ---------- > From: <[email protected] <mailto:[email protected]>> > Date: Wed, Mar 18, 2015 at 1:04 PM > Subject: RFC 7489 on Domain-based Message Authentication, Reporting, and > Conformance (DMARC) > To: [email protected] <mailto:[email protected]>, > [email protected] <mailto:[email protected]> > Cc: [email protected] <mailto:[email protected]>, > [email protected] <mailto:[email protected]> > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 7489 > > Title: Domain-based Message Authentication, Reporting, and > Conformance (DMARC) > Author: M. Kucherawy, Ed., > E. Zwicky, Ed. > Status: Informational > Stream: Independent > Date: March 2015 > Mailbox: [email protected] <mailto:[email protected]>, > [email protected] <mailto:[email protected]> > Pages: 73 > Characters: 162707 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-kucherawy-dmarc-base-12.txt > > URL: https://www.rfc-editor.org/info/rfc7489 > <https://www.rfc-editor.org/info/rfc7489> > > Domain-based Message Authentication, Reporting, and Conformance > (DMARC) is a scalable mechanism by which a mail-originating > organization can express domain-level policies and preferences for > message validation, disposition, and reporting, that a mail-receiving > organization can use to improve mail handling. > > Originators of Internet Mail need to be able to associate reliable > and authenticated domain identifiers with messages, communicate > policies about messages that use those identifiers, and report about > mail using those identifiers. These abilities have several benefits: > Receivers can provide feedback to Domain Owners about the use of > their domains; this feedback can provide valuable insight about the > management of internal operations and the presence of external domain > name abuse. > > DMARC does not produce or encourage elevated delivery privilege of > authenticated email. DMARC is a mechanism for policy distribution > that enables increasingly strict handling of messages that fail > authentication checks, ranging from no action, through altered > delivery, up to message rejection. > > > 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://www.ietf.org/mailman/listinfo/ietf-announce> > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist> > > For searching the RFC series, see https://www.rfc-editor.org/search > <https://www.rfc-editor.org/search> > For downloading RFCs, see https://www.rfc-editor.org/rfc.html > <https://www.rfc-editor.org/rfc.html> > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to [email protected] > <mailto:[email protected]>. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
