Re: [Autoconf] what's a router

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 05 August 2010 09:59 UTC

Return-Path: <alexandru.petrescu@gmail.com>
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 9C2FA3A6955 for <autoconf@core3.amsl.com>; Thu, 5 Aug 2010 02:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.167
X-Spam-Level:
X-Spam-Status: No, score=-2.167 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 AkdKPDzPrQgj for <autoconf@core3.amsl.com>; Thu, 5 Aug 2010 02:59:30 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.166.172.107]) by core3.amsl.com (Postfix) with ESMTP id 80E223A6781 for <autoconf@ietf.org>; Thu, 5 Aug 2010 02:59:30 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o759xtcG018026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Aug 2010 11:59:55 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o759xtrH000964; Thu, 5 Aug 2010 11:59:55 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o759xs8g026437; Thu, 5 Aug 2010 11:59:55 +0200
Message-ID: <4C5A8B9A.90904@gmail.com>
Date: Thu, 05 Aug 2010 11:59:54 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1
MIME-Version: 1.0
To: Henning Rogge <henning.rogge@fkie.fraunhofer.de>
References: <4C528979.7010006@oracle.com> <201008051133.32630.henning.rogge@fkie.fraunhofer.de> <4C5A86DD.1050907@gmail.com> <201008051142.48619.henning.rogge@fkie.fraunhofer.de>
In-Reply-To: <201008051142.48619.henning.rogge@fkie.fraunhofer.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] what's a router
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 09:59:31 -0000

Le 05/08/2010 11:42, Henning Rogge a écrit :
> On Thu August 5 2010 11:39:41 Alexandru Petrescu wrote:
>> Le 05/08/2010 11:33, Henning Rogge a écrit :
>>> On Thu August 5 2010 11:21:37 Alexandru Petrescu wrote:
>>>> To me a router is a device and its software doing this: - has
>>>> a routing table called such. - does longest-prefix match
>>>> algorithm to search in it.  This operation
>>>>
>>>> is not specified (no RFC) but it is there everywhere in every
>>>> router, thanks BSD.
>>>>
>>>> - includes that route.h I believe as CP said. - has multiple
>>>> interfaces.
>>> one of them or all of them ?
>>
>> Right, both of them, IMHO.
> That make no sense for a MANET, most MANET routers have only a single
> interface.

Well, are MANET routers 'routers' at all?

Does a MANET router execute the longest-prefix match algorithm?

Does a MANET router select an output interface depending on the result
of that agorithm?  Or is it just doing it with always the same result?

> And you don't need any header files like route.h on a router, just
> on your development system. I don't think you will find many
> embedded routers (DSL, MANET, ...) with header files on them.

WEll... the /usr/include stuff is there everywhere in the deployed
routers running binaries.  E.g. linux phones.  I think a device that
boots a kernel has a file system and that should have a /usr/include.

Alex

>
> Henning Rogge