Re: [Gen-art] RE: Gen-ART review of draft-ietf-ccamp-te-node-cap-05
Ross Callon <rcallon@juniper.net> Thu, 31 May 2007 14:52 UTC
Return-path: <gen-art-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Htm0g-0001jL-V0; Thu, 31 May 2007 10:52:18 -0400
Received: from gen-art by megatron.ietf.org with local (Exim 4.43) id 1Htm0e-0001h9-Uj for gen-art-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 10:52:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Htm0e-0001h1-Kz for gen-art@ietf.org; Thu, 31 May 2007 10:52:16 -0400
Received: from kremlin.juniper.net ([207.17.137.120] helo=smtpa.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Htm0d-0004xc-Ag for gen-art@ietf.org; Thu, 31 May 2007 10:52:16 -0400
Received: from unknown (HELO merlot.juniper.net) ([172.17.27.10]) by smtpa.juniper.net with ESMTP/TLS/DES-CBC3-SHA; 31 May 2007 07:52:15 -0700
X-IronPort-AV: i="4.14,599,1170662400"; d="scan'208"; a="11819137:sNHT43209072"
Received: from rcallon-lt1.juniper.net ([172.23.1.106]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l4VEqCJ01868; Thu, 31 May 2007 07:52:12 -0700 (PDT) (envelope-from rcallon@juniper.net)
Message-Id: <5.0.0.25.2.20070531103149.034005b0@zircon.juniper.net>
X-Sender: rcallon@zircon.juniper.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Thu, 31 May 2007 10:52:07 -0400
To: Adrian Farrel <adrian@olddog.co.uk>, Russ Housley <housley@vigilsec.com>, dward@cisco.com
From: Ross Callon <rcallon@juniper.net>
Subject: Re: [Gen-art] RE: Gen-ART review of draft-ietf-ccamp-te-node-cap-05
In-Reply-To: <08b001c7a366$26ed5c30$0200a8c0@your029b8cecfe>
References: <B356D8F434D20B40A8CEDAEC305A1F24042EF1A3@esebe105.NOE.Nokia.com> <D109C8C97C15294495117745780657AE07AFCBB0@ftrdmel1.rd.francetelecom.fr> <200705302052.l4UKqAfk002023@mta5.iomartmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: rcallon@juniper.net, gen-art@ietf.org, Pasi.Eronen@nokia.com, LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@orange-ftgroup.com>, dbrungard@att.com
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org
At 10:22 AM 5/31/2007 +0100, Adrian Farrel wrote: >Maybe someone could clarify the progress of the IS-IS RFCs from >Informational to Standards Track. > >It seems to me that this operation has been progressing for the longest >time, and it is leaving everyone in a state of mild confusion about what >they should be doing. > >For example, if it is the intention that all IS-IS protocol RFCs will be >Standards Track, then new I-Ds should have intended status of Standards >Track. But that means that, until the old RFCs are upgraded, we >automatically have a downref. > >It seems to me that the downref process was not designed to handle this >type of downref, and that we should just get on with things instead of >enforcing this particular rule. > >Adrian Two issues here: First of all, there is a group of seven IS-IS RFCs that are in the process of being updated from Informational to Standards track. I discussed this with Dave Ward, in his role as IS-IS co-chair, a month or so ago, and we agreed that we needed updated IDs for minor editorial reasons, such as updating references and changing the status indicated on the first page of the draft. Thus my understanding is that we are waiting on updates to the seven drafts. Secondly: I think that the downref rules are actually quite silly, and are an example (and definitely not the only example) of the IESG DOS'ing itself. The rules state that we are supposed to mention downrefs in the IETF last call. If we forget, then we get to repeat the last call or change the type of reference. In fact, from the perspective of a vendor: No one cares about whether a document is standards track or informational. Whether it gets implemented depends upon customer demand, and NOT on the status of the document. Also, in terms of people who have products to build and/or networks to deploy, no one cares about downrefs. Yes, there are some people who are not focused on building products or deploying networks who will on rare occasion respond when an IETF last call mentions a downref. However, we have lots of people involved in the IETF who like to get bent out of shape about silly details, and even these people don't bother to respond the vast majority of the time when an IETF last call mentions a downref. Thus personally I think that in the interest of making the IETF and more efficient and more effective and practical standards organization, we should change to the rules regarding downrefs to simply permit them, and not require any special treatment for downrefs. Ross >----- Original Message ----- From: "Russ Housley" <housley@vigilsec.com> >To: <rcallon@juniper.net> >Cc: "LE ROUX Jean-Louis RD-CORE-LAN" ><jeanlouis.leroux@orange-ftgroup.com>; <Pasi.Eronen@nokia.com>; ><gen-art@ietf.org>; <ccamp-chairs@tools.ietf.org>; ><ccamp-ads@tools.ietf.org>; <jpv@cisco.com> >Sent: Wednesday, May 30, 2007 9:51 PM >Subject: Re: [Gen-art] RE: Gen-ART review of draft-ietf-ccamp-te-node-cap-05 > > >>Ross: >> >>I think you have to issue a second Last Call to resolve this problem. >> >>Russ >> >>At 10:24 AM 5/30/2007, LE ROUX Jean-Louis RD-CORE-LAN wrote: >>> > 3) As noted in the proto write-up, there's a normative >>> > downref (RFC 3784). This downref was not called out in the >>> > IETF last call message, and it's not listed in the downref >>> >registry. >>> >>>OK, what shall we do to cover this point? >> > _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-ART review of draft-ietf-ccamp-te-n… Pasi.Eronen
- [Gen-art] RE: Gen-ART review of draft-ietf-ccamp-… LE ROUX Jean-Louis RD-CORE-LAN
- Re: [Gen-art] RE: Gen-ART review of draft-ietf-cc… Russ Housley
- Re: [Gen-art] RE: Gen-ART review of draft-ietf-cc… Adrian Farrel
- Re: [Gen-art] RE: Gen-ART review of draft-ietf-cc… Ross Callon