IETF Logo Mail Archive

CID: url type

Larry Masinter <masinter@parc.xerox.com> Wed, 11 October 1995 04:52 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05471; 11 Oct 95 0:52 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05467; 11 Oct 95 0:52 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa02126; 11 Oct 95 0:52 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id AAA05792 for uri-out; Wed, 11 Oct 1995 00:13:04 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id AAA05786 for <uri@services.bunyip.com>; Wed, 11 Oct 1995 00:13:00 -0400
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA05897 (mail destined for uri@services.bunyip.com); Wed, 11 Oct 95 00:12:57 -0400
Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with SMTP id <16877(4)>; Tue, 10 Oct 1995 21:12:51 PDT
Received: by golden.parc.xerox.com id <2733>; Tue, 10 Oct 1995 21:12:47 -0700
To: ELevinson@accurate.com
Cc: html-wg@oclc.org, uri@bunyip.com, ietf-822@dimacs.rutgers.edu
Subject: CID: url type
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Larry Masinter <masinter@parc.xerox.com>
Fake-Sender: masinter@parc.xerox.com
Reply-To: uri@bunyip.com
Message-Id: <95Oct10.211247pdt.2733@golden.parc.xerox.com>
Date: Tue, 10 Oct 1995 21:12:45 -0700
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

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.

Please advise.

v2.23.0 | Report a Bug | By Email