Re: [Autoconf] draft-boot-autoconf-support4hosts

Hello Teco,

Comments below:

>                     Packet forwarding between hosts is always lead
>    via one ore more MANET routers, unless link-local addresses are used
>    and direct reachability between the hosts exists.

I did not understand this sentence.

>                                                    However, usage of
>    link-local addresses is not recommended, as non-link-local addresses
>    provide better support for session continuity in mobile environments.

I was surprised to read that the purpose for using non-link-local
addresses was for session continuity.  I think it is more along the
lines of "identity preservation and uniqueness".

> Charles E. Parkins

Thanks for the acknowledgement.  My last name has
an 'e' in it :-).

>                                                 Mobility
>    solutions are already available and can be used in the MANET
>    scenario.

This is true, but usually is considered in the context
of having a home agent in the Internet instead of in
the ad-hoc network.  Is this what you are proposing?

Regards,
Charlie P.

On 11/29/2010 1:30 PM, Teco Boot wrote:
> Feel free to comment on a draft I just submitted.
> http://www.ietf.org/id/draft-boot-autoconf-support4hosts-00.txt
> Teco.
>
>> Abstract:
>> This document describes how hosts using IPv6 Stateless Address
>> Autoconfiguration can be used in a MANET, without a need for any
>> change, neither in functioning of Neighbor Discovery nor in MANET
>> protocols.  In addition, legacy hosts nor other parts of the network
>> are faced any deviation on the IPv6 Addressing architecture.
>
> _______________________________________________
> Autoconf mailing list
> Autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/autoconf
>