IETF Logo Mail Archive

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

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvzUl-0003k8-E7; Thu, 29 Jun 2006 12:35:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvzUk-0003k3-CU for manet-dt@ietf.org; Thu, 29 Jun 2006 12:35:58 -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 1FvzUj-00068a-4B for manet-dt@ietf.org; Thu, 29 Jun 2006 12:35:58 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id k5TGZfr8005094; Thu, 29 Jun 2006 09:35:42 -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 k5TGZsw01031; Thu, 29 Jun 2006 09:35:54 -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); Thu, 29 Jun 2006 09:35:52 -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:35:52 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1017740D3@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE604@glkms0008>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Manet-dt] IANA Port & Multicast Addresses
Thread-Index: Acabi86dDiVmOcRhTwqZo1o7FNS2ggAAEsPAAAMv+nA=
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "Ian Chakeres" <ian.chakeres@gmail.com>
X-OriginalArrivalTime: 29 Jun 2006 16:35:52.0681 (UTC) FILETIME=[163A0D90:01C69B9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: manet-dt@ietf.org
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, is your opinion we should define only one link-local multicast
>> address at this time?
>
> I think we should find out what people want and submit
> whatever there's a definite need for (not a hypothetical
> maybe in the future case). I only can see a need for
> all link-local neighbour routers in terms of what the WG
> is chartered to do. If someone else has such a need (an
> aspect of SMF or DYMO I've overlooked for example) then
> bring that on too, but if not, not.

I would also like to see at least a site-scoped "All MANET Routers"
address to go with the link-local one, i.e., as for the "All Routers"
multicast address in IPv6. An immediate use-case is for multicast
discovery of Internet gateways that are within the connected MANET
but multiple L3 hops away.

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