IT. Expert System.

RFC (unknown status)

Pressure from the Chairman. S.D. Crocker. March 1971. RFC111. (Format: TXT=2098 bytes) (Updates RFC107) (Updated by RFC130) (Status: UNKNOWN) (DOI: 10.17487 / RFC111)


 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] 


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

License.
All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 690 / 158764354. Delta: 0.01897 с