[dhcwg] Review of DHCPv4 Implementation Issues
"Barr Hibbs" <rbhibbs@pacbell.net> Mon, 03 February 2003 20:50 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21261 for <dhcwg-archive@odin.ietf.org>; Mon, 3 Feb 2003 15:50:46 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h13KttS24619 for dhcwg-archive@odin.ietf.org; Mon, 3 Feb 2003 15:55:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13KtsJ24616 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 3 Feb 2003 15:55:54 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21237 for <dhcwg-web-archive@ietf.org>; Mon, 3 Feb 2003 15:50:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13Ks3J24543; Mon, 3 Feb 2003 15:54:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13KrbJ24514 for <dhcwg@optimus.ietf.org>; Mon, 3 Feb 2003 15:53:37 -0500
Received: from smtp015.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21123 for <dhcwg@ietf.org>; Mon, 3 Feb 2003 15:47:57 -0500 (EST)
Received: from adsl-64-169-91-213.dsl.snfc21.pacbell.net (HELO BarrH63p601) (rbhibbs@pacbell.net@64.169.91.213 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 3 Feb 2003 20:51:33 -0000
Reply-To: rbhibbs@pacbell.net
From: Barr Hibbs <rbhibbs@pacbell.net>
To: Dhcwg <dhcwg@ietf.org>
Date: Mon, 03 Feb 2003 12:50:36 -0800
Message-ID: <JCELKJCFMDGAKJCIGGPNIEAOFAAA.rbhibbs@pacbell.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Review of DHCPv4 Implementation Issues
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
One of the work items adopted by the DHC Working Group at IETF-55 in Atlanta was a review of what I'll generically call "implementation issues" faced by implementors of DHCP clients, servers, and relay agents. The purpose of this review is to identify areas of the protocol that were: 1. not well-specified 2. described in a less-than-clear way 3. had dubious value or harmful side-effects 4. conflicted with other RFCs 5. internally inconsistent, that is, conflicted with other sections of the specification 6. "difficult" to implement or test for interoperability 7. not implemented because of external policies 8. "seemed like a good idea" at the time, but are now considered unnecessary, redundant, or wrong I'm calling on all implementors, developers, and designers to offer their observations, comments, wishes, anecdotes, and observations so that we may create a list of problem areas that need resolution before submitting the RFC for consideration as a full Internet Standard. Even typographical errors, grammatical mistakes, and organizational issues are fair game for this purpose. Thanks in advance for your help. --Barr _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg