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

"Teco Boot" <teco@inf-net.nl> Tue, 20 November 2007 15:40 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 1IuVDS-00065D-HC; Tue, 20 Nov 2007 10:40:46 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IuVDR-000658-Rd for autoconf-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 10:40:45 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuVDR-00064m-Gw for autoconf@ietf.org; Tue, 20 Nov 2007 10:40:45 -0500
Received: from hpsmtp-eml19.kpnxchange.com ([213.75.38.84]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuVDO-0006bl-Lu for autoconf@ietf.org; Tue, 20 Nov 2007 10:40:43 -0500
Received: from hpsmtp-eml08.kpnxchange.com ([213.75.38.108]) by hpsmtp-eml19.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Nov 2007 16:40:41 +0100
Received: from M90Teco ([86.83.9.22]) by hpsmtp-eml08.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Nov 2007 16:40:27 +0100
From: Teco Boot <teco@inf-net.nl>
To: 'Alexandru Petrescu' <alexandru.petrescu@gmail.com>, autoconf@ietf.org
References: <4742FB0D.40208@gmail.com>
In-Reply-To: <4742FB0D.40208@gmail.com>
Subject: RE: [Autoconf] Multicast confusion between MANET Arch and AUTOCONF Problem Statement
Date: Tue, 20 Nov 2007 16:40:22 +0100
Message-ID: <00b701c82b8b$a9a524c0$fcef6e40$@nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcgriOIp7D/VtzBvT9uFen2G0WRmSgAAX4DA
Content-Language: nl
X-OriginalArrivalTime: 20 Nov 2007 15:40:27.0317 (UTC) FILETIME=[AC6A8650:01C82B8B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc:
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 the confusion is related with having two models, e.g. 802.11 BSS/ESS
and IBSS. BSS/ESS has coordination function and the IP subnet model works
quite well. IBSS is also called ad-hoc mode.

With IBSS, fully mesh is not guaranteed. Here we use the MANET protocols for
end-to-end connectivity.

Now, the MANET protocols are evolved and can be used to connect nodes on
different segments, like classical IP routing protocols.

Maybe the two documents are describing the IBSS / ad-hoc mode. I agree on
adding text that there is a need for ad-hoc networking for the other mode
also. 
Just look at your desk and see the need for this;-)

Teco.


> -----Oorspronkelijk bericht-----
> Van: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]
> Verzonden: dinsdag 20 november 2007 16:20
> Aan: autoconf@ietf.org
> Onderwerp: [Autoconf] Multicast confusion between MANET Arch and
> AUTOCONF Problem Statement
> 
> 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



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