Re: [Autoconf] practical addressing (was: new charter)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 27 February 2009 17:44 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 EC98A3A6A1D for <autoconf@core3.amsl.com>; Fri, 27 Feb 2009 09:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.186
X-Spam-Level:
X-Spam-Status: No, score=-2.186 tagged_above=-999 required=5 tests=[AWL=0.063, 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 mo8yya56Ncdd for <autoconf@core3.amsl.com>; Fri, 27 Feb 2009 09:44:32 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.166.172.106]) by core3.amsl.com (Postfix) with ESMTP id 02A883A67A3 for <autoconf@ietf.org>; Fri, 27 Feb 2009 09:44:31 -0800 (PST)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-1.2) with ESMTP id n1RHir36000825; Fri, 27 Feb 2009 18:44:53 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by nephilia.intra.cea.fr (8.13.8/8.13.8) with ESMTP id n1RHir8l031663; Fri, 27 Feb 2009 18:44:53 +0100 (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 n1RHirkt011727; Fri, 27 Feb 2009 18:44:53 +0100
Message-ID: <49A82694.8090801@gmail.com>
Date: Fri, 27 Feb 2009 18:44:52 +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> <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com> <49A6D436.7020505@gmail.com> <000001c99845$1dc56190$595024b0$@nl> <49A6F125.40400@gmail.com> <1235680887.4585.5.camel@localhost> <49A7BB89.5040807@gmail.com> <003901c998cb$42b71e90$c8255bb0$@nl> <49A7E97A.2010503@gmail.com> <006801c998fd$06c5bd60$14513820$@nl>
In-Reply-To: <006801c998fd$06c5bd60$14513820$@nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] practical addressing (was: new charter)
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 Feb 2009 17:44:33 -0000

[Thanks for the details Linux/Vista/IOS routing tables!  I didn't know
  all that, only for linux]

Teco Boot a écrit :
>>> Routers may generate a /128 prefix-address, and advertize this in
>>>  the routing domain.
> 
>> A host-based route propagated and deleted throughout a domain? I 
>> don't see the necessity of doing so. Assuming the routers are 
>> mobile within 25m ranges then they wouldn't need to change their 
>> addresses, thus no need to propagate host-based routes.
> 
> If the /128 is not propagated, there will be no multi-hop network.

Well I disagree.  In the multi-hop network below only /64 prefixes are 
present in Routers' routing tables, no /128 (host-based) routes:


   -----  wifi "adhoc1"  ------  wifi "adhoc2"  ------- "adhoc3"-----
  |Host1|---------------|Router|---------------|Router2|-------|Host2|
   ----- LL1    P1   LL2 ------ LL3   P2   LL4  -------LL5 P3  LL6---
         G1                                                    G4

           P1, P2, P3: /64 prefixes, such as:
                       2001:db8:1::/64
                       2001:db8:2::/64 and
                       2001:db8:3::/64

Would this kind of use of /64 prefixes alleviate the need to 
propagate/delete /128 prefixes throughout the network?

Alex