IETF Logo Mail Archive

RE: [Manet-dt] IANA Port & Multicast Addresses

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 29 June 2006 16:22 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvzHa-0004eP-AK; Thu, 29 Jun 2006 12:22:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvzHY-0004eK-WF for manet-dt@ietf.org; Thu, 29 Jun 2006 12:22:21 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48] helo=slb-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvzHX-0005Ax-FK for manet-dt@ietf.org; Thu, 29 Jun 2006 12:22:20 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id k5TGLutV026345; Thu, 29 Jun 2006 09:21:56 -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 k5TGM8325880; Thu, 29 Jun 2006 11:22:08 -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); Thu, 29 Jun 2006 09:22:00 -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] IANA Port & Multicast Addresses
Date: Thu, 29 Jun 2006 09:21:59 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1017740D2@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE5FF@glkms0008>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Manet-dt] IANA Port & Multicast Addresses
Thread-Index: AcabS23TcWp4K/AiQTi9vmew28NkMgACbDQgABCbuAA=
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "Ian Chakeres" <ian.chakeres@gmail.com>, <manet-dt@ietf.org>
X-OriginalArrivalTime: 29 Jun 2006 16:22:00.0442 (UTC) FILETIME=[262C75A0:01C69B98]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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

Chris,

> First I don't understand the distinction between
> all MANET routers and all MANET nodes. The model
> I have (which I think is shared by RFC 2501) is
> that a node contains a router and may contain hosts.
> So "all MANET nodes" means "all MANET routers" plus
> maybe also delivering to all hosts in the MANET, but
> that's not clear to me.

We have been discussing this internally too. I think the
question is, is it possible to have a node on a MANET
link that is a neighbor of a MANET router but does not
participate in the MANET routing protocol itself? If so,
then it might make sense to have an "All MANET Nodes"
multicast address that is different from "All MANET
Routers". (And if not, why not?)

Fred
fred.l.templin@boeing.com 

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

v2.8.7 | Report a Bug | By Email