[Autoconf] Self-addressing using local information

Ricardo Schmidt <super.ismiti@gmail.com> Wed, 04 February 2009 12:39 UTC

Return-Path: <super.ismiti@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 8CB8B28C201 for <autoconf@core3.amsl.com>; Wed, 4 Feb 2009 04:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 KAbq-CZApQHs for <autoconf@core3.amsl.com>; Wed, 4 Feb 2009 04:39:40 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by core3.amsl.com (Postfix) with ESMTP id C844E28C17E for <autoconf@ietf.org>; Wed, 4 Feb 2009 04:39:40 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so2824140wfd.31 for <autoconf@ietf.org>; Wed, 04 Feb 2009 04:39:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=QoNwrR08SEvNL4n6H+twyDXHKXK2DGUfH78xP1opN74=; b=IvQHKfh6/68l5zmYXBIHEn232lVj716HscfSqu/AfGmTtpNUl5waNLNzcHgQNRXuGy abcPASPCWw6Ow7OLd1TrKZPSrkCKmTvT00o8p44+3MWje61PQeKzg0fvMon9a5W7NQfG wxX2o1JESNy+L39UAm3VgZgb4zMu4nK5H1WtQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=f2AhNVag5h8G94BQqPzLjK+v6l909Fr97aKwh2FY/R71Wsfs+Px1D7dExVMmZGcpcR FkNgp+Ez9YQyaC5XgssFiU9qX1nAP+IuMI0tq9Nw9KisOKaWW5H+Gsm7O4A4ddwqNr9N DRhcNrbCBI/LEayMKJmFCwChdLHEKH8+QqN58=
MIME-Version: 1.0
Received: by 10.142.240.19 with SMTP id n19mr619861wfh.10.1233751160981; Wed, 04 Feb 2009 04:39:20 -0800 (PST)
Date: Wed, 04 Feb 2009 10:39:20 -0200
Message-ID: <db92277f0902040439h5a7b7b47k516d87adc1cb7e66@mail.gmail.com>
From: Ricardo Schmidt <super.ismiti@gmail.com>
To: autoconf@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [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 12:39:41 -0000

Hello all,

I am developing a short introducing research on autoconfiguration in MANETs.
Right now I am writing about some protocols for self-addressing.

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.

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.

Thanks in advance for repliers!

-- 
Ricardo de Oliveira Schmidt