RFC 2935 on IOTP HTTP Supplement
RFC Editor <rfc-ed@ISI.EDU> Wed, 27 September 2000 19:07 UTC
Return-Path: <ietf-trade-errors@lists.eListX.com>
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017SDXK@eListX.com>; Wed, 27 Sep 2000 15:07:25 -0400 (EDT)
Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017SDXJ@eListX.com> (original mail from rfc-ed@ISI.EDU); Wed, 27 Sep 2000 15:07:25 -0400 (EDT)
Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E037SCXE@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 15:07:24 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017SBXD@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 15:07:23 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1K00D5X7SAOO@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 15:07:23 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id MAA10965; Wed, 27 Sep 2000 12:07:03 -0700 (PDT)
Date: Wed, 27 Sep 2000 12:07:03 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Subject: RFC 2935 on IOTP HTTP Supplement
To: IETF-Announce:;
Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com
Message-id: <200009271907.MAA10965@boreas.isi.edu>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_+ottin6vgVc6meTROsqhaA)"
List-Owner: <mailto:ietf-trade-help@lists.elistx.com>
List-Post: <mailto:ietf-trade@lists.elistx.com>
List-Subscribe: <mailto:ietf-trade-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <mailto:ietf-trade-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-trade>
List-Help: <http://lists.elistx.com/doc/email-manage.html>, <mailto:ietf-trade-request@lists.elistx.com?body=help>
A new Request for Comments is now available in online RFC libraries. RFC 2935 Title: Internet Open Trading Protocol (IOTP) HTTP Supplement Author(s): D. Eastlake, C. Smith Status: Standards TraCk Date: September 2000 Mailbox: Donald.Eastlake@motorola.com, chris.smith@royalbank.com Pages: 8 Characters: 16168 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trade-iotp-http-07.txt URL: ftp://ftp.isi.edu/in-notes/rfc2935.txt Internet Open Trading Protocol (IOTP) messages will be carried as Extensible Markup Language (XML) documents. As such, the goal of mapping to the transport layer is to ensure that the underlying XML documents are carried successfully between the various parties. This document describes that mapping for the Hyper Text Transport Protocol (HTTP), Versions 1.0 and 1.1. This document is a product of the Internet Open 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 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.
- RFC 2935 on IOTP HTTP Supplement RFC Editor