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

Slides:

Advertisements

Similar presentations

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Advertisements

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

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

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.

HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: (PRO#12.0) Agenda Item: HTTP.

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

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

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

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

App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, Meeting Date:

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

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

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

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

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

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

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.

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

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

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

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

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.

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

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

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

M2M Service Session Management (SSM) CSF

E2EKey Resource Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.3, Agenda Item: End-to-End Security.

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, 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:

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

LWM2M Interworking Proxy Procedures ARC Considerations

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.

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

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

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

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

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 on Certification Group Name: TST WG Source: JaeSeung Song, WG6 Chair, Meeting Date: TST #21.

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

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

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

App-ID Ad-Hoc Technical Issues TP AppID R02

3GPP MBMS protocol stack

Service Framework Proposal

Group multicast fanOut Procedure

2nd Interoperability testing issues

Emergency Service – NS/EP Vs E-911 for IEEE m

Possible options of using DDS in oneM2M

MAF&MEF Interface Specification discussion of the next steps

3GPP Interworking Abstraction

oneM2M Versioning Next Steps

Considering issues regarding handling token

CMDH Refinement Contribution: oneM2M-ARC-0397R01

Service Layer Dynamic Authorization [SLDA]

Presentation transcript:

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

Response Code - Basic Ranges rs: response code: This parameter indicates whether the operation was successful, unsuccessful or is an acknowledgement Propose first numeric field of multi-field response code is (constrained integer type) 0000-vvvv indicates successful operation wwww-xxxx indicates unsuccessful operation yyyy-zzzz indicates acknowledgement © 2014 oneM2M Partners PRO Response_Status_Codes_Concepts 2

Response Code – Multi-Field Many response codes expected to only need encoded numeric field e.g. ACKs Some response codes may have additional fields for detailed parameters which are not encoded in response codes e.g. version Some successful response codes expected to have additional fields regarding Warnings Many unsuccessful response codes will have additional fields e.g. List of Request parameter names not supported PRO Response_Status_Codes_Concepts

Mcc vs Mca Response Codes Many response codes will be used at the service level which are not exposed to AEs. – External Protocol/Device management related – Transport Protocol related AE response codes needed per AE Requests only – ROA and reserved numeric field ranges for SOA Plus other reserved numeric field ranges for future – Mcn and Mcc’ – Future releases – Additional protocols – Vendor extensions PRO Response_Status_Codes_Concepts

Response Code – Basic Format Encoded number, oneM2M version, argument1, …, argumentN (TS-0004 data type: constrained integer, list of strings) Use “argument” used since we already use “parameters” and “attributes” All fields mandatory dependent upon encoded number Not included – Support for multiple response codes I.E. only first error/warning detected per validation procedures – Selection mechanism of lite vs. detailed response code Optimizations may be included in subsequent releases – Human readable description – Support for ARC TS “cn may be present in a Response to provide more error information” – Support for ARC TS “cs: status codes (e.g., authorization timeout, etc.).” Encoding of response codes is FFS, new TS-0004 clause and other stage 3 TS’s PRO Response_Status_Codes_Concepts