Doug Sauder <[email protected]> writes:
> The SIP URI syntax in RFC 3261 is not compatible with the generic
> URI syntax in RFC 3986. Specifically, the character "?" should
> not appear in the user component. Arguably, the character "/"
> also should not appear in the user component.
It does look like you're right.
> Surely this topic must have been discussed before now. Does
> anyone have information about prior discussions, or other
> comments on this topic? Has there been a previous attempt
> to make the SIP URI syntax compatible with the generic URI
> syntax?
Given that the SIP URI syntax was fixed before RFC 3986 was written,
it's easier to argue that RFC 3986 was non-upward-compatible with
existing practice.
The reference in 3261 is:
[5] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
And it seems to me that RFC 2396 is similar to RFC 3986, in that it
doesn't allow "?" or "/" in <userinfo>.
This ought to be discussed in the IETF "sipcore" mailing list,
<[email protected]>. But perhaps it already has been.
There are already the errata to 3261:
http://www.rfc-editor.org/errata_search.php?rfc=3261&rec_status=15&presentation=table
and the updates to it: RFC3265, RFC3853, RFC4320, RFC4916, RFC5393, RFC5621,
RFC5626, RFC5630, RFC5922, RFC5954, RFC6026, RFC6141, RFC6665, RFC6878
and one of those might discuss the problem.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
