[dhcwg] Reserved anycast address for DHCPv6
Ralph Droms <rdroms@cisco.com> Fri, 05 April 2002 19:41 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 OAA15414 for <dhcwg-archive@odin.ietf.org>; Fri, 5 Apr 2002 14:41:58 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA24733 for dhcwg-archive@odin.ietf.org; Fri, 5 Apr 2002 14:42:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA24642; Fri, 5 Apr 2002 14:40:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA24624 for <dhcwg@optimus.ietf.org>; Fri, 5 Apr 2002 14:40:31 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15313 for <dhcwg@ietf.org>; Fri, 5 Apr 2002 14:40:27 -0500 (EST)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-251.cisco.com [161.44.149.251]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA18583 for <dhcwg@ietf.org>; Fri, 5 Apr 2002 14:40:00 -0500 (EST)
Message-Id: <4.3.2.7.2.20020405143407.00b3cca8@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 05 Apr 2002 14:39:58 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Reserved anycast address for DHCPv6
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
<draft-ietf-ipv6-dns-discovery-04.txt> includes the definition of three
anycast addresses for use by DNS resolvers:
fec0:0:0:ffff::1
fec0:0:0:ffff::2
fec0:0:0:ffff::3
I had a request in Minneapolis that we consider defining an anycast address
for DHCPv6 that would allow the use of DHCPv6 on NBMA networks. Seems to
me like a reasonable suggestion.
One potential problem is that clients now have two addresses: the
All_DHCP_Agents multicast address and the new anycast address. Which
should the client choose to use?
BTW, the DNS Discovery draft includes the following:
Note to readers: the above addresses are tentative, but the ffff
is intended to be consistent with a simultaneous proposal to
reserve the ffff SLA for use with IANA-assigned addresses such as
these.
Does anyone on the list know anything about the proposal for reserving a
site-scoped SLA for anycast addresses?
- Ralph
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Reserved anycast address for DHCPv6 Ralph Droms
- RE: [dhcwg] Reserved anycast address for DHCPv6 Bernie Volz (EUD)
- RE: [dhcwg] Reserved anycast address for DHCPv6 Ralph Droms
- RE: [dhcwg] Reserved anycast address for DHCPv6 Bernie Volz (EUD)