Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
William Allen Simpson <wsimpson@greendragon.com> Fri, 09 December 2005 10:55 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 1Ekfur-0003Il-J1; Fri, 09 Dec 2005 05:55:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekfuq-0003II-6m for pppext@megatron.ietf.org; Fri, 09 Dec 2005 05:55:52 -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 FAA16978 for <pppext@ietf.org>; Fri, 9 Dec 2005 05:54:48 -0500 (EST)
Received: from mail.watervalley.net ([64.49.6.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekfup-0006jY-2C for pppext@ietf.org; Fri, 09 Dec 2005 05:55:53 -0500
Received: from [207.74.179.20] (pm916-10.dialip.mich.net [207.74.179.20]) by mail.watervalley.net (Postfix) with ESMTP id 380EF11DE16; Fri, 9 Dec 2005 04:54:58 -0600 (CST)
Message-ID: <43996295.2020003@greendragon.com>
Date: Fri, 09 Dec 2005 05:55: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>
In-Reply-To: <7FB7EE0A621BA44B8B69E5F0A09DC76401170857@xmb-rtp-208.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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
Stan Ratliff (sratliff) wrote: >> 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. > > I, for one, would be OK with this text. > 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. Going back 20+ years, I have had considerable experience deploying protocols over radio links. The best design would be to put a router at every radio link. Goodness gracious, TAL did it commercially going on 15 years ago! Simple 2 port routers are cheap! Also, we have seen a long history here of problems with inter-layer interactions -- multimedia bridges, L2TP, PPPoE, etc, etc. Something close to the original warning is required: 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 consensus of the working group is that implementors would be better advised either to seek ways of making the underlying radio link suitable for general Ethernet-like use, or to abandon the incomplete emulation of Ethernet entirely. -- 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