RFC 4112 on Electronic Commerce Modeling Language (ECML) Version 2 Specification

rfc-editor@rfc-editor.org Sat, 25 June 2005 00:57 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dlyze-0003ri-Mv; Fri, 24 Jun 2005 20:57:58 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dlyzc-0003rd-DY for ietf-announce@megatron.ietf.org; Fri, 24 Jun 2005 20:57:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15280 for <ietf-announce@ietf.org>; Fri, 24 Jun 2005 20:57:55 -0400 (EDT)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlzOE-0003xS-UV for ietf-announce@ietf.org; Fri, 24 Jun 2005 21:23:24 -0400
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j5P0utt05700; Fri, 24 Jun 2005 17:56:55 -0700 (PDT)
Message-Id: <200506250056.j5P0utt05700@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 24 Jun 2005 17:56:55 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: ietf-trade@lists.elistx.com, rfc-editor@rfc-editor.org
Subject: RFC 4112 on Electronic Commerce Modeling Language (ECML) Version 2 Specification
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

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.
IETF-Announce mailing list