Re: [Autoconf] Self-addressing using local information

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 04 February 2009 14:57 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 451953A6937 for <autoconf@core3.amsl.com>; Wed, 4 Feb 2009 06:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.179
X-Spam-Level:
X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5 tests=[AWL=0.070, 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 3izSZ18mQC6a for <autoconf@core3.amsl.com>; Wed, 4 Feb 2009 06:57:35 -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 6282128C268 for <autoconf@ietf.org>; Wed, 4 Feb 2009 06:57:28 -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 n14Ev7vV027404; Wed, 4 Feb 2009 15:57:07 +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 n14Ev7kP002199; Wed, 4 Feb 2009 15:57:07 +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 n14Ev6Ca001660; Wed, 4 Feb 2009 15:57:07 +0100
Message-ID: <4989ACC2.6050303@gmail.com>
Date: Wed, 04 Feb 2009 15:57:06 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Ricardo Schmidt <super.ismiti@gmail.com>
References: <db92277f0902040439h5a7b7b47k516d87adc1cb7e66@mail.gmail.com>
In-Reply-To: <db92277f0902040439h5a7b7b47k516d87adc1cb7e66@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Self-addressing using local information
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, 04 Feb 2009 14:57:40 -0000

Ricardo Schmidt a écrit :
> Hello all,
> 
> I am developing a short introducing research on autoconfiguration in
> MANETs. Right now I am writing about some protocols for
> self-addressing.

'Self'-addressing?  Maybe the use of the loopback address is pertinent?
  127.0.0.1

> I noticed that, most of the proposed solutions implement a randomly 
> choice of address. For example, a node picks an address from the
> range 1-2047 for temporary address and later an address from the
> range 2048-65534 for the tentative address.

Are we talking about an article (which?) or an Internet Draft or an RFC? 
    Or a non-standard implementation?

For IPv6 there's the forming of a link-local address from the MAC 
address of the interface RFC2464, and the 'privacy' extensions for 
global addresses (basically a random choice) RFC4941.

> Well, I would like to know if there available works where a formula
> is implemented for creating an address, in order to avoid the 
> duplication. Something like Prophet. However, I am looking for a 
> proposal that uses information such as the MAC from the interface to 
> calculate a tentative address.

Sorry what is Prophet?

MAC is used directly to form the IPv6 link-local address over Ethernet 
and the IPv6 global address some times.

For IPv4, there are IPv4 link-local addresses 169.254.x.x RFC3927, and 
within the text there's recommendation to use the MAC address as a seed 
for the random generation.  These addresses are used for example by 
Microsoft's ActiveSync IP over USB, and I guess by Apple's Bonjour; for 
example some ActiveSync devices show:

> Carte Ethernet Connexion au reseau local 5:
> 
>         Suffixe DNS propre a la connexion : 
>         Description . . . . . . . . . . . : Windows Mobile-based Device
>         Adresse physique . . . . . . . . .: 80-00-60-0F-E8-00
>         DHCP active. . . . . . . . . . . : Oui
>         Configuration automatique activee . . . . : Oui
>         Adresse IP. . . . . . . . . . . . : 169.254.2.2
>         Masque de sous-reseau . . . . . . : 255.255.255.0
>         Adresse IP. . . . . . . . . . . . : fe80::8200:60ff:fe0f:e800%16
>         Passerelle par defaut . . . . . . : 
>         Serveur DHCP. . . . . . . . . . . : 169.254.2.1
>         Serveurs DNS . . . . . . . . . .  : fec0:0:0:ffff::1%1
> 	                                    fec0:0:0:ffff::2%1
> 	                                    fec0:0:0:ffff::3%1
>         Bail obtenu . . . . . . . . . . . : mercredi 4 fevrier 2009 15:10:20
>         Bail expirant . . . . . . . . . . : vendredi 6 mars 2009 15:10:20

(remark how this is USB and has no IEEE-assigned MAC address, but it has
  a 'self'-generated MAC address on 48bit and is used to form an IP
  address over USB even if there's no IP-over-USB RFC :-)

There are sometimes contradictory requirements between uniqueness and 
privacy of an address.


Alex