Search RFCs

RFC Editor

File formats:

Status:

BEST CURRENT PRACTICE

Updated by:

RFC 8314

Authors:

C. Hutzler
D. Crocker
P. Resnick
E. Allman
T. Finch

Stream:

IETF

Source:

NON WORKING GROUP

Cite this BCP:TXT  | XML

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC

Abstract

Email has become a popular distribution service for a variety ofsocially unacceptable, mass-effect purposes. The most obvious onesinclude spam and worms. This note recommends conventions for theoperation of email submission and transport services betweenindependent operators, such as enterprises and Internet ServiceProviders. Its goal is to improve lines of accountability forcontrolling abusive uses of the Internet mail service. To this end,this document offers recommendations for constructive operationalpolicies between independent operators of email submission andtransmission services.

Email authentication technologies are aimed at providing assurancesand traceability between internetworked networks. In many emailservices, the weakest link in the chain of assurances is initialsubmission of a message. This document offers recommendations forconstructive operational policies for this first step of emailsending, the submission (or posting) of email into the transmissionnetwork. Relaying and delivery entail policies that occur subsequentto submission and are outside the scope of this document. This document specifies an Internet Best Current Practices for theInternet Community, and requests discussion and suggestions forimprovements.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.