From exim@www1.ietf.org Wed Jan 14 18:23:27 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20829 for ; Wed, 14 Jan 2004 18:23:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguLk-0007e0-Pd for imss-archive@odin.ietf.org; Wed, 14 Jan 2004 18:23:00 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0ENN0DR029380 for imss-archive@odin.ietf.org; Wed, 14 Jan 2004 18:23:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguLk-0007dn-JY for imss-web-archive@optimus.ietf.org; Wed, 14 Jan 2004 18:23:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20785 for ; Wed, 14 Jan 2004 18:22:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AguLh-0000yt-00 for imss-web-archive@ietf.org; Wed, 14 Jan 2004 18:22:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AguKk-0000vr-00 for imss-web-archive@ietf.org; Wed, 14 Jan 2004 18:21:58 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AguJo-0000tC-00 for imss-web-archive@ietf.org; Wed, 14 Jan 2004 18:21:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguJq-0007Rl-0F; Wed, 14 Jan 2004 18:21:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguIs-0007Q2-QG for imss@optimus.ietf.org; Wed, 14 Jan 2004 18:20:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20550 for ; Wed, 14 Jan 2004 18:19:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AguIp-0000r3-00 for imss@ietf.org; Wed, 14 Jan 2004 18:19:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AguHt-0000pR-00 for imss@ietf.org; Wed, 14 Jan 2004 18:19:02 -0500 Received: from razorbill.mail.pas.earthlink.net ([207.217.121.248]) by ietf-mx with esmtp (Exim 4.12) id 1AguHF-0000nt-00; Wed, 14 Jan 2004 18:18:21 -0500 Received: from 9.sub-166-154-182.myvzw.com ([166.154.182.9] helo=EGRodriguez) by razorbill.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 1AguHD-0004oo-00; Wed, 14 Jan 2004 15:18:20 -0800 From: "Elizabeth Rodriguez" To: , Date: Wed, 14 Jan 2004 15:18:04 -0800 Message-ID: <005601c3daf4$ad9ed990$09b69aa6@EGRodriguez> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-ELNK-Trace: 298a5331f71a6b7b79fa035ab2d882059ef193a6bfc3dd482963ec55751d50dda02a3b78a927ce26bd9aa8b00e01cd47350badd9bab72f9c350badd9bab72f9c Content-Transfer-Encoding: quoted-printable Subject: [imss] FW: Processing of Expired Internet-Drafts Sender: imss-admin@ietf.org Errors-To: imss-admin@ietf.org X-BeenThere: imss@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Internet and Management Support for Storage Working Group List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable FYI For IPS, this applies to the iscsi naming extension and the iSNS MIB. It does not currently apply to any IMSS draft. This also applies to individual submissions not yet an official working group item. Elizabeth Rodriguez -----Original Message----- From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org] = On Behalf Of The IETF Secretariat Sent: Wednesday, January 14, 2004 7:53 AM To: IETF-Announce: Cc: iesg@ietf.org Subject: Processing of Expired Internet-Drafts The IETF Secretariat has updated its procedures for processing expired=20 Internet-Drafts. The updated procedures, which are presented below,=20 can also be found in the document entitled "Guidelines to Authors of=20 Internet-Drafts" (http://www.ietf.org/ietf/1id-guidelines.txt). =20 An Internet-Draft will expire exactly 185 days from the date that it is posted=20 on the IETF Web site (http://www.ietf.org/ID.html) unless it is replaced = by an updated version (in which case the clock will start all over again = for the new version, and the old version will be removed from the = Internet-Draft repositories), or unless it is under official review by the IESG=20 (i.e., a request to publish it has been submitted). Specifically, when=20 an Internet-Draft enters the "Publication Requested" state in the I-D Tracker,=20 it will not be expired until its status is resolved (e.g., it is = published as=20 an RFC). I-D Tracker states not associated with a formal request to = publish a document (e.g., "AD is Watching") will not prevent an Internet-Draft = from=20 expiring after 185 days. Internet-Drafts will not expire during the period surrounding an IETF Meeting=20 when submission of updates to Internet-Drafts is suspended (i.e., = between=20 the cutoff date for submission of updated drafts, which is two weeks = prior to=20 an IETF Meeting, and the date that Internet-Draft submissions are once = again being accepted). All Internet-Drafts scheduled to expire during this = period will expire on the day that the Secretariat reopens Internet-Draft submissions. When an Internet-Draft expires, a "tombstone" file will be created that includes the filename and version number of the Internet-Draft that has expired. = The filename of the tombstone file will be the same as that of the = expired=20 Internet-Draft with the version number increased by one. If a revised version=20 of an expired Internet-Draft is submitted for posting, then the revised version will replace the tombstone file and will receive the same version number = as that previously assigned to the tombstone file. Tombstone files will never expire and will always be available for reference unless they are replaced by updated=20 versions of the subject Internet-Drafts. The IETF Secretariat _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss