Re: mid and cid URLs -- Consensus!

Daniel W. Connolly (connolly@beach.w3.org)
Wed, 22 Nov 1995 17:02:02 -0500


Message-Id: <199511222202.RAA30022@beach.w3.org>
To: asg@severn.wash.inmet.com (Al Gilman)
Cc: moore@cs.utk.edu (Keith Moore), ietf-types@uninett.no, uri@bunyip.com
Subject: Re: mid and cid URLs -- Consensus! 
In-Reply-To: Your message of "Wed, 22 Nov 1995 16:24:08 EST."
             <9511222124.AA21131@severn.wash.inmet.com> 
Date: Wed, 22 Nov 1995 17:02:02 -0500
From: "Daniel W. Connolly" <connolly@beach.w3.org>

In message <9511222124.AA21131@severn.wash.inmet.com>, Al Gilman writes:
>
>2. I wanted to turn on header encoding in parameters, thus:
>
>(after the above)
>  *( ; header-name=header-value-phrase )
>
>  header-name				; per RFC 822
>  header-value-phrase			; per RFC 822 quoted and escaped asreq.
>
>Is good for legacy multi-mode, multi-server objects like FAQs.


Yeah verily. e.g.

<p>In <a href="mid:9511222124.AA21131@severn.wash.inmet.com;date=Wed,%2022%20Nov%201995%2016:24:08%20EST;to=uri@bunyip.com;from=asg@severn.wash.imnet.com">a previous message</a>, Al Gilman writes:

This would allow folks to apply heuristics like:

	I know an archive for the uri@bunyp.com mailing list
	exists on ftp.foo.bar

Similarly for newsgroup archives, local mail archives, etc.

The date is immensely useful in these situations too (though I wish
it were written in YYYYMMDD format).

Dan