CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 06:57:02 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=F_DgpMpduHLDKIOI1TPBHOGaHGv4iN2YxsZBV5WZznM-1760079422-1.0.1.1-LkeVXoOiFB5qswZdHYBLVVpMx3MSxgUOZbmq_Pa_NXIMkaJ43QUaxxXWmVakGqv55NMuKQTYwNpxmG0CIzQdaiKqiKoyIE6_oQU.jnDVEN0; path=/; expires=Fri, 10-Oct-25 07:27:02 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c4389fb914c1b0-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 801 » RFC Editor
Search RFCs
RFC 801
NCP/TCP transition plan, November 1981
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC0801
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 801
Abstract
This RFC discusses the conversion of hosts from NCP to TCP. And making available the principle services: Telnet, File Transfer, and Mail. These protocols allow all hosts in the ARPA community to share a common interprocess communication environment.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us