One document matched: draft-ietf-trade-ecml2-req-01.txt
Differences from draft-ietf-trade-ecml2-req-00.txt
INTERNET DRAFT Jon W. Parsons (SeraNova)
David Shepherd (IBM)
Donald E. Eastlake 3rd (Motorola)
Expires September 2001 March 2001
Electronic Commerce Modeling Language (ECML):
Version 2 Requirements
<draft-ietf-trade-ecml2-req-01.txt>
Status of this Memo
Distribution of this document is unlimited. Comments should be sent
to the authors or the IETF TRADE working group <ietf-
trade@lists.elistx.com>.
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) 2001, The Internet Society. 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 XML syntax,
data model, format, payment processing, and external requirements.
J. Parsons, D. Shepherd, D. Eastlake [Page 1]
INTERNET-DRAFT ECML v2 Requirements March 2001
Table of Contents
Status of this Memo........................................1
Copyright Notice...........................................1
Abstract...................................................1
Table of Contents..........................................2
1. Introduction............................................3
1.1 Relationship to Other Standards........................3
2. Design Principles and Scope.............................3
3. Requirements............................................4
3.1 Payment Processing Elements............................4
3.2 Payment Processing Types...............................4
3.3 XML Data Model and Syntax..............................5
3.4 Implementation.........................................5
3.5 Detailed Requests......................................5
4. Security Considerations.................................6
References.................................................6
Authors Addresses..........................................8
Full Copyright Statement...................................9
File name and Expiration...................................9
J. Parsons, D. Shepherd, D. Eastlake [Page 2]
INTERNET-DRAFT ECML v2 Requirements March 2001
1. Introduction
ECML Version 2.0 will describe the syntax of a class of data objects
called Payment Processing Objects. This will involve the development
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, 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".
1.1 Relationship to Other Standards
The set of fields documented herein was started by the ECML Alliance
[ECML] which developed the North American / HTML form field oriented
Version 1 of ECML [RFC 2706, v1.1]. 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], [JCM], or other sources.
ECML Version 2.0 is not a replacement or alternative to TLS [RFC
2246], SET [SET], EMV [EMV], XML [XML], or IOTP [RFC 2801]. These are
important standards that provide functionality such as
confidentiality, non-repudiatable transactions, automatable payment
scheme selection, and smart card support.
2. Design Principles and Scope
1. The specification must describe the fields necessary to process a
payment describing the XML syntax and content in particular.
2. Keep the addition of fields beyond those in ECML v1.1 [RFC v1.1]
to a minimum.
3. Maintain all existing functionality from ECML v1.1. In essence,
J. Parsons, D. Shepherd, D. Eastlake [Page 3]
INTERNET-DRAFT ECML v2 Requirements March 2001
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, Line of Credit,
Purchasing Card and eCheck. 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 B2B payment vehicles, such as
B2B Wallets, Marketplaces, etc.
7. Test all XML DTDs and XML examples in the specification to insure
that they are well-formed XML.
8. Create an usage/implementation guide section of the specification
to cover additional use cases for functionality included.
9. ECML version 2 may include the concept of an offer.
10. 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] In this context, this standard
should take advantage of existing provider (and infrastructure)
primitives.
3. Requirements
3.1 Payment Processing Elements
1. Cost
2. Receipt
3. Currency
4. Card
5. Payment
6. Bank/Telco
3.2 Payment Processing Types
1. All current Processing types for ECML 1.1
2. ACH
3. eCheck
J. Parsons, D. Shepherd, D. Eastlake [Page 4]
INTERNET-DRAFT ECML v2 Requirements March 2001
4. Line Of Credit (LOC)
5. Mobile phone payments
6. PDA payments
3.3 XML Data Model and Syntax
1. A well-formed DTD needs to be developed to include new fields
in this standard.
2. W3C Schema note may be drafted to document changes to the
schema.
3.4 Implementation
1. The ECML version 2 specification should meet the requirements
of the following applications:
1. Internet Open Trading Protocol v1.0 [IOTP]
2. Others ???
2. Check against representative LOC, ACH, eCheck, Mobile Phone and
PDA processes.
3. Compare completeness against (in accordance with standard's
goals:)
1. [ECML v1.1]
2. [P3P NOTE]
3. [ISO 8583]
4. [JCM]
5. cXML
6. EBXML
7. BizTalk
3.5 Detailed Requests
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.
J. Parsons, D. Shepherd, D. Eastlake [Page 5]
INTERNET-DRAFT ECML v2 Requirements March 2001
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.
4. Security Considerations
Some ECML fields contain sensitive private information. ECML is
dependent upon the security of the infrastructure of transmission
providers that use the standard format. ECML does not add any
security to this infrastructure. See the ECML v2 specification for
more detailed privacy and security considerations.
References
[Berners-Lee] - "Axioms of Web Architecture: URIs",
<http://www.w3.org/DesignIssues/Axioms.html>, "Web Architecture from
50,000 feet", <http://www.w3.org/DesignIssues/Architecture.html>
[eCheck] - <http://www.echeck.org>
[ECML] - The ECML Alliance, <http://www.ecml.org>.
[HTML] - "HTML 3.2 Reference Specification",
<http://www.w3.org/TR/REC-html32.html>, D. Raggett, January 1997.
[ISO 8583] - "Financial transaction card originated messages --
Interchange message specifications", International Standards
Organization, 1993.
[JCM] - "Java Commerce Messages", Sun Microsystems, IBM, April 1998.
[EMV] - <http://www.emvco.org/specifications.cfm>
[RFC 2026] - "The Internet Standards Process -- Revision 3", S.
Bradner, October 1996.
[RFC 2246] - "The TLS Protocol: Version 1.0", T. Dierks, C. Allen.
January 1999.
[RFC 2706] - "ECML v1: Field Names for E-Commerce", D. Eastlake, T.
Goldstein, October 1999.
[RFC 2801] - "Internet Open Trading Protocol - IOTP Version 1.0", D.
J. Parsons, D. Shepherd, D. Eastlake [Page 6]
INTERNET-DRAFT ECML v2 Requirements March 2001
Burdett, April 2000.
[RFC v1.1] - "ECML v1.1: Field Names for E-Commerce", D. Eastlake, T.
Goldstein, draft-eastlake-ecom-fields2-05.txt, in RFC Editor's queue
for publication as an non-WG Informational RFC.
[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,
<http://www.w3.org/TR/WD-P3P/basedata.html>.
[P3P ECOM] - "Using P3P for E-Commerce", J. Coco, S. Klien, D.
Schutzer, S. Yen, A. Slater, November 1999,
<http://www.w3.org/TR/P3P-for-ecommerce>.
[SET] - "Secure Electronic Transaction",
<http://www.setco.org/set_specifications.html>.
[WebData] - "Web Architecture: Describing and Exchanging Data",
<http://www.w3.org/1999/04/WebData>
[XML] - "Extensible Markup Language (XML) 1.0 (Second Edition)",
<http://www.w3.org/TR/1998/REC-xml>, T. Bray, J. Paoli, C. M.
Sperberg-McQueen.
J. Parsons, D. Shepherd, D. Eastlake [Page 7]
INTERNET-DRAFT ECML v2 Requirements March 2001
Authors Addresses
Jon W. Parsons
SeraNova
10210 N. 25th Avenue
Phoenix, AZ 85012
Phone: +1-602-674-1853
EMail: jon.parsons@seranova.com
David Shepherd
IBM
Secure Payments Systems
P. O. Box 12195
3039 Cornwallis Road
Research Triangle Park, NC 27709-2195 USA
Phone: +1-919-254-5194
Email: dshepher@us.ibm.com
Donald E. Eastlake 3rd
Motorola
155 Beaver Street
Milford, MA 01757 USA
Phone: +1-508-261-5434 (w)
+1-508-634-2066 (h)
Email: Donald.Eastlake@motorola.com
J. Parsons, D. Shepherd, D. Eastlake [Page 8]
INTERNET-DRAFT ECML v2 Requirements March 2001
Full Copyright Statement
Copyright (c) 2001 The Internet Society, 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.
File name and Expiration
This file is draft-ietf-trade-ecml2-req-01.txt.
It expires September 2001.
J. Parsons, D. Shepherd, D. Eastlake [Page 9]
| PAFTECH AB 2003-2026 | 2026-04-24 04:43:36 |