RE : [dhcwg] RFC 3315: DHCPv6 server unicast address

"Jean-Michel COMBES" <jeanmichel.combes@francetelecom.com> Mon, 09 May 2005 16:18 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVAxJ-0003Ax-Qd; Mon, 09 May 2005 12:18:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVAxH-0003As-GW for dhcwg@megatron.ietf.org; Mon, 09 May 2005 12:18:03 -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 MAA01783 for <dhcwg@ietf.org>; Mon, 9 May 2005 12:18:01 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVBCP-00077N-FA for dhcwg@ietf.org; Mon, 09 May 2005 12:33:42 -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 18:18:15 +0200
Received: from PXPELLAFOL ([10.193.161.117]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Mon, 9 May 2005 18:17:23 +0200
From: Jean-Michel COMBES <jeanmichel.combes@francetelecom.com>
To: 'Ted Lemon' <Ted.Lemon@nominum.com>
Subject: RE : [dhcwg] RFC 3315: DHCPv6 server unicast address
Date: Mon, 09 May 2005 18:17:23 +0200
Organization: France Telecom R&D
Message-ID: <02f101c554b2$a7e82d10$75a1c10a@rd.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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
In-Reply-To: <332FAC05-F6FA-48AF-A4AE-F0436D6FFB41@nominum.com>
X-OriginalArrivalTime: 09 May 2005 16:17:54.0821 (UTC) FILETIME=[A7EDAB50:01C554B2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
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

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com] 
> Sent: Monday, May 09, 2005 5:59 PM
> To: COMBES Jean-Michel RD-MAPS
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] RFC 3315: DHCPv6 server unicast address
> 
> 
> On May 9, 2005, at 8:29 AM, Jean-Michel COMBES wrote:
> > If for example, we assume that the DHCPv6 Client has got 
> the DHCPv6  
> > Server's
> >
> 
> We don't assume that!   The DHCP client gets the DHCPv6 server's IP  
> address by exchanging packets with it.   There's no provision in the  
> protocol for a way to look the DHCPv6 server's IP address up 
> in the DNS.
> 

Is it a MUST? If so, where is such a reference?

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