RFC 4408 on Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1

rfc-editor@rfc-editor.org Fri, 28 April 2006 19:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZYCC-0001ym-Ba; Fri, 28 Apr 2006 15:00:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FZYCA-0001y8-1a for ietf-announce@ietf.org; Fri, 28 Apr 2006 15:00:02 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZYC9-0004b5-Mn for ietf-announce@ietf.org; Fri, 28 Apr 2006 15:00:02 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k3SJ01tC005904; Fri, 28 Apr 2006 12:00:01 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k3SJ019f005903; Fri, 28 Apr 2006 12:00:01 -0700
Date: Fri, 28 Apr 2006 12:00:01 -0700
Message-Id: <200604281900.k3SJ019f005903@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4408 on Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 4408

        Title:      Sender Policy Framework (SPF) for 
                    Authorizing Use of Domains in E-Mail, 
                    Version 1 
        Author:     M. Wong, W. Schlitt
        Status:     Experimental
        Date:       April 2006
        Mailbox:    mengwong+spf@pobox.com, 
                    wayne@schlitt.net
        Pages:      48
        Characters: 105009
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-schlitt-spf-classic-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4408.txt

E-mail on the Internet can be forged in a number of ways.  In
particular, existing protocols place no restriction on what a sending
host can use as the reverse-path of a message or the domain given on
the SMTP HELO/EHLO commands.  This document describes version 1 of
the ender Policy Framework (SPF) protocol, whereby a domain may
explicitly authorize the hosts that are allowed to use its domain
name, and a receiving host may check such authorization.  This memo defines an Experimental Protocol for the Internet community.

EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet 
community. It does not specify an Internet standard of any kind. 
Discussion and suggestions for improvement are requested.  Distribution 
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce