PowerPoint Presentation

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

App-ID Ad-Hoc Technical IssuesTP AppID-2014-0003R02

Group Name: App-ID Ad-Hoc Group

Source: Darold Hemphill, iconectiv, dhemphill@iconectiv.com

Meeting Date: 2015-01-23

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Contents

•What is App-ID?

•Registry challenges

•App-ID Ad Hoc Group charge

1.Requirements for potential App-ID Registration Authorities

2.Recommendation for determining the App-ID RegistrationAuthorities

3.Recommendation for the timeline of the selection of the RegistrationAuthorities

•Open Issues

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

What is App-ID

•App-ID is short for Application ID

–Nicolas Damour introduced ARC-2015-1716 to clarify theintended meaning and use of App‑ID in TS‑0001 - Thanks

•App-ID identifies a softwareapplication (by version) runningin the Application Layer

Application

Layer

Common Services

Layer

Network Service

Layer

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Uses of App-ID

•The Common Service Layer knows theapplication by its AE-ID and App-ID

•App-ID is used by security

•App-ID will likely be requiredfor certification

Application

Layer

Common Services

Layer

Network Service

Layer

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Registry Challenges

•Required fields

–Software version e.g., version 3.2

–Company requesting App-ID e.g., CustomSoft Inc.

•Company creating App-ID is only party allowed to versionthe 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

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

App-ID Ad-Hoc Group Charge

Provide recommendations to the TP for:

1.Requirements to be met by the App-IDRegistration Authorities

2.Recommendation for determining the App-IDRegistration Authorities

3.Recommendation for the timeline of theselection of the Registration Authorities

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

1. Requirements for App-ID Registry

The Registration Authorities shall comply with the following:

1.oneM2M Registrars shall ensure global uniqueness of registered IDs.

2.The company requesting an App-ID will have a Company ID.

a)Company incorporation documentation will be required when requesting a newCompany ID

b)The Company ID shall be associated with the App-ID

3.The Registration Authority shall maintain a Service Level of 99% uptime.Scheduled downtime of more than 4 hours should be communicated tothe oneM2M Steering Committee.

4.Registrars must maintain activity log files and provide to oneM2MSteering Committee upon request.

5.Required attributes shall be collected in support of ID generation.

6.All registry information shall be in the English language.

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

2. Requirements for App-IDRegistration Authorities

7.Training to support the use of the registry content and access shall bemade available.

8.Registration Authorities may use company branding for the registry aslong as the oneM2M logo also appears – per MARCOM approval

9.Reasonable and customary charges will be allowed for pay services.

10.User information will be passed over HTTPS connections. Registryinformation will be secured behind a firewall.

Note: The oneM2M standard allows companies to create a private App-IDRegistry for their internal use. The above requirements do not apply toprivate App-ID Registries.

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

2. Determining the App-IDRegistration Authorities

1.oneM2M member or partner in good standing

2.history of providing and managing a global registryin coordination with an international standardsbody and in compliance with internationalstandards

3.high-level schedule to meet the oneM2M timelines

4.description of customer support and training insupport of the oneM2M Registry

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

2. Determining the App-IDRegistration Authorities

Legal Challenge

•oneM2M is not a legal entity that can contractfor the services of a Registration Authority

•Most likely a SDO will be asked to contractwith the Registration Authorities

•oneM2M will need to agree to the vendorselection requirements of the SDO e.g., openRFP and timeline

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

3. Recommended Timeline

Date

Activity

2/15/2015

App-ID Ad-hoc group presentrecommendation to Technical Plenarybefore TP#17

3/23/2015

Technical Plenary review, approve andpresent recommendations to SteeringCommittee

3/15/2015

Steering Committee review andacceptance of recommendation

5/1/2015

Steering Committee selection ofRegistration Authorities

7/31/2015

Registry available for beta testing

12/31/2015

oneM2M registries generally available

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Summary

•This is an introduction to the Registry issues

•An initial draft of recommendations iscontained in contribution TP AppID-2014-0002

•It is understood that additional concepts andissues may arise as the result of this overview

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Open Issues

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Partitioned Registry

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

Registrar A

A-123

Registrar B

B-123

Registrar C

C-123

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

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Common Infrastructure

Central/Root

Registry

Registrar A

ABC-123

Registrar B

ABC-124

Registrar C

ABC-125

API

Central/Root Registry

Pros

•DB Layer and someprocessing 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 andmaintain the DB and API as ashared resource

•API source ownership

Firewall

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

Background Slides

$C:\Documents and Settings\mcauley\Local Settings\Temp\wz83a6\oneM2M\oneM2M-Logo.gif$

ARC-2015-1716 CR

•Nicolas Damour introduced ARC-2015-1716 to clarify theintended meaning and use of App‑ID in TS‑0001 - Thanks

7.1.3Application Identifier (App-ID)

An Application Identifier (App-ID) uniquely identifies an M2MApplication in a given context. More precisely, there are twotypes of App-ID: registration authority defined App-ID (registeredApp-ID) and non-registered App-ID. The establishment of theregistered App-ID is guaranteed to be globally unique; the non-registered App‑ID is not guaranteed to be globally unique. Thedetail format is described in clause 7.2.