Re: [dhcwg] RFC 3118
Thomas Narten <narten@us.ibm.com> Fri, 08 November 2002 13:19 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 IAA17911 for <dhcwg-archive@odin.ietf.org>; Fri, 8 Nov 2002 08:19:25 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA8DLSO23848 for dhcwg-archive@odin.ietf.org; Fri, 8 Nov 2002 08:21:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DLSv23845 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 08:21:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17898 for <dhcwg-web-archive@ietf.org>; Fri, 8 Nov 2002 08:18:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DJEv23730; Fri, 8 Nov 2002 08:19:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DIXv23694 for <dhcwg@optimus.ietf.org>; Fri, 8 Nov 2002 08:18:33 -0500
Received: from cichlid.adsl.duke.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17801 for <dhcwg@ietf.org>; Fri, 8 Nov 2002 08:15:59 -0500 (EST)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id gA8DHw316596; Fri, 8 Nov 2002 08:17:58 -0500
Message-Id: <200211081317.gA8DHw316596@cichlid.adsl.duke.edu>
To: "BORZ,JOHN (HP-Roseville,ex1)" <john.borz@hp.com>
cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Subject: Re: [dhcwg] RFC 3118
In-Reply-To: Message from "BORZ,JOHN (HP-Roseville,ex1)" <john.borz@hp.com> of "Thu, 07 Nov 2002 19:02:34 EST." <499DC368E25AD411B3F100902740AD650E7E0479@xrose03.rose.hp.com>
Date: Fri, 08 Nov 2002 08:17:57 -0500
From: Thomas Narten <narten@us.ibm.com>
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>
> Is anyone aware of any server implementations of RFC 3118? The proposed DHC recharter includes the following words: > * RFC 3118 defines current security mechanisms for DHCPv4. > Unfortunately, RFC 3118 has neither been implemented nor deployed to > date. There is widespread feeling that its current restriction to > manual keying of clients limits its deployability. I assume that the above statement is correct. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] RFC 3118 BORZ,JOHN (HP-Roseville,ex1)
- Re: [dhcwg] RFC 3118 Thomas Narten