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

"Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl> Tue, 20 November 2007 15:49 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 1IuVMB-00005S-5G; Tue, 20 Nov 2007 10:49:47 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IuVMA-00005N-5a for autoconf-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 10:49:46 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuVM9-00005F-PP for autoconf@ietf.org; Tue, 20 Nov 2007 10:49:45 -0500
Received: from mail92.messagelabs.com ([194.106.220.51]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IuVM9-0006qv-6y for autoconf@ietf.org; Tue, 20 Nov 2007 10:49:45 -0500
X-VirusChecked: Checked
X-Env-Sender: Ronald.intVelt@tno.nl
X-Msg-Ref: server-6.tower-92.messagelabs.com!1195573743!32010517!1
X-StarScan-Version: 5.5.12.14.2; banners=tno.nl,-,-
X-Originating-IP: [134.221.2.2]
Received: (qmail 31439 invoked from network); 20 Nov 2007 15:49:03 -0000
Received: from zeus.tno.nl (HELO zeus.tno.nl) (134.221.2.2) by server-6.tower-92.messagelabs.com with SMTP; 20 Nov 2007 15:49:03 -0000
Received: from ms-dt01thalia.tsn.tno.nl (ms-dt01thalia.tno.nl [134.221.225.157]) by zeus.tno.nl (8.11.7p1+Sun/8.11.7) with ESMTP id lAKFn3002529 for <autoconf@ietf.org>; Tue, 20 Nov 2007 16:49:03 +0100 (MET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Autoconf] Multicast confusion between MANET Arch and AUTOCONFProblem Statement
Date: Tue, 20 Nov 2007 16:49:02 +0100
Message-ID: <7877C5C0B5CC894AB26113CF06CF88631EA662@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <4742FB0D.40208@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Autoconf] Multicast confusion between MANET Arch and AUTOCONFProblem Statement
thread-index: AcgriNgeSfACGnF1RfW0m3kQw6vN8gAApArg
References: <4742FB0D.40208@gmail.com>
From: "Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl>
To: autoconf@ietf.org
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
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

Hi Alex, 

> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com] 
> Sent: dinsdag 20 november 2007 16:20
> To: autoconf@ietf.org
> Subject: [Autoconf] Multicast confusion between MANET Arch 
> and AUTOCONFProblem 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.

"link" versus "subnetwork" are distinct notions, aren't they? What is
left of a "subnetwork" in an environment where \128 (\32 for IPv4)
prefixes are configured on MANET interfaces? If your local interface is
the only one in the subnet, then all interfaces in the subnet are
trivially reachable :-) "Link" is something else...

> 
> [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.
>

No, not all interfaces of all MANET routers. Just those of the
*neighbo(u)ring* MANET routers. See MANET architecture for a definition
of neighbo(u)r.
 
> 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

Just my 2 cents,
Ronald


This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html


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