Re: SPF I-D for review: draft-schlitt-spf-classic-00.txt

wayne <[email protected]>
Newsgroups gmane.ietf.rfc822
Message-ID <[email protected]>
In <[email protected]> Frank Ellermann <[email protected]> writes:

> All we can do here is help Wayne to get the syntax for the
> Received-SPF header field right.  Or let's help Martin to get
> his Archived-At right.

Yeah, that's what I came here for.


> At the moment (spf-classic-00) he allows apparently no [CFWS],
> {FWS], or *WSP between "=" and ";" in a key-value-pair.  If
> that's for some reason not okay I'd be interested to hear it.
>
> Received-SPF: Pass ip = 127.0.0.1 ; (not allowed ?)
> .......................^.........^                   Bye, Frank

My understanding is that this is allowed.  The current draft defines
key-value-pair as:

        key-value-pair   = key [CFWS] "=" ( dot-atom / quoted-string )

With both dot-atom or a quoted-string as defined in RFC2822.  Both of
these ABNF terminals have [CFWS] at the beginning and the end.

This was also allowed under spf-draft-200406, although it used

        key-value-pair = 1*VCHAR "=" *(WSP / VCHAR) ";"

This is an example of something I have changed.  The old ABNF allowed
for something like:

        Received-SPF: Pass (comment) a==; "=;

And this could be parsed many different ways, such as the key being
"a" or "a=", and the value being "=; \"=", or ";\"=", or "", etc.




-wayne
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.