% Datatracker information for RFCs on the Legacy Stream is unfortunately often % incorrect. Please correct the bibtex below based on the information in the % actual RFC at https://rfc-editor.org/rfc/rfc916.txt @misc{rfc916, series = {Request for Comments}, number = 916, howpublished = {RFC 916}, publisher = {RFC Editor}, doi = {10.17487/RFC0916}, url = {https://www.rfc-editor.org/info/rfc916}, author = {}, title = {{Reliable Asynchronous Transfer Protocol (RATP)}}, pagetotal = 54, year = 1984, month = oct, abstract = {This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This paper proposes and specifies a protocol which allows two programs to reliably communicate over a communication link. It ensures that the data entering one end of the link if received arrives at the other end intact and unaltered. The protocol, named RATP, is designed to operate over a full duplex point-to-point connection. It contains some features which tailor it to the RS-232 links now in common use.}, }