1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
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
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Network Working Group D. Eastlake
Request for Comments: 3505 Motorola
Category: Informational March 2003
<span class="h1">Electronic Commerce Modeling Language (ECML):</span>
<span class="h1">Version 2 Requirements</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document lists the design principles, scope, and requirements
for the Electronic Commerce Modeling Language (ECML) version 2
specification. It includes requirements as they relate to Extensible
Markup Language (XML) syntax, data model, format, and payment
processing.
Table of Contents
<a href="#section-1">1</a>. Introduction.................................................... <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a> Relationship to Other Standards............................. <a href="#page-2">2</a>
<a href="#section-2">2</a>. Design Principles and Scope..................................... <a href="#page-2">2</a>
<a href="#section-3">3</a>. Requirements.................................................... <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a> Payment Processing Elements................................. <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a> Payment Processing Types.................................... <a href="#page-3">3</a>
<a href="#section-3.3">3.3</a> XML Data Model and Syntax................................... <a href="#page-4">4</a>
<a href="#section-3.4">3.4</a> Implementation.............................................. <a href="#page-4">4</a>
<a href="#section-3.5">3.5</a> Detailed Requests........................................... <a href="#page-4">4</a>
<a href="#section-4">4</a>. Security Considerations......................................... <a href="#page-5">5</a>
<a href="#section-5">5</a>. References...................................................... <a href="#page-5">5</a>
<a href="#section-6">6</a>. Acknowledgments................................................. <a href="#page-6">6</a>
<a href="#section-7">7</a>. Authors' Addresses.............................................. <a href="#page-7">7</a>
<a href="#section-8">8</a>. Full Copyright Statement........................................ <a href="#page-8">8</a>
<span class="grey">Eastlake Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
ECML Version 2.0 will describe the syntax of a class of data objects
called Payment Processing Objects. This will involve the development
of a hierarchically organized set of data elements and an XML syntax
for payment transaction information for both electronic wallets and
Business to Business (B2B) payment types such as credit card,
electronic check, line of credit, ACH (Automated Clearing House,)
Mobile Phone Payments, and PDA Payments.
This document lists the design principles, scope, and requirements
over three things: (1) the scope of work available to the WG, (2) the
ECML version 2 specification, and (3) applications that implement the
specification. It includes requirements as they relate to the
payment element syntax, data model, format, implementation, and
external requirements. Those things that are required are designated
as "must", those things that are optional are designated by "may",
those things that are optional but recommended are designated as
"should".
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Relationship to Other Standards</span>
The set of fields documented herein was started by the ECML Alliance
[<a href="#ref-ECML" title="The ECML Alliance">ECML</a>] which developed the North American / HTML form field oriented
Versions 1 and 1.1 of ECML [<a href="./rfc3106">RFC 3106</a>]. Control and development of
future versions of the standard has been transferred to the IETF.
The ECML Version 1 fields were initially derived from and are
consistent with the W3C P3P base data schema [P3P BASE]. Version 2
extends the fields provided to encompass [P3P ECOM] and selected
additional fields from [ISO 8583], [<a href="#ref-JCM" title=""Java Commerce Messages"">JCM</a>], or other sources.
ECML Version 2.0 is not a replacement or alternative to TLS [RFC
2246], SET [<a href="#ref-SET" title=""Secure Electronic Transaction"">SET</a>], EMV [<a href="#ref-EMV" title="MasterCard">EMV</a>], XML [<a href="#ref-XML" title=""Extensible Markup Language (XML) 1.0 (Second Edition)"">XML</a>], or IOTP [<a href="./rfc2801">RFC 2801</a>]. These
are important standards that provide functionality such as
confidentiality, non-repudiated transactions, automatic payment
scheme selection, and smart card support.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Design Principles and Scope</span>
1. The specification must describe the fields necessary to process a
payment between a consumer and merchant or between two businesses,
describing the XML syntax and content in particular.
2. Keep the addition of fields beyond those in ECML v1.1 [<a href="./rfc3106">RFC 3106</a>]
to a minimum.
<span class="grey">Eastlake Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
3. Maintain all existing functionality from ECML v1.1. In essence,
ECML v2 should be a superset of ECML v1.1.
4. Increase the flexibility of the standard to include other forms of
payments. These include ACH, Mobile Phone, PDA, Purchasing Card
and electronic check. See [P3P ECOM, JCM], etc.
5. Allow for use of a common and uniform DTD with back-end payment
systems such as Enterprise Resource Provision (ERP), Card Line
Item Detail (LID) Level II & Level III, etc.
6. Allow for use of the standard with Business to Business (B2B)
payment vehicles, such as B2B Wallets, Marketplaces, etc.
7. Create a usage/implementation guide section of the specification
to cover additional use cases for functionality included.
8. ECML version 2 may include the concept of an offer.
9. ECML version 2 should be developed as part of the broader Web
design philosophy of decentralization, URIs, Web data, modularity
/layering / extensibility, and assertions as statements about
statements. [Berners-Lee, WebData, XML, XML Name] In this
context, this standard should take advantage of existing provider
(and infrastructure) primitives.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Requirements</span>
ECML v2 must cover the data types and other requirements enumerated
in this section. It should provide for asserting and querying
relevant element values.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Payment Processing Elements</span>
1. Cost
2. Receipt
3. Currency
4. Card
5. Payment
6. Bank/Telco
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Payment Processing Types</span>
1. All current Processing types for ECML 1.1 [<a href="./rfc3106">RFC 3106</a>].
2. Automated Clearing house [<a href="#ref-ACH">ACH</a>]
3. Electronic check [<a href="#ref-eCheck">eCheck</a>]
4. Mobile phone payments
5. PDA payments
<span class="grey">Eastlake Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> XML Data Model and Syntax</span>
1. A well-formed DTD and possibly schema need to be developed to
include new fields in this standard.
2. A W3C Note may be drafted to document changes from [W3C ECOM].
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Implementation</span>
1. The ECML version 2 specification should meet the requirements of
the following applications:
a. Internet Open Trading Protocol v1.0 [IOTP]
b. Check against representative ACH, electronic check, and Mobile
Phone payment setup.
2. Test all XML DTDs, schemas and XML examples included the
specification to insure that they are well-formed XML.
3. Compare completeness against (in accordance with standard's
goals:)
1. ECML v1.1 [<a href="./rfc3106">RFC 3106</a>]
2. Using P3P for E-Commerce [P3P NOTE]
3. Financial transaction card originated messages [ISO 8583]
4. ebXML
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Detailed Requests</span>
The following are specific comments received on claimed deficiencies
in ECML v1.1 and should all be considered for possible inclusion in
ECML v2.
1. Increase Last Name field minimum required support to at least 22
characters.
2. Improved Internationalization support.
3. Longer minimum supported telephone number and email fields.
4. Provide a "translation field" which would specify a mapping
between existing fields and ECML specified fields. The addition
of such a field in ECML v2 (which would normally be hidden when
presented in HTML) would permit ECML support with no change to
existing fields or code. ECML code could fill in existing fields
based on the ECML field they map to.
<span class="grey">Eastlake Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Many ECML fields contain sensitive private information. ECML is
dependent upon:
- the security of the transmission infrastructure used to send such
private information
- the security of applications which store or release such sensitive
information.
ECML need not add any security mechanisms to this infrastructure or
these applications. The ECML v2 specification must include adequate
warnings and suggested courses of action to protect this information.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
[<a id="ref-ACH">ACH</a>] Automated Clearing House <<a href="http://www.nacha.org">http://www.nacha.org</a>>
[<a id="ref-Berners-Lee">Berners-Lee</a>] "Axioms of Web Architecture: URIs",
<<a href="http://www.w3.org/DesignIssues/Axioms.html">http://www.w3.org/DesignIssues/Axioms.html</a>>, "Web
Architecture from 50,000 feet",
<<a href="http://www.w3.org/DesignIssues/Architecture.html">http://www.w3.org/DesignIssues/Architecture.html</a>>
[<a id="ref-eCheck">eCheck</a>] Electronic Check <<a href="http://www.echeck.org">http://www.echeck.org</a>>
[<a id="ref-ECML">ECML</a>] Electronic Commerce Modeling Language, The ECML
Alliance, <<a href="http://www.oasis-open.org/cover/ecml.html">http://www.oasis-open.org/cover/ecml.html</a>>.
[<a id="ref-HTML">HTML</a>] "HTML 3.2 Reference Specification", Hyper Text Markup
Language, <<a href="http://www.w3.org/TR/REC-html32.html">http://www.w3.org/TR/REC-html32.html</a>>, D.
Raggett, January 1997.
[ISO 8583] "Financial transaction card originated messages --
Interchange message specifications", International
Standards Organization, 1993.
[<a id="ref-JCM">JCM</a>] "Java Commerce Messages", Sun Microsystems, IBM, April
1998.
[<a id="ref-EMV">EMV</a>] The EuroCard, MasterCard, Visa chip card protocol
standard. <<a href="http://www.emvco.org">http://www.emvco.org</a>>
[<a id="ref-RFC 2026">RFC 2026</a>] Bradner, S., "The Internet Standards Process --
Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
[<a id="ref-RFC 2246">RFC 2246</a>] Dierks, T. and C. Allen, "The TLS Protocol: Version
1.0", <a href="./rfc2246">RFC 2246</a>, January 1999.
<span class="grey">Eastlake Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
[<a id="ref-RFC 2801">RFC 2801</a>] "Internet Open Trading Protocol - IOTP Version 1.0", D.
Burdett, April 2000.
[<a id="ref-RFC 3106">RFC 3106</a>] Eastlake, D. and T. Goldstein, "ECML v1.1: Field Names
for E-Commerce", <a href="./rfc3106">RFC 3106</a>, April 2001.
[P3P BASE] "The Platform for Privacy Preferences 1.0 (P3P1.0)
Specification", L. Cranor, M. Langheinrich, M.
Marchiori, M. Presler-Marshall, J. Reagle, December
2000, <<a href="http://www.w3.org/TR/WD-P3P/basedata.html">http://www.w3.org/TR/WD-P3P/basedata.html</a>>.
[P3P ECOM] "Using P3P for E-Commerce", J. Coco, S. Klein, D.
Schutzer, S. Yen, A. Slater, November 1999,
<<a href="http://www.w3.org/TR/P3P-for-ecommerce">http://www.w3.org/TR/P3P-for-ecommerce</a>>.
[<a id="ref-SET">SET</a>] "Secure Electronic Transaction",
<<a href="http://www.setco.org/set_specifications.html">http://www.setco.org/set_specifications.html</a>>.
[<a id="ref-WebData">WebData</a>] "Web Architecture: Describing and Exchanging Data",
<<a href="http://www.w3.org/1999/04/WebData">http://www.w3.org/1999/04/WebData</a>>
[<a id="ref-XML">XML</a>] "Extensible Markup Language (XML) 1.0 (Second
Edition)", <<a href="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</a>>, T. Bray, J.
Paoli, C. M. Sperberg-McQueen.
[XML Name] "Namespaces in XML", Tim Bray, Dave Hollander, Andrew
Layman, 14 January 1999.
<<a href="http://www.w3.org/TR/REC-xml-names">http://www.w3.org/TR/REC-xml-names</a>>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Jon W. Parsons and David Shepherd contributed substantially to this
document.
<span class="grey">Eastlake Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authors' Addresses</span>
Donald E. Eastlake 3rd
Motorola
155 Beaver Street
Milford, MA 01757 USA
Phone: +1-508-851-8280 (w)
+1-508-634-2066 (h)
EMail: Donald.Eastlake@motorola.com
<span class="grey">Eastlake Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3505">RFC 3505</a> ECML: v2 Requirements March 2003</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Eastlake Informational [Page 8]
</pre>
|
