RE: "*" and "#" signs in the userinfo of SIP URI

Hi, 

>>It is my impression that the reason it is this way
is so that a sip
uri is consistent with the generic syntax for 
>>URIs. This is important for those cases where a sip
URI is processed
by something that understands generic URIs and 
>>not specifically sip URIs. That is something we need
to  > preserve.
> 
>why?  is it a religious issue?  how it is possible that
xmpp 
>uris allow # unescaped?  why does cisco phones send #
unescaped?
> 
>looks like protocol people participating this mailing
list have lost
sense of real life.

This reminds me very much of the send-DTMF-using-INFO
discussion... 

Regards,

Christer

_______________________________________________
Iptel mailing list
Iptelietf.org
https://
www1.ietf.org/mailman/listinfo/iptel

Hello altogether

Can the outcome of the discussion be summarised as the
encoding of the
"*" and "#": 

- Using "E" and "F" is not recommended.
- Using escaped "*" and "#" is possible
according to the current SIP URI
ABNF syntax but is not wanted
- Using unescaped "*" and "#" is
currently against the syntax but it is
the wanted solution

What would be then the next steps based on this results?

Greetings,
Denis Alexeitsev

 

_______________________________________________
Iptel mailing list
Iptelietf.org
https://
www1.ietf.org/mailman/listinfo/iptel