Internet Open Trading Protocol (IOTP) Codes per [RFC2801] (last updated 2001-12-27) To help ensure interoperability, there is a need for codes used by IOTP to be maintained in a controlled environment so that their meaning and usage are well defined and duplicate codes avoided. [IANA] is the mechanism to be used for this purpose as described in RFC 2434. The element types and attributes names to which this procedure applies is shown in the table below together with the initial values that are valid for these attributes. Note that: o the IETF Trade mailing list's email address is ietf-trade&lists.elistx.com o "Designated Experts" (see [IANA]) are appointed by the IESG. Element Types/Attribute Names and Attribute Values Algorithm/Name (When Algorithm is a child of an AuthReq Component) ------------------------------------------------------------------ "sha1" - indicates that a [SHA1] authentication will apply "signature" - indicates that authentication consists of the generation of a digital signature. "Pay:ppp" where "ppp" may be set to any valid value for "iotpbrand" (see below) With the exception of Algorithms that begin with "pay:", new values are allocated following review on the IETF Trade mailing list and by the Designated Expert. Note: The Algorithm element is likely to be eventually defined within the [DSIG] name space. It is likely that the maintenance procedure defined here may need to vary over time, as the DSIG proposals become more widely adopted. Brand/BrandId ------------- The following list of initial BrandIds have been taken from those Organisations that have applied for SET certificates as at 1st June 1999: Brand/BrandID Organization Contact Person/E-mail address ------------- --------------- ------------------------------------ "Amex" - American Express "Dankort" - Dankort "JCB" - JCB "Maestro" - Maestro "MasterCard" - MasterCard "NICOS" - NICOS "VISA" - Visa Tony Lewis In addition the following Brand Id values are defined: "atCredits" - @UK PLC "EZpay" - ITI Services "GeldKarte" - GeldKarte "Mondex" - Mondex "paybox" - paybox.net AG New values of BrandId must be announced to the IETF Trade mailing list and, if there are no objections within three weeks, are allocated on a "first come first served" basis. CurrencyAmount/CurrCode ----------------------- Currency codes are dependent on CurrCodeType (see below). If CurrCodeType is "ISO4217-A" then the currency code is an alphabetic currency code as defined by [ISO4217]. If CurrCodeType is "IOTP" then new values must be announced to the IETF Trade mailing list and, if there are no objections within three weeks, are allocated on a "first come first served" basis. Note: The Currency Code Type of IOTP, is designed to allow the support of "new" psuedo currencies such as loyalty or frequent flyer points. At the time of writing this specification, no currency codes of this type have been defined. CurrencyAmount/CurrCodeType --------------------------- "ISO4217-A" "IOTP" New values of CurrCodeType attribute are allocated following review on the IETF Trade mailing list and by the Designated Expert. DeliveryData/DelivMethod ------------------------ "Post" "Web" "Email" New values of Delivery Method attribute are allocated following review on the IETF Trade mailing list and by the Designated Expert. This may require the publication of additional documentation to describe how the delivery method is used. PackagedContent/Content ----------------------- "PCDATA" "MIME" "MIME:mimetype" (where mimetype must be the same as content-type as defined by [MIME] ) "XML" If the Content attribute is of the form "MIME"mimetype", then control of new values for "mimetype" is as defined in [MIME]. Otherwise, new values of the Content attribute are allocated following review on the IETF Trade mailing list and by the Designated Expert. This may require the publication of additional documentation to describe how the new attribute is used within a Packaged Content element. RelatedTo/RelationshipType -------------------------- "IotpTransaction" "Reference" New values of the RelationshipType attribute are allocated following review on the IETF Trade Working Group mailing list and by the Designated Expert. This may require the publication of additional documentation to describe how the delivery method is used. Status/StatusType ----------------- Offer Payment Delivery Authentication Unidentified New values of the Status Type attribute are allocated following: o publication to the IETF Trade Working Group, of an RFC describing the Trading Exchange, Trading Roles and associated components that relate to the Status, and o review of the document on the IETF Trade mailing list and by the Designated Expert. Note: The document describing new values for the Status Type attribute may be combined with documents that describe new Trading Roles and types of signatures (see below). TradingRole/Trading Role ------------------------ "Consumer" "Merchant" "PaymentHandler" "DeliveryHandler" "DelivTo" "CustCare" New values of the Trading Role attribute are allocated following: o publication to the IETF Trade Working Group, of an RFC describing the Trading Exchange, Trading Roles and associated components that relate to the Trading Role, and o review of the document on the IETF Trade mailing list and by the Designated Expert. Note: The document describing new values for the Trading Role attribute may be combined with documents that describe new Status Types (see above) and types of signatures (see below). TransId/IotpTransType --------------------- "BaselineAuthentication" "BaselineDeposit" "BaselinePurchase" "BaselineRefund" "BaselineWithdrawal" "BaselineValueExchange" "BaselineInquiry" "BaselinePing" New values of the IotpTransType attribute are allocated following: o publication to the IETF Trade mailing list, of an RFC describing the new IOTP Transaction, and o review of the document on the IETF Trade Working Group mailing list and by the Designated Expert. Attibute/Content (see Signature Component) ------------------------------------------ "OfferResponse" "PaymentResponse" "DeliveryResponse" "AuthenticationRequest" "AuthenticationResponse" "PingRequest" "PingResponse" New values of the code that define the type of a signature are allocated following: o publication to the IETF Trade Working Group, of an RFC describing the Trading Exchange where the signature is being used, and o review of the document on the IETF Trade mailing list and by the Designated Expert. Note: The document describing new values for the types of signatures may be combined with documents that describe new Status Types and Trading Roles (see above). References ---------- [RFC2801] Burdett, D., "Internet Open Trading Protocol - IOTP Version 1.0", RFC 2801, April 2000 (created 2000-04) []