RFC 4130: MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)
In plain English — editorial summary, not part of the RFC
This document provides an applicability statement (RFC 2026, Section 3.2) that describes how to exchange structured business data securely using the HTTP transfer protocol, instead of SMTP; the applicability statement for SMTP is found in RFC 3335. Structured business data may be XML; Electronic Data Interchange (EDI) in either the American National Standards Committee (ANSI) X12 format or the UN Electronic Data Interchange for Administration, Commerce, and Transport (UN/EDIFACT) format; or other structured data formats. The data is packaged using standard MIME structures. Authentication and data confidentiality are obtained by using Cryptographic Message Syntax with S/MIME security body parts. Authenticated acknowledgements make use of multipart/signed Message Disposition Notification (MDN) responses to the original HTTP message. This applicability statement is informally referred to as "AS2" because it is the second applicability statement, produced after "AS1", RFC 3335. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4130
- Published
- July 2005
- Authors
- D. Moberg; R. Drummond
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 47
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4141SMTP and MIME Extensions for Content ConversionCurrent
November 2005
- RFC 4229HTTP Header Field RegistrationsCurrent
December 2005
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent
September 2004
- RFC 4406Sender ID: Authenticating E-MailCurrent
April 2006
- RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent
July 2004
- RFC 4437Web Distributed Authoring and Versioning (WebDAV) Redirect Reference ResourcesCurrent
March 2006
- RFC 3463Enhanced Mail System Status CodesUpdated
January 2003
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?