Re: IRIP version 4 (Part 1) c II

[Doug Royer <Doug.Royer@xxxxxxx>]

> From: Bruce_Kahn@iris.com
> Date: Wed, 24 Mar 1999 20:26:46 GMT
> ...
> Since you cannot allow some stuff like <CR> and <LF> in the relCalID you 
> are faced w/2 possible choices to follow:
> 
> 1: The URI RFC(s) allow for encoding rules of what we call the relCalID. 
> The MIME world has the concept of RFC 2047 encoding DBCS/MBCS info (ie: 
> Kanji in the RFC 822 phrase part).  By utilizing these you provide the 
> creator fo the relCalID w/a very robust set of ways to name the relCalIDs. 
>  This is a nice thing to do if humans are ever to read/enter/modify 
> relCalIDs by hand since it can easily encode their language specific info.
>
> 2: The RFC 822 approach of restricting the allowable characters to 
> _printable_ US-ASCII.  This is the KISS approach and is probably best 
> taken when humans are not going to be actively involved in 
> reading/entering/modifying relCalIDs.


Item (2): Only the header names, not the values:

	From: =?ISO-8859-1?Q?Olle_J=E4rnefors?= <ojarnef@admin.kth.se>

However that's not an URL and not how they are encoded.

I vote for RFC1723 (or the appropriate replacement).

-Doug