RFC 4154 on Voucher Trading System Application Programming Interface (VTS-API)

rfc-editor@rfc-editor.org Thu, 08 September 2005 00:35 UTC

Return-Path: <ietf-trade-errors+ietf-trade-1104-log+40pipe+2elists+2eelistx+2ecom@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0IMH00A022ZX1D@elistx.com> (original mail from rfc-ed@ISI.EDU) for ietf-trade-1104-log@pipe.lists.elistx.com; Wed, 07 Sep 2005 20:35:57 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0IMH00A012ZS1C@elistx.com> for ietf-trade@lists.elistx.com; Wed, 07 Sep 2005 20:35:52 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0IMH004N62ZSVL@elistx.com> for ietf-trade@lists.elistx.com; Wed, 07 Sep 2005 20:35:52 -0400 (EDT)
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j880Xfk16333; Wed, 07 Sep 2005 17:33:41 -0700 (PDT)
Date: Wed, 07 Sep 2005 17:33:41 -0700
From: rfc-editor@rfc-editor.org
Subject: RFC 4154 on Voucher Trading System Application Programming Interface (VTS-API)
Sender: rfc-ed@ISI.EDU
To: ietf-announce@ietf.org
Cc: rfc-editor@rfc-editor.org, ietf-trade@lists.elistx.com
Message-id: <200509080033.j880Xfk16333@boreas.isi.edu>
MIME-version: 1.0
Content-type: Multipart/Mixed; Boundary="NextPart"
X-Virus-Scanned-At: eList eXpress <http://www.elistx.com/>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>, <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 4154

        Title:      Voucher Trading System Application Programming
                    Interface (VTS-API)
        Author(s):  M. Terada, K. Fujimura
        Status:     Informational
        Date:       September 2005
        Mailbox:    te@rex.yrp.nttdocomo.co.jp,
                    fujimura.ko@lab.ntt.co.jp
        Pages:      32
        Characters: 61629
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-trade-voucher-vtsapi-06.txt

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


This document specifies the Voucher Trading System Application
Programming Interface (VTS-API).  The VTS-API allows a wallet or other
application to issue, transfer, and redeem vouchers in a uniform
manner independent of the VTS implementation.  The VTS is a system for
securely transferring vouchers; e.g., coupons, tickets, loyalty
points, and gift certificates.  This process is often necessary in the
course of payment and/or delivery transactions.

This document is a product of the Internet Open Trading Protocol
Working Group of the IETF.  

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.

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/rfc4154.txt"><ftp://ftp.isi.edu/in-notes/rfc4154.txt>