RFC214 Network checkpoint

0214 Network checkpoint. E. Harslem. August 1971. (Format: TXT=3047 bytes) (Obsoletes RFC0198) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                              21 August 1971
Request for Comments 214                           E. Harslem-Rand
NIC 7195
Category: F
Obsoletes: 193, 198


                            NETWORK CHECKOUT


      As of August 21 we had performed the following verifications
with the sites listed below.  These verifications were done on an
arranged basis and do not indicate any degree of continuous
availability.

      In the category "NCP-107" the heading is somewhat misleading.
It does not indicate a thorough checkout of all the NCP functions
described in Document 1 and RFC-107.  It only indicates that the NCP
in question functioned to the extent required to respond to a RESET (a
necessary condition for the Rand NCP to consider the remote host "up")
and that the NCP performed the functions necessary for an ICP.  Thus,
this column really indicates only a small degree of NCP completeness.
Such function as ECHO, Give Back, error message generation and so on
were not checked.  We have checked some of these functions with UCSB
and SDC but not exhaustively.  This is mainly due to the tedium of
such a process.  BBN is currently writing a protocol certifier for
their DDP-516 host that will do this automatically.

                                  User   Server          Access
               NCP-107  ICP-156  Telnet  Telnet  Logger  Service
UCLA Sigma7      x        x        x       x       x       x
UCLA /91         x        x        x       x       na      x
SRI NIC          x        x                ?       ?       ?
UCSB             x        x        x       x       na      x
BBN A10          x        x                x       x       x
BBN TIP          x        x        x       x               na
MIT Multics      x        ?
MIT DMCG         x        x        x       x       x       x
SDC              x        x        x       x       ?
LINCOLN /67      x        x        x       x       x       x
UTAH             TENEX being installed


LEGEND:

 --- the function has not been verified for the host

x--- the function has been verified for the host



                                                                [Page 1]

21 Auguest 1971                                                  RFC 214


na-- the function is not applicable to the host due to its
     operating system or intended network use

?--- a comment follows for that function in that host


COMMENTS:

SRI NIC -- both a server telnet and logger exist; however, they
           do not process the telnet messages correctly

MIT Multics  -- we were only able to connect to an interim
          logger that sent a 'ts' message

SDC  -- the logger causes the system to crash following login


      Any discrepancies should be noted via phone call.  This
RFC will be updated in about one month.




       [ This RFC was put into machine readable form for entry ]
          [ into the online RFC archives by Brian Court 6/97 ]


























                                                                [Page 2]

一覧

 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系アプリ系の製作案件募集中です。

上に戻る