Last Call on the use of RFC 1951 as a normative reference

IESG Secretary <iesg-secretary@ietf.org> Wed, 31 January 2007 15:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHaf-0002XZ-5b; Wed, 31 Jan 2007 10:41:41 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHac-0002Tv-0x; Wed, 31 Jan 2007 10:41:38 -0500
Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HCHab-0008Os-Pv; Wed, 31 Jan 2007 10:41:37 -0500
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns4.neustar.com (Postfix) with ESMTP id B8BB92AC9F; Wed, 31 Jan 2007 15:41:07 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43) id 1HCHa7-0007A9-H0; Wed, 31 Jan 2007 10:41:07 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1HCHa7-0007A9-H0@ietf.org>
Date: Wed, 31 Jan 2007 10:41:07 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: iesg@ietf.org
Subject: Last Call on the use of RFC 1951 as a normative reference
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>
Errors-To: ietf-announce-bounces@ietf.org

Under the term of RFC 3967, the IESG may approve a normative
reference to a document at a lower level, after an appropriate
Last Call. RFC 1951 is referenced by two documents recently
put to Last Call: draft-ietf-lemonade-compress and
draft-ietf-crisp-iris-lwz . As is common with algorithm documents,
RFC 1951 is Informational, where both drafts are targeted
for the standards track. RFC 1951 has already been similarly
used by other documents, including RFC 2616 (HTTP), RFC
3724 (CMS Compressed mode), and RFC 4253 (Secure Shell
Transport Layer), but the IESG has no record of the downref
being called out in those last calls.

The IESG intends to make a decision on whether to permit
these downrefs at the next IESG telechat, and it would appreciate
input by Feb 8, 2007. Further input on whether RFC 1951
should be considered among those documents for which
Last Call references are no longer required (as noted in Section
3 of RFC 3967) would also be welcome. Comments should
be sent to ietf@ietf.org. Exceptionally, comments may be sent
to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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