RFC 41 UNKNOWN OPERATIONAL · NETWORK · MESSAGES

IMP-IMP Teletype Communication

A request to add time and time-zone information to some IMP teletype messages.

RFC EDITOR

Melvin, J.T., "IMP-IMP Teletype Communication", RFC 41, DOI 10.17487/RFC0041, March 1970, <https://www.rfc-editor.org/info/rfc41>.

BIBTEX

@misc{rfc41,
  series = {Request for Comments},
  number = 41,
  howpublished = {RFC 41},
  publisher = {RFC Editor},
  doi = {10.17487/RFC0041},
  url = {https://www.rfc-editor.org/info/rfc41},
  author = {J.T. Melvin},
  title = {{IMP-IMP Teletype Communication}},
  pagetotal = 1,
  year = 1970,
  month = mar,
}

PUBLISHED: March 1970
AUTHORS: J.T. Melvin
STREAM: Legacy
REQUESTED TIME FORMAT: 24-hour time with time-zone designation
DOI: 10.17487/RFC0041

RFC text

Original text · RFC Editor View on rfc-editor.org ↗

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   ]

ISO Plain Language

On this page

PROBLEMAn operator may not know when a teletype message from another site was sent, making it harder to decide whether a response is timely.

MECHANISMThe note requests that IMP sites tag teletype messages that receive no response with 24-hour time and a time-zone designation.

THE REQUESTIt is a brief operational request, not a detailed protocol specification.

§1Why Message Time Matters

John Melvin describes seeing a message from another site on an IMP teletype without knowing its date or time. The age matters because a response may be appropriate if the message is recent but not if it is several hours old.

The note also points to sites spanning U.S. time zones and lacking a direct voice connection.

An operator may receive a message without knowing whether it is recent or several hours old. That information can affect whether the operator should reply.

§1Add Time to IMP-to-IMP Teletype Messages

The note requests that everyone tag IMP-to-IMP teletype messages that cause no response at the receiving IMP. It says the transmitting IMP site should use 24-hour time and include the time-zone designation.

The sending site should put the time and time zone on these messages. Then the receiving operator can tell when the message was sent.

§1A Brief Operational Request

RFC 41 describes a problem for operators and asks for a specific message annotation: 24-hour time plus a time-zone designation. It does not define a message format or other protocol details.

This short note asks operators to include timing information on certain teletype messages. It does not specify a broader protocol change.