Re: [Autoconf] Autoconf addressing model

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 05 March 2009 17:53 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 D061528C3BF for <autoconf@core3.amsl.com>; Thu, 5 Mar 2009 09:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 tagged_above=-999 required=5 tests=[AWL=0.138, 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 dwOWtB5E0bQd for <autoconf@core3.amsl.com>; Thu, 5 Mar 2009 09:53:41 -0800 (PST)
Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) by core3.amsl.com (Postfix) with ESMTP id CBA3528C288 for <autoconf@ietf.org>; Thu, 5 Mar 2009 09:53:39 -0800 (PST)
Received: from smtp2-g21.free.fr (localhost [127.0.0.1]) by smtp2-g21.free.fr (Postfix) with ESMTP id 160E64B0156; Thu, 5 Mar 2009 18:54:04 +0100 (CET)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp2-g21.free.fr (Postfix) with ESMTP id A34BF4B01C3; Thu, 5 Mar 2009 18:54:01 +0100 (CET)
Message-ID: <49B011B2.600@gmail.com>
Date: Thu, 05 Mar 2009 18:53:54 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <499F0BA7.90501@piuha.net> <49AD9760.3080909@gmail.com> <49AD98D4.3@earthlink.net><49AD9EA8.6040803@gmail.com> <49ADA17B.9040600@earthlink.net><49ADAF7C.1050509@gmail.com> <49ADB9FB.6050600@earthlink.net> <49AE3A3A.5000305@gmail.com> <7FB7EE0A621BA44B8B69E5F0A09DC76407B5D783@xmb-rtp-208.amer.cisco.com> <49AE9827.5090309@gmail.com> <7FB7EE0A621BA44B8B69E5F0A09DC76407B5D803@xmb-rtp-208.amer.cisco.com> <49AEBA6D.7030903@gmail.com> <7FB7EE0A621BA44B8B69E5F0A09DC76407B5DB1F@xmb-rtp-208.amer.cisco.com> <49AF97FA.70200! 07@gmail.com> <002201c99d76$017d4b20$0477e160$@nl> <49AFAA15.9! 060905@gmail.com> <003a01c99d8e$f47ba2f0$dd72e8d0$@nl> <49AFD85E.50403! 01@gmail.com> <004a01c99d9b$542e1e10$fc8a5a30$@nl> <49AFDE93.60! 904@gmail.com> <004b01c99da1$dc4ab9b0$94e02d10$@nl> <49AFEB3C! .8010703@gmail.com> <004c01c99da7$ee315700$ca940500$@nl> <49AFF! 2B7.2060600@gmail.com> <005701c99db0$adbc6620$09353260$@nl> <49B0026F.5070905@gmail.co m> <006401c99db5$cad6dc90$608495b0$@nl>
In-Reply-To: <006401c99db5$cad6dc90$608495b0$@nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 090305-0, 05/03/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: Thu, 05 Mar 2009 17:53:41 -0000

Teco Boot a écrit :
> OK, we can start with a single interface setup:
> Agreed on the starting point with three nodes, and non-transitivity solved
> by MANET Routing?
> 
>                               
>                            <-------------------------v-------->
> <------v-------------------------->                  |
>    <---|----------------------v----------------------|--->
>        |                      |                      |
>        |2001:db8:1::1/64      |2001:db8:2::2/64      |2001:db8:3::3/64
>        |fe80::1/64            |fe80::2/64            |fe80::3/64
>    +---+---+              +---+---+              +---+---+
>    |Router1|              |Router2|              |Router3|
>    +-------+              +-------+              +-------+

Teco I don't agree with this setup.  It's a significant leap of faith 
from the initial starting point.

I need first to listen to what others think about the initial starting 
point.

Alex

> 
> 
> Routing table Router1:
> Destination       Next-hop    Hops
> ===============   ========    ====
> 2001:db8:2::/64   fe80::2     1
> 2001:db8:3::/64   fe80::2     2
> 
> Routing table Router2:
> Destination       Next-hop    Hops
> ===============   ========    ====
> 2001:db8:1::/64   fe80::1     1
> 2001:db8:3::/64   fe80::3     1
> 
> Routing table Router3:
> Destination       Next-hop    Hops
> ===============   ========    ====
> 2001:db8:1::/64   fe80::2     2
> 2001:db8:2::/64   fe80::2     1
> 
> I see a problem with this, who has assigned the globally unique prefixes?
> Manually configured? Is it intended to connect to the Internet? Is the
> Access Router known on forehand?
> Maybe it is better to start with ULA as the most basic setup.
> 
> 
> Teco.
> 
> 
> 
> 
> 
>