RFC 3504 on Internet Open Trading Protocol (IOTP) Version 1, Errata

rfc-editor@rfc-editor.org Fri, 14 March 2003 00:20 UTC

Return-Path: <ietf-trade-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HBP00G04QA6MS@eListX.com> (original mail from rfc-ed@ISI.EDU); Thu, 13 Mar 2003 19:20:30 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HBP00G01QA2MK@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Thu, 13 Mar 2003 19:20:29 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0HBP00G01QA1MJ@eListX.com> for ietf-trade@elist.lists.elistx.com (ORCPT ietf-trade@lists.elistx.com); Thu, 13 Mar 2003 19:20:25 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBP00C7BQA1I8@eListX.com> for ietf-trade@lists.elistx.com; Thu, 13 Mar 2003 19:20:25 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h2E0JZZ26570; Thu, 13 Mar 2003 16:19:35 -0800 (PST)
Date: Thu, 13 Mar 2003 16:19:35 -0800
From: rfc-editor@rfc-editor.org
Subject: RFC 3504 on Internet Open Trading Protocol (IOTP) Version 1, Errata
Sender: rfc-ed@ISI.EDU
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, ietf-trade@lists.elistx.com
Message-id: <200303140019.h2E0JZZ26570@gamma.isi.edu>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_+LXcU/SQ+CSclZyW9MQ6lQ)"
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <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 3504

        Title:      Internet Open Trading Protocol (IOTP)
                    Version 1, Errata
        Author(s):  D. Eastlake
        Status:     Informational
        Date:       March 2003
        Mailbox:    Donald.Eastlake@motorola.com
        Pages:      6
        Characters: 8655
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-trade-iotp-v1-errata-01.txt

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


Since the publication of the RFCs specifying Version 1.0 of the
Internet Open Trading Protocol (IOTP), some errors have been noted.
This informational document lists these errors and provides
corrections for them.

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
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.


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.
ftp://ftp.isi.edu/in-notes/rfc3504.txt"><ftp://ftp.isi.edu/in-notes/rfc3504.txt>