Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id CAA24406; Tue, 25 Jul 1995 02:56:42 -0400 X-Resent-To: drums@CS.UTK.EDU ; Tue, 25 Jul 1995 02:56:41 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from alpha.xerox.com by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id CAA24399; Tue, 25 Jul 1995 02:56:40 -0400 Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with SMTP id <15071(1)>; Mon, 24 Jul 1995 23:56:02 PDT Received: by golden.parc.xerox.com id <2762>; Mon, 24 Jul 1995 23:55:55 -0700 To: drums@CS.UTK.EDU In-reply-to: Harald.T.Alvestrand@uninett.no's message of Sun, 23 Jul 1995 13:08:52 -0700 <199507232008.WAA00170@dale.uninett.no> Subject: Re: An idea for MID and CID URsomethings From: Larry Masinter Sender: Larry Masinter Fake-Sender: masinter@parc.xerox.com Message-Id: <95Jul24.235555pdt.2762@golden.parc.xerox.com> Date: Mon, 24 Jul 1995 23:55:41 PDT I think you are paying too much attention to the 'Location' part of URLs. The 'news:' URL scheme already contains news IDs even though they don't contain the location of the information. draft-levinson-cid-00.txt already describes the CID: URL scheme. I think it's useful for you to lay out 'how much has to change before assigning a new MID: URL' for message-ID, which is related to the issue of when message-ID's for mail messages can change when being processed.