HIEP: HTB Internet E-Wallet Protocol

Document Type Active Internet-Draft (individual)
Last updated 2016-11-28
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Draft             Shanghai Hongchuang WEB Technology Service Co., Ltd.

Intended Status: Experimental                                      Tian Guorong

                                                                   Curtis Young

                                                                    Teo Engsoon

                                                                     Monica Zhu

                                                                    Jinzhu Wang

                                                                   Jianhua Tong                                                                            
                                                                    28 Nov 2016                                                                                              
                                                              Expires: May 2017


HIEP: HTB Internet E-Wallet Protocol


This Internet-Draft is submitted in full conformance with the provisions of BCP
78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other groups may 
also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and
may be updated, replaced, or obsoleted by other documents at any time. 
It is inappropriate to use Internet-Drafts as reference material or to cite 
them other than as "work in progress".

The list of current Internet-Drafts can be accessed at 

The list of Internet-Draft Shadow Directories can be accessed at 

This Internet-Draft will expire on Oct., 2015.

Copyright (c) 2016 IETF Trust and the persons identified as the document authors.
All rights reserved. This document is subject to BCP 78 and the IETF Trust's 
Legal Provisions Relating to IETF Documents (http://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.



This document describes an online-paying method that realizes the paying
addressing on the basis of HTTP protocol. It is for the purpose to 
setup a normative and safe E-paying system standard, and specify the 
definition of E-paying. In the last version, we described how this system 
working with bank. We would like to introduce the HART pay application 
functions we designed. 

Table of Contents

1. Introduction

2. Conventions used in the Document

3. HIEP Problem Statements

4. HIEP Main Application Functions

5. Security Considerations

6. IANA Considerations

7. Conclusions

8. References


1. Introduction

Till now, there's no one paying addressing language to realize the online paying 
or data set's interoperating that COULD be used for definite or name of E-
currency's widely used. Under the promoting by W3C, the future generation WEB of 
the semantic web is defined as "the WEB concept structure which COULD be handled 
directly by the machine". On the background of this technology, this ID describes 
an E-currency paying public infrastructure of the bank pre-positive system in the 
field of e-paying. Explanation of Nouns: Hart main account: Hart account platform 
within the account, refers to the domain name of Hart. Hart bank main account 
(Collection): Hart main account in the bank account corresponding to the open 
account which is a main account. Hart bank accounts (payment): Hart main account
in the bank under the corresponding bank account of sub-account.

2. Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 
"SHOULD NOT", "RECOMMENDED", "MAY", AND "OPTIONAL" in this document are to be 
interpreted as described in RFC 2119 [RFC2119]. In this document, these words 
will appear with that interpretation only when in ALL CAPS. Lower case uses of 
these words are not to be interpreted as carrying RFC 2119 [RFC2119] significance.


3. HIEP Problem Statements

At present, differentiation of the payment communication and system structure are 
formed by independent bank organizations or 3rd party payment company's leading 
position, that they are using different payment models to describe the objects, 
and formulate each standard. Those standards just extend the life time of each 
Show full document text