|
RFC Home |
Full RFC Index |
Recent RFCs |
RFC Standards |
Best Current Practice |
RFC Errata |
1 April RFC |
|
||||||
|
IETF RFC 41
IMP-IMP Teletype Communication Last modified on Wednesday, November 19th, 1997 Permanent link to RFC 41 Search GitHub Wiki for RFC 41 Show other RFCs mentioning RFC 41 Network Working Group John Melvin Request for Comments: 41 SRI/ARC 30 March 1970 IMP/IMP Teletype Communication I have occasionally found myself in a situatuation in Which I see a message from site X on my IMP teletype, but I don't know the time and date of the message. I find this annoying, since a response to it may be in order if it is (say) less than an hour old, but not if it is several hours old. The situation is not improved by the existence of sites that now span all time zones of the U.S. and do not have direct voice connection. It is requested that everyone tag their IMP to IMP tele- type messages that cause no response at the receiving IMP. The transmitting IMP site should use 24 hour time and include the time zone designation. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Larry Campbell 7/97 ] IMP-IMP Teletype Communication RFC TOTAL SIZE: 1038 bytes PUBLICATION DATE: Wednesday, November 19th, 1997 LEGAL RIGHTS: The IETF Trust (see BCP 78) |