UTF-8 Option for FTP
draft-ietf-ftpext-utf-8-option-00
| Document | Type |
Expired Internet-Draft
(ftpext WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Gregory A. Lundberg | ||
| Last updated | 2002-05-24 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies an extension to the File Transfer Protocol (FTP) which provides for inter-operation between existing implementations and those supporting the exchange of UTF-8 encoded pathnames, and clarifies certain issues involved with UTF-8 encoding. It introduces a new option, UTF-8, negotiated by use of the OPTS command. Through use of this option, the user informs the server of its willingness to accept UTF-8 encoded pathnames. The proposed extension requires that neither party transmit UTF-8 encoded pathnames without having first successfully negotiated this option.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)