[dhcwg] RFC 3315: DHCPv6 server unicast address
"Jean-Michel COMBES" <jeanmichel.combes@francetelecom.com> Mon, 09 May 2005 15:29 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVAC9-0001R9-AG; Mon, 09 May 2005 11:29:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVAC8-0001R4-AI for dhcwg@megatron.ietf.org; Mon, 09 May 2005 11:29:20 -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 LAA26425 for <dhcwg@ietf.org>; Mon, 9 May 2005 11:29:18 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVARF-00054N-JL for dhcwg@ietf.org; Mon, 09 May 2005 11:44:58 -0400
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 9 May 2005 17:29:35 +0200
Received: from PXPELLAFOL ([10.193.161.117]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Mon, 9 May 2005 17:29:16 +0200
From: Jean-Michel COMBES <jeanmichel.combes@francetelecom.com>
To: dhcwg@ietf.org
Date: Mon, 09 May 2005 17:29:16 +0200
Organization: France Telecom R&D
Message-ID: <02db01c554ab$dc86a6c0$75a1c10a@rd.francetelecom.fr>
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.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-OriginalArrivalTime: 09 May 2005 15:29:16.0741 (UTC) FILETIME=[DC9DFF50:01C554AB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Subject: [dhcwg] RFC 3315: DHCPv6 server unicast address
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
Hi, The RFC 3315 says in: Section 18.1, p39 "If the client has a source address of sufficient scope that can be used by the server as a return address, and the client has received a Server Unicast option (section 22.12) from the server, the client SHOULD unicast any Request, Renew, Release and Decline messages to the server." And Annex A, p98 The Server Unicast is only allowed in the REPLY Message So, my question is: If for example, we assume that the DHCPv6 Client has got the DHCPv6 Server's unicast address from a DNS, why the DHCPv6 Client will not be able to use the DHCPv6 Server's unicast address until to receive the Unicast Option (bad case, 4 messages before to be allowed to use it: SOLICIT->ADVERTISE->REQUEST->REPLY)? Thanks for your help. Regards. JMC. France Telecom - R&D Division - MAPS/NSS Jean-Michel COMBES, Internet/Intranet Security E-Mail: jeanmichel.combes@francetelecom.com Phone: +33 (0)1 45 29 45 94 Fax: +33 (0)1 45 29 65 19 Mobile: +33 (0)6 07 29 30 16 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] RFC 3315: DHCPv6 server unicast address Jean-Michel COMBES
- Re: [dhcwg] RFC 3315: DHCPv6 server unicast addre… Ted Lemon
- RE : [dhcwg] RFC 3315: DHCPv6 server unicast addr… Jean-Michel COMBES