INTERNET DRAFT Donald E. Eastlake 3rd Motorola Laboratories Expires December 2004 June 2004 Electronic Commerce Modeling Language (ECML): Version 2 Specification Status of this Memo This draft is intended to become an Informational RFC. Distribution of this document is unlimited. Comments should be sent to the author or the IETF TRADE working group . This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. 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 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) The Internet Society 2004. This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Abstract Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically organized payment related information field names in an XML syntax are defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meeting the requirements of RFC 3505. D. Eastlake 3rd [Page 1] INTERNET-DRAFT ECML v2 Specification June 2004 Acknowledgements The following, listed is alphabetic order, have contributed to the material herein: Ray Bellis, Jon Parsons, Lauri Piikivi, David Shepherd, James J. Peter. Table of Contents Status of this Memo........................................1 Abstract...................................................1 Acknowledgements...........................................2 Table of Contents..........................................2 1. Introduction............................................3 1.2 History and Relationship to Other Standards............3 2. Field Definitions and DTD...............................4 2.1 Field List and Descriptions............................4 2.1.1 The Field List.......................................4 2.1.2 Field Foot Notes.....................................8 2.2 ECML v2 XML DTD.......................................12 2.3 ECML v2 XML Schema....................................17 3. Usage Notes for ECML v2................................18 3.1 Presentation of the Fields............................18 3.2 Methods and Flow of Setting the Fields................18 4. Security and Privacy Considerations....................19 5. IANA Considerations....................................20 5.1 ECML v2 URN Template..................................20 5.1.1 Subregistration of v2.0.............................21 5.2 IANA Registries.......................................21 Normative References......................................22 Informative References....................................23 Appendix: Changes from v1.1 to v2.........................25 Intellectual Property Rights and Disclaimer...............26 Author's Address..........................................26 File name and Expiration..................................27 D. Eastlake 3rd [Page 2] INTERNET-DRAFT ECML v2 Specification June 2004 1. Introduction Numerous parties are conducting business on the Internet using ad hoc fields and forms. The data formats and structure can vary considerably from one party to another. Where forms are filled out manually, many users find the diversity confusing and the process of manually filling in these forms to be tedious and error prone. Software tools including electronic wallets can help this situation. Such tools can assist in conducting online transactions by storing billing, shipping, payment, preference, and similar information and using this information to automatically complete the data sets required by interactions. For example, software that fills out forms has 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 more automated transactions software has been hampered by the lack of standards. ECML (Electronic Commerce Modeling Language) provides a set of hierarchical payment oriented data structures that will enable automated software, including electronic wallets, from multiple vendors to supply and query for needed data in a more uniform manner. Version 2.0 extends ECML Version 1.0 [RFC 2706] and 1.1 [RFC 3106] as described in the Appendix to this document. These enhancements include support for additional payment mechanisms and transaction information and use of XML as the exemplar syntax. Likely uses for ECML v2 are consumer payment information input and business-to-business transactions. The first is still likely to occur through HTML forms. The second is more likely to use XML documents. ECML is designed to provide a simple baseline useful in a variety of contexts. 1.2 History and Relationship to Other Standards The ECML fields were initially derived from the W3C P3P base data schema [P3P BASE] by the ECML Alliance as described in [RFC 2706, 3106]. Technical development and change control of ECML was then transferred to the IETF. In version 2, ECML is extended by the fields in a W3C P3P Note related to eCommerce [P3P ECOM], by [ISO 8583], and other sources. Its primary form is now an XML syntax. D. Eastlake 3rd [Page 3] INTERNET-DRAFT ECML v2 Specification June 2004 2. Field Definitions and DTD The ECML Standard is the definition and naming of a hierarchically structured set of fields and the provision of an optional XML syntax for their transmission. These fields can also be encoded in other syntaxes. Regardless of the encoding used, they can be transmitted via a variety of protocols. Section 2.1 below lists and describes the fields and Section 2.2 provides an XML DTD for use with the fields. To conform to this standard, field names must be structured and named as closely to the structure and naming listed below as practical given the syntax and transaction protocol in use. (NOTE: this does not impose any restriction on human visible labeling of fields, just on their name or names as used in on-the-wire communication.) 2.1 Field List and Descriptions The fields are listed below. along with the minimum data entry size to allow. Implementations may accept larger data sizes, where that makes sense, and for some applications, will need to allow for larger data sizes. Note that these fields are hierarchically organized as indicated in this table by the embedded underscore ("_") characters. Appropriate data 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 address components that a consumer is willing to provide. The labeling, marshalling, unmarshalling of the components of such aggregates depends on the data transfer protocol used. The recommended syntax is XML as specified in Section 2.2. 2.1.1 The Field List The table below is the ECMLv2 field list. The NAME column gives the structured string name of each field as explained above. The MIN column below is the minimum data size the MUST be allowed for 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 D. Eastlake 3rd [Page 4] INTERNET-DRAFT ECML v2 Specification June 2004 sense and where this is the case, it is usually documented in a Note for the field. The following fields are typically used to communicate from the customer to the merchant: FIELD NAME Min Notes ship to title Ecom_ShipTo_Postal_Name_Prefix 4 ( 1) ship to first name Ecom_ShipTo_Postal_Name_First 15 (54) ship to middle name Ecom_ShipTo_Postal_Name_Middle 15 ( 2) ship to last name Ecom_ShipTo_Postal_Name_Last 15 (54) 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) 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 (54) bill to middle name Ecom_BillTo_Postal_Name_Middle 15 ( 2) bill to last name Ecom_BillTo_Postal_Name_Last 15 (54) 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) receipt to (32) receipt to title Ecom_ReceiptTo_Postal_Name_Prefix 4 ( 1) receipt to first name Ecom_ReceiptTo_Postal_Name_First 15 (54) receipt to middle name Ecom_ReceiptTo_Postal_Name_Middle 15 ( 2) receipt to last name Ecom_ReceiptTo_Postal_Name_Last 15 (54) receipt to name suffix Ecom_ReceiptTo_Postal_Name_Suffix 4 ( 3) receipt to company name Ecom_ReceiptTo_Postal_Company 20 receipt to street line1 Ecom_ReceiptTo_Postal_Street_Line1 20 ( 4) receipt to street line2 Ecom_ReceiptTo_Postal_Street_Line2 20 ( 4) receipt to street line3 Ecom_ReceiptTo_Postal_Street_Line3 20 ( 4) D. Eastlake 3rd [Page 5] INTERNET-DRAFT ECML v2 Specification June 2004 receipt to city Ecom_ReceiptTo_Postal_City 22 receipt to state/province Ecom_ReceiptTo_Postal_StateProv 2 ( 5) receipt to postal code Ecom_ReceiptTo_Postal_PostalCode 14 ( 6) receipt to country Ecom_ReceiptTo_Postal_CountryCode 2 ( 7) receipt to phone Ecom_ReceiptTo_Telecom_Phone_Number 10 ( 8) receipt to 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 issuer number Ecom_Payment_Card_IssueNumber 2 (53) 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 valid date day Ecom_Payment_Card_ValidFrom_Day 2 (14) card valid date month Ecom_Payment_Card_ValidFrom_Month 2 (15) card valid date year Ecom_Payment_Card_ValidFrom_Year 4 (16) card protocols Ecom_Payment_Card_Protocol 20 (17) loyalty card name Ecom_Loyalty_Card_Name 30 (10) loyalty card type Ecom_Loyalty_Card_Type 20 (52) loyalty card number Ecom_Loyalty_Card_Number 40 (34) loyalty card verification Ecom_Loyalty_Card_Verification 4 (13) loyalty card expire day Ecom_Loyalty_Card_ExpDate_Day 2 (14) loyalty card expire month Ecom_Loyalty_Card_ExpDate_Month 2 (15) loyalty card expire year Ecom_Loyalty_Card_ExpDate_Year 2 (16) loyalty card valid day Ecom_Loyalty_Card_ValidFrom_Day 2 (14) loyalty card valid month Ecom_Loyalty_Card_ValidFrom_Month 2 (15) loyalty card valid year Ecom_Loyalty_Card_ValidFrom_Year 4 (16) consumer order ID Ecom_ConsumerOrderID 20 (18) user ID Ecom_User_ID 40 (19) user password Ecom_User_Password 20 (19) user certificate Ecom_User_Certificate_URL 128 (35) user data country Ecom_UserData_Country 2 ( 7) user data language Ecom_UserData_Language 30 (33) D. Eastlake 3rd [Page 6] INTERNET-DRAFT ECML v2 Specification June 2004 user data gender Ecom_UserData_Gender 1 (36) user data birth day Ecom_UserData_BirthDate_Day 2 (14) user data birth month Ecom_UserData_BirthDate_Month 2 (15) user data birth year Ecom_UserData_BirthDate_Year 4 (16) user data preferences Ecom_UserData_Preferences 60 (34) schema version Ecom_SchemaVersion 30 (20) wallet id Ecom_WalletID 40 (21) wallet URL Ecom_Wallet_Location 128 (35) customer device ID Ecom_Device_ID 20 (37) customer device type Ecom_Device_Type 20 (38) end transaction flag Ecom_TransactionComplete - (22) The following fields are typically used to communicate from the merchant to the consumer: FIELD NAME Min Notes merchant home domain Ecom_Merchant 128 (23) processor home domain Ecom_Processor 128 (24) transaction identifier Ecom_Transaction_ID 128 (25) transaction URL inquiry Ecom_Transaction_Inquiry 500 (26) transaction amount Ecom_Transaction_Amount 128 (27) transaction currency Ecom_Transaction_CurrencyCode 3 (28) transaction date Ecom_Transaction_Date 80 (29) transaction type Ecom_Transaction_Type 24 (30) transaction signature Ecom_Transaction_Signature 160 (31) end transaction flag Ecom_TransactionComplete - (22) The following fields are used to communicate between the merchant and a processor acting for the merchant (such a processor is commonly called an acquirer and is frequently a bank): FIELD NAME Min Notes merchant identifier Ecom_Merchant_ID 8 merchant terminal Ecom_Merchant_Terminal_ID 8 (39) merchant terminal data Ecom_Merchant_Terminal_Data 128 transaction process code Ecom_Transaction_ProcessingCode 6 (40) transaction reference Ecom_Transaction_Reference_ID 12 transaction acquirer Ecom_Transaction_Acquire_ID 13 (41) transaction forward Ecom_Transaction_Forward_ID 13 (42) transaction trace Ecom_Transaction_Trace_Audit 6 (43) transaction effective date Ecom_Transaction_Effective_Date 4 (44) transaction CID Ecom_Transaction_CID 8 D. Eastlake 3rd [Page 7] INTERNET-DRAFT ECML v2 Specification June 2004 transaction POS Ecom_Transaction_POSCode 12 (45) transaction private use Ecom_Transaction_PrivateUseData 166 transaction response Ecom_Transaction_ResponseData 27 transaction approval code Ecom_Transaction_ApprovalCode 12 (46) transaction retrieval code Ecom_Transaction_RetrievalCode 128 transaction response action Ecom_Transaction_ActionCode 13 (47) transaction reason Ecom_Transaction_ReasonCode 4 transaction AAV Ecom_Transaction_AAV 3 transaction settlement date Ecom_Transaction_Settle_Date 4 (48) transaction capture date Ecom_Transaction_Capture_Date 4 (49) transaction Track 1 Ecom_Transaction_Track1 39 (50) transaction Track 2 Ecom_Transaction_Track2 39 (51) 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, and last line3. Thus, for example, it is an error for line1 to be null if lines2 or line3 is not. ( 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 country codes. ( 8) 10 digits are the minimum for numbers within the North American Numbering Plan (: US, Canada and a number of Caribbean and smaller 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, etc. While it is desirable for telephone numbers to be in standard international format [E.164], it may 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 since may people will enter local formatted numbers without area/access codes. It is recommend that an "x" be placed before D. Eastlake 3rd [Page 8] INTERNET-DRAFT ECML v2 Specification June 2004 extension numbers. ( 9) For example: jsmith@example.com (10) The name of the cardholder as it appears on the card. (11) Case insensitive. Use up to the first 4 letters of the association name (102): AMER American Express BANK Bankcard (Australia) DC DC (Japan) DINE Diners Club DISC Discover JCB JCB MAST Mastercard NIKO Nikos (Japan) SAIS Saison (Japan) UC UC (Japan) UCAR UCard (Taiwan) 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 valid 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 echeck simcard phoneid D. Eastlake 3rd [Page 9] INTERNET-DRAFT ECML v2 Specification June 2004 "Set" indicates usable with SET protocol (i.e., is in a SET wallet) but does not have a SET certificate [SET]. "Setcert" indicates usable with SET and has a set certificate [SET]. "iotp" indicates the IOTP protocol [RFC 2801] is supported at the customer. "echeck" indicates that the eCheck protocol [eCheck] is supported at the customer. "simcard" indicates use the transaction instrument built into a Cellphone subscriber for identification. "phoneid" indicates use for the transaction of a billable phone number. "None" indicates that automatic field fill is operating but there is no further information. (18) A unique order ID generated by the consumer software. (19) The user ID and password fields are used in cases where the user has a pre-established account with the merchant to which access is authenticated by such values. (20) URI [RFC 2396]] indicating version of this set of fields. Usually a hidden field. Equal to "urn:ietf:params:ecml:v2.0" for this version. See Section 5 below. (21) A string to identify the source and version of form fill software that is acting on behalf of a user. Should contain company and/or product name and version. Example "Wallets Inc., SuperFill, v42.7". (101) (22) A flag to indicate that this web-page/aggregate is the final one for this transaction. (101) (23) Merchant domain name [RFC 1034] such as www.merchant.example. (101) (24) Domain name [RFC 1034] of the gateway transaction processor that is actually accepting the payment on behalf of the merchant such as www.processor.example. (101) (25) A Transaction identification string whose format is specific to the processor. (101) (26) A URL [RFC 2396] that can be invoked to inquire about the transaction. (100) (101) (27) The amount of the transaction in ISO currency format [ISO 4217]. This is two integer numbers with a period in between but no other currency marks (such as a $ dollar sign). (101) (28) This is the three letter ISO currency code [ISO 4217]. For example, for US dollars it is USD. (101) (29) ISO Transaction date. (101) D. Eastlake 3rd [Page 10] INTERNET-DRAFT ECML v2 Specification June 2004 (30) The type of the transaction if known. (101) Currently a value from the following list debit credit (31) A digital signature base64 encoded [RFC 2045]. (101) (32) The ReceiptTo fields are used when the BillTo entity, location, or address and the ReceiptTo entity, location, or address are different. For example, when using some forms of Corporate Purchasing Cards or Agent Purchasing Cards, the individual card holder would be in the ReceiptTo fields and the corporate or other owner would be in the BillTo fields. (33) An IETF Language Tag as defined in [RFC 3066]. (34) User preferences as specified by the merchant. (102) (35) Uniform Resource Locator [RFC 2396] for accessing the customer's "wallet" software. (100) (36) A single capital letter, M=male, F=Female, U=Unknown [ISO 5218]. (37) An immutable device identification or serial number. (102) (38) User understandable device brand name. (102) (39) [ISO 8583] field "card acceptor terminal identification". (40) [ISO 8583] field "processing code". (41) [ISO 8583] field "acquiring institution identification code". (42) [ISO 8583] field "forwarding institution identification code". (43) [ISO 8583] field "system trace audit field". (44) [ISO 8583] field "date effective". (45) [ISO 8583] field "point of sale date code". (46) [ISO 8583] field "approval code". (47) [ISO 8583] field "action code". (48) [ISO 8583] field "date settlement". (49) [ISO 8583] field "date capture". (50) [ISO 8583] field "trace 1 data". D. Eastlake 3rd [Page 11] INTERNET-DRAFT ECML v2 Specification June 2004 (51) [ISO 8583] field "trace 2 data". (52) User recognizable loyalty card brand name. Values for this field are not controlled and there is no IANA or other registry for them. (102) (53) The card issue number required by the UK based Switch and Solo acquirers. (54) The field names "first_name" and "last_name" have been retained for compatibility with earlier versions of ECML. However, "last_name" should be understood to refer to family or inherited names(s) while "first_name" is the first given or non-inherited name and "middle_name" is the subsequent given or non-inherited name or names if any. Meta notes (referenced by other notes): (100) ECML, being a basic field naming and structuring convention, does not impose any particular requirements on these URLs. It is to be expected that most applications that make use of ECML will impose limitations and perform checking to be sure that provided URLs conform to such limitations before attempting to invoke them. (101) This is a field which, when presented as a web page, is usually hidden. (102) ASCII [ASCII] character string with no leading or trailing white space. 2.2 ECML v2 XML DTD For internationalization of ECML, use the general XML character encoding provisions [XML], 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 3rd [Page 13] INTERNET-DRAFT ECML v2 Specification June 2004 D. Eastlake 3rd [Page 16] INTERNET-DRAFT ECML v2 Specification June 2004 2.3 ECML v2 XML Schema TBD D. Eastlake 3rd [Page 17] INTERNET-DRAFT ECML v2 Specification June 2004 3. Usage Notes for ECML v2 This section provides a general usage guide for ECML v2. 3.1 Presentation of the Fields This standard merely names fields and specifies their content and hierarchical organization. It does not constrain the order or completeness of communication of or query for these fields. Some parties may wish to provide or ask for more information, some less by omitting fields. Some 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 parties may require that all the information they request be provided while other make much information optional. Other variations are likely. Every element may be flagged as a query or assertion by including the optional Mode attribute with the value "Query" or "Assert" respectively. The Mode attribute effects all descendant elements until overridden by a lower level element with a Mode attribute. Thus it is early to indicate that all of the elements in an ECML structure are present as queries or assertions. Query elements may have data content. Such content should be interpreted as a default value to be returned if no better value is known. There is no way with Version 2.0 of ECML to indicate what query fields the party considers mandatory. From the point of view of software, all fields queried are optional to complete. However, a party 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 parties by which one can indicate what fields it wants the other to provide. Probably the easiest method for currently deployed mass software is as fields in an [HTML] form. Other possibilities are to use an [XML] exchange, the IOTP Authenticate transaction [RFC 2801], or proprietary protocols. D. Eastlake 3rd [Page 18] INTERNET-DRAFT ECML v2 Specification June 2004 So that browser software can tell what version it is dealing with, it is REQUIRED that the Ecom_SchemaVersion field be included in every transactions when ECML is being used on the web. Ecom_SchemaVersion SHOULD appear on every web page that has any Ecom fields. It is usually a hidden field. User action or the appearance of the Ecom_SchemaVersion field are examples of triggers that can be used to initiate a facility capable of providing information in response to an ECML based query or utilizing information from ECML assertions. Because some web software may require user activation, it is RECOMMENDED that these be at least one user visible Ecom field on every web page with any Ecom fields present when ECML is used via the web. Because, under some circumstances, communications can proceed very slowly, it may not be clear to an automated processing function when it is finished receiving ECML fields on a web page or the like. For this reason, it is RECOMMENDED that the Ecom_SchemaVersion field be the last Ecom field on a web page. Transfer or 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 provide personal data beyond with end of the transaction with a particular business. 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-interaction automated logic can know when to stop if it chooses to check for this field. 4. Security and Privacy Considerations The information called for by many of these fields is sensitive. It should be protected from unauthorized modification and kept confidential if stored in a location or transmitted over a channel where it might otherwise be observed. In addition, the authenticity of the information will be a concern in many systems. Mechanisms for such protection and authentication are not specified herein but might, depending on circumstances, include object security protocols, such as XMLDSIG [RFC 3275], XML encryption [XMLENC], or CMS [RFC 3369], or channel security such as TLS [RFC 2246] or IPSec [RFC 2411]. Systems in which an ECML field or fields are stored and later forwarded will likely find object security to be the most appropriate. When information is being requested from a user, their control over D. Eastlake 3rd [Page 19] INTERNET-DRAFT ECML v2 Specification June 2004 release of such information is needed to protect their privacy. Software that is installed on a shared or public terminal should be configurable such that memory of any sensitive or individual identity 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 sensitive or individual identification information is stored, the operator or user should have an option to protect the information, for example with a password without which the information will be unavailable, even to someone who has access to the file(s) in which it is being stored. Any multi-page/screen 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. It should be remembered that default, hidden, and other values transferred to another party may be maliciously modified before being returned. 5. IANA Considerations The sections below provide for a version URN for ECML Versions, provide for the registration of particular versions and register Version 2.0, and provide for three additional IANA regitries for elements appearing in three ECML v2 fields. 5.1 ECML v2 URN Template As specified by the template below from [RFC 3553], urn:ietf:params:ecml is permanently registered with sub registration via RFC publication. Registry name: urn:ietf:params:ecml Specification: RFC XXXX - (draft-ietf-trade-ecml2-spec-*.txt) Repository: RFC XXXX - (draft-ietf-trade-ecml2-spec-*.txt) Index value: Values subordinate to urn:ietf:params:ecml are registered by RFC publication. As provided in [RFC 3553], once such a value is registered, it may never change. D. Eastlake 3rd [Page 20] INTERNET-DRAFT ECML v2 Specification June 2004 5.1.1 Subregistration of v2.0 The subordinate value "v2.0" is hereby permanently registered so that the URN urn:ietf:params:ecml:v2.0 is used to indicate an ECML field or fields that conform to this specification. Additional subregistration shall be via IESG approval. 5.2 IANA Registries There are three fields describes in Section 2.1.2 that require the establishment of IANA registries as described below: Ecom_Payment_Card_Type A registry of case insensitive alphanumeric ASCII [ASCII] card type designations from one to four characters in length with no leading or trailing white space. See Section 2.1.2, note 11, for the initial 12 designations. Designations are added based on expert approval. Applicants for registration will normally be required to already have an ISO Issuer Identification Number (IIN) or range of IINs. Ecom_Payment_Card_Protocol This fields holds a space separated list of protocols designated by case insensitive alphanumeric ASCII [ASCII] tokens from this registry or the token "none". See Section 2.1.2, note 17, for the initial seven registered tokens (including "none") and further information. Tokens are added to the registry based on expert approval. Ecom_Transaction_Type A case insensitive alphabetic ASCII [ASCII] value indicating the type of transaction. See Section 2.1.2, note 30, for the initial two registered values. Values are added based on expert approval. D. Eastlake 3rd [Page 21] INTERNET-DRAFT ECML v2 Specification June 2004 Normative References [ASCII] - USA Standard Code for Information Interchange, X3.4 American National Standards Institute; New York, 1968. [E.164] - ITU-T Recommendation E.164/I.331 (05/97): The International Public Telecommunication Numbering Plan. 1997. [IANA] - Internet Assigned Numbers Authority, Official Names for Character Sets, ed. Keld Simonsen et al. notes/iana/assignments/character-sets>. [ISO 3166] - "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes", ISO 3166-1, 1997. [ISO 4217] - "Codes for the representation of currencies and funds", ISO 4217, 2001. [ISO 5218] - "Information interchange -- Representation of human sexes", ISO 5218, 1977. [ISO 7812] - "Identification card - Identification of issuers - Part 1: Numbering system", ISO 7812-1, 2000. [ISO 8583] - "Financial transaction card originated messages - Interchange message specifications - Part 1: Messages, elements and code values", ISO 8583-1, 2001. [RFC 1766] - "Tags for the Identification of Languages", H. Alvestrand, March 1995. [RFC 2045] - "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", N. Freed, N. Borenstein, November 1996. [RFC 2396] - "Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. [RFC 3066] - "Tags for the Identification of Languages", H. Alvestrand, January 2001. [XML] - Extensible Markup Language (XML) 1.0 (Second Edition), , T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler D. Eastlake 3rd [Page 22] INTERNET-DRAFT ECML v2 Specification June 2004 Informative References [eCheck] - [EMV] - [HTML] - "HTML 3.2 Reference Specification", < http://www.w3.org/TR/REC-html32.html>, D. Raggett, January 1997. [P3P BASE] - "The Platform for Privacy Preferences 1.0 (P3P1.0) Specification", L. Cranor, M. Langheinrich, M. Marchiori, M. Presler-Marshall, J. Reagle, December 2000, . [P3P ECOM] - "Using P3P for E-Commerce", J. Coco, S. Klien, D. Schutzer, S. Yen, A. Slater, November 1999, . [RFC 1034] - "Domain names - concepts and facilities", P.V. Mockapetris, Nov-01-1987. [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. [RFC 2801] - "Internet Open Trading Protocol - IOTP Version 1.0", D. Burdett, April 2000. [RFC 3106] - "ECML v1.1: Field Specifications for E-Commerce", D. Eastlake, T. Goldstein, April 2001. [RFC 3275] - "(Extensible Markup Language) XML-Signature Syntax and Processing", D. Eastlake 3rd, J. Reagle, D. Solo, March 2002. [RFC 3369] - "Cryptographic Message Syntax (CMS)", R. Housley, August 2002. [RFC 3553] - "An IETF URN Sub-namespace for Registered Protocol Parameters", M. Mealling, L. Masinter, T. Hardie, G. Klyne, June 2003. [SET] - Secure Electronic Transaction, D. Eastlake 3rd [Page 23] INTERNET-DRAFT ECML v2 Specification June 2004 [XMLENC] - "XML Encryption Syntax and Processing", D. Eastlake 3rd, J. Reagle, http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/, December 2002. D. Eastlake 3rd [Page 24] INTERNET-DRAFT ECML v2 Specification June 2004 Appendix: Changes from v1.1 to v2 Substantial rewording of text to change the emphasis from an HTML Form Field naming to XML Syntax. Addition of the merchant -> processor fields. Addition of the Ecom_Wallet_Location and Ecom_User_Certificate_URL fields. Addition of the "Mode" attribute. Addition of the ECom_Payment_Card_IssueNumber, Loyalty Card fields, Device ID, Valid From, and User Data fields. Some minor fixes related to telephone numbers. Addition of IANA Considerations section. D. Eastlake 3rd [Page 25] INTERNET-DRAFT ECML v2 Specification June 2004 Intellectual Property Rights and Disclaimer By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Author's Address Donald E. Eastlake 3rd Motorola Laboratories 155 Beaver Street Milford, MA 01757 USA Phone: 1-508-786-7554 (work) 1-508-634-2066 (home) EMail: Donald.Eastlake@motorola.com D. Eastlake 3rd [Page 26] INTERNET-DRAFT ECML v2 Specification June 2004 File name and Expiration This file is draft-ietf-trade-ecml2-spec-10.txt. It expires December 2004. D. Eastlake 3rd [Page 27]