Internet Open Trading Protocol Version 2 Requirements
draft-ietf-trade-iotp2-req-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3354.
Author Donald E. Eastlake 3rd
Last updated 2015-10-14 (Latest revision 2002-01-03)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3354 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Patrik Fältström
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-trade-iotp2-req-02 
A new Request for Comments is now available in online RFC libraries.

        RFC 3354

        Title:      Internet Open Trading Protocol Version 2
                    Requirements 
        Author(s):  D. Eastlake, III
        Status:     Informational
        Date:       August 2002
        Mailbox:    Donald.Eastlake@motorola.com
        Pages:      6
        Characters: 9671
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-trade-iotp2-req-02.txt

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

This document gives requirements for the Internet Open Trading
Protocol (IOTP) Version 2 by describing design principles and scope
and dividing features into those which will, may, or will not be
included.

Version 2 of the IOTP will extend the interoperable framework for
Internet commerce capabilities of Version 1 while replacing the XML
messaging and digital signature part of IOTP v1 with standards based
mechanisms.

This document is a product of the 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
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.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.