IETF Logo Mail Archive

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

Thomas Narten <narten@us.ibm.com> Wed, 15 May 2002 17:04 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 NAA13458 for <dhcwg-archive@odin.ietf.org>; Wed, 15 May 2002 13:04:15 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA13131 for dhcwg-archive@odin.ietf.org; Wed, 15 May 2002 13:04:29 -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 MAA11910; Wed, 15 May 2002 12:53: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 MAA11882 for <dhcwg@ns.ietf.org>; Wed, 15 May 2002 12:53:55 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (cichlid.adsl.duke.edu [152.16.64.203]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13069 for <dhcwg@ietf.org>; Wed, 15 May 2002 12:53:36 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id g4FGqN902056; Wed, 15 May 2002 12:52:23 -0400
Message-Id: <200205151652.g4FGqN902056@cichlid.adsl.duke.edu>
To: Ralph Droms <rdroms@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] dhcpv6-24: use of anycast
In-Reply-To: Message from Ralph Droms <rdroms@cisco.com> of "Wed, 08 May 2002 11:07:35 EDT." <4.3.2.7.2.20020508110115.031eaab0@funnel.cisco.com>
Date: Wed, 15 May 2002 12:52:22 -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.

I've asked some more IPv6 people about whether they believe there are
(or will ever be) links that support IPv6, but not IPv6 multicast.

No one has argued that such links will exists or should be allowed to
exist.

Based on the above, I would like to request that all the anycast text
be removed from the document. It simply does not seem to be needed to
solve an actual problem.

Thomas

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

v2.23.0 | Report a Bug | By Email