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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 25 August 2010 16:14 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 EA2D33A6B36 for <autoconf@core3.amsl.com>; Wed, 25 Aug 2010 09:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.136
X-Spam-Level:
X-Spam-Status: No, score=-2.136 tagged_above=-999 required=5 tests=[AWL=0.113, 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 UoS1VzTpoQrf for <autoconf@core3.amsl.com>; Wed, 25 Aug 2010 09:14:32 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.166.172.106]) by core3.amsl.com (Postfix) with ESMTP id 5D4BB3A689F for <autoconf@ietf.org>; Wed, 25 Aug 2010 09:14:32 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o7PGF4nU011354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <autoconf@ietf.org>; Wed, 25 Aug 2010 18:15: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 o7PGF4Ku031818 for <autoconf@ietf.org>; Wed, 25 Aug 2010 18:15:04 +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 o7PGF4Jg014309 for <autoconf@ietf.org>; Wed, 25 Aug 2010 18:15:04 +0200
Message-ID: <4C754187.4090301@gmail.com>
Date: Wed, 25 Aug 2010 18:15: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.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: autoconf@ietf.org
References: <AANLkTi=MZORvNSW7wHdHYOzkOwNZojBars26GfSPgWc9@mail.gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D035CA5CE@GLKMS2100.GREENLNK.NET> <4C741EBB.8060909@earthlink.net> <ABE739C5ADAC9A41ACCC72DF366B719D03609170@GLKMS2100.GREENLNK.NET> <4C75308C.1090506@earthlink.net>
In-Reply-To: <4C75308C.1090506@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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: Wed, 25 Aug 2010 16:14:34 -0000

Le 25/08/2010 17:02, Charles E. Perkins a écrit :
> Hello Chris,
>
> Follow-up below...
>
> On 8/25/2010 1:45 AM, Dearlove, Christopher (UK) wrote:
>
>> I didn't make the definition, go back to RFC 2501.
>
> I did. I even quoted 2501 in part of my message to you that you
> didn't answer.
>
>> If the node is to be mobile, attaching at different points,
>> available as a destination to others, it has to be running
>> something.
>
> Mobile nodes do this today and they aren't classified as routers.

Charlie - a Node is a Host "or" a Router - this makes all Mobile Nodes
routers...

I have a hard time seeing Hosts anywhere actually.

I agree that a smartphone with a huge IP stack can do many dynamic
addressing and routing things without running dynamic routing protocols,
w/o running Mobile IP.  And that smartphone is a "Host" in the sense
that it is the end of the application (end-to-end), TCP), end of IPsec,
has GUI to human fingers and eyes, browses the Web as a Client for
entertainment -- all being run sometimes by Routers too... they're all
Routers in the end.

Maybe we could distinguish them better based on the data structures and
algos.

Maybe a Host is a machine whose main goal is to run TCP, whereas a
Router's main goal is to run longest-prefix match.

During one identifiable second a machine doing more MIPS for TCP than
for longest-prefix match, is a Host, otherwise it's a Router.

A machine with more bytes in the routing table than in the TCP
structures, at a given time, is a Host.

Or so...

Alex

  You can even do it without running Mobile IP
> to some extent.
>
> Regards, Charlie P.
>
>
> On 8/25/2010 1:45 AM, Dearlove, Christopher (UK) wrote:
>> I didn't make the definition, go back to RFC 2501.
>>
>> If the node is to be mobile, attaching at different points,
>> available as a destination to others, it has to be running
>> something.
>>
>
> _______________________________________________ Autoconf mailing list
> Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf
>