Re: [Autoconf] Another addressing model for AUTOCONF

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 23 July 2010 14:05 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 43FC33A6876 for <autoconf@core3.amsl.com>; Fri, 23 Jul 2010 07:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.14
X-Spam-Level:
X-Spam-Status: No, score=-2.14 tagged_above=-999 required=5 tests=[AWL=0.109, 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 Vo8VlZulknrK for <autoconf@core3.amsl.com>; Fri, 23 Jul 2010 07:05:20 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id 581363A686B for <autoconf@ietf.org>; Fri, 23 Jul 2010 07:05:19 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o6NE5bRr018568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Jul 2010 16:05:37 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o6NE5bcY006556; Fri, 23 Jul 2010 16:05:37 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o6NE5aWX024036; Fri, 23 Jul 2010 16:05:37 +0200
Message-ID: <4C49A1B0.2010204@gmail.com>
Date: Fri, 23 Jul 2010 16:05:36 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <4C48B1AE.2030408@gmail.com> <672CA84A-1850-4B17-922F-AE75D4CF961B@inf-net.nl> <4C4987EC.3000500@gmail.com> <7760A358-F35E-4868-9580-9F2324B07F11@inf-net.nl> <4C499A55.6080103@gmail.com> <279CC75B-84C2-4646-82E0-023DDED29C15@inf-net.nl>
In-Reply-To: <279CC75B-84C2-4646-82E0-023DDED29C15@inf-net.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "autoconf@ietf.org" <autoconf@ietf.org>
Subject: Re: [Autoconf] Another addressing model for AUTOCONF
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, 23 Jul 2010 14:05:22 -0000

Le 23/07/2010 15:55, Teco Boot a écrit :
>
> Op 23 jul 2010, om 15:34 heeft Alexandru Petrescu het volgende
> geschreven:
>
>>> You depict multiple addresses with FE80::FFFE_MAC1 and
>>> FE80::FFFE_MAC2. You have dup L2 addresses (please destroy your
>>> stuff), or you spoof addresses (please don't).
>>
>> Ah yes sorry.  It is again wrong notation on my side.
>> "FE80::FFFE_MAC1" is abbreviation to mean the link local address
>> derived from that interface's MAC address.
>>
>> I do not mean to spoof any address from any interface to any other,
>> sorry for misunderstanding.
>>
>> I could further explain if needed.  And I can change the slide if
>> I ever present in AUTOCONF... I am still unaware of any agenda and
>>  time is short now.
>
> OK, now you cleared up your proposal. I think it is not new, and in
> line with IPv6 address architecture.

WEll it is indeed not new, but different than the current addressing
model draft.

> Your proposal highly relate to MEXT, MNP is provided with mechanisms
> defined in MEXT, isn't it?

Well no, not for the moment.  The MNP is provided I don't know how.  But
however provides that MNP must update routing.

> So better leave it there.

I will present there.

> Back to Autoconf: we are looking for solutions for configuring
> addresses / prefixes for nodes that require multi-hop communication,
> without restrictions for packet relaying via same interface, either
> for isolated MANETs and / or for MANETs connected to the Internet.

Ok, deserves another thread, but I don't understand your "without
restrictions for packet relaying via same interface".  My mechanism does
not relay packets via the same interface.

Alex

>
> Teco.
>
>