Editorial Nit in section 4.1 (new editorial issue GENERIC_MESSAGE)

Forwarded message 1

• From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
• Date: Sun, 16 Nov 1997 15:38:37 -0800
• Subject: zero or more header fields
• To: Jim Gettys <jg@pa.dec.com>
• Cc: "Dean Justus (Exchange)" <deanj@exchange.microsoft.com>
• Message-Id: <9711161551.aa28937@paris.ics.uci.edu>

I'm not sure what the status of this is r.e. the current draft,
but the BNF is correct.  The generic message parser needs to look
for zero or more header fields.  It may later complain about the
lack of Host or Date, but that is a different issue (different parser).

....Roy


------- Forwarded Message

Message-ID: <2FBF98FC7852CF11912A000000000001076C6A6D@DINO>
From: "Dean Justus (Exchange)" <deanj@exchange.microsoft.com>
To: "'fielding@ics.uci.edu'" <fielding@ics.uci.edu>
Subject: rfc2068
Date: Fri, 14 Nov 1997 11:15:25 -0800

Mr. Roy Fielding;

I do not know if this is an appropriate manner in handling this issue,
but in reading section 4.1 entitled "Message Types" in rfc2068 (Jan '97)
shouldn't:

 generic-message = start-line
			*message-header
                     CRLF
                     [ message-body ]

be written as:

 generic-message = start-line
			1*message-header
			CRLF
                     [ message-body ]


The paragraph above this describes the "message-header" as one or more
header fields.  Thus, in keeping with the *rule of the BNF, shouldn't it
be "1*message-header" instead of "*message-header?"

I apologize if I am aproaching this issue in an unappropriate manner and
would appreciate it if you could communicate to me the right way in
handling issues of this same nature.

Dean Justus

------- End of Forwarded Message