-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
Meng forwarded me the notification he received from the RFC Editor. That
notification, which I included below, has a pointer to the SPF RFC draft
as edited by the RFC Editor:
http://ftp.rfc-editor.org/in-notes/authors/rfc4408.txt
So our RFC number will be 4408. I find it interesting that Microsoft's
SUBMITTER draft has received the number 4405 and the Sender-ID and PRA
drafts 4406 and 4407, i.e. numbers that are lower than ours. (But I like
4408 better anyway. At least it is divisible by 4. :-P)
Although we'll probably have to wait for Wayne to return before the RFC
Editor can proceed, we now should start compiling the list of final edits.
I have already done an initial review of the RFC Editor's changes...
http://ftp.rfc-editor.org/in-notes/authors/rfc4408-diff.html
...and have collected some changes that should make it into the final RFC:
http://new.openspf.org/draft-schlitt-spf-classic_AUTH48_changes
Everyone who can spare the time, please read through the draft (see the
first URL above) one last time as thoroughly as you can and report soon
any errors you find!
I seriously hope Wayne pops up soon because we need his list of changes,
too. (I think there were some bugs in the ABNF grammar, etc.)
Julian.
- ---------- Forwarded Message ----------
Subject: Fwd: AUTH48 [EN]: RFC 4408 <draft-schlitt-spf-classic-02.txt>
NOW AVAILABLE
Date: Friday, 10. March 2006 23:19
From: Meng Weng Wong <mengwong(_at_)pobox(_dot_)com>
To: Julian Mehnle <julian(_at_)mehnle(_dot_)net>
here's the notification i got form eric nord.
- ---------- Forwarded Message ----------
From: Eric Nord <nord(_at_)ISI(_dot_)EDU>
Date: March 9, 2006 11:57:16 AM PST
To: mengwong+spf(_at_)pobox(_dot_)com, wayne(_at_)schlitt(_dot_)net,
rfc-editor(_at_)rfc-editor(_dot_)org
Cc: rfc-editor(_at_)rfc-editor(_dot_)org, hardie(_at_)qualcomm(_dot_)com
Subject: Re: AUTH48 [EN]: RFC 4408 <draft-schlitt-spf-classic-02.txt>
NOW AVAILABLE
Reply-To: Eric Nord <nord(_at_)ISI(_dot_)EDU>
Meng & Wayne,
This message is being resent because we have not received approval of the
document. The document will not be published until we receive approval of
the document in its current or edited form.
If you have edits, please send them.
Thank you.
RFC Editor / ejn
- ---------- Attached Message ----------
Date: Mon, 13 Feb 2006 16:49:54 -0800
To: mengwong+spf(_at_)pobox(_dot_)com, wayne(_at_)schlitt(_dot_)net
Subject: AUTH48 [EN]: RFC 4408 <draft-schlitt-spf-classic-02.txt>
NOW AVAILABLE
From: rfc-editor(_at_)rfc-editor(_dot_)org
Cc: rfc-editor(_at_)rfc-editor(_dot_)org, Ted Hardie
<hardie(_at_)qualcomm(_dot_)com>
****IMPORTANT*****
Updated 2006/02/13
RFC AUTHOR(S):
- --------------
This is your LAST CHANCE to make changes to your RFC to be:
draft-schlitt-spf-classic-02.txt, once the document is published as
an RFC we *WILL NOT* make any changes.
Please check your document at:
ftp://ftp.rfc-editor.org/in-notes/authors/rfc4408.txt
ATTENTION: The editing process occasionally introduces errors that
were not in the Internet Draft. Although the RFC Editor tries very
hard to catch all errors, proofreading the text at least twice, typos
can slip through. You, as an author of the RFC, are taking
responsibility for the correctness of the final product when you OK
publication. You should therefore proofread the entire RFC carefully
and without assumptions. Errors in RFCs last forever.
OTE: We have run a diff tool that compares the approved internet-draft
against our edited RFC version of the document. Please review this file
at:
ftp://ftp.rfc-editor.org/in-notes/authors/rfc4408-diff.html
The document will NOT BE PUBLISHED until ALL of the authors listed in
the RFC have affirmed that the document is ready to be published, as ALL of
the authors are equally responsible for verifying the documents readiness
for publication.
** Please send us a list of suitable keywords for this document, over
and above those which appear in the title.
Frequently INCORRECT information includes
- Contact Information
- References (are they up to date)
- Section Numbers
(especially if you originally put the copyright somewhere
other than the VERY end of the document, or if you numbered
the \"Status of the Memo\" field)
Please send us the changes, *DO NOT* send a new document with the
changes made. (If we think that the changes might be more than
editorial we will contact the AD or the IESG to confirm that the
changes do not require review.)
Send us the changes in THIS format.
1)*** SECTION #\'s*** [i.e. Section 5, 2nd paragraph]
2) the text you want changed,
3) the new correct text and
4) if the changes are spacing or indentation than please note
that.
FOR EXAMPLE:
Section 5.6, 3rd paragraph
OLD:
The quick brown fox jumped over the lazy dog.
NEW:
The quick brown dog jumps over the lazy fox.
^^^ ^ ^^^
If you have a whole paragraph to replace you do not need to use
the arrow to point out the differences
INTRODUCTION, 2nd paragraph
Replace OLD:
alsdfja;sldjf;lajsd;fljas;dlfj;
With NEW:
nv;alkjd;lsf;aoisj;ltjka;sldkjf
Spacing or indentation problems...
Section 10, 1st paragraph (remove spaces between bit
and of, add space after butter)
OLD:
Better botter bought a bit
of bitter butterMary mary quite contrary
NEW:
Better botter bought a bit of bitter butter
Mary mary quite contrary
This document will NOT be published until we receive agreement, from
ALL listed authors, that the document is ready for publication.
Thanks for your cooperation,
- -RFC Editor/ar
Title : Sender Policy Framework SPF
for Authorizing Use of Domains
in E-MAIL version
Author(s) : M. Wong, W. Schlitt
Working Group Chair(s) :
Area Director(s) :
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFEE4jvwL7PKlBZWjsRAtS+AKCn3TsR4WbzYIj3dwG17PE+sA486QCg9vI0
TK4XhzcjUpW2qjoLjE9Dz7I=
=BgHG
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com