| 1 |
<pre>Network Working Group B. Adamson |
| 2 |
Request for Comments: 1677 Naval Research Laboratory |
| 3 |
Category: Informational August 1994 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Tactical Radio Frequency Communication Requirements for IPng</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. This memo |
| 11 |
does not specify an Internet standard of any kind. Distribution of |
| 12 |
this memo is unlimited. |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
This document was submitted to the IETF IPng area in response to <a href="./rfc1550">RFC</a> |
| 17 |
<a href="./rfc1550">1550</a>. Publication of this document does not imply acceptance by the |
| 18 |
IPng area of any ideas expressed within. Comments should be |
| 19 |
submitted to the [email protected] mailing list. |
| 20 |
|
| 21 |
Executive Summary |
| 22 |
|
| 23 |
The U.S. Navy has several efforts exploring the applicability of |
| 24 |
commercial internetworking technology to tactical RF networks. Some |
| 25 |
these include the NATO Communication System Network Interoperability |
| 26 |
(CSNI) project, the Naval Research Laboratory Data/Voice Integration |
| 27 |
Advanced Technology Demonstration (D/V ATD), and the Navy |
| 28 |
Communication Support System (CSS) architecture development. |
| 29 |
|
| 30 |
Critical requirements have been identified for security, mobility, |
| 31 |
real-time data delivery applications, multicast, and quality-of- |
| 32 |
service and policy based routing. Address scaling for Navy |
| 33 |
application of internet technology will include potentially very |
| 34 |
large numbers of local (intra-platform) distributed information and |
| 35 |
weapons systems and a smaller number of nodes requiring global |
| 36 |
connectivity. The flexibility of the current Internet Protocol (IP) |
| 37 |
for supporting widely different communication media should be |
| 38 |
preserved to meet the needs of the highly heterogeneous networks of |
| 39 |
the tactical environment. Compact protocol headers are necessary for |
| 40 |
efficient data transfer on the relatively-low throughput RF systems. |
| 41 |
Mechanisms which can enhance the effectiveness of an internet |
| 42 |
datagram protocol to provide resource reservation, priority, and |
| 43 |
service quality guarantees are also very important. The broadcast |
| 44 |
nature of many RF networks and the need for broad dissemination of |
| 45 |
information to warfighting participants makes multicast the general |
| 46 |
case for information flow in the tactical environment. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Adamson [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
Background |
| 58 |
|
| 59 |
This paper describes requirements for Internet Protocol next |
| 60 |
generation (IPng) candidates with respect to their application to |
| 61 |
military tactical radio frequency (RF) communication networks. The |
| 62 |
foundation for these requirements are experiences in the NATO |
| 63 |
Communication System Network Interoperability (CSNI) project, the |
| 64 |
Naval Research Laboratory Data/Voice Integration Advanced Technology |
| 65 |
Demonstration (D/V ATD), and the Navy Communication Support System |
| 66 |
(CSS) architecture development. |
| 67 |
|
| 68 |
The goal of the CSNI project is to apply internetworking technology |
| 69 |
to facilitate multi-national interoperability for typical military |
| 70 |
communication applications (e.g., electronic messaging, tactical data |
| 71 |
exchange, and digital voice) on typical tactical RF communication |
| 72 |
links and networks. The International Standard Organization (ISO) |
| 73 |
Open Systems Interconnect (OSI) protocol suite, including the |
| 74 |
Connectionless Network Protocol (CLNP), was selected for this project |
| 75 |
for policy reasons. This paper will address design issues |
| 76 |
encountered in meeting the project goals with this particular |
| 77 |
protocol stack. |
| 78 |
|
| 79 |
The D/V ATD is focused on demonstrating a survivable, self- |
| 80 |
configuring, self-recovering RF subnetwork technology capable of |
| 81 |
simultaneously supporting data delivery, including message transfer, |
| 82 |
imagery, and tactical data, and real-time digital voice applications. |
| 83 |
Support for real-time interactive communication applications was |
| 84 |
extended to include a "white board" and other similar applications. |
| 85 |
IP datagram delivery is also planned as part of this demonstration |
| 86 |
system. |
| 87 |
|
| 88 |
The CSS architecture will provide U.S. Navy tactical platforms with a |
| 89 |
broad array of user-transparent voice and data information exchange |
| 90 |
services. This will include support for sharing and management of |
| 91 |
limited platform communication resources among multiple warfighting |
| 92 |
communities. Emphasis is placed on attaining interoperability with |
| 93 |
other military services and foreign allies. Utilization of |
| 94 |
commercial off-the-shelf communications products to take advantage of |
| 95 |
existing economies of scale is important to make any resulting system |
| 96 |
design affordable. It is anticipated that open, voluntary standards, |
| 97 |
and flexible communication protocols, such as IP, will play a key |
| 98 |
role in meeting the goals of this architecture. |
| 99 |
|
| 100 |
Introduction |
| 101 |
|
| 102 |
Before addressing any IPng requirements as applied to tactical RF |
| 103 |
communications, it is necessary to define what this paper means by |
| 104 |
"IPng requirements". To maintain brevity, this paper will focus on |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Adamson [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
criteria related specifically to the design of an OSI model's Layer 3 |
| 114 |
protocol format and a few other areas suggested by <a href="./rfc1550">RFC 1550</a>. There |
| 115 |
are several additional areas of concern in applying internetwork |
| 116 |
protocols to the military tactical RF setting including routing |
| 117 |
protocol design, address assignment, network management, and resource |
| 118 |
management. While these areas are equally important, this paper will |
| 119 |
attempt to satisfy the purpose of <a href="./rfc1550">RFC 1550</a> and address issues more |
| 120 |
directly applicable to selection of an IPng candidate. |
| 121 |
|
| 122 |
Scaling |
| 123 |
|
| 124 |
The projection given in <a href="./rfc1550">RFC 1550</a> that IPng should be able to deal |
| 125 |
with 10 to the 12th nodes is more than adequate in the face of |
| 126 |
military requirements. More important is that it is possible to |
| 127 |
assign addresses efficiently. For example, although a military |
| 128 |
platform may have a relatively small number of nodes with |
| 129 |
requirements to communicate with a larger, global infrastructure, |
| 130 |
there will likely be applications of IPng to management and control |
| 131 |
of distributed systems (e.g., specific radio communications equipment |
| 132 |
and processors, weapons systems, etc.) within the platform. This |
| 133 |
local expansion of address space requirements may not necessarily |
| 134 |
need to be solved by "sheer numbers" of globally-unique addresses but |
| 135 |
perhaps by alternate delimitation of addressing to differentiate |
| 136 |
between globally-unique and locally-unique addressing. The |
| 137 |
advantages of a compact internet address header are clear for |
| 138 |
relatively low capacity RF networks. |
| 139 |
|
| 140 |
Timescale, Transition and Deployment |
| 141 |
|
| 142 |
The U.S. Navy and other services are only recently (the last few |
| 143 |
years) beginning to design and deploy systems utilizing open systems |
| 144 |
internetworking technology. From this point of view, the time scale |
| 145 |
for selection of IPng must be somewhat rapid. Otherwise, two |
| 146 |
transition phases will need to be suffered, 1) the move from unique, |
| 147 |
"stove pipe" systems to open, internetworked (e.g., IP) systems, and |
| 148 |
then 2) a transition from deployed IP-based systems to IPng. In some |
| 149 |
sense, if an IPng is quickly accepted and widely implemented, the |
| 150 |
transition for tactical military systems will be somewhat easier than |
| 151 |
the enterprise Internet where a large investment in current IP |
| 152 |
already exists. However, having said this, the Department of Defense |
| 153 |
as a whole already deploys a large number of IP-capable systems, and |
| 154 |
the issue of transition from IP to IPng remains significant. |
| 155 |
|
| 156 |
Security |
| 157 |
|
| 158 |
As with any military system, information security, including |
| 159 |
confidentiality and authenticity of data, is of paramount importance. |
| 160 |
With regards to IPng, network layer security mechanisms for tactical |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Adamson [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 167 |
|
| 168 |
|
| 169 |
RF networks generally important for authentication purposes, |
| 170 |
including routing protocol authentication, source authentication, and |
| 171 |
user network access control. Concerns for denial of service attacks, |
| 172 |
traffic analysis monitoring, etc., usually dictate that tactical RF |
| 173 |
communication networks provide link layer security mechanisms. |
| 174 |
Compartmentalization and multiple levels of security for different |
| 175 |
users of common communication resources call for additional security |
| 176 |
mechanisms at the transport layer or above. In the typical tactical |
| 177 |
RF environment, network layer confidentiality and, in some cases, |
| 178 |
even authentication becomes redundant with these other security |
| 179 |
mechanisms. |
| 180 |
|
| 181 |
The need for network layer security mechanisms becomes more critical |
| 182 |
when the military utilizes commercial telecommunications systems or |
| 183 |
has tactical systems inter-connected with commercial internets. |
| 184 |
While the Network Encryption Server (NES) works in this role today, |
| 185 |
there is a desire for a more integrated, higher performance solution |
| 186 |
in the future. Thus, to meet the military requirement for |
| 187 |
confidentiality and authentication, an IPng candidate must be capable |
| 188 |
of operating in a secure manner when necessary, but also allow for |
| 189 |
efficient operation on low-throughput RF links when other security |
| 190 |
mechanisms are already in place. |
| 191 |
|
| 192 |
In either of these cases, key management is extremely important. |
| 193 |
Ideally, a common key management system could be used to provide key |
| 194 |
distribution for security mechanisms at any layer from the |
| 195 |
application to the link layer. As a result, it is anticipated, |
| 196 |
however, that key distribution is a function of management, and |
| 197 |
should not dependent upon a particular IPng protocol format. |
| 198 |
|
| 199 |
Mobility |
| 200 |
|
| 201 |
The definition of most tactical systems include mobility in some |
| 202 |
form. Many tactical RF network designs provide means for members to |
| 203 |
join and leave particular RF subnets as their position changes. For |
| 204 |
example, as a platform moves out of the RF line-of-sight (LOS) range, |
| 205 |
it may switch from a typical LOS RF media such as the ultra-high |
| 206 |
frequency (UHF) band to a long-haul RF media such as high frequency |
| 207 |
(HF) or satellite communication (SATCOM). |
| 208 |
|
| 209 |
In some cases, such as the D/V ATD network, the RF subnet will |
| 210 |
perform its own routing and management of this dynamic topology. |
| 211 |
This will be invisible to the internet protocol except for |
| 212 |
(hopefully) subtle changes to some routing metrics (e.g., more or |
| 213 |
less delay to reach a host). In this instance, the RF subnetwork |
| 214 |
protocols serve as a buffer to the internet routing protocols and |
| 215 |
IPng will not need to be too concerned with mobility. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Adamson [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 223 |
|
| 224 |
|
| 225 |
In other cases, however, the platform may make a dramatic change in |
| 226 |
position and require a major change in internet routing. IPng must |
| 227 |
be able to support this situation. It is recognized that an internet |
| 228 |
protocol may not be able to cope with large, rapid changes in |
| 229 |
topology. Efforts will be made to minimize the frequency of this in |
| 230 |
a tactical RF communication architecture, but there are instances |
| 231 |
when a major change in topology is required. |
| 232 |
|
| 233 |
Furthermore, it should be realized that mobility in the tactical |
| 234 |
setting is not limited to individual nodes moving about, but that, in |
| 235 |
some cases, entire subnetworks may be moving. An example of this is |
| 236 |
a Navy ship with multiple LANs on board, moving through the domains |
| 237 |
of different RF networks. In some cases, the RF subnet will be |
| 238 |
moving, as in the case of an aircraft strike force, or Navy |
| 239 |
battlegroup. |
| 240 |
|
| 241 |
Flows and Resource Reservation |
| 242 |
|
| 243 |
The tactical military has very real requirements for multi-media |
| 244 |
services across its shared and inter-connected RF networks. This |
| 245 |
includes applications from digital secure voice integrated with |
| 246 |
applications such as "white boards" and position reporting for |
| 247 |
mission planning purposes to low-latency, high priority tactical data |
| 248 |
messages (target detection, identification, location and heading |
| 249 |
information). Because of the limited capacity of tactical RF |
| 250 |
networks, resource reservation is extremely important to control |
| 251 |
access to these valuable resources. Resource reservation can play a |
| 252 |
role in "congestion avoidance" for these limited resources as well as |
| 253 |
ensuring that quality-of-service data delivery requirements are met |
| 254 |
for multi-media communication. |
| 255 |
|
| 256 |
Note there is more required here than can be met by simple quality- |
| 257 |
of-service (QoS) based path selection and subsequent source-routing |
| 258 |
to get real-time data such as voice delivered. For example, to |
| 259 |
support digital voice in the CSNI project, a call setup and resource |
| 260 |
reservation protocol was designed. It was determined that the QoS |
| 261 |
mechanisms provided by the CLNP specification were not sufficient for |
| 262 |
our voice application path selection. Voice calls could not be |
| 263 |
routed and resources reserved based on any single QoS parameter |
| 264 |
(e.g., delay, capacity, etc.) alone. Some RF subnets in the CSNI |
| 265 |
test bed simply did not have the capability to support voice calls. |
| 266 |
To perform resource reservation for the voice calls, the CLNP cost |
| 267 |
metric was "hijacked" as essentially a Type of Service identifier to |
| 268 |
let the router know which datagrams were associated with a voice |
| 269 |
call. The cost metric, concatenated with the source and destination |
| 270 |
addresses were used to form a unique identifier for voice calls in |
| 271 |
the router and subnet state tables. Voice call paths were to be |
| 272 |
selected by the router (i.e. the "cost" metric was calculated) as a |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Adamson [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 279 |
|
| 280 |
|
| 281 |
rule-based function of each subnet's capability to support voice, its |
| 282 |
delay, and its capacity. While source routing provided a possible |
| 283 |
means for voice datagrams to find their way from router to router, |
| 284 |
the network address alone was not explicit enough to direct the data |
| 285 |
to the correct interface, particularly in cases where there were |
| 286 |
multiple communication media interconnecting two routers along the |
| 287 |
path. Fortunately, exclusive use of the cost QoS indicator for voice |
| 288 |
in CSNI was able to serve as a flag to the router for packets |
| 289 |
requiring special handling. |
| 290 |
|
| 291 |
While a simple Type of Service field as part of an IPng protocol can |
| 292 |
serve this purpose where there are a limited number of well known |
| 293 |
services (CSNI has a single special service - 2400 bps digital |
| 294 |
voice), a more general technique such as RSVP's Flow Specification |
| 295 |
can support a larger set of such services. And a field, such as the |
| 296 |
one sometimes referred to as a Flow Identification (Flow ID), can |
| 297 |
play an important role in facilitating inter-networked data |
| 298 |
communication over these limited capacity networks. |
| 299 |
|
| 300 |
For example, the D/V ATD RF sub-network provides support for both |
| 301 |
connectionless datagram delivery and virtual circuit connectivity. |
| 302 |
To utilize this capability, an IPng could establish a virtual circuit |
| 303 |
connection across this RF subnetwork which meets the requirements of |
| 304 |
an RSVP Flow Specification. By creating an association between a |
| 305 |
particular Flow ID and the subnetwork header identifying the |
| 306 |
established virtual circuit, an IPng gateway could forward data |
| 307 |
across the low-capacity while removing most, if not all, of the IPng |
| 308 |
packet header information. The receiving gateway could re- construct |
| 309 |
these fields based on the Flow Specification of the particular Flow |
| 310 |
ID/virtual circuit association. |
| 311 |
|
| 312 |
In summary, a field such as a Flow Identification can serve at least |
| 313 |
two important purposes: |
| 314 |
|
| 315 |
1) It can be used by routers (or gateways) to identify |
| 316 |
packets with special, or pre-arranged delivery |
| 317 |
requirements. It is important to realize that it may |
| 318 |
not always be possible to "peek" at internet packet |
| 319 |
content for this information if certain security |
| 320 |
considerations are met (e.g., an encrypted transport |
| 321 |
layer). |
| 322 |
|
| 323 |
2) It can aid mapping datagram services to different |
| 324 |
types of communication services provided by |
| 325 |
specialized subnet/data link layer protocols. |
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Adamson [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 335 |
|
| 336 |
|
| 337 |
Multicast |
| 338 |
|
| 339 |
Tactical military communication has a very clear requirement for |
| 340 |
multicast. Efficient dissemination of information to distributed |
| 341 |
warfighting participants can be the key to success in a battle. In |
| 342 |
modern warfare, this information includes imagery, the "tactical |
| 343 |
scene" via tactical data messages, messaging information, and real- |
| 344 |
time interactive applications such as digital secure voice. Many of |
| 345 |
the tactical RF communication media are broadcast by nature, and |
| 346 |
multicast routing can take advantage of this topology to distribute |
| 347 |
critical data to a large number of participants. The throughput |
| 348 |
limitations imposed by these RF media and the physics of potential |
| 349 |
electronic counter measures (ECM) dictate that this information be |
| 350 |
distributed efficiently. A multicast architecture is the general |
| 351 |
case for information flow in a tactical internetwork. |
| 352 |
|
| 353 |
Quality of Service and Policy-Based Routing |
| 354 |
|
| 355 |
Quality of service and policy based routing are of particular |
| 356 |
importance in a tactical environment with limited communication |
| 357 |
resources, limited bandwidth, and possible degradation and/or denial |
| 358 |
of service. Priority is a very important criteria in the tactical |
| 359 |
setting. In the tactical RF world of limited resources (limited |
| 360 |
bandwidth, radio assets, etc.) there will be instances when there is |
| 361 |
not sufficient capacity to provide all users with their perception of |
| 362 |
required communication capability. It is extremely important for a |
| 363 |
shared, automated communication system to delegate capacity higher |
| 364 |
priority users. Unlike the commercial world, where everyone has a |
| 365 |
more equal footing, it is possible in the military environment to |
| 366 |
assign priority to users or even individual datagrams. An example of |
| 367 |
this is the tactical data exchange. Tactical data messages are |
| 368 |
generally single-datagram messages containing information on the |
| 369 |
location, bearing, identification, etc., of entities detected by |
| 370 |
sensors. In CSNI, tactical data messages were assigned 15 different |
| 371 |
levels of CLNP priority. This ensured that important messages, such |
| 372 |
as a rapidly approaching enemy missile's trajectory, were given |
| 373 |
priority over less important messages, such as a friendly, slow- |
| 374 |
moving tanker's heading. |
| 375 |
|
| 376 |
Applicability |
| 377 |
|
| 378 |
There will be a significant amount of applicability to tactical RF |
| 379 |
networks. The current IP and CLNP protocols are being given |
| 380 |
considerable attention in the tactical RF community as a means to |
| 381 |
provide communication interoperability across a large set of |
| 382 |
heterogeneous RF networks in use by different services and countries. |
| 383 |
The applicability of IPng can only improve with the inclusion of |
| 384 |
features critical to supporting QoS and Policy based routing, |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Adamson [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 391 |
|
| 392 |
|
| 393 |
security, real-time multi-media data delivery, and extended |
| 394 |
addressing. It must be noted that it is very important that the IPng |
| 395 |
protocol headers not grow overly large. There is a sharp tradeoff |
| 396 |
between the value added by these headers (interoperability, global |
| 397 |
addressing, etc.) and the degree of communication performance |
| 398 |
attainable on limited capacity RF networks. Regardless of the data |
| 399 |
rate that future RF networks will be capable of supporting, there is |
| 400 |
always a tactical advantage in utilizing your resources more |
| 401 |
efficiently. |
| 402 |
|
| 403 |
Datagram Service |
| 404 |
|
| 405 |
The datagram service paradigm provides many useful features for |
| 406 |
tactical communication networks. The "memory" provided by datagram |
| 407 |
headers, provides an inherent amount of survivability essential to |
| 408 |
the dynamics of the tactical communication environment. The |
| 409 |
availability of platforms for routing and relaying is never 100% |
| 410 |
certain in a tactical scenario. The efficiency with which multi-cast |
| 411 |
can be implemented in a connectionless network is highly critical in |
| 412 |
the tactical environment where rapid, efficient information |
| 413 |
dissemination can be a deciding factor. And, as has been proven, |
| 414 |
with several different Internet applications and experiments, a |
| 415 |
datagram service is capable of providing useful connection-oriented |
| 416 |
and real-time communication services. |
| 417 |
|
| 418 |
Consideration should be given in IPng to how it can co-exist with |
| 419 |
other architectures such as switching fabrics which offer demand- |
| 420 |
based control over topology and connectivity. The military owns many |
| 421 |
of its own communication resources and one of the large problems in |
| 422 |
managing the military communication infrastructure is directing those |
| 423 |
underlying resources to where they are needed. Traditional |
| 424 |
management (SNMP, etc.) is of course useful here, but RF |
| 425 |
communication media can be somewhat dynamically allocated. Circuit |
| 426 |
switching designs offer some advantages here. Dial-up IP routing is |
| 427 |
an example of an integrated solution. The IPng should be capable of |
| 428 |
supporting a similar type of operation. |
| 429 |
|
| 430 |
Support of Communication Media |
| 431 |
|
| 432 |
The tactical communication environment includes a very broad spectrum |
| 433 |
of communication media from shipboard fiber-optic LANs to very low |
| 434 |
data rate (<2400 bps) RF links. Many of the RF links, even higher |
| 435 |
speed ones, can exhibit error statistics not necessarily well- |
| 436 |
serviced by higher layer reliable protocols (i.e., TCP). In these |
| 437 |
cases, efficient lower layer protocols can be implemented to provide |
| 438 |
reliable datagram delivery at the link layer, but at the cost of |
| 439 |
highly variable delay performance. |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Adamson [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1677">RFC 1677</a> IPng Tactical RF Requirements August 1994</span> |
| 447 |
|
| 448 |
|
| 449 |
It is also important to recognize that RF communication cannot be |
| 450 |
viewed from the IPng designer as simple point-to-point links. |
| 451 |
Often, highly complex, unique subnetwork protocols are utilized to |
| 452 |
meet requirements of survivability, communications performance with |
| 453 |
limited bandwidth, anti- jam and/or low probability of detection |
| 454 |
requirements. In some of these cases IPng will be one of several |
| 455 |
Layer 3 protocols sharing the subnetwork. |
| 456 |
|
| 457 |
It is understood that IPng cannot be the panacea of Layer 3 |
| 458 |
protocols, particularly when it comes to providing special mechanisms |
| 459 |
to support the endangered-specie low data rate user. However, note |
| 460 |
that there are many valuable low data rate applications useful to the |
| 461 |
tactical user. And low user data rates, coupled with efficient |
| 462 |
networking protocols can allow many more users share limited RF |
| 463 |
bandwidth. As a result, any mechanisms which facilitate compression |
| 464 |
of network headers can be considered highly valuable in an IPng |
| 465 |
candidate. |
| 466 |
|
| 467 |
Security Considerations |
| 468 |
|
| 469 |
Security issues are discussed throughout this memo. |
| 470 |
|
| 471 |
Author's Address |
| 472 |
|
| 473 |
R. Brian Adamson |
| 474 |
Communication Systems Branch |
| 475 |
Information Technology Division |
| 476 |
Naval Research Laboratory |
| 477 |
NRL Code 5523 |
| 478 |
Washington, DC 20375 |
| 479 |
|
| 480 |
EMail: [email protected] |
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
Adamson [Page 9] |
| 501 |
</pre> |