From mailman-bounces@ietf.org Wed Dec 1 06:17:17 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14556 for ; Wed, 1 Dec 2004 06:17:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZSZJ-0005mM-Cp for discuss-web-archive@ietf.org; Wed, 01 Dec 2004 06:22:48 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZRpl-0002uH-Lr for discuss-web-archive@ietf.org; Wed, 01 Dec 2004 05:35:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: apps.ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: discuss-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:27:07 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your apps.ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@apps.ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@apps.ietf.org. Thanks! Passwords for discuss-web-archive@ietf.org: List Password // URL ---- -------- discuss@apps.ietf.org axuhzo https://www1.ietf.org/mailman/options/discuss/discuss-web-archive%40ietf.org From discuss-bounces@apps.ietf.org Mon Dec 6 06:00:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23347 for ; Mon, 6 Dec 2004 06:00:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbGi8-0007fA-Gu for discuss-web-archive@ietf.org; Mon, 06 Dec 2004 06:07:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbGav-00031E-99; Mon, 06 Dec 2004 05:59:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbGRt-0001QB-Aq for discuss@megatron.ietf.org; Mon, 06 Dec 2004 05:50:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22323 for ; Mon, 6 Dec 2004 05:50:30 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbGYD-0007Nb-EO for discuss@apps.ietf.org; Mon, 06 Dec 2004 05:57:06 -0500 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 06 Dec 2004 03:58:15 +0000 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from edison.cisco.com (edison.cisco.com [171.71.180.109]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iB6AnvAJ016982; Mon, 6 Dec 2004 02:49:58 -0800 (PST) Received: from [144.254.23.225] (dhcp-data-vlan10-23-225.cisco.com [144.254.23.225]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id CAA27127; Mon, 6 Dec 2004 02:49:56 -0800 (PST) Message-ID: <41B43952.2060309@cisco.com> Date: Mon, 06 Dec 2004 11:49:54 +0100 From: Eliot Lear User-Agent: Mozilla Thunderbird 1.0RC1 (Macintosh/20041117) X-Accept-Language: en-us, en MIME-Version: 1.0 To: drums@cs.utk.edu, lemonade@ietf.org, discuss@apps.ietf.org Subject: standards spring cleaning X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: 7bit X-BeenThere: discuss@apps.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: general discussion of application-layer protocols List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: discuss-bounces@ietf.org Errors-To: discuss-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Good day, I am currently involved in an experimental process to see what it would take to hold to the notion that Proposed and Draft Standards shouldn't stay in that state forever. There are a number of mail related standards that fall into this category, and I wonder if people can tell me whether the list of standards below (or any others on the broader list) should stay or go. The original list was generated programmatically by looking for proposed standards below RFC 2000 that are not obsoleted (we'll do draft later). Here they are: RFC1421 Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures RFC1422 Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management RFC1423 Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers RFC1424 Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services RFC1494 Equivalences between 1988 X.400 and RFC-822 Message Bodies RFC1496 Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages RFC1502 X.400 Use of Extended Character Sets RFC1648 Postmaster Convention for X.400 Operations RFC1740 MIME Encapsulation of Macintosh Files - MacMIME RFC1767 MIME Encapsulation of EDI Objects RFC1848 MIME Object Security Services RFC1985 SMTP Service Extension for Remote Message Queue Starting (ETRN) If you believe any of the above standards should not be reclassified as historic, could you please send a note to old-standards@alvestrand.no with the RFC number and a brief reason as to why not and whether the document should be advanced. A good reason is that the standard is still generally useful. A bad reason is that a piece of old code implements it somewhere on the 'net. That having been said we have a pretty low threshold for removing something from the above list. Thanks for your time, Eliot