WG 03 IoT Identifier Task Force Status 11/2017

Slides:



Advertisements
Similar presentations
1 Femto Cell System Overview S.P Status Update to CDG and Femto Forum Fukuoka, Japan, September 2010.
Advertisements

0 Chicago, IL March 6 th, 2007 Use Case Requirements, Design and Standards Selection HITSP Use Case Requirements, Design and Standards Selection Date:
Screen 1 of 24 Reporting Food Security Information Understanding the User’s Information Needs At the end of this lesson you will be able to: define the.
Science and Technology Committee GGOS, December 2006.
Gabriela Macoveiu North-East RDA, Romania PP11 – WP responsible Cluster Policy Learning Platform WP3 Description Smarter Cluster Policies for South-East.
AIOTI ALLIANCE FOR INTERNET OF THINGS INNOVATION Chair: Kit Lam (Samsung) & Co-Chair: Thomas Kallstenius (iMinds) Brussels, WG7 Wearables.
Capacity Building in: GEO Strategic Plan 2016 – 2025 and Work Programme 2016 Andiswa Mlisa GEO Secretariat Workshop on Capacity Building and Developing.
Brussels, January 16th, Overview and status of the project.
FSC Auditor requirements
Future Network Standardization Activities in ISO/IEC JTC1/SC6
Issues need harmonization
Third PMC meeting University of Priština, Kosovska Mitrovica
Status report on CJK NGN Working Group
Requirements Validation – II
IEEE 802 OmniRAN EC SG July 2013 Conclusion
IEEE 802 OmniRAN EC SG July 2013 Conclusion
OGSA Service Classifications
OmniRAN Introduction and Way Forward
Status report on CJK NGN Working Group
Vertical Applications TAG
Streamlining Vendor Risk Management with the HECVAT
Outcome TFCS-07 // August NH Den Haag, NL
Status report on the activities of TF-CS/OTA
DG Environment, Unit D.2 Marine Environment and Water Industry
WG Belgian Grid Implementation Network Codes.
VERMONT INFORMATION TECHNOLOGY LEADERS
Implementing the ESS Vision 2020
Standards” and by the Council key Priorities
Strategic Planning at Sunnybrook
Marine Strategy Framework Directive (MSFD)
Outcome of TFCS-12 - summary slides - (detailed meeting minutes will be provided separately) April The Shilla Seoul, ROK.
Well Identification Industry Meeting
Patrick Staes and Ann Stoffels
In this lesson you will learn how to…
the Public Procurement Audit Practical Guide
First 8 slides are what was presented in San Fransisco…
Activities of the UNECE-UNODC Task Force on Victimization Surveys
Status Nov 2017 and discussion on next steps
CEOS & Work Plan Status Steven Hosford WGCV-44 28th August 2018
WG 2.9 Best Practices in River Basin Planning
Status report from UNECE Task Force on Cyber Security &
Adaptive Product Development Process Framework
NERC Reliability Standards Development Plan
Informal document GRPE-78-23
OmniRAN Introduction and Way Forward
ISA2 Action : Catalogue of public services
Background During last GRPE meeting, EU, Japan and Korea requested the creation of an RDE IWG The GRPE accepted the proposal during its June 2018 meeting.
IMT-Advanced Technical Requirements
Status report of TF-CS/OTA
Completing your Program Review
Draft Mandate and Proposed Approach for the Drafting Group on
NERC Reliability Standards Development Plan
ESS.VIP ADMIN EssNet on Quality in Multi-source Statistics, progress report 19TH WORKING GROUP ON QUALITY IN STATISTICS, 6 December 2016 Fabrice Gras,
2nd Edition: 2019 Winter Standards Meeting
Current state & Prospects of implementation
Teacher Reference (Please use electronic version with class)
Adult Education Survey mandate of the TF AES
Exercise Name player Briefing
BUSINESS PLAN COMPETITION
Green Infrastructure: Working method
WG03 Task Force "IoT relation and impact on 5G"
DG Environment, Unit D.2 Marine Environment and Water Industry
Invasive Alien Species
Feedback from Meeting of the Working Group on Economic and Social Analysis 14th October 2014 MSCG November 2014, Brussels.
DG Environment, Unit D.2 Marine Environment and Water Industry
… Two-step approach Conceptual Framework Annex I Annex II Annex III
Implementing the ESS Vision 2020
UN-GGIM: Europe – Work Plan
Transmitted by the experts of IWG ASEP
High-Level Group for the Modernisation of Official Statistics
Presentation transcript:

WG 03 IoT Identifier Task Force Status 11/2017 22nd November 2017 WG 03 IoT Identifier Task Force Status 11/2017 Task Force co-leader: juergen.heiles@siemens.com Task Force co-leader: henri.barthel@gs1.org

WG 03 IoT Identifier Task Force - Scope Identification plays an important role for IoT. In addition to the identification of the Things identification of other entities will be needed. Various identification schemes already exist, are standardized and deployed. A thorough analysis of the identification needs and related standardization for IoT is therefore needed. The “IoT Identifier” task force will Evaluate identification needs for IoT and related requirements Classify different identification needs Collect existing identification standards and ongoing standardization work and elaborate their applicability for IoT Consider interoperability of identifiers Identify standardization gaps related to the IoT identification needs Consider security and privacy issues related to identification together with the Privacy and Security sub-groups of WG03 and the related work/activities in AIOTI WG04

WG 03 IoT Identifier Task Force - Deliverable The task force will generate a document that collects, evaluates and summarizes the topics covered by its scope including: IoT identification needs and related requirements Collection of existing identification standards and ongoing standardization work and their applicability for IoT Standardization gaps related to the IoT identification needs (not in release 1) The document will further consider specific topics like: Interoperability of identifiers Security and privacy issues related to identification???? The document will be developed as stand-alone document, however parts or even the whole document may become part of the IoT High Level Architecture document. The target is to have a version for review by end of 2017

WG 03 IoT Identifier Task Force – History & Status Survey was performed during March and April 2017 sent to over 80 standardization bodies, industry alliances and research projects around the world 82 responses were received including AIOTI WG03 internal feedback Survey result was used to define classes of identifiers and categories of requirements Identifier classes: Thing, Application & Service, Communication, User, Data, Protocol, Location Requirements categories: Uniqueness; Privacy; Security; Identified Entities; Identifier Pattern; Traceability, Authenticity & Origin; Scalability; Interoperability & Standards; Persistency & Re-use; Allocation, Registration & Resolution Editing meeting November 21st – 22nd in Brussels Went thru whole document, provided final text for several sections or discussed and assigned actions to provide final text to participants Final text shall be provided on December 13th Final editing and clean up afterwards WG03 review planned starting January 8th 2018 How long? Review at AITOI level: when, how External bodies? -> could result in a request to list standards from all of these bodies in our example list

Deliverable ToC Executive Summary List of Abbreviations Introduction Classification of identifiers Requirement Categories for Identifiers Identifier Standards Allocation, Registration and Resolution of Identifiers Security and privacy?? Interoperability of Identifiers Annex I IoT Identifiers Survey Annex II Multiple Identifiers Example: Mobile Phone Annex III References Annex on Example of identifiers in LPWAN (might be added) Link do document: https://docs.google.com/document/d/117VQK1FNTfj-rzfS3Ff_Yc8dZ7T9Tg7-V8Qt5dQPAC8/edit?usp=sharing

WG 03 IoT Identifier Task Force – Issues Requirements section of document contains WG03 view Based on discussion of participants of editing meeting Could be controversial, lets see review feedback Standards We cannot list all standards that we have in our list (which is anyway not complete). Just writing down a standard is useless if we don’t provide the relevant information related to identifiers for that standard. As we don’t have access to all standards, not the time, not the resources and not the expertise to do that for all of them we will select only a few as examples. That will be expressed in the introduction also saying that these examples are not specific recommendations from WG03. For each identifier category we will provide some examples. Without a detailed standardization analysis it is also not possible to perform a gap analysis Security & Privacy We don’t have the expertise to write this section We don’t get specific input from the security and privacy group of WG3 How to go forward (remove, leave open, repeat general statements from requirements section)? In general we have limited (but effective) participation and expertise to cover all topics relevant for identifiers in detail

WG 03 IoT Identifier Task Force – Supporters We would like to specially thank Stefan Mangold and Thomas Klein for their contribution and support of the editing work We would like to thank Lindsay Frost and Marco Hogewoning for their contribution

Jürgen Heiles (juergen.heiles@siemens.com) Henri Barthel (henri.barthel@gs1.org)