RFC1676 on INFN Requirements for an IPng

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 11 August 1994 20:32 UTC

Message-Id: <199408112029.AA08261@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1676 on INFN Requirements for an IPng
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 11 Aug 1994 13:30:24 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1676:

        Title:      INFN Requirements for an IPng
        Author:     A. Ghiselli, D. Salomoni & C. Vistoli
        Mailbox:    Salomoni@infn.it, Vistoli@infn.it,
                    Ghiselli@infn.it
        Pages:      4
        Characters: 8,493
        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.

This white paper is sent by INFN network team, the Italian National
Institute for nuclear physics, whose network, named INFNet, is a
nationwide network founded to provide the access to existing national
and international HEP laboratory and to facilitate communications
between the researchers.  With this paper we would like to emphasize
the key points that we would to consider if charged with IPng plan. We
do not really expect to add original items to the selection, but we
think that it could be useful to submit the opinions and ideas that
come from our network experience.

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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ds.internic.net/rfc/rfc1676.txt"><ftp://ds.internic.net/rfc/rfc1676.txt>

RFC1676 on INFN Requirements for an IPng Joyce K. Reynolds