RFC 4112 on Electronic Commerce Modeling Language (ECML) Version 2 Specification
rfc-editor@rfc-editor.org Sat, 25 June 2005 00:58 UTC
Return-Path: <ietf-trade-errors+ietf-trade-1104-log+40pipe+2elists+2eelistx+2ecom@lists.elistx.com>
Received: from FILTER-ELIST-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0IIM00K02811SY@elistx.com> (original mail from rfc-ed@ISI.EDU) for ietf-trade-1104-log@pipe.lists.elistx.com; Fri, 24 Jun 2005 20:58:13 -0400 (EDT)
Received: from DIRECTORY-DAEMON.elistx.com by elistx.com (PMDF V6.0-025 #44856) id <0IIM00K0180YSX@elistx.com> for ietf-trade@lists.elistx.com; Fri, 24 Jun 2005 20:58:10 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by elistx.com (PMDF V6.0-025 #44856) with ESMTP id <0IIM00K3X80XF8@elistx.com> for ietf-trade@lists.elistx.com; Fri, 24 Jun 2005 20:58:10 -0400 (EDT)
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j5P0utt05700; Fri, 24 Jun 2005 17:56:55 -0700 (PDT)
Date: Fri, 24 Jun 2005 17:56:55 -0700
From: rfc-editor@rfc-editor.org
Subject: RFC 4112 on Electronic Commerce Modeling Language (ECML) Version 2 Specification
Sender: rfc-ed@ISI.EDU
To: ietf-announce@ietf.org
Cc: rfc-editor@rfc-editor.org, ietf-trade@lists.elistx.com
Message-id: <200506250056.j5P0utt05700@boreas.isi.edu>
MIME-version: 1.0
Content-type: Multipart/Mixed; Boundary="NextPart"
X-Virus-Scanned-At: eList eXpress <http://www.elistx.com/>
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/subscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/unsubscribe>, <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-trade-request@lists.elistx.com?body=help>
List-Id: <ietf-trade.lists.elistx.com>
A new Request for Comments is now available in online RFC libraries. RFC 4112 Title: Electronic Commerce Modeling Language (ECML) Version 2 Specification Author(s): D. Eastlake 3rd Status: Standards Track Date: June 2005 Mailbox: Donald.Eastlake@motorola.com Pages: 34 Characters: 72537 Updates: 3106 I-D Tag: draft-ietf-trade-ecml2-spec-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4112.txt Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505. This document is a product of the Internet Open Trading Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.