Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA01613; Sun, 14 Dec 1997 11:54:24 -0500 (EST) Received: by CS.UTK.EDU (bulk_mailer v1.7); Sun, 14 Dec 1997 11:52:28 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id LAA01482; Sun, 14 Dec 1997 11:52:27 -0500 (EST) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA01460; Sun, 14 Dec 1997 11:52:20 -0500 (EST) Received: (qmail 18981 invoked from network); 14 Dec 1997 16:52:18 -0000 Received: from mg134-106.ricochet.net (HELO GK) (204.179.134.106) by smtp.dial.pipex.com with SMTP; 14 Dec 1997 16:52:18 -0000 Message-Id: <3.0.32.19971213040942.007ab100@pop.dial.pipex.com> X-Sender: maiw03@pop.dial.pipex.com (Unverified) X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 14 Dec 1997 17:49:50 +0000 To: Jacob Palme From: Graham Klyne Subject: Re: Message-ID text Cc: IETF working group on revision of mail standards , Pete Resnick Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:52 11/12/97 +0100, Jacob Palme wrote: >I am writing this message during the drums meeting in Washington. Here is a >proposal for new text on the Message-ID based on the discussion during this >meeting. > >An identical Message-ID on two copies of a message means that the sender >believes that they are essentially identical. [...] I believe this statement misses the intent of Message-ID, which is to identify the *transaction*, not the *content*. (The term "Identical" doesn't seem to apply to a transaction.) I would suggest "... believes that they are phases of the same message transaction". GK. --- ------------ Graham Klyne