[dhcwg] draft-dhankins-dhcp-option-guidelines-00
"David W. Hankins" <David_Hankins@isc.org> Tue, 24 April 2007 23:48 UTC
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgUkB-00023w-Vt; Tue, 24 Apr 2007 19:48:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgUkA-00023r-Uw for dhcwg@ietf.org; Tue, 24 Apr 2007 19:48:22 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgUk9-0001Kb-VK for dhcwg@ietf.org; Tue, 24 Apr 2007 19:48:22 -0400
Received: by goliath.isc.org (Postfix, from userid 10200) id 016D87D2D; Tue, 24 Apr 2007 16:48:06 -0700 (PDT)
Date: Tue, 24 Apr 2007 16:48:06 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20070424234806.GM8898@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: [dhcwg] draft-dhankins-dhcp-option-guidelines-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0575328216=="
Errors-To: dhcwg-bounces@ietf.org
http://www.ietf.org/internet-drafts/draft-dhankins-dhcp-option-guidelines-00.txt At IETF 67 (San Diego), I gave a presentation on an informative document I called 'Atomic DHCP'. This was, more or less, an examination, and definition of terms of a DHCP software implementation written by Ted Lemon ("ISC DHCP"). I mostly intended to ultimately provide input for a document written by someone far more clever than I that might explore the conclusions of "how to write an adoptable option" more fully. What I heard at that IETF was that the reasons we have for certain advice to DHCP option draft writers is less important than the things we might wish to tell them, and at least a couple of people thought it might be a good idea for me to take a stab at such a document. So as discussed, I've pared down (possibly by not enough, I see now at least two paragraphs that should have gone) and moved the 'Atomic DHCP' explanation to an appendix, and brought the "lessons learned" from the old document into the forefront and completed them. I'd still like to see other appendices for other implementations, or if other implementations are willing to say that they understand the definition to be sufficiently similar to their own, we could generalize the language and make it non-ISC specific ("At least two implementations solved this by..."). At this point, the document is essentially complete so far as I know, which means that any good advice to draft writers you can think of for any section of the document would be great feedback. -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins
_______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] draft-dhankins-dhcp-option-guidelines-00 David W. Hankins
- Re: [dhcwg] draft-dhankins-dhcp-option-guidelines… Stig Venaas
- Re: [dhcwg] draft-dhankins-dhcp-option-guidelines… David W. Hankins