RE: [dhcwg] dhc-v4-threat-analysis
"Bernie Volz \(volz\)" <volz@cisco.com> Thu, 04 August 2005 08:49 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0bPy-0000Od-Io; Thu, 04 Aug 2005 04:49:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0bPx-0000OS-Ev for dhcwg@megatron.ietf.org; Thu, 04 Aug 2005 04:49:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12875 for <dhcwg@ietf.org>; Thu, 4 Aug 2005 04:49:31 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0bwl-0005sT-Dj for dhcwg@ietf.org; Thu, 04 Aug 2005 05:23:30 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 04 Aug 2005 04:49:22 -0400
X-IronPort-AV: i="3.95,166,1120449600"; d="scan'208"; a="65178908:sNHT28984708"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j748nIQl002423; Thu, 4 Aug 2005 04:49:19 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 4 Aug 2005 04:49:18 -0400
Subject: RE: [dhcwg] dhc-v4-threat-analysis
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 04 Aug 2005 04:49:17 -0400
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <8E296595B6471A4689555D5D725EBB21742C80@xmb-rtp-20a.amer.cisco.com>
Thread-Topic: [dhcwg] dhc-v4-threat-analysis
Thread-Index: AcWY0PIZwVMqCoLDRn+GB2+e7NZfLgAAEm1w
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, dhcwg@ietf.org
X-OriginalArrivalTime: 04 Aug 2005 08:49:18.0417 (UTC) FILETIME=[66709C10:01C598D1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc:
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
As one of the authors, it was produced with mostly DHCPv4 in mind, though many of the issues apply to DHCPv6 as well. - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > On Behalf Of Tim Chown > Sent: Thursday, August 04, 2005 4:42 AM > To: dhcwg@ietf.org > Subject: [dhcwg] dhc-v4-threat-analysis > > Ralph mentioned this (expired) draft just now. > > The last version can be found here: > > http://www.watersprings.org/pub/id/draft-ietf-dhc-v4-threat-an > alysis-02.txt > > Is there any planned work on DHCPv6? How much of the above > is IPv4-specific? > > -- > Tim/::1 > > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhc-v4-threat-analysis Tim Chown
- RE: [dhcwg] dhc-v4-threat-analysis Bernie Volz (volz)