IETF Logo Mail Archive

[dhcwg] Extending the DHCPv4 option codes

Ralph Droms <rdroms@cisco.com> Mon, 06 October 2003 20:06 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20248; Mon, 6 Oct 2003 16:06:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6bcH-00074N-2F; Mon, 06 Oct 2003 16:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6bbc-00072U-WC for dhcwg@optimus.ietf.org; Mon, 06 Oct 2003 16:05:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20181 for <dhcwg@ietf.org>; Mon, 6 Oct 2003 16:05:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6bba-00033D-00 for dhcwg@ietf.org; Mon, 06 Oct 2003 16:05:18 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1A6bba-00032r-00 for dhcwg@ietf.org; Mon, 06 Oct 2003 16:05:18 -0400
Received: from cisco.com (64.102.124.13) by sj-iport-3.cisco.com with ESMTP; 06 Oct 2003 13:12:09 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h96K4j5g029016 for <dhcwg@ietf.org>; Mon, 6 Oct 2003 16:04:45 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com (rtp-vpn2-201.cisco.com [10.82.240.201]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ACX89274; Mon, 6 Oct 2003 16:04:44 -0400 (EDT)
Message-Id: <4.3.2.7.2.20031006155851.048a9f60@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 06 Oct 2003 16:04:42 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Extending the DHCPv4 option codes
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>

By my rough count, once the option codes list in
draft-ietf-dhc-unused-optioncodes-07 are returned to the list of available
DHCP option codes, there will be about 20 option codes available for
assignment to new options.  We currently have fewer than five documents
specifying new options in the dhc WG document queue, leaving us about 15
option codes for future assignment.

draft-ietf-dhc-extended-optioncodes-00 proposes a couple of ways to extend
the list of available option codes.  At least one of the proposed mechanisms
would take some time to implement, so we should start a decision process now
to give us enough time to implement whatever mechanism we eventually settle on.

Please review draft-ietf-dhc-extended-optioncodes-00 and comment on the
proposed mechanisms.  Feel free to suggest an atlernative if you have a
better idea...

- Ralph


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email