Re: [Autoconf] Updated ad hoc addressing model document

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 29 January 2010 17:10 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 64D043A6A55 for <autoconf@core3.amsl.com>; Fri, 29 Jan 2010 09:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 6PA8QqTo7J+z for <autoconf@core3.amsl.com>; Fri, 29 Jan 2010 09:10:32 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 239EA3A6A4F for <autoconf@ietf.org>; Fri, 29 Jan 2010 09:10:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=HpLrE2wTqFY3IS8CDMfK3gj3JoTv7lNl6BJwDRrYgogIhJ4g943uhUbuZ1jOtj9r; 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 [12.204.153.98] (helo=[10.166.254.12]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1NauMu-00011O-G1; Fri, 29 Jan 2010 12:10:52 -0500
Message-ID: <4B631699.7040504@earthlink.net>
Date: Fri, 29 Jan 2010 09:10:49 -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.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <be8c8d781001260409qd23d4era0eac47eaeb3dba2@mail.gmail.com> <8DCBF4A4-7879-4148-A8FE-9A73219536B9@gmail.com> <008c01caa0fe$0eee3530$2cca9f90$@nl>
In-Reply-To: <008c01caa0fe$0eee3530$2cca9f90$@nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52ebb43ebc1bfe3012062c88a9b2d2eb4c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: autoconf@ietf.org, 'Thomas Heide Clausen' <thomas@thomasclausen.org>
Subject: Re: [Autoconf] Updated ad hoc addressing model document
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: Fri, 29 Jan 2010 17:10:34 -0000

Hello Teco,

On 1/29/2010 8:13 AM, Teco Boot wrote:
> I am quite uncomfortable with a large drawback of the proposed
> addressing model, which makes it unacceptable for the deployed MANETs
> I am involved in.
> My requirement is that L3 communication between nodes, that have L2
> connectivity, must be possible in all conditions, including conditions
> with a non-operational MANET protocol.
>    

I don't see that the addressing model prevents any such L3 communication.

> Maybe this drawback is overlooked or underestimated.
>    

It doesn't even seem to be a drawback at all as far as I can tell.

> And the text on link locals does not describe how IPv6 works. LLs are
> used in MANETs for multiple purposes. We can't without.
>    

This isn't true.  You can build MANETs without using link-local at all
in any fashion.

I'm not saying you have to ignore link-local.


> My other comments are textual or on incompleteness. Especially, the
> document doesn't describe anything useful for assigning globals.
>    

Yeah, it would be nice if we could get to the
point of doing address autoconfiguration in
this group.

Regards,
Charlie P.