Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
James Carlson <james.d.carlson@sun.com> Fri, 09 December 2005 14:19 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 1Ekj5Y-0000y5-Df; Fri, 09 Dec 2005 09:19:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekj5W-0000xi-F4 for pppext@megatron.ietf.org; Fri, 09 Dec 2005 09:19:06 -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 JAA09791 for <pppext@ietf.org>; Fri, 9 Dec 2005 09:18:12 -0500 (EST)
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekj5g-00058k-Qh for pppext@ietf.org; Fri, 09 Dec 2005 09:19:18 -0500
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id jB9EJ23F013028 for <pppext@ietf.org>; Fri, 9 Dec 2005 07:19:02 -0700 (MST)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id jB9EJ1We024622 for <pppext@ietf.org>; Fri, 9 Dec 2005 09:19:02 -0500 (EST)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5) with ESMTP id jB9EJ1J6006134; Fri, 9 Dec 2005 09:19:01 -0500 (EST)
Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5/Submit) id jB9EJ1sf006131; Fri, 9 Dec 2005 09:19:01 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17305.37461.664962.331436@gargle.gargle.HOWL>
Date: Fri, 09 Dec 2005 09:19:01 -0500
From: James Carlson <james.d.carlson@sun.com>
To: Karl Fox <karlfox@columbus.rr.com>
Subject: Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
In-Reply-To: Karl Fox's message of 9 December 2005 08:24:34
References: <7FB7EE0A621BA44B8B69E5F0A09DC76401170857@xmb-rtp-208.amer.cisco.com> <43996295.2020003@greendragon.com> <104B0E92-C0C3-4D99-A7D6-DBECC54FF53A@columbus.rr.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
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
Karl Fox writes: > Broken. Yes, I said broken. PPPoE is broken. A PPP-over-Ethernet- > over-radio design that needs new options to work properly is, by > definition, also broken. Broken because the designers designed their > product improperly. And now they want us to accept their broken > design as OK by standardizing it. Agreed; the whole thing is swilly. However, I disagree with that last bit. The only intent here is to publish as Informational (not Standards Track), and to make sure it's specified to be minimally harmful. In an ideal world, we would have been able to argue the authors away from this split-termination design. There wouldn't have been any issue here at all, and no draft to write. However, we haven't quite managed to do that, and they've asked the IESG to publish. In an ideal world, the IETF wouldn't have a vanity press feature such as Informational. Instead, we'd just tell people working on things that are tangential (or inimical) to our agreed-on technical direction to go find or form another standards body. However, the IETF does have this feature, and we've got some built-in limits to what we can stop. I agree it's not pretty, but I think we're getting the best of world that we can have. The authors were directed here to get input from folks who know these protocols, even though they were under little obligation to do so. They got the input and may be mostly disregarding it, but at least the resulting document will have an appropriate warning. -- 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