Hi, while in SIP/SIPS/tel URI is "easy" to fix the problem of
addr-spec in headers:
From: sip:[EMAIL PROTECTED];hdr_param
From: <sip:[EMAIL PROTECTED];uri_param>;hdr_param
From: tel:+12345678;hdr_param
From: <tel:+12345678;uri_param>;hdr_param
I find it very complex to do the same in absolute URI since:
absoluteURI = scheme ":" ( hier-part / opaque-part )
opaque-part = uric-no-slash *uric
uric-no-slash = unreserved / escaped
/ ";" / "?" / ":" / "@" / "&" / "=" /
"+" / "$" / ","
This is: 'opaque-part' can contain a ";" so it's really complex (at
least for me) to know if the ";" is part of the opaque-part or a URI
parameter.
Couls I assume that an absolute URI will *always* appear in name-addr
format (this is: enclosed between < > )?
If not then I think that it's just impossible to parse properly. Of
course, it's not valid the "solution" of considering all after the ";"
as parameters because I remember that, for example, a SIP URI can
contain ";" into the userinfo:
From: sip:1234;[EMAIL PROTECTED];tag=1234
- protocol: sip
- userinfo: 1234;usertag=kk
- hostpart: domain.com
- header params: tag=1234
So the same could occur with other kind of URIs, couldn't it?
Any help please? Thanks a lot.
PD: This time I will not complain of the hype-permissive syntax of RFC3261.
--
Iñaki Baz Castillo
<[EMAIL PROTECTED]>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
