RE: [manet] Re: MANET definition of a neighbor

"Mullen, John" <jomullen@ad.nmsu.edu> Mon, 08 May 2006 19:48 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBiX-0006mJ-Rn; Mon, 08 May 2006 15:48:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBiW-0006mB-CB for manet@ietf.org; Mon, 08 May 2006 15:48:28 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdBiV-00049C-3p for manet@ietf.org; Mon, 08 May 2006 15:48:28 -0400
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] Re: MANET definition of a neighbor
Date: Mon, 08 May 2006 13:48:33 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF6B6@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4AAlPAEwAAEFvpAAAp3tkAAAIW+QAGdtmkAANZeBsA==
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: DANIEL BYRNE <daniel.byrne@adtran.com>, manet@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc:
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

"Maybe a new stack architecture is needed for MANETS where protocols can
still partition layer specific items yet share cross applicable
information."

I agree, but we may still be able to pull it off without having to mess
up the stack.

John Mullen 


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
 
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com] 
Sent: Sunday, May 07, 2006 12:18 PM
To: Mullen, John; manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

"...That is why I feel a cross-layer approach will win out in the end.
The physical and link layers will have information that is normally
hidden from the routing layer that will be needed to evaluate potential
links, but the MANET protocol will have the job of finding an optimal
network solution."

True, the routing protocol could use information attained by lower
layers.  A mechanism to pass information up the stack is needed, or the
protocol needs to be multi-layer aware. However, the later causes
problems when there are changes in technologies.  Maybe a new stack
architecture is needed for MANETS where protocols can still partition
layer specific items yet share cross applicable information.

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