Re: [Autoconf] WC consensus call for RFC5889 modifications (Fwd:Forgotone [Was: RFC 5889)

"Charles E. Perkins" <charles.perkins@earthlink.net> Thu, 05 August 2010 22:16 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 9D09E3A6999 for <autoconf@core3.amsl.com>; Thu, 5 Aug 2010 15:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=0.401, 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 Cl4Bqk5UIGpB for <autoconf@core3.amsl.com>; Thu, 5 Aug 2010 15:16:31 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 443AB3A687F for <autoconf@ietf.org>; Thu, 5 Aug 2010 15:16:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=FEX+uZHhJkimGn2KQnH8kd+2mVZ3/hbsY6BLIBMnvFoxq4DVLjOQSr6V0UV2BvuS; 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.158]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1Oh8kH-0008Ux-AX; Thu, 05 Aug 2010 18:17:01 -0400
Message-ID: <4C5B3854.3050706@earthlink.net>
Date: Thu, 05 Aug 2010 15:16:52 -0700
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.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
References: <4C528979.7010006@oracle.com><201008040756.04650.henning.rogge@fkie.fraunhofer.de> <4C596602.1060308@earthlink.net><201008051039.03011.henning.rogge@fkie.fraunhofer.de> <AANLkTikWgoUHeJsZwWDViVyavWXjvtLfffrosHPcCPya@mail.gmail.com>
In-Reply-To: <AANLkTikWgoUHeJsZwWDViVyavWXjvtLfffrosHPcCPya@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f526857921bea0441b29a9cdeb34832a54b350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] WC consensus call for RFC5889 modifications (Fwd:Forgotone [Was: RFC 5889)
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: Thu, 05 Aug 2010 22:16:32 -0000

Hello Emmanuel,

> Maybe it would be easier to focus on the counterpart instead, and
> consider the question "what is the definition of a host?". It seems to
> me that the devices we are aiming to configure are typically capable of
> things that hosts can't do (including, for instance, forwarding traffic
> on behalf of other devices, if necessary).

I don't think so.  If a device is a host and not
a router, it shouldn't be forwarding packets.

I'm sure that there are going to be non-routing
hosts in wireless ad hoc networks.  From previous
design work, I know that it is absolutely straightforward
to allow a host to request an address and get one (if
available).  You might check [from year 2001]:
	www.cs.ucsb.edu/~ebelding/txt/autoconf.txt
We seemed to know more on average in 2001, than has
been displayed here lately in the autoconf WG.  A node
does NOT have to forward packets to request an address!



>   "hosts are considered to be connected to a MANET only through
> a router, and thus, the MANET can be considered as comprising of only
> routers".

Do you _really_ want to exclude hosts from your network?
Where will the applications reside?  Hmmm... a network without
hosts...  Seems like a niche market.  But, ad hoc networks
are still a niche market, so this would be a niche niche
market.  <hmmm, sounds like Monty Python's knights...>

> This architectural consideration thus separated the issue of
> "configuring routers" from the issue of "configuring hosts" in this
> context, and the rough consensus was that we would first focus on
> configuring routers. Which lead us to where we are now.

When was this rough consensus?  Do you mean in Maastricht?
Or, before?  If the latter, I surely missed it.

Regards,
Charlie P.