Hello,
I have a couple of questions about SIP parsing.
Firstly, bis-04 seems (incorrectly) to permit backslash and quote as
unescaped ctext character within a comment. Which would make the escaping
mechanism and quoted-string parsing ambiguous and unusable. For instance
the current spec would seem to permit ("hello) as a legal comment, and
would entertain two possible parsings for the string (\))
The situation could be fixed by changing the SIP spec to say:
ctext = < any TEXT-UTF8 excluding "(", ")", <"> and "\" >
Should one just assume these "common-sense" restrictions?
Secondly, are there any general rules about the significance of comma as a
header field seperator and semicolon as a parameter seperator? I note that
in From, To and Contact lines, care has been taken to protect commas and
semicolons in URLs using angle-brackets; but it is left open as to whether
future-defined headers can have internal commas or semicolons?
For instance, if a message contained:
Meal: <fish,chips>, peas;type=mushy
is it possible to guess whether there are one, two or three "Meal" headers
without knowing the precise definition of "Meal"; or if "type" is a header
parameter rather than part of the header proper?
Regards,
Nick Hollinghurst [EMAIL PROTECTED]
Research Engineer
AT&T Laboratories, Cambridge, England
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
