Requirements and Design for Voucher Trading System (VTS)
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3506.
|Authors||Donald E. Eastlake 3rd , Ko Fujimura|
|Last updated||2015-10-14 (Latest revision 2002-07-25)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|IESG||IESG state||RFC 3506 (Informational)|
|Responsible AD||Patrik Fältström|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3506 Title: Requirements and Design for Voucher Trading System (VTS) Author(s): K. Fujimura, D. Eastlake Status: Informational Date: March 2003 Mailbox: email@example.com, Donald.Eastlake@motorola.com Pages: 15 Characters: 30945 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trade-drt-requirements-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3506.txt Crediting loyalty points and collecting digital coupons or gift certificates are common functions in purchasing and trading transactions. These activities can be generalized using the concept of a "voucher", which is a digital representation of the right to claim goods or services. This document presents a Voucher Trading System (VTS) that circulates vouchers securely and its terminology; it lists design principles and requirements for VTS and the Generic Voucher Language (GVL), with which diverse types of vouchers can be described. 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.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.