RFC 1676 (rfc1676) - Page 1 of 4
INFN Requirements for an IPng
Alternative Format: Original Text Document
Network Working Group A. Ghiselli
Request for Comments: 1676 D. Salomoni
Category: Informational C. Vistoli
INFN/CNAF
August 1994
INFN Requirements for an IPng
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.
Overview
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 mailing list.
Abstract
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.
1. General Requirements
The problems that are to be solved in IP internet are mainly three:
1. address exhaustion
2. flat address space
3. routing efficiency, flexibility and capacity.
The aim of IPng study should be to define a plan that solves all
these problems as a whole and not each of them separately.
The general requirements that we underline for this transition are:
Ghiselli, Salomoni & Vistoli