IETF Logo Mail Archive

Re: [dhcwg] questions on RFC 3046 and RFC 3527

Ted Lemon <mellon@nominum.com> Wed, 18 August 2004 23:54 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 TAA01453; Wed, 18 Aug 2004 19:54:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxa9y-0003l5-Rt; Wed, 18 Aug 2004 19:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxa86-0003Nf-Rl for dhcwg@megatron.ietf.org; Wed, 18 Aug 2004 19:46:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00859 for <dhcwg@ietf.org>; Wed, 18 Aug 2004 19:46:05 -0400 (EDT)
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxaEP-0005lc-EA for dhcwg@ietf.org; Wed, 18 Aug 2004 19:52:38 -0400
Received: from [10.0.2.3] (neubayern.net [66.93.162.100]) by toccata.fugue.com (Postfix) with ESMTP id 71F651B22E8; Wed, 18 Aug 2004 18:42:41 -0500 (CDT)
In-Reply-To: <591B780D9676844E8A704B5B013FFE92025D7742@zrc2hxm1.corp.nortel.com>
References: <591B780D9676844E8A704B5B013FFE92025D7742@zrc2hxm1.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <C1D85480-F170-11D8-A31C-000A95D9C74C@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@nominum.com>
Subject: Re: [dhcwg] questions on RFC 3046 and RFC 3527
Date: Wed, 18 Aug 2004 16:45:59 -0700
To: Kuntal Chowdhury <chowdury@nortelnetworks.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, "Kostur, Andre" <akostur@incognito.com>
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

On Aug 18, 2004, at 4:12 PM, Kuntal Chowdhury wrote:
> It is true that RemoteID is not necessarily an IP address, but it MAY 
> be an
> IP address. The question is, if the RemoteID is an IP address, is the 
> use of
> RFC 3527 redundant or there are some other reason to include the Link
> selection sub-option?

The DHCP server will use the link selection suboption to select the 
link on which to configure the client.   It will not use the remote ID 
option for this purpose.   If you can't think of a reason to send the 
link selection suboption, do not send it.   It is intended for a 
specific purpose, and is not something that every relay agent should 
send in all circumstances.


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

v2.23.0 | Report a Bug | By Email