A new Request for Comments is now available in online RFC libraries.


        RFC 1667:

        Title:      Modeling and Simulation Requirements for IPng
        Author:     S. Symington, D. Wood & M. Pullen
        Mailbox:    susan@gateway.mitre.org, wood@mitre.org
                    mpullen@cs.gmu.edu
        Pages:      7
        Characters: 17,291
        Updates/Obsoletes:  none


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.  

The Defense Modeling and Simulation community is a major user of
packet networks and as such has a stake in the definition of IPng.
This white paper summarizes the Distributed Interactive Simulation
environment that is under development, with regard to its real-time
nature, scope and magnitude of networking requirements.  The
requirements for real-time response, multicasting, and resource
reservation are set forth, based on our best current understanding of
the future of Defense Modeling and Simulation.

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 announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute