Re: [dhcwg] additional option for dhcpv6

Ted Lemon <mellon@nominum.com> Fri, 18 January 2002 21:49 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 QAA28462 for <dhcwg-archive@odin.ietf.org>; Fri, 18 Jan 2002 16:49:27 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA06191 for dhcwg-archive@odin.ietf.org; Fri, 18 Jan 2002 16:49:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06088; Fri, 18 Jan 2002 16:43:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06066 for <dhcwg@ns.ietf.org>; Fri, 18 Jan 2002 16:43:40 -0500 (EST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28255 for <dhcwg@ietf.org>; Fri, 18 Jan 2002 16:43:37 -0500 (EST)
Received: from green.bisbee.fugue.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g0ILcPS12435; Fri, 18 Jan 2002 13:38:26 -0800 (PST)
Received: from dechen (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g0ILf9h14087; Fri, 18 Jan 2002 15:41:09 -0600 (CST)
Date: Fri, 18 Jan 2002 15:41:09 -0600
Subject: Re: [dhcwg] additional option for dhcpv6
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v480)
Cc: dhcwg@ietf.org
To: Vijay Bhaskar A K <vijayak@india.hp.com>
From: Ted Lemon <mellon@nominum.com>
In-Reply-To: <200201182052.CAA16946@dce.india.hp.com>
Message-Id: <159A20DC-0C5C-11D6-BEE9-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

I don't think we need the subnet selection option anymore.   The DHCPv6 
server sends relay-reply messages to the IP source address from which it 
received the relay-forward message, so the relay-provided prefix doesn't 
have to even be a valid IP address, much less one of the relay agent's IP 
addresses.   It just has to represent a valid prefix on the link to which 
the client is attached, which is what the subnet selection option is.


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