[dhcwg] Discussion of DHCP implementation issues
Ralph Droms <rdroms@cisco.com> Thu, 29 January 2004 21:28 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19798 for <dhcwg-archive@odin.ietf.org>; Thu, 29 Jan 2004 16:28:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmJhI-0000GB-6k for dhcwg-archive@odin.ietf.org; Thu, 29 Jan 2004 16:27:36 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0TLRan5000998 for dhcwg-archive@odin.ietf.org; Thu, 29 Jan 2004 16:27:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmJhI-0000Fz-1k for dhcwg-web-archive@optimus.ietf.org; Thu, 29 Jan 2004 16:27:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19670 for <dhcwg-web-archive@ietf.org>; Thu, 29 Jan 2004 16:27:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmJhG-0004vS-00 for dhcwg-web-archive@ietf.org; Thu, 29 Jan 2004 16:27:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmJfd-0004Yl-00 for dhcwg-web-archive@ietf.org; Thu, 29 Jan 2004 16:25:54 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AmJeM-0004F8-00 for dhcwg-web-archive@ietf.org; Thu, 29 Jan 2004 16:24:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmJeN-00086v-5W; Thu, 29 Jan 2004 16:24:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmJYh-0007Ev-4k for dhcwg@optimus.ietf.org; Thu, 29 Jan 2004 16:18:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18977 for <dhcwg@ietf.org>; Thu, 29 Jan 2004 16:18:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmJYf-0003Yo-00 for dhcwg@ietf.org; Thu, 29 Jan 2004 16:18:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmJXl-0003S3-00 for dhcwg@ietf.org; Thu, 29 Jan 2004 16:17:45 -0500
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 1AmJXK-0003Jl-00 for dhcwg@ietf.org; Thu, 29 Jan 2004 16:17:18 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 29 Jan 2004 13:22:32 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0TLGkPn016588 for <dhcwg@ietf.org>; Thu, 29 Jan 2004 13:16:47 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-113.cisco.com [10.86.242.113]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFQ76115; Thu, 29 Jan 2004 16:15:19 -0500 (EST)
Message-Id: <4.3.2.7.2.20040129160545.01f01008@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 29 Jan 2004 16:15:17 -0500
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] Discussion of DHCP implementation issues
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
At the WG meeting in Minneapolis, the WG reviewed draft-ietf-dhc-implementation-01.txt. During the review, the WG decided to hold a conference call and possibly a workshop to come to closure on the various issues in draft-ietf-dhc-implementation-01.txt. I'd like to schedule the conf call for the week of 2/23 (the week before the IETF meeting in Seoul). To begin organizing the call, please respond to the dhcwg list with: * an indication if you are interested in joining the call * your timezone and available times * goals for the meeting * specific agenda items - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Discussion of DHCP implementation issues Ralph Droms
- FW: [dhcwg] Discussion of DHCP implementation iss… Barr Hibbs
- RE: [dhcwg] Discussion of DHCP implementation iss… Bernie Volz
- Re: [dhcwg] Discussion of DHCP implementation iss… Vijayabhaskar A K