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

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 27 August 2010 11:28 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 E3FBF3A6782 for <autoconf@core3.amsl.com>; Fri, 27 Aug 2010 04:28:29 -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=[AWL=0.000, 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 rilX5ep7jqJ0 for <autoconf@core3.amsl.com>; Fri, 27 Aug 2010 04:28:29 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id 00D893A681D for <autoconf@ietf.org>; Fri, 27 Aug 2010 04:28:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Q23NjbpC9VdbVhdNXBHLUIGzwieoZ5oUSJxso6I2QL8uboC+GkkaymQk9v7Viabz; 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 [207.74.239.6] (helo=[10.150.0.248]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1Oox7E-0003JJ-Li; Fri, 27 Aug 2010 07:29:01 -0400
Message-ID: <4C77A17A.1090708@earthlink.net>
Date: Fri, 27 Aug 2010 04:28:58 -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.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Dearlove, Christopher \(UK\)" <Chris.Dearlove@baesystems.com>
References: <AANLkTi=MZORvNSW7wHdHYOzkOwNZojBars26GfSPgWc9@mail.gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D035CA5CE@GLKMS2100.GREENLNK.NET> <4C741EBB.8060909@earthlink.net> <ABE739C5ADAC9A41ACCC72DF366B719D03609170@GLKMS2100.GREENLNK.NET> <4C75308C.1090506@earthlink.net> <ABE739C5ADAC9A41ACCC72DF366B719D036094AB@GLKMS2100.GREENLNK.NET> <4C767360.7050805@earthlink.net> <ABE739C5ADAC9A41ACCC72DF366B719D03609914@GLKMS2100.GREENLNK.NET> <4C773080.8010601@earthlink.net> <ABE739C5ADAC9A41ACCC72DF366B719D03609AE8@GLKMS2100.GREENLNK.NET>
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D03609AE8@GLKMS2100.GREENLNK.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52e1e9829af188f5961ef01f0f1eaff11d350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.74.239.6
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Closing summary on consensus-call for RFC5889modifications
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, 27 Aug 2010 11:28:30 -0000

Hello Chris,

The examples I gave DO NOT provide the
functionality in your message.

That _is_ the point.  The point is that a node can
beneficially reside in an ad hoc network without
doing those things.  ... and that we should not
legislate otherwise.

Regards,
Charlie P.



On 8/27/2010 1:26 AM, Dearlove, Christopher (UK) wrote:
> I'm failing to see how any of the examples you quote (which I
> agree, would not make a node a router) are sufficient for all
> of the functionality I noted. I really would like (but I'll
> be unable to reply to for at least some days - it's a long
> weekend coming up) to know how you get the functionality.
> Ideally I'd like equivalent functionality to the OLSR example,
> what I wouldn't count is where a host node is permanently
> (albeit wirelessly) attached to a single other router node.
> How far from the latter and close to the former can you get?
> (I can see how to get from the one permanent point of
> attachment to occasionally changing that, with transients,
> using Mobile IP.)
>