From: "Attila Sipos" <[EMAIL PROTECTED]>
>>The '*' char shall not be escaped IMO, this is allowed
>>by RFC 2396 in URI syntax. Have you references saying
>>the '*' should be escaped?
Sorry, you are right.
Looking at the rfc 3261 grammar...
userinfo = ( user / telephone-subscriber ) [ ":" password ] "@"
user = 1*( unreserved / escaped / user-unreserved )
user-unreserved = "&" / "=" / "+" / "$" / "," / ";" / "?" / "/"
unreserved = alphanum / mark
mark = "-" / "_" / "." / "!" / "~" / "*" / "'"
/ "(" / ")"
'*' is part of the "mark" set which is part of "unreserved" which
is part of "user" which is part of "userinfo".
So, as you correctly say, a * does not require escaping.
A subtle point revolves around characters that are not required to be
escaped, but are in situations where an escape can be used. E.g.,
"sip:[EMAIL PROTECTED]" vs. "sip:[EMAIL PROTECTED]". Based on this
principle in section 19.1.4 "URI Comparison":
o Characters other than those in the "reserved" set (see RFC 2396
[5]) are equivalent to their ""%" HEX HEX" encoding.
the consensus seems to be that in any situation where escaping is
permitted but not mandatory, the escaped version of a character or
string is functionally equivalent to the un-escaped version.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
