Introduction to MAF Stage 3 CR SEC2016 0128

  • Slides: 7
Download presentation
Introduction to MAF Stage 3 CR SEC-2016 -0128 Group Name: SEC WG Source: Qualcomm

Introduction to MAF Stage 3 CR SEC-2016 -0128 Group Name: SEC WG Source: Qualcomm Inc. , Phil Hawkes, Wolfgang Granzow Meeting Date: SEC#23. 4, 2016 -06 -29 Agenda Item: End-to-End Security

Entities involved in Remote Security Provisioning Field Domain UN-SP Domain GBA BSF (=MEF) 3

Entities involved in Remote Security Provisioning Field Domain UN-SP Domain GBA BSF (=MEF) 3 rd Party Domain or M 2 M-SP Infrastructure Domain Field or Infrastructure Domain MEF MAF M 2 M Entity A SAEF after RSPF M 2 M Entity B 2

Currently unspecified interfaces Field Domain 3 rd Party Domain or M 2 M-SP Infrastructure

Currently unspecified interfaces Field Domain 3 rd Party Domain or M 2 M-SP Infrastructure Domain Field or Infrastructure Domain MEF MAF M 2 M Entity A Interface in scope of SEC -2016 -0128 M 2 M Entity B 3

Summary of SEC-2016 -0128 • Editorial Changes – End-Point MAF Client – MAF Security

Summary of SEC-2016 -0128 • Editorial Changes – End-Point MAF Client – MAF Security Framework MAF Interface • Scope: Between MAF Client and MAF only – Reorganization of existing sub clauses (next slide) • Technical changes – Stage 3 details for MAF Interface 4

Use of MAF Interface 5

Use of MAF Interface 5

MAF Interface Stage 3 Details • Used similar approach to separation of Mcc/Mca stage

MAF Interface Stage 3 Details • Used similar approach to separation of Mcc/Mca stage 3 – Specify data objects, structure and data types TS-0004 (Core) • Data objects = {Primitive parameters, resources and attributes} • Also includes detailed processing – Specify bindings to Application layer transport protocols • TS-0008/9/10/20 (HTTP/1. 1, Co. Ap, MQTT, Web. Socket) • For MAF Interface – Already have detailed processing specification – NEW Specify data objects, structure and data types • Data objects = requests and responses parameters – NEW Define Bindings to application layer transport protocol • So far have HTTP/1. 1, Co. AP. Could easily add Web. Socket. MQTT not suitable 6

New Organization of Clause 8. 8 Clause Topic Was Changes 8. 8. 1 Introduction

New Organization of Clause 8. 8 Clause Topic Was Changes 8. 8. 1 Introduction to MAF I/F 8. 8. 1 Terminology. Scope of MAF i/f 8. 8. 2 MAF I/F Processing details NEW 8. 8. 2. 1 Introduction to clause 8. 8. 2 NEW 8. 8. 2. 28. 8. 2. 5 MAF Procedures 8. 8. 38. 8. 6 8. 8. 3 MAF I/F msg Def’n NEW 8. 8. 3. 1 Generic details. . NEW * Generic def’n of parameters in MAF I/F request and response * Datatypes 8. 8. 3. 2 Procedure-specific details. . NEW Parameter values for each procedure 8. 8. 3. 3 MAF I/F Protocol Binding NEW HTTP/1. 1 and Co. AP 8. 8. 4 MAF Credential Configuration 8. 8. 2 Terminology. Reference to msg definitions Terminology 7