Hi Satya and icmpv6-pd draft co-authors,

Rao Satyanarayana-W60007 wrote:
We believe that there is a need for an alternate way of doing PD simply because the DHCP PD is not intrinsic to the stack and makes it
 unusable sometimes.  ICMPv6 is intrinsic

I understand there may be a need for ICMPv6-PD, but there's also a need
to motivate it better than just that.

Why do you need PD in first place?  (regardless of DHCP or ICMP based).
 Is it for a DSL-like deployment for users in their SOHO or their house
to get an IPv6 prefix and distribute to the other PCs in house?

Is it for a mobile phone to connect to a cellular-like wireless
provider?  There wouldn't be a need for a prefix in that case.

Is it for a netlmm-like deployment where prefix-per-mobile seems to be
the guiding line?  In that deployment there's no need to assign an
entire prefix to the mobile, just the address has to be derived from a
specific prefix.  I.e. a netlmm mobile wouldn't need to propagate
further sub-prefixes.

Is it for a mobile phone acting as a mobile router (NEMOv6) and needing
to offer addresses to other hosts in its moving network?

Please explain why do you need PD in first place (regardless of DHCP or
PD).  This is stuff that has already been discussed in all the above
contexts.  What is _your_ context?

( by intrinsic, I mean that is always available in the ipv6 stack implementations)

This makes little sense to a wide various audience.  There are available
IPv6 stack implementations that do today DHCPv6 and PD.  They are more
available than others (depending where from you look at it).

Some Mobile Devices have built-in IPv6 ICMPv6 stacks that are hardly
modifiable, for which it is much much easier to modify DHCPv6 to PD.

Please describe _your_ context and acknowledge where DHCPv6-PD _could_ work.

Alex


--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to