Re: Minimal presence of MIME headers in message payload

"Steven E. Harris" <[email protected]> writes:

> In the case where /no/ headers are present, is there just a spare
> CRLF pair at the beginning of the payload after the BEEP header?

I found a message from this mailing list in August 2000¹ that shows a
more detailed ABNF indicating the payload content requires at least
one CRLF pair:

  mime       = <MIME Content {entity-headers} from RFC 2045>
  payload    = [mime] CR LF *OCTET


I have not yet found a follow-up message arguing against this
definition, but it apparently did not make it into RFC 3080.


Footnotes: 
¹ [BXXPwg] proposal for 1:N interactions
  Marshall Rose
  http://drakken.dbc.mtview.ca.us/pipermail/beepwg/2000-August/000823.html

-- 
Steven E. Harris