Re: IETF80 questions regarding "On demand IPv4 address provisioning in Dual-Stack PPP deployment" - Topic for WG?

On Fri, Jun 17, 2011 at 10:04 AM, Dave Thaler <[email protected]> wrote:
> Mark Townsley wrote:
> [...]
>> Applications may not be all that forgiving to IPv4 coming and going eith=
er, e.g.,
>> I have a popular mail client that has recently taken to crashing when I =
switch
>> from wired to wireless and get a different IP address in the process. So=
me of
>> the IM connections I keep up recover quickly to IP changes, others do no=
t. The
>> IETF has a whole WG (DNA) dedicated to this tricky behavior of an IP add=
ress
>> coming and going - it's not always easy, in particular when the link-lay=
er is not
>> giving your IP stack any up/down notification, which I believe by defini=
tion is
>> what your proposal requires from the very start.
> [...]
>
> I'll second the above. =A0 This is very problematic for some applications.
> (Other solutions like DSTM that have on-demand IP addresses have this sam=
e issue.)
>
> So any network that deploys such a solution in anything other than
> a tightly controlled environment where directly connected nodes are restr=
icted
> to a specific set of pre-tested applications, will likely result in many =
support calls.
>

Is this really different from the dial-on-demand routing that has
existed for years and still exist as  common backup connectivity
technique?

I assume that this would be implemented on an Home Gateway which
provides consistent addressing to IPv4 hosts within the home, and
dial-on-demand type mechanism request the IPv4 address to the home
gateway to do NAT44 in the event of an IPv4 stream arrives.


Cameron