App-ID Ad-Hoc Technical Issues TP AppID R02

Slides:



Advertisements
Similar presentations
Intro Matt Reeves – FirsTech Lyle Wolinsky – Global Express Stella Pulliam – Sempra Utilities Kim Folks – Tampa Electric Guidelines for a Successful RFP.
Advertisements

HORIZONT 1 ProcMan ® The Handover Process Manager Product Presentation HORIZONT Software for Datacenters Garmischer Str. 8 D München Tel ++49(0)89.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
App-ID Ad-Hoc Technical Issues TP AppID R02 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,
Introduction to ICANN’s new gTLD program. A practical example: the Dot Deloitte case. Jan Corstens, Partner, Deloitte WIPO Moscow, 9 Dec 2011.
ISO 9001:2008 What did the November 2008 amendments to ISO 9001 mean to you?
OneM2M Draft proposal for slide set. This is not intended to be a oneM2M presentation. It is a collection of source material slides which can be used.
OSIAM4HE Proposed org structure Authored by the strategy and organization team.
Proposal for App Id and Service Provider Id registration Group Name: Shelby Kiewel Source: Shelby Kiewel, iconectiv / Ericsson,
Solution Provider Agreement (SPA) Re-enrollment 2006 Name Title Group Microsoft Corporation.
App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,
App-ID Ad-Hoc Technical Issues TP AppID R01 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,
OpenSG Conformity IPRM Overview July 20, ITCA goals under the IPRM at a high level and in outline form these include: Organize the Test and Certification.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
1 Thank you for visiting our site and welcome to the “Introduction to ISO 22000” Presentation that you requested. For more information.
Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.
Second Generation Electronic Filing Specifications Legal XML Court Filing Committee April 26, 2004.
Company Confidential Registration Management Committee (RMC) AS9104/2A Presentation San Diego, CA January 17, 2013 Tim Lee The Boeing Company 1 Other Party.
Proposal for App Id and Service Provider Id registration Group Name: Shelby Source: Shelby, iconectiv / Ericsson,
ISO Environmental Management Systems 1 ISO LEGAL AND OTHER REQUIREMENTS.
Timeline for the oneM2M Partnership Project Timeline and Milestones [Steve Barclay, ATIS] [Joachim Koss, ETSI] Contribution to oneM2M-Cons#4, 28 Mar 2012.
App-ID Use Cases, Syntax and Attributes ARC R01-App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,
Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: Agenda Item:
Credential Identifiers Group Name: SEC#14.2 Source: Phil Hawkes, Qualcomm Inc, Meeting Date:
WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
Networks ∙ Services ∙ People eduGAIN Townhall Meeting Nicole Harris (or updating the eduGAIN policy suite) “Unicorns can be sued in Wales”
M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:
Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
International Planetary Data Alliance Registry Project Update September 16, 2011.
Contestability in Connections Contestability Working Group Meeting NIE/SONI Joint Presentation 9 September
Training for developers of X-Road interfaces
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Clean Development Mechanism
Training for developers of X-Road interfaces
InLoox 9 Web App Product Presentation
Recommended Draft Policy ARIN
Resource subscription using DDS in oneM2M
Help make energy efficiency easy, transparent and scalable.
PLWG Review 6.9 and the Interconnection process
Training for developers of X-Road interfaces
ATIS Open Source IoT (OS-IoT)
Possible options of using DDS in oneM2M
Proposed design principles for modelling interworked devices
WPM ad-hoc group report TP#25
<Insert Picture Here>
Построение культуры integrity в компании Aнар Каримов партнёр «ЭКВИТА»
SDLS Protocol Green Book initiation
2 Selecting a Healthcare Information System.
InLoox 9 Web App Product Presentation
Outcome TFCS-11// February Washington DC
3GPP Status.
Choosing the Discovery Model Martin Forsberg
Project Plan Template (Help text appears in cursive on slides and in the notes field)
MODULE C - LEGAL SUBMODULES C1. Conflict Of Interest/Code Of Ethics
SBS Vendor Management™
Cybersecurity Special Public Meeting/Commission Workshop for Natural Gas Utilities September 27, 2018.
Recommended Draft Policy ARIN : Post-IPv4-Free-Pool-Depletion Transfer Policy Staff Introduction.
Inhalt Project Management in your browser Your Workplace on the Web
CIS460 – NETWORK ANALYSIS AND DESIGN
Proof of concept 29 September 2010
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
e-Invoicing – e-Ordering 20/11/2008
Current standardization activities – oneM2m
Metadata The metadata contains
Support for syntaxes (UBL and UN/CEFACT) Nicosia October 30, 2017
Executive Project Kickoff
Project Kick-off <Customer Name> <Project Name>
{Project Name} Organizational Chart, Roles and Responsibilities
Mobile Registration App Training Guide for OPO Staffers
Presentation transcript:

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.