Re: CID: url type

Ed Levinson (elevinso@Accurate.COM)
Wed, 11 Oct 1995 10:56:10 -0400

Message-Id: <9510111456.AA18711@Accurate.COM>
Cc:, ELevinson@Accurate.COM,,
Subject: Re: CID: url type 
In-Reply-To: Your message of "Wed, 11 Oct 1995 13:53:04 BST."
Date: Wed, 11 Oct 1995 10:56:10 -0400
From: Ed Levinson <elevinso@Accurate.COM>

Pushing forward multipart/related can be done at once.  I have a
revision ready to go and will submit it today.  Seems like ietf-822
should be the place to discuss it although it has been handled so far
in the mimesgml wg.  Should it continue as a mimesgml wg

The CID scheme can easily be upgraded to to include the message id.
Larry correctly notes an issue with the cid syntax (angle bracket
usage).  Another issue was raised be Roy Fielding (if I remember
correctly), how to represent non-ascii characters in the headers http
syntax %hh or quoted printable.  Is it appropriate to discuss this on
the same list as related?

Harald, pick a place for discussion.


On Wed, 11 Oct 1995 13:53:04 BST wrote:
> I suggest the following actions:
> - Either Ed refreshes his Cid: scheme, or I replace it with the proposal
>   for Cid: and Mid: URLs I proposed on DRUMS in July
> - Ed should push forward the multipart/related AT ONCE
> - Someone (me, Jacob, or someone else) should draft the "glue" text that
>   says how to use this stuff in E-mail to provide transfer of HTML.

On Tue, 10 Oct 1995 21:12:45 PDT wrote:
> draft-levinson-cid-00.txt has expired, although the not-yet-expired
> draft-ietf-mimesgml-multipart-rel-01.txt refers to it.  Is there any
> intent to revive either of these?
> If you intend to revive the CID URL idea:
> I think the original idea was that the CID: URL would *not* contain
> angle brackets:
> instead of
> 	cid:<>
> in the same way that news: articles don't, even though the content-ID
> field might contain the angle brackets.
> I suggest followup conversation on the syntax of the CID: URL occur on
> the mailing list.
> I'm not sure where followup for the use of CID: URLs within
> multipart/related might go. draft-ietf-mimesgml-related-01.txt looks
> like it is a draft of the 'mimesgml' working group, but the preface of
> the draft itself suggests discussing it on the ietf-822 mailing list.