|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
All of the documents are approved OMA specifications
|
|
3.
|
Justification for the specific reference:
|
|
|
This OMA standard is referenced in ITU-T Y.oneM2M.DM.OMA
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
There are IPR claims concerning presence in the OMA IPR data base
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The documents are all approved OMA specifications that are undergoing continuing development
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[3GPP23.003] “Numbering, addressing and identification”, 3GPP,/
URL: http://www.3gpp.org/
[3GPP31.102] “Characteristics of the Universal Subscriber Identity Module (USIM) application”, 3GPP,/
URL: http://www.3gpp.org/
[C.S0023-B_v1.0] “Removable User Identity Module For Spread Spectrum Systems”, 3GPP2 C.S0023-B version 1.0,/
URL: http://www.3gpp2.org/Public_html/specs/C.S0023-B_v1.0_040426.pdf/
[DM-AD] “Device Management Architecture”, Open Mobile Alliance™, OMA-AD-DM-V2_0,/
URL: http://www.openmobilealliance.org//
[GCM] “Google Cloud Messaging for Android”, Google,/
URL: http://developer.android.com/google/gcm/index.html/
[GPSCP03] “GlobalPlatform Secure Channel Protocol 03 (SCP 03) Amendment D v1.1 Sept 2009”,/
URL: http://www.globalplatform.org/specificationscard.asp/
[ISO29115] Information technology- Security Techniques – Entity authentication assurance framework (2013-04-01),/
URL: http://www.iso.org/
[ISO639-2] “Codes for the representation of names of languages-- Part 2: alpha-3 code”/
URL: http://www.loc.gov/standards/iso639-2//
[JSON-SCHEMA] “JSON Schema: core definitions and terminology, draft-zyp-json-schema-04”, K. Zyp, Ed, January 31, 2013./
URL: http://tools.ietf.org/html/draft-zyp-json-schema-04/
[PKCS#15] PKCS #15 v1.1: Cryptographic Token Information Syntax Standard”, RSA Laboratories, June 6, 2000./
URL: ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-15/pkcs-15v1_1.pdf/
[POSIX] ISO/IEC/IEEE 9945-2009 Information Technology — Portable Operating System Interface (POSIX®) Base Specifications, Issue 7./
[PUSHOTA] “Push Over The Air”, Open Mobile Alliance, OMA_TS-PushOTA-V2_3,/
URL: http://www.openmobilealliance.org/
[REST] “Architectural Styles and the Design of Network-based Software Architectures”, Roy Thomas Fielding, 2000/
URL: http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm/
[RFC1521] “MIME (Multipurpose Internet Mail Extensions) Part One”, Borenstein & Freed, Sep 1993/
URL: http://www.ietf.org/rfc/rfc1521.txt/
[RFC1766] “Tags for the Identification of Languages”. H. Alvestrand. March 1995./
URL: http://www.ietf.org/rfc/rfc1766.txt/
[RFC2119] “Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner, March 1997, URL: http://www.ietf.org/rfc/rfc2119.txt/
[RFC2616] “Hypertext Transfer Protocol -- HTTP/1.1”, R, Fielding, June 1999, URL: http://www.ietf.org/rfc/rfc2616.txt/
[RFC2617] “HTTP Authentication: Basic and Digest Access Authentication”, J. Franks, et al., June 1999, URL:http://www.ietf.org/rfc/rfc2617.txt/
[RFC2817] “Upgrading to TLS Within HTTP/1.1”, R. Khare and S. Lawrence, May 2000, URL:http://www.ietf.org/rfc/rfc2817.txt/
[RFC2818] “HTTP over TLS”, E. Rescorla, May 2000, URL:http://www.ietf.org/rfc/rfc2818.txt/
[RFC3629] “UTF-8, a transformation format of ISO 10646”, F. Yergeau, November 2003, URL: http://tools.ietf.org/html/rfc3629/
[RFC3986] “Uniform Resource Identifier (URI): Generic Syntax”, Berners-Lee, et al. Jan 2005, URL: http://www.ietf.org/rfc/rfc3986.txt/
[RFC4122] “A Universally Unique Identifier (UUID) URN Namespace”, P. Leach, et al. July 2005,/
URL: http://www.ietf.org/rfc/rfc4122.txt/
[RFC4234] “Augmented BNF for Syntax Specifications: ABNF”. D. Crocker, Ed., P. Overell. October 2005,/
URL: http://www.ietf.org/rfc/rfc4234.txt/
[RFC4279] “Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)”, P. Eronen, H. Tschofenig, December 2005, URL:http://www.ietf.org/rfc/rfc4279/
[RFC4346] “The Transport Layer Security (TLS) Protocol Version 1.1”, T. Dierks and E. Rescorla, April 2006,/
URL:http://www.ietf.org/rfc/rfc4346.txt/
[RFC4627] “The application/json Media Type for JavaScript Object Notation (JSON)”, D. Crockford. July 2006,/
URL: http://www.ietf.org/rfc/rfc4627.txt/
[RFC5198] “Unicode Format for Network Interchange”, J. Klensin, M. Padlipsky, March 2003,/
URL: http://www.ietf.org/rfc/rfc5198.txt/
[RFC5246] “The Transport Layer Security (TLS) Protocol Version 1.2”, T. Dierks and E. Rescorla, August 2008,/
URL:http://www.ietf.org/rfc/rfc5246.txt/
[RFC5280] “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile”,/
D. Cooper, S. Santesson, S. Farrell, May 2008,/
URL:http://www.ietf.org/rfc/rfc5280.txt/
[RFC5289] “TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM), E./
Rescorla, August 2008/
URL:http://www.ietf.org/rfc/rfc5289.txt/
[RFC6125] “Representation and Verification of Domain-Based Application Service Identity within Internet Public/
Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)”, P./
Saint-Andre, J. Hodges, March 2011,/
URL:http://www.ietf.org/rfc/rfc6125.txt/
[RFC6234] “US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) ”, D. Eastlake 3rd, etc. May 2011 URL: http://www.ietf.org/rfc/rfc6234.txt/
[SCRRULES] “SCR Rules and Procedures”, Open Mobile Alliance™, OMA-ORG-SCR_Rules_and_Procedures,/
URL: http://www.openmobilealliance.org//
[TS102.221] “Smart Cards; UICC-Terminal interface; Physical and logical characteristics”, (ETSI TS 102 221 release 6),/
URL: http://www.etsi.org//
[TS151.011] “Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface”, (ETSI TS 151 011),/
URL: http://www.etsi.org//
[TS33.220] “Generic Bootstrapping Architecture (GBA) ”, URL: http://www.3gpp.org/
[TS33.223] “Generic Bootstrapping Architecture (GBA) Push function”, URL: http://www.3gpp.org
|
|
9.
|
Qualification of
OMA:
|
|
|
Qualification of OMA: OMA is recognized under the provisions of ITU-T Recommendation A.5. Qualifying information is on file in TSB.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
