Re: [Autoconf] Multicast confusion between MANET Arch and AUTOCONFProblem Statement
Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr> Tue, 20 November 2007 17:42 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 1IuX6z-0002tf-JF; Tue, 20 Nov 2007 12:42:13 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IuX6y-0002rq-Pp for autoconf-confirm+ok@megatron.ietf.org; Tue, 20 Nov 2007 12:42:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuX6y-0002rc-FP for autoconf@ietf.org; Tue, 20 Nov 2007 12:42:12 -0500
Received: from mail4-relais-sop.national.inria.fr ([192.134.164.105]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuX6u-0001OI-Pw for autoconf@ietf.org; Tue, 20 Nov 2007 12:42:12 -0500
X-IronPort-AV: E=Sophos;i="4.21,442,1188770400"; d="scan'208";a="19507028"
Received: from z0213.pia.fu-berlin.de (HELO BoolfightMaN-Laptop.local) ([87.77.2.19]) by mail4-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Nov 2007 18:42:07 +0100
Message-ID: <47431C6F.5090809@inria.fr>
Date: Tue, 20 Nov 2007 18:42:07 +0100
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: autoconf@ietf.org
Subject: Re: [Autoconf] Multicast confusion between MANET Arch and AUTOCONFProblem Statement
References: <4742FB0D.40208@gmail.com> <7877C5C0B5CC894AB26113CF06CF88631EA662@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <7877C5C0B5CC894AB26113CF06CF88631EA662@ms-dt01thalia.tsn.tno.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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 agree with Ronald. If there was already an easy definition of what is a "MANET link" then the architecture document would not be needed, would it? Emmanuel Velt, R. (Ronald) in 't a écrit : > 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 > > _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf
- [Autoconf] Multicast confusion between MANET Arch… Alexandru Petrescu
- RE: [Autoconf] Multicast confusion between MANET … Teco Boot
- RE: [Autoconf] Multicast confusion between MANET … Velt, R. (Ronald) in 't
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- RE: [Autoconf] Multicast confusion between MANET … Teco Boot
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- RE: [Autoconf] Multicast confusion between MANET … Teco Boot
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- RE: [Autoconf] Multicast confusion between MANET … Teco Boot
- Re: [Autoconf] Multicast confusion between MANET … Emmanuel Baccelli
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- RE: [Autoconf] Multicast confusion between MANET … Teco Boot
- Re: [Autoconf] Multicast confusion between MANET … Alexandru Petrescu
- Re: [Autoconf] Multicast confusion between MANET … Emmanuel Baccelli
- RE: [Autoconf] Multicast confusion between MANET … Teco Boot