Re: [Autoconf] updated draft on aspects of multi-hop wireless communication

"Teco Boot" <teco@inf-net.nl> Wed, 25 February 2009 08:22 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 A79A43A68E4 for <autoconf@core3.amsl.com>; Wed, 25 Feb 2009 00:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.513
X-Spam-Level:
X-Spam-Status: No, score=-0.513 tagged_above=-999 required=5 tests=[AWL=-0.767, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, MANGLED_PILL=2.3]
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 6xwKzewTyeiw for <autoconf@core3.amsl.com>; Wed, 25 Feb 2009 00:22:28 -0800 (PST)
Received: from hpsmtp-eml20.kpnxchange.com (hpsmtp-eml20.KPNXCHANGE.COM [213.75.38.85]) by core3.amsl.com (Postfix) with ESMTP id 7F36C3A689A for <autoconf@ietf.org>; Wed, 25 Feb 2009 00:22:28 -0800 (PST)
Received: from cpsmtp-eml102.kpnxchange.com ([213.75.84.102]) by hpsmtp-eml20.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 25 Feb 2009 09:22:47 +0100
Received: from M90Teco ([86.83.9.22]) by cpsmtp-eml102.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 25 Feb 2009 09:22:47 +0100
From: "Teco Boot" <teco@inf-net.nl>
To: "'Thomas Heide Clausen'" <ietf@thomasclausen.org>, "'Charles E. Perkins'" <charles.perkins@earthlink.net>
References: <be8c8d780902230203k5f0ffb38m97d817aff9d95554@mail.gmail.com> <49A31B60.9050604@gmail.com> <49A31CD5.4090204@earthlink.net> <532BA0E9-FBFD-4022-88AF-BB0D5108FF4D@thomasclausen.org>
In-Reply-To: <532BA0E9-FBFD-4022-88AF-BB0D5108FF4D@thomasclausen.org>
Date: Wed, 25 Feb 2009 09:22:41 +0100
Message-ID: <002c01c99722$3a526390$aef72ab0$@nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmWDWbJWKEUV20cT+qMyIZTiSHZywBEkM2Q
Content-Language: nl
X-OriginalArrivalTime: 25 Feb 2009 08:22:47.0130 (UTC) FILETIME=[3D623BA0:01C99722]
Cc: autoconf@ietf.org, 'Emmanuel Baccelli' <Emmanuel.Baccelli@inria.fr>
Subject: Re: [Autoconf] updated draft on aspects of multi-hop wireless communication
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, 25 Feb 2009 08:22:29 -0000

Inline.

|-----Oorspronkelijk bericht-----
|Van: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] Namens
|Thomas Heide Clausen
|Verzonden: dinsdag 24 februari 2009 0:21
|Aan: Charles E. Perkins
|CC: autoconf@ietf.org; Emmanuel Baccelli
|Onderwerp: Re: [Autoconf] updated draft on aspects of multi-hop wireless
|communication
|
|Hello Alex,
|
|To second Charlie here: in MANETs, routers:
|
|	o	ALWAYS have one MANET interface.
|	o	OFTEN they have other (non-MANET) interfaces
|	o	OCCASIONALLY have more than one MANET interface

I think the definition is still not clear.
Is it a requirement for a MANET Router to forward packets?
What is a MANET interface ? (I think I know, but I refer to the endless
discussion in [Autoconf])
Is the MANET a complete set of nodes, including attached hosts and
"classical routers"?

I think the term MANET is quite abstract and attempts to come up with strict
definitions tend to fail. For specifying protocols, we can come up with
strict definitions. We could say:
An OLSR Router:
 o   ALWAYS have one OLSR interface;
 o   OFTEN they have other (non-OLSR) interfaces;
 o   OCCASIONALLY have more than one OLSR interface.



|I.e. it is quite common for traffic to be forwarded over the same
|interface as the one on which it was received.

The attribute that traffic may be forwarded over the same interface as the
one on which it was received is not specific to MANET at all. Think of WLAN
AP, DSL/cable concentrators, FR/ATM/ISDN, dual-hop satcom etc. Sometimes we
use logical interfaces for links, sometimes we don't. Using logical
interfaces introduce problems utilizing layer-2 broadcast for IP broadcast /
multicast.
Please note that I do not suggest having detailed discussions on layer-2
technologies itself.


Teco.





|Thomas
|
|ps: and for the record, AFAIK all MANET wg routing protocols support
|all the situations listed above, i.e. a MANET router with a single or
|with multiple MANET interfaces and with or without other non-MANET
|interfaces.
|
|On 23Feb , 2009, at 23:01 , Charles E. Perkins wrote:
|
|>
|> Hello Alex,
|>
|> On this point I disagree.  I think it is better to show the
|> routers with a single network interface -- which is what
|> they have in real life.  This is also the reason that techniques
|> like split horizon aren't appropriate.
|>
|> Regards,
|> Charlie P.
|>
|>
|> Alexandru Petrescu wrote:
|>> Emmanuel, AUTOCONFers,
|>>
|>> Just a short clarifying point: I think it would be clarifying to
|>> illustrate the routers to have two interfaces.  Routers with only one
|>> interface aren't very typical.
|>>
|>> Just a note,
|>>
|>> Alex
|>>
|>> Emmanuel Baccelli a écrit :
|>>> Hi all,
|>>>
|>>>
|>>> following the fruitful discussions about initial version of the
|>>> document, here is an update to the draft describing aspects of
|>>> multi-hop wireless communication:
|>>>
|>>> http://www.ietf.org/internet-drafts/draft-baccelli-multi-hop-
|>>> wireless-communication-01.txt
|>>>
|>>>
|>>>
|>>> Again, the goal of this document is to identify a consensus about
|>>> this topic, and then use this to move on quicker with the rest of
|>>> the
|>>> work...
|>>>
|>>> Please review it, and provide feedback as soon as possible.
|>>>
|>>>
|>>> Cheers
|>>>
|>>> Emmanuel
|>>>
|>>>
|>>> --------------------------------------------------------------------
|>>> ----
|>>>
|>>>
|>>> _______________________________________________ Autoconf mailing
|>>> list
|>>>  Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf
|>>
|>> _______________________________________________
|>> Autoconf mailing list
|>> Autoconf@ietf.org
|>> https://www.ietf.org/mailman/listinfo/autoconf
|>>
|>>
|>
|> _______________________________________________
|> Autoconf mailing list
|> Autoconf@ietf.org
|> https://www.ietf.org/mailman/listinfo/autoconf
|
|_______________________________________________
|Autoconf mailing list
|Autoconf@ietf.org
|https://www.ietf.org/mailman/listinfo/autoconf