Re: [dhcwg] Should triggered-reconfigure define a new DHCP message header format?

Bud Millwood <budm@weird-solutions.com> Fri, 14 December 2012 15:23 UTC

Return-Path: <budmillwood@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3910E21F845E for <dhcwg@ietfa.amsl.com>; Fri, 14 Dec 2012 07:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAg8K2q3ABFa for <dhcwg@ietfa.amsl.com>; Fri, 14 Dec 2012 07:23:06 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 697BD21F84ED for <dhcwg@ietf.org>; Fri, 14 Dec 2012 07:23:01 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so6097991ieb.31 for <dhcwg@ietf.org>; Fri, 14 Dec 2012 07:23:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=neyF/H7ogx1L2bnd0c+nQQ+ovv4uIQahFZJ2R7WXJT4=; b=C4XZN3/jlBNJ/xBjfORdK7dHvwxh0GGxxIcGrkaQ7XlK9mh/RH7nAT34f503vAuMtI q6r0+Zm86DHCXDUjDcGfaDMswmkgTVJW+bBgumUPKXmFZQxoE5CxzRuXalk61gxTBfb7 KVgbwNPhsvEG6Vpbad7XN4VY9s8AxSxWyJ7+uQC0wk1nDewp188kwgVtHzJZHtEI7Zj1 s/OIAJ+XShyL2JgYvEkRRL0bIBDF9/muQ7hmCBO8AvCgIwohHPTaMmR7hMJRqsxpKCoj Gu4DkvEpWpmQ4vromBGn9vhNi473fCnB76xelZ4KorH12CUfB8Uq/10gwwloX+fBr5cg LTvQ==
MIME-Version: 1.0
Received: by 10.42.68.203 with SMTP id y11mr4810973ici.26.1355498580984; Fri, 14 Dec 2012 07:23:00 -0800 (PST)
Sender: budmillwood@gmail.com
Received: by 10.64.86.47 with HTTP; Fri, 14 Dec 2012 07:23:00 -0800 (PST)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630747439188@mbx-01.win.nominum.com>
References: <8D23D4052ABE7A4490E77B1A012B63074740F186@mbx-01.win.nominum.com> <8D23D4052ABE7A4490E77B1A012B630747435F45@mbx-01.win.nominum.com> <8D23D4052ABE7A4490E77B1A012B63074743767B@mbx-01.win.nominum.com> <94C682931C08B048B7A8645303FDC9F36E9D16DAE6@PUEXCB1B.nanterre.francetelecom.fr> <30427_1355391399_50C9A1A7_30427_1160_1_983A1D8DA0DA5F4EB747BF34CBEE5CD15A61A65D82@PUEXCB1C.nanterre.francetelecom.fr> <6EBE28CD-41FB-4F35-8A6F-D14864F5E535@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307474389C2@mbx-01.win.nominum.com> <9ED9351E-8213-474C-B79F-6D885558F774@cisco.com> <8D23D4052ABE7A4490E77B1A012B630747438A6F@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E0F5EB342@xmb-rcd-x04.cisco.com> <8D23D4052ABE7A4490E77B1A012B630747438ABF@mbx-01.win.nominum.com> <CAL10_BqwOEVeKR71JRjRhtqy1x755SXPFf8x6v7-ipw+C0JPbQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630747438BB4@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E0F5EB4F7@xmb-rcd-x04.cisco.com> <399EAC0B-D466-472A-A8AF-A16B96ED3B55@cisco.com> <8D23D4052ABE7A4490E77B1A012B630747439188@mbx-01.win.nominum.com>
Date: Fri, 14 Dec 2012 16:23:00 +0100
X-Google-Sender-Auth: I19cDOf-WWvP0qpFwikTXZrOdp8
Message-ID: <CAOpJ=k0Kctghb38BKfU7Stfi-xQOVvOfPiJb_HH_Apu_53JPOQ@mail.gmail.com>
From: Bud Millwood <budm@weird-solutions.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Should triggered-reconfigure define a new DHCP message header format?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Dec 2012 15:23:07 -0000

> b) An alternative reading of "continue the RFC3315 convention" is
> to consider the existing fixed-length message headers defined
> in RFC3315 as the headers that you should use unless you
> *really* need another fixed length message header, and to use
> options in the *existing* 3315-defined message headers.

This sums it up for me. I'll happily add a new message format if
that's where it really belongs, but if seems to belong in the context
of an existing message in any way then it should be an option.

Anything that doesn't throw away messages it doesn't understand is an
accident waiting to happen.

- Bud