[Search] [pdfized|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02 03 04 05 rfc3505                        Informational
A new Request for Comments is now available in online RFC libraries.

        RFC 3505

        Title:      Electronic Commerce Modeling Language (ECML):
                    Version 2 Requirements
        Author(s):  D. Eastlake
        Status:     Informational
        Date:       March 2003
        Mailbox:    Donald.Eastlake@motorola.com
        Pages:      8
        Characters: 13915
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-trade-ecml2-req-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3505.txt

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

This document is a product of the Internet Open Trading Protocol
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.echo
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.