Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt-netboot-05
Stephen Jacob <Stephen.Jacob@nominum.com> Tue, 06 October 2009 20:38 UTC
Return-Path: <Stephen.Jacob@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C14C3A68D3 for <dhcwg@core3.amsl.com>; Tue, 6 Oct 2009 13:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXovv+9hysB3 for <dhcwg@core3.amsl.com>; Tue, 6 Oct 2009 13:38:09 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id 163AE3A67BE for <dhcwg@ietf.org>; Tue, 6 Oct 2009 13:38:09 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKSsurEE8DL04d3Pf4tOEVEsu04f5LG7QS@postini.com; Tue, 06 Oct 2009 13:39:47 PDT
Received: by shell-too.nominum.com (Postfix, from userid 11053) id E4A071B82F7; Tue, 6 Oct 2009 13:39:52 -0700 (PDT)
Date: Tue, 06 Oct 2009 13:39:52 -0700
From: Stephen Jacob <Stephen.Jacob@nominum.com>
To: Thomas Huth <THUTH@de.ibm.com>
Message-ID: <20091006203952.GB30094@shell-too.nominum.com>
Mail-Followup-To: Thomas Huth <THUTH@de.ibm.com>, Damien Neil <Damien.Neil@nominum.com>, dhcwg@ietf.org
References: <994ABFCB-3ABF-484C-9855-1EEACC663CF4@nominum.com> <OFF44B7F4A.E3B6EB26-ONC1257647.004B36D7-C1257647.004D435F@de.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <OFF44B7F4A.E3B6EB26-ONC1257647.004B36D7-C1257647.004D435F@de.ibm.com>
User-Agent: Mutt/1.4.2.2i
X-URI: http://www.nominum.com/
Organization: Nominum, Inc.
Cc: dhcwg@ietf.org, Damien Neil <Damien.Neil@nominum.com>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt-netboot-05
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2009 20:38:10 -0000
On Tue, Oct 06, 2009 at 04:03:55PM +0200, Thomas Huth wrote: > Well, by separating the parameters from the boot file option, it's enough > to specify the parameters once for all boot images (if all take the same > parameters). That's much easier to maintain than if copies of the > parameters would be put into the same options as the boot file name (you > would then have to change all options in your DHCP server configuration > file if you want to change only the parameters).> How common do you think it will be to /both/: (1) have multiple boot images AND (2) have them all (or several) share the same boot parameters? It feels to me like your draft introduces significant complexity in order to optimize (not even to support -- it would already be possible; just with duplication of information) for this one case. In every other case, it is significant added complexity for no benefit. It may not seem particularly complex, but as someone involved in writing the server side I am glad that it seems like I would not have to be on the receiving end of these options (and could just send to clients what was administratively configured, thus avoiding having to do a lot of special-case work). Introducing a new form of linkage between options seems like it could be a bit of a pain for implementors, especially of clients. > All in all, I think we're doing the right approach with the latest version > of our draft already. It's also available for more than half a year now, > and so far nobody complained about this yet. Strictly speaking, Damien just did, so somebody has ... however I suspect that you didn't mean to discount what he said. :) I imagine this is a subtle translation issue. Regards, Stephen -- Stephen Jacob | Stephen.Jacob@nominum.com | +1 650 381 6051 Nominum, Inc. | http://www.nominum.com/ | +1 650 381 6000
- [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt-net… Damien Neil
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Huth
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Narten
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Ted Lemon
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Narten
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Ted Lemon
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Narten
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Damien Neil
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Ted Lemon
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Stephen Jacob
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Alfred Hönes
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Ted Lemon
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Huth
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Bud Millwood
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Huth
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Jarrod Johnson
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Jarrod Johnson
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Jarrod Johnson
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Jarrod Johnson
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Bud Millwood
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Jarrod Johnson
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Huth
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Jarrod Johnson
- Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt… Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Niall.oReilly+lists
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Chuck Anderson
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … H. Peter Anvin
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Niall.oReilly+lists
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Narten
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … jarrod.b.johnson@gmail.com
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Woundy, Richard
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Narten
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Woundy, Richard
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Thomas Narten
- Re: [dhcwg] netboot load balancing (was: draft-ie… Thomas Huth
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 … H. Peter Anvin