Path: utzoo!utgpu!watmath!clyde!att!osu-cis!killer!ames!pasteur!ucbvax!EWOK.AMD.BNL.GOV!gc
From: gc@EWOK.AMD.BNL.GOV (Graham Campbell)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Re: VERY strange behavior at USENET/BITNET gateway
Message-ID: <8901101440.AA20029@ewok.amd.bnl.gov>
Date: 10 Jan 89 14:40:14 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20


	Status: RO
	
	On another note, perhaps the standards should be more careful
	to define things like "blank line".  My interpretation would be
	"a line with zero or more blanks, but no other characters".
	
Quoting from RFC822, page 5

	It is separated from the headers by a null line (i.e., a line
	with nothing preceding the CRLF)
	
You may argue that such a definition was not well enough thought out
since it does not acknowlege the MVS problem with null lines, but it 
seems like a pretty clear definition to me.

Graham


----- End Forwarded Message -----