RFC111 Pressure from the Chairman

0111 Pressure from the Chairman. S.D. Crocker. March 1971. (Format: TXT=2098 bytes) (Updates RFC0107) (Updated by RFC0130) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                           S. Crocker
Request for Comments #111                       UCLA
NIC #5815                                       31 March 71

                       Pressure from the Chairman

[Categories:  A.5;
 RFC's obsoleted:  none;
 RFC's updated:  107]

It is time to set serious schedules for the implementation of NCP's  and
Telnets.   To  facilitate  matters,  John  Heafner of Rand has agreed to
monitor each site's progress and test its implementation.

Network Liaison Contacts are hereby responsible for preparing a schedule
for  implementation  and  informing  John.  Such a schedule must include
dates of

   (a)  implementation of an NCP according to the specifications
        in Document #1 as modified by RFC #107;

   (b)  implementation of a user-Telnet which enables local users to
        login to foreign Hosts;

   (c)  implementation of a server-Telnet which enables foreign users to
        login on your Host;

   (d)  documentation of the mechanism for connecting to and logging in
        to your Host;

   (e)  documentation of the mechanism for obtaining job numbers,
        passwords, etc. to your Host;

   (f)  documentation of the services available on your Host; and

   (e) regular operation at advertised hours.















                                                                [Page 1]

RFC 111


John is hereby responsible  for  prodding  Host  teams  to  prodcue  the
requisite  schedule,  software  and  documentation;  for testing out the
advertised  implementations;  and  for  probing  and  understanding  the
reasons  for  unseemly  delays.   Concomitantly,  John  is now the right
person  to  complain   to   about   ambiguities,   insufficiencies   and
misunderstandings of the protocols.

   Thank you for your cooperation.



               Steve Crocker



       [ This RFC was put into machine readable form for entry ]
         [ into the online RFC archives by Josh Elliott 1/98 ]


































                                                                [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 

スポンサーリンク

Seedの実行順(外部キー制約などを先に実行させる方法) Foreign key violation

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

上に戻る