RFC queue documents stuck on a normative reference
Thomas Narten <narten@us.ibm.com> Wed, 27 July 2005 17:47 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxq0G-0006N4-0V; Wed, 27 Jul 2005 13:47:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxq0D-0006Mt-Tk for wgchairs@megatron.ietf.org; Wed, 27 Jul 2005 13:47:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17306 for <wgchairs@ietf.org>; Wed, 27 Jul 2005 13:47:28 -0400 (EDT)
Received: from e35.co.us.ibm.com ([32.97.110.133]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxqVS-0005HJ-IX for wgchairs@ietf.org; Wed, 27 Jul 2005 14:19:53 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j6RHlIWY538054 for <wgchairs@ietf.org>; Wed, 27 Jul 2005 13:47:19 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j6RHlLE9158276 for <wgchairs@ietf.org>; Wed, 27 Jul 2005 11:47:21 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j6RHlI8q031926 for <wgchairs@ietf.org>; Wed, 27 Jul 2005 11:47:18 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-157-249.mts.ibm.com [9.49.157.249]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j6RHlGAw031824 for <wgchairs@ietf.org>; Wed, 27 Jul 2005 11:47:17 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j6RHl2dq031457 for <wgchairs@ietf.org>; Wed, 27 Jul 2005 13:47:03 -0400
Message-Id: <200507271747.j6RHl2dq031457@cichlid.raleigh.ibm.com>
To: wgchairs@ietf.org
In-Reply-To: Message from Bill Fenner <fenner@research.att.com> of "Fri, 22 Jul 2005 17:01:03 EDT." <200507222101.j6ML13pc022118@bright.research.att.com>
Date: Wed, 27 Jul 2005 13:47:02 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Subject: RFC queue documents stuck on a normative reference
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
Sender: wgchairs-bounces@ietf.org
Errors-To: wgchairs-bounces@ietf.org
I happened to be looking at the RFC queue recently, and noticed that there are a number of documents currently blocked, pending the availability of a normative reference. I'd encourage you to look for documents that you are responsible for (i.e., those in your WG!) and determine what can be done to get the normative references satisfied. Your options are: - remove the normative reference, i.e., by tweaking the text to ensure that the way the reference is used, it is informational rather than normative. (note: this usually means more than just moving the reference to the "informative references" section; the wording surrounding the use of the reference needs to be of an informational nature.) Also, folk really should look at this option carefully. In my experience reviewing documents, I've seen plenty of "normative" references that IMO didn't need to be normative. See section 1.1 of RFC 3967 for some additional wording on the topic of normative vs. informative. - followup with the stuck document and help to get it completed and published. There's some 65 documents here. And some of been waiting many many _months_. To figure out what is going on for document X, go to www.rfc-editor.org/queue.html, and see what document X is waiting on. Then go see its status, etc. (You may need to do this recursively.) You might also find http://rtg.ietf.org/~fenner/iesg/rfc-deps.pdf useful, as it shows the normative reference relationships graphically. Thomas Days ID name ==== ======= 2 draft-ietf-enum-msg 16 draft-zeilenga-ldap-assert 16 draft-zeilenga-ldap-readentry 17 draft-zeilenga-ldap-t-f 26 draft-rescorla-dtls 27 draft-ietf-sipping-cc-conferencing 32 draft-ietf-mip6-mipv6-mib 32 draft-ietf-simple-xcap 34 draft-ietf-ipcdn-docsisevent-mib 34 draft-ietf-mmusic-sdp-media-label 47 draft-ietf-ops-mib-review-guidelines 66 draft-ietf-msec-gsakmp-sec 69 draft-ietf-l3vpn-mpls-vpn-mib 74 draft-ietf-aaa-diameter-cc 102 draft-ietf-ipsec-rfc2401bis 110 draft-ietf-ipsec-esp-v3 110 draft-ietf-msec-mikey-dhhmac 110 draft-ietf-sipping-kpml 115 draft-ietf-simple-event-filter-funct 115 draft-ietf-simple-filter-format 117 draft-burmeister-avt-rtcp-feedback-sim 117 draft-ietf-avt-rtcp-feedback 117 draft-ietf-nsis-rsvp-sec-properties 126 draft-ietf-sasl-anon 131 draft-ietf-sip-guidelines 136 draft-ietf-l2vpn-l2-framework 136 draft-ietf-simple-xcap-pidf-manipulation-usage 145 draft-ietf-ldapbis-dn 145 draft-ietf-ldapbis-filter 145 draft-ietf-ldapbis-models 151 draft-ietf-simple-xcap-list-usage 152 draft-zeilenga-ldup-sync 165 draft-ietf-ldapbis-url 185 draft-melnikov-imap-disc 191 draft-ietf-ipoib-ip-over-infiniband 194 draft-ietf-ipsec-esn-addendum 194 draft-ietf-ipsec-rfc2402bis 202 draft-ietf-ipsec-esp-ah-algorithms 202 draft-zeilenga-ldap-authzid 236 draft-ietf-grow-collection-communities 237 draft-ietf-v6ops-3gpp-analysis 243 draft-behringer-mpls-security 243 draft-ietf-mboned-mroutesec 272 draft-ietf-l3vpn-as2547 272 draft-ietf-l3vpn-rfc2547bis 286 draft-holbrook-idmr-igmpv3-ssm 293 draft-ietf-ipsec-ikev2 297 draft-ietf-isis-igp-p2p-over-lan 303 draft-ietf-ipsec-ikev2-algorithms 303 draft-ietf-ipsec-ui-suites 332 draft-ietf-ipv6-node-requirements 332 draft-ietf-mboned-msdp-deploy 332 draft-ietf-mboned-ssm232 411 draft-ietf-ospf-graceful-impl-report 419 draft-ietf-magma-igmp-proxy 433 draft-ietf-ipoib-architecture 474 draft-ietf-imapext-condstore 495 draft-ietf-ospf-2547-dnbit 503 draft-ietf-magma-igmpv3-and-routing 516 draft-ietf-ipsec-ciph-aes-ccm 559 draft-ietf-magma-snoop 684 draft-ietf-mmusic-sdpng-trans 838 draft-ietf-idwg-beep-idxp 838 draft-ietf-idwg-requirements 853 draft-ietf-smime-symkeydist
- Proposed Elimination of Tombstone Files IETF Secretariat
- Re: Proposed Elimination of Tombstone Files Ole Jacobsen
- Re: Proposed Elimination of Tombstone Files Margaret Wasserman
- Re: Proposed Elimination of Tombstone Files Henrik Levkowetz
- Re: Proposed Elimination of Tombstone Files Martin Duerst
- Re: Proposed Elimination of Tombstone Files Henrik Levkowetz
- Re: Proposed Elimination of Tombstone Files Geoff Huston
- Re: Proposed Elimination of Tombstone Files Olaf M. Kolkman
- Re: Proposed Elimination of Tombstone Files Henrik Levkowetz
- Re: Proposed Elimination of Tombstone Files Paul Hoffman
- Re: Proposed Elimination of Tombstone Files Randy Presuhn
- Re: Proposed Elimination of Tombstone Files Rohan Mahy
- Re: Proposed Elimination of Tombstone Files Henk Uijterwaal
- Re: Proposed Elimination of Tombstone Files Rohan Mahy
- RE: Proposed Elimination of Tombstone Files Susan Hares
- Re: Proposed Elimination of Tombstone Files Brian E Carpenter
- Re: Proposed Elimination of Tombstone Files Henk Uijterwaal
- Re: Proposed Elimination of Tombstone Files Rohan Mahy
- Re: Proposed Elimination of Tombstone Files Brian E Carpenter
- Re: Proposed Elimination of Tombstone Files Brian E Carpenter
- Re: Proposed Elimination of Tombstone Files Henk Uijterwaal
- Re: Proposed Elimination of Tombstone Files Thomas Narten
- Re: Proposed Elimination of Tombstone Files Bill Fenner
- Re: Proposed Elimination of Tombstone Files Brian E Carpenter
- Re: Proposed Elimination of Tombstone Files Thomas Narten
- Re: Proposed Elimination of Tombstone Files Margaret Wasserman
- Re: Proposed Elimination of Tombstone Files Thomas Narten
- Re: Proposed Elimination of Tombstone Files Brian E Carpenter
- RFC queue documents stuck on a normative reference Thomas Narten