RFC 3506 on Requirements and Design for Voucher Trading System (VTS)
firstname.lastname@example.org Fri, 14 March 2003 00:23 UTC
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HBP00G04QFZTB@eListX.com> (original mail from rfc-ed@ISI.EDU); Thu, 13 Mar 2003 19:23:59 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HBP00G01QFVT5@eListX.com> for email@example.com (ORCPT firstname.lastname@example.org); Thu, 13 Mar 2003 19:23:58 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HBP00G01QFVT4@eListX.com> for email@example.com (ORCPT firstname.lastname@example.org); Thu, 13 Mar 2003 19:23:55 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [126.96.36.199]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBP00C73QFUIK@eListX.com> for email@example.com; Thu, 13 Mar 2003 19:23:54 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [188.8.131.52]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h2E0N5Z29242; Thu, 13 Mar 2003 16:23:05 -0800 (PST)
Date: Thu, 13 Mar 2003 16:23:05 -0800
Subject: RFC 3506 on Requirements and Design for Voucher Trading System (VTS)
To: IETF-Announce: ;
Cc: firstname.lastname@example.org, email@example.com
Content-type: multipart/mixed; boundary="Boundary_(ID_N/jWvOTlxzyo1VFoIIIGZw)"
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:firstname.lastname@example.org?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:email@example.com?body=unsubscribe>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:firstname.lastname@example.org?body=help>
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. 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.