Subject: Simplified BNF

From: Henning Schulzrinne <[email-masked]>
Date: Sat, 17 Apr 1999 12:56:43 -0400

Currently, the SIP (and HTTP) BNF allows quoted strings and comments to
include escaped newlines. This makes multi-stage parsing a bit of a
pain, since you can't separate the input into lines without looking for
quoted strings or comments. I can't think of a real good use for putting
\n into a comment or string, so one possibility is to disallow \n or \r
in quoted strings in a future version of the spec. 

Disadvantage: it diverges from HTTP conventions.

(Jonathan R. pointed this out.)

Any comments?
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs