[SIPForum-discussion] "100 REL" vs "100 rel"

AMIT ANAND amiit.anand at gmail.com
Fri Jun 12 12:47:34 UTC 2009


Yes, totally agree with oscar, there is no diff between 100REL and 100rel
both are same and valid.

Cheers
Amit

2009/5/31 Oscar Alonso Sánchez Hernández <oasanchezh at gmail.com>

> Dear all.
> I find no reason to say that *100REL* is incorrect
> I understand that both *100REL* and *100rel* are correct expresions, i.e.,
> the grammar for parameter values is case-insensitive and the RFC3262 does
> not mention any contrary rule for grammar for parameter names and parameter
> values wich is defined in RFC3261, except, for RAck header (wich is
> case-sensitive)
>
> [RFC3261, pag 30]
>
>    When comparing header fields, field names are always case-
>    insensitive.  Unless otherwise stated in the definition of a
>    particular header field, field values, parameter names, and parameter
>    values are case-insensitive.  Tokens are always case-insensitive.
>    Unless specified otherwise, values expressed as quoted strings are
>    case-sensitive.  For example,
>       Contact: <sip:alice at atlanta.com <sip%3Aalice at atlanta.com>
> >;expires=3600
>    is equivalent to
>       CONTACT: <sip:alice at atlanta.com <sip%3Aalice at atlanta.com>
> >;ExPiReS=3600
>    and
>       Content-Disposition: session;handling=optional
>    is equivalent to
>       content-disposition: Session;HANDLING=OPTIONAL
>    The following two header fields are not equivalent:
>       Warning: 370 devnull "Choose a bigger pipe"
>       Warning: 370 devnull "CHOOSE A BIGGER PIPE"
> Regards,
>
> Oscar Alonso Sánchez Hernández
>
> 2009/5/29 nitin kapoor <nitinkapoorr at gmail.com>
>
> Hello Chesser,
>>
>> There is no OPTION Tag with the name of 100REL, there is only OPTION Tag
>> with the name of "*100rel*" and we are using this option tag is for
>> reliability of provisional responses.  When present in a Supported header,
>> it indicates that the UA can send or receive reliable provisional
>> responses.When present in a Require header in a request, it indicates that
>> the UAS MUST send all provisional responses reliably.When present in a
>> Require header in a reliable provisional response, it indicates that the
>> response is to be sent reliably.
>>
>> Please refer to rfc 3261 and 3262 for more info.
>>
>> Thanks,
>> Nitin Kapoor
>> General Telecom
>>
>>
>> 2009/5/28 chesser domingo <chesnet at yahoo.com>
>>
>>
>>> Hello to everybody...
>>>
>>> Kindly help me with the difference between "100 REL" and "100 rel".
>>>
>>> We have a ZTE ZXSS SS1a/b soft switch and a SIP trunk interconnection
>>> with a Nortel CS1000 PBX. On the SUPPORTED header of the Invite from ZTE, it
>>> places "100 REL". On the other hand, the supported header from the Nortel
>>> CS1000 indicates a "100 rel". IS there a chance that the ZTE soft switch
>>> does not accept the "100 rel" from the Nortel PBX?
>>>
>>> Kind Regards,
>>>
>>> Chesser Domingo
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> This is the SIP Forum discussion mailing list
>>> TO UNSUBSCRIBE, or edit your delivery options, please visit
>>> http://sipforum.org/mailman/listinfo/discussion
>>> Post to the list at discussion at sipforum.org
>>>
>>
>>
>> _______________________________________________
>> This is the SIP Forum discussion mailing list
>> TO UNSUBSCRIBE, or edit your delivery options, please visit
>> http://sipforum.org/mailman/listinfo/discussion
>> Post to the list at discussion at sipforum.org
>>
>>
>
>
> --
> Oscar Alonso Sánchez Hernández
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20090612/261e97df/attachment-0002.html>


More information about the discussion mailing list