RE: [dhcwg] Server Unicast Option in DCHPv6

"Bernie Volz" <volz@cisco.com> Sat, 04 September 2004 20:38 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 QAA06069; Sat, 4 Sep 2004 16:38:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3hGb-0006fx-Bs; Sat, 04 Sep 2004 16:36:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3hCr-0006L9-2Q for dhcwg@megatron.ietf.org; Sat, 04 Sep 2004 16:32:17 -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 QAA05800 for <dhcwg@ietf.org>; Sat, 4 Sep 2004 16:32:14 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3hFj-00085W-TW for dhcwg@ietf.org; Sat, 04 Sep 2004 16:35:16 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-5.cisco.com with ESMTP; 04 Sep 2004 13:31:49 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i84KVg8J000480; Sat, 4 Sep 2004 13:31:43 -0700 (PDT)
Received: from volzw2k (che-vpn-cluster-2-171.cisco.com [10.86.242.171]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ALI20371; Sat, 4 Sep 2004 16:31:41 -0400 (EDT)
From: "Bernie Volz" <volz@cisco.com>
To: "'Suman'" <suman@samsung.com>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] Server Unicast Option in DCHPv6
Date: Sat, 4 Sep 2004 16:31:43 -0400
Organization: Cisco
Message-ID: <000c01c492be$31311bc0$6501a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-Reply-To: <000601c49175$b2e5eaf0$8d476c6b@sisodomain.com>
x-mimeole: Produced By Microsoft MimeOLE V5.50.4939.300
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable
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: quoted-printable

The unicast option is only server to client; not client to server. So, no
the client does not send the option.

There is no hard requirement for a client to use unicast. From the option
description in RFC 3315:

   The server specifies the IPv6 address to which the client is to send
   unicast messages in the server-address field.  When a client receives
   this option, where permissible and appropriate, the client sends
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   messages directly to the server using the IPv6 address specified in
   the server-address field of the option.

   When the server sends a Unicast option to the client, some messages
   from the client will not be relayed by Relay Agents, and will not
   include Relay Agent options from the Relay Agents.  Therefore, a
   server should only send a Unicast option to a client when Relay
   Agents are not sending Relay Agent options.  A DHCP server rejects
   any messages sent inappropriately using unicast to ensure that
   messages are relayed by Relay Agents when Relay Agent options are in
   use.

   Details about when the client may send messages to the server using
   unicast are in section 18.



-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Suman
Sent: Friday, September 03, 2004 1:20 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Server Unicast Option in DCHPv6


Hi,
 
      I need some clarification on the Server Unicast Option, in DHCPv6, RFC
3315. 
 
In particular, when the client receives a Server Unicast option in an
advertise message and it has to send a request message to that server, it
unicasts the message to the server. That apart, should the client include
Server Unicast Option in the Request message that it sends? 
 
Also, all the subsequent transaction between the client and that server has
to be unicast, if I have got it right! Does the client need to include this
option in all the subsequent message exchanges, Request message in
particular?
 
Any insight into this would be greatly appreciated. 
 
Regards,
Suman.
 
 


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