RFC 3506: Requirements and Design for Voucher Trading System (VTS)
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3506
- Published
- March 2003
- Authors
- K. Fujimura; D. Eastlake
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3505Electronic Commerce Modeling Language (ECML): Version 2 RequirementsCurrent
March 2003
- RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent
March 2003
- RFC 3510Internet Printing Protocol/1.1: IPP URL SchemeCurrent
April 2003
- RFC 3492Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)Updated
March 2003
- RFC 3491Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)Obsoleted
March 2003
- RFC 3490Internationalizing Domain Names in Applications (IDNA)Obsoleted
March 2003
- RFC 3538Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP)Current
June 2003
- RFC 3466A Model for Content Internetworking (CDI)Obsoleted
March 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?