RFC 985 (rfc985) - Page 2 of 23

Requirements for Internet gateways - draft

RFC 985                                                         May 1986
Requirements for Internet Gateways -- DRAFT


      Larry Landweber, U Wisconsin    
      Tony Lauck, DEC                 rhea!bergil!a
      Dave Mills (Chairman), Linkabit a
      Dennis Perry, DARPA/IPTO        a

   The subcommittee wishes to thank the following additional
   contributors and invited referees:

      Len Bosack, Stanford U/CISCO    a
      Bob Braden, ISI                 a
      Hans-Werner Braun, U Michigan   
      Noel Chiappa, MIT/Proteon       a
      Doug Comer, Purdue U            
      Ira Fuchs, Princeton U          fuchs%
      Ed Krol, U Illinois            krol%
      Barry Leiner, RIACS             a
      Mike Muuss, BRL                 a
      Ron Natalie, BRL                a
      Harvey Newman, CIT              a
      Jon Postel, ISI                 a
      Marshall Rose, NRTC             
      Jeff Schiller, MIT              
      Lixia Zhang, MIT                

1.  Introduction

   The following sections are intended as an introduction and background
   for those unfamiliar with the DARPA Internet architecture and the
   Internet gateway model.  General background and discussion on the
   Internet architecture and supporting protocol suite can be found in
   the DDN Protocol Handbook [25] and ARPANET Information Brochure [26],
   both available from the Network Information Center, SRI
   International, Menlo Park, CA 94025.  Readers familiar with these
   concepts can proceed directly to Section 2.

   1.1.  The DARPA Internet Architecture

      The DARPA Internet system consists of a number of gateways and
      networks that collectively provide packet transport for hosts
      subscribing to the DARPA Internet protocol architecture.  These
      protocols include the Internet Protocol (IP), Internet Control
      Message Protocol (ICMP), Transmission Control Protocol (TCP) and
      application protocols depending upon them.  All protocols use IP
      as the basic packet-transport mechanism.  IP is a datagram, or
      connectionless, service and includes provision for service
      specification, fragmentation/reassembly and security information.
      ICMP is considered an integral part of IP, although it is


NTAG