Re: Lines count in USEFOR

Harald Alvestrand <[email protected]> Tue, 17 Nov 2009 11:35:49 +0100
Newsgroups	gmane.ietf.usenet.format
Message-ID	<[email protected]>
My memory says that we had an extensive discussion before we landed on=20
the idea that the line count =3D=3D the number of CRLFs in the Body.

1) It's unambiguously correct for bodies that end with CRLF and with no=20
bare CRLF
2) It's clear how to count for bodies that contain bare CR or bare LF
3) It's compatible with at least some existing code for bodies that=20
don't end in CRLF

I suggest we leave this one alone.

Julien =C9LIE wrote:
>
> Hi,
>
> According to USEFOR:
>
>
> 3.3.1.  Lines
>
>   The Lines header field indicates the number of lines in the <body>
>   (as defined in [RFC5322]) of the article.
>
>   lines           =3D  "Lines:" SP *WSP 1*DIGIT *WSP CRLF
>
>   The line count is the number of CRLF separators in the <body>.
>
>   Historically, this header field was used by the NNTP [RFC3977]
>   overview facility, but its use for this purpose is now deprecated.
>   As a result, this header field is to be regarded as obsolescent, and
>   it is likely to be removed entirely in a future version of this
>   standard.  All agents SHOULD ignore it and SHOULD NOT generate it.
>
>
>
> If I read RFC 5322:
>
>    body   =3D   (*(*998text CRLF) *998text) / obs-body
>
> Isn't the final *998text counting for a line?
> I believe the line count is the number of CRLF separators in the <body>=

> PLUS ONE.
> (Unless I'm mistaken by the definition of the body?)
>
>
> The second part of the paragraph seems unclear.  I am under the
> impression that RFC 3977 says we can use Lines: in the overview
> but USEFOR -- posterior to RFC 3977 -- deprecates that use.
> This header field is not used by OVER in RFC 3977.
>
> Maybe the reference to RFC 3977 should just be removed in the
> paragraph.  Thus leaving NNTP in general.
>