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

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Thu, 09 May 2002 13:13 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 JAA19409 for <dhcwg-archive@odin.ietf.org>; Thu, 9 May 2002 09:13:10 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA24788 for dhcwg-archive@odin.ietf.org; Thu, 9 May 2002 09:13:18 -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 JAA24566; Thu, 9 May 2002 09:08:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24497 for <dhcwg@optimus.ietf.org>; Thu, 9 May 2002 09:08:22 -0400 (EDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19122 for <dhcwg@ietf.org>; Thu, 9 May 2002 09:08:13 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6att.ericy.com [138.85.224.157]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id g49D7qi23418 for <dhcwg@ietf.org>; Thu, 9 May 2002 08:07:52 -0500 (CDT)
Received: from eamrcnt747.exu.ericsson.se (eamrcnt747.exu.ericsson.se [138.85.133.37]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id g49D7p508412 for <dhcwg@ietf.org>; Thu, 9 May 2002 08:07:51 -0500 (CDT)
Received: FROM eamrcnt760.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Thu May 09 08:07:50 2002 -0500
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <KR4LJD2M>; Thu, 9 May 2002 08:07:50 -0500
Message-ID: <66F66129A77AD411B76200508B65AC69B4D3D6@EAMBUNT705>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "'Thomas Narten'" <narten@us.ibm.com>, Ole Troan <ot@cisco.com>
Cc: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] dhcpv6-24: use of anycast
Date: Thu, 9 May 2002 08:07:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1F75A.8537ABA0"
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:

>Perhaps one could take the approach that DHC uses link-local multicast
>by default, unless the specific link-layer over FOO document says use
>anycast. This is cleaner than saying "use anycast over NBMA" because
>its clearly specified on a case-by-case basis.

The only issue with this is that DHCP usually runs as an application and is therefore only able to access that information which the lower layers (via APIs) make available.

Determining whether multicast is supported or not is pretty standard from the socket API. However, determining that a particular interface is a specific media type may be difficult.

Therefore, there is some value in providing a clear direction here that is also relatively easy to implement.

If all interface types provide multicast (either inherently or via some type of emulation), there is little need to ever use the anycast address and so what harm is there in specifying it.

What we probably should say is that the client MUST use the multicast address if the interface on which it is sending the message supports multicast. Otherwise, it may use the anycast address.

- Bernie

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com]
Sent: Thursday, May 09, 2002 8:04 AM
To: Ole Troan
Cc: Ralph Droms; dhcwg@ietf.org
Subject: Re: [dhcwg] dhcpv6-24: use of anycast 


Ole Troan <ot@cisco.com> writes:

> >> 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,

See RFC 2491 and 2492. Multicast is supported. At least in the case of
SVC/PVC. Not clear that anyone uses anything else (i.e., pure NBMA
cloud).

> Frame Relay RFC2491)

Ditto.

> ISDN/PSTN

Always modeled as a p-2-p link, so mcast is trivially defined.

> MPLS

MPLS is a funny one. I don't think it is typically viewed as an NBMA
cloud. Also, MPLS is used within the core, by routers, and NOT at the
edges, so I'd think DHC is not really applicable in general here.

> 6to4

Not clear that this is applicable. The router defining 6to4 is an IPv4
box on the interface and uses DHCPv4. It does provide IPv6 support,
but this is explicitely in an environment where IPv6 is not supported
by the upstream. So DHCPv6 doesn't seem applicable; it it was, why
would one even be using 6to4?

> ISATAP.

Not clear this is applicable.

> 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.

This is not at all clear to me.

99% of the applicability of DHCv6 will be traditional media, i.e.,
Ethernets.

Another thought. The IPv6 over foo documents provide specifics for how
to run IPv6 over that media. In some cases, those documents can
override defaults for running IPv6 over a media in general. For
example, one can change the number of times one retransmits in
DAD. The default is 1, but a specific document can make that 0 or 2,
etc.

Perhaps one could take the approach that DHC uses link-local multicast
by default, unless the specific link-layer over FOO document says use
anycast. This is cleaner than saying "use anycast over NBMA" because
its clearly specified on a case-by-case basis.

Thomas

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