Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K01UPPJK@eListX.com>; Wed, 31 May 2000 15:13:01 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K01UPOJJ@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 31 May 2000 15:13:00 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K03UPOJH@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 31 May 2000 15:13:00 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K01UPNJG@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 31 May 2000 15:12:59 -0400 (EDT) Received: from torque.pothole.com ([38.138.52.132]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FVF00K1IUPL7B@eListX.com> for ietf-trade@lists.eListX.com; Wed, 31 May 2000 15:12:59 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id PAA10925 for ietf-trade@lists.elistx.com; Wed, 31 May 2000 15:14:36 -0400 (EDT) Date: Wed, 31 May 2000 15:14:35 -0400 From: "Donald E. Eastlake 3rd" Subject: HTTP Supplement and MIME Type Detector drafts To: ietf-trade@lists.eListX.com Message-id: <200005311914.PAA10925@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp Hi, This is the start of a two week Working Group last call on the draft-ietf-trade-mime-detector-03.txt draft. This is an informational document on determining what sort of MIME types a browser supports. Since there were no objections to the draft-ietf-trade-iotp-http-05.txt draft as per below, I'm going to do a quick update onit to replace draft references with RFC references and forward it to the IESG for their approval for publication as a Proposed Standard RFC. Thanks, Donald Date: Wed, 03 May 2000 15:35:35 -0400 From: "Donald E. Eastlake 3rd" Subject: WG Last CAll draft-ietf-trade-iotp-http-05.txt To: ietf-trade@lists.eListX.com Message-id: <200005031935.PAA01825@torque.pothole.com> Since there have been no comments or suggestions on this draft for some time and earlier comments and suggestions have generally been incorporated, I'm calling a two week Working Group Last Call on this draft. I intend to forward the draft to the IESG as is or with minor changes based on future comments sometime on or after 17 May. Thanks, Donald ===================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 140 Forest Avenue +1 914-276-2668(h) Hudson, MA 01749 USA +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00701BKRS5@eListX.com>; Tue, 16 May 2000 18:24:27 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00701BKRS4@eListX.com> (original mail from CHRIS.SMITH@ROYALBANK.COM) ; Tue, 16 May 2000 18:24:27 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00703BKQS2@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 18:24:27 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00701BKQS1@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 18:24:26 -0400 (EDT) Received: from smtp2.royalbank.com (smtp2.royalbank.com [198.96.131.29]) by eListX.com (PMDF V5.2-33 #43584) with SMTP id <0FUO00746BKP0D@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 18:24:26 -0400 (EDT) Received: from wsecure1.royalbank.com by smtp2.royalbank.com via smtpd (for one.elistx.com [209.116.252.130]) with SMTP; Tue, 16 May 2000 22:20:32 +0000 (UT) Received: from 10.224.0.67 by se001019.royalbank.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Tue, 16 May 2000 18:20:17 -0400 Received: by se001017.royalbank.com with Internet Mail Service ( 5.5.2650.21) id ; Tue, 16 May 2000 18:20:17 -0400 Date: Tue, 16 May 2000 18:20:18 -0400 From: "Smith, Chris " Subject: RE: RFC 2801 on IOTP/1.0 To: "ietf-trade@lists. eListX. com (E-mail)" Message-id: <2B30A9965635D311A29F002035297FFB0461546C@se001010.rbc1.royalbank.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: multipart/alternative; boundary="Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ)" X-Server-Uuid: 47ce64ae-6caa-11d3-9dcc-00902732b24c X-WSS-ID: 153F162B170333-01-01 List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable > -----Original Message----- > From: RFC Editor [mailto:rfc-ed@ISI.EDU] > Sent: May 16, 2000 01:32 PM > Cc: rfc-ed@ISI.EDU; ietf-trade@lists.eListX.com > Subject: RFC 2801 on IOTP/1.0 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 > RFC 2801 >=20 > Title: Internet Open Trading Protocol - IOTP Version 1.0 > Author(s): D. Burdett > Status: Informational > Date: April 2000 > Mailbox: david.burdett@commerceone.com Congratulations to ALL - the uncountable all, for getting this far. Now comes the hard part - making RFC2801 as recognizable as, say 822. > Pages: 290 > Characters: 598794 I've confirmed it against the official list, by sorting all of the RFCs in order of size. RFC 2801 is the=20 largest text RFC in existence. ------------------------------------------------------------=20 =A0Chris = Smith=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 +1.416.348.6090=20 =A0Royal = Bank=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = chris.smith@royalbank.com=20 --Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: quoted-printable RE: RFC 2801 on IOTP/1.0

> -----Original Message-----
> From: RFC Editor [mailto:rfc-ed@ISI.EDU]
> Sent: May 16, 2000 01:32 PM
> Cc: rfc-ed@ISI.EDU; = ietf-trade@lists.eListX.com
> Subject: RFC 2801 on IOTP/1.0
>
> A new Request for Comments is now available in = online RFC libraries.
>
>         = RFC 2801
>
>         = Title:            = Internet Open Trading Protocol - IOTP Version 1.0
>         = Author(s):  D. Burdett
>         = Status:     Informational
>         = Date:       April 2000
>         = Mailbox:    david.burdett@commerceone.com

Congratulations to ALL - the uncountable all, for = getting this far.

Now comes the hard part - making RFC2801 as = recognizable as, say 822.

>         = Pages:      290
>         = Characters: 598794

I've confirmed it against the official list, by = sorting
all of the RFCs in order of size. RFC 2801 is the =
largest text RFC in existence.

------------------------------------------------------------ =
=A0Chris = Smith=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 +1.416.348.6090
=A0Royal = Bank=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = chris.smith@royalbank.com

--Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010IPM4@eListX.com>; Tue, 16 May 2000 14:25:38 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010I0M3@eListX.com> (original mail from ietf-trade-moderator@lists.eListX.com); Tue, 16 May 2000 14:25:12 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006070HZLX@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 14:25:11 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YILA0@eListX.com> for ietf-trade-moderator@moderate.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:21 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YIL9Z@eListX.com> for ietf-trade-moderator@lists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:21 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00603YIK9X@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:20 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YIK9W@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:20 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUN002K3YIBN0@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 13:42:20 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA17518; Tue, 16 May 2000 10:38:03 -0700 (PDT) Date: Tue, 16 May 2000 10:38:03 -0700 From: RFC Editor Subject: RFC 2803 on Digest Values for DOM (DOMHASH) To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200005161738.KAA17518@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA) A new Request for Comments is now available in online RFC libraries. RFC 2803 Title: Digest Values for DOM (DOMHASH) Author(s): H. Maruyama, K. Tamura, N. Uramoto Status: Informational Date: April 2000 Mailbox: maruyama@jp.ibm.com, kent@trl.ibm.co.jp, uramoto@jp.ibm.com Pages: 11 Characters: 22552 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2803.txt This memo defines a clear and unambiguous definition of digest (hash) values of the XML objects regardless of the surface string variation of XML. This definition can be used for XML digital signature as well efficient replication of XML objects. 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. --Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA) Content-type: multipart/alternative; boundary="Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)" --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000516103556.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2803 --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; name="rfc2803.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000516103556.RFC@RFC-EDITOR.ORG> --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)-- --Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010IPM4@eListX.com>; Tue, 16 May 2000 14:25:38 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010I0M1@eListX.com> (original mail from ietf-trade-moderator@lists.eListX.com); Tue, 16 May 2000 14:25:12 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006040HZLX@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 14:25:11 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YDR9M@eListX.com> for ietf-trade-moderator@moderate.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:28 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YDR9L@eListX.com> for ietf-trade-moderator@lists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:27 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00603YDR9J@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:27 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YDQ9I@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:26 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUN002JXYDNN0@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 13:39:26 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA17231; Tue, 16 May 2000 10:35:12 -0700 (PDT) Date: Tue, 16 May 2000 10:35:12 -0700 From: RFC Editor Subject: RFC 2802 on Digital Signatures for IOTP To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200005161735.KAA17231@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ) A new Request for Comments is now available in online RFC libraries. RFC 2802 Title: Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP) Author(s): K. Davidson, Y. Kawatsura Status: Informational Date: April 2000 Mailbox: kent@differential.com, kawatura@bisd.hitachi.co.jp Pages: 29 Characters: 52756 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2802.txt A syntax and procedures are described for the computation and verification of digital signatures for use within Version 1.0 of the Internet Open Trading Protocol (IOTP). This document is a product of the Internet Open Trading Protocol Wokring 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. --Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ) Content-type: multipart/alternative; boundary="Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)" --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000516103310.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2802 --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; name="rfc2802.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000516103310.RFC@RFC-EDITOR.ORG> --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)-- --Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010IPM4@eListX.com>; Tue, 16 May 2000 14:25:38 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010HZLZ@eListX.com> (original mail from ietf-trade-moderator@lists.eListX.com); Tue, 16 May 2000 14:25:12 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010HYLX@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 14:25:10 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601Y849H@eListX.com> for ietf-trade-moderator@moderate.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:04 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601Y849G@eListX.com> for ietf-trade-moderator@lists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:04 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00603Y849E@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:04 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601Y839D@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:03 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUN002JUY82N0@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 13:36:03 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA16430; Tue, 16 May 2000 10:31:53 -0700 (PDT) Date: Tue, 16 May 2000 10:31:53 -0700 From: RFC Editor Subject: RFC 2801 on IOTP/1.0 To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200005161731.KAA16430@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w) A new Request for Comments is now available in online RFC libraries. RFC 2801 Title: Internet Open Trading Protocol - IOTP Version 1.0 Author(s): D. Burdett Status: Informational Date: April 2000 Mailbox: david.burdett@commerceone.com Pages: 290 Characters: 598794 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2801.txt The Internet Open Trading Protocol (IOTP) provides an interoperable framework for Internet commerce. It is payment system independent and encapsulates payment systems such as SET, Secure Channel Credit/Debit, Mondex, CyberCoin, GeldKarte, etc. IOTP is able to handle cases where such merchant roles as the shopping site, the Payment Handler, the Delivery Handler of goods or services, and the provider of customer support are performed by different parties or by one party. 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. --Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w) Content-type: multipart/alternative; boundary="Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)" --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000516102853.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2801 --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; name="rfc2801.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000516102853.RFC@RFC-EDITOR.ORG> --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)-- --Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00801CCTDB@eListX.com>; Fri, 12 May 2000 11:00:29 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00801CCSDA@eListX.com> (original mail from nsyracus@cnri.reston.va.us) ; Fri, 12 May 2000 11:00:28 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00803CCSD8@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Fri, 12 May 2000 11:00:28 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00801CCRD7@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Fri, 12 May 2000 11:00:27 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUG0073JCCQHY@eListX.com> for ietf-trade@lists.eListX.com; Fri, 12 May 2000 11:00:27 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03314; Fri, 12 May 2000 10:56:25 -0400 (EDT) Date: Fri, 12 May 2000 10:56:24 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-trade-mime-detector-03.txt Sender: nsyracus@cnri.reston.va.us To: IETF-Announce: ; Cc: ietf-trade@lists.eListX.com Reply-to: Internet-Drafts@ietf.org Message-id: <200005121456.KAA03314@ietf.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A) A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF. Title : HTTP MIME Type Handler Detection Author(s) : D. Eastlake 3rd,C. Smith, D. Soroka Filename : draft-ietf-trade-mime-detector-03.txt Pages : 13 Date : 11-May-00 Entities composing web pages to provide services over HTTP frequently have the problem of not knowing what MIME types have handlers installed at a user's browser. For example, whether an IOTP or VRML or SET or some streaming media handler is available. In many cases they would want to display different web pages or content depending on a MIME handler's availability. This document summarizes a reasonable technique to solve this problem for most of the browsers actually deployed on the Internet as of August 1999. It is intended to be of practical use to implementors during the period before the wide deployment of superior standards based techniques which may be developed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-trade-mime-detector-03.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-trade-mime-detector-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-trade-mime-detector-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A) Content-type: multipart/alternative; boundary="Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA)" --Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000511135442.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-trade-mime-detector-03.txt --Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA) Content-type: Message/External-body; name="draft-ietf-trade-mime-detector-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000511135442.I-D@ietf.org> --Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA)-- --Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L01Z8ZXO@eListX.com>; Wed, 10 May 2000 15:24:35 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L01Z8ZXN@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 10 May 2000 15:24:35 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L03Z8YXL@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 10 May 2000 15:24:34 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L01Z8YXK@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 10 May 2000 15:24:34 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUC00L1UZ8VPP@eListX.com> for ietf-trade@lists.eListX.com; Wed, 10 May 2000 15:24:34 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id PAA10590 for ietf-trade@lists.elistx.com; Wed, 10 May 2000 15:22:10 -0400 (EDT) Date: Wed, 10 May 2000 15:22:10 -0400 From: "Donald E. Eastlake 3rd" Subject: APPLICATION/IOTP Officially registered To: ietf-trade@lists.eListX.com Message-id: <200005101922.PAA10590@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp ... Dear Donald, We have registered the following MIME media type with you as the point of contact: application/iotp Thank you, Michelle Schipper, Administrator *************************************************************** Internet Assigned Numbers Authority (IANA) 4676 Admiralty Way, Suite 330 Marina del Rey, California 90292 Voice: (310) 823-9358 x12 FAX: (310) 823-8649 email: iana@iana.org *************************************************************** Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C015YMZM@eListX.com>; Thu, 4 May 2000 19:15:58 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C015YLZL@eListX.com> (original mail from dee3@torque.pothole.com) ; Thu, 04 May 2000 19:15:58 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C035YLZJ@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Thu, 04 May 2000 19:15:57 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C015YLZI@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Thu, 04 May 2000 19:15:57 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FU200C4Z5YICY@eListX.com> for ietf-trade@lists.eListX.com; Thu, 04 May 2000 19:15:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id TAA03849; Thu, 04 May 2000 19:13:34 -0400 (EDT) Date: Thu, 04 May 2000 19:13:34 -0400 From: "Donald E. Eastlake 3rd" Subject: Re: XML/EDI In-reply-to: "Your message of Wed, 03 May 2000 16:41:29 EDT." <39108EF9.AD04135B@computer.org> To: Don Isenor Cc: iotp Message-id: <200005042313.TAA03849@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp I'm much more familiar with IOTP than EDI or OBI but it is my impression they have very different aims: IOTP is desigined for consumer to merchant interaction where there is not a prior existing relationship. It provides for the merchant function to be split among multiple machines (store front, payment handler, delivery handler, ...) and other features. OBI (Open Buying on the Internet), as I understand it, is designed for business to merchant interaction where there is a prior relationship. It provides for the business purchasing function to be split into requisitioner, approver, treasurer ... and other features. EDI, as I understand it, is designed for business to business interaction. At least original, it required an extensive prior relationship. In fact, it was commonly estimated to cost between $10,000 and $15,000 to set up an EDI connection between a pair of businesses because it was really just a very broad framework as indicated by its name, Electronic Data Interchange. The actual message contents to be used needed to be agreed upon. In some cases, EDI was more or less forced on suppliers by major purchasers as part of the price of being one of suppliers. I understand that there are a lot of efforts at simplified and/or standardized EDI to try to make it easier to set up. IOTP is already in XML but I understand that both OBI and EDI are headed that way. I suppose it is possible that at some point they could all merge. But right now, I believe they provide quite distinct services. Donald From: Don Isenor Date: Wed, 03 May 2000 16:41:29 -0400 To: iotp Message-id: <39108EF9.AD04135B@computer.org> >Apologies if this has been discussed before, but I have heard that >XML/EDI covers pretty much the same ground as does IOTP, but XML/EDI >appears to have much more widespread backing than does IOTP. Can anyone >here comment on IOTP vs. XML/EDI? > >Don Isenor >Ambercon Inc. Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006014CMUS@eListX.com>; Wed, 3 May 2000 16:45:58 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006014CEUR@eListX.com> (original mail from disenor@computer.org); Wed, 03 May 2000 16:45:50 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006034CEUP@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Wed, 03 May 2000 16:45:50 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006014CDUO@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Wed, 03 May 2000 16:45:49 -0400 (EDT) Received: from atlas.pathcom.com (pathway1.pathcom.com [209.250.128.4]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FU0002GI4CC70@eListX.com> for ietf-trade@lists.eListX.com; Wed, 03 May 2000 16:45:49 -0400 (EDT) Received: from computer.org (www.ambercon-inc.com [209.250.134.123]) by atlas.pathcom.com (8.9.3/8.9.3) with ESMTP id QAA21037 for ; Wed, 03 May 2000 16:42:01 -0400 (EDT) Date: Wed, 03 May 2000 16:41:29 -0400 From: Don Isenor Subject: XML/EDI To: iotp Message-id: <39108EF9.AD04135B@computer.org> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , Apologies if this has been discussed before, but I have heard that XML/EDI covers pretty much the same ground as does IOTP, but XML/EDI appears to have much more widespread backing than does IOTP. Can anyone here comment on IOTP vs. XML/EDI? Don Isenor Ambercon Inc. Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060117CJG@eListX.com>; Wed, 3 May 2000 15:38:00 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060117BJF@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 03 May 2000 15:37:59 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060317BJD@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 03 May 2000 15:37:59 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060117AJC@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 03 May 2000 15:37:58 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FU0002EB17770@eListX.com> for ietf-trade@lists.eListX.com; Wed, 03 May 2000 15:37:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id PAA01825 for ietf-trade@lists.elistx.com; Wed, 03 May 2000 15:35:36 -0400 (EDT) Date: Wed, 03 May 2000 15:35:35 -0400 From: "Donald E. Eastlake 3rd" Subject: WG Last CAll draft-ietf-trade-iotp-http-05.txt To: ietf-trade@lists.eListX.com Message-id: <200005031935.PAA01825@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp Since there have been no comments or suggestions on this draft for some time and earlier comments and suggestions have generally been incorporated, I'm calling a two week Working Group Last Call on this draft. I intend to forward the draft to the IESG as is or with minor changes based on future comments sometime on or after 17 May. Thanks, Donald ===================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 140 Forest Avenue +1 914-276-2668(h) Hudson, MA 01749 USA +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001019NAIP@eListX.com>; Tue, 2 May 2000 16:45:10 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001019N9IO@eListX.com> (original mail from dee3@torque.pothole.com) ; Tue, 02 May 2000 16:45:09 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001039N9IM@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Tue, 02 May 2000 16:45:09 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001019N8IL@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Tue, 02 May 2000 16:45:08 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FTY0002X9N5T6@eListX.com> for ietf-trade@lists.eListX.com; Tue, 02 May 2000 16:45:08 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id QAA00419 for ietf-trade@lists.elistx.com; Tue, 02 May 2000 16:42:37 -0400 (EDT) Date: Tue, 02 May 2000 16:42:37 -0400 From: "Donald E. Eastlake 3rd" Subject: XrML To: ietf-trade@lists.eListX.com Message-id: <200005022042.QAA00419@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp Here is a web site talking about "Digitial Rights" but they just mean mark up to indicate right in content, as far as I can tell. Donald ===================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 65 Shindegan Hill Road, RR#1 +1 914-276-2668(h) Carmel, NY 10512 USA +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K01UPPJK@eListX.com>; Wed, 31 May 2000 15:13:01 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K01UPOJJ@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 31 May 2000 15:13:00 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K03UPOJH@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 31 May 2000 15:13:00 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FVF00K01UPNJG@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 31 May 2000 15:12:59 -0400 (EDT) Received: from torque.pothole.com ([38.138.52.132]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FVF00K1IUPL7B@eListX.com> for ietf-trade@lists.eListX.com; Wed, 31 May 2000 15:12:59 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id PAA10925 for ietf-trade@lists.elistx.com; Wed, 31 May 2000 15:14:36 -0400 (EDT) Date: Wed, 31 May 2000 15:14:35 -0400 From: "Donald E. Eastlake 3rd" Subject: HTTP Supplement and MIME Type Detector drafts To: ietf-trade@lists.eListX.com Message-id: <200005311914.PAA10925@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp Hi, This is the start of a two week Working Group last call on the draft-ietf-trade-mime-detector-03.txt draft. This is an informational document on determining what sort of MIME types a browser supports. Since there were no objections to the draft-ietf-trade-iotp-http-05.txt draft as per below, I'm going to do a quick update onit to replace draft references with RFC references and forward it to the IESG for their approval for publication as a Proposed Standard RFC. Thanks, Donald Date: Wed, 03 May 2000 15:35:35 -0400 From: "Donald E. Eastlake 3rd" Subject: WG Last CAll draft-ietf-trade-iotp-http-05.txt To: ietf-trade@lists.eListX.com Message-id: <200005031935.PAA01825@torque.pothole.com> Since there have been no comments or suggestions on this draft for some time and earlier comments and suggestions have generally been incorporated, I'm calling a two week Working Group Last Call on this draft. I intend to forward the draft to the IESG as is or with minor changes based on future comments sometime on or after 17 May. Thanks, Donald ===================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 140 Forest Avenue +1 914-276-2668(h) Hudson, MA 01749 USA +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00701BKRS5@eListX.com>; Tue, 16 May 2000 18:24:27 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00701BKRS4@eListX.com> (original mail from CHRIS.SMITH@ROYALBANK.COM) ; Tue, 16 May 2000 18:24:27 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00703BKQS2@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 18:24:27 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO00701BKQS1@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 18:24:26 -0400 (EDT) Received: from smtp2.royalbank.com (smtp2.royalbank.com [198.96.131.29]) by eListX.com (PMDF V5.2-33 #43584) with SMTP id <0FUO00746BKP0D@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 18:24:26 -0400 (EDT) Received: from wsecure1.royalbank.com by smtp2.royalbank.com via smtpd (for one.elistx.com [209.116.252.130]) with SMTP; Tue, 16 May 2000 22:20:32 +0000 (UT) Received: from 10.224.0.67 by se001019.royalbank.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Tue, 16 May 2000 18:20:17 -0400 Received: by se001017.royalbank.com with Internet Mail Service ( 5.5.2650.21) id ; Tue, 16 May 2000 18:20:17 -0400 Date: Tue, 16 May 2000 18:20:18 -0400 From: "Smith, Chris " Subject: RE: RFC 2801 on IOTP/1.0 To: "ietf-trade@lists. eListX. com (E-mail)" Message-id: <2B30A9965635D311A29F002035297FFB0461546C@se001010.rbc1.royalbank.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: multipart/alternative; boundary="Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ)" X-Server-Uuid: 47ce64ae-6caa-11d3-9dcc-00902732b24c X-WSS-ID: 153F162B170333-01-01 List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable > -----Original Message----- > From: RFC Editor [mailto:rfc-ed@ISI.EDU] > Sent: May 16, 2000 01:32 PM > Cc: rfc-ed@ISI.EDU; ietf-trade@lists.eListX.com > Subject: RFC 2801 on IOTP/1.0 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 > RFC 2801 >=20 > Title: Internet Open Trading Protocol - IOTP Version 1.0 > Author(s): D. Burdett > Status: Informational > Date: April 2000 > Mailbox: david.burdett@commerceone.com Congratulations to ALL - the uncountable all, for getting this far. Now comes the hard part - making RFC2801 as recognizable as, say 822. > Pages: 290 > Characters: 598794 I've confirmed it against the official list, by sorting all of the RFCs in order of size. RFC 2801 is the=20 largest text RFC in existence. ------------------------------------------------------------=20 =A0Chris = Smith=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 +1.416.348.6090=20 =A0Royal = Bank=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = chris.smith@royalbank.com=20 --Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: quoted-printable RE: RFC 2801 on IOTP/1.0

> -----Original Message-----
> From: RFC Editor [mailto:rfc-ed@ISI.EDU]
> Sent: May 16, 2000 01:32 PM
> Cc: rfc-ed@ISI.EDU; = ietf-trade@lists.eListX.com
> Subject: RFC 2801 on IOTP/1.0
>
> A new Request for Comments is now available in = online RFC libraries.
>
>         = RFC 2801
>
>         = Title:            = Internet Open Trading Protocol - IOTP Version 1.0
>         = Author(s):  D. Burdett
>         = Status:     Informational
>         = Date:       April 2000
>         = Mailbox:    david.burdett@commerceone.com

Congratulations to ALL - the uncountable all, for = getting this far.

Now comes the hard part - making RFC2801 as = recognizable as, say 822.

>         = Pages:      290
>         = Characters: 598794

I've confirmed it against the official list, by = sorting
all of the RFCs in order of size. RFC 2801 is the =
largest text RFC in existence.

------------------------------------------------------------ =
=A0Chris = Smith=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 +1.416.348.6090
=A0Royal = Bank=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = chris.smith@royalbank.com

--Boundary_(ID_u7CRErqnvmV1h3EZ7qe6XQ)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010IPM4@eListX.com>; Tue, 16 May 2000 14:25:38 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010I0M3@eListX.com> (original mail from ietf-trade-moderator@lists.eListX.com); Tue, 16 May 2000 14:25:12 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006070HZLX@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 14:25:11 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YILA0@eListX.com> for ietf-trade-moderator@moderate.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:21 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YIL9Z@eListX.com> for ietf-trade-moderator@lists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:21 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00603YIK9X@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:20 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YIK9W@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:42:20 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUN002K3YIBN0@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 13:42:20 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA17518; Tue, 16 May 2000 10:38:03 -0700 (PDT) Date: Tue, 16 May 2000 10:38:03 -0700 From: RFC Editor Subject: RFC 2803 on Digest Values for DOM (DOMHASH) To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200005161738.KAA17518@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA) A new Request for Comments is now available in online RFC libraries. RFC 2803 Title: Digest Values for DOM (DOMHASH) Author(s): H. Maruyama, K. Tamura, N. Uramoto Status: Informational Date: April 2000 Mailbox: maruyama@jp.ibm.com, kent@trl.ibm.co.jp, uramoto@jp.ibm.com Pages: 11 Characters: 22552 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2803.txt This memo defines a clear and unambiguous definition of digest (hash) values of the XML objects regardless of the surface string variation of XML. This definition can be used for XML digital signature as well efficient replication of XML objects. 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. --Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA) Content-type: multipart/alternative; boundary="Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)" --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000516103556.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2803 --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; name="rfc2803.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000516103556.RFC@RFC-EDITOR.ORG> --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)-- --Boundary_(ID_3Ok+Vd+p0qTpALiHIduHOA)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010IPM4@eListX.com>; Tue, 16 May 2000 14:25:38 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010I0M1@eListX.com> (original mail from ietf-trade-moderator@lists.eListX.com); Tue, 16 May 2000 14:25:12 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006040HZLX@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 14:25:11 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YDR9M@eListX.com> for ietf-trade-moderator@moderate.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:28 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YDR9L@eListX.com> for ietf-trade-moderator@lists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:27 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00603YDR9J@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:27 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601YDQ9I@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:39:26 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUN002JXYDNN0@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 13:39:26 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA17231; Tue, 16 May 2000 10:35:12 -0700 (PDT) Date: Tue, 16 May 2000 10:35:12 -0700 From: RFC Editor Subject: RFC 2802 on Digital Signatures for IOTP To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200005161735.KAA17231@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ) A new Request for Comments is now available in online RFC libraries. RFC 2802 Title: Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP) Author(s): K. Davidson, Y. Kawatsura Status: Informational Date: April 2000 Mailbox: kent@differential.com, kawatura@bisd.hitachi.co.jp Pages: 29 Characters: 52756 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2802.txt A syntax and procedures are described for the computation and verification of digital signatures for use within Version 1.0 of the Internet Open Trading Protocol (IOTP). This document is a product of the Internet Open Trading Protocol Wokring 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. --Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ) Content-type: multipart/alternative; boundary="Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)" --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000516103310.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2802 --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; name="rfc2802.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000516103310.RFC@RFC-EDITOR.ORG> --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)-- --Boundary_(ID_zf0LLAKWUkP4PyttQ7GOMQ)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010IPM4@eListX.com>; Tue, 16 May 2000 14:25:38 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010HZLZ@eListX.com> (original mail from ietf-trade-moderator@lists.eListX.com); Tue, 16 May 2000 14:25:12 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUO006010HYLX@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 14:25:10 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601Y849H@eListX.com> for ietf-trade-moderator@moderate.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:04 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601Y849G@eListX.com> for ietf-trade-moderator@lists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:04 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00603Y849E@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:04 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUN00601Y839D@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Tue, 16 May 2000 13:36:03 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUN002JUY82N0@eListX.com> for ietf-trade@lists.eListX.com; Tue, 16 May 2000 13:36:03 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA16430; Tue, 16 May 2000 10:31:53 -0700 (PDT) Date: Tue, 16 May 2000 10:31:53 -0700 From: RFC Editor Subject: RFC 2801 on IOTP/1.0 To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200005161731.KAA16430@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w) A new Request for Comments is now available in online RFC libraries. RFC 2801 Title: Internet Open Trading Protocol - IOTP Version 1.0 Author(s): D. Burdett Status: Informational Date: April 2000 Mailbox: david.burdett@commerceone.com Pages: 290 Characters: 598794 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2801.txt The Internet Open Trading Protocol (IOTP) provides an interoperable framework for Internet commerce. It is payment system independent and encapsulates payment systems such as SET, Secure Channel Credit/Debit, Mondex, CyberCoin, GeldKarte, etc. IOTP is able to handle cases where such merchant roles as the shopping site, the Payment Handler, the Delivery Handler of goods or services, and the provider of customer support are performed by different parties or by one party. 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. --Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w) Content-type: multipart/alternative; boundary="Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)" --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000516102853.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2801 --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g) Content-type: Message/External-body; name="rfc2801.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000516102853.RFC@RFC-EDITOR.ORG> --Boundary_(ID_r3b0iMACByW3ZpXFbIR61g)-- --Boundary_(ID_fI9wimr6Llr1OKalU8Jk8w)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00801CCTDB@eListX.com>; Fri, 12 May 2000 11:00:29 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00801CCSDA@eListX.com> (original mail from nsyracus@cnri.reston.va.us) ; Fri, 12 May 2000 11:00:28 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00803CCSD8@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Fri, 12 May 2000 11:00:28 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUG00801CCRD7@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Fri, 12 May 2000 11:00:27 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUG0073JCCQHY@eListX.com> for ietf-trade@lists.eListX.com; Fri, 12 May 2000 11:00:27 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03314; Fri, 12 May 2000 10:56:25 -0400 (EDT) Date: Fri, 12 May 2000 10:56:24 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-trade-mime-detector-03.txt Sender: nsyracus@cnri.reston.va.us To: IETF-Announce: ; Cc: ietf-trade@lists.eListX.com Reply-to: Internet-Drafts@ietf.org Message-id: <200005121456.KAA03314@ietf.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A) A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Open Trading Protocol Working Group of the IETF. Title : HTTP MIME Type Handler Detection Author(s) : D. Eastlake 3rd,C. Smith, D. Soroka Filename : draft-ietf-trade-mime-detector-03.txt Pages : 13 Date : 11-May-00 Entities composing web pages to provide services over HTTP frequently have the problem of not knowing what MIME types have handlers installed at a user's browser. For example, whether an IOTP or VRML or SET or some streaming media handler is available. In many cases they would want to display different web pages or content depending on a MIME handler's availability. This document summarizes a reasonable technique to solve this problem for most of the browsers actually deployed on the Internet as of August 1999. It is intended to be of practical use to implementors during the period before the wide deployment of superior standards based techniques which may be developed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-trade-mime-detector-03.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-trade-mime-detector-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-trade-mime-detector-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A) Content-type: multipart/alternative; boundary="Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA)" --Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000511135442.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-trade-mime-detector-03.txt --Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA) Content-type: Message/External-body; name="draft-ietf-trade-mime-detector-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000511135442.I-D@ietf.org> --Boundary_(ID_B6qaFrnZRjJGU9gWqmw0YA)-- --Boundary_(ID_enyOZ1OazeHSPg9FpQQ+0A)-- Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L01Z8ZXO@eListX.com>; Wed, 10 May 2000 15:24:35 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L01Z8ZXN@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 10 May 2000 15:24:35 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L03Z8YXL@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 10 May 2000 15:24:34 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-33 #43584) id <0FUC00L01Z8YXK@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 10 May 2000 15:24:34 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-33 #43584) with ESMTP id <0FUC00L1UZ8VPP@eListX.com> for ietf-trade@lists.eListX.com; Wed, 10 May 2000 15:24:34 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id PAA10590 for ietf-trade@lists.elistx.com; Wed, 10 May 2000 15:22:10 -0400 (EDT) Date: Wed, 10 May 2000 15:22:10 -0400 From: "Donald E. Eastlake 3rd" Subject: APPLICATION/IOTP Officially registered To: ietf-trade@lists.eListX.com Message-id: <200005101922.PAA10590@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp ... Dear Donald, We have registered the following MIME media type with you as the point of contact: application/iotp Thank you, Michelle Schipper, Administrator *************************************************************** Internet Assigned Numbers Authority (IANA) 4676 Admiralty Way, Suite 330 Marina del Rey, California 90292 Voice: (310) 823-9358 x12 FAX: (310) 823-8649 email: iana@iana.org *************************************************************** Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C015YMZM@eListX.com>; Thu, 4 May 2000 19:15:58 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C015YLZL@eListX.com> (original mail from dee3@torque.pothole.com) ; Thu, 04 May 2000 19:15:58 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C035YLZJ@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Thu, 04 May 2000 19:15:57 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU200C015YLZI@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Thu, 04 May 2000 19:15:57 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FU200C4Z5YICY@eListX.com> for ietf-trade@lists.eListX.com; Thu, 04 May 2000 19:15:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id TAA03849; Thu, 04 May 2000 19:13:34 -0400 (EDT) Date: Thu, 04 May 2000 19:13:34 -0400 From: "Donald E. Eastlake 3rd" Subject: Re: XML/EDI In-reply-to: "Your message of Wed, 03 May 2000 16:41:29 EDT." <39108EF9.AD04135B@computer.org> To: Don Isenor Cc: iotp Message-id: <200005042313.TAA03849@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp I'm much more familiar with IOTP than EDI or OBI but it is my impression they have very different aims: IOTP is desigined for consumer to merchant interaction where there is not a prior existing relationship. It provides for the merchant function to be split among multiple machines (store front, payment handler, delivery handler, ...) and other features. OBI (Open Buying on the Internet), as I understand it, is designed for business to merchant interaction where there is a prior relationship. It provides for the business purchasing function to be split into requisitioner, approver, treasurer ... and other features. EDI, as I understand it, is designed for business to business interaction. At least original, it required an extensive prior relationship. In fact, it was commonly estimated to cost between $10,000 and $15,000 to set up an EDI connection between a pair of businesses because it was really just a very broad framework as indicated by its name, Electronic Data Interchange. The actual message contents to be used needed to be agreed upon. In some cases, EDI was more or less forced on suppliers by major purchasers as part of the price of being one of suppliers. I understand that there are a lot of efforts at simplified and/or standardized EDI to try to make it easier to set up. IOTP is already in XML but I understand that both OBI and EDI are headed that way. I suppose it is possible that at some point they could all merge. But right now, I believe they provide quite distinct services. Donald From: Don Isenor Date: Wed, 03 May 2000 16:41:29 -0400 To: iotp Message-id: <39108EF9.AD04135B@computer.org> >Apologies if this has been discussed before, but I have heard that >XML/EDI covers pretty much the same ground as does IOTP, but XML/EDI >appears to have much more widespread backing than does IOTP. Can anyone >here comment on IOTP vs. XML/EDI? > >Don Isenor >Ambercon Inc. Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006014CMUS@eListX.com>; Wed, 3 May 2000 16:45:58 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006014CEUR@eListX.com> (original mail from disenor@computer.org); Wed, 03 May 2000 16:45:50 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006034CEUP@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Wed, 03 May 2000 16:45:50 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU0006014CDUO@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.eListX.com); Wed, 03 May 2000 16:45:49 -0400 (EDT) Received: from atlas.pathcom.com (pathway1.pathcom.com [209.250.128.4]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FU0002GI4CC70@eListX.com> for ietf-trade@lists.eListX.com; Wed, 03 May 2000 16:45:49 -0400 (EDT) Received: from computer.org (www.ambercon-inc.com [209.250.134.123]) by atlas.pathcom.com (8.9.3/8.9.3) with ESMTP id QAA21037 for ; Wed, 03 May 2000 16:42:01 -0400 (EDT) Date: Wed, 03 May 2000 16:41:29 -0400 From: Don Isenor Subject: XML/EDI To: iotp Message-id: <39108EF9.AD04135B@computer.org> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , Apologies if this has been discussed before, but I have heard that XML/EDI covers pretty much the same ground as does IOTP, but XML/EDI appears to have much more widespread backing than does IOTP. Can anyone here comment on IOTP vs. XML/EDI? Don Isenor Ambercon Inc. Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060117CJG@eListX.com>; Wed, 3 May 2000 15:38:00 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060117BJF@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 03 May 2000 15:37:59 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060317BJD@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 03 May 2000 15:37:59 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FU00060117AJC@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Wed, 03 May 2000 15:37:58 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FU0002EB17770@eListX.com> for ietf-trade@lists.eListX.com; Wed, 03 May 2000 15:37:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id PAA01825 for ietf-trade@lists.elistx.com; Wed, 03 May 2000 15:35:36 -0400 (EDT) Date: Wed, 03 May 2000 15:35:35 -0400 From: "Donald E. Eastlake 3rd" Subject: WG Last CAll draft-ietf-trade-iotp-http-05.txt To: ietf-trade@lists.eListX.com Message-id: <200005031935.PAA01825@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp Since there have been no comments or suggestions on this draft for some time and earlier comments and suggestions have generally been incorporated, I'm calling a two week Working Group Last Call on this draft. I intend to forward the draft to the IESG as is or with minor changes based on future comments sometime on or after 17 May. Thanks, Donald ===================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 140 Forest Avenue +1 914-276-2668(h) Hudson, MA 01749 USA +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001019NAIP@eListX.com>; Tue, 2 May 2000 16:45:10 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001019N9IO@eListX.com> (original mail from dee3@torque.pothole.com) ; Tue, 02 May 2000 16:45:09 -0400 (EDT) Received: from ELISTS-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001039N9IM@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Tue, 02 May 2000 16:45:09 -0400 (EDT) Received: from DIRECTORY-DAEMON by eListX.com (PMDF V5.2-32 #43584) id <0FTY001019N8IL@eListX.com> for ietf-trade@elists.eListX.com (ORCPT rfc822;ietf-trade@lists.elistx.com); Tue, 02 May 2000 16:45:08 -0400 (EDT) Received: from torque.pothole.com ([209.94.126.195]) by eListX.com (PMDF V5.2-32 #43584) with ESMTP id <0FTY0002X9N5T6@eListX.com> for ietf-trade@lists.eListX.com; Tue, 02 May 2000 16:45:08 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id QAA00419 for ietf-trade@lists.elistx.com; Tue, 02 May 2000 16:42:37 -0400 (EDT) Date: Tue, 02 May 2000 16:42:37 -0400 From: "Donald E. Eastlake 3rd" Subject: XrML To: ietf-trade@lists.eListX.com Message-id: <200005022042.QAA00419@torque.pothole.com> X-Authentication-warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , X-MTS: smtp Here is a web site talking about "Digitial Rights" but they just mean mark up to indicate right in content, as far as I can tell. Donald ===================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 65 Shindegan Hill Road, RR#1 +1 914-276-2668(h) Carmel, NY 10512 USA +1 508-261-5434(w)