RFC 4823: FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet
In plain English — editorial summary, not part of the RFC
This Applicability Statement (AS) describes how to exchange structured business data securely using the File Transfer Protocol (FTP) for XML, Binary, Electronic Data Interchange (EDI - ANSI X12 or UN/EDIFACT), or other data used for business-to-business data interchange for which MIME packaging can be accomplished using standard MIME content types. Authentication and data confidentiality are obtained by using Cryptographic Message Syntax (S/MIME) security body parts. Authenticated acknowledgements employ multipart/signed replies to the original message. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4823
- Published
- April 2007
- Authors
- T. Harding; R. Scott
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 40
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4561Definition of a Record Route Object (RRO) Node-Id Sub-ObjectCurrent
June 2006
- RFC 5502The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) SubsystemUpdated
April 2009
- RFC 3138Extended Assignments in 233/8Obsoleted
June 2001
- RFC 2328OSPF Version 2Updated
April 1998
- RFC 2280Routing Policy Specification Language (RPSL)Obsoleted
January 1998
- RFC 2178OSPF Version 2Obsoleted
July 1997
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 2015
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
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?