RFC 2640: Internationalization of the File Transfer Protocol
In plain English — editorial summary, not part of the RFC
This document addresses the internationalization (I18n) of FTP, which includes supporting the multiple character sets and languages found throughout the Internet community. This is achieved by extending the FTP specification and giving recommendations for proper internationalization support. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2640
- Published
- July 1999
- Authors
- B. Curtin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 27
- Also known as
- —
- Updates:
- RFC 959
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2428FTP Extensions for IPv6 and NATsCurrent
September 1998
- RFC 2389Feature negotiation mechanism for the File Transfer ProtocolCurrent
August 1998
- RFC 3659Extensions to FTPCurrent
March 2007
- RFC 2585Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTPCurrent
May 1999
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 6249Metalink/HTTP: Mirrors and HashesCurrent
June 2011
- RFC 2987Registration of Charset and Languages Media Features TagsCurrent
November 2000
- RFC 1342Representation of Non-ASCII Text in Internet Message HeadersObsoleted
June 1992
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?