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

Ole Troan <ot@cisco.com> Wed, 08 May 2002 15:49 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 LAA13974 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 11:49:25 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA08461 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 11:49:31 -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 LAA08322; Wed, 8 May 2002 11:46:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08302 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 11:46:49 -0400 (EDT)
Received: from cisco.com (mrwint.cisco.com [144.254.98.48]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13774 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:46:41 -0400 (EDT)
Received: (from otroan@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id QAA11998; Wed, 8 May 2002 16:46:17 +0100 (BST)
X-Authentication-Warning: mrwint.cisco.com: otroan set sender to ot@cisco.com using -f
To: Thomas Narten <narten@us.ibm.com>
Cc: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] dhcpv6-24: use of anycast
References: <200205081531.g48FVCC19526@rotala.raleigh.ibm.com>
From: Ole Troan <ot@cisco.com>
Date: Wed, 08 May 2002 16:46:17 +0100
In-Reply-To: <200205081531.g48FVCC19526@rotala.raleigh.ibm.com> (Thomas Narten's message of "Wed, 08 May 2002 11:31:12 -0400")
Message-ID: <7t5d6w6wsl2.fsf@mrwint.cisco.com>
Lines: 26
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/20.7 (sparc-sun-solaris2.8)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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?

ATM, Frame Relay RFC2491), ISDN/PSTN, MPLS, 6to4, ISATAP.  if routers
use DHCP (e.g Prefix Delegation) then support is needed for the first
set of media. hosts connecting through an ISATAP cloud could very well
need DHCP I should think.

cheers,
Ole

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