IETF Logo Mail Archive

Re: [Autoconf] Re: movement scenario

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 04 December 2007 21:58 UTC

Return-path: <autoconf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izfmx-0002Gp-9g; Tue, 04 Dec 2007 16:58:47 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Izfmv-0002Cg-CC for autoconf-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 16:58:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izfmv-0002BT-1i for autoconf@ietf.org; Tue, 04 Dec 2007 16:58:45 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Izfms-0007FC-UK for autoconf@ietf.org; Tue, 04 Dec 2007 16:58:45 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-9.tower-119.messagelabs.com!1196805521!23609539!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 27458 invoked from network); 4 Dec 2007 21:58:42 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102) by server-9.tower-119.messagelabs.com with SMTP; 4 Dec 2007 21:58:42 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id lB4LwfL1023537; Tue, 4 Dec 2007 14:58:41 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id lB4LwdsI019862; Tue, 4 Dec 2007 15:58:40 -0600 (CST)
Received: from [127.0.0.1] (mvp-10-197-20-84.corp.mot.com [10.197.20.84]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id lB4LwZUD019780; Tue, 4 Dec 2007 15:58:37 -0600 (CST)
Message-ID: <4755CD8B.1020700@gmail.com>
Date: Tue, 04 Dec 2007 13:58:35 -0800
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ulrich Herberg <ulrich.herberg@polytechnique.edu>
Subject: Re: [Autoconf] Re: movement scenario
References: <B1CA250F-56DE-4F6E-89D4-E138AF9A4F8C@gmail.com> <7.0.0.16.2.20071202181233.04971348@ie.niigata-u.ac.jp> <475323CF.4080604@gmail.com> <7.0.0.16.2.20071203115230.04bda790@ie.niigata-u.ac.jp> <002301c8355e$639a3e70$2acebb50$@nl> <7.0.0.16.2.20071203125837.049dbf18@ie.niigata-u.ac.jp> <4754AB65.2090800@gmail.com> <7.0.0.16.2.20071204134958.0476dac8@ie.niigata-u.ac.jp> <4754E18D.3080302@gmail.com> <7.0.0.16.2.20071204143038.047a72d0@ie.niigata-u.ac.jp> <25c114b90712040946j47de7a71ve45b50e341ef4dc6@mail.gmail.com>
In-Reply-To: <25c114b90712040946j47de7a71ve45b50e341ef4dc6@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 071204-1, 04/12/2007), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: autoconf@ietf.org
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
Errors-To: autoconf-bounces@ietf.org

Ulrich Herberg wrote:
> Hi,
> 
> I agree with Kenichi. Maybe one could mention different scenarios in 
> the PS, but basically no particular mobility model should be 
> considered in my opinion.

What are the risks of not considering the limits of each entity's
movement?  Do we risk anything?

Or is it just a problem of verbally/writenly communicating the movement
scenario - problem that we could ignore?

> For Alex's concern about comparability, I don't think this should be
>  part of a PS (maybe more in a solution space? or something like 
> draft-bernardos-autoconf-evaluation-considerations ?). The problem of
>  autoconfiguration should be applicable to all mobility patterns to 
> my understanding.

I kind of agree.  I'd say it should apply to a wide range of mobility
patterns.

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www1.ietf.org/mailman/listinfo/autoconf

v2.23.0 | Report a Bug | By Email