IETF Logo Mail Archive

Re: [dhcwg] dhcpv6-24: use of anycast

Thomas Narten <narten@us.ibm.com> Wed, 08 May 2002 15:35 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13126 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 11:35:59 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA07255 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 11:36:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06567; Wed, 8 May 2002 11:30:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06542 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 11:30:54 -0400 (EDT)
Received: from e21.nc.us.ibm.com (e21.nc.us.ibm.com [32.97.136.227]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12697 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:30:47 -0400 (EDT)
Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.us.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.12.2/8.12.2) with ESMTP id g48FUn64012920; Wed, 8 May 2002 11:30:49 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.9.21]) by southrelay02.raleigh.ibm.com (8.11.1m3/NCO/VER6.1) with ESMTP id g48FUmQ143996; Wed, 8 May 2002 11:30:48 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g48FVCC19526; Wed, 8 May 2002 11:31:12 -0400
Message-Id: <200205081531.g48FVCC19526@rotala.raleigh.ibm.com>
To: Ralph Droms <rdroms@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] dhcpv6-24: use of anycast
In-Reply-To: Message from "Wed, 08 May 2002 11:07:35 EDT." <4.3.2.7.2.20020508110115.031eaab0@funnel.cisco.com>
Date: Wed, 08 May 2002 11:31:12 -0400
From: Thomas Narten <narten@us.ibm.com>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

> Thomas - the use of anycast is to allow the use of DHCP on links
> that do not support multicast.  The intention is to use anycast just
> across the link to which the client is attached; a relay agent
> forward messages across the rest of the path to the server.

OK. It was not clear to me that anycast was restricted to the first
hop.

But... If a link doesn't support IPv6 multicast, how will it support
Neighbor Discovery? I suspect there are only a few links that might
have this property. Do we understand what those link types are and
whether its important that DHC run over them?

> If all IPv6 links support multicast, then we don't need the anycast address
> for DHCP.

This would be my assumption. Do folks have examples of link types they
are concerned about?

Thomas

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

v2.23.0 | Report a Bug | By Email