Summary:

BaswareONE supports by default the most common communication protocols.
Please find the list below together with some brief explanation about the protocol:

• HTTP
• FTP
• X400
• VAN
• AS2

Additional Information:

HTTP:
The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems.[1] HTTP is the foundation of data communication for the World Wide Web.
Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext.

The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network, such as the Internet.
FTP is built on a client-server architecture and uses separate control and data connections between the client and the server.[1] FTP users may authenticate themselves using a clear-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that protects the username and password, and encrypts the content, FTP is often secured with SSL/TLS (FTPS). SSH File Transfer Protocol (SFTP) is sometimes also used instead, but is technologically different.

X400:
X400 is a suite of ITU-T Recommendations that define standards for Data Communication Networks for Message Handling Systems (MHS) — more commonly known as email.
At one time, the designers of X.400 were expecting it to be the predominant form of email, but this role has been taken by the SMTP-based Internet e-mail. Despite this, it has been widely used within organizations and was a core part of Microsoft Exchange Server until 2006; variants continue to be important in military and aviation contexts.

BaswareONE X400-address :

CT (test):
C=NL
A=400NET
P=CERTIONE
S=staging

Production:
C=NL
A=400NET
P=CERTIONE
S=production

VAN:
• Communication through IE VAN Mailbox system (GXS /IBM)
• Exchange of solely pure EDI messages

Production BaswareONE mailbox

BEADI.BEADI039

The AS2 protocol is based on HTTP and S/MIME. It was the second AS protocol developed and uses the same signing, encryption and MDN conventions used in the original AS1 protocol introduced in the late 90s. In other words:

• Files are encoded as "attachments" in a standardized S/MIME message (an AS2 message).
• AS2 messages are always sent using the HTTP or HTTPS protocol
• Messages can be signed, but do not have to be.
• Messages can be encrypted, but do not have to be.
• Messages may request a Message Disposition Notification (MDN) back if all went well, but do not have to request such a message.
• If the original AS2 message requested an MDN:
  
  • Upon the receipt of the message and its successful decryption or signature validation (as necessary) a "success" MDN will be sent back to the original sender. This MDN is typically signed but never encrypted (unless temporarily encrypted in transit via HTTPS).
  • Upon the receipt and successful verification of the signature on the MDN, the original sender will "know" that the recipient got their message (this provides the "Non-repudiation" element of AS2)
  • If there are any problems receiving or interpreting the original AS2 message, a "failed" MDN may be sent back. However, part of the AS2 protocol states that the client must treat a lack of an MDN as a failure as well, so some AS2 receivers will simply not return an MDN in this case.