idnits 2.17.1 draft-ietf-trade-iotp-http-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC2801]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 2000) is 8533 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCs 1945' is mentioned on line 76, but not defined -- Looks like a reference, but probably isn't: '2616' on line 76 == Missing Reference: 'RFC2119' is mentioned on line 84, but not defined == Unused Reference: 'RFC 1945' is defined on line 288, but no explicit reference was found in the text == Unused Reference: 'RFC 2119' is defined on line 295, but no explicit reference was found in the text == Unused Reference: 'RFC 2616' is defined on line 306, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 1945 ** Obsolete normative reference: RFC 2048 (Obsoleted by RFC 4288, RFC 4289) ** Obsolete normative reference: RFC 2246 (Obsoleted by RFC 4346) ** Obsolete normative reference: RFC 2376 (Obsoleted by RFC 3023) ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Downref: Normative reference to an Informational RFC: RFC 2801 ** Downref: Normative reference to an Informational RFC: RFC 2802 -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 13 errors (**), 0 flaws (~~), 7 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT IOTP HTTP Supplement 2 Expires December 2000 4 Internet Open Trading Protocol (IOTP) HTTP Supplement 5 -------- ---- ------- -------- ------ ---- ---------- 6 8 Donald E. Eastlake 3rd 9 Chris J. Smith 11 Status of This Document 13 Distribution of this document is unlimited. Comments should be sent 14 to the TRADE WG mailing list or to the 15 authors. 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC2026. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months. Internet-Drafts may be updated, replaced, or obsoleted by 25 other documents at any time. It is not appropriate to use Internet- 26 Drafts as reference material or to cite them other than as a 27 ``working draft'' or ``work in progress.'' 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Abstract 37 Internet Open Trading Protocol (IOTP [RFC 2801]) messages will be 38 carried as XML documents. As such, the goal of mapping to the 39 transport layer is to ensure that the underlying XML documents are 40 carried successfully between the various parties. 42 This documents describes that mapping for the Hyper Text Transport 43 Protocol (HTTP), Versions 1.0 and 1.1. 45 Table of Contents 47 Status of This Document....................................1 48 Abstract...................................................1 50 Table of Contents..........................................2 52 1. Introduction............................................3 53 2. HTTP Servers and Clients................................3 54 3. HTTP Net Locations......................................3 55 4. Consumer Clients........................................3 56 4.1 Starting the IOTP Client and the Merchant IOTP Server..4 57 4.2 Ongoing IOTP Messages..................................4 58 4.3 Stopping an IOTP Transaction...........................5 59 5. Starting the Payment handler and Deliverer IOTP Servers.6 60 6. Security Considerations.................................6 61 7. IANA Considerations.....................................6 63 References.................................................8 65 Authors Addresses..........................................9 66 Expiration and File Name...................................9 68 1. Introduction 70 Internet Open Trading Protocol (IOTP) messages will be carried as XML 71 [XML] documents. As such, the goal of mapping to the transport layer 72 is to ensure that the underlying XML documents are carried 73 successfully between the various parties. 75 This documents describes that mapping for the Hyper Text Transport 76 Protocol (HTTP), Versions 1.0 and 1.1 [RFCs 1945, 2616]. 78 There may be future documents describing IOTP over email (SMTP), TCP, 79 cable TV, or other transports. 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in [RFC2119]. 85 2. HTTP Servers and Clients 87 The structure of IOTP maps on to the structure of HTTP in the 88 following way: 90 The merchant, payment handler, delivery handler, and customer care 91 roles are all represented by HTTP servers. Each may be represented 92 by a separate server, or they may be combined in any combination. 94 The consumer role is represented by an HTTP client. 96 Note: A Merchant, may act in the role of a consumer, for example to 97 deposit electronic cash. In this case the Merchant, as an 98 organization rather than as a role, would need to be supported by an 99 HTTP client. 101 3. HTTP Net Locations 103 The Net Locations contained within the IOTP specification are all 104 URIs [RFC 2396]. If a secure connection is required or desired a 105 secure channel that both the HTTP Server and Client support MUST be 106 used. Examples of such channels are SSL version 3 or TLS [RFC 2246]. 108 4. Consumer Clients 110 In most environments, the consumer agent will initially be an HTML 111 browser. However, current browsers do not provide the needed 112 capability to act as an agent for the consumer for an IOTP 113 transaction. This leads to two requirements: 115 a method of starting and passing control to the IOTP client, and 117 a method of closing down the IOTP client cleanly and passing control 118 back to the HTML browser once the IOTP Transaction has finished. 120 4.1 Starting the IOTP Client and the Merchant IOTP Server 122 At some point, the HTTP client at the consumer will send an HTTP 123 request that is interpreted as an "IOTP Startup Request" by the 124 Merchant HTTP server. This might, for example, be the result of 125 clicking on a "pay" button. This message is a stand-in for a request 126 message of some form and the Merchant Server will respond with the 127 first IOTP Message in the form of an XML document. 129 The MIME type for all IOTP messages is: "APPLICATION/IOTP"; however 130 "APPLICATION/X-IOTP" has been in use for experimentation and 131 development and SHOULD also be recognized. See section 7 below for 132 the MIME type registration template for APPLICATION/IOTP. Because 133 HTTP is binary clean, no content-transfer-encoding is required. (See 134 [RFC 2376] re the application/xml type which has some similar 135 considerations.) 137 This HTTP response will be interpreted by the HTML browser as a 138 request to start the application associated with MIME type 139 "APPLICATION/IOTP", and to pass the content of this message to that 140 application. 142 At this point, the IOTP client will be started and have the first 143 message. 145 IOTP messages are short-lived. Therefore, the HTTP server SHOULD 146 avoid having its responses cached. In HTTP V1.0, the "nocache" 147 pragma can be used. This can be neglected on SSL/TLS secured 148 connections which are not cached and on HTTP POST requests in HTTP 149 v1.1 as in v1.1 POST responses are not cached. 151 4.2 Ongoing IOTP Messages 153 Data from earlier IOTP Messages in a transaction MUST be retained by 154 the IOTP Client so that it may (1) be copied to make up part of later 155 IOTP messages, (2) used in calculations to verify signatures in later 156 IOTP message, (3) be resent in some cases where a request has timed 157 out without response, (4) used as input to the Customer Care role in 158 later versions of IOTP, etc. The way in which the data is copied 159 depends on the IOTP Transaction. The data MUST be retained until the 160 end of the transaction, whether by success, failure, or cancelation, 161 and as long thereafter as it is desired for any of the parties to 162 inquire into it. 164 The IOTP messages contain Net Locations (e.g. the PayReqNetLocn) 165 which for HTTP will contain the URIs to which the IOTP client MUST 166 send IOTP messages. 168 Subsequent IOTP messages (XML documents) will be sent using the POST 169 function of HTTP. The HTTP client MUST perform full HTTP POST 170 requests. 172 The XML documents MUST be sent in a manner compatible with the 173 external encodings allowed by the XML [XML] specification. 175 4.3 Stopping an IOTP Transaction 177 The following should be read in conjunction with [RFC 2801]. 179 An IOTP Transaction is complete when 181 -- the IOTP client decides to fail the IOTP Transaction for some 182 reason either by canceling the transaction or as a result of 183 discovering an error in an IOTP message received, or 185 -- a "time out" occurs or a connection fails, e.g. a response to an 186 IOTP Message, has not been received after some user-defined period 187 of Time (including retransmissions). 189 An IOTP Client which processes an IOTP Transaction which: 191 -- completes successfully (i.e. it has not received an Error Block 192 with a HardError or a Cancel Block) MUST direct the browser to the 193 Net Location specified in SuccessNetLocn in the Protocol Options 194 Component, i.e., cause it to do an HTTP GET with that URL. 196 -- does not complete successfully, because it has received some Error 197 Trading Block, MUST display the information in the Error Message, 198 stop the transaction, and pass control to the browser so that it 199 will do a GET on the Error Net Location specified for the role 200 from which the error was received. 202 -- is cancelled since a Cancel Block has been received, MUST stop the 203 IOTP Transaction and hand control to the browser so that it will 204 do a GET on the on the Cancel Net Location specified for the role 205 from which the Cancel Block was received. 207 -- is in error because an IOTP Message does not conform to this 208 specification, MUST send an IOTP Message containing a Error 209 Trading Block to role from which the erroneous message was 210 received and the ErrorLogNetLoc specified for that role, stop the 211 IOTP Transaction, and hand control to the browser so that it will 212 do a GET from the Error Net Location specified for the role from 213 which the bad message was received. 215 -- has a "time out", MUST display a message describing the time out. 216 May give the user the option of cancelling or retrying and/or may 217 automatically retry. On failure due to time out, treat as an 218 error above. 220 Each implementation of an IOTP client may decide whether or not to 221 terminate the IOTP Client application immediately upon completing an 222 IOTP Transaction or whether to wait until it is closed down as a 223 result of, for example, user shut down or browser shut down. 225 5. Starting the Payment handler and Deliverer IOTP Servers 227 Payment Handler and Deliverer IOTP Servers are started by receiving 228 an IOTP Message which contains: 230 -- for a Payment handler, a Payment Request Block, and 232 -- for a Delivery Handler, a Delivery Request Block 234 6. Security Considerations 236 Security of Internet Open Trade Protocol messages is primarily 237 dependent on signatures within IOTP as described in [RFC 2801] and 238 [RFC 2802]. Privacy protection for IOTP interactions Should can be 239 obtained by using a secure channel for IOTP messages, such as SSL/TLS 240 [RFC 2246]. 242 Note that the security of payment protocols transported by IOTP is 243 the responsibility of those payment protocols, NOT of IOTP. 245 7. IANA Considerations 247 This specification defines the APPLICATION/IOTP MIME type. The 248 registration template is as follows [RFC 2048]: 250 To: ietf-types@iana.org 251 Subject: Registration of MIME media type APPLICATION/IOTP 253 MIME media type name: APPLICATION 255 MIME subtype name: IOTP 257 Required parameters: (none) 259 Optional parameters: charset - see RFC 2376 261 Encoding considerations: Content is XML and may in some cases 262 require quoted printable or base64 encoding. However, no encoding 263 is required for HTTP transport which is expected to be common. 265 Security considerations: IOTP includes provisions for digital 266 authentication but for confidentiality, other mechanisms such as 267 TLS should be used. See RFC 2801 and RFC 2802. 269 Interoperability considerations: See RFC 2801. 271 Published specification: See RFC 2801 and RFC 2802. 273 Applications which use this media type: Internet Open Trading 274 Protocol applications. 276 Additional information: (none) 278 Person & email address to contact for further information: 279 Name: Donald E. Eastlake 3rd 280 Email: Donald.Eastlake@motorola.com 282 Intended usage: COMMON 284 Author/Change controller: IETF 286 References 288 [RFC 1945] - "Hypertext Transfer Protocol -- HTTP/1.0", T. Berners- 289 Lee, R. Fielding & H. Frystyk. May 1996. 291 [RFC 2048] - "Multipurpose Internet Mail Extensions (MIME) Part Four: 292 Registration Procedure", N. Freed, J. Klensin, J. Postel, November 293 1996. 295 [RFC 2119] - "Key words for use in RFCs to Indicate Requirement 296 Levels", S. Bradner, March 1997. 298 [RFC 2246] - "The TLS Protocol Version 1.0", T. Dierks, C. Allen. 299 January 1999. 301 [RFC 2376] - "XML Media Types", E. Whitehead, M. Murata. July 1998. 303 [RFC 2396] - "Uniform Resource Identifiers (URI): Generic Syntax", T. 304 Berners-Lee, R. Fielding, L. Masinter, August 1998. 306 [RFC 2616] - "Hypertext Transfer Protocol -- HTTP/1.1", R. Fielding, 307 J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners- 308 Lee, June 1999. 310 [RFC 2801] - "Internet Open Trading Protocol - IOTP Version 1.0", D. 311 Burdett, April 2000. 313 [RFC 2802] - "Digital Signatures for the v1.0 Internet Open Trading 314 Protocol (IOTP)", K. Davidson, Y. Kawatsura, April 2000 316 [XML] - "Extensible Markup Language (XML) 1.0" 317 , Tim Bray, Jean Paoli, C. M. 318 Sperberg-McQueen, 10 February 1998 320 Authors Addresses 322 Donald E. Eastlake 3rd 323 Motorola 324 140 Forest Avenue 325 Hudson, MA 01749 USA 327 Telephone: +1 978-562-2827(h) 328 +1 508-261-5434(w) 329 FAX: +1 508-261-4447(w) 330 email: Donald.Eastlake@motorola.com 332 Chris J. Smith 333 Royal Bank of Canada 334 277 Front Street West 335 Toronto, Ontario M5V 3A4 CANADA 337 Telephone: +1 416-348-6090 338 FAX: +1 416-348-2210 339 email: chris.smith@royalbank.com 341 Expiration and File Name 343 This draft expires December 2000. 345 Its file name is draft-ietf-trade-iotp-http-07.txt.