RE: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Vernon Schryver <vjs@calcite.rhyolite.com> Thu, 08 December 2005 18:08 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 1EkQCQ-0004wN-3K; Thu, 08 Dec 2005 13:08:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkQCP-0004sZ-Hr for pppext@megatron.ietf.org; Thu, 08 Dec 2005 13:08:57 -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 NAA19159 for <pppext@ietf.org>; Thu, 8 Dec 2005 13:07:53 -0500 (EST)
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkQCG-0002f2-5H for pppext@ietf.org; Thu, 08 Dec 2005 13:08:49 -0500
Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.13.4/8.13.4) with ESMTP id jB8I8TqQ019718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pppext@ietf.org> env-from <vjs@calcite.rhyolite.com>; Thu, 8 Dec 2005 11:08:29 -0700 (MST)
Received: (from vjs@localhost) by calcite.rhyolite.com (8.13.4/8.13.4/Submit) id jB8I8TI1019717 for pppext@ietf.org; Thu, 8 Dec 2005 11:08:29 -0700 (MST)
Date: Thu, 08 Dec 2005 11:08:29 -0700
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200512081808.jB8I8TI1019717@calcite.rhyolite.com>
To: pppext@ietf.org
Subject: RE: [Pppext] warning suggestions for draft-bberry-pppoe-credit
In-Reply-To: <7FB7EE0A621BA44B8B69E5F0A09DC76401170826@xmb-rtp-208.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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
> "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." That text has nothing to do with the intent of the other text. It tries to apply the impremature of the IETF to the proposal. It is also simply wrong on technial grounds. (e.g. "radios with point-to-point transmission characteristics" is bogus.) For comparison, here is the other text: 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. Unless alternate text that says that the WG *does not* like the proposal and perhaps a little of why, the original text must be used. As James Carlson also wrote: ] (Please -- no matter which side of this divide ] you're on -- direct your flames to /dev/null. Yes, I and the rest of ] the folks here know all of the arguments on both sides. We don't need ] to go over the issues again.) Vernon Schryver vjs@rhyolite.com _______________________________________________ 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