firstname.lastname@example.org on 10/07/98 01:59:34 PM
Please respond to email@example.com
To: Harry Lewis/Boulder/IBM@ibmus, firstname.lastname@example.org
cc: robert.herriot@Eng.Sun.COM, email@example.com, Carl Kugler/Boulder/IBM@ib=
Subject: RE: IPP> uRl CAse iSsUE
I would add the recomendation that implementations avoid creating URLs =
differnt printers that differ only in their case.
I.e. dont have Printer1 and printer1 as two different printers.
From: Ron Bergman [mailto:firstname.lastname@example.org]
Sent: Wednesday, October 07, 1998 11:37 AM
To: Harry Lewis
Cc: email@example.com; Carl Kugler; firstname.lastname@example.org;
Subject: Re: IPP> uRl CAse iSsUE
On Wed, 7 Oct 1998, Harry Lewis wrote:
> THiS IS abOUT As fAR As i WOUlD gO wiTH anY REcomMendAtiOn reGARding =
> SensiTIVitY in ThE IMPleMeNtoRS GUiDe...
> " IPP client and server implementations must be aware of the diverse
> uppercase/lowercase nature of URLs. RFC xxxx defines URL schemes and =
> as case insensitive but reminds us that the rest of the URL may well
> demonstrate case sensitivity. When creating URL's, where the choice i=
> completely arbitrary, it is probably best to select lower case howeve=
> cannot be guaranteed and implementations MUST NOT rely on any specifi=
> type in the URL beyond the URL scheme and host name".
> Harry Lewis - IBM Printing Systems