App-ID Ad-Hoc Technical Issues TP AppID-2014-0003R01 Group Name: App-ID Ad-Hoc Group Source: Darold...
-
Upload
kevin-crawford -
Category
Documents
-
view
217 -
download
1
Transcript of App-ID Ad-Hoc Technical Issues TP AppID-2014-0003R01 Group Name: App-ID Ad-Hoc Group Source: Darold...
App-ID Ad-Hoc Technical IssuesTP AppID-2014-0003R01
Group Name: App-ID Ad-Hoc GroupSource: Darold Hemphill, iconectiv, [email protected] Date: 2015-01-12
© 2014 oneM2M Partners
Contents
• Registry challenges• Possible registry solutions: Partitioned vs.
Central/Root• Required attributes• Use case scenarios
2
© 2014 oneM2M Partners
Registry Challenges• Ensuring App-IDs are not duplicated• Required fields are provided• Archive and Validate API (WADL, WSDL etc.)• Identify Company or Group creating App-ID– Company creating App-ID is only party allowed to
version the App-ID i.e., version 1, version 2 (not software version)
– Associating users to companies to control authorization
– Maintain Company/Group buyouts, mergers, acquisitions
3
© 2014 oneM2M Partners
Partitioned Registry
4
Pros•Steering Committee assigns namespaces to Registrars•Registrars are independent - no common infrastructureCons•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 AA-123
Registrar BB-123
Registrar CC-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
© 2014 oneM2M Partners
Common Infrastructure
Central/RootRegistry
Registrar AABC-123
Registrar BABC-124
Registrar CABC-125
API
Central/Root Registry
5
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 RegistrarsCons•Someone needs to build and maintain the DB and API as a shared resource•API source ownership
Firewall
© 2014 oneM2M Partners
Required Attributes for App-ID
• Company (and User) requesting the App-ID– Who can version the App-ID?
• Version of the App-ID – Expect that APIs will expand and change over time
• Protocol of the App-ID– App-ID for REST and SOAP might have the same
scope, but nodes can speak one protocol and not the other
6
© 2014 oneM2M Partners
App-ID Scenario 1• Company A creates App-ID X version 1 for a REST
API• Hardware and software environment build
around App-ID X• Company B creates a variation of App-ID X
Questions1. Should any Company B be able to define App-ID X
version 2 or create their own App-ID?
7
© 2014 oneM2M Partners
App-ID Scenario 2• The Steering Committee initially assigns 3 registrars in
a partitioned App-ID solution.• After some time, one of the registrars wishes to
discontinue supporting their registry partition.• The Steering Committee would need to transition the
partitioned App-ID space to a new registrar or existing registrar who would assume responsibility for maintaining the App-IDs going forward.
• Companies wishing to version their App-IDs will purchase from new registrar.
Note: this scenario only occurs in a partitioned App ID ‑registry.
8
Summary
• This is an introduction to the Registry issues• An initial draft of recommendations is
contained in contribution TP AppID-2014-0001• It is understood that additional concepts and
issues may arise as the result of this overview
9