IETF Logo Mail Archive

Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-opt-netboot-05

Ted Lemon <Ted.Lemon@nominum.com> Wed, 07 October 2009 00:55 UTC

Return-Path: <Ted.Lemon@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 BA3963A6818 for <dhcwg@core3.amsl.com>; Tue, 6 Oct 2009 17:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.331
X-Spam-Level:
X-Spam-Status: No, score=-6.331 tagged_above=-999 required=5 tests=[AWL=0.268, 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 hYWUofkzIr4b for <dhcwg@core3.amsl.com>; Tue, 6 Oct 2009 17:55:40 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with ESMTP id DC3A03A67BD for <dhcwg@ietf.org>; Tue, 6 Oct 2009 17:55:36 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKSsvnahcrtFOV2sIFzNbRtk+tALi72j38@postini.com; Tue, 06 Oct 2009 17:57:19 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E53FC1B82E2; Tue, 6 Oct 2009 17:57:22 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.393.1; Tue, 6 Oct 2009 17:57:13 -0700
MIME-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <200910062234.AAA07005@TR-Sys.de>
Date: Tue, 06 Oct 2009 17:57:11 -0700
Content-Transfer-Encoding: 7bit
Message-ID: <AD61797F-DB2D-4889-8888-5339521ADE8F@nominum.com>
References: <200910062234.AAA07005@TR-Sys.de>
To: ah@tr-sys.de
X-Mailer: Apple Mail (2.1076)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
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: Wed, 07 Oct 2009 00:55:41 -0000

On Oct 6, 2009, at 3:34 PM, ah@tr-sys.de wrote:
>

Thanks, that helps to make sense of it.   What do you think about the  
idea of just grouping the URI in with the boot parameters?   Also, you  
said that the client might need more than one bootfile, but the  
current draft doesn't provide any way to differentiate, unless it's in  
the bootfile parameters.  Consequently, I understood that the various  
different bootfile parameters were options to try, not files to be  
loaded in sequence.

v2.23.0 | Report a Bug | By Email