[dhcwg] Security for leasequery messages

Ralph Droms <rdroms@cisco.com> Wed, 07 April 2004 04:25 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06786 for <dhcwg-archive@odin.ietf.org>; Wed, 7 Apr 2004 00:25:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB4cW-0006NM-Dw for dhcwg-archive@odin.ietf.org; Wed, 07 Apr 2004 00:25:00 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i374P0kj024508 for dhcwg-archive@odin.ietf.org; Wed, 7 Apr 2004 00:25:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB4cW-0006ND-Aj for dhcwg-web-archive@optimus.ietf.org; Wed, 07 Apr 2004 00:25:00 -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 AAA06663 for <dhcwg-web-archive@ietf.org>; Wed, 7 Apr 2004 00:24:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BB4cT-0004vs-00 for dhcwg-web-archive@ietf.org; Wed, 07 Apr 2004 00:24:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BB3mf-0005YT-00 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 23:31:26 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BB2V8-0006AZ-00 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 22:09:15 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BB2V8-0003JL-QZ for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 22:09:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB2OG-0004UR-0A; Tue, 06 Apr 2004 22:02:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB2Nj-0004Kv-Ly for dhcwg@optimus.ietf.org; Tue, 06 Apr 2004 22:01:35 -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 WAA25058 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 22:01:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BB2Ng-0005AZ-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 22:01:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BB1cy-0006bn-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 21:13:17 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BB0Qx-000754-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 19:56:47 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 06 Apr 2004 16:03:58 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i36NuGGF006643 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 16:56:16 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-83.cisco.com [10.86.240.83]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHK35294; Tue, 6 Apr 2004 19:56:14 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040406195254.02bc7b90@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 06 Apr 2004 19:56:12 -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] Security for leasequery messages
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

The following issues relate to security for leasequery messages:

Steve Bellovin:

Discuss:
(26 March 2004)
The Security Considerations section says this:

    DHCP servers SHOULD prevent exposure of location information
    (particularly the mapping of hardware address to IP address lease,
    which can be an invasion of broadband subscriber privacy) by
    employing some form of relay agent authentication between the
    DHCPLEASEQUERY client and the DHCP server.

    Clients of the DHCPLEASEQUERY message SHOULD ensure that their data
    path to the DHCP server is secure.  Clients SHOULD use Relay Agent
    Information security as a way to achieve this goal.

What is "some form of ... authentication"?  What is "Relay Agent Information
security"?  Put another way, what is mandatory to implement?

Russ Housley:

Discuss:
   Section 7 says:
   >
   > DHCP servers SHOULD prevent exposure of location information
   > (particularly the mapping of hardware address to IP address lease,
   > which can be an invasion of broadband subscriber privacy) by
   > employing some form of relay agent authentication between the
   > DHCPLEASEQUERY client and the DHCP server.
   >
   There needs to be more discussion of the authentication requirements.
   I would prefer the specification to name a mandatory-to-implement
   mechanism, but that may be asking too much.

   Section 7 also says:
   >
   > Clients of the DHCPLEASEQUERY message SHOULD ensure that their data
   > path to the DHCP server is secure.
   >
   What security services are needed?  Integrity, authentication, access
   control, replay protection confidentiality?  The hint about Relay Agent
   Information security, with no reference, is not sufficient.



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