Joint PRO/ARC session at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date: 2015-11-09.

Slides:

Advertisements

Similar presentations

WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Advertisements

Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

WG PRO Progress Report at TP17 Group Name: oneM2M TP17 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Group:WG3 (PRO) Source:Peter Niblett, IBM, Date: Agenda:PRO#14 TS-0004 Data Representation Proposal Discussion.

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

OneM2M-MP Data_Model_Repository Establishing Data Model Repository for oneM2M Group Name: Method and Procedure Sub-commitee Source: WG3 chair.

Group:WG3 (PRO) Source:Peter Niblett, IBM, Date: Agenda:PRO#14 TS-0004 Data Representation Proposal Discussion.

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.

TST WG Progress Report at TP 17 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Sapporo, Japan Agenda.

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless

OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

WG 3 Progress Report at TP14 Group Name: oneM2M TP14 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Guidelines for: Release Maintenance, Small Enhancement and Feature Work Items Group Name: TP15 Source: Mow Convenor, (Scarrone Enrico, Telecom Italia)

WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Subscription ID Scope Date Submitted: June, 14 th, 2007 Presented.

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,

WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.

Abierman-netconf-mar07 1 NETCONF WG 68 th IETF Prague, CZ March 19, 2007.

MoW&M&P Report Group Name: TP18 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

ARC / PRO questions Source: Peter Niblett, IBM Date:

WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

SRAMP-8 Update ZIP Publishing. Issue 8 – ZIP Publishing ZIP Publishing in the contributed documents needs to be reviewed and revisited. The basics of.

WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

WPM ad-hoc group report TP#20 Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Discussion of open issues for WebSocket binding Group Name: PRO WG Source: Qualcomm Inc., Wolfgang Granzow, Nobu Uchida Meeting Date: PRO#22,

TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.

Session-Independent Policies draft-ietf-sipping-session-indep-policy-02 Volker Hilt Jonathan Rosenberg Gonzalo.

oneM2M interop 3 issues and optimizations

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

MIME Type Definition Group Name: PRO WG

2nd Interoperability testing issues

oneM2M Service Layer Protocol Version Handling

MAF&MEF Interface Specification discussion of the next steps

TS-0004 Data Representation Proposal Discussion

Discussion to clarify online/offline behavior

oneM2M Versioning Next Steps

Service Layer Dynamic Authorization [SLDA]

Network Services Interface

Summary of the MAF and MEF Interface Specification TS-0032

Change Proposals for SHAKEN Documents

oneM2M interop 6 action point

BINDing URIs to SIP AORs

Presentation transcript:

Joint PRO/ARC session at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

Items for discussion ResourceName attribute vs Name Primitive parameter Findings of interop test TS-0001 / TS-0004 Alignment Stage 3 contributions for R2 items

Resource Name © 2015 oneM2M Partners 3 Current status – R1 versions of TS-0001 and TS-0004 contain both a Name primitive parameter and a resourceName universal attribute The idea is you use the Name parameter to request a name on a create request, but the actual name (which may be different) is returned in the resourceName attribute There are some contradictions in the current drafts of these documents, which has led to some confusion among implementers – The Name primitive parameters has been removed from the R2 version of TS-0001 On create, you now supply the name that you want in the resourceName attribute – this may then get modified by the hosting CSE WG3 has CRs in progress to remove the Name parameter from R2 versions of TS-0004 and the various protocol bindings TS documents Questions – What changes do we make to R1 ? – Under what circumstances is the hosting CSE allowed to modify the value (8.10)?

Resource Name options © 2015 oneM2M Partners 4 1.Remove the Name parameter from release 1 versions of TS-0001 / TS-0004 and the bindings documents. In other words mirror the R2 changes back into R1. 2.Leave the Name parameter in release 1 version of TS-0001 / TS-0004, but update TS-0004 to permit (or possibly encourage) the use of the ResourceName attribute on Create as an alternative. 3.Leave the definition of the Name parameter in release 1 of TS-0001 / TS and update the text in TS-0004 to make it clear that you use this parameter (not the ResourceName) on Create. The consequence of this is that release 1 and release 2 will be different. 4.Add the Name parameter back into release 2, and clarify its use on create (i.e. reverse the decision to remove it)

ClauseDescriptionARCPRO 8.1Notification URI structureN/ACR needed 8.2Notification Content formatCR needed 8.3Structured resource URI formatN/ACR needed 8.4Timestamp formatN/APRO /7 8.5Ability to use milliseconds in timestampsN/ACR needed 8.6XSD file version consistencyN/A? 8.7XSD validationN/A? 8.8Root element in JSON representationN/APRO Representation of JSON listsN/A? Interop test findings -1

ClauseDescriptionARCPRO 8.10Altering resourceName by the server?PRO Notification event type default?PRO /7 8.12Notification type 3 (direct child creation)?? 8.13SP-ID position in resource URI?? 8.14HTTP header case sensitivityN/APRO /3 8.15Contents of update responseN/A? 8.16Default ACP for registered AE’sN/A? 8.17HTTP conflict status code inconsistencyN/APRO /4 8.18ResourceID attribute structure?CR needed Interop test findings -2

ClauseDescriptionARCPRO 8.19Make RequestID optional?? 8.19Less verbose media typesN/A? 8.19Make Response Status Code optionalN/A? 8.20Allow both long and short names?? 8.20Support other encodings (e.g. binary ones)?? Interop test findings -3