RFC 3538: Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP)

In plain English — editorial summary, not part of the RFC

This document describes detailed Input/Output parameters for the Internet Open Trading Protocol (IOTP) Payment Application Programming Interface (API). It also describes procedures in the Payment Bridge for the use of SET (SET Secure Electronic Transaction) as the payment protocol within Version 1.0 of the IOTP. This memo provides information for the Internet community.

Document record

Document ID

RFC3538

Published

June 2003

Authors

Y. Kawatsura

Status

INFORMATIONAL

Stream

IETF

Area

app

Pages

56

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3538

Topics

• payment
• input
• output
• parameter

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent

  January 2004

• RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent

  March 2003

• RFC 3354Internet Open Trading Protocol Version 2 RequirementsCurrent

  August 2002

• RFC 2801Internet Open Trading Protocol - IOTP Version 1.0Current

  April 2000

• RFC 2816A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN TechnologiesCurrent

  May 2000

• RFC 4357Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 AlgorithmsCurrent

  January 2006

• RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current

  May 2006

• RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent

  May 2006

Also filed under

• INFORMATIONAL
• 2003
• IETF stream
• app area