One document matched: draft-eastlake-ecom-fields2-00.txt
INTERNET DRAFT D. Eastlake
OBSOLETES RFC 2706 IBM
T. Goldstein
Brodia
Expires April 2000 October 1999
draft-eastlake-ecom-fields2-00.txt
ECML v1.1: Field Specifications for E-Commerce
---- ----- ----- -------------- --- - --------
Status of this Memo
This draft is file name draft-eastlake-ecom-fields2-00.txt.
Distribution of this document is unlimited. Comments should be sent
to the author.
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. 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. Internet-Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet-
Drafts as reference material or to cite them other than as a
``working draft'' or ``work in progress.''
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) 1999, The Internet Society. All Rights Reserved.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 1]
INTERNET-DRAFT ECom Field Names October 1999
Abstract
Customers are frequently required to enter substantial amounts of
information at an Internet merchant site in order to complete a
purchase or other transaction, especially the first time they go
there. A standard set of information fields is defined as the first
version of an Electronic Commerce Modeling Language (ECML) so that
this task can be more easily automated, for example by wallet
software that could fill in fields. Even for the manual data entry
case, customers will be less confused by varying merchant sites if a
substantial number adopt these standard fields.
Acknowledgements
The following persons, in alphabetic order, contributed substantially
to the material herein:
George Burne, Trintech
Joe Coco, Microsoft
James Salsman
Kevin Weller, Visa
D. Eastlake, T. Goldstein PRE-DRAFT [Page 2]
INTERNET-DRAFT ECom Field Names October 1999
Table of Contents
Status of this Memo........................................1
Copyright Notice...........................................1
Abstract...................................................2
Acknowledgements...........................................2
Table of Contents..........................................3
1. Introduction............................................4
1.1 Background.............................................4
1.2 Relationship to Other Standards........................5
1.3 Areas Deferred to Future Versions......................5
2. Field Definitions and Schemas...........................6
2.1 Field List and Descriptions............................6
2.1.1 Field List...........................................6
2.1.2 Field Foot Notes.....................................8
2.2 Use in HTML...........................................10
2.3 An ECML 1.1 XML DTD...................................10
2.4 ECML 1.1 W3C XML Schema...............................12
2.5 ECML 1.1 IE5 XML Schema...............................12
3. Using The Fields.......................................13
3.1 Presentation of the Fields............................13
3.2 Methods and Flow of Setting the Fields................13
3.3 Examples..............................................14
3.3.1 HTML Example........................................14
3.3.2 XML Example.........................................15
4. Security and Privacy Considerations....................16
References................................................17
Appendix: Changes from ECML 1.0...........................18
Full Copyright Statement..................................19
Author's Address..........................................20
File name and Expiration..................................20
D. Eastlake, T. Goldstein PRE-DRAFT [Page 3]
INTERNET-DRAFT ECom Field Names October 1999
1. Introduction
1.1 Background
Today, numerous merchants are successfully conducting business on the
Internet using HTML-based forms. The data formats used in these forms
varies considerably from one merchant to another. End-users find the
diversity confusing and the process of manually filling in these
forms to be tedious. The result is that many merchant forms,
reportedly around two thirds, are abandoned during the fill in
process.
Software tools called electronic wallets can help this situation. A
digital wallet is an application or service that assists consumers in
conducting online transactions by allowing them to store billing,
shipping, payment, and preference information and to use this
information to automatically complete merchant interactions. This
greatly simplifies the check-out process and minimizes the need for a
consumer to think about and complete a merchant's form every time.
Digital wallets that fill forms have been successfully built into
browsers, as proxy servers, as helper applications to browsers, as
stand-alone applications, as browser plug-ins, and as server-based
applications. But the proliferation of electronic wallets has been
hampered by the lack of standards.
ECML (Electronic Commerce Modeling Language, <www.ecml.org>) Version
1.1 provides a set of simple guidelines for web merchants that will
enable electronic wallets from multiple vendors to fill in their web
forms. The end-result is that more consumers will find shopping on
the web to be easy and compelling.
The set of fields documented herein was developed by the ECML
Alliance (www.ecml.org) which now includes, in alphabetic order, the
following, the fifteen Steeting Committee members listed below and
numerous General Members some of whom are listed on the ECML web
site.
1. American Express (www.americanexpress.com>
2. AOL (www.aol.com)
3. Brodia (www.brodia.com)
4. Compaq (www.compaq.com)
5. CyberCash (www.cybercash.com)
6. Discover (www.discovercard.com)
7. FSTC (www.fstc.org)
8. IBM (www.ibm.com)
9. Mastercard (www.mastercard.com)
10. Microsoft (www.microsoft.com)
11. Novell (www.novell.com>
12. SETCo (www.setco.org)
D. Eastlake, T. Goldstein PRE-DRAFT [Page 4]
INTERNET-DRAFT ECom Field Names October 1999
13. Sun Microsystems (www.sun.com)
14. Trintech (www.trintech.com>
15. Visa International (www.visa.com)
The ECML fields were initially derived from and are consistent with
the W3C P3P base data schema at
<http://www.w3.org/TR/WD-P3P/basedata.html>.
1.2 Relationship to Other Standards
ECML Version 1.1 is not a replacement or alternative to SSL/TLS [RFC
2246], SET [SET], XML [XML], or IOTP [IOTP]. These are important
standards that provide functionality such as non-repudiatable
transactions, automatable payment scheme selection, and smart card
support.
ECML may be used with any payment mechanism. It simply allows a
merchant to publish consistent simple web forms.
Multiple wallets and multiple merchants interoperably support ECML.
This is an open standard. ECML is designed to be simple. Version 1.1
of the project adds no new technology to the web. A merchant can
adopt ECML and gain the support of these multiple Wallets by making
very simple changes to their site. Use of ECML requires no license.
1.3 Areas Deferred to Future Versions
Standardization of information fields transmitted from the merchant
to the consumer including merchant identification, considerations for
business purchasing cards, non-card payment mechanisms, wallet
activation, privacy related mechanisms, additional payment
mechanisms, currency exchange, and any sort of "negotiation" were
among the areas deferred to consideration in future versions. Hidden
or other special fields were minimized.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 5]
INTERNET-DRAFT ECom Field Names October 1999
2. Field Definitions and Schemas
The ECML Standard is primarily the definition and naming of fields.
These fields can be encoded in a variety of syntaxes and protocols.
Section 2.1 below lists and describes the fields, Section 2.2 gives
additional notes on HTML usage of the fields, and the remaining
subsections (2.3, 2.4, 2.5) provide an XML syntax and schemas for use
with the fields.
2.1 Field List and Descriptions
The fields are listed below along with the minimum data entry size to
allow. Note that these fields are hierarchically organized as
indicated by the embedded underscore ("_") characters. Appropriate
consumer to merchant transmission mechanisms may use this to request
and send aggregates, such as Ecom_Payment_Card_ExpDate to encompass
all the date components or Ecom_ShipTo to encompass all the ship to
components that the consumer is willing to provide. The labeling,
marshalling, unmarshalling of the components of such aggregates
depends on the data transfer protocol used.
2.1.1 Field List
IMPORTANT NOTE: "MIN" in the table below is the MINIMUM DATA SIZE TO
ALLOW FOR ON DATA ENTRY. It is NOT the minimum size for valid
contents of the field and merchant software should, in most
cases, be prepared to receive a longer or shorter value.
Merchant dealing with areas where, for example, the
state/province name or phone number is longer than the "Min"
given below must obviously permit longer data entry. In some
cases, however, there is a maximum size that makes sense and
where this is the case, it is documented in a Note for the
field.
FIELD NAME Min Notes
ship to title Ecom_ShipTo_Postal_Name_Prefix 4 ( 1)
ship to first name Ecom_ShipTo_Postal_Name_First 15
ship to middle name Ecom_ShipTo_Postal_Name_Middle 15 ( 2)
ship to last name Ecom_ShipTo_Postal_Name_Last 15
ship to name suffix Ecom_ShipTo_Postal_Name_Suffix 4 ( 3)
ship to company name Ecom_ShipTo_Postal_Company 20
ship to street line1 Ecom_ShipTo_Postal_Street_Line1 20 ( 4)
ship to street line2 Ecom_ShipTo_Postal_Street_Line2 20 ( 4)
ship to street line3 Ecom_ShipTo_Postal_Street_Line3 20 ( 4)
D. Eastlake, T. Goldstein PRE-DRAFT [Page 6]
INTERNET-DRAFT ECom Field Names October 1999
ship to city Ecom_ShipTo_Postal_City 22
ship to state/province Ecom_ShipTo_Postal_StateProv 2 ( 5)
ship to zip/postal code Ecom_ShipTo_Postal_PostalCode 14 ( 6)
ship to country Ecom_ShipTo_Postal_CountryCode 2 ( 7)
ship to phone Ecom_ShipTo_Telecom_Phone_Number 10 ( 8)
ship to email Ecom_ShipTo_Online_Email 40 ( 9)
bill to title Ecom_BillTo_Postal_Name_Prefix 4 ( 1)
bill to first name Ecom_BillTo_Postal_Name_First 15
bill to middle name Ecom_BillTo_Postal_Name_Middle 15 ( 2)
bill to last name Ecom_BillTo_Postal_Name_Last 15
bill to name suffix Ecom_BillTo_Postal_Name_Suffix 4 ( 3)
bill to company name Ecom_BillTo_Postal_Company 20
bill to street line1 Ecom_BillTo_Postal_Street_Line1 20 ( 4)
bill to street line2 Ecom_BillTo_Postal_Street_Line2 20 ( 4)
bill to street line3 Ecom_BillTo_Postal_Street_Line3 20 ( 4)
bill to city Ecom_BillTo_Postal_City 22
bill to state/province Ecom_BillTo_Postal_StateProv 2 ( 5)
bill to zip/postal code Ecom_BillTo_Postal_PostalCode 14 ( 6)
bill to country Ecom_BillTo_Postal_CountryCode 2 ( 7)
bill to phone Ecom_BillTo_Telecom_Phone_Number 10 ( 8)
bill to email Ecom_BillTo_Online_Email 40 ( 9)
receiptTo title Ecom_ReceiptTo_Postal_Name_Prefix 4 ( 1)
receiptTo first name Ecom_ReceiptTo_Postal_Name_First 15
receiptTo middle name Ecom_ReceiptTo_Postal_Name_Middle 15 ( 2)
receiptTo last name Ecom_ReceiptTo_Postal_Name_Last 15
receiptTo name suffix Ecom_ReceiptTo_Postal_Name_Suffix 4 ( 3)
receiptTo company name Ecom_ReceiptTo_Postal_Company 20
receiptTo street line1 Ecom_ReceiptTo_Postal_Street_Line1 20 ( 4)
receiptTo street line2 Ecom_ReceiptTo_Postal_Street_Line2 20 ( 4)
receiptTo street line3 Ecom_ReceiptTo_Postal_Street_Line3 20 ( 4)
receiptTo city Ecom_ReceiptTo_Postal_City 22
receiptTo state/province Ecom_ReceiptTo_Postal_StateProv 2 ( 5)
receiptTo postal code Ecom_ReceiptTo_Postal_PostalCode 14 ( 6)
receiptTo country Ecom_ReceiptTo_Postal_CountryCode 2 ( 7)
receiptTo phone Ecom_ReceiptTo_Telecom_Phone_Number 10 ( 8)
receiptTo email Ecom_ReceiptTo_Online_Email 40 ( 9)
name on card Ecom_Payment_Card_Name 30 (10)
card type Ecom_Payment_Card_Type 4 (11)
card number Ecom_Payment_Card_Number 19 (12)
card verification value Ecom_Payment_Card_Verification 4 (13)
card expire date day Ecom_Payment_Card_ExpDate_Day 2 (14)
card expire date month Ecom_Payment_Card_ExpDate_Month 2 (15)
card expire date year Ecom_Payment_Card_ExpDate_Year 4 (16)
card protocols Ecom_Payment_Card_Protocol 20 (17)
D. Eastlake, T. Goldstein PRE-DRAFT [Page 7]
INTERNET-DRAFT ECom Field Names October 1999
consumer order ID Ecom_ConsumerOrderID 20 (18)
character set Ecom_CharacterSet 20 (19)
language Ecom_Language 20 (20)
schema version Ecom_SchemaVersion 30 (21)
wallet id Ecom_WalletID 40 (22)
end transaction flag Ecom_TransactionComplete - (23)
FIELD NAME Min Notes
IMPORTANT NOTE: "MIN" in the table above is the MINIMUM DATA SIZE TO
ALLOW FOR ON DATA ENTRY. It is NOT the minimum size for valid
contents of the field and merchant software should, in most
cases, be prepared to receive a longer or shorter value.
Merchant dealing with areas where, for example, the
state/province name or phone number is longer than the "Min"
given below must obviously permit longer data entry. In some
cases, however, there is a maximum size that makes sense and
this is documented in a Note for the field.
2.1.2 Field Foot Notes
( 1) For example: Mr., Mrs., Ms., Dr. This field is commonly not
used.
( 2) May also be used for middle initial
( 3) For example: Ph.D., Jr. (Junior), 3rd, Esq. (Esquire). This
field is commonly not used.
( 4) Address lines must be filled in the order line1, then line2,
last line3.
( 5) 2 characters are the minimum for the US and Canada, other
countries may require longer fields. For the US use 2 character US
Postal state abbreviation.
( 6) Minimum field lengths for Postal Code will vary based on
international market served. Use 5 character or 5+4 ZIP for the US
and 6 character postal code for Canada. The size given, 14, is
believed to be the maximum required anywhere in the world.
( 7) Use [ISO 3166] standard two letter codes
<http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1.html> for
country names.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 8]
INTERNET-DRAFT ECom Field Names October 1999
( 8) 10 digits are the minimum for numbers local to the North
American Numbering Plan (<http://www.nanpa.com>: US, Canada and a
number of smaller Caribbean and Pacific nations (but not Cuba)),
other countries may require longer fields. Telephone numbers are
complicated by differing international access codes, variant
punctuation of area/city codes within countries, confusion caused by
the fact that the international access code in the NANP region is
usually the same as the "country code" for that area (1), etc. It
will probably be necessary to use heuristics or human examination
based on the telephone number and addresses given to figure out how
to actually call a customer. It is recommend that an "x" be placed
before extension numbers.
( 9) For example: jsmith@example.com
(10) The name of the cardholder.
(11) Use the first 4 letters of the association name: American
Express=AMER; Diners Club=DINE; Discover=DISC; JCB=JCB;
Mastercard=MAST; Visa=VISA.
(12) Includes the check digit at end but no spaces or hyphens [ISO
7812]. The Min given, 19, is the longest number permitted under the
ISO standard.
(13) An additional cardholder verification number printed on the card
(but not embossed or recorded on the magnetic stripe) such as
American Express' CIV, MasterCard's CVC2, and Visa's CVV2 values.
(14) The day of the month. Values: 1-31. A leading zero is ignored
so, for example, 07 is valid for the seventh day of the month.
(15) The month of the year. Jan - 1, Feb - 2, March - 3, etc.;
Values: 1-12. A leading zero is ignored so, for example, 07 is avlid
for July.
(16) The value in the wallet cell is always four digits, e.g., 1999,
2000, 2001, ...
(17) A space separated list of protocols available in connection with
the specified card. Initial list of case insensitive tokens: none,
set, setcert, iotp, and echeck. "Set" indicates usable with SET
protocol (i.e., is in a SET wallet) but does not have a SET
certificate. "Setcert" indicates same but does have a set
certificate. "iotp" indicates the IOTP protocol [IOTP] is supported
at the customer. "echeck" indicates that the eCheck protocol
[eCheck] is supported at the customer. "None" indicates that
automatic field fill is operating but there is no SET wallet or the
card is not entered in any SET wallet.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 9]
INTERNET-DRAFT ECom Field Names October 1999
(18) A unique order ID generated by the consumer software.
(19) A name registered with [IANA] as a "charset". Used only if it
is necessary to explicitly override the character set indication
mechanism for the data transfer protocol in use. For example, an
HTML form POST in a different character set such as ISO-2022-JP
instead of ISO-8859-1. Will not work in general if character sets
are different width.
(20) Language code as specified in [RFC 1766]. Used only if it is
necessary to explicitly override the language indication mechanism
for the data transfer protocol in use. For example, not used with
XML which has its own language taking facility.
(21) URI indicating version of this set of fields. Usually a hidden
field. Equal to "http://www.ecml.org/version/1.1" for this version.
(22) A string to identify the source and version of the form fill
software that is acting on behalf of the user. Should contain
company and/or product name and version. Example "Wallets Inc.,
SuperFill, v42.7". Usually a hidden field.
(23) A flag to indicate that this web-page/aggregate is the final one
for this transaction. Usually a hidden field.
2.2 Use in HTML
The normal use of ECML is HTML is as a form with input ield names
identical to those given in section 2.1 above. In general, <INPUT>
tags with type text, hidden, and password must be supported as must
<SELECT> tags.
Internationalization in HTML is limited. The information available
with the HTML form Method as to character set and language may be
used. Alternatively, these may be over-ridden for the entire form
reponse with the HTML only Ecom_CharSet and/or Ecom_Language fields.
2.3 An ECML 1.1 XML DTD
Below is an XML DTD that can be used for the XML encoding of ECML
v1.1 Fields.
For internationaization of [XML] ECML, use the general XML character
encoding provisions, which mandate support of UTF-8 and UTF-16 and
permit support of other character sets, and the xml:lang attribute
which may be used to specify language information.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 10]
INTERNET-DRAFT ECom Field Names October 1999
<!-- Electronic Commerce Modeling Language 1.1 -->
<!ELEMENT Ecom ( #PCDATA | ShipTo | BillTo | ReceiptTo | Payment |
TransacationComplete )* >
<!ATTLIST Ecom
id ID #IMPLIED
ConsumerOrderID CDATA #IMLIED
SchemaVersion ( "http://www.ecml.org/version/1.0" |
"http://www.ecml.org/version/1.1" )
#IMPLIED
WalletID CDATA #IMPLIED >
<!ELEMENT ShipTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST ShipTo
id ID #IMPLIED >
<!ELEMENT BillTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST BillTo
id ID #IMPLIED >
<!ELEMENT ReceiptTo ( #PCDATA | Postal | Telecom | Online )* >
<!ATTLIST ReceiptTo
id ID #IMPLIED >
<!ELEMENT Postal ( #PCDATA | Name | Company |
Street | City | StateProv )* >
<!ATTLIST Postal
id ID #IMPLIED
PostalCode NMTOKEN #IMPLIED
CountryCode NMTOKEN #IMPLIED >
<!ELEMENT Name EMPTY >
<!ATTLIST Name
id ID #IMPLIED
Prefix NMTOKEN #IMPLIED
First NMTOKEN #IMPLIED
Middle NMTOKEN #IMPLIED
Last NMTOKEN #IMPLIED
Suffix NMTOKEN #IMPLIED >
<!ELEMENT Street EMPTY >
<!ATTLIST Street
Line1 CDATA #REQUIRED
Line2 CDATA #IMPLIED
Line3 CDATA #IMPLIED >
<!ELEMENT Company #PCDATA >
<!ELEMENT City #PCDATA >
D. Eastlake, T. Goldstein PRE-DRAFT [Page 11]
INTERNET-DRAFT ECom Field Names October 1999
<!ELEMENT StateProv #PCDATA >
<!ELEMENT Telecom ( #PCDATA | Phone )* >
<!ELEMENT Phone EMPTY >
<!ATTLIST Phone
id ID #IMPLIED
Number CDATA #REQUIRED >
<!ELEMENT Online ( #PCDATA | Email )* >
<!ELEMENT Email #PCDATA >
<!ELEMENT Payment Card>
<!ELEMENT Card ExpDate >
<!ATTLIST Card
Name CDATA #IMPLIED
Type NMTOKEN #IMPLIED
Number NMTOKEN #REQUIRED
Protocols NMTOKENS #IMPLIED
Verficiation NMTOKEN #REQUIRED >
<!ELEMENT ExpDate EMPTY >
<!ATTLIST ExpDate
Day NMTOKEN #IMPLIED
Month NMTOKEN #REQUIRED
Year NMTOKEN #REQUIRED >
<!ELEMENT TransactionComplete EMPTY>
...
2.4 ECML 1.1 W3C XML Schema
...
2.5 ECML 1.1 IE5 XML Schema
...
D. Eastlake, T. Goldstein PRE-DRAFT [Page 12]
INTERNET-DRAFT ECom Field Names October 1999
3. Using The Fields
To conform to this document, the field names must be structured as
listed in section 2 above. Note: this does not impose any restriction
on the user visible labeling of fields, just on their names as used
in communication with the merchant.
3.1 Presentation of the Fields
There is no necessary implication as to the order or manner of
presentation. Some merchants may wish to ask for more information,
some less by omitting fields. Some merchants may ask for the
information they want in one interaction or web page, others may ask
for parts of the information at different times in multiple
interactions or different web pages. For example, it is common to
ask for "ship to" information earlier, so shipping cost can be
computed, before the payment method information. Some merchants may
require that all the information they request be provided while other
make much information optional. Etc.
There is no way with version 1.1 of ECML to indicate what fields the
merchant considers mandatory. From the point of view of customer
software, all fields are optional to complete. However, the merchant
may give an error or re-present a request for information if some
field it requires is not completed, just as it may if a field is
completed in a manner it considers erroneous.
3.2 Methods and Flow of Setting the Fields
There are a variety of methods of communication possible between the
customer and the merchant by which the merchant can indicate what
fields they want that the consumer can provide. Probably the easiest
to use for currently deployed software is as fields in an [HTML] form
(see section 2.2). Other possibilities are to use the IOTP
Authenticate transaction [IOTP], an [XML] exchange, or proprietary
protocols.
User action or the appearance of the Ecom_SchemaVersion field are
examples of triggers that could be used to initiate a facility
capable of filling in fields. Because some wallets may require user
activtaion, there should be at least one user visible Ecom field on
every page with any Ecom fields present. It is also required that
the Ecom_SchemaVersion field, which is usually a hidden field, be
included on every web page that has any Ecom fields.
Because web pages can load very slowly, it may not be clear to an
D. Eastlake, T. Goldstein PRE-DRAFT [Page 13]
INTERNET-DRAFT ECom Field Names October 1999
automated field fill-in function when it is finished filling in
fields on a web page. For this reason, it is recommended that the
Ecom_SchemaVersion field be the last Ecom field on a web page.
Merchant requests for information can extend over several
interactions or web pages. Without further provision, a facility
could either require re-starting on each page or possibly violate or
appear to violate privacy by continuing to fill in fields for pages
beyond with end of the transaction with a particular merchant. For
this reason the Ecom_TransactionComplete field, which is normally
hidden, is provided. It is recommended that it appear on the last
interaction or web page involved in a transaction, just before an
Ecom_SchemaVersion field, so that multi-web-page automated field fill
in logic could know when to stop if it chooses to check for this
field.
3.3 Examples
3.3.1 HTML Example
An example HTML form might be as follows:
<HTML>
<HEAD>
<title> eCom Fields Example </title>
</HEAD>
<BODY>
<FORM action="http://ecom.example.com" method="POST">
Please enter card information:
<p>Your name on the card
<INPUT type="text" name="Ecom_Payment_Card_Name" SIZE=40>
<br>The card number
<INPUT type="text" name="Ecom_Payment_Card_Number" SIZE=19>
<br>Expiration date (MM YY)
<INPUT type="text" name="Ecom_Payment_Card_ExpDate_Month" SIZE=2>
<INPUT type="text" name="Ecom_Payment_Card_ExpDate_Year" SIZE=4>
<INPUT type="hidden" name="Ecom_Payment_Card_Protocol">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.1">
<br>
<INPUT type="submit" value="submit"> <INPUT type="reset">
</FORM>
</BODY>
</HTML>
After all of the pages are submitted, the merchant will reply with a
D. Eastlake, T. Goldstein PRE-DRAFT [Page 14]
INTERNET-DRAFT ECom Field Names October 1999
confirmation page informing both the user and the wallet that the
transaction is complete.
<HTML>
<HEAD>
<title> eCom Transaction Complete Example </title>
</HEAD>
<BODY>
<FORM>
Thank you for your order. It will be shipped in several days.
<INPUT type="hidden" name="Ecom_TransactionComplete">
<INPUT type="hidden" name="Ecom_SchemaVersion"
value="http://www.ecml.org/version/1.1">
</FORM>
</BODY>
</HTML>
3.3.2 XML Example
...
D. Eastlake, T. Goldstein PRE-DRAFT [Page 15]
INTERNET-DRAFT ECom Field Names October 1999
4. Security and Privacy Considerations
The information called for by many of these fields is sensitive and
should be secured if being sent over the public Internet or through
other channels where it can be observed. Mechanisms for such
protection are not specified herein but channel encryption such as
SSL/TLS [RFC 2246] or IPSec [RFC 2411] would be appropriate in many
cases.
User control over release of such information is needed to protect
the user's privacy.
A wallet that is installed on a shared or public terminal should be
configurable such that the ECML memory of address and other contact
information is fully disabled. This is vital to protect the privacy
of library patrons, students, and customers using public terminals,
and children who might, for example, use a form on a public terminal
without realizing that their information is being stored.
When contact information is stored, the operator should have an
option to protect the information with a password, without which the
information might be unavailable, even to someone who has access to
the file(s) in which it is being stored. This would also allow for a
convenient method for multiple people to use their own ECML
information from the same browser.
Any multi-web-page or other multi-aggregate field fill in or data
provision mechanism should check for the Ecom_TransactionComplete
field and cease automated fill when it is encountered until fill is
further authorized.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 16]
INTERNET-DRAFT ECom Field Names October 1999
References
[eCheck] -
[HTML] - HTML 3.2 Reference Specification <http://www.w3.org/TR/REC-
html32.html>, D. Raggett, January 1997.
[IANA] - Internet Assigned Numbers Authority, Official Names for
Character Sets, ed. Keld Simonsen et al. <ftp://ftp.isi.edu/in-
notes/iana/assignments/character-sets>.
[ISO 3166] - Codes for the representation of names of countries,
<http://www.din.de/gremien/nas/nabd/iso3166ma>
[ISO 7812] - "Identification card - Identification of issuers - Part
1: Numbering system"
[RFC 1766] - "Tags for the Identification of Languages", H.
Alvestrand. March 1995.
[RFC 2026] - "The Internet Standards Process -- Revision 3", S.
Bradner, October 1996.
[RFC 2246] - "The TLS Protocol: Version 1.0", T. Dierks, C. Allen.
January 1999.
[RFC 2411] - "IP Security: Document Roadmap", R. Thayer, N.
Doraswany, R. Glenn. November 1998.
[RFC 2706] - "ECML v1: Field Names for E-Commerce", D. Eastlake, T.
Goldstein, September 1999.
[IOTP] - Internet Open Trading Protocol, being specified in the IETF
TRADE working group, D. Burdett
[SET] - Secure Electronic Transaction,
<http://www.setco.org/set_specifications.html>
[XML] - Extensible Markup Language (XML) 1.0,
<http://www.w3.org/TR/1998/REC-xml-19980210>, T. Bray, J. Paoli, C.
M. Sperberg-McQueen
D. Eastlake, T. Goldstein PRE-DRAFT [Page 17]
INTERNET-DRAFT ECom Field Names October 1999
Appendix: Changes from ECML 1.0
ECML 1.0 is documented in RFC 2706.
(1) Fields added are listed below. Adding fields is a backward
compatible change
(1a) Wallet ID to identify source and version of the form fill
agent acting for the consumer.
(1b) Company Name
(1c) Ecom_CharacterSet and Ecom_Language
(1d) ...
(2) Change Ecom_SchemaVersion field value to
"http://www.ecml.org/version/1.1".
(3) Addition of XML DTD, XML Schemas, and XML example.
(4) Add "iotp" and "echeck" as allowed tokens in
Ecom_Payment_Card_Protocol.
(5) Specify that a leading zero is permitted in day and month number
fields.
(6) Change "Security Considerations" section to "Security and Privacy
Consderations" and add material.
(7) Add internationalization material to HTML and XML subsections of
section 2.
(8) Enumerate HTML form elements that must be supported (section 2.2)
including SELECT.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 18]
INTERNET-DRAFT ECom Field Names October 1999
Full Copyright Statement
Copyright (C) 1999, The Internet Society. All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 19]
INTERNET-DRAFT ECom Field Names October 1999
Author's Address
Donald E. Eastlake, 3rd
IBM, J1-N63
17 Skyline Drive
Hawthorne, NY 10532 USA
tel: +1-914-784-7913
fax: +1-914-784-3833
email: dee3@us.ibm.com
Ted Goldstein
Brodia
221 Main Street, Suite 1530
San Francisco, CA 94105 USA
tel: +1 415-495-3100 x222
fax: +1 415-495-3177
email: tgoldstein@brodia.com
File name and Expiration
This file is draft-eastlake-ecom-fields2-00.txt.
It expires April 2000.
D. Eastlake, T. Goldstein PRE-DRAFT [Page 20]
| PAFTECH AB 2003-2026 | 2026-04-23 15:55:03 |