RE: [dhcwg] dhc WG meeting in Vancouver

"Bernie Volz (volz)" <volz@cisco.com> Mon, 19 November 2007 14:42 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 1Iu7px-0004vr-Ko; Mon, 19 Nov 2007 09:42:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu7pw-0004vj-Ls for dhcwg@ietf.org; Mon, 19 Nov 2007 09:42:56 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iu7ps-00062P-Vz for dhcwg@ietf.org; Mon, 19 Nov 2007 09:42:56 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Nov 2007 09:42:53 -0500
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 lAJEgq19002228; Mon, 19 Nov 2007 09:42:52 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lAJEgDWH005699; Mon, 19 Nov 2007 14:42:50 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Nov 2007 09:42:38 -0500
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
Subject: RE: [dhcwg] dhc WG meeting in Vancouver
Date: Mon, 19 Nov 2007 09:42:31 -0500
Message-ID: <8E296595B6471A4689555D5D725EBB210592C987@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <B810EB94-9CE7-4BF7-A479-42BEB34EB298@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] dhc WG meeting in Vancouver
Thread-Index: AcgpP2nbbZqmYPMlTv+LWxGCXvtU9gBepGoA
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>
X-OriginalArrivalTime: 19 Nov 2007 14:42:38.0869 (UTC) FILETIME=[6EA59C50:01C82ABA]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15554.002
X-TM-AS-Result: No--28.763700-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=4072; t=1195483372; x=1196347372; 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:=20RE=3A=20[dhcwg]=20dhc=20WG=20meeting=20in=20Vancouver |Sender:=20 |To:=20=22Ralph=20Droms=20(rdroms)=22=20<rdroms@cisco.com>; bh=TIP5dCBKMyzrdoQx2lJmM0XBzfxRmIQOTaXixIQ+V5Y=; b=rtVpM3lag7ae6WgsRgHrywX69lT0VQbJPdse2jYbjRrPTLULnBNRJHyCJo5aJJrL0jlUiaAC gPg2eYKiStXOt1eCIKfNiEJRyXT8UMEa6D+JIQZDnRwhL8Ix6leW1KQf;
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: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: dhcwg@ietf.org, Dhc Chairs <dhc-chairs@tools.ietf.org>
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

The only action items remaining are to update the IANA registry with the
current status, which is what this draft was attempting to do.

128  PXE - undefined (vendor specific)                         [RFC4578]
129  PXE - undefined (vendor specific)                         [RFC4578]
130  PXE - undefined (vendor specific)                         [RFC4578]
131  PXE - undefined (vendor specific)                         [RFC4578]
132  PXE - undefined (vendor specific)                         [RFC4578]
133  PXE - undefined (vendor specific)                         [RFC4578]
134  PXE - undefined (vendor specific)                         [RFC4578]
135  PXE - undefined (vendor specific)                         [RFC4578]
150  TFTP server address (Tentatively Assigned - 23 Jun 2005 -
          DRAFT-RAJ-DHC-TFTP-ADDR-OPTION-01.TXT)
175-177 Unassigned                                             [RFC3942]
208  pxelinux.magic (string) = F1:00:74:7E (241.0.116.126) (Tentatively
          Assigned - 23 Jun 2005 - DRAFT-IETF-DHC-PXELINUX-01.TXT)
209  pxelinux.configfile (text) (Tentatively Assigned - 23 Jun 2005 -
          DRAFT-IETF-DHC-PXELINUX-01.TXT)
210  pxelinux.pathprefix (text) (Tentatively Assigned - 23 Jun 2005 -
          DRAFT-IETF-DHC-PXELINUX-01.TXT)
211  pxelinux.reboottime (unsigned integer 32 bits) (Tentatively
          Assigned - 23 Jun 2005 - DRAFT-IETF-DHC-PXELINUX-01.TXT)
220  Subnet Allocation Option (Tentatively Assigned - 23 Jun 2005 -
          DRAFT-IETF-DHC-SUBNET-ALLOC-04.TXT)
221  Virtual Subnet Selection Option    (Tentatively Assigned - 23 Jun
          2005 - DRAFT-IETF-DHC-VPN-OPTION-06.TXT)

The above list is changed slightly because 208-211 are covered by the
soon to be published RFC-ietf-dhc-pxelinux-03.txt and there have been
some revisions to the other documents to get them through WG last call.

- Bernie

-----Original Message-----
From: Ralph Droms (rdroms) 
Sent: Saturday, November 17, 2007 12:28 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org; Dhc Chairs
Subject: Re: [dhcwg] dhc WG meeting in Vancouver

Bernie - are there any action items remaining from RFC 3942?  Might  
be good to (a) update  draft-volz-dhc-3942-status-00 (although I  
regret I'm responding too late for you to make the draft pub  
deadline) and (b) publish a final doc when everything from RFC 3942  
is wrapped up to capture that the issues have all been closed.

- Ralph

On Nov 8, 2007, at Nov 8, 2007,11:30 PM, Bernie Volz (volz) wrote:

> I'd like to discuss what should be done about
> draft-volz-dhc-3942-status-00. It has expired and while I could simply
> make a few edits (such as addressing 208-211) and resubmit, it seems
> silly to do that if there is no support or interest for the DHC WG.
>
> I did ask the DHC WG in early October about next steps for this draft,
> but it didn't go anywhere.
>
> We need to give IANA information about updating the DHCP options
> registry.
>
> - Bernie
>
> -----Original Message-----
> From: Ralph Droms (rdroms)
> Sent: Thursday, November 08, 2007 11:36 AM
> To: dhcwg@ietf.org
> Cc: Dhc Chairs
> Subject: [dhcwg] dhc WG meeting in Vancouver
>
> The dhc WG will meet in Vancouver, http://ietf.org/meetings/70-
> IETF.html; here is the tentative scheduled date and time for our
> meeting:
>
> TUESDAY, December 4, 2007
> 1300-1500 Afternoon Session I
> Salon 1  INT  dhc  Dynamic Host Configuration WG
>
> Please contact the WG chairs, dhc-chairs@tools.ietf.org, with agenda
> requests before Wed, Nov 14.
>
> As always, we are looking for volunteers to act as meeting and Jabber
> scribes.
>
> Here are some important dates: http://ietf.org/meetings/70-
> cutoff_dates.html  Note that the I-D rev -00 submission deadline is
> 0900 EST this coming Mon, 11/12, and the general I-D submission
> deadline is 0900 EST Mon, 11/19.
>
> - Ralph
>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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