What is your justification for thinking this? Is there something about 
the section I cited that you think doesn't apply?

        Paul

rahul wrote:
> Hi,
>   I think "#' is allowed...If ur using tel uri
> 
> -Regards,
> Ravi
> 
> -- Paul Kyzivat <[EMAIL PROTECTED]> wrote:
> 
>>
>> Frank Shearar wrote:
>>> "Markus Hofmann" <[EMAIL PROTECTED]> asked:
>>>
>>>> Hello @all,
>>>>
>>>> I checked the RFC 3261 to find out if the hash
>> mark is allowed in the
>>>> SIP URL but did not find anything.
>>>>
>>>> reserved    =  ";" / "/" / "?" / ":" / "@" / "&"
>> / "=" / "+"
>>>>                      / "$" / ","
>>>> unreserved  =  alphanum / mark
>>>> mark        =  "-" / "_" / "." / "!" / "~" / "*"
>> / "'"
>>>>                     / "(" / ")"
>>>> escaped     =  "%" HEXDIG HEXDIG
>>>>
>>>> SIP-URI          =  "sip:" [ userinfo ] hostport
>>>>                     uri-parameters [ headers ]
>>>> SIPS-URI         =  "sips:" [ userinfo ] hostport
>>>>                     uri-parameters [ headers ]
>>>> userinfo         =  ( user / telephone-subscriber
>> ) [ ":" password ] "@"
>>>> user             =  1*( unreserved / escaped /
>> user-unreserved )
>>>>
>>>> Is a SIP URL which looks like:
>> <sip:[EMAIL PROTECTED]> allowed?
>>> The user rule doesn't allow a # character.
>> However, RFC 2806 defines
>>> telephone-subscriber, which references dtmf-digit,
>> which looks like
>>>   dtmf-digit = "*" / "#" / "A" / "B" / "C" / "D"
>>>
>>> Thus, "003#xyz" is indeed a valid userinfo.
>> Not quite. RFC 3261 section 19.1.2 says:
>>
>>     The telephone-subscriber subset of the user
>> component has special
>>     escaping considerations.  The set of characters
>> not reserved in the
>>     RFC 2806 [9] description of telephone-subscriber
>> contains a number of
>>     characters in various syntax elements that need
>> to be escaped when
>>     used in SIP URIs.  Any characters occurring in a
>> telephone-subscriber
>>     that do not appear in an expansion of the BNF
>> for the user rule MUST
>>     be escaped.
>>
>> So you will have to go with:
>> <sip:[EMAIL PROTECTED]>
>>
>>      Paul
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>>
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to