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

"Ian Chakeres" <ian.chakeres@gmail.com> Fri, 07 July 2006 23:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyzKR-00039D-3V; Fri, 07 Jul 2006 19:01:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyzKQ-000398-4r for manet-dt@ietf.org; Fri, 07 Jul 2006 19:01:42 -0400
Received: from ug-out-1314.google.com ([66.249.92.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyzKO-0002VY-S7 for manet-dt@ietf.org; Fri, 07 Jul 2006 19:01:42 -0400
Received: by ug-out-1314.google.com with SMTP id m3so944419uge for <manet-dt@ietf.org>; Fri, 07 Jul 2006 16:01:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BvyeY74+WWALcySi+Gy7eI5c8Xf2817M44WlU18ykjvow58KTh9T86uyXG+/BwiDV33eGhEydMz5taRFByNHox2eX0EyargQ/5rjomapnAnMJgEAHbnlfc4Ahnt/o8YT+8CqRHr2hRLMGkXEHXCpg0SvktrvsqiUYWKUZJZapPk=
Received: by 10.66.219.11 with SMTP id r11mr2514597ugg; Fri, 07 Jul 2006 16:01:39 -0700 (PDT)
Received: by 10.66.224.14 with HTTP; Fri, 7 Jul 2006 16:01:39 -0700 (PDT)
Message-ID: <374005f30607071601s59799ef9yd71553a866aff129@mail.gmail.com>
Date: Fri, 7 Jul 2006 16:01:39 -0700
From: "Ian Chakeres" <ian.chakeres@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: [Manet-dt] IANA Port & Multicast Addresses
In-Reply-To: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE604@glkms0008>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE604@glkms0008>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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

  Comments inline.

On 6/29/06, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
>
<snip>
> > 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.

I don't see any problem running DYMO and OLSRv2 along side each other
on the same port, thanks to packetbb.

Regarding the IP header - perhaps it should be stated in the packetbb
draft that only messages with the same IP
source/destination/ttl(hoplimit)/etc are allowed to be combined.

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