From owner-ietf-msgtrk@mail.imc.org Fri Sep 3 15:39:50 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10178 for ; Fri, 3 Sep 2004 15:39:49 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i83JUoI2049871; Fri, 3 Sep 2004 12:30:50 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i83JUohx049870; Fri, 3 Sep 2004 12:30:50 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from mail.verisignlabs.com (cliffie.verisignlabs.com [65.201.175.9]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i83JUnPV049859 for ; Fri, 3 Sep 2004 12:30:49 -0700 (PDT) (envelope-from sah@428cobrajet.net) Received: from dul1shollenbl1 ([::ffff:216.168.239.87]) (AUTH: LOGIN shollenb, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Fri, 03 Sep 2004 15:30:46 -0400 id 003089AD.4138C666.00003CF1 From: "Scott Hollenbeck" To: ietf-msgtrk@imc.org Subject: MSGTRK Closing Date: Fri, 3 Sep 2004 15:30:47 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF02E0F875@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id i83JUnPV049865 Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8bit All: The msgtrk documents are now in RFC Editor "auth48" status. That means that they are in the final stage of review before being published as RFCs. That being the case, I intend to close the working group after the RFCs are announced. Speak now if you believe there is any reason to *not* close. The working group mailing list can remain open once the group has closed. You all can decide to close the list if you wish to do so, but there's no harm (and there's often benefit) in leaving the list open after a group has been closed. Congratulations on a job almost completed! -Scott- From owner-ietf-msgtrk@mail.imc.org Wed Sep 29 19:24:29 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01010 for ; Wed, 29 Sep 2004 19:24:27 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNEDI2087928; Wed, 29 Sep 2004 16:14:13 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8TNEDWP087927; Wed, 29 Sep 2004 16:14:13 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNEAPR087902 for ; Wed, 29 Sep 2004 16:14:12 -0700 (PDT) (envelope-from rfc-ed@ISI.EDU) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8TNCoJ00770; Wed, 29 Sep 2004 16:12:50 -0700 (PDT) Message-Id: <200409292312.i8TNCoJ00770@boreas.isi.edu> To: ietf-announce@ietf.org Subject: RFC 3885 on SMTP Service Extension for Message Tracking Cc: rfc-editor@rfc-editor.org, ietf-msgtrk@imc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 29 Sep 2004 16:12:49 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3885 Title: SMTP Service Extension for Message Tracking Author(s): E. Allman, T. Hansen Status: Standards Track Date: September 2004 Mailbox: eric@Sendmail.COM, tony+msgtrk@maillennium.att.com Pages: 9 Characters: 17458 Updates: 3461 I-D Tag: draft-ietf-msgtrk-smtpext-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3885.txt This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking. This document is a product of the Message Tracking Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040929154930.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3885 --OtherAccess Content-Type: Message/External-body; name="rfc3885.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040929154930.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-ietf-msgtrk@mail.imc.org Wed Sep 29 19:24:30 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01011 for ; Wed, 29 Sep 2004 19:24:29 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNG6Sx088017; Wed, 29 Sep 2004 16:16:06 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8TNG6Ie088016; Wed, 29 Sep 2004 16:16:06 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNG6p4088007 for ; Wed, 29 Sep 2004 16:16:06 -0700 (PDT) (envelope-from rfc-ed@ISI.EDU) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8TNEYJ01311; Wed, 29 Sep 2004 16:14:34 -0700 (PDT) Message-Id: <200409292314.i8TNEYJ01311@boreas.isi.edu> To: ietf-announce@ietf.org Subject: RFC 3886 on An Extensible Message Format for Message Tracking Responses Cc: rfc-editor@rfc-editor.org, ietf-msgtrk@imc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 29 Sep 2004 16:14:34 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3886 Title: An Extensible Message Format for Message Tracking Responses Author(s): E. Allman Status: Standards Track Date: September 2004 Mailbox: eric@Sendmail.COM Pages: 11 Characters: 21746 Updates: 3463 I-D Tag: draft-ietf-msgtrk-trkstat-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3886.txt Message Tracking is expected to be used to determine the status of undelivered e-mail upon request. Tracking is used in conjunction with Delivery Status Notifications (DSN) and Message Disposition Notifications (MDN); generally, a message tracking request will be issued only when a DSN or MDN has not been received within a reasonable timeout period. This memo defines a MIME content-type for message tracking status in the same spirit as RFC 3464, "An Extensible Message Format for Delivery Status Notifications". It is to be issued upon a request as described in "Message Tracking Query Protocol". This memo defines only the format of the status information. An extension to SMTP to label messages for further tracking and request tracking status is defined in a separate memo. This document is a product of the Message Tracking Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040929161306.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3886 --OtherAccess Content-Type: Message/External-body; name="rfc3886.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040929161306.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-ietf-msgtrk@mail.imc.org Wed Sep 29 19:26:21 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01266 for ; Wed, 29 Sep 2004 19:26:20 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNH6Ha088203; Wed, 29 Sep 2004 16:17:06 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8TNH6LJ088202; Wed, 29 Sep 2004 16:17:06 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNH6j3088180 for ; Wed, 29 Sep 2004 16:17:06 -0700 (PDT) (envelope-from rfc-ed@ISI.EDU) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8TNGKJ01890; Wed, 29 Sep 2004 16:16:20 -0700 (PDT) Message-Id: <200409292316.i8TNGKJ01890@boreas.isi.edu> To: ietf-announce@ietf.org Subject: RFC 3887 on Message Tracking Query Protocol Cc: rfc-editor@rfc-editor.org, ietf-msgtrk@imc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 29 Sep 2004 16:16:20 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3887 Title: Message Tracking Query Protocol Author(s): T. Hansen Status: Standards Track Date: September 2004 Mailbox: tony+msgtrk@maillennium.att.com Pages: 23 Characters: 42763 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-msgtrk-mtqp-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3887.txt Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document describes the Message Tracking Query Protocol that is used in conjunction with extensions to the ESMTP protocol to provide a complete message tracking solution for the Internet. This document is a product of the Message Tracking Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040929161443.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3887 --OtherAccess Content-Type: Message/External-body; name="rfc3887.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040929161443.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-ietf-msgtrk@mail.imc.org Wed Sep 29 19:27:18 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01484 for ; Wed, 29 Sep 2004 19:27:18 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNJ6ej088425; Wed, 29 Sep 2004 16:19:06 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8TNJ6ip088424; Wed, 29 Sep 2004 16:19:06 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8TNJ6NK088405 for ; Wed, 29 Sep 2004 16:19:06 -0700 (PDT) (envelope-from rfc-ed@ISI.EDU) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8TNHqJ02699; Wed, 29 Sep 2004 16:17:52 -0700 (PDT) Message-Id: <200409292317.i8TNHqJ02699@boreas.isi.edu> To: ietf-announce@ietf.org Subject: RFC 3888 on Message Tracking Model and Requirements Cc: rfc-editor@rfc-editor.org, ietf-msgtrk@imc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 29 Sep 2004 16:17:52 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3888 Title: Message Tracking Model and Requirements Author(s): T. Hansen Status: Informational Date: September 2004 Mailbox: tony+msgtrk@maillennium.att.com Pages: 11 Characters: 20950 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-msgtrk-model-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3888.txt Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document provides a model of message tracking that can be used for understanding the Internet-wide message infrastructure and to further enhance those capabilities to include message tracking, as well as requirements for proposed message tracking solutions. This document is a product of the Message Tracking Protocol Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040929161635.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3888 --OtherAccess Content-Type: Message/External-body; name="rfc3888.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040929161635.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-ietf-msgtrk@mail.imc.org Thu Sep 30 11:33:39 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00995 for ; Thu, 30 Sep 2004 11:33:38 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8UFIYvI011003; Thu, 30 Sep 2004 08:18:34 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8UFIYeA011002; Thu, 30 Sep 2004 08:18:34 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from mail.verisignlabs.com (cliffie.verisignlabs.com [65.201.175.9]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8UFIXHv010967 for ; Thu, 30 Sep 2004 08:18:33 -0700 (PDT) (envelope-from sah@428cobrajet.net) Received: from dul1shollenbl1 ([::ffff:63.240.218.148]) (AUTH: LOGIN shollenb, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Thu, 30 Sep 2004 11:18:30 -0400 id 003C82DD.415C23C6.00001081 From: "Scott Hollenbeck" To: ietf-msgtrk@imc.org Subject: RE: MSGTRK Closing Date: Thu, 30 Sep 2004 11:18:39 -0400 Message-ID: <002301c4a700$c40f4470$eed3010a@vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF02E0F875@vsvapostal8.vcorp.ad.vrsn.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id i8UFIYHv010992 Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 8bit The four MSGTRK RFCs were announced yesterday. That being done, the working group will be closed shortly. No one expressed any opinions on keeping this mailing list open or closing it. Speak NOW if you have an opinion, because I need to tell the IETF Secretariat if the list will remain when the group is closed. Since closing the list requires explicit action, I am going to assume that a lack of opinion or explicit action to close the list means that it should remain open. -Scott- > -----Original Message----- > From: Scott Hollenbeck [mailto:sah@428cobrajet.net] > Sent: Friday, September 03, 2004 3:31 PM > To: ietf-msgtrk@imc.org > Subject: MSGTRK Closing > > > > All: > > The msgtrk documents are now in RFC Editor "auth48" status. > That means that > they are in the final stage of review before being published > as RFCs. That > being the case, I intend to close the working group after the RFCs are > announced. Speak now if you believe there is any reason to > *not* close. > > The working group mailing list can remain open once the group > has closed. > You all can decide to close the list if you wish to do so, > but there's no > harm (and there's often benefit) in leaving the list open > after a group has > been closed. > > Congratulations on a job almost completed! > > -Scott- > > > From owner-ietf-msgtrk@mail.imc.org Thu Sep 30 12:04:04 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03912 for ; Thu, 30 Sep 2004 12:04:04 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8UFtrLZ020600; Thu, 30 Sep 2004 08:55:53 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8UFtrLR020599; Thu, 30 Sep 2004 08:55:53 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from ckmso2.proxy.att.com (ckmso2.att.com [209.219.209.75]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8UFtqHY020556 for ; Thu, 30 Sep 2004 08:55:52 -0700 (PDT) (envelope-from tony@att.com) Received: from maillennium.att.com ([135.25.114.99]) by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id i8UFtjMh003351 for ; Thu, 30 Sep 2004 11:55:46 -0400 Received: from [135.91.110.23] (thansen-n.mt.att.com[135.91.110.23](untrusted sender)) by maillennium.att.com (mailgw1) with ESMTP id <20040930155640gw100goejje> (Authid: tony); Thu, 30 Sep 2004 15:56:40 +0000 Message-ID: <415C2C83.3040806@att.com> Date: Thu, 30 Sep 2004 11:55:47 -0400 From: Tony Hansen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Hollenbeck CC: ietf-msgtrk@imc.org Subject: Re: MSGTRK Closing References: <002301c4a700$c40f4470$eed3010a@vcorp.ad.vrsn.com> In-Reply-To: <002301c4a700$c40f4470$eed3010a@vcorp.ad.vrsn.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit I feel it should remain open. If message tracking takes off, then we will need the mailing list for possible subsequent work. Tony Hansen tony@att.com Scott Hollenbeck wrote: > The four MSGTRK RFCs were announced yesterday. That being done, the working > group will be closed shortly. > > No one expressed any opinions on keeping this mailing list open or closing > it. Speak NOW if you have an opinion, because I need to tell the IETF > Secretariat if the list will remain when the group is closed. Since closing > the list requires explicit action, I am going to assume that a lack of > opinion or explicit action to close the list means that it should remain > open. > > -Scott- > > >>-----Original Message----- >>From: Scott Hollenbeck [mailto:sah@428cobrajet.net] >>Sent: Friday, September 03, 2004 3:31 PM >>To: ietf-msgtrk@imc.org >>Subject: MSGTRK Closing >> >> >> >>All: >> >>The msgtrk documents are now in RFC Editor "auth48" status. >>That means that >>they are in the final stage of review before being published >>as RFCs. That >>being the case, I intend to close the working group after the RFCs are >>announced. Speak now if you believe there is any reason to >>*not* close. >> >>The working group mailing list can remain open once the group >>has closed. >>You all can decide to close the list if you wish to do so, >>but there's no >>harm (and there's often benefit) in leaving the list open >>after a group has >>been closed. >> >>Congratulations on a job almost completed! >> >>-Scott- >> >> >> > > > From owner-ietf-msgtrk@mail.imc.org Thu Sep 30 12:17:11 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05230 for ; Thu, 30 Sep 2004 12:17:10 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i8UG8pOv024481; Thu, 30 Sep 2004 09:08:51 -0700 (PDT) (envelope-from owner-ietf-msgtrk@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i8UG8pjH024480; Thu, 30 Sep 2004 09:08:51 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-msgtrk@mail.imc.org using -f Received: from aux153.plano.net (fife-smtp.catalog.com [209.217.36.155]) by above.proper.com (8.12.11/8.12.9) with SMTP id i8UG8ork024470 for ; Thu, 30 Sep 2004 09:08:51 -0700 (PDT) (envelope-from Corroll.Driskell@Konzultz.Biz) Received: (qmail 19275 invoked from network); 30 Sep 2004 16:09:57 -0000 Received: from unknown (HELO KONZULTZMOBILE) (67.108.128.162) by smtp1.catalog.com with SMTP; 30 Sep 2004 16:09:57 -0000 From: "Corro'll Driskell \(from the Tablet PC\)" To: Subject: RE: MSGTRK Closing Date: Thu, 30 Sep 2004 12:08:38 -0400 Organization: Konzultz Incorporation Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcSnB0D6F6l1FqdKQaSqsqbNoJ+3mAAAGhsg Importance: High In-Reply-To: <415C2C83.3040806@att.com> Sender: owner-ietf-msgtrk@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit I would like to have it available for other initiatives. Corro'll Driskell Trainer/Facilitator/Consultant Konzultz Incorporated /consulting results/ Corroll.Driskell@Konzultz.Biz (888) 875-8708 ext. 709 fon (888) 875-8708 fax The Solution, Konzultz. The Outcome, Results. "A person succeeds or fails according to the multitude of decisions that are made day after day. The right decisions lead to rewards; incorrect decisions lead to disappointment and delay." --S. Truett Cathy, Founder of Chick-fil-A, Inc Note: Under Bill s.1618 Title III passed by the 105th U.S. Congress this mail cannot be considered spam as long as contact information and a remove link for removal from mailing list is included. To be removed from our mailing list reply with "remove" in the subject heading, and include your "original email address / addresses and your full name." :-----Original Message----- :From: owner-ietf-msgtrk@mail.imc.org [mailto:owner-ietf- :msgtrk@mail.imc.org] On Behalf Of Tony Hansen :Sent: Thursday, September 30, 2004 11:56 AM :To: Scott Hollenbeck :Cc: ietf-msgtrk@imc.org :Subject: Re: MSGTRK Closing : : :I feel it should remain open. If message tracking takes off, then we :will need the mailing list for possible subsequent work. : : Tony Hansen : tony@att.com : :Scott Hollenbeck wrote: : :> The four MSGTRK RFCs were announced yesterday. That being done, the :working :> group will be closed shortly. :> :> No one expressed any opinions on keeping this mailing list open or :closing :> it. Speak NOW if you have an opinion, because I need to tell the IETF :> Secretariat if the list will remain when the group is closed. Since :closing :> the list requires explicit action, I am going to assume that a lack of :> opinion or explicit action to close the list means that it should remain :> open. :> :> -Scott- :> :> :>>-----Original Message----- :>>From: Scott Hollenbeck [mailto:sah@428cobrajet.net] :>>Sent: Friday, September 03, 2004 3:31 PM :>>To: ietf-msgtrk@imc.org :>>Subject: MSGTRK Closing :>> :>> :>> :>>All: :>> :>>The msgtrk documents are now in RFC Editor "auth48" status. :>>That means that :>>they are in the final stage of review before being published :>>as RFCs. That :>>being the case, I intend to close the working group after the RFCs are :>>announced. Speak now if you believe there is any reason to :>>*not* close. :>> :>>The working group mailing list can remain open once the group :>>has closed. :>>You all can decide to close the list if you wish to do so, :>>but there's no :>>harm (and there's often benefit) in leaving the list open :>>after a group has :>>been closed. :>> :>>Congratulations on a job almost completed! :>> :>>-Scott- :>> :>> :>> :> :> :>