On 2/28/12 6:37 AM, satish agrawal wrote:
> Thanks Hughe/Dmitry
>
> 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.

I hope you realize that this draft was never approved as an RFC until 
recently when it was adopted as Historic simply to permanently record 
what had never been approved but had achieved some degree of defacto 
use. The text is much older than it appears - probably more than 10 
years. And because it was never agreed to as an RFC it never had careful 
scrutiny of its ABNF.

It is common practice that whitespace is allowed before each parameter. 
The manner of doing this was revamped in 3261. I suspect this draft was 
written before then when things were more sloppy.

You can try to argue with somebody that they are not in conformance with 
5806, and so get them to remove the whitespace. But I suspect you won't 
have a lot of luck with that.

        Good luck,
        Paul

> Thanks
> Satish
>
>
> On Tue, Feb 28, 2012 at 4:28 PM, Hugh 
> Waite<[email protected]>wrote:
>
>> Hi,
>>
>> On 28/02/2012 10:09, satish agrawal wrote:
>>
>>> Hi
>>>
>>> Can any body Explain me in the Header after colon(;) space is allowed or
>>> not. If now then
>>> Where the RFC say as per my understanding space is not allowed. I am
>>> trying
>>> to find out the
>>> statement in RFC.
>>>
>>> Contact:<sip:[email protected]**>*;*expires=3600
>>>
>>>   Whitespace around the semicolon ; in header parameters is allowed.
>> The ABNF in RFC3261 defines a contact as:
>>
>> Contact        =  ("Contact" / "m" ) HCOLON
>>                   ( STAR / (contact-param *(COMMA contact-param)))
>> contact-param  =  (name-addr / addr-spec) *(SEMI contact-params)
>> SEMI    =  SWS ";" SWS
>>
>> where a contact can be followed by any number of "SEMI contact-params".
>> The definition of SEMI allows whitespace before and after the ';'.
>>
>> Regards,
>> Hugh
>>
>> --
>> Hugh Waite
>> Senior Design Engineer
>> Crocodile RCS Ltd.
>>
>>
>
>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to