Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
James Carlson <james.d.carlson@sun.com> Fri, 09 December 2005 16:15 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 1Ekkuc-00071y-CO; Fri, 09 Dec 2005 11:15:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekkub-0006z7-GF for pppext@megatron.ietf.org; Fri, 09 Dec 2005 11:15: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 LAA25047 for <pppext@ietf.org>; Fri, 9 Dec 2005 11:14:47 -0500 (EST)
Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkkuW-00013V-7I for pppext@ietf.org; Fri, 09 Dec 2005 11:15:53 -0500
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id jB9GFaD7026425 for <pppext@ietf.org>; Fri, 9 Dec 2005 09:15:37 -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 jB9GFZWc008723 for <pppext@ietf.org>; Fri, 9 Dec 2005 11:15:36 -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 jB9GFZ1O006592; Fri, 9 Dec 2005 11:15:35 -0500 (EST)
Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5/Submit) id jB9GFZbd006589; Fri, 9 Dec 2005 11:15:35 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17305.44455.749579.858657@gargle.gargle.HOWL>
Date: Fri, 09 Dec 2005 11:15:35 -0500
From: James Carlson <james.d.carlson@sun.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: [Pppext] warning suggestions for draft-bberry-pppoe-credit
In-Reply-To: Vernon Schryver's message of 9 December 2005 08:50:18
References: <17305.37461.664962.331436@gargle.gargle.HOWL> <200512091550.jB9FoIQc002230@calcite.rhyolite.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 2.8 (++)
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
Vernon Schryver writes: > Let's be honest with ourselves. If the difference between "Informational" > and "Standards Track" were real, there would be no need to add the > deprecating text to this proposal. The intent is for the IETF to OK Yes, I'm an implementor, and I have certainly noticed that many (though not exactly _all_; I think that's a bit of hyperbole) customers, users, and other implementors ignore the overly subtle distinction between Standards Track and the rest. I even agree that ditching Informational as a failed experiment would likely work out for the best. That doesn't imply that this is really the right forum to redesign the IETF/IESG process. As long as that process exists, we might as well respect it as best we can. I agree that many people will breeze right past the Informational warning as well as any text (no matter how clear) indicating that the document shouldn't be viewed by anyone ... ever.[1] Just the same, as long as publishing is going to happen no matter what we say here, I think we're in a better place with the text than without. Again, as an implementor, I like being able to say to a customer, "gee, did you notice the warning message? That's why I'm just not going to put a high priority on fixing your bug. Pony up some serious cash or just go away." ;-} [1] Apologies to Trey Parker for stealing^Wborrowing that phrase. -- 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