Perhaps each of these should be separate issues, but for now:
There are three main things talked about in RFC 3987 which are not currently in the URL standard.
Addressing these should be in the problem-statement somehow:
a) comparison. 3986 and 3987 both talk about how to compare two URIs, two URIs, for equivalence for various purposes. Neither is entirely accurate or corresponds to current implementation. Every URL processor implicitly defines an equivalence relationship -- two URLs are X-equivalent if they have the same result when processed by X, but comparison generally is predictive, and sometimes being conservative means avoiding false positives and sometimes means avoiding false negatives.
b) URLs with Bidi components, and advice for presentation and use.
c) Security considerations for display of URLs to users, especially non-ASCII URLs.
Perhaps each of these should be separate issues, but for now: There are three main things talked about in RFC 3987 which are not currently in the URL standard. Addressing these should be in the problem-statement somehow: a) comparison. 3986 and 3987 both talk about how to compare two URIs, two URIs, for equivalence for various purposes. Neither is entirely accurate or corresponds to current implementation. Every URL processor implicitly defines an equivalence relationship -- two URLs are X-equivalent if they have the same result when processed by X, but comparison generally is predictive, and sometimes being conservative means avoiding false positives and sometimes means avoiding false negatives. b) URLs with Bidi components, and advice for presentation and use. c) Security considerations for display of URLs to users, especially non-ASCII URLs.