App-ID Ad-Hoc Technical Issues TP AppID-2014-0003R02 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv, dhemphill@iconectiv.com Meeting Date: 2015-01-23

Contents What is App-ID? Registry challenges App-ID Ad Hoc Group charge Requirements for potential App-ID Registration Authorities Recommendation for determining the App-ID Registration Authorities Recommendation for the timeline of the selection of the Registration Authorities Open Issues

What is App-ID App-ID is short for Application ID Nicolas Damour introduced ARC-2015-1716 to clarify the intended meaning and use of App‑ID in TS‑0001 - Thanks App-ID identifies a software application (by version) running in the Application Layer Application Layer Common Services Network Service

Uses of App-ID The Common Service Layer knows the application by its AE-ID and App-ID App-ID is used by security App-ID will likely be required for certification Application Layer Common Services Network Service

Registry Challenges Required fields Generating App-ID Software version e.g., version 3.2 Company requesting App-ID e.g., CustomSoft Inc. Company creating App-ID is only party allowed to version the App-ID i.e., 3.2, 3.3 etc. Maintain Company/Group buyouts, mergers, acquisitions Associating users to companies to control authorization Generating App-ID Ensuring App-IDs are not duplicated Required fields are provided

App-ID Ad-Hoc Group Charge Provide recommendations to the TP for: Requirements to be met by the App-ID Registration Authorities Recommendation for determining the App-ID Registration Authorities Recommendation for the timeline of the selection of the Registration Authorities

1. Requirements for App-ID Registry The Registration Authorities shall comply with the following: oneM2M Registrars shall ensure global uniqueness of registered IDs. The company requesting an App-ID will have a Company ID. Company incorporation documentation will be required when requesting a new Company ID The Company ID shall be associated with the App-ID The Registration Authority shall maintain a Service Level of 99% uptime. Scheduled downtime of more than 4 hours should be communicated to the oneM2M Steering Committee. Registrars must maintain activity log files and provide to oneM2M Steering Committee upon request. Required attributes shall be collected in support of ID generation. All registry information shall be in the English language.

2. Requirements for App-ID Registration Authorities Training to support the use of the registry content and access shall be made available. Registration Authorities may use company branding for the registry as long as the oneM2M logo also appears – per MARCOM approval Reasonable and customary charges will be allowed for pay services. User information will be passed over HTTPS connections. Registry information will be secured behind a firewall. Note: The oneM2M standard allows companies to create a private App-ID Registry for their internal use. The above requirements do not apply to private App-ID Registries.

2. Determining the App-ID Registration Authorities oneM2M member or partner in good standing history of providing and managing a global registry in coordination with an international standards body and in compliance with international standards high-level schedule to meet the oneM2M timelines description of customer support and training in support of the oneM2M Registry

2. Determining the App-ID Registration Authorities Legal Challenge oneM2M is not a legal entity that can contract for the services of a Registration Authority Most likely a SDO will be asked to contract with the Registration Authorities oneM2M will need to agree to the vendor selection requirements of the SDO e.g., open RFP and timeline

3. Recommended Timeline Date Activity 2/15/2015 App-ID Ad-hoc group present recommendation to Technical Plenary before TP#17 3/23/2015 Technical Plenary review, approve and present recommendations to Steering Committee 3/15/2015 Steering Committee review and acceptance of recommendation 5/1/2015 Steering Committee selection of Registration Authorities 7/31/2015 Registry available for beta testing 12/31/2015 oneM2M registries generally available

Summary This is an introduction to the Registry issues An initial draft of recommendations is contained in contribution TP AppID-2014-0002 It is understood that additional concepts and issues may arise as the result of this overview

Open Issues

Partitioned Registry Registrar B B-123 Registrar A A-123 Registrar C Pros Steering Committee assigns namespaces to Registrars Registrars are independent - no common infrastructure Cons Synchronization1 between Registrars required to provide view of all App-IDs Namespace included in App-ID name e.g., A-123, B-123, C-123, registrar lock-in All registrars must implement solution correctly or the registry will suffer Company changes registrar will change name space of future App-IDs 1 Possibly model database synchronization off of Whitespace database–to–database synchronization specification http://transition.fcc.gov/bureaus/oet/whitespace/guides/TVWS_Database_Synchronization_InteropSpec_V1.1.1%204-17-12.pdf

Central/Root Registry Registrar A ABC-123 Registrar B ABC-124 Registrar C ABC-125 Pros DB Layer and some processing is common Single naming space No synchronization Common reference data e.g., Company Code API is RDBMS or API Scales with # of Registrars Cons Someone needs to build and maintain the DB and API as a shared resource API source ownership Firewall Common Infrastructure API Central/Root Registry

Background Slides

ARC-2015-1716 CR Nicolas Damour introduced ARC-2015-1716 to clarify the intended meaning and use of App‑ID in TS‑0001 - Thanks 7.1.3 Application Identifier (App-ID) An Application Identifier (App-ID) uniquely identifies an M2M Application in a given context. More precisely, there are two types of App-ID: registration authority defined App-ID (registered App-ID) and non-registered App-ID. The establishment of the registered App-ID is guaranteed to be globally unique; the non-registered App‑ID is not guaranteed to be globally unique. The detail format is described in clause 7.2.