RFC39 Comments on Protocol Re: NWG/RFC #36

0039 Comments on Protocol Re: NWG/RFC #36. E. Harslem, J.F. Heafner. March 1970. (Format: TXT=4779 bytes) (Updates RFC0036) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                         E. Harslem
Request for Comments: 39                                      J. Heafner
                                                                    RAND
                                                           25 March 1970


                  COMMENTS ON PROTOCOL RE: NWG/RFC #36

   We offer the following suggestions to be considered as additions to
   the April 28th 1970 protocol grammar specifications.

   ERROR MESSAGES

          

   It is desirable to include debugging aids in the initial protocol for
   checking out Network Control Programs, etc.

   There are three classes of errors--content errors, status errors, and
   resource allocation or exhaustion.  specifies the class and the
   offending member of the class.  The command is returned to the
   sending NCP for identification and analysis.

   Examples of status errors are: messages sent over blocked links and
   attempts to unblock an unblocked link.  Examples of content errors
   are: an invalid RFC complete; a message sent on a link not connected;
   closing of an unconnected link; and an attempt to unblock an
   unconnected link.  Examples of resource errors are:  a request for a
   non-existent program and connection table overflow, etc.  Resource
   errors should be followed by a  in response to the .

   QUERIES

           < >

   or      

   Queries provide an extension to the  facility as well as limited
   error recovery, thus avoiding re-initialization of an NCP.

   The first command requests the remote NCP to supply the status of all
   connections to the user specified by the user number in .
   The second is the reply;  contains the connection status
   information.  If an NCP wants the status of all connections to a
   remote HOST, the  is zero.






Harlsem & Heafner                                               [Page 1]

RFC 39            COMMENTS ON PROTOCOL RE: NWG/RFC #36        March 1970


   PROGRAM TERMINATION NOTIFICATION

         

   This command supplements rather than replaces .  It severs all
   communication between a program and those programs in a given HOST to
   which it is connected.  This command performs what would otherwise be
   handled by multiple  commands.  contains the sender's
   user number.

   HOST STATUS

        
        

   These messages (HOST coming up and HOST voluntarily going down) are
   compatible with asynchronous, interrupt-driven programs, as opposed
   to the more conventional post/poll method.

   TRANSMIT AND BROADCAST

         
         

   Unlike the previous commands, these are not sent over the control
   link, but rather over links assigned to user programs.  The prefix of
    or  indicates, to the receiving NCP, the disposition of
   the message body.  indicates a message to be passed to a single
   process.  specifies to the destination NCP that the message is
   to be distributed over all receiving connections linked to the
   sender.  In response to a system call by the user to an NCP
   requesting , the NCP generates one  to each HOST to which
   the sender is connected.

   RFC AND DYNAMIC RECONNECTION

   This protocol is complex; it proliferates control messages; it causes
   queues (to become associated with re-entrant procedures) that are
   artificially imposed via the protocol (remote AEN assignment); and
   discounts the situation where only controlling process "A" has
   knowledge that slave process "B" should be "rung out" in a dynamic
   reconnection.

   The , etc., are suggestions for inclusion as additions in the
   April 28th protocol specifications.  The above criticism is, of
   course, not intended to affect modification of the RFC structure by
   April 28th, nor to reflect on those who planned it.  We have not
   studied the problem.  It is meant, however, to voice our concern



Harlsem & Heafner                                               [Page 2]

RFC 39            COMMENTS ON PROTOCOL RE: NWG/RFC #36        March 1970


   about complexity and resulting response times.  This is a difficult
   problem and it deserves more study after we have exercised the
   current RFC specifications.  We hope to offer constructive
   suggestions with respect to the RFC in the future.



   JFH:hs


         [ This RFC was put into machine readable form for entry ]
          [ into the online RFC archives by Mario Vitale 08/99 ]







































Harlsem & Heafner                                               [Page 3]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る