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

"Charles E. Perkins" <charles.perkins@earthlink.net> Sat, 04 December 2010 00:08 UTC

Return-Path: <charles.perkins@earthlink.net>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09A7C3A69E2 for <autoconf@core3.amsl.com>; Fri, 3 Dec 2010 16:08:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cozv5Stmx5cw for <autoconf@core3.amsl.com>; Fri, 3 Dec 2010 16:08:25 -0800 (PST)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by core3.amsl.com (Postfix) with ESMTP id 0B8113A69DF for <autoconf@ietf.org>; Fri, 3 Dec 2010 16:08:25 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ZBuMj7I57nZ2evQt5tmp0iaXPotdTz/Urzbq7LvdBhtcZVt5UlMmL+QThBnzWa+a; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [138.111.58.2] (helo=[172.17.96.25]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1POfh8-0002dw-T3; Fri, 03 Dec 2010 19:09:42 -0500
Message-ID: <4CF986C5.8070208@earthlink.net>
Date: Fri, 03 Dec 2010 16:09:41 -0800
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <20101129212013.184B53A6BDB@core3.amsl.com> <E0D3D031-3334-40A2-BAE1-D1E045DBB798@inf-net.nl>
In-Reply-To: <E0D3D031-3334-40A2-BAE1-D1E045DBB798@inf-net.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f5298bd03ebd448ff0c7a1534681dbcbb74350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 138.111.58.2
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] draft-boot-autoconf-support4hosts
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Dec 2010 00:08:26 -0000

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
>