idnits 2.17.1 draft-tianguorong-hiep-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 355 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 85 instances of too long lines in the document, the longest one being 11 characters in excess of 72. ** There are 2 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (28 Nov 2016) is 2706 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Missing reference section? 'RFC2119' on line 277 looks like a reference -- Missing reference section? 'RFC2616' on line 280 looks like a reference -- Missing reference section? 'RFC1866' on line 284 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Shanghai Hongchuang WEB Technology Service Co., Ltd. 3 Intended Status: Experimental Tian Guorong 5 Curtis Young 7 Teo Engsoon 9 Monica Zhu 11 Jinzhu Wang 13 Jianhua Tong 15 28 Nov 2016 16 Expires: May 2017 18
20 HIEP: HTB Internet E-Wallet Protocol 22 draft-tianguorong-hiep-05 24 This Internet-Draft is submitted in full conformance with the provisions of BCP 25 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering Task Force 28 (IETF), its areas, and its working groups. Note that other groups may 29 also distribute working documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months and 32 may be updated, replaced, or obsoleted by other documents at any time. 33 It is inappropriate to use Internet-Drafts as reference material or to cite 34 them other than as "work in progress". 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/1id-abstracts.html 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html 42 This Internet-Draft will expire on Oct., 2015. 44 Copyright (c) 2016 IETF Trust and the persons identified as the document authors. 45 All rights reserved. This document is subject to BCP 78 and the IETF Trust's 46 Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 47 in effect on the date of publication of this document. Please review these 48 documents carefully, as they describe your rights and restrictions with respect 49 to this document. 51
53 Abstract: 55 This document describes an online-paying method that realizes the paying 56 addressing on the basis of HTTP protocol. It is for the purpose to 57 setup a normative and safe E-paying system standard, and specify the 58 definition of E-paying. In the last version, we described how this system 59 working with bank. We would like to introduce the HART pay application 60 functions we designed. 62 Table of Contents 64 1. Introduction 66 2. Conventions used in the Document 68 3. HIEP Problem Statements 70 4. HIEP Main Application Functions 72 5. Security Considerations 74 6. IANA Considerations 76 7. Conclusions 78 8. References 80
82 1. Introduction 84 Till now, there's no one paying addressing language to realize the online paying 85 or data set's interoperating that COULD be used for definite or name of E- 86 currency's widely used. Under the promoting by W3C, the future generation WEB of 87 the semantic web is defined as "the WEB concept structure which COULD be handled 88 directly by the machine". On the background of this technology, this ID describes 89 an E-currency paying public infrastructure of the bank pre-positive system in the 90 field of e-paying. Explanation of Nouns: Hart main account: Hart account platform 91 within the account, refers to the domain name of Hart. Hart bank main account 92 (Collection): Hart main account in the bank account corresponding to the open 93 account which is a main account. Hart bank accounts (payment): Hart main account 94 in the bank under the corresponding bank account of sub-account. 96 2. Conventions used in this document 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 99 "SHOULD NOT", "RECOMMENDED", "MAY", AND "OPTIONAL" in this document are to be 100 interpreted as described in RFC 2119 [RFC2119]. In this document, these words 101 will appear with that interpretation only when in ALL CAPS. Lower case uses of 102 these words are not to be interpreted as carrying RFC 2119 [RFC2119] significance. 104
106 3. HIEP Problem Statements 108 At present, differentiation of the payment communication and system structure are 109 formed by independent bank organizations or 3rd party payment company's leading 110 position, that they are using different payment models to describe the objects, 111 and formulate each standard. Those standards just extend the life time of each 112 existed systems, instead ensure the data exchange or dataset's interoperation 113 between different paying systems. Obviously, it will restrict the application 114 field online paying, and it COULD not reach the ability and technique of handling 115 the paying activities of all kinds of bank cards. The real-time of paying is 116 finally a bottleneck problem of the E-business development. Without solving this 117 problem, furthermore, it will bring the unsafe hidden trouble on the capital 118 operation. For the time being, we can only say in own scope utmost, as it only 119 can realize the online paying with safe within each own system. It cannot make 120 the real-time online paying, and can not reach the comprehensive integration of 121 huge scale (supranational, super-region, super-section). Currency's credit: The 122 currency is a credit symbol of paying, people trust it to make it as the 123 intermediation of substitution. It is accepted by the social due to its 124 characteristic advantage comparing the metal money on "Gold Standard System" or 125 "Silver Standard System". Obviously, the symbol in virtual paying organizations 126 transaction Must use a unique identifier, which COULD make into a definition when 127 people using. This is the credit problem in the paying procedure. 129
131 4.HIEP Main Application Functions 133 4.1 Enterprise Version Functions 135 4.1.1 Domain Name Activation 137 Enterprise users COULD activate its domain name account on APP after its 138 registration in bank, pls find details in HART Domain Name Activation Procedure. 140 4.1.2 Bank Main Account Balance Inquiry 142 COULD check the balance, frozen amount, withdrawal amount, unwithdrawal amount 144 4.1.3 Account Transaction List Inquiry 146 COULD check the user?s indicated transaction type, status, time, details. Details 147 include transaction flow number, date, time, amount, type and status. 149 4.1.4 Bank Reconciliation Statement Inquiry 151 Check account platform supplied reconciliation list everyday, to fulfill the 152 checking automatically. 154 4.1.5 Account Security Setup 156 Enterprise users COULD make the setup functions as transaction code and check-in 157 code etc. 159 Find the Transaction Password 161 Amend the Transaction Password 163 Find the Check-in Password 165 Amend the Transaction Password 167 4.1.6 Enterprise Registration Data Inquiry 169 In the users interface, enterprises COULD inquiry the data as domain name, company 170 name, company add., contact, telephone, email add., business license, settlement 171 bank, HART bank account, account status etc. 173
175 4.2 Individual Version Functions 177 4.2.1 Domain Activation 179 Individual users COULD activate its domain name account on APP(Individual Version) 180 after its registration in bank, pls find details in ?HART Domain Name Activation 181 Procedure?. 183 4.2.2 Bank Account Balance Inquiry 185 Service of account balance inquiry is available. 187 Inquiry Procedure: 189 4.2.2.1 Individual users send the inquiry request to account platform system by 190 its HART APP; 192 4.2.2.2 The platform make out the information related after received the request, 193 and revert 194 to the APP; 196 4.2.2.3 HART APP got the data from the platform, and reveal to the end user in 197 APP. 199 4.2.3 Account Rechargement 201 Individual users COULD realize the function of recharge from its bank account to 202 its own HART bank account. This function via APP inlay the bank WAP interface, 203 and fund transfering-fulfil through the bank WAP. Details pls find in Bank WAP 204 Procedure. 206
208 4.2.4 Account Transaction List Inquiry 210 Service of transaction details inquiry is available KEY phrase: opposite account, 211 transaction amount, transaction time, transaction type, flow number Inquiry 212 procedure: 214 4.2.4.1 Individual users send the inquiry request via its APP to HART account 215 platform system; 217 4.2.4.2 The platform make out the information related after received the request, 218 and revert to the APP; 220 4.2.4.3 HART APP got the data from the platform, and reveal to the end user in 221 APP. 223 4.2.5 Account Security Setup 225 Individual users COULD make the setup functions as transaction code and checkin 226 code etc. 228 Find the Transaction Password 230 Amend the Transaction Password 232 Find the Checkin Password 234 Amend the Transaction Password 236 4.2.6 Payment Setup 238 Single Transaction Limit Setup: To setup each single transaction maximum amount 239 within the bank limits; Day Transaction Limit Setup: To setup every days 240 accumulate transaction maximum amount within the bank limits. 242
244 4.2.6 Housekeeping Function 246 House regular payment business as water, gas, power fund by using the intermediary 247 service platform interface with bank. 249 4.2.8 Applications Collection 251 Contractor businesses push their application links or introductions to the 252 individual users via APP. Individual users COULD collect all the related and 253 interested HART contact business in this function, and collect those accounts. 255 5. Security Considerations 257 In order to realize the interconnection and mutual certification, the HIEP mutual 258 information approval is refer to X.509V3 extension. It is merged into PKCS#12, 259 the indicated HTB domain name Must be the first level domain name of a bank. Bind 260 the user's public key information with other identified information including the 261 username and email add., to complete the certification of users on the internet. 263 6.IANA Considerations 265 The IANA will configure the HTB port for HIEP. 267 7.Conclusions 269 This document describes the pre-position E-currency paying public infrastructure 270 of bank in the field of the internet E-paying, that realize the HIEP on the HTTP 271 protocol according to the open standard of W3C. 273
275 8.References: 277 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate Requirement Levels", 278 BCP 14, RFC 2119, March 1997 280 [RFC2616] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, 281 T.Berners- Lee, 282 "Hypertext Transfer Protocol - HTTP/1.1", June 1999 284 [RFC1866] T. Berners-Lee, D. Connolly, "Hypertext Markup Language - 2.0", 285 November 1995 287
289 Author's Address: 291 Tian Guorong 292 Shanghai Hongchuang WEB Technology Service Co., Ltd. 293 Bldg 14, Xinyun Economic Zone, Lane 3199 Zhenbei Rd. 294 Shanghai, China 295 Phone no.: 0086 135 8592 1617 296 Email: bill@iftg.org 298 Curtis Yang 299 Phone No.: 0086 138 0178 0703 300 Email: curtis.yang@iftg.org 302 Teo Engsoon 303 Phone No.: 0065 9015 4476 304 Email: francis@iftg.org 306 Monica Zhu 307 Phone No.: 0086 138 0178 0703 308 Email: monica@iftg.org 310 Jinzhu Wang 311 Phone No.: 0086 134 3566 8777 312 Email: jinzhuwang@iftg.org 314 Jianhua Tong 315 Phone No.: 0086 138 0297 9993 316 Email: jianhuatong@iftg.org