idnits 2.17.1 draft-ietf-trade-iotp-v1.0-protocol-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-03-29) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Bad filename characters: the document name given in the document, 'draft-ietf-trade-iotp-v1.0-', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-trade-iotp-v1.0-', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-trade-iotp-v1.0-', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == Mismatching filename: the document gives the document name as 'draft-ietf-trade-iotp-v1.0-', but the file name used is 'draft-ietf-trade-iotp-v1.0-protocol-01' == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (March 1999) is 9146 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 11 errors (**), 1 flaw (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT IOTP v1.0 3 September 1998 4 Expires March 1999 6 Internet Open Trading Protocol (IOTP) Version 1.0 7 -------- ---- ------- -------- ------ ------- --- 9 Donald E. Eastlake 3rd 11 Status of This Document 13 A later version of this draft, file name draft-ietf-trade-iotp-v1.0- 14 protocol-01.txt, is intended to become an Informational RFC. 15 Distribution of this document is unlimited. Comments should be sent 16 to the TRADE WG mailing list . 18 This document is an Internet-Draft. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months. Internet-Drafts may be updated, replaced, or obsoleted by 25 other documents at any time. It is not appropriate to use Internet- 26 Drafts as reference material or to cite them other than as a 27 ``working draft'' or ``work in progress.'' 29 To view the entire list of current Internet-Drafts, please check the 30 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 31 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 32 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 33 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 35 Technical control over the Internet Open Trading Protocol is being 36 transfered to the IETF TRADE working group from the OTP Consortium. 37 In some cases, the most current version of techncial documents is an 38 OTP Consortium version that has not yet been republished as an RFC 39 and is available from web site (which has not 40 yet been fully updates to indicate the technical switch to the IETF). 42 In this case, see 43 . It 45 is intended that that document be published as an later verson of 46 this internet-draft and then as an Informational RFC. 48 Abstract 50 The Internet Open Trading Protocol (IOTP) provides an interoperable 51 framework for Internet commerce. It is payment system independent 52 and can encapsulates a variety of payment systems. IOTP is able to 53 handle cases where such merchant roles as the shopping site, the 54 payment handler, the delivery handler of goods or services, and the 55 provider of customer care are performed by different parties or by 56 one party. 58 [This draft is a place holder for an internet-draft version of the 59 v1.0 starting point for the trade working group.] 61 Table of Contents 63 Status of This Document....................................1 65 Abstract...................................................2 66 Table of Contents..........................................2 68 1. Place Holder............................................3 69 2. Security Considerations.................................3 71 References.................................................4 72 Author's Address...........................................4 73 Expiration and File Name...................................4 75 1. Place Holder 77 Technical control over the Internet Open Trading Protocol is being 78 transfered to the IETF TRADE working group from the OTP Consortium. 79 In some cases, the most current version of technical documents is an 80 OTP Consortium version that has not yet been republished as an RFC 81 and is available from web site (which has not 82 yet been fully updates to indicate the technical switch to the IETF). 84 In this case, see 85 . It 87 is intended that that document be appropriately reformated / edited 88 and published as an later verson of this internet-draft and then as 89 an Informational RFC. 91 2. Security Considerations 93 Security of Internet Open Trade Protocol messages is primarily 94 dependent on signatures within IOTP as described in [v0.9.9]. 96 Note that the security of payment protocols transported by IOTP is 97 the responsibility of those payment protocols. 99 References 101 v0.9.9 - David Burdett, "Internet Open Trading Protocol, Version 102 0.9.9", OTP Consortium, 17 August 1998. 104 Author's Address 106 Donald E. Eastlake 3rd 107 IBM 108 318 Acton Street 109 Carlisle, MA 01741 USA 111 Telephone: +1 978 287 4877 112 +1 914 784-7913 113 FAX: +1 978 371 7148 114 email: dee3@us.ibm.com 116 Expiration and File Name 118 This draft expires December 1998. 120 Its file name is draft-ietf-trade-iotp-v1.0-protocol-01.txt.