rfc1015.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

    The IRIO can then establish sub-contracts for engineering,
    procurement, installation, and management of gateways and operation
    of the user services center.

    To initiate the research coordination, the following steps will be
    accomplished.

    The Internet Activities Board will evolve into the Internet Research
    Activities Board, through added membership and charter revision.

    Additional task forces will be formed as needed to reflect the
    expanded areas of research interest.

    Once the IRI is established and operating, the funding and use of
    the IRI will be reviewed to determine if equal funding is equitable.
    If not, the IRIO should be tasked to develop a recommendation for a
    practical cost allocation scheme. In addition, once the IRI has
    proved itself to be successful,  other agencies will join the IRI
    and provide additional funding.

INDUSTRY ROLE

    This report has thus far addressed the interconnection of agency
    supported networks and the use of such an internet by agency
    supported researchers. However, industry also has a need for a
    similar infrastructure to support its research activities. [13]
    [14]. Note that this refers only to industrial research activities.
    It is not envisioned, nor would it be appropriate, for the IRI to
    provide a communications system for normal industrial activities.
    Regulatory concerns make it difficult for industry to connect to a
    network that is supported by a federal agency in pursuit of the
    agency mission.

    The IRI structure above, though, may permit the connection of
    industrial research organizations.  Since the IRIO is a non-profit
    non-government organization, it would be able to accept funds from



Leiner                                                         [Page 20]

RFC 1015                      IRI Plan                         July 1987


    industry as a fair share of the costs of using the IRI. These funds
    in turn can be used to expand the networking resources so that no
    degradation of service is felt by the users suppported by the
    federal agencies. This topic would need to be discussed further by
    the Policy Board and the organization selected as the IRIO.

SUMMARY AND CONCLUSIONS

    The interconnection of the various agency networks supporting
    scientific research into an overall infrastructure in support of
    such research represents an exciting opportunity.  This report
    recommends an approach and a specific set of actions that can
    achieve that goal. It is hoped that, regardless of the mechanism
    used, that the Federal agencies involved recognize the importance of
    providing an appropriate national infrastructure in support of
    scientific research and take action to make such an infrastructure a
    reality.

ACKNOWLEDGEMENT

    This report was prepared with advice and comments from a large
    number of people, including the members of the FCCSET Committee
    Network Working Group and the Internet Activities Board.  Their
    input is greatly appreciated, and I hope that this report represents
    a consensus on both the need for the IRI and the proposed approach.


























Leiner                                                         [Page 21]

RFC 1015                      IRI Plan                         July 1987


APPENDIX A - FUNDING BREAKDOWN

    This appendix provides the details for the budgetary estimates of
    Table 1.

    Gateways

    Gateways will be required between the various agency (and perhaps
    regional) networks. As an upper bound, assume one IRI gateway per
    state times $40K per gateway, spread out over two years, for a
    capital cost of $1M per year for first two years.

    Operation Center

    The IRI operations center will have to engineer the location and
    capacity of the gateways, as well as install, operate and maintain
    them. It also will need to coordinate support and maintenance of
    end-to-end service, helping to identify and correct problems in the
    interconnections. Costs are estimated as two people round the clock
    to man the operations center and three full time people to
    coordinate, operate, and engineer the IRI.  Using an estimate of
    $120K (including other direct costs (ODC)) per year for an operator
    and $200K per year for other activities, and translating 2 people
    round the clock into 9 people results in a total annual cost of
    $1.7M. In addition, equipment costs of roughly $500K per year can be
    expected.

    Transit Networks

    It is expected that support of at least one transit network will be
    necessary. This may involve reimbursement to one of the agencies for
    use of their network, or may involve operations and maintenance of
    an IRI dedicated network. An estimate for these costs, based on
    historical data for operating the Arpanet, is $4M per year.

    User Support Organization

    To provide effective support as discussed above will require a staff
    available during working hours.  A reasonable estimate for the costs
    of such an organization is 5 people times $200K per year, or $1M per
    year (including ODC). In addition, there will be capital equipment
    costs in the first two years totalling roughly $2M.









Leiner                                                         [Page 22]

RFC 1015                      IRI Plan                         July 1987


REFERENCES

       1.  FCCSET Committee on Very High Performance Computing Network
           Working Group, Report on Interagency Networking for Research
           Programs, February 1986.

       2.  Cerf, V.G. and P. Kirstein, "Issues in packet-network
           interconnection,"  Proceedings of the IEEE, pp. 1386-1408,
           November 1978

       3.  Cerf, V.G. and E. Cain, "The Dod intenet architecture model,
           "Computer Networks, pp. 307-318, July 1983.

       4.  Leiner, B.M., J. Postel, R. Cole, and D. Mills, "The DARPA
           internet protocol suite,"  IEEE communications Magazine
            March 1985.

       5.  Defense Advanced Research Projects Agency, A History of the
           Arpanet: The First Decade, Defense Advanced Research Projects
           Agency, April 1981.  (Defense Tech. Info. Center AD A1 15440)

       6.  Jacobs, I.M. et. al., "General purpose satellite networks,"
           Proceedings of the IEEE pp. 1448-1467, November 1978

       7.  Tobagi, F., R. Binder, and B.M. Leiner, "Packet radio and
           satellite networks," IEEE Communications Magazine, November
           1984.

       8.  Kahn, R.E. et. al., "Advances in packet radio technology,"
           Proceedings of the IEEE pp. 1468-1496, November

       9.  Clark, D. et. al., "An introduction to local area
           networks,", Proceedings of the IEEE, November 1978

      10.  Lederberg, J., "Digital communications and the conduct
           of science: the new literacy," vol. 66, pp. 1314-1319,
           November 1978.

      11.  Hoskins, J.C. and J.S. Quaterman, "Notable Computer
           Networks,", pp. 932-971, October 1986.

      12.  Dennings, P.J., A.C. Hearn, and C.W. Kern, "History and
           overview of CSNET," pp. 138-145, March 1983.

      13.  Comer, D., "The computer science research network
           CSNET: A history and status report", vol. 26, pp. 747-753,
           October 1983.




Leiner                                                         [Page 23]

RFC 1015                      IRI Plan                         July 1987


      14.  Bailey, R.R. NAS: supercomputing master tool for
           aeronautics Aerospace America, pp. 118-121, January 1985

      15.  Jennings, D.M., L.H. Landweber, I.H. Fuchs, W.R. Adrion
           "Computer Networking for Scientist Science" vol. 231
           pp. 943-950, February 1986

      16.  Cerf, V.G. R.E. Kahn, "A protocol for packet network
           intercommunication, IEEE Transactions on Communications
           vol. COM-22, May 1974

      17.  Zimmerman, H. "OSI reference model - the ISO model of
           architecture for open systems intercommunications, IEEE
           Transactions on Communications vol. COM-28 pp. 425-432
           April 1980

      18.  Defense Communications Agency, MIL STD 1777: Internet
           Protocol, 1983

      19.  Defense Communications Agency, MIL STD 1778: Transmission
           Control Protocol Defense Communications Agency, 1983

      20.  Defense Communications Agency, MIL STD 1780: File Transfer
           Protocol Defense Communications Agency, 1985

      21.  Defense Communications Agency, MIL STD 1781: Simple Mail
           Transfer Protocol Defense Communications Agency, 1985

      22.  Defense Communications Agency, MIL STD 1782: Telnet
           Protocol Defense Communications Agency, 1985

      23.  Leiner, B.M. and M. Bishop, Research Institute for Advanced
           Computer Science Access Control and Privacy in Large
           Distribution Systems, RIACS TR 86.6, March 1986

















Leiner                                                         [Page 24]