Re: [dhcwg] Address autoconfiguration

Ralph Droms <rdroms@cisco.com> Sat, 07 September 2002 00:12 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25249 for <dhcwg-archive@odin.ietf.org>; Fri, 6 Sep 2002 20:12:55 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g870EAW16204 for dhcwg-archive@odin.ietf.org; Fri, 6 Sep 2002 20:14:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g870EAX16201 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 6 Sep 2002 20:14:10 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25208 for <dhcwg-web-archive@ietf.org>; Fri, 6 Sep 2002 20:12:25 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g870B2X16101; Fri, 6 Sep 2002 20:11:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8709nX16063 for <dhcwg@optimus.ietf.org>; Fri, 6 Sep 2002 20:09:49 -0400
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25031 for <dhcwg@ietf.org>; Fri, 6 Sep 2002 20:08:04 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (rtp-vpn1-160.cisco.com [10.82.224.160]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id UAA01173; Fri, 6 Sep 2002 20:09:09 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020906110604.02209010@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 06 Sep 2002 11:08:27 -0400
To: Alexandru Petrescu <petrescu@crm.mot.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Address autoconfiguration
Cc: John Wells <wells@ieee.org>, dhcwg@ietf.org
In-Reply-To: <m3u1lcr9s8.fsf@test9.crm.mot.com>
References: <20020829180950.B8009@io.irean.vt.edu> <20020829112549.A5758@io.irean.vt.edu> <m3n0r563l0.fsf@test9.crm.mot.com> <20020829180950.B8009@io.irean.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

RFC2131 specifies interface disconnect/reconnect as the trigger for a DHCP 
update.  Nothing else.

Initiating changes in routes advertised by RIP is certainly possible, 
although I don't know of any DHCP servers that will do it today.

Are you talking about DHCP/IPv4 or DHCP/IPv6?

- Ralph

At 11:11 AM 8/30/2002 +0200, Alexandru Petrescu wrote:
>Hi John,
>
>John Wells <wells@ieee.org> writes:
> > Hi Alex,
> > That was precisely the idea I had.  It's a good one because it gives
> > optimal routing and sidesteps communicating the home address and care-of
> > address to mobile nodes.
>
>We can discuss about this, but this is only half DHC.  It gives
>optimal routing but only within that routing domain.  No need of HoA
>and CoA but only if staying in that domain.
>
> > Can any DHCP servers do this now?
>
>I don't know of any DHCP implementation that interacts with routing
>daemons.  But enhanching a DHCPv6 implementation to send UDP messages
>to routing daemons, a proof-of-concept like, must not be very
>difficult.
>
>RIP needs some modifications to act well for this.  Again, off-topic,
>but links torn down information propagate badly.
>
>Alex
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg

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