[dhcwg] Results of WG last call on draft-ietf-dhc-3315id-for-v4
Ralph Droms <rdroms@cisco.com> Tue, 20 April 2004 17:08 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04707 for <dhcwg-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:08:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFyT9-00073S-2u for dhcwg-archive@odin.ietf.org; Tue, 20 Apr 2004 12:51:35 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KGpZjV027092 for dhcwg-archive@odin.ietf.org; Tue, 20 Apr 2004 12:51:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFxtN-0005zy-9j for dhcwg-web-archive@optimus.ietf.org; Tue, 20 Apr 2004 12:14:37 -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 MAA00422 for <dhcwg-web-archive@ietf.org>; Tue, 20 Apr 2004 12:14:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFxtL-00026Z-V3 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:14:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFxs2-0001mU-00 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:13:14 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFxrJ-0001VT-00 for dhcwg-web-archive@ietf.org; Tue, 20 Apr 2004 12:12:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFxeH-0007Tn-V5; Tue, 20 Apr 2004 11:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFwnK-0003Y2-Ud for dhcwg@optimus.ietf.org; Tue, 20 Apr 2004 11:04:18 -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 LAA23977 for <dhcwg@ietf.org>; Tue, 20 Apr 2004 11:04:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFwnI-0003PG-8q for dhcwg@ietf.org; Tue, 20 Apr 2004 11:04:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFwmW-00038c-00 for dhcwg@ietf.org; Tue, 20 Apr 2004 11:03:29 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BFwlX-0002ca-00 for dhcwg@ietf.org; Tue, 20 Apr 2004 11:02:27 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 20 Apr 2004 07:12:16 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i3KF1r7v009419 for <dhcwg@ietf.org>; Tue, 20 Apr 2004 08:01:55 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-104.cisco.com [10.86.240.104]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHS54420; Tue, 20 Apr 2004 11:01:51 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040420103705.01fa7e50@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 20 Apr 2004 11:01:43 -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] Results of WG last call on draft-ietf-dhc-3315id-for-v4
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.1 required=5.0 tests=AWL autolearn=no version=2.60
draft-ietf-dhc-3315id-for-v4 did not pass WG last call. Barr Hibbs raised the issue of creating a new DHCP option for the new client identifier. Bernie Volz responded, http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03389.html , and I infer from Barr's message http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03478.html that he now supports using the existing option 61 for the new client identifier. Barr also raised the issue of folding the definition of the new identifier into the revision of RFC 2131 and RFC 2132. Bernie and Ted Lemon responded, http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03426.html and http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03440.html, and I infer from Barr's message http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03478.html that he now supports moving forward with the new client identifier independent of any revision of RFC 2131 and RFC 2132. I asked about an example of a client identifier constructed according to this draft, http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03413.html Finally, Barr provided some editorial corrections and suggestions, http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03478.html and http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg03479.html So, we'll wait for a revision of the draft to be published and then conduct another WG last call. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg