Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
William Allen Simpson <wsimpson@greendragon.com> Mon, 12 December 2005 01:36 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 1Elcbt-0007Pv-KL; Sun, 11 Dec 2005 20:36:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Elcbs-0007PU-P0 for pppext@megatron.ietf.org; Sun, 11 Dec 2005 20:36:12 -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 UAA04864 for <pppext@ietf.org>; Sun, 11 Dec 2005 20:35:08 -0500 (EST)
Received: from mail.watervalley.net ([64.49.6.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElccS-000549-5h for pppext@ietf.org; Sun, 11 Dec 2005 20:36:48 -0500
Received: from [207.74.178.173] (pm914-19.dialip.mich.net [207.74.178.173]) by mail.watervalley.net (Postfix) with ESMTP id 4151811C7A8; Sun, 11 Dec 2005 19:35:51 -0600 (CST)
Message-ID: <439CD402.5040905@greendragon.com>
Date: Sun, 11 Dec 2005 20:36:02 -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: <200512091657.LAA28631@cisco.com>
In-Reply-To: <200512091657.LAA28631@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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
Mark Lanzo wrote: > On 9 Dec, William Allen Simpson wrote: >> 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! > > Would it help if the proposal began with a clearer explanation that > although it "extends" PPPoE, that the usage is not in fact for PPPoE > as traditionally recognized, but instead is being used as a protocol > for using an ethernet as a backplace for communicating with external > serial-port "concentrators"? Is there a different RFC this group > should be looking at, which already provides just this sort of thing? > Ah yes, I remember when it was thought that implementing PPP was too complex for a "serial port concentrator" until Telebit did it on a 286, and then many other firms. Took Cisco years to catch up. And I remember when it was thought PPP was too complex for end user terminal devices, until Vocal did it in a modem that could sit in the palm of your hand, and Qualcomm did it in a cell phone (IIRC, both were 186 embedded processors with something like 4K RAM). The Qualcomm phones could run *2* PPP sessions, one over the radio link, and another over the serial port to a laptop, _and_ emulate a fax/modem, _and_ run simultaneous voice. (Disclaimer: I helped design and implement all products mentioned above, so I'm probably biased.) You might look at EIA/TIA/CTIA IS-99, although it's probably not an Interim Standard anymore (having written the thing circa 1993). And that also would still require modification to the radio.... Really, just because there are "dumb" ethernet-radio bridges doesn't mean they're a good idea. Especially in these days of cheap memory. Caveat emptor. -- 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