[dhcwg] *DRAFT* minutes from dhc WG meeting, IETF 56
Ralph Droms <rdroms@cisco.com> Thu, 10 April 2003 18:46 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00433 for <dhcwg-archive@odin.ietf.org>; Thu, 10 Apr 2003 14:46:25 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3AIqEd03292 for dhcwg-archive@odin.ietf.org; Thu, 10 Apr 2003 14:52:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIqE803289 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 10 Apr 2003 14:52:14 -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 OAA00395 for <dhcwg-web-archive@ietf.org>; Thu, 10 Apr 2003 14:45:54 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 193gnV-0003Ua-00 for dhcwg-web-archive@ietf.org; Thu, 10 Apr 2003 14:29:17 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 193gnV-0003UX-00 for dhcwg-web-archive@ietf.org; Thu, 10 Apr 2003 14:29:17 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIjx802968; Thu, 10 Apr 2003 14:45:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AIh5802845 for <dhcwg@optimus.ietf.org>; Thu, 10 Apr 2003 14:43:05 -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 OAA29981 for <dhcwg@ietf.org>; Thu, 10 Apr 2003 14:36:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 193gee-0003PJ-00 for dhcwg@ietf.org; Thu, 10 Apr 2003 14:20:08 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by ietf-mx with esmtp (Exim 4.12) id 193gee-0003Og-00 for dhcwg@ietf.org; Thu, 10 Apr 2003 14:20:08 -0400
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3AIcoRP024353 for <dhcwg@ietf.org>; Thu, 10 Apr 2003 14:38:50 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-192.cisco.com [161.44.149.192]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA26789 for <dhcwg@ietf.org>; Thu, 10 Apr 2003 14:38:49 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030410143352.042e9610@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 10 Apr 2003 14:38:47 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [dhcwg] *DRAFT* minutes from dhc WG meeting, IETF 56
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>
Included below are *DRAFT* minutes from the dhc WG meeting in SF. Please respond with additions, deletions or corrections before 4PM EDT, Fri 4/11. - Ralph ----- Minute of dhc WG Meeting, IETF 56 ================================= Administrivia, agenda bashing, WG progress report - Ralph Droms --------------------------------------------------------------- Progress report since last WG meeting: RFCs published: The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4, RFC3442 Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration, RFC3495 Accepted as Draft Standard: DHCPv6 Link Selection sub-option for the Relay Agent Information Option for DHCPv4 Passed last call: Security Ticket Control Sub-option for the CableLabs Client Configuration Option DNS Configuration options for DHCPv6 NIS Configuration Options for DHCPv6 Time Configuration Options for DHCPv6 DHCP Options for Internet Storage Name Service IPv6 Prefix Options for DHCPv6 Review of new charter, request for milestones - Ralph Droms ----------------------------------------------------------- Droms announced that charter had been accepted by IESG and posted to www.ietf.org. He noted that draft authors will be asked to supply milestones for posting with the charter. DHCP security review team report - Barr Hibbs --------------------------------------------- Review team has made progress but did not publish draft prior to pre-IETF deadline; team will publish initial draft after IETF blackout. Focus is currently on DHCPv4, but results may be applicable to DHCPv6 as well. Vipul Gupta has agreed to re-publish earlier draft on certificate-based DHCP authentication. Ted Lemon and Michael Richardson have published a draft using SIG(0) keys (see below). 'Securing DHCP with DNSSEC bourne public keys' - Ted Lemon <draft-richardson-dhc-auth-sig0-00.txt> ---------------------------------------------------------- This draft was published just before the IETF deadline and is incomplete. The fundamental idea in this draft is to perform DHCP authentication using DNS SIG(0) keys. The WG accepted the draft as WG work item. Authentication of relay agent options - John Schnizlein ------------------------------------------------------- Schnizlein volunteered at previous IETF to conduct comparison of two proposals for securing communication between a relay agent and server (draft-ietf-dhc-auth-suboption-01.txt, Stapp and Lemon; draft-droms-dhcp-relay-agent-ipsec-00.txt, Droms). His conclusion is that the proposals are each applicable in different situations. Thomas Narten questioned whether the WG should advance two mechanisms that address the same problem. The authors of the two drafts and Schnizlein said the two proposals may be appropriate in different environments, if IPsec is already available on all the participating components, the IPsec-based method may be usable with no additional configuration or software updates; the authentication has better scalability (key management) properties when IPsec is not already deployed. Narten suggested we could flip a coin to choose between the two proposals. Droms observed that, while there is some overlap between the applicability of the two proposals, there are significant cases in which only one of the two is appropriate. The WG will continue to work on both proposals. VPN-ID option and sub-option - Kim Kinnear <draft-ietf-dhc-vpn-option-02.txt> <draft-ietf-dhc-agent-vpn-id-02.txt> ------------------------------------------- Narten asked about the requirements for these options - what problem spaces do they apply to? What are the situations in which the server sends the option to the client/relay agent and what are the situations in which the client/relay agent sends the option to the server? Erik Nordmark asked about security considerations. John Schnizlein suggested the use of "VPN" in the name might be confusing - this option is intended to pass a VPN identifier as additional information about a client, rather than use a VPN in any kind of security. These two drafts are ready for WG last call after a name change and addition of an example case. DHCP server MIB - Barr Hibbs <draft-ietf-dhc-server-mib-08.txt> ---------------------------------- This draft is ready for WG last call; the MIB doctors who reviewed the draft will be asked to comment during WG last call. Option code recovery - Ralph Droms <draft-ietf-dhc-unused-optioncodes-00.txt> ------------------------------------------ This draft will be revised to edit out option codes related to PXE standard and to add more words about the plan for the use of draft; the document will then be ready for WG last call. Option code extensions - Bernie Volz <draft-volz-dhc-extended-optioncodes-00.txt> -------------------------------------------- This document resurrects an old proposal from Droms about using option codes 126 and 127 for options that would extend the DHCP option code space with 16-bit option codes. Volz proposes redefining option codes in the range 128-223 as DHCP option codes (managed by IANA), leaving option codes 224-254 as site-specific options codes. The WG accepted this document as a WG work item. Review of DHCP RFCs - Barr Hibbs draft-ietf-dhc-implementation-00.txt ------------------------------------ Hibbs is collecting references to text in the DHCP RFCs that is confusing, contradictory, incomplete, conflicted with other RFCs, difficult to implement, or could only be resolved by consensus at connectathons. The objective is to document these issues and suggest clarifications and corrections where necessary. The final document will be used in moving DHCP to full Standard. Rob Stevens is co-editor; the work was started three years ago by Mike Carney. Hibbs asked for more input. Failover protocol - Kinnear draft-ietf-dhc-failover-12.txt ------------------------------ Kinnear reported on changes since last revision and discussion. There was a meeting of failover authors and implementors in Atlanta, IETF 55: Kim Kinnear, Scanner Luce, Bernie Volz, Mark Stapp. Notes from that meeting are available at http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg01902.html. Narten suggested publishing as Experimental. There are at least 6 implementations and at least two implementors reported customer interest in failover that will interoperate between DHCP servers from different vendors. One vendor (Lucent) noted that there has never been a request for their implementation. Droms asked if Experimental could be a step towards Standards track. Narten responded that SRV started as Experimental. Kinnear said he had no problem with Experimental; the important issue is to get a stake in the ground for implementors to work toward. WG responded that Proposed Standard is appropriate. Draft is now ready for WG last call. Lease query protocol - Kim Kinnear draft-ietf-dhc-leasequery-05.txt ---------------------------------- Kinnear described changes to draft and noted that there have been questions about the functions provided by the most recent document relative to the problem statement in the introduction. Narten expressed concern about feature creep; that is, using this mechanism to supply information to a network element that wouldn't be available to the network element through DHCP messages. Kinnear will revise draft to provide information retrieval capability identical to what could be obtained through reading DHCP messages. Document will then be ready for WG last call. DHCPv6 status - Ralph Droms draft-ietf-dhc-dhcpv6-28.txt draft-ietf-dhc-dhcpv6-interop-01.txt ------------------------------------ The base protocol specification has been accepted as Proposed Standard. Several options have passed WG last call and are ready to be forwarded to the IESG. Two rounds of interoperability testing have been conducted (TAHI and Connectathon), resulting in identification of several minor editorial and clarification issues. These issues have been published in draft-ietf-dhc-dhcpv6-interop-01.txt and will be announced to IETF. The changes documented with the issues in that draft will be made before publication of the RFC. IPv4 Link Local addressing issue from zeroconf WG - Lemon --------------------------------------------------------- Ted explained that there is a dependency between IPv4LL and DHCP: the current specification for IPv4LL restricts an interface to be configured with either a routable IPv4 address or an IPv4LL address. However, transition from DHCP-assigned address to an IPv4LL address will require a change to RFC2131, to cause a DHCP client to drop its routable address in favor of an IPv4LL address when INIT-REBOOT fails. Ted will publish a summary of the issue to the DHC WG mailing list. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg