IETF Logo Mail Archive

[dhcwg] draft-volz-dhc-3942-status-00.txt - next steps?

"Bernie Volz (volz)" <volz@cisco.com> Tue, 02 October 2007 01:07 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IcWEP-0002Co-72; Mon, 01 Oct 2007 21:07:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IcWEN-0002Bg-SZ for dhcwg@ietf.org; Mon, 01 Oct 2007 21:07:23 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IcWEM-0000B6-Ng for dhcwg@ietf.org; Mon, 01 Oct 2007 21:07:23 -0400
X-IronPort-AV: E=Sophos;i="4.21,219,1188792000"; d="scan'208";a="133572349"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 01 Oct 2007 21:07:21 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9217MmU019021 for <dhcwg@ietf.org>; Mon, 1 Oct 2007 21:07:22 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l9217MCJ019704 for <dhcwg@ietf.org>; Tue, 2 Oct 2007 01:07:22 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 Oct 2007 21:07:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 01 Oct 2007 21:07:22 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21052B8417@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-volz-dhc-3942-status-00.txt - next steps?
Thread-Index: AcgEkJYybjeuSE7mSvyB6tCxW2DmVA==
From: "Bernie Volz (volz)" <volz@cisco.com>
To: DHC WG <dhcwg@ietf.org>
X-OriginalArrivalTime: 02 Oct 2007 01:07:22.0454 (UTC) FILETIME=[965D0760:01C80490]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-3.800.1026-15056.000
X-TM-AS-Result: No--8.060700-8.000000-2
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1858; t=1191287242; x=1192151242; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20draft-volz-dhc-3942-status-00.txt=20-=20next=20steps? |Sender:=20 |To:=20=22DHC=20WG=22=20<dhcwg@ietf.org>; bh=WP6Z+CFHXE0xD5dAhRnp/CSJv6KU2L7t56FwqePiHRs=; b=cYQ3wi3rDgA+SfJTQvQrHqoZnstrNSgixe4s6UOMWHB6AGvmSXego0BvRNoejLFuDViU1PkA pd4PAmP347kb/unE2X8vDBacFeDk3VWm0Jip0oHY6xHoMqi/gwWf1Ikp;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [dhcwg] draft-volz-dhc-3942-status-00.txt - next steps?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org

Hi:

draft-volz-dhc-3942-status-00.txt, Status of Reclassifying DHCPv4
Options (RFC 3942), will be expiring later this month.

>From the Prague IETF (March 2007) minutes:

---
Reclassifying DHCPv4 Options - RFC 3942
  Bernie Volz gave an update on the process to reclassify DHCPv4
  options as specified in RFC 3942.  In May, 2006, IANA moved all
  options that were not announced as "in use" to "Available".  Reports
  were received on the following option codes:

  128-135: PXE (only formal submission received; other uses reported
           anecdotally)
  150:     TFTP server addresses documented in
           draft-raj-dhc-tftp-addr-option; no documents received for
           two other reported uses
  175-177: Uses reported but no documents received
  208-211: PXELinux options; documented in draft-ietf-dhc-pxelinux
  220:     Subnet allocation; documented in
           draft-ietf-dhc-subnet-alloc
  221:     Subnet selection; documented in draft-ietf-dhc-agent-vpn-id

  Bernie proposed assigning option codes 128-135, 150, 208-211 and
  220-221 as "Tentatively Assigned", and reclassifying 175-177 as
  ""Available".  Bernie will write an I-D summarizing progress on RFC
  3942 progress for WG review and approval before requesting the
  changes from IANA.
---

So, we need "WG review and approval".

When it expires later this month, I can republish this as an individual
submission or, if adopted by the DHC WG, as a WG document.

I don't believe I've received any comments on this document (either in
favor or raising issues/objections).

Please look it over
(http://www.ietf.org/internet-drafts/draft-volz-dhc-3942-status-00.txt)
as it would be good to incorporate issues before republication and
perhaps you can also indicate whether you are in favor of adopting this
as a WG item.

- Bernie

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

v2.23.0 | Report a Bug | By Email