Re: [Autoconf] Another addressing model for AUTOCONF
Teco Boot <teco@inf-net.nl> Fri, 23 July 2010 10:58 UTC
Return-Path: <teco@inf-net.nl>
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 2C3E73A69D2 for <autoconf@core3.amsl.com>;
Fri, 23 Jul 2010 03:58:17 -0700 (PDT)
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 7gI+Qc4JFUPI for
<autoconf@core3.amsl.com>; Fri, 23 Jul 2010 03:58:16 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com
[209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id DCA663A69AC for
<autoconf@ietf.org>; Fri, 23 Jul 2010 03:58:15 -0700 (PDT)
Received: by ewy22 with SMTP id 22so29106ewy.31 for <autoconf@ietf.org>;
Fri, 23 Jul 2010 03:58:33 -0700 (PDT)
Received: by 10.213.33.197 with SMTP id i5mr465502ebd.44.1279882713435;
Fri, 23 Jul 2010 03:58:33 -0700 (PDT)
Received: from [10.128.0.173] ([77.61.241.196]) by mx.google.com with ESMTPS
id x54sm180649eeh.11.2010.07.23.03.58.32 (version=TLSv1/SSLv3 cipher=RC4-MD5);
Fri, 23 Jul 2010 03:58:33 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <4C48B1AE.2030408@gmail.com>
Date: Fri, 23 Jul 2010 12:58:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <672CA84A-1850-4B17-922F-AE75D4CF961B@inf-net.nl>
References: <4C48B1AE.2030408@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1081)
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 10:58:17 -0000
Alex, Quick comments: Your example 2001:1::/24 and 2001:2::/24 share a common prefix. Better use 2001:1::/32 and 2001:2::/32 or longer, e.g. /64. On your presso: I would not use same ssid on APs in all vehicles. (slide 2, essid: "V3"). And I dislike the address spoofing mode, suggested in slide 4. So it so +1 on others remarks. Teco. Op 22 jul 2010, om 23:01 heeft Alexandru Petrescu het volgende geschreven: > Addressing model we use, pdf 300Kb: > > http://dl.free.fr/m95j1Km7a > (the username is left empty and password is 'password', without > quotes. File stays there for 30 days.) > > Teco asked whether my draft contains an addressing model... true - it doesn't show so obviously > (http://tools.ietf.org/html/draft-petrescu-autoconf-ra-based-routing-00). > > I said that there is an addressing model in this figure of the draft: >> egress| |egress >> ---- ---- ---- ---- ---- ---- >> | LFN| |LFN | | MR | | MR | |LFN | |LFN | >> ---- ---- ---- ---- ---- ---- >> | | ingress| |ingress | | >> --------------------- --------------------- >> 2001:1::/24 2001:2::/24 > > ThomasC and Chris also expressed doubts with respect to LFN--MR--MR--LFN > topology and link-local addresses; let me explain further. > > We are using this addressing model on several moving networks. See the pdf at the beginning of this email. They show MR-to-MR with a single addressing scheme, then with a double addressing scheme; (double is necessary for our plan.) > > And then a slide shows MR-to-MR-to-MR addressing model. > > There are some scalability remarks and a route propagation model (pencil > and paper). > > The mechanism has been prototyped and demoed since about one year now, > on three Mobile Routers and a bunch of LFNs, which shows it may work. We > have great plans for demoing on vehicles. > > This is an addressing model we consider strongly. It needs later to > auto-configure some prefixes, because currently MNPs are pre-configured > in each moving network (this is the case in some deployments). > > This addressing model is important to us, and uses link-local addresses. > > Alex > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf
- [Autoconf] Another addressing model for AUTOCONF Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Dearlove, Christopher (UK)
- Re: [Autoconf] Another addressing model for AUTOC… Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Thomas Heide Clausen
- Re: [Autoconf] Another addressing model for AUTOC… Teco Boot
- Re: [Autoconf] Another addressing model for AUTOC… Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Ulrich Herberg
- Re: [Autoconf] Another addressing model for AUTOC… Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Teco Boot
- Re: [Autoconf] Another addressing model for AUTOC… Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Teco Boot
- Re: [Autoconf] Another addressing model for AUTOC… Alexandru Petrescu
- Re: [Autoconf] Another addressing model for AUTOC… Henning Rogge
- Re: [Autoconf] Another addressing model for AUTOC… Teco Boot