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

rfc-editor@rfc-editor.org Tue, 24 June 2003 22:49 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HH000J04CQF8S@eListX.com> (original mail from rfc-ed@ISI.EDU); Tue, 24 Jun 2003 18:49:27 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HH000J01CQC8M@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Tue, 24 Jun 2003 18:49:27 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HH000J01CQC8L@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Tue, 24 Jun 2003 18:49:24 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HH000I3OCQAIZ@eListX.com> for ietf-trade@lists.elistx.com; Tue, 24 Jun 2003 18:49:23 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5OMf1K20304; Tue, 24 Jun 2003 15:41:01 -0700 (PDT)
Date: Tue, 24 Jun 2003 15:41:01 -0700
From: rfc-editor@rfc-editor.org
Subject: RFC 3538 on Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP)
Sender: rfc-ed@ISI.EDU
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, ietf-trade@lists.elistx.com
Message-id: <200306242241.h5OMf1K20304@gamma.isi.edu>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_RG4UGQkOj5edatpibmoXAA)"
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-trade-request@lists.elistx.com?body=help>
List-Id: <ietf-trade.lists.elistx.com>

A new Request for Comments is now available in online RFC libraries.


        RFC 3538

        Title:      Secure Electronic Transaction (SET) Supplement for
                    the v1.0 Internet Open Trading Protocol (IOTP)
        Author(s):  Y. Kawatsura
        Status:     Informational
        Date:       June 2003
        Mailbox:    kawatura@bisd.hitachi.co.jp
        Pages:      56
        Characters: 103475
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-trade-iotp-v1.0-set-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3538.txt


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 document is a product of the Internet Open Trading Protocol
Working Group.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc3538.txt"><ftp://ftp.isi.edu/in-notes/rfc3538.txt>