Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
William Allen Simpson <wsimpson@greendragon.com> Mon, 12 December 2005 00:59 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elc2b-0007lP-6y; Sun, 11 Dec 2005 19:59:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elc2Z-0007lG-JT for pppext@megatron.ietf.org; Sun, 11 Dec 2005 19:59:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01498 for <pppext@ietf.org>; Sun, 11 Dec 2005 19:58:47 -0500 (EST)
Received: from mail.watervalley.net ([64.49.6.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Elc3F-0003zv-RJ for pppext@ietf.org; Sun, 11 Dec 2005 20:00:27 -0500
Received: from [207.74.178.173] (pm914-19.dialip.mich.net [207.74.178.173]) by mail.watervalley.net (Postfix) with ESMTP id 47BAC11D5A5 for <pppext@ietf.org>; Sun, 11 Dec 2005 18:59:10 -0600 (CST)
Message-ID: <439CCB65.1090202@greendragon.com>
Date: Sun, 11 Dec 2005 19:59:17 -0500
From: William Allen Simpson <wsimpson@greendragon.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051025)
MIME-Version: 1.0
To: pppext@ietf.org
Subject: Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
References: <7FB7EE0A621BA44B8B69E5F0A09DC76401170857@xmb-rtp-208.amer.cisco.com> <43996295.2020003@greendragon.com> <17305.33797.545874.434026@gargle.gargle.HOWL>
In-Reply-To: <17305.33797.545874.434026@gargle.gargle.HOWL>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
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
James Carlson wrote: > William Allen Simpson writes: >> While I, for one, would not! Merely describing the protocol deployment >> environment is a part of the specification, not a WG warning about the >> poor design. > > I had intended to integrate that text into the previous warning, not > replace, and was just word-smithing the subset to get the commentary > on the original usage case right. Something like this: > > "The PPP Extensions Working Group (pppext) has reservations about > the desirability of the feature described in this document. In > particular, it solves a general problem at an inappropriate layer > and it may have unpredictable interactions with higher and lower > level protocols. The techniques described in this document are > intended for use with a particular deployment technique that uses a > PPP termination separated from a radio termination by an Ethernet, > and that has radio-side flow control for a slower PPP-only link to > remote nodes. Implementors are better advised to avoid split > termination and use traditional IP routing instead." > OK. I'd say "... split termination with inter-media protocol translation, and use standard Internet Protocol routing instead." Just so it's very clear that there's a box there doing work, probably involves software, monitoring, passing packets between two interfaces that require packet translation, and most other features of an INTER-net router, but not actually meeting the router requirements. After all, as the Cisco folks are saying, it's not "THE router" -- by which they mean their expensive router, as opposed to the other vendor's simpler box. -- William Allen Simpson Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32 _______________________________________________ Pppext mailing list Pppext@ietf.org https://www1.ietf.org/mailman/listinfo/pppext
- [Pppext] warning suggestions for draft-bberry-ppp… James Carlson
- RE: [Pppext] warning suggestions for draft-bberry… Stan Ratliff (sratliff)
- RE: [Pppext] warning suggestions for draft-bberry… James Carlson
- RE: [Pppext] warning suggestions for draft-bberry… Stan Ratliff (sratliff)
- RE: [Pppext] warning suggestions for draft-bberry… James Carlson
- RE: [Pppext] warning suggestions for draft-bberry… Vernon Schryver
- RE: [Pppext] warning suggestions for draft-bberry… Stan Ratliff (sratliff)
- Re: [Pppext] warning suggestions for draft-bberry… William Allen Simpson
- Re: [Pppext] warning suggestions for draft-bberry… James Carlson
- Re: [Pppext] warning suggestions for draft-bberry… Karl Fox
- Re: [Pppext] warning suggestions for draft-bberry… Karl Fox
- Re: [Pppext] warning suggestions for draft-bberry… James Carlson
- Re: [Pppext] warning suggestions for draft-bberry… Vernon Schryver
- Re: [Pppext] warning suggestions for draft-bberry… Karl Fox
- Re: [Pppext] warning suggestions for draft-bberry… James Carlson
- Re: [Pppext] warning suggestions for draft-bberry… Bo Berry
- Re: [Pppext] warning suggestions for draft-bberry… Vernon Schryver
- Re: [Pppext] warning suggestions for draft-bberry… Karl Fox
- Re: [Pppext] warning suggestions for draft-bberry… James Carlson
- Re: [Pppext] warning suggestions for draft-bberry… Mark Lanzo
- RE: [Pppext] warning suggestions for draft-bberry… Nelson, David
- Re: [Pppext] warning suggestions for draft-bberry… Vernon Schryver
- Re: [Pppext] warning suggestions for draft-bberry… James Carlson
- Re: [Pppext] warning suggestions for draft-bberry… James Carlson
- Re: [Pppext] warning suggestions for draft-bberry… William Allen Simpson
- Re: [Pppext] warning suggestions for draft-bberry… William Allen Simpson