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

--NextPart


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:    [email protected]
        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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="[email protected]"

Content-Type: text/plain
Content-ID: <[email protected]>

RETRIEVE: rfc
DOC-ID: rfc4112

--OtherAccess
Content-Type: Message/External-body; name="rfc4112.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <[email protected]>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IETF-Announce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf-announce

--NextPart--