HPN Working Group Input to the IPng Requirements Solicitation (RFC1679)
Original Publication Date: 1994-Aug-01
Included in the Prior Art Database: 2000-Sep-12
Internet Society Requests For Comment (RFCs)
D. Green: AUTHOR [+4]
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 email@example.com mailing list.
Network Working Group D. Green
Request for Comments: 1679 P. Irey
Category: Informational D. Marlow
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.
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 firstname.lastname@example.org mailing list.
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
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.
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 address...