IETF Logo Mail Archive

Re: [Autoconf] Updated ad hoc addressing model document

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 05 February 2010 18:18 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 974193A6C14 for <autoconf@core3.amsl.com>; Fri, 5 Feb 2010 10:18:32 -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=[AWL=0.000, 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 kM1-Y1-Sok-Q for <autoconf@core3.amsl.com>; Fri, 5 Feb 2010 10:18:31 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id C54343A6F6A for <autoconf@ietf.org>; Fri, 5 Feb 2010 10:18:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=BNzBU9CWy5ucelVwnWUNwaJLzvDPuz4so+qS4ookgBqByqjuN2845q4+XyFyxuWM; 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.146]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1NdSm1-0002dZ-1u; Fri, 05 Feb 2010 13:19:21 -0500
Message-ID: <4B6C6120.7000808@earthlink.net>
Date: Fri, 05 Feb 2010 10:19:12 -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> <4B631699.7040504@earthlink.net> <009001caa10d$8729a2a0$957ce7e0$@nl> <4B6347DA.1040004@earthlink.net> <00a601caa19e$7122c810$53685830$@nl> <C8A0698C-B04F-475B-B750-842C8786778F@thomasclausen.org> <005501caa5a5$9b0fc7d0$d12f5770$@nl> <6CD290EC-969F-4421-B5C9-0558A4A5A865@thomasclausen.org> <003501caa63a$7b15ca20$71415e60$@nl>
In-Reply-To: <003501caa63a$7b15ca20$71415e60$@nl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52ed5bd4d89443134cc42f1e374370bb89350badd9bab72f9c350badd9bab72f9c
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, 05 Feb 2010 18:18:32 -0000

Hello Teco,


On 2/5/2010 12:09 AM, Teco Boot wrote:

>
> The IP stack puts the configured prefixes on IP interfaces in the
> routing table. This provides L3 connectivity whenever there is a L2
> link.

You used "configured" in a magic way.
Where did the configuration arise?

> The 'something clever' puts longer prefixes in the routing table.
> This could introduce multi-hop paths for 1-hop reachable nodes, for sure
> when link metrics are in place. And of course multi-hop paths to nodes
> that are in the MANET, but not 1-hop reachable.

O.K.

>
> I strongly disagree with "that 'something clever' is the same thing as
> what configures the interface". Our old charter was clear the Autoconf
> mechanism shall be independent of MANET protocols.

I do not remember anyone claiming that they were the same.
What am I missing?

Regards,
Charlie P.

v2.8.7 | Report a Bug | By Email