RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 3977, "Network News Transfer Protocol (NNTP)", October 2006

Source of RFC: nntpext (app)

Errata ID: 2311
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Julien Élie
Date Reported: 2010-06-24
Held for Document Update by: Alexey Melnikov

Section 8.3.2 says:

   For all fields, the value is processed by first removing all CRLF
   pairs (that is, undoing any folding and removing the terminating
   CRLF) and then replacing each TAB with a single space.  If there is
   no such header in the article, no such metadata item, or no header or
   item stored in the database for that article, the corresponding field
   MUST be empty.

It should say:

   For all fields, the value is processed by first removing all CRLF
   pairs (that is, undoing any folding and removing the terminating
   CRLF) and then replacing each TAB with a single space.  If there is
   no such header in the article, no such metadata item, or no header or
   item stored in the database for that article, the corresponding field
   MUST be empty.  If a given header occurs in the article more than once,
   only the content of the first occurrence is returned by OVER.

Notes:

The precision about using the first occurrence of a given header exists for the HDR command (Section 8.5.2). The same thing should be done for OVER, out of consistency between the two commands.

Note: Maybe future versions of the protocol should consider the notion of concatenation of header fields. (We could transform "Comments: Line 1\r\nComments: Line 2" into "Comments: Line 1 Line 2" in the overview field instead of losing information.)

Report New Errata