[dhcwg] dhc WG last call on draft-ietf-dhc-v4-threat-analysis-02

Ralph Droms <rdroms@cisco.com> Tue, 13 July 2004 10:19 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28721; Tue, 13 Jul 2004 06:19:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkKCz-0004H0-Gr; Tue, 13 Jul 2004 06:08:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkK8F-0002fo-E1 for dhcwg@megatron.ietf.org; Tue, 13 Jul 2004 06:03:27 -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 GAA27478 for <dhcwg@ietf.org>; Tue, 13 Jul 2004 06:03:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkK8D-0006Rm-2q for dhcwg@ietf.org; Tue, 13 Jul 2004 06:03:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkK7H-000698-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 06:02:27 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BkK6P-0005Yn-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 06:01:33 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-1.cisco.com with ESMTP; 13 Jul 2004 03:01:52 -0700
X-BrightmailFiltered: true
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 i6DA13ZU016283 for <dhcwg@ietf.org>; Tue, 13 Jul 2004 03:01:03 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-77.cisco.com [10.86.242.77]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AKB82416; Tue, 13 Jul 2004 06:01:02 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040713055938.02c1de60@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 13 Jul 2004 06:00:14 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-v4-threat-analysis-02
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

This message announces a WG last call on "Dynamic Host Configuration
Protocol for IPv4 (DHCPv4) Threat Analysis"
<draft-ietf-dhc-v4-threat-analysis-02>.  The last call will conclude
at (insert date here).

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

"Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Threat
Analysis" provides a comprehensive threat analysis of the Dynamic Host
Configuration Protocol.  DHCPv4 (RFC 2131) is a stable, widely used
protocol for configuration of host systems in a TCP/IPv4 network. RFC
2131 did not provide for authentication of clients and servers, nor
did it provide for data confidentiality. This is reflected in the
original "Security Considerations" section of RFC 2131, which
identifies a few threats and leaves development of any defenses
against those threats to future work. Beginning in about 1995 DHCP
security began to attract attention from the Internet community,
eventually resulting in the publication of RFC 3118 in 2001. Although
RFC 3118 was a mandatory prerequisite for the DHCPv4 Reconfigure
Extension, RFC 3203, it has had no known usage by any commercial or
private implementation since its adoption. The DHC Working Group has
adopted a work item to review and modify or replace RFC 3118 to afford
a workable, easily deployed security mechanism for DHCPv4. This memo
provides a comprehensive threat analysis of the Dynamic Host
Configuration Protocol for use both as RFC 2131 advances from Draft
Standard to Full Standard and to support our chartered work improving
the acceptance and deployment of RFC 3118. This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-v4-threat-analysis-02.txt

- Ralph Droms 


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