RE: [Manet-dt] Revivied discussion on MANET multicast addresses

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 16 May 2006 23:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg9FV-0007GY-H2; Tue, 16 May 2006 19:46:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg9FU-0007GO-9f for manet-dt@ietf.org; Tue, 16 May 2006 19:46:44 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg9FQ-0007r3-Sy for manet-dt@ietf.org; Tue, 16 May 2006 19:46:44 -0400
Received: from blv-av-01.boeing.com ([192.42.227.216]) by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id QAA11234; Tue, 16 May 2006 16:46:37 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k4GNkbr26464; Tue, 16 May 2006 16:46:37 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 May 2006 16:46:37 -0700
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: [Manet-dt] Revivied discussion on MANET multicast addresses
Date: Tue, 16 May 2006 16:46:36 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1818C26@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <374005f30605151342j167ddc15oaaee96369b65b09d@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Manet-dt] Revivied discussion on MANET multicast addresses
Thread-Index: AcZ4ZtveTYnxbNjzS/GIS0c+SMzxxQA2UVlQ
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Ian Chakeres" <ian.chakeres@gmail.com>, <manet-dt@ietf.org>
X-OriginalArrivalTime: 16 May 2006 23:46:37.0123 (UTC) FILETIME=[F889F130:01C67942]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc:
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=subscribe>
Errors-To: manet-dt-bounces@ietf.org

Ian, 

> Now, I'd like to ask about creating a global ALL_MANET_ROUTERS or a
> range of global addresses that are used for dissemination of packets
> within the MANET between MANET Routers.
>
> How do people feel about a global ALL_MANET_ROUTERS or a range of
> global multicast addresses for us within a MANET?

To me, this would suggest a "site-local" scope for ALL_MANET_ROUTERS
if one considers an entire connected MANET as a "site". The IPv6
addressing architecture defines a site-local scope for multicast
(see: RFC4291, Section 2.7) and there is in fact an 'All Routers'
site-local multicast address already assigned in:

http://www.iana.org/assignments/ipv6-multicast-addresses

Unfortunately, things don't seem quite so clear-cut in IPv4.
(RFC3171, Section 3) seems to indicate that assignments
from the local network control block (224.0.0/24) must not
be forwarded at all (i.e., they are of link-local scope),
while assignments from other blocks appear to be of global
scope. I don't know if there is a way to allocate a
local/global-scoped IPv4 multicast and specify that it
is actually to be treated as site-local?

Fred
fred.l.templin@boeing.com  

_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt

_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt