draft-ietf-trade-iotp-v1.0-papi-01.txt   draft-ietf-trade-iotp-v1.0-papi-02.txt 
TRADE Working Group Werner Hans TRADE Working Group Werner Hans
INTERNET-DRAFT Hans-Bernhard.Beykirch INTERNET-DRAFT Hans-Bernhard.Beykirch
SIZ SIZ
Masaaki Hiroya Masaaki Hiroya
Yoshiaki Kawatsura Yoshiaki Kawatsura
Hitachi Hitachi
Expires: March 2001 September 2000 Expires: March 2001 September 2000
Payment API for v1.0 Internet Open Trading Protocol (IOTP) Payment API for v1.0 Internet Open Trading Protocol (IOTP)
------- --- --- ---- -------- ---- ------- -------- ------ ------- --- --- ---- -------- ---- ------- -------- ------
draft-ietf-trade-iotp-v1.0-papi-01.txt <draft-ietf-trade-iotp-v1.0-papi-02.txt>
Status of this Memo Status of this Memo
This document is intended to become an Informational RFC and will be This document is intended to become an Informational RFC and will be
in full conformance with all provisions of Section 10 of RFC2026. in full conformance with all provisions of Section 10 of RFC2026.
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
skipping to change at page 14, line 7 skipping to change at page 14, line 7
"Change Process State" is used (here only) for abnormal termination. "Change Process State" is used (here only) for abnormal termination.
(cf. Payment Processing Related API Functions). (cf. Payment Processing Related API Functions).
o Brand Selection Related API Functions o Brand Selection Related API Functions
"Find Payment Instrument" identifies which instances of a payment "Find Payment Instrument" identifies which instances of a payment
instrument of a particular payment brand are available for use in a instrument of a particular payment brand are available for use in a
payment. payment.
"Find Payment Protocol" identifies which payment protocols are
supported by a specific payment instrument, resp. payment brand.
This function might be used in conjunction with the aforementioned
function or called without any brand identifier.
"Check Payment Possibility" checks whether a specific payment "Check Payment Possibility" checks whether a specific payment
instrument is able to perform a payment. instrument is able to perform a payment.
"Authenticate" forwards any payment scheme specific authentication "Authenticate" forwards any payment scheme specific authentication
data to the IOTP Payment Bridge for processing. data to the IOTP Payment Bridge for processing.
"Change Process State" is used (here only) for abnormal termination. "Change Process State" is used (here only) for abnormal termination.
(cf. Payment Processing Related API Functions). (cf. Payment Processing Related API Functions).
o Payment Processing Related API Functions o Payment Processing Related API Functions
skipping to change at page 16, line 50 skipping to change at page 16, line 43
Inquire Authentication Challenge(Algn*) -> IPB Inquire Authentication Challenge(Algn*) -> IPB
Inq. Auth. Challenge Response(Algn,Chn) <- IPB Inq. Auth. Challenge Response(Algn,Chn) <- IPB
Create and transmit Authentication Request Block Create and transmit Authentication Request Block
Authenticatee Authenticate(Alg1, Ch1) -> IPB Authenticatee Authenticate(Alg1, Ch1) -> IPB
AuthenticateResponse(...) <- IPB AuthenticateResponse(...) <- IPB
. . . . . .
Authenticate(Algm, Chm) -> IPB Authenticate(Algm, Chm) -> IPB
AuthenticateResponse(Res) <- IPB AuthenticateResponse(Res) <- IPB
Create and transmit Authentication Response Block Create and transmit Authentication Response Block
Authenticator Check Authentication Response(Algm,Chm,Res)->IPB Authenticator Check Authentication Response(Algm,Chm,Res)->IPB
Check Auth. Resp. Response() <-IPB Check Auth. Response() <-IPB
Create and transmit Authentication Status Block Create and transmit Authentication Status Block
*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+* *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*
Figure 12 Authentication Message Flows Figure 12 Authentication Message Flows
1. (Authenticator Process) None, one or multiple IOTP Payment Bridges 1. (Authenticator Process) None, one or multiple IOTP Payment Bridges
(IPB) are requested for one or multiple authentication challenge (IPB) are requested for one or multiple authentication challenge
values ("Inquire Authentication Challenge"). Each value is values ("Inquire Authentication Challenge"). Each value is
encapsulated in an IOTP Authentication Request Component. In encapsulated in an IOTP Authentication Request Component. In
addition, the IOTP Application Core may add payment scheme addition, the IOTP Application Core may add payment scheme
independent authentication methods. All of them form the final IOTP independent authentication methods. All of them form the final IOTP
skipping to change at page 43, line 40 skipping to change at page 43, line 40
attribute contains a value which the IOTP attribute contains a value which the IOTP
Aware Application generating the message Aware Application generating the message
reporting the error could not recognize. reporting the error could not recognize.
The AttName attributes of ErrorLocation The AttName attributes of ErrorLocation
elements might refer to the corresponding elements might refer to the corresponding
attribute tags attribute tags
MsgTooLarge Message too large. The message is too large MsgTooLarge Message too large. The message is too large
to be processed by the IOTP Payment Bridge to be processed by the IOTP Payment Bridge
(resp. IOTP Application Core). (or IOTP Application Core).
ElTooLarge Element too large. The element is too large ElTooLarge Element too large. The element is too large
to be processed by the IOTP Payment Bridge to be processed by the IOTP Payment Bridge
(resp. IOTP Application Core). (or IOTP Application Core).
The ElementRef attributes of ErrorLocation The ElementRef attributes of ErrorLocation
elements might might refer to the elements might might refer to the
corresponding elements. corresponding elements.
ValueTooSmall Value too small or early. The value of all ValueTooSmall Value too small or early. The value of all
or part of an element content or an or part of an element content or an
attribute, although valid, is too small. attribute, although valid, is too small.
The ErrorLocation elements might refer to The ErrorLocation elements might refer to
skipping to change at page 86, line 22 skipping to change at page 86, line 22
introduces the Error Codes. introduces the Error Codes.
4.4 General Inquiry API Calls 4.4 General Inquiry API Calls
The following calls are not necessarily assigned to a payment The following calls are not necessarily assigned to a payment
transaction and may be issued at any time. There are no dependencies transaction and may be issued at any time. There are no dependencies
on any other calls. on any other calls.
4.4.1 Remove Payment Log 4.4.1 Remove Payment Log
The IOTP Application Core notifies the IOTP Payment Bridge resp. the The IOTP Application Core notifies the IOTP Payment Bridge and/or the
Existing Payment Software that any record in the Payment Log file, corresponding Existing Payment Software via IOTP Payment Bridge that
that deals with the listed payment transaction, might be removed. any record in the Payment Log file, that deals with the listed
payment transaction, might be removed.
Input Parameters Input Parameters
o Party's Payment Identifier o Party's Payment Identifier
o Wallet Identifier and/or Pass Phrase o Wallet Identifier and/or Pass Phrase
XML definition: XML definition:
<!ELEMENT RemovePaymentLog EMPTY > <!ELEMENT RemovePaymentLog EMPTY >
<!ATTLIST RemovePaymentLog <!ATTLIST RemovePaymentLog
skipping to change at page 94, line 10 skipping to change at page 94, line 10
PayReceiptNameRefs NMTOKENS #IMPLIED > PayReceiptNameRefs NMTOKENS #IMPLIED >
Tables 4 and 5 explain the attributes and elements; Table 3 Tables 4 and 5 explain the attributes and elements; Table 3
introduces the Error Codes. introduces the Error Codes.
4.5.4 Start Payment Inquiry 4.5.4 Start Payment Inquiry
This API function responds any additional payment scheme specific This API function responds any additional payment scheme specific
data that is needed by the Payment Handler for Consumer initiated data that is needed by the Payment Handler for Consumer initiated
payment transaction inquiry processing. Probably, the IOTP Payment payment transaction inquiry processing. Probably, the IOTP Payment
Bridge resp. Existing Payment Software has to determine the payment Bridge (or the corresponding Existing Payment Software) has to
related items that were provided with the "Start Payment Consumer" determine the payment related items that were provided with the
API function call. "Start Payment Consumer" API function call.
Input Parameters Input Parameters
o Consumer Payment Identifier o Consumer Payment Identifier
o Wallet Identifier and/or Pass Phrase o Wallet Identifier and/or Pass Phrase
XML definition: XML definition:
<!ELEMENT StartPaymentInquiry EMPTY > <!ELEMENT StartPaymentInquiry EMPTY >
<!ATTLIST StartPaymentInquiry <!ATTLIST StartPaymentInquiry
skipping to change at page 96, line 4 skipping to change at page 96, line 4
4.6 Other API Calls 4.6 Other API Calls
4.6.1 Manage Payment Software 4.6.1 Manage Payment Software
The following API function notifies the IOTP Payment Bridge about the The following API function notifies the IOTP Payment Bridge about the
intended registration, modification, or deletion of a payment intended registration, modification, or deletion of a payment
instrument. The actual processing is up to the IOTP Payment Bridge. instrument. The actual processing is up to the IOTP Payment Bridge.
This API request may also be used to activate the IOTP Payment Bridge This API request may also be used to activate the IOTP Payment Bridge
resp. Existing Payment Software for general administration purposes. (and the corresponding Existing Payment Software) for general
administration purposes.
Input Parameters Input Parameters
o Brand Identifier o Brand Identifier
o Protocol Identifier o Protocol Identifier
o Any action code: o Any action code:
o New - add new payment method / instrument o New - add new payment method / instrument
o Update - change the payment method's / instrument's data o Update - change the payment method's / instrument's data
o Delete - delete a payment method / instrument o Delete - delete a payment method / instrument
o Wallet Identifier and/or Pass Phrase o Wallet Identifier and/or Pass Phrase
skipping to change at page 96, line 34 skipping to change at page 96, line 35
deletions may require the selection of the payment instrument. A new deletions may require the selection of the payment instrument. A new
wallet might be silently generated on the supplement of a new Wallet wallet might be silently generated on the supplement of a new Wallet
Identifier or after an additional end user acknowledge. The IOTP Identifier or after an additional end user acknowledge. The IOTP
Application Core should not provide any pass phrases for new wallets. Application Core should not provide any pass phrases for new wallets.
Instead, the IOTP Payment Bridge has to request and verify them which Instead, the IOTP Payment Bridge has to request and verify them which
may return their value to the IOTP Application Core in plain text. In may return their value to the IOTP Application Core in plain text. In
addition, the IOTP Payment Bridge returns the supported addition, the IOTP Payment Bridge returns the supported
authentication algorithms when a new brand and protocol pair has been authentication algorithms when a new brand and protocol pair has been
registered. registered.
If the "Action" attribute is omitted, the IOTP Payment Bridge resp. If the "Action" attribute is omitted, the IOTP Payment Bridge which
Existing Payment Software pops up in a general interactive mode. is responsible for the Existing Payment Software pops up in a general
interactive mode.
XML definition: XML definition:
<!ELEMENT ManagePaymentSoftware (BrandPackagedContent*, <!ELEMENT ManagePaymentSoftware (BrandPackagedContent*,
ProtocolAmountPackagedContent*, ProtocolAmountPackagedContent*,
PayProtocolPackagedContent*) > PayProtocolPackagedContent*) >
<!ATTLIST ManagePaymentSoftware <!ATTLIST ManagePaymentSoftware
BrandId CDATA #IMPLIED BrandId CDATA #IMPLIED
ProtocolId CDATA #IMPLIED ProtocolId CDATA #IMPLIED
Action (New | Action (New |
skipping to change at page 97, line 18 skipping to change at page 97, line 18
o Wallet Identifier and/or Pass Phrase o Wallet Identifier and/or Pass Phrase
The IOTP Payment Bridge does not return any information about the set The IOTP Payment Bridge does not return any information about the set
of registered payment instruments because these data items are of registered payment instruments because these data items are
dynamically inferred during the brand selection process at the dynamically inferred during the brand selection process at the
beginning of each IOTP transaction. However, the IOTP Application beginning of each IOTP transaction. However, the IOTP Application
Core has to be notified about new wallets and should be notified Core has to be notified about new wallets and should be notified
about updated and removed wallet (identifier)s". Alternatively, about updated and removed wallet (identifier)s". Alternatively,
removed wallets can be implicitly detected during the next brand removed wallets can be implicitly detected during the next brand
selection phase. Updated wallets do no affect the processing of the selection phase. Updated wallets do no affect the processing of the
IOTP Application Core. The IOTP Payment Software resp. Existing IOTP Application Core. The IOTP Payment Bridge should only support
Payment Software should only support the addition of at most one the addition of at most one wallet because it is not able to report
wallet because it is not able to report multiple additions at once multiple additions at once back to the IOTP Application Core.
back to the IOTP Application Core.
XML definition: XML definition:
<!ELEMENT ManagePaymentSoftwareResponse EMPTY > <!ELEMENT ManagePaymentSoftwareResponse EMPTY >
<!ATTLIST ManagePaymentSoftwareResponse <!ATTLIST ManagePaymentSoftwareResponse
Action (New | Action (New |
Update | Update |
Delete) #IMPLIED Delete) #IMPLIED
WalletID CDATA #IMPLIED WalletID CDATA #IMPLIED
Passphrase CDATA #IMPLIED Passphrase CDATA #IMPLIED
skipping to change at page 102, line 9 skipping to change at page 102, line 9
Masaaki Hiroya and Yoshiaki Kawatsura Masaaki Hiroya and Yoshiaki Kawatsura
Hitachi, Ltd. Hitachi, Ltd.
890 Kashimada Saiwai-ku Kawasaki-shi 890 Kashimada Saiwai-ku Kawasaki-shi
Kanagawa, Japan 212-8567 Kanagawa, Japan 212-8567
E-mail: hiroya@sdl.hitachi.co.jp, kawatura@bisd.hitachi.co.jp E-mail: hiroya@sdl.hitachi.co.jp, kawatura@bisd.hitachi.co.jp
Expiration and File Name Expiration and File Name
This draft expires March 2001. This draft expires March 2001.
Its file name is draft-ietf-trade-iotp-v1.0-papi-01.txt. Its file name is draft-ietf-trade-iotp-v1.0-papi-02.txt.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/