or a dynamic mechanism like BOOTP.

                 Note that BOOTP is not sufficiently general to specify
                 the configurations of all interfaces of a multihomed
                 host.  A multihomed host must either use BOOTP
                 separately for each interface, or configure one
                 interface using BOOTP to perform the loading, and
                 perform the complete initialization from a file later.

                 Application layer configuration information is expected
                 to be obtained from files after loading of the system
                 code.

         6.2.2.2  Loading Phase

            A suggested approach for the loading phase is to use TFTP
            [BOOT:1] between the IP addresses established by BOOTP.

            TFTP to a broadcast address SHOULD NOT be used, for reasons
            explained in Section 4.2.3.4.






























 



RFC1123              SUPPORT SERVICES -- MANAGEMENT         October 1989


   6.3  REMOTE MANAGEMENT

      6.3.1  INTRODUCTION

         The Internet community has recently put considerable effort
         into the development of network management protocols.  The
         result has been a two-pronged approach [MGT:1, MGT:6]:  the
         Simple Network Management Protocol (SNMP) [MGT:4] and the
         Common Management Information Protocol over TCP (CMOT) [MGT:5].

         In order to be managed using SNMP or CMOT, a host will need to
         implement an appropriate management agent.  An Internet host
         SHOULD include an agent for either SNMP or CMOT.

         Both SNMP and CMOT operate on a Management Information Base
         (MIB) that defines a collection of management values.  By
         reading and setting these values, a remote application may
         query and change the state of the managed system.

         A standard MIB [MGT:3] has been defined for use by both
         management protocols, using data types defined by the Structure
         of Management Information (SMI) defined in [MGT:2].  Additional
         MIB variables can be introduced under the "enterprises" and
         "experimental" subtrees of the MIB naming space [MGT:2].

         Every protocol module in the host SHOULD implement the relevant
         MIB variables.  A host SHOULD implement the MIB variables as
         defined in the most recent standard MIB, and MAY implement
         other MIB variables when appropriate and useful.

      6.3.2  PROTOCOL WALK-THROUGH

         The MIB is intended to cover both hosts and gateways, although
         there may be detailed differences in MIB application to the two
         cases.  This section contains the appropriate interpretation of
         the MIB for hosts.  It is likely that later versions of the MIB
         will include more entries for host management.

         A managed host must implement the following groups of MIB
         object definitions: System, Interfaces, Address Translation,
         IP, ICMP, TCP, and UDP.

         The following specific interpretations apply to hosts: