Presentation is loading. Please wait.

Presentation is loading. Please wait.

Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: 2015-09-07 Agenda Item:

Similar presentations


Presentation on theme: "Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: 2015-09-07 Agenda Item:"— Presentation transcript:

1 Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, dhemphill@iconectiv.com Meeting Date: 2015-09-07 Agenda Item: Proposed App-ID Format

2 © 2015 oneM2M Partners 2 Agenda App-ID TP mail list discussion Proposed App-ID

3 TP App-ID Mail List Discussion Weekly Topics Week 1: (July 27 th ) Requirements Week 2: (Aug 3 rd ) Use cases Week 3: (Aug 10 th ) Application Registrant – company, organization, individual Week 4: (Aug 17 th ) App-ID format - Full App-ID format, separator etc. Week 5: (Aug 24 th ) Summary and Change Request Week 7: (Sept 7 th ) TP#19

4 Email Discussion Summary Focus is on the format of registered App-IDs – no guidance for non-registered App-ID format – security processes are independent of the App-ID format and are being handled separately Clarified terminology surrounding uniqueness “The full registered App-ID is globally unique, and the [namespace].[appName] is unique in the scope of the Registration Authority.”

5 Proposed App-ID Format Existing App-ID format (Rel 1): r[Authority-ID]/[Registered-App-ID] Proposed App-ID format: (Rel 2)r[Authority-ID].[namespace].[appName] Example: ra01.com.ibm.smartcity r – App-IDs which begin with an “r” are registered IDs. App ‑ IDs which begin with an “n” are non-registered IDs. a01 – the Authority-ID as managed by the oneM2M Steering Committee and assigned by the Management Authority com.ibm – the application developer namespace smartcity – the application name

6 App-ID Format Notes Proposed App-ID format: r[Authority-ID].[namespace].[appName] Example Registered App-ID: ra01.com.ibm.smartcity Notes: 1.The full registered App-ID is guaranteed to be unique. The Registration Authority will ensure the [namespace].[appName] is unique within the Authority-ID. 2.Namespace is recommended to be reverse DNS and will follow DNS naming restrictions e.g., a-z, 0-9, periods and hyphens, but can not start or end with a hyphen or period. No validation of Namespace is provided. 3.AppName is recommended to be the application name using only a-z and 0-9 as characters.


Download ppt "Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: 2015-09-07 Agenda Item:"

Similar presentations


Ads by Google