IETF Logo Mail Archive

Re: [dhcwg] Renumbering DNS with stateless DHCPv6 - bug?

Vijayabhaskar A K <vijayak@india.hp.com> Thu, 13 November 2003 22:35 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25086 for <dhcwg-archive@odin.ietf.org>; Thu, 13 Nov 2003 17:35:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ3O-0004Dp-Hw for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 17:35:08 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADMZ65q016223 for dhcwg-archive@odin.ietf.org; Thu, 13 Nov 2003 17:35:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ3O-0004Da-Df for dhcwg-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 17:35:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25019 for <dhcwg-web-archive@ietf.org>; Thu, 13 Nov 2003 17:34:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKQ3L-0006sk-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 17:35:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKQ3L-0006sd-00 for dhcwg-web-archive@ietf.org; Thu, 13 Nov 2003 17:35:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ3J-0004AX-Jf; Thu, 13 Nov 2003 17:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKQ2p-00049Q-9x for dhcwg@optimus.ietf.org; Thu, 13 Nov 2003 17:34:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24992 for <dhcwg@ietf.org>; Thu, 13 Nov 2003 17:34:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKQ2m-0006rt-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 17:34:28 -0500
Received: from palrel10.hp.com ([156.153.255.245]) by ietf-mx with esmtp (Exim 4.12) id 1AKQ2m-0006rp-00 for dhcwg@ietf.org; Thu, 13 Nov 2003 17:34:28 -0500
Received: from iconsrv5.india.hp.com (iconsrv5.india.hp.com [15.42.229.13]) by palrel10.hp.com (Postfix) with ESMTP id 2199D1C010AF; Thu, 13 Nov 2003 14:34:25 -0800 (PST)
Received: from india.hp.com (nt23056.india.hp.com [15.42.230.56]) by iconsrv5.india.hp.com (8.9.3 (PHNE_29774)/8.9.3 SMKit7.02) with ESMTP id EAA28150; Fri, 14 Nov 2003 04:03:08 +0530 (IST)
Message-ID: <3FB406E8.6020200@india.hp.com>
Date: Fri, 14 Nov 2003 04:04:16 +0530
From: Vijayabhaskar A K <vijayak@india.hp.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031014 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stig Venaas <Stig.Venaas@uninett.no>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, dnsop@cafax.se, dhcwg@ietf.org
Subject: Re: [dhcwg] Renumbering DNS with stateless DHCPv6 - bug?
References: <20031113191145.GS3473@login.ecs.soton.ac.uk> <3FB3E69E.4060705@india.hp.com> <20031113205538.GA20348@sverresborg.uninett.no> <3FB3F6C0.2050205@india.hp.com> <20031113214047.GA20420@sverresborg.uninett.no>
In-Reply-To: <20031113214047.GA20420@sverresborg.uninett.no>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Stig Venaas wrote:

>On Fri, Nov 14, 2003 at 02:55:20AM +0530, Vijayabhaskar A K wrote:
>  
>
>>An intruder relay can trigger the clients to initiate the renewal of 
>>config info by sending the reconfigure message, leading to flooding of 
>>dhcp packets from all the dhcpv6 client nodes and DoS attack on the 
>>server... Thats the reason why Reconfigure message needs to be 
>>authenticated...
>>    
>>
>
>Ah ok, I see. One could possibly do authentication for multicasted
>messages too, but the current authentication method wouldn't work
>I think.
>
>Stig
>
>
>  
>
There is some work going on multicast security,
http://www.ietf.org/html.charters/msec-charter.html
It could be used here...

Vijay

-- 
__________________________________________________________
Vijayabhaskar A K            Phone : +91-80-2053085
Hewlett Packard              Mobile: +91-9845241382
29 Cunningham Road           Telnet: 847-3085
Bangalore 52                 Email : vijayak@india.hp.com

Until you have the courage to lose sight of the shore,
you will not know the terror of being forever lost at sea.
 __________________________________________________________




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

v2.23.0 | Report a Bug | By Email