Re: [Autoconf] Closing summary on consensus-call for RFC5889modifications

"Charles E. Perkins" <> Thu, 26 August 2010 13:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BBC743A6876 for <>; Thu, 26 Aug 2010 06:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KP1+VVhW2QOI for <>; Thu, 26 Aug 2010 06:59:30 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 396D33A687D for <>; Thu, 26 Aug 2010 06:59:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327;; b=fjikwgsrPuuYBqiQyO7IV19lGkFMGf2nI0j1tj+sKTXjndIpUr28MgC7DF90YXjW; 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 [] (helo=[]) by with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <>) id 1Ooczq-0001we-MK; Thu, 26 Aug 2010 10:00:02 -0400
Message-ID: <>
Date: Thu, 26 Aug 2010 07:00:00 -0700
From: "Charles E. Perkins" <>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Dearlove, Christopher \(UK\)" <>
References: <> <ABE739C5ADAC9A41ACCC72DF366B719D035CA5CE@GLKMS2100.GREENLNK.NET> <> <ABE739C5ADAC9A41ACCC72DF366B719D03609170@GLKMS2100.GREENLNK.NET> <> <ABE739C5ADAC9A41ACCC72DF366B719D036094AB@GLKMS2100.GREENLNK.NET>
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D036094AB@GLKMS2100.GREENLNK.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f522a1a10624c732f7517c5f3c3795f351e350badd9bab72f9c350badd9bab72f9c
Subject: Re: [Autoconf] Closing summary on consensus-call for RFC5889modifications
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Aug 2010 13:59:34 -0000

Hello Christopher,

I didn't ask what functions YOUR routers performed.

I asked what functions a node would be REQUIRED to
perform in order to communicate in an ad hoc network.

A host does NOT have to pick MPRs in order to
forward packets to a default router.  A host does
NOT have to run a routing protocol in order to
identify one or more default routers.  A host
does NOT have to run a routing protocol in order
to select among network interfaces for delivering
packets to one of its possibly several default

Surely it must be possible to have a discussion
about this without meandering afar from the point.

Charlie P.

On 8/25/2010 8:17 AM, Dearlove, Christopher (UK) wrote:
> I didn't have time to pick up all your points (and I don't
> really have time even for this, so it will be brief).
> You asked what router functions the example I gave satisfied:
> - It's running a routing protocol, and actively participating in
>    it. For example running OLSR it picks MPRs and communicates
>    them.
> - When a host on that node sends a packet, it chooses which
>    neighbour is to be the next hop (possibly even which interface
>    to use to do that) in order to route correctly.
> That'll do to be going on from.
> As for what my mobile is running to pick different points of
> attachment, it's running an entire UMTS protocol stack (and
> a GSM one) to select between base stations. And it's a much
> more asymmetric relationship than any in an ad hoc network.