IETF Logo Mail Archive

[dhcwg] Server Unicast Option in DCHPv6

Suman <suman@samsung.com> Fri, 03 September 2004 05:32 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 BAA12971; Fri, 3 Sep 2004 01:32:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C36bh-0006GW-1o; Fri, 03 Sep 2004 01:27:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C36Vr-0002Fc-Mr for dhcwg@megatron.ietf.org; Fri, 03 Sep 2004 01:21:29 -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 BAA12332 for <dhcwg@ietf.org>; Fri, 3 Sep 2004 01:21:26 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C36YN-0004yA-Fu for dhcwg@ietf.org; Fri, 03 Sep 2004 01:24:05 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I3G006LP9IPX0@mailout3.samsung.com> for dhcwg@ietf.org; Fri, 03 Sep 2004 14:20:49 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I3G004RC9I8VH@mailout3.samsung.com> for dhcwg@ietf.org; Fri, 03 Sep 2004 14:20:32 +0900 (KST)
Received: from SUMAN ([107.108.71.141]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0I3G0085U9I5V6@mmp1.samsung.com> for dhcwg@ietf.org; Fri, 03 Sep 2004 14:20:32 +0900 (KST)
Date: Fri, 03 Sep 2004 10:50:09 +0530
From: Suman <suman@samsung.com>
Subject: [dhcwg] Server Unicast Option in DCHPv6
To: dhcwg@ietf.org
Message-id: <000601c49175$b2e5eaf0$8d476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
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>
Content-Type: multipart/mixed; boundary="===============0902264325=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

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

v2.23.0 | Report a Bug | By Email