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

"Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> Thu, 29 June 2006 16:20 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvzFS-0003Vr-JY; Thu, 29 Jun 2006 12:20:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvzFR-0003Vm-QX for manet-dt@ietf.org; Thu, 29 Jun 2006 12:20:09 -0400
Received: from smtp1.bae.co.uk ([20.133.0.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvzFQ-00057j-Em for manet-dt@ietf.org; Thu, 29 Jun 2006 12:20:09 -0400
Received: from ngbaux (ngbaux.msd.bae.co.uk [141.245.68.234]) by smtp1.bae.co.uk (Switch-3.1.9/Switch-3.1.9) with ESMTP id k5TGJuVC026921 for <manet-dt@ietf.org>; Thu, 29 Jun 2006 17:20:06 +0100 (BST)
Received: from glkas0002.GREENLNK.NET ([10.15.184.52]) by ngbaux.net.bae.co.uk (PMDF V5.2-33 #44998) with ESMTP id <0J1M00CSSQUFF0@ngbaux.net.bae.co.uk> for manet-dt@ietf.org; Thu, 29 Jun 2006 17:23:03 +0100 (BST)
Received: from glkms0002.GREENLNK.NET ([10.15.184.2]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Thu, 29 Jun 2006 16:07:47 +0100
Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0002.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Thu, 29 Jun 2006 16:07:42 +0100
Date: Thu, 29 Jun 2006 16:07:42 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: RE: [Manet-dt] IANA Port & Multicast Addresses
To: Ian Chakeres <ian.chakeres@gmail.com>
Message-id: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE604@glkms0008>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6556.0
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable
Thread-Topic: [Manet-dt] IANA Port & Multicast Addresses
Thread-Index: Acabi86dDiVmOcRhTwqZo1o7FNS2ggAAEsPA
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-OriginalArrivalTime: 29 Jun 2006 15:07:42.0970 (UTC) FILETIME=[C55035A0:01C69B8D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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.

> Regarding 3 = Port
> The document says all interoperable implementations use the MANET
> port. If you chose to run OLSRv2 on another port, it wouldn't be
> considered interoperable. Otherwise, I don't see an issue with running
> a protocol on another port.

At the moment I don't see any meaning to, for example,
running OLSRv2 and DYMO on the same port, and doing
so introduces distinct complications. Again I'm of
the view of asking for what's needed, no more, no less.
I don't say there isn't a possibility here, but we
should first discuss the architectures and the nasty
questions that arise (I have several, here's one just
for starters - what about multi-message packets, and
who gets the packet header?) and if we have a need,
then ask. Until then, don't.


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

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