Parsing the Injection-Info: header field
Julien ÉLIE <[email protected]> Sat, 9 Jan 2010 00:21:42 +0100
| Newsgroups | gmane.ietf.usenet.format |
|---|---|
| Organization | TrigoFACILE -- http://www.trigofacile.com/ |
| Message-ID | <3F6C660203CE4751A068B86CD382864E@Iulius> |
Hi,
I follow a discussion that was initiated in news.software.nntp:
http://groups.google.fr/group/news.software.nntp/browse_frm/thread/c7=
04d0859dd84d38
<news:[email protected]>
According to Section 3.2.8 of RFC 5536:
injection-info =3D "Injection-Info:" SP [CFWS] path-identity
[CFWS] *( ";" [CFWS] parameter ) [CFWS] CRLF
NOTE: The syntax of <parameter> (Section 5.1 of [RFC2045], as
amended by [RFC2231]), taken in conjunction with the folding rules
of [RFC0822] (note: not [RFC2822] or [RFC5322]), effectively
allows [CFWS] to occur on either side of the "=3D" inside a
<parameter>.
I do not understand well that point.
Does it mean that CFWS is allowed both before and after the "=3D"?
Why should RFC 822 be followed here? And why doesn't RFC 5322 mention
that?
I thought that RFC 5536 was based upon RFC 5322 and therefore would
not allow a space before "=3D", and would allow a space after "=3D" only
if <value> is a quoted-string.
Just afterwards:
<attribute> format of <value>
-------------------- -----------------
"posting-host" a <host-value>
"posting-account" any <value>
"logging-data" any <value>
"mail-complaints-to" an <address-list>
NOTE: Since any such <host-value> or <address-list> also has to be
a syntactically correct <value>, it will usually be necessary to
encapsulate it as a <quoted-string>, for example:
posting-host =3D "posting.example.com:192.0.2.1"
So it shows that a space is allowed before "=3D".
Isn't it a difference with RFC 5322 that ought to be mentioned in appendi=
x C?
When it is said that <host-value> is encapsulated as a <quoted-string>, d=
oes
it mean that:
posting-host =3D "pos\ting.example.com"
posting-host =3D (Comment) "posting.example.com" (Comment)
are two valid values for this parameter? (Both being "posting.example.co=
m".)
Incidentally, I do not know how to parse
posting-host=3D"20bd:20bd::1"
It could be the IPv6 address "20bd:20bd::1" or the host name "20bd" assoc=
iated
with the IPv6 address "20bd::1"!
--=20
Julien =C9LIE
=AB En v=E9rit=E9, le chemin importe peu, la volont=E9 d'arriver suffit =E0=
tout. =BB