Feature negotiation mechanism for the File Transfer Protocol
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 9
- Abstract
- This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK]
- Publication Date
- 1998-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2389- Link
- https://doi.org/10.17487/RFC2389
- Author(s)
- Paul HethmonRobert Elz
- Keyword(s)
- FTP
Latest version of IETF RFC 2389
Document Versions — IETF RFC 2389
-
▶ IETF RFC 2389 (1998-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 959 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2234 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2389.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2389, Feature negotiation mechanism for the File Transfer Protocol. Available at https://doi.org/10.17487/RFC2389
Snippet:
IETF RFC 2389, Feature negotiation mechanism for the File Transfer Protocol. Available at https://doi.org/10.17487/RFC2389
HTML (ISO 690 compliant)
Preview:
IETF RFC 2389, Feature negotiation mechanism for the File Transfer Protocol. Available at https://doi.org/10.17487/RFC2389
Snippet:
<span class="citation"><cite>IETF RFC 2389</cite>, Feature negotiation mechanism for the File Transfer Protocol. Available at <a href="https://doi.org/10.17487/RFC2389" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2389</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2389, Feature negotiation mechanism for the File Transfer Protocol
doi: 10.17487/RFC2389
url: https://doi.org/10.17487/RFC2389
doi: 10.17487/RFC2389
url: https://doi.org/10.17487/RFC2389
Snippet:
<li> <cite id="bib-rfc2389">IETF RFC 2389</cite>, Feature negotiation mechanism for the File Transfer Protocol <span class="doi">10.17487/RFC2389</span> </li>
Referenced By
- IETF RFC 2557 [Active*]
- IETF RFC 4217 [Active*]