Re: CID: url type
Ed Levinson <elevinso@accurate.com> Wed, 11 October 1995 16:37 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15507; 11 Oct 95 12:37 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15503; 11 Oct 95 12:37 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa13989; 11 Oct 95 12:37 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id MAA07545; Wed, 11 Oct 1995 12:02:00 -0400
Received: from dimacs.rutgers.edu (root@dimacs.rutgers.edu [128.6.75.16]) by list.cren.net (8.6.12/8.6.12) with ESMTP id LAA05622 for <ietf-822@list.cren.net>; Wed, 11 Oct 1995 11:45:21 -0400
Received: from Princeton.EDU (root@Princeton.EDU [128.112.128.1]) by dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with SMTP id LAA05987 for <ietf-822@dimacs.rutgers.edu>; Wed, 11 Oct 1995 11:45:16 -0400
Received: from acupain.UUCP by Princeton.EDU (5.65b/2.122/princeton) id AA18732; Wed, 11 Oct 95 11:07:31 -0400
Received: by Accurate.COM (4.1/SMI-4.0) id AA18711; Wed, 11 Oct 95 10:56:40 EDT
Message-Id: <9510111456.AA18711@Accurate.COM>
Date: Wed, 11 Oct 1995 10:56:10 -0400
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ed Levinson <elevinso@accurate.com>
To: Harald.T.Alvestrand%uninett.no@princeton.edu
Cc: uri@bunyip.com, ELevinson@accurate.com, html-wg@oclc.org, ietf-822@dimacs.rutgers.edu, elevinso@accurate.com
Subject: Re: CID: url type
In-Reply-To: Your message of "Wed, 11 Oct 1995 13:53:04 BST." <9510111255.AA19821@Princeton.EDU>
X-Org-Addr: 2 Industrial Way
X-Org-Addr: Eatontown, NJ 07724
X-Org-Misc: 1.908.389.5550 (phone) 1.908.389.5556 (fax)
X-Mailer: MH 6.8
X-Listprocessor-Version: 7.2 -- ListProcessor by CREN
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 document? 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. Best.../Ed On Wed, 11 Oct 1995 13:53:04 BST Harald.T.Alvestrand@uninett.no 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 masinter@parc.xerox.com 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: > > cid:950118.1532@XIson.com > > instead of > > cid:<950118.1532@XIson.com> > > 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 uri@bunyip.com 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.
- CID: url type Larry Masinter
- Re: CID: url type Harald.T.Alvestrand
- Re: CID: url type Harald.T.Alvestrand
- Re: CID: url type Ed Levinson
- RE: CID: url type Dr. Mark K. Joseph