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

Thomas Heide Clausen <thomas@thomasclausen.org> Fri, 06 August 2010 15:52 UTC

Return-Path: <thomas@thomasclausen.org>
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 BF3CC3A67A2 for <autoconf@core3.amsl.com>; Fri, 6 Aug 2010 08:52:36 -0700 (PDT)
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 gPrkRcrFsiLg for <autoconf@core3.amsl.com>; Fri, 6 Aug 2010 08:52:35 -0700 (PDT)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id C22D228C0E9 for <autoconf@ietf.org>; Fri, 6 Aug 2010 08:52:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 7E3553236DB1; Fri, 6 Aug 2010 08:53:07 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from static-host.sme (AMontsouris-552-1-15-16.w86-212.abo.wanadoo.fr [86.212.102.16]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 5F2083228449; Fri, 6 Aug 2010 08:53:06 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Thomas Heide Clausen <thomas@thomasclausen.org>
In-Reply-To: <4C5B3854.3050706@earthlink.net>
Date: Fri, 6 Aug 2010 17:53:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2946D37-14F1-4DC0-94C3-DC4FE6A3BE79@thomasclausen.org>
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> <4C5B3854.3050706@earthlink.net>
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
X-Mailer: Apple Mail (2.1081)
Cc: autoconf@ietf.org, Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
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: Fri, 06 Aug 2010 15:52:36 -0000

On Aug 6, 2010, at 00:16 , Charles E. Perkins wrote:

>>  "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...>

User applications (regular user applications) reside on hosts. Hosts are accessing the network by way of being connected to (i.e. one IP hop away from) a router. 

The connectivity between a host and a router is a "classic IP link", and there are already excellent protocols in existence for managing also autoconfiguration of addresses for hosts on classic IP links. 

The connectivity between routers is.....who knows? Maybe a MANET, maybe an OSPF network, maybe an ISIS network, and maybe links between routers have "undetermined connectivity properties" -- or not, they may be of NBMA or P2P or telepathic nature. However, that's a matter for routers to figure out and manage; hosts are exposed to a classic IP link and are isolated by an IP hop from any specific connectivity properties of the connectivity/links between routers.

Of course, there *may* be applications (for example, the routing demon) running on routers and exposed to the specific connectivity properties of the connectivity/links between routers. These, and only these (non-user) applications should be sufficiently aware of these properties to operate correctly. User-applications reside on hosts, separated by an IP hop from any "strangeness" between routers, and exposed to well-defined properties of a classic IP link.

That is analogous to how the Internet otherwise work.

>> 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.

Now, you made me go look it up exactly...

This particular point was discussed - at length - at IETF'67 in 2006 in San Diego, where it received (in my recollection) wide consensus; in part because of its analogy with the "regular Internet".

Sincerely yours,

Thomas