Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit

Vernon Schryver <vjs@calcite.rhyolite.com> Fri, 09 December 2005 16:28 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 1Ekl6r-0002t7-9c; Fri, 09 Dec 2005 11:28:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekl6p-0002gG-O4 for pppext@megatron.ietf.org; Fri, 09 Dec 2005 11:28:35 -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 LAA26813 for <pppext@ietf.org>; Fri, 9 Dec 2005 11:27:37 -0500 (EST)
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekl6x-0001Xr-Ac for pppext@ietf.org; Fri, 09 Dec 2005 11:28:44 -0500
Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.13.4/8.13.4) with ESMTP id jB9GSJME039708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pppext@ietf.org> env-from <vjs@calcite.rhyolite.com>; Fri, 9 Dec 2005 09:28:19 -0700 (MST)
Received: (from vjs@localhost) by calcite.rhyolite.com (8.13.4/8.13.4/Submit) id jB9GSJWm039707 for pppext@ietf.org; Fri, 9 Dec 2005 09:28:19 -0700 (MST)
Date: Fri, 09 Dec 2005 09:28:19 -0700
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200512091628.jB9GSJWm039707@calcite.rhyolite.com>
To: pppext@ietf.org
Subject: Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
In-Reply-To: <BB7AECAF-1E2C-483F-9B61-FD8FC7A31959@columbus.rr.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

> 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