RFC 2935: Internet Open Trading Protocol (IOTP) HTTP Supplement
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2935
- Published
- September 2000
- Authors
- D. Eastlake 3rd; C. Smith
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2803Digest Values for DOM (DOMHASH)Current
April 2000
- RFC 2802Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)Current
April 2000
- RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent
March 2003
- RFC 2731Encoding Dublin Core Metadata in HTMLObsoleted
December 1999
- RFC 2376XML Media TypesObsoleted
July 1998
- RFC 2807XML Signature RequirementsCurrent
July 2000
- RFC 3075XML-Signature Syntax and ProcessingObsoleted
March 2001
- RFC 3076Canonical XML Version 1.0Current
March 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?