[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Alain Durand <Alain.Durand@Sun.COM>
Cc: dnsop@cafax.se, rdroms@cisco.com
From: Mohsen Souissi <Mohsen.Souissi@nic.fr>
Date: Thu, 17 Jul 2003 10:01:15 +0200
Content-Disposition: inline
In-Reply-To: <155F1C85-B75E-11D7-9A7A-00039358A080@sun.com>; from Alain.Durand@Sun.COM on Wed, Jul 16, 2003 at 12:21:14AM -0700
Sender: owner-dnsop@cafax.se
User-Agent: Mutt/1.2.5.1i
Subject: Re: proposal for a compromise on DNS discovery

If this tradeoff proposal can help us move quickly to an operational
solution which maybe quickly implemented and shipped in OS's, I fully
support it.

My concern is that while having this endless religious debate (thanks
Tim for the word), people who want to deploy real and credible IPv6
networks still lack this critical feature (recursive name server
discovery).

Mohsen.

On 16 Jul, Alain Durand wrote:
| I have circulated this among several people yesterday and it may be time
| to bring this to the list.
| 
| Our community is basically divided in two camps,
| the "conservatives", coming from v4 where the operational practice
| is to use DHCP for DNS discovery and would like to operate the same way
| for v6, and the "liberals", coming from v6 where the autoconfiguration
| story is build on Neighbor Discovery and RA/RS, and who would like to
| expand on this.
| 
| As I explain in an earlier mail, the differences in the mode of 
| operation are:
| - DHCPv6 can also pass the address of the NTP server
| - RA/RS have the unsolicited multicast provision that helps save 
| bandwidth
|    when a large number of nodes are autoconfiguring at the same time.
| 
| The compromise solution I'd like to bring forward is to optionally 
| piggy back the
| unsolicited multicast mode to DHCPv6-lite.
| 
| More specifically, this would work the following way:
| 
| At boot time, the client wait a bit (random 0..MAX1 seconds) and listen
| to unsolicited DHCPv6 DNS recursive server advertisements sent to the
| link-local-all-node multicast address.
| If noting comes, it send a DHCPv6 request.
| The DHCPv6 server answer to the unicast address of the requester
| and, if configured to do so (this would be optional), send the same 
| thing to the
| link-local-all-node multicast address.
| Those multicast responses will be rate limited by the server,
| that is, if a second request come within MAX2 seconds,
| only the unicast answer will be sent.
| 
| I'm sure there would be many details to work out.
| 
| 	- Alain.
| 
| #----------------------------------------------------------------------
| # To unsubscribe, send a message to <dnsop-request@cafax.se>.
| 

-- 
Mohsen Souissi

***********************************************************************
* 			AFNIC -  http://www.afnic.fr/                 *
***************************************+*******************************
* 		  mailto:Mohsen.Souissi@nic.fr                        *
* Tél. : +33 1 39 30 83 40       |  Fax :    +33 1 39 30 83 01        *
*--------------------------------+------------------------------------*
* Immeuble International - 2, rue Stephenson - Montigny le Bretonneux *
* 78181 Saint Quentin en Yvelines Cedex                               *
***********************************************************************
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.

Home | Date list | Subject list