HPN Working Group Input to the IPng Requirements Solicitation
RFC 1679

Document Type RFC - Informational (August 1994; No errata)
Was draft-green-ipng-navy-hpn (individual)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1679 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           D. Green
Request for Comments: 1679                                       P. Irey
Category: Informational                                        D. Marlow
                                                           K. O'Donoghue
                                                                 NSWC-DD
                                                             August 1994

     HPN Working Group Input to the IPng Requirements Solicitation

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Abstract

   This document was submitted to the IETF IPng area in response to RFC
   1550.  Publication of this document does not imply acceptance by the
   IPng area of any ideas expressed within.  Comments should be
   submitted to the big-internet@munnari.oz.au mailing list.

Executive Summary

   The Navy's High Performance Network (HPN) working group has studied
   the requirements of mission critical applications on Navy platforms.
   Based on this study, three basic categories of issues for IPng have
   been identified.  The assumptions identified include accommodation of
   current functionality, commercial viability, and transitioning. The
   general requirements identified include addressing, integrated
   services architecture, mobility, multicast, and rapid route
   reconfiguration. Finally, the additional considerations identified
   include fault tolerance, policy based routing, security, and time
   synchroniztion. The HPN working group is interested in participating
   with the IETF in the development of standards which would apply to
   mission critical systems. In particular, the HPN working group is
   interested in the development of multicast functionality, an
   integrated services architecture, and support for high performance
   subnetworks.

1.   Introduction

   The HPN working group has been established to study future network
   architectures for mission critical applications aboard Navy
   platforms.  As a result, the HPN working group is interested in the
   results of the IPng selection and development process. This document
   is a product of discussions within the HPN working group.

Green, Irey, Marlow & O'Donoghue                                [Page 1]
RFC 1679                 HPN IPng Requirements               August 1994

   The purpose of this document is to provide what the HPN working group
   perceives as requirements for an IPng protocol set. Many of the
   necessary capabilities exist in current Internet and ISO network
   protocols; however, the HPN working group has identified needed
   capabilities that are beyond the existing standards.

   The HPN working group has identified three categories of topics for
   discussion in this document. The first category is assumptions or
   those topics that the HPN working group believes the IPng process
   will solve satisfactorily without specific Navy input. The second
   category is general requirements. These are capabilities that are
   felt to be insufficiently addressed in existing network protocols and
   of key importance to Navy mission critical applications. Finally, a
   set of additional considerations has been identified. These are also
   issues of importance to the HPN working group. However, no guidance
   or specific requests can be provided at this time.

2.   Background

   The US Navy has set up a program through the Space and Naval Warfare
   Systems Command called the Next Generation Computer Resources (NGCR)
   Program. The purpose of this program is to identify the evolving
   needs for information system technology in Navy mission critical
   systems. The NGCR High Performance Network (HPN) working group was
   recently established by the NGCR program to examine high performance
   networks for use on future Navy platforms (aircraft, surface ships,
   submarines, and certain shore-based applications). This working group
   is currently reviewing Navy needs. The requirements provided below
   are based on the HPN working group's current understanding of these
   Navy application areas. The application areas of interest are further
   examined below. The time frame for design, development, and
   deployment of HPN based systems and subsystems is 1996 into the
   twenty first century.

   Three general problem domains have been identified by the HPN working
   group. These are the particular problem domains within a mission
   critical environment that the HPN working group is targeting. The
   first is a distributed combat system environment.  This problem
   domain is analogous to a collection of workstations involved in many
   varied applications involving multiple sources and types of
   information.  Analog, audio, digital, discrete, graphic, textual,
   video, and voice information must be coordinated in order to present
Show full document text