Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M01F9TTF@eListX.com>; Thu, 28 Sep 2000 06:46:41 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M01F9TTE@eListX.com> (original mail from nsyracus@cnri.reston.va.us) ; Thu, 28 Sep 2000 06:46:41 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M03F9TTC@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Thu, 28 Sep 2000 06:46:41 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M01F9STB@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Thu, 28 Sep 2000 06:46:40 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1L00JJ9F9SOQ@eListX.com> for ietf-trade@lists.eListX.com; Thu, 28 Sep 2000 06:46:40 -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 GAA16406; Thu, 28 Sep 2000 06:46:28 -0400 (EDT) Date: Thu, 28 Sep 2000 06:46:28 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-trade-iotp-v1.0-papi-01.txt Sender: nsyracus@cnri.reston.va.us To: IETF-Announce: ; Cc: ietf-trade@lists.eListX.com Reply-to: Internet-Drafts@ietf.org Message-id: <200009281046.GAA16406@ietf.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_6c4MZASv1J+1T9WL58Sr0w)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_6c4MZASv1J+1T9WL58Sr0w) 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 : Payment API for v1.0 Internet Open Trading Protocol (IOTP) Author(s) : W. Hans, H. Beykirch, M. Hiroya, Y. Kawatsura Filename : draft-ietf-trade-iotp-v1.0-papi-01.txt Pages : 102 Date : 27-Sep-00 The Internet Open Trading Protocol provides a data exchange format for trading purposes while integrating existing pure payment protocols seamlessly. This motivates the multiple layered system architecture which consists of at least some generic IOTP application core and multiple specific payment modules. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-papi-01.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-iotp-v1.0-papi-01.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-iotp-v1.0-papi-01.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_6c4MZASv1J+1T9WL58Sr0w) Content-type: multipart/alternative; boundary="Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg)" --Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000927140020.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-trade-iotp-v1.0-papi-01.txt --Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg) Content-type: Message/External-body; name="draft-ietf-trade-iotp-v1.0-papi-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000927140020.I-D@ietf.org> --Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg)-- --Boundary_(ID_6c4MZASv1J+1T9WL58Sr0w)-- Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017VZY1@eListX.com>; Wed, 27 Sep 2000 15:09:35 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017VZY0@eListX.com> (original mail from rfc-ed@ISI.EDU); Wed, 27 Sep 2000 15:09:35 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E037VYXY@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 15:09:34 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017VYXX@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 15:09:34 -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 <0G1K00D3Y7VXYI@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 15:09:34 -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 MAA11251; Wed, 27 Sep 2000 12:09:16 -0700 (PDT) Date: Wed, 27 Sep 2000 12:09:16 -0700 From: RFC Editor Subject: RFC 2936 on HTTP MIME Type Handler Detection To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200009271909.MAA11251@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_vCAYEFQJGkP1829MZRobVw)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_vCAYEFQJGkP1829MZRobVw) A new Request for Comments is now available in online RFC libraries. RFC 2936 Title: HTTP MIME Type Handler Detection Author(s): D. Eastlake, C. Smith, D. Soroka Status: Informational Date: September 2000 Mailbox: Donald.Eastlake@motorola.com, chris.smith@royalbank.com, dsoroka@us.ibm.com Pages: 13 Characters: 25238 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trade-mime-detector-03.txt URL: ftp://ftp.isi.edu/in-notes/rfc2936.txt Entities composing web pages to provide services over the Hypertext Transfer Protocol (HTTP) frequently have the problem of not knowing what Multipurpose Internet Mail Extensions (MIME) types have handlers installed at a user's browser. For example, whether an Internet Open Trading Protocol (IOTP) or VRML or SET or some streaming media handler is available. In some cases they would want to display different web pages or content depending on a MIME handler's availability. This document summarizes reasonable techniques to solve this problem for most of the browsers actually deployed on the Internet as of early 2000. 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. 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_vCAYEFQJGkP1829MZRobVw) Content-type: multipart/alternative; boundary="Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw)" --Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000927120732.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2936 --Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw) Content-type: Message/External-body; name="rfc2936.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000927120732.RFC@RFC-EDITOR.ORG> --Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw)-- --Boundary_(ID_vCAYEFQJGkP1829MZRobVw)-- Return-Path: 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 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: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_+ottin6vgVc6meTROsqhaA) 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. --Boundary_(ID_+ottin6vgVc6meTROsqhaA) Content-type: multipart/alternative; boundary="Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA)" --Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000927120444.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2935 --Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA) Content-type: Message/External-body; name="rfc2935.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000927120444.RFC@RFC-EDITOR.ORG> --Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA)-- --Boundary_(ID_+ottin6vgVc6meTROsqhaA)-- Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B01QD680@eListX.com>; Wed, 27 Sep 2000 08:51:06 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B01QD67Z@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 27 Sep 2000 08:51:06 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B03QD57X@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 08:51:05 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B01QD57W@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 08:51:05 -0400 (EDT) Received: from torque.pothole.com ([38.138.52.132]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1J007M0Q9QWO@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 08:51:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id IAA02458 for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 08:52:00 -0400 (EDT) Date: Wed, 27 Sep 2000 08:52:00 -0400 From: "Donald E. Eastlake 3rd" Subject: Re: I-D ACTION:draft-ietf-trade-iotp-v1.0-set-01.txt In-reply-to: "Your message of Wed, 27 Sep 2000 06:31:50 EDT." <200009271031.GAA07596@ietf.org> To: ietf-trade@lists.eListX.com Message-id: <200009271252.IAA02458@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 An updated payment API draft will be posted very shortly which goes with the just posted SET Supplement draft. Thanks, Donald =================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 140 Forest Avenue lde008@dma.isg.mot.com Hudson, MA 01749 USA +1 978-562-2827(h) +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A01JXG82@eListX.com>; Wed, 27 Sep 2000 06:32:04 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A01JXF81@eListX.com> (original mail from nsyracus@cnri.reston.va.us) ; Wed, 27 Sep 2000 06:32:03 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A03JXF7Z@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 06:32:03 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A01JXF7Y@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 06:32:03 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1J007EYJXEWO@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 06:32:02 -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 GAA07596; Wed, 27 Sep 2000 06:31:51 -0400 (EDT) Date: Wed, 27 Sep 2000 06:31:50 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-trade-iotp-v1.0-set-01.txt Sender: nsyracus@cnri.reston.va.us To: IETF-Announce: ; Cc: ietf-trade@lists.eListX.com Reply-to: Internet-Drafts@ietf.org Message-id: <200009271031.GAA07596@ietf.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_oS3L9Ru34bVhLFOwpjICyg)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_oS3L9Ru34bVhLFOwpjICyg) 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 : SET Supplement for the v1.0 Internet Open Trading Protocol (IOTP) Author(s) : Y. Kawatsura Filename : draft-ietf-trade-iotp-v1.0-set-01.txt Pages : 54 Date : 25-Sep-00 This document describes detailed Input/Output parameter for the IOTP Payment API and a procedure in the Payment Bridge for use SET as the payment protocol within Version 1.0 of the Internet Open Trading Protocol (IOTP). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-set-01.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-iotp-v1.0-set-01.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-iotp-v1.0-set-01.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_oS3L9Ru34bVhLFOwpjICyg) Content-type: multipart/alternative; boundary="Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg)" --Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000925145632.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-trade-iotp-v1.0-set-01.txt --Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg) Content-type: Message/External-body; name="draft-ietf-trade-iotp-v1.0-set-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000925145632.I-D@ietf.org> --Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg)-- --Boundary_(ID_oS3L9Ru34bVhLFOwpjICyg)-- Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M01F9TTF@eListX.com>; Thu, 28 Sep 2000 06:46:41 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M01F9TTE@eListX.com> (original mail from nsyracus@cnri.reston.va.us) ; Thu, 28 Sep 2000 06:46:41 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M03F9TTC@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Thu, 28 Sep 2000 06:46:41 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1L00M01F9STB@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Thu, 28 Sep 2000 06:46:40 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1L00JJ9F9SOQ@eListX.com> for ietf-trade@lists.eListX.com; Thu, 28 Sep 2000 06:46:40 -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 GAA16406; Thu, 28 Sep 2000 06:46:28 -0400 (EDT) Date: Thu, 28 Sep 2000 06:46:28 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-trade-iotp-v1.0-papi-01.txt Sender: nsyracus@cnri.reston.va.us To: IETF-Announce: ; Cc: ietf-trade@lists.eListX.com Reply-to: Internet-Drafts@ietf.org Message-id: <200009281046.GAA16406@ietf.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_6c4MZASv1J+1T9WL58Sr0w)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_6c4MZASv1J+1T9WL58Sr0w) 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 : Payment API for v1.0 Internet Open Trading Protocol (IOTP) Author(s) : W. Hans, H. Beykirch, M. Hiroya, Y. Kawatsura Filename : draft-ietf-trade-iotp-v1.0-papi-01.txt Pages : 102 Date : 27-Sep-00 The Internet Open Trading Protocol provides a data exchange format for trading purposes while integrating existing pure payment protocols seamlessly. This motivates the multiple layered system architecture which consists of at least some generic IOTP application core and multiple specific payment modules. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-papi-01.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-iotp-v1.0-papi-01.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-iotp-v1.0-papi-01.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_6c4MZASv1J+1T9WL58Sr0w) Content-type: multipart/alternative; boundary="Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg)" --Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000927140020.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-trade-iotp-v1.0-papi-01.txt --Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg) Content-type: Message/External-body; name="draft-ietf-trade-iotp-v1.0-papi-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000927140020.I-D@ietf.org> --Boundary_(ID_sgUvNn6zSSNlgtEYvgcZRg)-- --Boundary_(ID_6c4MZASv1J+1T9WL58Sr0w)-- Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017VZY1@eListX.com>; Wed, 27 Sep 2000 15:09:35 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017VZY0@eListX.com> (original mail from rfc-ed@ISI.EDU); Wed, 27 Sep 2000 15:09:35 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E037VYXY@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 15:09:34 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1K00E017VYXX@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 15:09:34 -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 <0G1K00D3Y7VXYI@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 15:09:34 -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 MAA11251; Wed, 27 Sep 2000 12:09:16 -0700 (PDT) Date: Wed, 27 Sep 2000 12:09:16 -0700 From: RFC Editor Subject: RFC 2936 on HTTP MIME Type Handler Detection To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com Message-id: <200009271909.MAA11251@boreas.isi.edu> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_vCAYEFQJGkP1829MZRobVw)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_vCAYEFQJGkP1829MZRobVw) A new Request for Comments is now available in online RFC libraries. RFC 2936 Title: HTTP MIME Type Handler Detection Author(s): D. Eastlake, C. Smith, D. Soroka Status: Informational Date: September 2000 Mailbox: Donald.Eastlake@motorola.com, chris.smith@royalbank.com, dsoroka@us.ibm.com Pages: 13 Characters: 25238 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trade-mime-detector-03.txt URL: ftp://ftp.isi.edu/in-notes/rfc2936.txt Entities composing web pages to provide services over the Hypertext Transfer Protocol (HTTP) frequently have the problem of not knowing what Multipurpose Internet Mail Extensions (MIME) types have handlers installed at a user's browser. For example, whether an Internet Open Trading Protocol (IOTP) or VRML or SET or some streaming media handler is available. In some cases they would want to display different web pages or content depending on a MIME handler's availability. This document summarizes reasonable techniques to solve this problem for most of the browsers actually deployed on the Internet as of early 2000. 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. 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_vCAYEFQJGkP1829MZRobVw) Content-type: multipart/alternative; boundary="Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw)" --Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000927120732.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2936 --Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw) Content-type: Message/External-body; name="rfc2936.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000927120732.RFC@RFC-EDITOR.ORG> --Boundary_(ID_SfJyC6SWpyr5L38xOzAPQw)-- --Boundary_(ID_vCAYEFQJGkP1829MZRobVw)-- Return-Path: 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 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: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_+ottin6vgVc6meTROsqhaA) 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. --Boundary_(ID_+ottin6vgVc6meTROsqhaA) Content-type: multipart/alternative; boundary="Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA)" --Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA) Content-type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000927120444.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2935 --Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA) Content-type: Message/External-body; name="rfc2935.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000927120444.RFC@RFC-EDITOR.ORG> --Boundary_(ID_hfx4S1nmY+5S+ug+UkIryA)-- --Boundary_(ID_+ottin6vgVc6meTROsqhaA)-- Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B01QD680@eListX.com>; Wed, 27 Sep 2000 08:51:06 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B01QD67Z@eListX.com> (original mail from dee3@torque.pothole.com) ; Wed, 27 Sep 2000 08:51:06 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B03QD57X@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 08:51:05 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00B01QD57W@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 08:51:05 -0400 (EDT) Received: from torque.pothole.com ([38.138.52.132]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1J007M0Q9QWO@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 08:51:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by torque.pothole.com (8.8.2/8.8.8) with SMTP id IAA02458 for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 08:52:00 -0400 (EDT) Date: Wed, 27 Sep 2000 08:52:00 -0400 From: "Donald E. Eastlake 3rd" Subject: Re: I-D ACTION:draft-ietf-trade-iotp-v1.0-set-01.txt In-reply-to: "Your message of Wed, 27 Sep 2000 06:31:50 EDT." <200009271031.GAA07596@ietf.org> To: ietf-trade@lists.eListX.com Message-id: <200009271252.IAA02458@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 An updated payment API draft will be posted very shortly which goes with the just posted SET Supplement draft. Thanks, Donald =================================================================== Donald E. Eastlake 3rd dee3@torque.pothole.com 140 Forest Avenue lde008@dma.isg.mot.com Hudson, MA 01749 USA +1 978-562-2827(h) +1 508-261-5434(w) Return-Path: Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A01JXG82@eListX.com>; Wed, 27 Sep 2000 06:32:04 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A01JXF81@eListX.com> (original mail from nsyracus@cnri.reston.va.us) ; Wed, 27 Sep 2000 06:32:03 -0400 (EDT) Received: from ELISTS-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A03JXF7Z@eListX.com> for ietf-trade-1104-outbound@reprocess.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 06:32:03 -0400 (EDT) Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-24 #44856) id <0G1J00A01JXF7Y@eListX.com> for ietf-trade@elists.eListX.com (ORCPT ietf-trade@lists.eListX.com); Wed, 27 Sep 2000 06:32:03 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by eListX.com (PMDF V6.0-24 #44856) with ESMTP id <0G1J007EYJXEWO@eListX.com> for ietf-trade@lists.eListX.com; Wed, 27 Sep 2000 06:32:02 -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 GAA07596; Wed, 27 Sep 2000 06:31:51 -0400 (EDT) Date: Wed, 27 Sep 2000 06:31:50 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-trade-iotp-v1.0-set-01.txt Sender: nsyracus@cnri.reston.va.us To: IETF-Announce: ; Cc: ietf-trade@lists.eListX.com Reply-to: Internet-Drafts@ietf.org Message-id: <200009271031.GAA07596@ietf.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_oS3L9Ru34bVhLFOwpjICyg)" List-Owner: List-Post: List-Subscribe: List-Unsubscribe: List-Archive: List-Help: , --Boundary_(ID_oS3L9Ru34bVhLFOwpjICyg) 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 : SET Supplement for the v1.0 Internet Open Trading Protocol (IOTP) Author(s) : Y. Kawatsura Filename : draft-ietf-trade-iotp-v1.0-set-01.txt Pages : 54 Date : 25-Sep-00 This document describes detailed Input/Output parameter for the IOTP Payment API and a procedure in the Payment Bridge for use SET as the payment protocol within Version 1.0 of the Internet Open Trading Protocol (IOTP). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0-set-01.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-iotp-v1.0-set-01.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-iotp-v1.0-set-01.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_oS3L9Ru34bVhLFOwpjICyg) Content-type: multipart/alternative; boundary="Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg)" --Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg) Content-type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000925145632.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-trade-iotp-v1.0-set-01.txt --Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg) Content-type: Message/External-body; name="draft-ietf-trade-iotp-v1.0-set-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000925145632.I-D@ietf.org> --Boundary_(ID_xZbHmPazDuUw1lCUy5YWdg)-- --Boundary_(ID_oS3L9Ru34bVhLFOwpjICyg)--