Browse Prior Art Database

Internet Open Trading Protocol (IOTP) HTTP Supplement (RFC2935)

IP.com Disclosure Number: IPCOM000005117D
Original Publication Date: 2000-Sep-01
Included in the Prior Art Database: 2001-Aug-15
Document File: 9 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Eastlake: AUTHOR [+2]

Abstract

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 text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 21% of the total text.

Network Working Group D. Eastlake Request for Comments: 2935 Motorola Category: Standards Track C. Smith Royal Bank of Canada

September 2000

Internet Open Trading Protocol (IOTP) HTTP Supplement

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

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.

Table of Contents

1. Introduction................................................... 2 2. HTTP Servers and Clients....................................... 2 3. HTTP Net Locations............................................. 2 4. Consumer Clients............................................... 2 4.1 Starting the IOTP Client and the Merchant IOTP Server.......... 3 4.2 Ongoing IOTP Messages.......................................... 3 4.3 Stopping an IOTP Transaction................................... 4 5. Starting the Payment handler and Deliverer IOTP Servers........ 5 6. Security Considerations........................................ 5 7. IANA Considerations............................................ 5 8. References..................................................... 6 9. Authors' Addresses............................................. 7 10. Full Copyright Statement....................................... 9

Eastlake Smith Standards Track [Page 1]

RFC 2935 IOTP HTTP Supplement September 2000

1. Introduction

Internet Open Trading Protocol (IOTP) [RFC2801] messages will be carried as XML [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 [RFCs 1945, 2616].

There may be future documents describing IOTP over email (SMTP), TCP, cable TV, or other transports.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

2. HTTP Servers and Clients

The structure of IOTP maps on to the structure of HTTP in the following way:

The merchant, payment handler, delivery handler, and customer care roles are all represented by HTTP servers. Each may be represented by a separate server, or they may be combined in any combination.

The consumer role i...