Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 - how to proceed?

Ted Lemon <Ted.Lemon@nominum.com> Fri, 23 October 2009 16:09 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 F08D93A67E6 for <dhcwg@core3.amsl.com>; Fri, 23 Oct 2009 09:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.141
X-Spam-Level:
X-Spam-Status: No, score=-5.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, 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 plk8xKAfOCfS for <dhcwg@core3.amsl.com>; Fri, 23 Oct 2009 09:09:29 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by core3.amsl.com (Postfix) with ESMTP id 3CB083A67AD for <dhcwg@ietf.org>; Fri, 23 Oct 2009 09:09:29 -0700 (PDT)
Received: from [IPv6:2620::b60:3:226:bbff:fe0c:e5bf] (unknown [IPv6:2620:0:b60:3:226:bbff:fe0c:e5bf]) by toccata.fugue.com (Postfix) with ESMTPSA id 19EE934E564F; Fri, 23 Oct 2009 09:11:17 -0700 (MST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/html; charset="us-ascii"
X-Apple-Base-Url: x-msg://255/
X-Apple-Mail-Remote-Attachments: NO
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <200910221941.n9MJfSV7019188@cichlid.raleigh.ibm.com>
X-Apple-Windows-Friendly: 1
Date: Fri, 23 Oct 2009 09:08:56 -0700
X-Apple-Mail-Signature:
Content-Transfer-Encoding: quoted-printable
Message-Id: <82D0F823-61A5-45F9-A87E-21720DF221F9@nominum.com>
References: <200910062234.AAA07005@TR-Sys.de><AD61797F-DB2D-4889-8888-5339521ADE8F@nominum.com><OF029AB4A7.6EEA954A-ONC125764B.004E95CE-C125764B.00536F30@de.ibm.com><FBD14811-7C9A-4FCB-8707-071A7CA12B96@nominum.com><OF73909874.9B93FADE-ONC1257653.002E96C8-C1257653.00302A9F@de.ibm.com><589F59F0-3E17-44FF-8918-FED51F03EE4D@nominum.com><4ADC156D.1070709@ucd.ie><669B95F2-FA8F-47AA-AB8A-4292DDB1A4EF@nominum.com><4ADD70CB.2080409@ucd.ie><OF2692FAA8.2F4AF98C-ONC1257657.002954C1-C1257657.00298474@de.ibm.com> <200910221814.n9MIETQR002070@cichlid.raleigh.ibm.com> <8A82D1BFEDDE7E4597978355239BBBCB4C204C@PACDCEXCMB06.cable.comcast.com> <200910221921.n9MJLJgW010502@cichlid.raleigh.ibm.com> <8A82D1BFEDDE7E4597978355239BBBCB4C2063@PACDCEXCMB06.cable.comcast.com> <200910221941.n9MJfSV7019188@cichlid.raleigh.ibm.com>
X-Uniform-Type-Identifier: com.apple.mail-draft
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1077)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-netboot-05 - how to proceed?
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: Fri, 23 Oct 2009 16:09:30 -0000

On Oct 22, 2009, at 12:41 PM, Thomas Narten wrote:
Well, I wasn't all that clear in my first note either! I'm really
hoping for the same. I'd be happy to support load balancing, but only
if was a real requirement coming from the folk who are using netboot
and have experience with it. Otherwise, I'd prefer that we keep things
simple.

I may be speaking out of turn here, but I think that the fact that this draft explicitly recommends http over tftp for downloading the boot file will solve a lot of the load problems that exist with the current DHCP/tftp boot mechanism in DHCPv4.   As I understand it, the primary problem with netbooting in IPv4 is that tftp is such a low-performance solution (due to the lock-step nature of the protocol), not that tftp boot servers get overloaded during power events.