RE: [Manet-dt] Link local Multicast Address - MANET Routers

"Joe Macker" <joseph.macker@nrl.navy.mil> Sat, 22 April 2006 17:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FXLTd-0003nL-3l; Sat, 22 Apr 2006 13:00:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FXLTb-0003n7-KT for manet-dt@ietf.org; Sat, 22 Apr 2006 13:00:55 -0400
Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FXLTa-0002DQ-9i for manet-dt@ietf.org; Sat, 22 Apr 2006 13:00:55 -0400
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id k3MH0rSZ012954; Sat, 22 Apr 2006 13:00:53 -0400 (EDT)
Received: (from SEXTANT [132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.11.41) with SMTP id M2006042213005207053 ; Sat, 22 Apr 2006 13:00:52 -0400
From: "Joe Macker" <joseph.macker@nrl.navy.mil>
To: "'Ian Chakeres'" <ian.chakeres@gmail.com>, "'Brian Haberman'" <brian@innovationslab.net>
Subject: RE: [Manet-dt] Link local Multicast Address - MANET Routers
Date: Sat, 22 Apr 2006 13:00:50 -0400
Message-ID: <03fd01c6662e$4ebd85d0$165cfa84@SEXTANT>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcZjBrhSiCrpBoLaQ0emTmUb5TPXtwDJnajQ
In-Reply-To: <374005f30604180939p5f30b8a2n52d439bb9712c40c@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
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

I am on vacation but I will also chime in.
I think we should look at common issues across routing protocols.

Plenty of  material written already... plenty of issues.
New protocols have been spec'd to use AH/ESP. This is not a panacea.

See
http://www.rpsec.org/
for some issues and presentations.

>-----Original Message-----
>From: Ian Chakeres [mailto:ian.chakeres@gmail.com] 
>Sent: Tuesday, April 18, 2006 12:40 PM
>To: Brian Haberman
>Cc: manet-dt@ietf.org
>Subject: Re: [Manet-dt] Link local Multicast Address - MANET Routers
>
>Comments inline.
>
>On 4/18/06, Brian Haberman <brian@innovationslab.net> wrote:
>> In what context would this common address be used?
>
>The common address will be used for link local MANET routing 
>protocol packets.
>
>In NHD the address will be used for HELLO messages - all 
>messages In OLSRv2 it will be used for TC messages - all 
>messages In DYMO it will be used for RREQ, RREP, & RERR 
>messages - all messages
>
>> Do we expect MANETs to exist that run multiple routing protocols?
>
>Given the common packet format, and soon to be common 
>neighborhood discovery, I think multiple MANET routing 
>protocol components may be run together in the future.
>
>> If so, the filtering now has to be done above the MAC 
>filters (i.e. on 
>> port or protocol numbers) which will affect power consumption.
>
>Yes, but using a different multicast address for each protocol 
>will require that each protocol's messages be carried in 
>separate packets.
>The consequence of carrying each protocols messages in their 
>own IP packets can increase wireless media access significantly.
>
>> What about security issues of sending packets that are not 
>meant for a 
>> subset of routers, but are received by them due to the 
>shared address?
>
>I do not see this as an issue to be addressed by the base 
>MANET protocols.
>
>We are discussing authentication of routing packets for the base spec.
>
>> In short, I would like to see a description of how this address will 
>> be used before I make any judgment.
>
>Does the discussion above help?
>
>Ian
>
>Note - this address would be very similar to OSPF (RFC 2328) 
>AllSPFRouters
>
>o   Use of IP multicast.  Some OSPF messages are multicast, when
>        sent over broadcast networks.  Two distinct IP multicast
>        addresses are used.  Packets sent to these multicast addresses
>        should never be forwarded; they are meant to travel a 
>single hop
>        only.  To ensure that these packets will not travel multiple
>        hops, their IP TTL must be set to 1.
>
>        AllSPFRouters
>            This multicast address has been assigned the value
>            224.0.0.5.  All routers running OSPF should be prepared to
>            receive packets sent to this address.  Hello packets are
>            always sent to this destination.  Also, certain OSPF
>            protocol packets are sent to this address during the
>            flooding procedure.
>
>  AllDRouters
>            This multicast address has been assigned the value
>            224.0.0.6.  Both the Designated Router and Backup 
>Designated
>            Router must be prepared to receive packets destined to this
>            address.  Certain OSPF protocol packets are sent to this
>            address during the flooding procedure.
>
>> Regards,
>> Brian
>>
>> On Apr 15, 2006, at 18:05, Ian Chakeres wrote:
>>
>> > Now that we have a common packet building block, and will 
>soon have 
>> > a common neighborhood discovery building block, I think it 
>is pretty 
>> > natural to use a common multicast address for reaching link-local 
>> > MANET routers. Please reply if you support this common multicast 
>> > address being allocated.
>> >
>> > If I receive support I will start moving on this.
>> >
>> > Ian Chakeres
>> >
>> > _______________________________________________
>> > Manet-dt mailing list
>> > Manet-dt@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/manet-dt
>>
>>
>> _______________________________________________
>> Manet-dt mailing list
>> Manet-dt@ietf.org
>> https://www1.ietf.org/mailman/listinfo/manet-dt
>>
>>
>>
>>
>
>_______________________________________________
>Manet-dt mailing list
>Manet-dt@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet-dt
>



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