RFC 3504 on Internet Open Trading Protocol (IOTP) Version 1, Errata
rfc-editor@rfc-editor.org Fri, 14 March 2003 00:25 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26562; Thu, 13 Mar 2003 19:25:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18td4p-0006SC-00 for ietf-announce-list@ran.ietf.org; Thu, 13 Mar 2003 19:29:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18td4g-0006Q7-00 for all-ietf@ran.ietf.org; Thu, 13 Mar 2003 19:29:26 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26400 for <all-ietf@ietf.org>; Thu, 13 Mar 2003 19:17:26 -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)
Message-Id: <200303140019.h2E0JZZ26570@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3504 on Internet Open Trading Protocol (IOTP) Version 1, Errata
Cc: rfc-editor@rfc-editor.org, ietf-trade@lists.elistx.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 13 Mar 2003 16:19:35 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
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.