Re: [dhcwg] identifier for key selection

Mayumi Yanagiya <yanagiya.mayumi@lab.ntt.co.jp> Fri, 09 July 2004 10:35 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 GAA16264; Fri, 9 Jul 2004 06:35:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BisFs-00050O-Db; Fri, 09 Jul 2004 06:05:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BirzS-0002AI-Ke for dhcwg@megatron.ietf.org; Fri, 09 Jul 2004 05:48:22 -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 FAA14131 for <dhcwg@ietf.org>; Fri, 9 Jul 2004 05:48:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BirzL-0007VJ-By for dhcwg@ietf.org; Fri, 09 Jul 2004 05:48:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiryM-0007DM-00 for dhcwg@ietf.org; Fri, 09 Jul 2004 05:47:15 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx with esmtp (Exim 4.12) id 1BirxR-0006ue-00 for dhcwg@ietf.org; Fri, 09 Jul 2004 05:46:17 -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 i699kBvX027510; Fri, 9 Jul 2004 18:46:11 +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 i699kAWf012906; Fri, 9 Jul 2004 18:46:10 +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 i699kAhI001001; Fri, 9 Jul 2004 18:46:10 +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 i699k9BL000998; Fri, 9 Jul 2004 18:46:09 +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 i699k9jr018549; Fri, 9 Jul 2004 18:46:09 +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 SAA04414; Fri, 9 Jul 2004 18:46:09 +0900 (JST)
Received: from lab.ntt.co.jp by ime.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id SAA14997; Fri, 9 Jul 2004 18:46:08 +0900 (JST)
Message-ID: <40EE6A11.8060803@lab.ntt.co.jp>
Date: Fri, 09 Jul 2004 18:49:05 +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: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] identifier for key selection
References: <002501c464f1$58cccfd0$6401a8c0@amer.cisco.com>
In-Reply-To: <002501c464f1$58cccfd0$6401a8c0@amer.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
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
Cc: dhcwg@ietf.org
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

Hi,

Thanks for your comments.
I try to make a problem statements draft.

Regards,
--Mayumi

>>I want to authenticate not hardware but user.
> 
> 
> Well, DHCP is the Dynamic Host Configuration Protocol. In many cases when
> DHCP starts there is no user (yet), or DHCP is being used by systems that
> are multi-user. But, I understand your desire to do this. And, there's
> always the ability to define additional authentication protocols.
> 
> - Bernie
> 
> 
>>-----Original Message-----
>>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
>>On Behalf Of Mayumi Yanagiya
>>Sent: Thursday, July 08, 2004 7:23 AM
>>To: Bernie Volz; dhcwg@ietf.org
>>Subject: Re: [dhcwg] identifier for key selection
>>
>>
>>Hello Bernie,
>>
>>Thank you for your comments.
>>
>>Bernie Volz wrote:
>>
>>
>>>Hi:
>>>
>>>Regarding the first question:
>>>
>>>As defined in RFC 3315:
>>>
>>>      DHCP realm                A name used to identify the DHCP
>>>                                administrative domain from 
>>
>>which a DHCP
>>
>>>                                authentication key was selected.
>>>
>>>So, both the realm and the client's DUID would be used to 
>>
>>obtain the 
>>
>>>key. If the received realm doesn't match the server's or one of the 
>>>server's, the server needn't bother looking for a key?
>>>
>>>Instead, it might send its realm to the client in an Advertise?
>>
>>I see.
>>
>>
>>>Regarding the second, where do you want to put this identifier? The 
>>>Client Identifier must be a DUID that follows one of the 
>>
>>formats given 
>>
>>>in the document. New formats could be defined. The Client 
>>
>>Identifier 
>>
>>>is supposed to represent the client (hardware), not the 
>>
>>user (though 
>>
>>>often there is only one user for each client). There's also the 
>>>possibility of defining new options to carry user, subscriber, etc 
>>>information similar to what has been done for DHCPv4 (see 
>>
>>the various 
>>
>>>Relay Agent suboptions).
>>
>>I want to authenticate not hardware but user.
>>Because, when we authenticate user, users are allowed to 
>>change hardware 
>>without reporting the change to administrator. I think that 
>>it is very 
>>convenience for user and administrator.So I'm looking for an 
>>identifier 
>>that I can use as user identifier.
>>
>>When I use suboption such as subscriber-ID specified in 
>>draft-ietf-dhc-subscriber-id-06.txt,can I use the suboption to select 
>>the client's key?
>>
>>
>>Thanks,
>>--Mayumi
>>
>>
>>
>>
>>_______________________________________________
>>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
> 

-- 

*++++++++++++++++++++++++++++++++++++++++++
NTT Network Service Systems Laboratories
Mayumi Yanagiya
tel: +81 422 59 6783   fax: +81 422 37 7688
E-mail: yanagiya.mayumi@lab.ntt.co.jp
+++++++++++++++++++++++++++++++++++++++++++*


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