Re: [Pppext] Old RFCs going to Historic
James Carlson <james.d.carlson@sun.com> Mon, 29 November 2004 14:21 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 JAA23611 for <pppext-web-archive@ietf.org>; Mon, 29 Nov 2004 09:21:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmTo-0002KP-Ct for pppext-web-archive@ietf.org; Mon, 29 Nov 2004 09:26:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYm8K-0003Uf-6t; Mon, 29 Nov 2004 09:04:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYm4J-0002LY-Qm for pppext@megatron.ietf.org; Mon, 29 Nov 2004 08:59:55 -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 IAA21773 for <pppext@ietf.org>; Mon, 29 Nov 2004 08:59:54 -0500 (EST)
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYm9E-0001oh-AB for pppext@ietf.org; Mon, 29 Nov 2004 09:05:01 -0500
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id iATDxrVu005226 for <pppext@ietf.org>; Mon, 29 Nov 2004 06:59:53 -0700 (MST)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id iATDxqJd017961 for <pppext@ietf.org>; Mon, 29 Nov 2004 08:59:52 -0500 (EST)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.1+Sun/8.13.1) with ESMTP id iATDxqR4011435; Mon, 29 Nov 2004 08:59:52 -0500 (EST)
Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.1+Sun/8.13.1/Submit) id iATDxq20011432; Mon, 29 Nov 2004 08:59:52 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <16811.11096.370401.888642@gargle.gargle.HOWL>
Date: Mon, 29 Nov 2004 08:59:52 -0500
From: James Carlson <james.d.carlson@sun.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [Pppext] Old RFCs going to Historic
In-Reply-To: Carsten Bormann's message of 29 November 2004 14:49:31
References: <16811.7922.778940.799381@gargle.gargle.HOWL> <7F1DD89B-420D-11D9-82C1-000A95DC4DB6@tzi.org>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: pppext@ietf.org
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Carsten Bormann writes: > > Those marked with "X" below have NOT been stricken from the list and > > will become Historic unless someone speaks up. This includes > > AppleTalk, IPX, and the PPP MIBs. > > This makes me rather curious about the intent. I came to this rather late, by way of a cc on someone else's reply to the list. I think the intent is to make as many old things Historic as possible, and the chosen method is to mark everything prior to some date (2000, perhaps) as "on the list," and request that those who care about those older documents complain to the document editor. > > X RFC1378 The PPP AppleTalk Control Protocol (ATCP) > > X RFC1552 The PPP Internetworking Packet Exchange Control Protocol > > (IPXCP) > > AT and IPX may be historic, but if you still have them, these documents > describe the currently agreed way how to send them over PPP, no? > (But then, I don't care about AT or IPX.) They do continue to describe those protocols, and RFCs are effectively immutable, but I think the intent is to say that new implementations ought not bother with them. > > X RFC1618 PPP over ISDN > > While this is not a particularly great document, I believe it is the > standard for PPP over ISDN (B channels). > (In case you don't know, ISDN is 20 years old but definitely *not* any > more historic at this time than is analog telephony.) > > Something is getting derailed about this whole de-crufting process here. That's somewhat close to what I said in an earlier message to that group. As for RFC 1618, it has had trouble with reality (is octet sync really recommended with ISDN?), but perhaps needs to be removed from the list. -- James Carlson, IP Systems Group? <james.d.carlson@sun.com> Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext
- [Pppext] Old RFCs going to Historic James Carlson
- Re: [Pppext] Old RFCs going to Historic James Carlson
- Re: [Pppext] Old RFCs going to Historic Carsten Bormann
- Re: [Pppext] Old RFCs going to Historic Carsten Bormann
- Re: [Pppext] Old RFCs going to Historic Karl Fox