Re: [Autoconf] what's a router

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 05 August 2010 12:05 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 9DFDA3A687B for <autoconf@core3.amsl.com>; Thu, 5 Aug 2010 05:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.14
X-Spam-Level:
X-Spam-Status: No, score=-2.14 tagged_above=-999 required=5 tests=[AWL=0.109, 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 Ottspm6b1idm for <autoconf@core3.amsl.com>; Thu, 5 Aug 2010 05:05:34 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id 27C123A696E for <autoconf@ietf.org>; Thu, 5 Aug 2010 05:05:33 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o75C63w6024484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Aug 2010 14:06:04 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o75C63m8020360; Thu, 5 Aug 2010 14:06:03 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o75C635t015996; Thu, 5 Aug 2010 14:06:03 +0200
Message-ID: <4C5AA92B.3010700@gmail.com>
Date: Thu, 05 Aug 2010 14:06:03 +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: Teco Boot <teco@inf-net.nl>
References: <4C528979.7010006@oracle.com> <201008040756.04650.henning.rogge@fkie.fraunhofer.de> <4C596602.1060308@earthlink.net> <201008051039.03011.henning.rogge@fkie.fraunhofer.de> <4C5A82A1.9000806@gmail.com> <AANLkTinCDg0tq3FdWbH4RUBGC9qnR1vua9NNDNtgRKfA@mail.gmail.com> <D5267CE1-FB95-4A03-8B65-D9199BC72028@inf-net.nl>
In-Reply-To: <D5267CE1-FB95-4A03-8B65-D9199BC72028@inf-net.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "autoconf@ietf.org autoconf@ietf.org" <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 12:05:35 -0000

Le 05/08/2010 13:06, Teco Boot a écrit :
> Alex,
>
> I guess this mail leads to nothing. But I give it a try.
>
>>> To me a router is a device and its software doing this: - has a
>>> routing table called such.
> All nodes have such. Including hosts.
>
>>> - 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.
>
> All nodes have such. Including hosts. Yes, described in RFCs.
> Started in RFC 1122 (or before), extended in many RFC's. Thanks IETF
> members.

If you mean rfc1812.  That "longest match" algo:
- is not the longest-prefix match algo
- talks IPv4 only,
- doesn't say how it "examines": it doesn't say bitwise compare
- doesn't treat the fairly common case of multiple entries of same
   prefix same length,
- does not treat the special default route
- has no licensing scheme
- and more.

As written there it's hardly implementable in an interoperable manner
(as compared to a much better of e.g. segment processing of IPv6 rfc2460
pp 16, or the C in rfc3174 SHA1).

That spec works well by example: it gives good examples, although not
any counter example.

Alex

>
>>> - includes that route.h I believe as CP said.
> Nonsense.
>
>>> - has multiple interfaces.
> All nodes may have such. Including hosts.
>
>>> In a sense every other host (my Windows PC) is a router because
>>> it does all these things.  My PDA, my cell phone, are all
>>> routers.
> Nonsense.
>
>
> Regards, Teco