--===============93769079432124469==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_3oDL/hVsKaOx22p";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_3oDL/hVsKaOx22p
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thiago Macieira wrote:
>>or even if they are have nothing
>>to do with the Internet, and it would be a mistake to make assumptions
>>about the case insensitivity of any part of a URL for which the protocol
>>isn't known to exhibit this property.
>
>URLs are defined with case insensitive hostnames. A protocol where hostnam=
es
>are case sensitive (there is no such thing in DNS) probably will have a ha=
rd
>time using URLs at all.

Answering myself with a bit more of backing:

RFC 1738 - Uniform Resource Locators (URL)

2.1 The main parts of URLs
[...]
 In general, URLs are written as follows:=20

       <scheme>:<scheme-specific-part>

3.1 Common Internet Scheme Syntax
[...] The scheme specific data start with a double slash "//" to indicate t=
hat=20
it complies with the common Internet scheme syntax. The different component=
s=20
obey the following rules:
[...]
host=20
 The fully qualified domain name of a network host, or its IP address as a =
set=20
of four decimal digit groups separated by ".". Fully qualified domain names=
=20
take the form as described in Section 3.5 of RFC 1034 [13] and Section 2.1 =
of=20
RFC 1123 [5]: a sequence of domain labels separated by ".", each domain lab=
el=20
starting and ending with an alphanumerical character and possibly also=20
containing "-" characters. The rightmost domain label will never start with=
 a=20
digit, though, which syntactically distinguishes all domain names from the =
IP=20
addresses.

(This is further updated by RFC 2732 - Format for Literal IPv6 Addresses in=
=20
URL's - that KURL has supported for several years now; with IDNA, this is=20
again further expanded)

The definition above makes KURL have every right to apply STD 3 and RFC 349=
1=20
rules to hostname parts of the URLs.

Note we're talking about URLs here, not the expanded sense of URIs as defin=
ed=20
by RFC 2396..

=2D-=20
  Thiago Macieira  -  Registered Linux user #65028
   thiagom@mail.com          =20
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--Boundary-02=_3oDL/hVsKaOx22p
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/LDo3M/XwBW70U1gRAgXQAKC09mY4qEsW0hjeAptRDE3tYG80JQCgvy/d
3MTjTVmEu7V35c40o+Smbgs=
=Md/G
-----END PGP SIGNATURE-----

--Boundary-02=_3oDL/hVsKaOx22p--

--===============93769079432124469==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============93769079432124469==--