Electronic Commerce Modeling Language (ECML): Version 2 Requirements
RFC 3505

Document Type RFC - Informational (March 2003; No errata)
Last updated 2015-10-14
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3505 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Patrik Fältström
Send notices to (None)
Network Working Group                                        D. Eastlake
Request for Comments: 3505                                      Motorola
Category: Informational                                       March 2003

             Electronic Commerce Modeling Language (ECML):
                         Version 2 Requirements

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

   1. Introduction.................................................... 2
      1.1 Relationship to Other Standards............................. 2
   2. Design Principles and Scope..................................... 2
   3. Requirements.................................................... 3
      3.1 Payment Processing Elements................................. 3
      3.2 Payment Processing Types.................................... 3
      3.3 XML Data Model and Syntax................................... 4
      3.4 Implementation.............................................. 4
      3.5 Detailed Requests........................................... 4
   4. Security Considerations......................................... 5
   5. References...................................................... 5
   6. Acknowledgments................................................. 6
   7. Authors' Addresses.............................................. 7
   8. Full Copyright Statement........................................ 8

Eastlake                     Informational                      [Page 1]
RFC 3505                 ECML: v2 Requirements                March 2003

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
   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".

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
   Versions 1 and 1.1 of ECML [RFC 3106].  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-repudiated transactions, automatic payment
   scheme selection, and smart card support.

2. Design Principles and Scope

   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 [RFC 3106]
      to a minimum.

Eastlake                     Informational                      [Page 2]
RFC 3505                 ECML: v2 Requirements                March 2003

   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
Show full document text