Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Karl Fox <karlfox@columbus.rr.com> Fri, 09 December 2005 16:42 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 1EklK7-0007vH-Hr; Fri, 09 Dec 2005 11:42:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EklK6-0007rS-OE for pppext@megatron.ietf.org; Fri, 09 Dec 2005 11:42:18 -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 LAA28978 for <pppext@ietf.org>; Fri, 9 Dec 2005 11:41:08 -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 1EklK3-000257-H9 for pppext@ietf.org; Fri, 09 Dec 2005 11:42:16 -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 1139287; Fri, 09 Dec 2005 11:41:57 -0500
In-Reply-To: <200512091628.jB9GSJWm039707@calcite.rhyolite.com>
References: <200512091628.jB9GSJWm039707@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <5BEF683C-7341-4581-821D-C1FAD653311B@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 11:41:56 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
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
Yes, it did do an end run around PPPEXT, but since then I've seen more hints that the IESG might be willing to listen to the WG as expert on the topic and act accordingly. I say we ask them to nix the whole thing, and come back to us for text mods if they disagree. Why can't the company just fix their design? Karl On Dec 9, 2005, at 11:28 AM, Vernon Schryver wrote: >> From: Karl Fox <karlfox@columbus.rr.com> > >> Frankly, I agree with Vern. Why can't the WG simply tell the IESG >> that it's a bad idea because the need is based on a defective product >> design? Surely they'd understand that--they're protocol designers, >> too. Who knows, maybe they'd say no, too. > > I see reasons not to tell the IESG "No": > > - The IESG might refuse to go along, which would encourage more > results > like PPPoE itself. (I have no recollections of debate about PPPoE > here. Am I wrong in thinking it bypassed this WG?) > > - If the IESG went along, the idea would be published in some > "PPPoE Forum" as the best thing since sliced bread and without any > caveats, and perhaps even without the improvements that have been > made to it here. > > - We should save our very limited power to say "No" and mean it > for worse things. > > > 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