By Topic

Comparing radio-to-router interface implementations on experimental CoTs and open source routers

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

7 Author(s)
Bow-Nan Cheng ; Airborne Networks Group MIT Lincoln Laboratory, Lexington, MA ; Randy Charland ; Paul Christensen ; Andrea Coyle
more authors

In highly dynamic wireless environments, link metrics such as link quality, availability, and others have become increasingly important to enable smart multi-hop routing decisions. In recent years, a number of radio-to-router interface (R2RI) protocols such as Point-to-Point over Ethernet RFC5578, Dynamic Link Exchange Protocol (DLEP), and Radio-Router Control Protocol (R2CP) have emerged to address the need to have a common set of link metrics exposed from the radio to the router to enhance multi-hop routing decisions. To fully evaluate R2RI functionality and specifications, differing implementations of both radio/client and router/server-side R2RI protocols must be prototyped and tested. In this paper, we present comparison tests of each of the three (3) radio-to-router interfaces with two (2) router/server-side R2RI experimental/beta R2RI implementations: one on a commercial Cisco router, and one on an open source Quagga platform. The goal of the comparison is not necessarily to provide a holistic performance comparison (as much of the code is experimental), but to highlight implementation differences and potential issues. In many cases, issues are already resolved in future releases.1

Published in:

MILCOM 2012 - 2012 IEEE Military Communications Conference

Date of Conference:

Oct. 29 2012-Nov. 1 2012