Re: [Autoconf] Autoconf addressing model

HyungJin Lim <dream.hjlim@gmail.com> Sun, 01 March 2009 03:05 UTC

Return-Path: <dream.hjlim@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 9F59D3A6B76 for <autoconf@core3.amsl.com>; Sat, 28 Feb 2009 19:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level:
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 H2HMYMggLAgu for <autoconf@core3.amsl.com>; Sat, 28 Feb 2009 19:05:38 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by core3.amsl.com (Postfix) with ESMTP id 695193A67C0 for <autoconf@ietf.org>; Sat, 28 Feb 2009 19:05:38 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id l9so1618478rvb.49 for <autoconf@ietf.org>; Sat, 28 Feb 2009 19:06:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ExDCFjSN2UiIHOB1H+xRws6Lq87Go8dtG0my086EWBM=; b=FWLuvV4fkfHkmjSkbvNGJmLi0/t6n2AT8CYBwRprsuNxdf7lkdtyhPgYs3UvfEykO3 JwyUXdvgLYypAAS5Lms/yolmc6iBOaZX/esnrzsFwqhEZHDBBDKXUK0eg8tSBuJT8e5B cnVb++nv7y/N+TvBmW8IJyJgJSTubyMPv8p8s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ga1sy3OUpmY+dHmAaMHFLfwgyjQ/e++2fzsV59MN868Gkrk4ZE0gTD8IEkeISTcThz 0MyZXXGjSv2bsLXh2u0vWT8Z8ORuZYmY9JyVmwBSJ7qr7PryJJ7w1T5pngOvhCmd6HP5 UfDhPLkWDCUJNkQEcKe96JCAT6WsjO5NfJqQs=
MIME-Version: 1.0
Received: by 10.142.242.8 with SMTP id p8mr2190526wfh.60.1235876762807; Sat, 28 Feb 2009 19:06:02 -0800 (PST)
In-Reply-To: <49A94589.9050203@gmail.com>
References: <499F0BA7.90501@piuha.net> <7E8A76F7-2CE0-463A-8EE8-8877C46B4715@gmail.com> <49A6D436.7020505@gmail.com> <000001c99845$1dc56190$595024b0$@nl> <49A6F125.40400@gmail.com> <1235680887.4585.5.camel@localhost> <002f01c998bf$8f112210$ad336630$@nl> <1235828619.6096.24.camel@localhost> <49A94589.9050203@gmail.com>
Date: Sun, 1 Mar 2009 12:06:02 +0900
Message-ID: <7e8d02d40902281906k3fd36f03ud329c1db2738221e@mail.gmail.com>
From: HyungJin Lim <dream.hjlim@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd32af06eeda6046405fb63
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Autoconf addressing model
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: Sun, 01 Mar 2009 03:05:39 -0000

inline..

2009/2/28, Alexandru Petrescu <alexandru.petrescu@gmail.com>om>:
>
> Carlos Jesús Bernardos Cano a écrit :
> [...]
>
>> It doesn't matter how many ad hoc segments there are. In the following
>>> scenario, the link to Access router G disappeared, Router 3 disappeared
>>> and
>>> a Router4 joined IBSS "adhoc1".
>>>
>>>
>>>
>>>     ---+-------Internet------
>>>        |                            |           +-------+-------+
>>>  |Access Router H|       +-------+-------+                |
>>>              ||Prefix information H          |V                     wifi
>>> "adhoc1"
>>>        |                   <---------------------------v-------->
>>>  <------|--v---------------------->                     |
>>>  |<-|--------------------v-----------------------|--->
>>>        |  |                    |                       |
>>>    +---+--'+               +---'---+               +---'---+
>>>    |Router1|>-------------<|Router2|>-------------<|Router4|
>>>    +---L---+ LL1      LL21 +---L---+ LL22      LL4 +---L---+
>>>        |M1                     |M2                     |M4
>>>        |H1                     |H2                     |H4
>>>
>>>              --------->               --------->
>>>              Prefix information H     Prefix information H
>>>
>>>
>>> Now, Router2 acts as a relay for Router4, so Router4 can reach Router1
>>> and
>>> the Internet. Router1 acts as Border Router for all nodes in the MANET.
>>>
>>>
>> While I think this is also much in linee with my thinking, I think it's
>> better to focus on the simplest cases before.
>>
>
> What are the simplest cases?


   I think we can divided into two category in MANET scenario as follows.

        Category 1
            Scenario 1: "MANET to Internet", in case, depths of nested
routers(NEMO)  is under three levels.
                           This is practical case in real world (i.e.,
most scenarios in real world)
         Scenario 2: "MANET to Internet", depths of nested routers is more
than three levels.
                             (i.e., perhaps disaster situation, etc.. )

       Category 2 (scenario 3)
                           : "Only MANET", in case, the network does not has
a connectivity to Internet.
                             (i.e., peer-to-peer network, etc..)

     Requirement of address model we need is different according with
considered scenario I think.
     Then some scenarios included in category 2 not needs topological
meaningful address.

      Which area is AUTOCONF want to pinpoint ?

      I think AUTOCONF should satisfy requirements between pure MANET, NEMO
and MANEMO
      that can compose of mesh network, although we discussed about the
difference between MANET, NEMO and MANEMO

      Moreover, these networks can has some impacts due to mobility pattern,
wireless coverage and any other situations. AUTOCONF
Addressing model can make a important role to efficient and secure aspects.

     What do you think about my comments ?

   Hyung-Jin, Lim


> Alex
>
> _______________________________________________
> Autoconf mailing list
> Autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/autoconf
>