Re: [dhcwg] doubt in rfc 3046

Ted Lemon <mellon@nominum.com> Tue, 04 September 2001 13:23 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14644; Tue, 4 Sep 2001 09:23:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24230; Tue, 4 Sep 2001 09:20:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24210 for <dhcwg@ns.ietf.org>; Tue, 4 Sep 2001 09:20:40 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14378 for <dhcwg@ietf.org>; Tue, 4 Sep 2001 09:19:15 -0400 (EDT)
Received: from grosse.bisbee.fugue.com (dsl081-147-128.chi1.dsl.speakeasy.net [64.81.147.128]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id f84DEbf24790; Tue, 4 Sep 2001 06:14:37 -0700 (PDT)
Received: from grosse.bisbee.fugue.com (localhost [127.0.0.1]) by grosse.bisbee.fugue.com (8.11.3/8.6.11) with ESMTP id f84DKFH00427; Tue, 4 Sep 2001 09:20:15 -0400 (EDT)
Message-Id: <200109041320.f84DKFH00427@grosse.bisbee.fugue.com>
To: AJAY BANSAL <bansal@india.hp.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] doubt in rfc 3046
In-Reply-To: Message from AJAY BANSAL <bansal@india.hp.com> of "Tue, 04 Sep 2001 16:27:42 +0530." <3B94B3A5.59DAAC3B@india.hp.com>
Date: Tue, 04 Sep 2001 09:20:15 -0400
From: Ted Lemon <mellon@nominum.com>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

> In a client's dhcp request, which a DHCP server
> recieves, can both,
> the 'client id' option as well as the 'remote
> client id'
> (relay agent sub-option)  be present?

The DHCP client never sends a relay agent information option.   So if
you are implementing a client, the answer to your question is "no,
never."   If you are implementing a relay agent, it's "yes," but the
remote-id is intended to refer to a remote link, not to an individual
client.   The client-id and remote-id fields are completely
unrelated.

> If yes, then will there be any significance of
> client id field in such cases,
> since client is not a trustworthy component?

The client isn't trustworthy, but hopefully the relay agent is.   The
client id identifies the client, so you just have to trust that the
client is telling the truth.

> Is it must for the server to copy the client id
> back in its reply?

I don't think so, but you should refer to the RFC to be sure.

			       _MelloN_




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