RE: RFC queue documents stuck on a normative reference
john.loughney@nokia.com Fri, 29 July 2005 06:07 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyO1r-0007P0-QW; Fri, 29 Jul 2005 02:07:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyO1o-0007NR-IS for wgchairs@megatron.ietf.org; Fri, 29 Jul 2005 02:07:30 -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 CAA00111 for <wgchairs@ietf.org>; Fri, 29 Jul 2005 02:07:26 -0400 (EDT)
From: john.loughney@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyOXQ-0005Nv-5W for wgchairs@ietf.org; Fri, 29 Jul 2005 02:40:08 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j6T63Yuu007993; Fri, 29 Jul 2005 09:03:39 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jul 2005 09:07:23 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jul 2005 09:07:22 +0300
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jul 2005 09:07:22 +0300
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CEA41@esebe100.NOE.Nokia.com>
Thread-Topic: RFC queue documents stuck on a normative reference
Thread-Index: AcWS06qTZDEgqJK9SpCbv72SvtDAqQBL/PoQ
To: narten@us.ibm.com, wgchairs@ietf.org
X-OriginalArrivalTime: 29 Jul 2005 06:07:22.0786 (UTC) FILETIME=[C8FE7820:01C59403]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: RE: 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
Thomas, What is the process to change something from Normative to Informative? Can the authors do it themselves, do WG chairs need to be involved, does the IESG need to be informed? I agree with you that many of the Normative refs could be considered Informative. thanks, John > -----Original Message----- > From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org]On > Behalf Of ext Thomas Narten > Sent: 27 July, 2005 20:47 > To: wgchairs@ietf.org > Subject: RFC queue documents stuck on a normative reference > > > 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 > > >
- RE: RFC queue documents stuck on a normative refe… john.loughney
- Re: RFC queue documents stuck on a normative refe… Brian E Carpenter
- RE: RFC queue documents stuck on a normative refe… john.loughney
- Re: RFC queue documents stuck on a normative refe… Brian E Carpenter
- Re: RFC queue documents stuck on a normative refe… Thomas Narten
- RE: RFC queue documents stuck on a normative refe… john.loughney
- Re: RFC queue documents stuck on a normative refe… Thomas Narten