> 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.
RFC 5806 is historic and is unintentionally not following RFC 4485. Thus you
might want to be strict sending and lenient receiving.
RFC 4485 indicates the following:
Header fields MUST follow the standard formatting for SIP, defined as
follows:
header = header-name HCOLON header-value
*(COMMA header-value)
header-name = token
header-value = value *(SEMI value-parameter)
value-parameter = token [EQUAL gen-value]
gen-value = token / host / quoted-string
value = token / host / quoted-string
Draft-levy-sip-diversion was originally based upon RFC 2543 (or
draft-ietf-sip-rfc2543bis-00). The BNF was unintentionally never correctly
updated to comply with RFC 4485 and RFC 3261 concerning the use of SEMI instead
of ';' (with implied *LWS).
The following is from RFC 2543.
"implied *LWS
The grammar described by this specification is word-based. Except
where noted otherwise, linear white space (LWS) can be included
between any two adjacent words (token or quoted-string), and between
adjacent tokens and separators, without changing the interpretation
of a field."
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
