| 1 |
<pre>Network Working Group D. Eastlake, III |
| 2 |
Request for Comments: 3354 Motorola |
| 3 |
Category: Informational August 2002 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Internet Open Trading Protocol</span> |
| 7 |
<span class="h1">Version 2 Requirements</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. It does |
| 12 |
not specify an Internet standard of any kind. Distribution of this |
| 13 |
memo is unlimited. |
| 14 |
|
| 15 |
Copyright Notice |
| 16 |
|
| 17 |
Copyright (C) The Internet Society (2002). All Rights Reserved. |
| 18 |
|
| 19 |
Abstract |
| 20 |
|
| 21 |
This document gives requirements for the Internet Open Trading |
| 22 |
Protocol (IOTP) Version 2 by describing design principles and scope |
| 23 |
and dividing features into those which will, may, or will not be |
| 24 |
included. |
| 25 |
|
| 26 |
Version 2 of the IOTP will extend the interoperable framework for |
| 27 |
Internet commerce capabilities of Version 1 while replacing the XML |
| 28 |
messaging and digital signature part of IOTP v1 with standards based |
| 29 |
mechanisms. |
| 30 |
|
| 31 |
Table of Contents |
| 32 |
|
| 33 |
<a href="#section-1">1</a>. Introduction ...................................................<a href="#page-2">2</a> |
| 34 |
<a href="#section-2">2</a>. Design Principles and Scope ....................................<a href="#page-2">2</a> |
| 35 |
<a href="#section-3">3</a>. Requirements ...................................................<a href="#page-2">2</a> |
| 36 |
<a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-4">4</a> |
| 37 |
References ........................................................<a href="#page-4">4</a> |
| 38 |
Authors Addresses .................................................<a href="#page-5">5</a> |
| 39 |
Full Copyright Statement ..........................................<a href="#page-6">6</a> |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Eastlake Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc3354">RFC 3354</a> IOTP V2 Requirements August 2002</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
Version 2 of the Internet Open Trading Protocol (IOTP) will extend |
| 60 |
the interoperable framework for Internet commerce capabilities of |
| 61 |
Version 1 [<a href="./rfc2801">RFC 2801</a>] as described in <a href="#section-3">Section 3</a> below. In addition, |
| 62 |
it will replace the ad hoc XML messaging and digital signature [RFC |
| 63 |
2802] parts of IOTP v1 with standards based mechanisms [<a href="./rfc3275">RFC 3275</a>]. |
| 64 |
|
| 65 |
This document gives requirements for the Internet Open Trading |
| 66 |
Protocol (IOTP) Version 2 by describing design principles and scope |
| 67 |
and dividing features into those which will, may, or will not be |
| 68 |
included. |
| 69 |
|
| 70 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Design Principles and Scope</span> |
| 71 |
|
| 72 |
1. The specification must describe the syntax and processing |
| 73 |
necessary for an extension of the interoperable framework for |
| 74 |
Internet commerce described in IOTP V1.0 [<a href="./rfc2801">RFC 2801</a>]. |
| 75 |
|
| 76 |
2. Keep changes to IOTP V1.0 to a minimum. |
| 77 |
|
| 78 |
3. Maintain all existing functionality of IOTP V1.0. |
| 79 |
|
| 80 |
4. Test all XML DTDs and/or Schemas and XML examples in the |
| 81 |
specification to insure that they are well-formed. |
| 82 |
|
| 83 |
5. Create usage/implementation guidance information, probably as a |
| 84 |
separate document. |
| 85 |
|
| 86 |
6. It should be designed to work well with other protocols such as |
| 87 |
ECML [<a href="./rfc3106">RFC 3106</a>]. |
| 88 |
|
| 89 |
7. IOTP Version 2 should be developed as part of the broader Web |
| 90 |
design philosophy of decentralization, URIs, Web data, and |
| 91 |
modularity /layering / extensibility. [<a href="#ref-Berners-Lee" title=""Axioms of Web Architecture: URIs"">Berners-Lee</a>, <a href="#ref-WebData" title=""Web Architecture: Describing and Exchanging Data"">WebData</a>] In |
| 92 |
this context, this standard should take advantage of existing |
| 93 |
provider (and infrastructure) primitives. |
| 94 |
|
| 95 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Requirements</span> |
| 96 |
|
| 97 |
IOTP Version 2 will include the following: |
| 98 |
|
| 99 |
1. Be a superset of IOTP Version 1. |
| 100 |
|
| 101 |
2. Provide for the Dynamic Definition of Trading Sequences. I.E., |
| 102 |
transactions will not be limited, as with v1, to a single payment |
| 103 |
and a single delivery with delivery occurring after payment. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Eastlake Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc3354">RFC 3354</a> IOTP V2 Requirements August 2002</span> |
| 111 |
|
| 112 |
|
| 113 |
Instead, it will be possible to propose an arbitrary sequence of |
| 114 |
transaction steps. |
| 115 |
|
| 116 |
3. Include specification of an Offer Request Block. |
| 117 |
|
| 118 |
4. Support Improved Problem Resolution (extend to cover presentation |
| 119 |
of signed receipt to customer support party, better defined |
| 120 |
Customer Care role, etc.). |
| 121 |
|
| 122 |
5. Add provisions to indicate and handle a payment protocol not |
| 123 |
tunneled through IOTP. |
| 124 |
|
| 125 |
6. Add support for server based wallets. |
| 126 |
|
| 127 |
The following may be include in IOTP v2: |
| 128 |
|
| 129 |
1. Support Repeated/ongoing payments. For example, a means to |
| 130 |
specify that a customer approval covers not only the instant |
| 131 |
purchase but also some limited number of future purchase with some |
| 132 |
total or per purchase spending limit. |
| 133 |
|
| 134 |
2. Enhanced Server to Server messages. For example, a means for a |
| 135 |
Delivery Handler to inform a Payment Handler that goods have |
| 136 |
actually shipped, which may be a pre-condition for making a charge |
| 137 |
against a credit card. |
| 138 |
|
| 139 |
3. Include the ability to add both fields and attributes to existing |
| 140 |
trading blocks in addition to the present ability to add entirely |
| 141 |
new trading blocks. |
| 142 |
|
| 143 |
The following are out of scope for IOTP version 2: |
| 144 |
|
| 145 |
1. Legal or regulatory issues surrounding the implementation of the |
| 146 |
protocol or information systems using it. |
| 147 |
|
| 148 |
2. Design of an XML Messaging Layer. Instead, whatever is or appears |
| 149 |
most likely to become the standard XML messaging layer will be |
| 150 |
used. This includes a standard enveloping, addressing, and error |
| 151 |
reporting framework. |
| 152 |
|
| 153 |
3. Design of XML Digital Signatures. Instead, the existing standard |
| 154 |
[<a href="./rfc3275">RFC 3275</a>] will be used. |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Eastlake Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc3354">RFC 3354</a> IOTP V2 Requirements August 2002</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 170 |
|
| 171 |
As provided above, IOTP v2 will provide optional authentication via |
| 172 |
standards based XML Digital Signatures [<a href="./rfc3275">RFC 3275</a>]; however, neither |
| 173 |
IOTP v1 nor v2 provide a confidentiality mechanism. Both require the |
| 174 |
use of secure channels such as those provided by TLS [<a href="./rfc2246">RFC 2246</a>] or |
| 175 |
IPSEC for confidentiality and depend on the security mechanisms of |
| 176 |
any payment system used in conjunction with them to secure payments. |
| 177 |
|
| 178 |
References |
| 179 |
|
| 180 |
[<a id="ref-Berners-Lee">Berners-Lee</a>] "Axioms of Web Architecture: URIs", |
| 181 |
<<a href="http://www.w3.org/DesignIssues/Axioms.html">http://www.w3.org/DesignIssues/Axioms.html</a>>, "Web |
| 182 |
Architecture from 50,000 feet", |
| 183 |
<<a href="http://www.w3.org/DesignIssues/Architecture.html">http://www.w3.org/DesignIssues/Architecture.html</a>>. |
| 184 |
|
| 185 |
[<a id="ref-RFC 2026">RFC 2026</a>] Bradner, S., "The Internet Standards Process -- |
| 186 |
Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996. |
| 187 |
|
| 188 |
[<a id="ref-RFC 2246">RFC 2246</a>] Dierks, T. and C. Allen, "The TLS Protocol: Version |
| 189 |
1.0", <a href="./rfc2246">RFC 2246</a>, January 1999. |
| 190 |
|
| 191 |
[<a id="ref-RFC 2801">RFC 2801</a>] Burdett, D., "Internet Open Trading Protocol - IOTP |
| 192 |
Version 1.0", <a href="./rfc2801">RFC 2801</a>, April 2000. |
| 193 |
|
| 194 |
[<a id="ref-RFC 2802">RFC 2802</a>] Davidson, K. and Y. Kawatsura, "Digital Signatures for |
| 195 |
the v1.0 Internet Open Trading Protocol (IOTP)", <a href="./rfc2802">RFC</a> |
| 196 |
<a href="./rfc2802">2802</a>, April 2000. |
| 197 |
|
| 198 |
[<a id="ref-RFC 3106">RFC 3106</a>] Eastlake, D. and T. Goldstein, "ECML v1.1: Field Names |
| 199 |
for E-Commerce", <a href="./rfc3106">RFC 3106</a>, April 2001. |
| 200 |
|
| 201 |
[<a id="ref-RFC 3275">RFC 3275</a>] Eastlake, D., Reagle, J. and D. Solo, "XML-Signature |
| 202 |
Syntax and Processing", <a href="./rfc3275">RFC 3275</a>, March 2002. |
| 203 |
|
| 204 |
[<a id="ref-WebData">WebData</a>] "Web Architecture: Describing and Exchanging Data", |
| 205 |
<<a href="http://www.w3.org/1999/04/WebData">http://www.w3.org/1999/04/WebData</a>>. |
| 206 |
|
| 207 |
[<a id="ref-XML">XML</a>] "Extensible Markup Language (XML) 1.0 (Second |
| 208 |
Edition)", <<a href="http://www.w3.org/TR/1998/REC-xml">http://www.w3.org/TR/1998/REC-xml</a>>, T. |
| 209 |
Bray, J. Paoli, C. M. Sperberg-McQueen. |
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Eastlake Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc3354">RFC 3354</a> IOTP V2 Requirements August 2002</span> |
| 223 |
|
| 224 |
|
| 225 |
Author's Addresses |
| 226 |
|
| 227 |
Donald E. Eastlake 3rd |
| 228 |
Motorola |
| 229 |
155 Beaver Street |
| 230 |
Milford, MA 01757 USA |
| 231 |
Phone: +1-508-851-8280 (w) |
| 232 |
+1-508-634-2066 (h) |
| 233 |
EMail: [email protected] |
| 234 |
|
| 235 |
|
| 236 |
|
| 237 |
|
| 238 |
|
| 239 |
|
| 240 |
|
| 241 |
|
| 242 |
|
| 243 |
|
| 244 |
|
| 245 |
|
| 246 |
|
| 247 |
|
| 248 |
|
| 249 |
|
| 250 |
|
| 251 |
|
| 252 |
|
| 253 |
|
| 254 |
|
| 255 |
|
| 256 |
|
| 257 |
|
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Eastlake Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc3354">RFC 3354</a> IOTP V2 Requirements August 2002</span> |
| 279 |
|
| 280 |
|
| 281 |
Full Copyright Statement |
| 282 |
|
| 283 |
Copyright (C) The Internet Society (2002). All Rights Reserved. |
| 284 |
|
| 285 |
This document and translations of it may be copied and furnished to |
| 286 |
others, and derivative works that comment on or otherwise explain it |
| 287 |
or assist in its implementation may be prepared, copied, published |
| 288 |
and distributed, in whole or in part, without restriction of any |
| 289 |
kind, provided that the above copyright notice and this paragraph are |
| 290 |
included on all such copies and derivative works. However, this |
| 291 |
document itself may not be modified in any way, such as by removing |
| 292 |
the copyright notice or references to the Internet Society or other |
| 293 |
Internet organizations, except as needed for the purpose of |
| 294 |
developing Internet standards in which case the procedures for |
| 295 |
copyrights defined in the Internet Standards process must be |
| 296 |
followed, or as required to translate it into languages other than |
| 297 |
English. |
| 298 |
|
| 299 |
The limited permissions granted above are perpetual and will not be |
| 300 |
revoked by the Internet Society or its successors or assigns. |
| 301 |
|
| 302 |
This document and the information contained herein is provided on an |
| 303 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 304 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 305 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 306 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 307 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 308 |
|
| 309 |
Acknowledgement |
| 310 |
|
| 311 |
Funding for the RFC Editor function is currently provided by the |
| 312 |
Internet Society. |
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Eastlake Informational [Page 6] |
| 333 |
</pre> |