[dhcwg] Preparation for dhc WG meeting in Vienna
Ralph Droms <rdroms@cisco.com> Tue, 08 July 2003 13:04 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20305; Tue, 8 Jul 2003 09:04:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zs8W-0000UK-L2; Tue, 08 Jul 2003 09:04:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zs82-0000Sn-6W for dhcwg@optimus.ietf.org; Tue, 08 Jul 2003 09:03:30 -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 JAA20219 for <dhcwg@ietf.org>; Tue, 8 Jul 2003 09:03:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zs80-0001NR-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 09:03:28 -0400
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 19Zs80-0001N0-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 09:03:28 -0400
Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 08 Jul 2003 06:05:34 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h68D2q7F003497 for <dhcwg@ietf.org>; Tue, 8 Jul 2003 06:02:52 -0700 (PDT)
Received: from rdroms-w2k.cisco.com (sjc-vpn1-159.cisco.com [10.21.96.159]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AAM06034; Tue, 8 Jul 2003 09:02:49 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030708081241.00baec18@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 08 Jul 2003 09:02:44 -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] Preparation for dhc WG meeting in Vienna
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>
Here are some more details about the dhc WG meeting in Vienna. Please be sure to read the drafts and come prepared to discuss the specific issues... IPv4 Network Attachment Detection <draft-aboba-dhc-nad-ipv4-00.txt> This draft collects and formally describes experience gained in the detection of network attachment. The final document will be relevant to the DHCP specification. DHCP PXE Suboptions <draft-johnston-pxe-options-00.txt> Several years ago, the dhc WG discussed three DHCP options to support the PXE boot protocol. Those options were assigned option codes but never specified in an RFC. We will discuss the specifics of the specifications in this draft and how to proceed toward a published IETF specification. Site Specific Options for DHCP for IPv6 <draft-volz-dhc-dhcpv6-site-options-00.txt> DHCPv4 reserves option codes 128-254 for site specific options that can be used within a site without a published IETF specification. This draft defines site-specific options for DHCPv6. Vendor-Identifying Vendor Options for DHCPv4 <draft-littlefield-dhcp-vendor-00.txt> Based on experience with the DHCPv4 vendor-specific options, the DHCPv6 specification includes a somewhat expanded definition of vendor-specific options: multiple instances of the vendor-specific option are allowed and each instance of the vendor-specific option includes a vendor identifier. A similarly expanded vendor-specific option is needed for DHCPv4 - for example, to accommodate DOCSIS-capable devices that need DOCSIS-specific options as well as vendor-specific options. DHCPv4 Threat Analysis draft-ietf-dhc-v4-threat-analysis-00.txt The threat analysis design team has completed a draft of its review of DHCPv4 security threats. Following a review of that draft, the design team will invite proposals for protocol designs that address the security threats. RFC3118 Delayed Authentication Using PANA <draft-tschofenig-pana-bootstrap-rfc3118-00.txt> This draft specifies an alternative authentication mechanism. DHCP RSA/DSA Authentication using DNS KEY records <draft-ietf-dhc-auth-sigzero-00.txt> This draft specifies an alternative authentication mechanism. DHCP-DDNS interaction <draft-ietf-dhc-ddns-resolution-05.txt> <draft-ietf-dhc-fqdn-option-05.txt> <draft-ietf-dnsext-dhcid-rr-06.txt> We have 6 remaining issues - the goal of this discussion will be to develop specific text to address each issue. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Preparation for dhc WG meeting in Vienna Ralph Droms