[dhcwg] Re: DHCPv6 Relay Queries.
"O.L.N.Rao" <olnrao@samsung.com> Wed, 25 August 2004 13:06 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 JAA12176; Wed, 25 Aug 2004 09:06:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzx2P-0005eR-KJ; Wed, 25 Aug 2004 08:38:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BztaA-0008NP-2T; Wed, 25 Aug 2004 04:56:38 -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 EAA25761; Wed, 25 Aug 2004 04:56:31 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bztal-0005Kj-61; Wed, 25 Aug 2004 04:57:16 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I2Z00H85VGG2S@mailout2.samsung.com>; Wed, 25 Aug 2004 17:55:28 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I2Z00FISVFG4M@mailout2.samsung.com>; Wed, 25 Aug 2004 17:54:53 +0900 (KST)
Received: from OLNRAO ([107.108.71.122]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPSA id <0I2Z006FWVFESO@mmp1.samsung.com>; Wed, 25 Aug 2004 17:54:52 +0900 (KST)
Date: Wed, 25 Aug 2004 14:24:51 +0530
From: "O.L.N.Rao" <olnrao@samsung.com>
To: surya_pc@huawei.com
Message-id: <04d601c48a81$304ea050$7a476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <008f01c48a71$3b09c4d0$5c04120a@suryapc>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 25 Aug 2004 08:37:59 -0400
Cc: dhcwg@ietf.org, ipv6@ietf.org
Subject: [dhcwg] Re: DHCPv6 Relay Queries.
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 Surya,
See my comments inline :)
[PS: This is related to DHCPv6 and would be better to discuss in
dhcwg@ietf.org]
Regards,
O. L. N. Rao & Suman V N
----- Original Message -----
From: "Surya" <surya_pc@huawei.com>
To: <ipv6@ietf.org>
Sent: Wednesday, August 25, 2004 12:30 PM
Subject: DHCPv6 Relay Queries.
> Hi,
>
> Could you please clarify on the below mentioned queries on DHCPv6 Relay
>
> When we use the following topology
>
> "Client ----- Relay1 -------Relay 2 ---------Server"
>
> 1) Does all the DHCP messages from Client goes to Relay even after
knowing
> the server?
==> Yes, they always go to/through Relay. However, if the DHCPv6 client
supports
"Server Unicast Option", then DHCPv6 Server will send its unicast address to
DHCPv6 Client.
DHCPv6 Client will then use unicast communication with server. Here, I
would like to mention
one more point. Even though, the messages are sent to
DHCPv6_All_Agents_and_Servers the
Server Identifier option specifies the DHCPv6 server to which the message
was intended.
>
> 2. Relay forms Relay forward message when it sends to another relay, will
it
> again construct a relay forward message?
===> Yes. Because, unless the total path is known, the reply can not come
back in the same path.
The server constructs the Relay-Reply message with the full path in Relay
Message Options.
>
> 3. DHCP message can be can be stored in Options field of the Relay
forward.
> When it reaches the last relay on the network which is connected to
Server,
> how the processing should be?
>
===> The Relay-Forward messages reaches Server as it is.
>
> Thanks
> Surya.
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Re: DHCPv6 Relay Queries. O.L.N.Rao