RE: [Pppext] warning suggestions for draft-bberry-pppoe-credit
"Stan Ratliff \(sratliff\)" <sratliff@cisco.com> Thu, 08 December 2005 18:20 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 1EkQNX-0000BI-QS; Thu, 08 Dec 2005 13:20:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkQNV-00008R-Oc for pppext@megatron.ietf.org; Thu, 08 Dec 2005 13:20:26 -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 NAA20490 for <pppext@ietf.org>; Thu, 8 Dec 2005 13:19:26 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkQNR-00035D-Ni for pppext@ietf.org; Thu, 08 Dec 2005 13:20:23 -0500
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 08 Dec 2005 10:20:10 -0800
X-IronPort-AV: i="3.99,231,1131350400"; d="scan'208"; a="238849843:sNHT33830804"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id jB8IK2Mi008049; Thu, 8 Dec 2005 10:20:07 -0800 (PST)
Received: from xmb-rtp-208.amer.cisco.com ([64.102.31.43]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 8 Dec 2005 13:20:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Date: Thu, 08 Dec 2005 13:20:05 -0500
Message-ID: <7FB7EE0A621BA44B8B69E5F0A09DC76401170857@xmb-rtp-208.amer.cisco.com>
Thread-Topic: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Thread-Index: AcX8IgZdDMGryXXiTaqlkVGxKuI0RwAAeYbg
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: James Carlson <james.d.carlson@sun.com>
X-OriginalArrivalTime: 08 Dec 2005 18:20:06.0565 (UTC) FILETIME=[03F9C550:01C5FC24]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
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
James, > > 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. Regards, Stan >-----Original Message----- >From: James Carlson [mailto:james.d.carlson@sun.com] >Sent: Thursday, December 08, 2005 1:06 PM >To: Stan Ratliff (sratliff) >Cc: pppext@ietf.org >Subject: RE: [Pppext] warning suggestions for draft-bberry-pppoe-credit > >Stan Ratliff (sratliff) writes: >> >Ethernet supports multiple protocols. What would you do if someone >> >ran some protocol *other* than PPPoE over this pseudo-Ethernet? >> >Wouldn't you be forced to fix the problem all over again? >> > >> >> I don't understand what you mean here. In our implementation, the >> radio and router are connected via a real Ethernet, not a pseudo- >> Ethernet. There is no intersection I'm aware of with other devices >> on the Ethernet communicating with each other via different >protocols. >> The intent isn't to create a pseudo-Ethernet with the extensions, >> rather, >> the intent is to create a group of pseudo point-to-point links, >> representing >> the individual TDMA radio links, tunneling over the Ethernet >connection >> from radio to router. > >It's Ethernet ... but with a kind of L2 backpressure mechanism that >regular Ethernet itself doesn't quite have. > >My point is that if you had something *other than* PPP to transmit to >those nodes over the radio, then you'd be sunk. You'd have to start >over because PPPoE carries only PPP. > >Your assertion seems to rest on a particular deployment and >combination of protocols: PPP (and nothing else) between radio and >remote nodes, Ethernet (and nothing else) between radio and router, >and no way to implement the patently obvious solution -- just >terminating PPP in the radio and using regular L2 forwarding or IP >routing outside of that context. No PPPoE required. > >Its narrowness makes it extremely suspicious. I agree that there may >well be a problem here that needs to be solved. I'm deeply concerned >that this doesn't actually address the problem in any lasting way and >is instead a diversion for developers. > >> "The techniques described in this document will not be applicable >> to all radio implementations. This document describes extensions >> better applied to radios with point-to-point transmission >> characteristics (e.g. TDMA). When used with multi-access, broadcast >> capable radios such as 802.11, these techniques may have >unpredictable >> interactions with higher and lower layers." > >How about: > > 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. > >-- >James Carlson, KISS Network ><james.d.carlson@sun.com> >Sun Microsystems / 1 Network Drive 71.232W Vox +1 >781 442 2084 >MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 >781 442 1677 > _______________________________________________ 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