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

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg9PN-00035n-GG; Tue, 16 May 2006 19:56:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg9PM-00035i-71 for manet-dt@ietf.org; Tue, 16 May 2006 19:56:56 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg9PK-0008Qi-TE for manet-dt@ietf.org; Tue, 16 May 2006 19:56:56 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6]) by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id QAA18767; Tue, 16 May 2006 16:56:53 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k4GNurG11406; Tue, 16 May 2006 18:56:53 -0500 (CDT)
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:56:49 -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:56:48 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1818C28@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1818C26@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Manet-dt] Revivied discussion on MANET multicast addresses
Thread-Index: AcZ4ZtveTYnxbNjzS/GIS0c+SMzxxQA2UVlQAADigeA=
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:56:49.0642 (UTC) FILETIME=[65A0ECA0:01C67944]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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

> Unfortunately, things don't seem quite so clear-cut in IPv4.

Then again, there is the IPv4 "Administratively Scoped"
multicast block (239.0.0.0/8) and portions of that space
are designated as "Site-Local Scope"; see RFC2365 and:

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

Fred
fred.l.templin@boeing.com

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