Enabler Test Report
Email Notification v1.0
OMA TestFest (July 2006)
Version 7-Jul-2006
Open Mobile Alliance
OMA-Enabler_Test_Report-EMN-10-2006-07-07
This document is considered confidential and may not be disclosed in any manner to any non-member of the
Open Mobile Alliance™, unless there has been prior explicit Board approval.
This document is a work in process and is not an approved Open Mobile Alliance™ specification. This document is
subject to revision or removal without notice. No part of this document may be used to claim conformance or
interoperability with the Open Mobile Alliance specifications.
© 2006 Open Mobile Alliance Ltd. All Rights Reserved. Terms and conditions of use are available from the Open
Mobile Alliance™ Web site (http://www.openmobilealliance.org/copyright.html)
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 2 (19)
© 2006 Open Mobile Alliance Ltd. All rights reserved.
Terms and conditions of use are available from the Open Mobile Alliance™ Web site at
http://www.openmobilealliance.org/copyright.html.
You may use this document or any part of the document for internal or educational purposes only, provided you do not
modify, edit or take out of context the information in this document in any manner. You may not use this document in any
other manner without the prior written permission of the Open Mobile Alliance™. The Open Mobile Alliance authorises
you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original
materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not
constitute an endorsement of the products or services offered by you.
The Open Mobile Alliance™ assumes no responsibility for errors or omissions in this document. In no event shall the Open
Mobile Alliance be liable for any special, indirect or consequential damages or any damages whatsoever arising out of or in
connection with the use of this information.
This document is not an Open Mobile Alliance™ specification, is not endorsed by the Open Mobile Alliance and is
informative only. This document is subject to revision or removal without notice. No part of this document may be used to
claim conformance or interoperability with the Open Mobile Alliance specifications.
Open Mobile Alliance™ members have agreed to use reasonable endeavors to disclose in a timely manner to the Open
Mobile Alliance the existence of all intellectual property rights (IPR's) essential to the present document. However, the
members do not have an obligation to conduct IPR searches. The information received by the members is publicly
available to members and non-members of the Open Mobile Alliance and may be found on the “OMA IPR Declarations”
list at http://www.openmobilealliance.org/ipr.html. Essential IPR is available for license on the basis set out in the schedule
to the Open Mobile Alliance Application Form.
No representations or warranties (whether express or implied) are made by the Open Mobile Alliance™ or any Open
Mobile Alliance member or its affiliates regarding any of the IPR’s represented on this “OMA IPR Declarations” list,
including, but not limited to the accuracy, completeness, validity or relevance of the information or whether or not such
rights are essential or non-essential.
This document is available online in PDF format at http://www.openmobilealliance.org/.
Known problems associated with this document are published at http://www.openmobilealliance.org/.
Comments regarding this document can be submitted to the Open Mobile Alliance™ in the manner published at
http://www.openmobilealliance.org/documents.html
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 3 (19)
Contents
1.
SCOPE .......................................................................................................................................................................4
2.
REFERENCES..........................................................................................................................................................5
2.1
NORMATIVE REFERENCES .................................................................................................................................5
2.2
INFORMATIVE REFERENCES ..............................................................................................................................5
3. TERMINOLOGY AND CONVENTIONS .............................................................................................................7
3.1
CONVENTIONS ....................................................................................................................................................7
3.2
ABBREVIATIONS .................................................................................................................................................7
4. SUMMARY ...............................................................................................................................................................8
5.
TEST DETAILS........................................................................................................................................................9
5.1
DOCUMENTATION ...............................................................................................................................................9
5.2
TEST CASE STATISTICS ....................................................................................................................................10
5.2.1
Test Case Summary...................................................................................................................................10
5.2.2
Test Case List............................................................................................................................................11
5.3
PROBLEM REPORTS..........................................................................................................................................17
6. CONFIRMATION ..................................................................................................................................................18
APPENDIX A.
CHANGE HISTORY (INFORMATIVE) .....................................................................................19
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 4 (19)
1. Scope
This report describes the results from the testing carried out at OMA TestFest-15 (June 2006) concerning Email
Notification v1.0 Enabler.
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 5 (19)
2. References
2.1
Normative References
[EMN]
Email Notification Version 1.0 OMA-Push-EMN-v1.0_20040614-C
[ETS]
OMA-ETS-EMN-V1_0-20050713A URL: http://www.openmobilealliance.org/
[IOPProc]
“OMA Interoperability Policy and Process”. Open Mobile Alliance™. OMA-IOP-Process-v1_0.
URL: http://www.openmobilealliance.org
[ISO10646]
“Information Technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1:
Architecture and Basic Multilingual Plane”, ISO/IEC 10646-1:2000.
[OMNA]
“OMA Naming Authority”, OMA™,
URL: http://www.openmobilealliance.org/tech/omna/index.htm
[RFC2119]
“Key words for use in RFCs to Indicate Requirement Levels”. S. Bradner. March 1997.
URL: http://www.ietf.org/rfc/rfc2119.txt
[RFC2234]
“Augmented BNF for Syntax Specifications: ABNF”. D. Crocker, Ed., P. Overell.
November 1997. URL: http://www.ietf.org/rfc/rfc2234.txt
[RFC2396]
“Uniform Resource Identifiers (URI): Generic Syntax”. T. Berners-Lee et al. August 1998
URL: http://www.ietf.org/rfc/rfc2396.txt
[RFC3023]
“XML Media Types”, M. Murata et al., January 2001. URL: http://www.ietf.org/rfc/rfc3023.txt
[UNICODE]
“The Unicode Standard: Version 2.0”, The Unicode Consortium, Addison-Wesley Developers
Press, 1996. URL: http://www.unicode.org/
[WBXML]
“Binary XML Content Format Format”, WAP Forum, WAP-192-WBXML-20010725-a, 25-Jul2001, URL: http://www.wapforum.org/
[XML]
“Extensible Markup Language (XML)”, W3C Recommendation 10-February-1998, REC-xml19980210”, T. Bray, et al, February 10, 1998, http://www.w3.org/TR/REC-xml
2.2
Informative References
[ISO8601]
“Data elements and interchange formats - Information interchange - Representation of dates and
times”, International Organization For Standardization (ISO), 15-June-1988
“Data elements and interchange formats - Information interchange - Representation of dates and
times, Technical Corrigendum 1”, International Organization For Standardization (ISO) Technical Committee ISO/TC 154, 01-May-1991
[PUSH]
“WAP Push Architectural Overview”. WAP Forum™.
WAP-250-PushArchOverview-20010703-a. URL: http//www.wapforum.org/
[PUSHMSG]
“Push Message”. WAP Forum™.
WAP-251-PushMessage-20010322-a. URL: http://www.wapforum.org/
[PushOTA]
“Push OTA Protocol”. WAP Forum™.
WAP-235-PushOTA-20010425-a. URL: http//www.wapforum.org/
[PushPAP]
“Push Access Protocol”. WAP Forum™.
WAP-247-PAP-20010429-a. URL: http://www.wapforum.org/
[RFC2192]
“IMAP URL Scheme”. C. Newman. September 1997. URL: http://www.ietf.org/rfc/rfc2192.txt
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 6 (19)
[RFC2384]
“POP URL Scheme”. R. Gellens. August 1998. URL: http://www.ietf.org/rfc/rfc2384.txt
[RFC2822]
“Internet Message Format“. P. Pesnick, Ed. April 2001.
URL: http://www.ietf.org/rfc/rfc2822.txt
[WAP]
“WAP Architecture”. WAP Forum™. WAP-210-WAPArch-20010712, URL:
http://www.wapforum.org/
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 7 (19)
3. Terminology and Conventions
3.1
Conventions
This is an informative document, i.e. the document does not intend to contain normative statements.
3.2
Abbreviations
DTD
Document Type Definition
EMN
E-Mail Notification
EMN UA
EMN User Agent
HTTP
Hypertext Transfer Protocol
IANA
Internet Assigned Numbers Authority
IMAP
Internet Message Access Protocol
IMAPS
Secure Internet Message Access Protocol
IOProc
Interoperability Procedure
MIME
Multipurpose Internet Mail Extensions
OMNA
Open Mobile Alliance Naming Authority
OTA
Over The Air
PAP
Push Access Protocol
PI
Push Initiator
POP
Post Office Protocol
POPS
Secure Post Office Protocol
PPG
Push Proxy Gateway
RFC
Request For Comments
SGML
Standard Generalized Markup Language
SMTP
Simple Mail Transfer Protocol
SSMTP
Secure Simple Mail Transfer Protocol
URI
Uniform Resource Identifier
URL
Uniform Resource Locator
UTC
Universal Time Co-ordinated
WAP
Wireless Application Protocol
WBXML
WAP Binary XML
XML
Extensible Mark-up Language
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 8 (19)
4. Summary
This report gives details of the testing carried out during the OMA TestFest-15 (June 2006) for Email Notification
(EMN) v1.0 Enabler
The report is compiled on behalf of OMA by the OMA Trusted Zone.
The work and reporting has followed the OMA IOP processes and policies [OMAIOPPROC].
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 9 (19)
5. Test Details
5.1
Documentation
This chapter lists the details of the enabler and any documentation, tools or test suites used to prove the enabler.
Date:
25th to 30th June 2006
Location:
Belfast, Northern Ireland, UK
Enabler:
Email Notification v1.0 Enabler
Process:
OMA Interoperability Policy and Process [OMAIOPPROC]
Type of Testing
Interoperability Testing
Products tested:
Client-to-server, Client-to-Client
Test Plan:
-
Test Specification:
EMN Enabler Test Specification - OMA-ETS-EMN-V1_0-20050713-C
Test Tool:
None
Test Code:
None
Type of Test event:
TestFest
Participants:
Nokia, Ericsson, Sony Ericsson, Openwave, Obigo
Number of Client
Products:
3
Participating Technology
Providers for clients:
Nokia, Sony Ericsson, Obigo
Number of Server
Products:
2
Participating Technology
Providers for servers:
Ericsson, Openwave
Number of test sessions
completed:
4
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
5.2
5.2.1
Page 10 (19)
Test Case Statistics
Test Case Summary
This chapter gives an overview of the result for all test cases included in [ETS].
The following status is used in the tables below:
•
Total number of TCs: Used in the summary to indicate how many test cases there are in total.
•
Number of passed: Used in the summary to indicate how many of the total test cases successfully passed.
•
Number of failed: Used in the summary to indicate how many of the total test cases failed.
•
Number of N/A: Used in the summary to indicate how many of the total test cases have not been run due to
one of the implementations not supporting the functionality required to run this test case.
•
Number of OT: Used in the summary to indicate how many of the total test cases have not been run due to no
time to run the test case.
•
Number of INC: Used in the summary to indicate how many of the total test cases have not been run due to
functionality not being tested due to an error in the implementation or other functionality that is required to run
this test case.
Test Section:
Client to Server TCs
Total
Number
of test
sessions:
4
Total
number
of TCs:
4
Open Mobile Alliance™ Confidential
Number
of
Failed:
2
Number
of N/A:
Number
of OT:
Number
of INC:
49
Number
of
Passed:
68
Total:
126
0
0
196
49
68
2
126
0
0
196
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
5.2.2
Page 11 (19)
Test Case List
This chapter lists the statistics for all test cases included in [ETS].
The following status is used in the tables below:
•
No. of runs(R): Used to indicate how many times the test cases have been run in total.
•
No. of passed(P): Used to indicate how many times the test case has been run with successful result.
•
No. of failed(F): Used to indicate how many times the test case has been run with failed result
•
No. of OT(O): Used to indicate how many times the test case has not been run due to no time available.
•
No. of INC(I): Used to indicate how many times the test case has not been run due to errors being found in
other functionality required for running this test case.
•
PR: Used to indicate if any PRs (Problem Reports) have been issued during testing.
•
Note: Used to indicate the cause of Inconclusive or Fail verdicts.
Tests for Push-to-talk Over Cellular TestFest from OMA-ETS-EMN-V1_0-20050713-A
Notes
Test Counts
Test Case
Description
EMN-1.0-int-1
Run
Pass
Fail
OT
INC
Verify that the client can support UTF –
8 encoding.
4
4
0
0
0
EMN-1.0-int-2
Verify that the client can support UTF –
16 encoding.
4
0
0
0
0
EMN-1.0-int-3
Verify that the client can parse the XML
schema and process it properly by the
device.
4
4
0
0
0
EMN-1.0-int-4
Verify that the Client Required to test
the Mailat URI which specifies the email
address this will comply with [RFC2822]
4
4
0
0
0
EMN-1.0-int-5
Verify that the Client handles
Timestamp attribute –DateTime
encoded in OPAQUE data format
4
3
0
0
0
EMN-1.0-int-6
Verify that the Client handles a valid
EMN Document Type Definition (DTD)
data format.
4
4
0
0
0
EMN-1.0-int-7
Verify that the Client handles a non
valid EMN Document Type Definition
(DTD) data format.
4
4
0
0
0
EMN-1.0-int-8
Verify that the Client handles a valid
EMN in Textual format.
4
2
0
0
0
Open Mobile Alliance™ Confidential
PR
(see
below)
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 12 (19)
Notes
Test Counts
Test Case
Description
Run
Pass
Fail
OT
INC
EMN-1.0-int-9
Verify that the Client handles a valid
EMN in Tokenised format using a
compact binary representation.
4
2
0
0
0
EMN-1.0-int-10
Verify the Push application Accept ID
announced in the User Agent Profile or
the accept headers in absolute URI
format
4
3
0
0
0
EMN-1.0-int-11
Verify the Push application Accept ID
announced in the User Agent Profile or
the accept headers in the Hex format as
assigned by [OMNA] The hexadecimal
code is (0x09)
4
4
0
0
0
EMN-1.0-int-12
Verify that different character coding as
set in the Content_Type field will be
supported by the device ie: UTF8
UTF16 and US-ASCII.
4
1
0
0
0
EMN-1.0-int-13
Verify that the Client can connect using
the Mailbox URI with the Email server
address. and compliant to [RFC 2396]
4
2
0
0
0
EMN-1.0-int-14
Verify that the Client can support POP2
protocol and uses the Mailat URI which
specifies the email address details. This
will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-15
Verify that the Client can support
POP2S protocol and uses the Mailat
URI which specifies the email address
details. This will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-16
Verify that the Client can support POP3
protocol and uses the Mailat URI which
specifies the email address details. This
will comply with [RFC2822]
4
1
1
0
0
EMN-1.0-int-17
Verify that the Client can support
POP3S protocol and uses the Mailat
URI which specifies the email address
details. This will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-18
Verify that the Client can support IMAP2
protocol and uses the Mailat URI which
specifies the email address details. This
will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-19
Verify that the Client can support
IMAP2S protocol and uses the Mailat
URI which specifies the email address
details. This will comply with [RFC2822]
4
0
0
0
0
Open Mobile Alliance™ Confidential
PR
(see
below)
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 13 (19)
Notes
Test Counts
Test Case
Description
Run
Pass
Fail
OT
INC
EMN-1.0-int-20
Verify that the Client can support IMAP4
protocol and uses the Mailat URI which
specifies the email address details. This
will comply with [RFC2822]
4
1
1
0
0
EMN-1.0-int-21
Verify that the Client can support
IMAP4S protocol and uses the Mailat
URI which specifies the email address
details. This will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-22
Verify that the Client can support HTTP
protocol and uses the Mailat URI which
specifies the email address details. This
will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-23
Verify that the Client can support
HTTPS protocol and uses the Mailat
URI which specifies the email address
details. This will comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-24
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-25
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-26
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-27
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-28
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-29
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-30
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
Open Mobile Alliance™ Confidential
PR
(see
below)
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 14 (19)
Notes
Test Counts
Test Case
Description
Run
Pass
Fail
OT
INC
EMN-1.0-int-31
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-32
Verify that the Client Required to test
the Mailbox URI which specifies the
email address and protocol this will
comply with [RFC2822]
4
0
0
0
0
EMN-1.0-int-33
Verify that the Client Required to test
the Mailbox URI which specifies the
email address this will comply with
[RFC2822]
4
0
0
0
0
EMN-1.0-int-34
Verify that the Client rejects an EMN
that specifies a mailing protocol that the
device does not support.
4
1
0
0
0
EMN-1.0-int-35
Verify that the Client can support Out of
Order notifications. So avoiding the
Race condition
4
1
0
0
0
EMN-1.0-int-36
Verify that the Client can support the
Time stamp of the notifications in coordinated Universal Time Format
(UTC). This avoids the use of different
time zones.
4
2
0
0
0
EMN-1.0-int-37
Verify that the Client can support other
character encoding sets as required by
XML but all should be transformed into
Universal character set.
4
0
0
0
0
EMN-1.0-int-38
Verify that the Client can support some
form of security to prevent against
attack. Thus preventing the device from
attaching to a fraudulent mailbox.
Therefore a security Policy should be
implemented
4
3
0
0
0
EMN-1.0-int-39
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully.
4
2
0
0
0
EMN-1.0-int-40
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully.
4
2
0
0
0
Open Mobile Alliance™ Confidential
PR
(see
below)
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 15 (19)
Notes
Test Counts
Test Case
Description
Run
Pass
Fail
OT
INC
EMN-1.0-int-41
Verify the Email Server can send the
proper Push application Accept ID
announced in the User Agent Profile or
the accept headers in absolute URI
format
4
2
0
0
0
EMN-1.0-int-42
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully.
4
2
0
0
0
EMN-1.0-int-43
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully. The
format of the EMN content is encoded
into a compact
4
2
0
0
0
EMN-1.0-int-44
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully in a
textual format.
4
2
0
0
0
EMN-1.0-int-45
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully in a
tokenised format.
4
2
0
0
0
EMN-1.0-int-46
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully. The
format of the tokenized elements has to
comply with
4
2
0
0
0
EMN-1.0-int-47
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully.
4
2
0
0
0
Open Mobile Alliance™ Confidential
PR
(see
below)
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 16 (19)
Notes
Test Counts
Test Case
Description
Run
Pass
Fail
OT
INC
EMN-1.0-int-48
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully. A
security Policy can be applied if
possible
4
2
0
0
0
EMN-1.0-int-49
Verify that the Email Server can
connect to the Wap Push Proxy
Gateway (PPG). Once a connection is
established then an EMN can be sent
via the Push Access Protocol (Push
PAP) to the PPG successfully.
4
2
0
0
0
Open Mobile Alliance™ Confidential
PR
(see
below)
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
5.3
Page 17 (19)
Problem Reports
During the activities for TestFest-15, the following problem reports were generated relating to the test materials and test
process:
None during the TestFest
PR
Number
Affecting
Description
Test Case reference /
Specification
reference
Full details of the Problem Reports can be found at:
http://www.openmobilealliance.org/OMA-Problem-Reporting-System.html
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 18 (19)
6. Confirmation
This signature states that the included information is true and valid.
____________________
OMA Trusted Zone
Open Mobile Alliance™ Confidential
© 2006 Open Mobile Alliance Ltd.
All rights reserved
OMA-Enabler_Test_Report-EMN-10-2006-07-07
Page 19 (19)
Appendix A. Change History
Type of Change
Initial Release
Date
7th July 2006
Open Mobile Alliance™ Confidential
Section
All
(Informative)
Description
Initial Report from TestFest-15
© 2006 Open Mobile Alliance Ltd.
All rights reserved