( sorry about duplicate, I made error on headers)
Pete Resnick <presnick(_at_)qualcomm(_dot_)com> writes:
On 4/23/07 at 9:15 PM -0400, Bruce Lilly wrote:
OK -- I suggest using an ABNF rule name for the construct of
"clause" (rather than -- or in addition to -- 2822 "name-val-pair")
to make the association between RFC text and ABNF clearer.
[...]
Also, please be very careful: a literal
clause = *(word / domain / addr-spec / angle-addr)
would allow currently illegal atrocities
So, as with other stuff, 2822upd is going to have a more general
syntax that it will be up to 2821bis to limit. In this case, I'm
simply going to have:
received = "Received:" *received-tokens ";" date-time CRLF
received-tokens = word / angle-addr / addr-spec / domain
and leave it to 2821bis to use syntax (including defining proper
"clauses") that won't allow such "atrocities".
You mean
received = "Received:" *( [CVFS] received-tokens ) ";" date-time CRLF
received-tokens = word / angle-addr / addr-spec / domain
perhaps?
(at least <word> does not include [CVFS] )
/ Kari Hurtta