Re: [Autoconf] Autoconf addressing model

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 28 February 2009 14:09 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 C70443A6A08 for <autoconf@core3.amsl.com>; Sat, 28 Feb 2009 06:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Level:
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=0.073, 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 az3raF7LgEnr for <autoconf@core3.amsl.com>; Sat, 28 Feb 2009 06:09:26 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id C57343A6997 for <autoconf@ietf.org>; Sat, 28 Feb 2009 06:09:24 -0800 (PST)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 40709E0810F; Sat, 28 Feb 2009 15:09:42 +0100 (CET)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp6-g21.free.fr (Postfix) with ESMTP id 018C9E080E3; Sat, 28 Feb 2009 15:09:39 +0100 (CET)
Message-ID: <49A94589.9050203@gmail.com>
Date: Sat, 28 Feb 2009 15:09:13 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: cjbc@it.uc3m.es
References: <499F0BA7.90501@piuha.net> <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com> <49A6D436.7020505@gmail.com> <000001c99845$1dc56190$595024b0$@nl> <49A6F125.40400@gmail.com> <1235680887.4585.5.camel@localhost> <002f01c998bf$8f112210$ad336630$@nl> <1235828619.6096.24.camel@localhost>
In-Reply-To: <1235828619.6096.24.camel@localhost>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 090227-0, 27/02/2009), Outbound message
X-Antivirus-Status: Clean
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Autoconf addressing model
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: Sat, 28 Feb 2009 14:09:26 -0000

Carlos Jesús Bernardos Cano a écrit :
[...]
>> It doesn't matter how many ad hoc segments there are. In the following
>> scenario, the link to Access router G disappeared, Router 3 disappeared and
>> a Router4 joined IBSS "adhoc1".
>>
>>
>>
>>      ---+-------Internet------
>>         |                     
>>         |           
>> +-------+-------+      
>> |Access Router H|       
>> +-------+-------+        
>>         |                       
>>         ||Prefix information H  
>>         |V                     wifi "adhoc1"
>>         |                   <---------------------------v--------> 
>>  <------|--v---------------------->                     | 
>>         |<-|--------------------v-----------------------|--->
>>         |  |                    |                       |
>>     +---+--'+               +---'---+               +---'---+
>>     |Router1|>-------------<|Router2|>-------------<|Router4|
>>     +---L---+ LL1      LL21 +---L---+ LL22      LL4 +---L---+
>>         |M1                     |M2                     |M4
>>         |H1                     |H2                     |H4
>>
>>               --------->               --------->
>>               Prefix information H     Prefix information H
>>
>>
>> Now, Router2 acts as a relay for Router4, so Router4 can reach Router1 and
>> the Internet. Router1 acts as Border Router for all nodes in the MANET.
>>
> 
> While I think this is also much in linee with my thinking, I think it's
> better to focus on the simplest cases before.

What are the simplest cases?

Alex