Hi Shree,
On 10-09-09 06:46 AM, JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK) wrote:
Suresh,
5. Creating an alternative to DHCPv6 ?
One SLAAC is defined to do functionality similar to DHCP (including per
host prefixes/options)
how long before options are added so SLAAC becomes an alternative to
DHCPv6 ?
The goal is not to come up with an alternative to DHCPv6. The goal is to
provide backward compatibility for IPv6 hosts that are SLAAC only.
[Shree] Understand the goal,
but with no way to distinguish between "SLAAC only" V/s "DHCP capable hosts"
the natural choice would be to opt for lowest common denominator i.e. "SLAAC only" mechanism.
Not necessarily. In most deployment scenarios we know the "host" is a
routed residential gateway and the SDOs usually specify what is required
on them. e.g. in BBF, the routed RG will certainly have a DHCPv6 client
on it and hence we can assume that it will be present. So we narrow down
the uncertainty to a few scenarios that are not extremely common.
Thanks
Suresh
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
