RE: [Pppext] removing the milestones
"Glen Zorn \(gwz\)" <gwz@cisco.com> Tue, 23 November 2004 17:44 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02782 for <pppext-web-archive@ietf.org>; Tue, 23 Nov 2004 12:44:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWemU-0000x9-IU for pppext-web-archive@ietf.org; Tue, 23 Nov 2004 12:48:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWeeA-0004dU-P0; Tue, 23 Nov 2004 12:40:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWeQp-0001pa-1k for pppext@megatron.ietf.org; Tue, 23 Nov 2004 12:26:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01678 for <pppext@ietf.org>; Tue, 23 Nov 2004 12:26:19 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWeUM-0006zf-9y for pppext@ietf.org; Tue, 23 Nov 2004 12:30:12 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-4.cisco.com with ESMTP; 23 Nov 2004 09:26:01 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from gwzw2k01 (sjc-vpn5-162.cisco.com [10.21.88.162]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iANHPcft020752; Tue, 23 Nov 2004 09:25:39 -0800 (PST)
Message-Id: <200411231725.iANHPcft020752@sj-core-4.cisco.com>
From: "Glen Zorn (gwz)" <gwz@cisco.com>
To: 'James Carlson' <james.d.carlson@sun.com>
Subject: RE: [Pppext] removing the milestones
Date: Tue, 23 Nov 2004 09:25:38 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <200411231334.iANDY5dN000028@phorcys.East.Sun.COM>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
Thread-Index: AcTRY6HQ+c4chWSDS1OofpBvTJ9/oQAHAxBg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: pppext@ietf.org
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gwz@cisco.com
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
Sender: pppext-bounces@ietf.org
Errors-To: pppext-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
James Carlson <> wrote: > I've had a request to remove our stale milestones from the list. I > agree, and I'm sending mail to the AD and secretariat now. > > Essentially, we have a null list of goals and milestones at this > point and are effectively dormant. > > Below are my notes on the existing list of milestones. If you have > any interest in restoring these with new target dates, or would like > to have new milestones added, please speak up. > >> Dec 99 Advance AODI draft to Proposed Standard > > There's been no activity on this draft in quite some time, and I > don't expect it to end up advancing. > >> Dec 99 Advance CHAP (RFC 1994) to Standard >> Dec 99 Advance Multilink (RFC 1990) to Standard >> Dec 99 Advance LQM (RFC 1989) to Standard >> Dec 99 Advance IPCP (RFC 1332) to Draft Standard >> Dec 99 Advance CCP (RFC 1962) to Draft Standard >> Dec 99 Advance ECP (RFC 1968) to Draft Standard >> Dec 99 Advance PPP over ISDN (RFC 1618) to Draft Standard >> Mar 00 Advance LCP MIB (RFC 1471) to Draft Standard >> Mar 00 Advance CHAP MIB (RFC 1472) to Draft Standard >> Mar 00 Advance IPCP MIB (RFC 1473) to Draft Standard > > These could be advanced, but it would take some minor work to do the > documentation necessary, and it's not clear that there's substantial > value in it. I find this an extremely interesting statement, esp. coming from a WG chair. You seem to be saying that there is doubtful value in advancing a document beyond Proposed Standard, essentially dismissing the most of the IETF standards process as irrelevant. This is particularly interesting (and somewhat distressing) since Draft Standard is, I believe, the only level that requires evidence of interoperability... > >> Dec 99 Add VLAN support to BCP (RFC 1638) and recycle at Proposed >> Standard > > This milestone has been achieved: RFC 2878 obsoleted 1638. Hope this helps, ~gwz Why is it that most of the world's problems can't be solved by simply listening to John Coltrane? -- Henry Gabriel _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext
- [Pppext] removing the milestones James Carlson
- RE: [Pppext] removing the milestones Glen Zorn (gwz)
- RE: [Pppext] removing the milestones James Carlson
- RE: [Pppext] removing the milestones Nelson, David
- RE: [Pppext] removing the milestones Glen Zorn (gwz)
- RE: [Pppext] removing the milestones James Carlson