[Autoconf] Multicast confusion between MANET Arch and AUTOCONF Problem Statement

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 20 November 2007 15:19 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 1IuUtE-0004hs-4x; Tue, 20 Nov 2007 10:19:52 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IuUtD-0004hm-6Z for autoconf-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 10:19:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuUtC-0004hd-Ry for autoconf@ietf.org; Tue, 20 Nov 2007 10:19:50 -0500
Received: from mail153.messagelabs.com ([216.82.253.51]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IuUtC-0005oB-9N for autoconf@ietf.org; Tue, 20 Nov 2007 10:19:50 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-153.messagelabs.com!1195571988!9811821!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.101]
Received: (qmail 13240 invoked from network); 20 Nov 2007 15:19:49 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-5.tower-153.messagelabs.com with SMTP; 20 Nov 2007 15:19:49 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id lAKFJhMZ024582 for <autoconf@ietf.org>; Tue, 20 Nov 2007 08:19:48 -0700 (MST)
Received: from az10vts04.mot.com (az10vts04.mot.com [10.64.251.245]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id lAKFJhb6016073 for <autoconf@ietf.org>; Tue, 20 Nov 2007 09:19:43 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id lAKFJfCx016055 for <autoconf@ietf.org>; Tue, 20 Nov 2007 09:19:42 -0600 (CST)
Message-ID: <4742FB0D.40208@gmail.com>
Date: Tue, 20 Nov 2007 16:19:41 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: autoconf@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 071119-1, 19/11/2007), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [Autoconf] Multicast confusion between MANET Arch and AUTOCONF Problem Statement
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

I think there may be a confusion with respect to the interpretation of
multicast in draft-ietf-autoconf-manetarch-07.txt vs
draft-ietf-autoconf-statement-02.txt.

It seems as if the manetarch accepts that link-layers have a well 
defined multicast behaviour whereas the problem statement doesn't.

autoconf-statement:
> Traditional solutions assume that a broadcast directly reaches every 
> router or host on the subnetwork, whereas this generally is not the 
> case in MANETs (see [2]).

So a broadcasted message (a special case of multicast) will not reach
every host on the MANET subnet.

[2] autoconf-manetarch:
> Link-local Multicast/Broadcast Scope On a MANET interface, a packet
> sent to a link-local multicast or all-ones broadcast address reaches
> the MANET interfaces of neighboring MANET routers...

So it actually does.

I personally think that the autoconf-manetarch definition is more inline
with how I see relationships between link-layer multicast and IP multicast.

Or maybe we could define 'subnet' to be a set of hosts and routers
linked together by the same link-layer technology where a multicast
behaviour is well defined.  Or similar?

What do you think?

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