IETF Logo Mail Archive

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

"Nelson, David" <dnelson@enterasys.com> Fri, 09 December 2005 16:57 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 1EklZ4-0005XF-K8; Fri, 09 Dec 2005 11:57:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EklZ3-0005Vu-PC for pppext@megatron.ietf.org; Fri, 09 Dec 2005 11:57:45 -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 LAA00559 for <pppext@ietf.org>; Fri, 9 Dec 2005 11:56:41 -0500 (EST)
Received: from gtfw2.enterasys.com ([12.25.1.128] ident=firewall-user) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EklZ0-0002XF-Iu for pppext@ietf.org; Fri, 09 Dec 2005 11:57:49 -0500
Received: from NHROCAVG2.ets.enterasys.com ([134.141.79.124]) by gtfw2.enterasys.com (0.25.1/8.12.6) with ESMTP id jB9GvPTV020285 for <pppext@ietf.org>; Fri, 9 Dec 2005 11:57:25 -0500 (EST)
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.124]) by 134.141.79.124 with InterScan Messaging Security Suite; Fri, 09 Dec 2005 11:57:32 -0500
Received: from source ([134.141.79.122]) by host ([134.141.79.124]) with SMTP; Fri, 09 Dec 2005 11:57:32 -0500
Received: from MABOSEVS2.ets.enterasys.com ([134.141.77.30]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 9 Dec 2005 11:57:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Date: Fri, 09 Dec 2005 11:56:51 -0500
Message-ID: <3CFB564E055A594B82C4FE89D215656006B716@MABOSEVS2.ets.enterasys.com>
Thread-Topic: [Pppext] warning suggestions for draft-bberry-pppoe-credit
Thread-Index: AcX83olAnLVoMgKERlOsSksi9c6lZQAAeOhQ
From: "Nelson, David" <dnelson@enterasys.com>
To: pppext@ietf.org
X-OriginalArrivalTime: 09 Dec 2005 16:57:32.0556 (UTC) FILETIME=[A591BCC0:01C5FCE1]
X-pstn-version: pmps:sps_win32_1_1_1c0 pase:2.8
X-pstn-levels: (C:79.5348 M:98.0742 P:95.9108 R:95.9108 S:42.9337 )
X-pstn-settings: 4 (0.2500:0.7500) p:14 m:14 C:14 r:14
X-pstn-addresses: from <dnelson@enterasys.com> forward (org good)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
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

Having been through a similar exercise in another WG, I believe the best
course of action is to negotiate an appropriate "disclaimer" note with
the shepherding AD.  The contents of the note will likely not fully
satisfy the WG members who think the draft is entirely "broken", nor
satisfy the authors who think it's an eminently reasonable extension.

The whole issue of "questionable" extensions to IETF protocols is
something of a murky depth.  The "suitability disclaimer" is the best
available method of dealing with these situations.


_______________________________________________
Pppext mailing list
Pppext@ietf.org
https://www1.ietf.org/mailman/listinfo/pppext

v2.23.0 | Report a Bug | By Email