Internet-Drafts Posting Update

IETF Secretariat <no-reply@ietf.org> Wed, 14 July 2004 12:41 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12717 for <ietf-announce-archive@ietf.org>; Wed, 14 Jul 2004 08:41:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bkj4t-00052J-He for ietf-announce-archive@ietf.org; Wed, 14 Jul 2004 08:41:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bkj48-0004fm-00 for ietf-announce-archive@ietf.org; Wed, 14 Jul 2004 08:40:53 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1Bkj3F-0004EX-00; Wed, 14 Jul 2004 08:39:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkipz-0004vS-U8; Wed, 14 Jul 2004 08:26:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkWNc-0002YW-Cl for ietf-announce@megatron.ietf.org; Tue, 13 Jul 2004 19:08:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04737 for <ietf-announce@ietf.org>; Tue, 13 Jul 2004 19:08:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkWNa-0006vH-P9 for ietf-announce@ietf.org; Tue, 13 Jul 2004 19:08:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkWEx-0004uY-00 for ietf-announce@ietf.org; Tue, 13 Jul 2004 18:59:11 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BkW6x-0002xg-00; Tue, 13 Jul 2004 18:50:55 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BkVxS-0005N1-EC; Tue, 13 Jul 2004 18:41:06 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BkUlc-0008SG-E9; Tue, 13 Jul 2004 17:24:48 -0400
To: IETF Announcement list <ietf-announce@ietf.org>
From: IETF Secretariat <no-reply@ietf.org>
Message-Id: <E1BkUlc-0008SG-E9@megatron.ietf.org>
Date: Tue, 13 Jul 2004 17:24:48 -0400
X-Mailman-Approved-At: Wed, 14 Jul 2004 08:26:13 -0400
Cc: wgchairs@ietf.org, iesg@ietf.org
Subject: Internet-Drafts Posting Update
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
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=AWL autolearn=no version=2.60

There has been much confusion within the community about the revised 
Internet-Draft boilerplate requirements.  Therefore, to ensure that 
Internet-Drafts are posted in a timely fashion, the Secretariat will not check 
for compliance with the new boilerplate until after the 60th IETF Meeting in San
Diego, California.


Specifically, the Secretariat will post all version 00 Internet-Drafts that 
were submitted prior to July 12th at 9:00 a.m. ET and all version 01+ 
Internet-Drafts that are submitted prior to July 19th at 9:00 a.m. ET regardless
of whether or not they include the revised boilerplate.  If you submitted a 
version 00 Internet-Draft before the cutoff date, and if it is not posted by 
Wednesday, July 14th at 4:00 p.m. ET, then please contact the Secretariat by 
sending a note to ietf-action@ietf.org.  The suggested subject line for this 
note is: Status of I-D Submission: <filename>. 


For information on the current boilerplate requirements, please refer to the 
section entitled "Notices required in Internet-Drafts" of the "Guidelines to 
Authors of Internet-Drafts" (http://www.ietf.org/ietf/1id-guidelines.txt).  We 
encourage you to follow these guidelines for any 01+ Internet-Drafts that you 
submit prior to the cutoff date.  However, we will not check for compliance with
the new boilerplate until we begin accepting submissions after the San Diego 
meeting.


The IETF Secretariat

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce