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

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.

	Paul

Juha Heinanen wrote:
> Christer Holmberg (JO/LMF) writes:
> 
>  > (I still think it should be allowed to send it
unescapted, because I
>  > don't think it can "break" a SIP-URI.)
> 
> that is the only sensible rfc action if any are done. 
simply change the
> grammar and allow # unescaped.  implementors are
already doing it in
> wide scale.
> 
> -- juha
> 
> _______________________________________________
> Iptel mailing list
> Iptelietf.org
> https://
www1.ietf.org/mailman/listinfo/iptel
> 

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

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. 

That is the reason that has been given, yes.

>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.

We need to consider whether that is a realistic case.

For example, I don't think the "#" would be used
in SIP-URIs which you
post on webpages etc, which could be scanned by generic URI
parsers. It
will be used between SIP nodes.

Regards,

Christer

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

Paul Kyzivat writes:

 > 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.

-- juha

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