[dhcwg] identifier for key selection

Mayumi Yanagiya <yanagiya.mayumi@lab.ntt.co.jp> Tue, 06 July 2004 13:58 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 JAA15437; Tue, 6 Jul 2004 09:58:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhpg2-0007tN-BJ; Tue, 06 Jul 2004 09:08:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BhpCd-0003Jz-TG for dhcwg@megatron.ietf.org; Tue, 06 Jul 2004 08:37:39 -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 IAA10574 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 08:37:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BhpCY-0006FI-3z for dhcwg@ietf.org; Tue, 06 Jul 2004 08:37:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BhpBd-0005un-00 for dhcwg@ietf.org; Tue, 06 Jul 2004 08:36:37 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx with esmtp (Exim 4.12) id 1BhpB3-0005Zp-00 for dhcwg@ietf.org; Tue, 06 Jul 2004 08:36:01 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i66CZxhf026753 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:59 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i66CZwUh016977 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:58 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i66CZwWS015658 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:58 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i66CZvi8015653 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:57 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i66CZvd8006279 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:57 +0900 (JST)
Received: from ime.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id VAA20256 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:56 +0900 (JST)
Received: from lab.ntt.co.jp by ime.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id VAA28548 for <dhcwg@ietf.org>; Tue, 6 Jul 2004 21:35:56 +0900 (JST)
Message-ID: <40EA9D5B.1060308@lab.ntt.co.jp>
Date: Tue, 06 Jul 2004 21:38:51 +0900
From: Mayumi Yanagiya <yanagiya.mayumi@lab.ntt.co.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] identifier for key selection
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
Content-Transfer-Encoding: 7bit

Hello,

I have some question about DHCP authentication.

1. Which identifier does DHCP server use to select a key for client?
  In 21.4.5, it is specified that the server selects a key for client,
  based on the "client’s DUID" and key selection policies.
  But in 21.4.1, it seems that the "DHCP realm" is used to identify
  authentication key.
  Which identifier does the server use?

2. Can we use user identifier, such as NAI, as DUID?
   In section 9, it is specified that DHCP servers use DUID to
   identify “clients”.
   Does the “clients” mean only hardware such as NIC?

Regards,
-Mayumi





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