Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Karl Fox <karlfox@columbus.rr.com> Fri, 09 December 2005 13:33 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 1EkiN7-0004iz-Vn; Fri, 09 Dec 2005 08:33:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkiN7-0004dj-8z for pppext@megatron.ietf.org; Fri, 09 Dec 2005 08:33:13 -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 IAA03792 for <pppext@ietf.org>; Fri, 9 Dec 2005 08:31:40 -0500 (EST)
Received: from 66.237.112.74.ptr.us.xo.net ([66.237.112.74] helo=lithik.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkiMf-0003WA-6W for pppext@ietf.org; Fri, 09 Dec 2005 08:32:45 -0500
Received: from [209.31.94.10] (account karl HELO [172.30.1.159]) by lithik.com (CommuniGate Pro SMTP 4.3.6) with ESMTPSA id 1139224; Fri, 09 Dec 2005 08:32:32 -0500
In-Reply-To: <17305.33797.545874.434026@gargle.gargle.HOWL>
References: <7FB7EE0A621BA44B8B69E5F0A09DC76401170857@xmb-rtp-208.amer.cisco.com> <43996295.2020003@greendragon.com> <17305.33797.545874.434026@gargle.gargle.HOWL>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <918F3977-B268-4F13-BFB0-FD2FEEF2A876@columbus.rr.com>
Content-Transfer-Encoding: 7bit
From: Karl Fox <karlfox@columbus.rr.com>
Subject: Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Date: Fri, 09 Dec 2005 08:32:30 -0500
To: James Carlson <james.d.carlson@sun.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: pppext@ietf.org, William Allen Simpson <wsimpson@greendragon.com>
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
Can't we work the work "broken" in there somehow? :-) Karl On Dec 9, 2005, at 8:17 AM, 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." > > -- > 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