> From: satish agrawal [[email protected]]
>
> for your prompt reply But my problem is regarding Diversion header
> In this case RFC 5806 say no white space is allowed After Colon(;).
> I have got the same.
One aspect of SIP BNF that is not well documented is this: Many, many
headers are designed to use the same or very similar syntax, which is
a list of items, separated by commas, with each item allowed to have
parameters, which start with semicolons. Usually, each item has the
syntax:
name-addr / addr-spec
which implicitly triggers the rule stated for Contact, From, and To in
section 20:
If the URI contains a comma, question mark or semicolon, the URI
MUST be enclosed in angle brackets (< and >). Any URI parameters
are contained within these brackets. If the URI is not enclosed in
angle brackets, any semicolon-delimited parameters are
header-parameters, not URI parameters.
Note that the BNF does not *state* that these headers are intended to
be parsed in the same way. The rule of section 20 states that it
applies to Contact, From, and To. Other similar headers have similar
rules stated in other places.
But in practice, and in design intent, all of these headers are
handled in the same way. If the text of the document provides a
slightly different syntax for a particular header that has this
general structure, it is almost certain that the intention was to use
the same syntax, and software should be prepared to handle the
standard syntax.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
