Re: [Autoconf] new charter

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 27 February 2009 10:07 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 872963A6BAA for <autoconf@core3.amsl.com>; Fri, 27 Feb 2009 02:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level:
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=0.068, 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 WmH-nDzBcidH for <autoconf@core3.amsl.com>; Fri, 27 Feb 2009 02:07:49 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.166.172.107]) by core3.amsl.com (Postfix) with ESMTP id 68D973A6AC3 for <autoconf@ietf.org>; Fri, 27 Feb 2009 02:07:49 -0800 (PST)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-1.2) with ESMTP id n1RA8A9P030519; Fri, 27 Feb 2009 11:08:10 +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 n1RA8AKV005167; Fri, 27 Feb 2009 11:08:10 +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 n1RA89ri018028; Fri, 27 Feb 2009 11:08:09 +0100
Message-ID: <49A7BB89.5040807@gmail.com>
Date: Fri, 27 Feb 2009 11:08:09 +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>
In-Reply-To: <1235680887.4585.5.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] 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 10:07:50 -0000

Carlos Jesús Bernardos Cano a écrit :
> Hi Alex:
> 
> One question below.
> 
> El jue, 26-02-2009 a las 20:44 +0100, Alexandru Petrescu escribió:
>> Sorry, I made an error indeed putting same prefix.  How about this
>>  updated picture with the prefixes being distinct:
>> 
>> 
>> -----  wifi "adhoc1"  ------  wifi "adhoc2"  ----- 
>> |Host1|---------------|Router|---------------|Host2| ----- LL1
>> LL2 ------ LL3        LL4  ----- G1
>> G4
>> 
>> 
>> "adhoc1" and "adhoc2": 802.11 ESSIDs in "ad-hoc" mode. Each is an
>> IPv6 subnet. LL1...4: IPv6 link-local addresses. Self-formed
>> according to rfc2464. G1, G4:  IPv6 global addresses, for example 
>> 2001:db8:1::1/64 and 2001:db8:2::4/64 Manually assigned, or
>> pre-configured with SNMP or formed according to stateless autoconf
>> rfc4862; the prefixes are advertised by Router in RAs.
>> 
> 
> Does this model only apply to Host-Router-Host scenarios?

Yes.

> I mean, does this model apply for Router-Router-Router scenarios?

Something like this?:

        -------  wifi "adhoc1"  -------  wifi "adhoc2"  -------
       |Router1|---------------|Router2|---------------|Router3|
        ------ LL1          LL2 -------LL3          LL4 -------
               G1                                    G4

       G1, G4: ?

> I fully agree the model fits the first scenario, but I don't for the
>  second, since routers' mobility within the ad-hoc network would
> force them to change prefixes often, I guess.

Ah.  But before being forced to change a prefix, a Router could still
move around as much as it wants.  I think the limit is within 25m range,
as imposed by the wifi 50m area (25m for two routers in opposite
directions).  What do you think about this practical limit?

> For those scenarios it might be better to think of addressing models
> in which MANET routers are configured with /128 (or /32 for IPv4)
> addresses, so they don't need to change their addresses as a result
> of link changes.

Sorry... in the picture above the addresses are also /128.  It was an 
abbreviation for me to show only 2001:db8:1::1/64 assigned to Host1. 
The full notation should have been 2001:db8:1::/64 prefix and 
2001:db8:1::1/128.  Would the following picture satisfy the need for 
/128 addresses?:

         -----  wifi "adhoc1"  ------  wifi "adhoc2"  -----
        |Host1|---------------|Router|---------------|Host2|
         ----- LL1    P1   LL2 ------ LL3   P2   LL4  -----
               G1                                G4

        G1, G4:  IPv6 global addresses, for example
                 2001:db8:1::1/128 and
                 2001:db8:2::4/128
                 Manually assigned, or pre-configured with SNMP
                 or formed according to stateless autoconf rfc4862;
                 the prefixes are advertised by Router in RAs.
        P1, P2:  IPv6 global prefixes, for example
                 2001:db8:1::/64 and
                 2001:db8:2::/64
                 Manually assigned, or pre-configured with SNMP.


Or is it not what you mean?

I also don't understand why you think that if /128 addresses are 
assigned to routers then they don't need to change them as a result of 
link changes.

Alex