1. PRO-2014-0516R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU, shingo_fujimoto@jp.fujitsu.com Meeting Date: 2014-10-09 Agenda Item: Protocol Core TS

2. PRO-2014-0516R01-URI_mapping_discussion Introduction The distributed administration of m2m resources looks good, but it may be troublesome in our M2M use cases. This contribution proposed to use single URI space covering resources which are hosted by multiple CSEs

3. PRO-2014-0516R01-URI_mapping_discussion Problem on CSE addressing Arc-TS specified the Registration procedure of CSE, but it is not feasible on multi-hopped MN-CSE configuration IN-CSE cannot find the route to Hosting CSE in this example, since Hosting CSE did not register on IN-CSE and IN-CSE cannot route the request to MN-CSE. Registrar CSE for AE AE IN-CSE MN-CSE (reachable) Hosting CSE (Target) MN-CSE (unreachable) Reachability information is not provided to IN-CSE by Registration

4. PRO-2014-0516R01-URI_mapping_discussion Single URI space for domain Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Delivery-path RegistrationInternal Request Forwarding Path Registration on IN-CSE (out-of-bound ?) Registration through Mca Path Registration on IN-CSE (Registration forwarding) Registration through Mca Forward Request to Hosting CSE via MN-CSE Forward Request to Hosting CSE Request to URI pointing IN-CSE URI  CSE Mapping

5. PRO-2014-0516R01-URI_mapping_discussion Use Case not require request forwarding Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Container hosted by IN-CSEDevice Management through Mcn Management through Mcn Sending Data as ContentInstance Report Management Result thorugh Mcc Request to URI pointing IN-CSE Sending Data as ContentInstance Retrieval of Data

6. PRO-2014-0516R01-URI_mapping_discussion Proposed Assumption on URI URI will be based on the address of IN-CSE. Each CSE can be accessed through remoteCSE resource on IN-CSE. “Path-Registration” may be implemented to enable routing with in-bound communication. Request will be forwarded based on PoA information hop-by-hop from IN-CSE.

7. PRO-2014-0516R01-URI_mapping_discussion URI Examples http://m2m.example.com/cseA/res1/res2  http://cseb.example.com/cseA/res1/res2 (rewrite URI) http://m2m.example.com/mgmt-cseA/res3/res4  mapping to Mcn access (ex. OMA-DM) to CSE-A http://m2m.example.com/container/pl1/content1  data storage hosting on IN-CSE as /container/pl1/… URI of CSEBase Name of remoteCSE ( via cseB.example.com) Path of resource URI of CSEBase Name of mgmtObj resource Path of MO URI of CSEBase Name of containers

8. PRO-2014-0516R01-URI_mapping_discussion Conclusion This change may not affect on Arc-TS, but WG3 member requested to check with WG2 HTTP/CoAP binding use URI as the address, and relationship between CSE-ID and (hierarchical) resource URI should be clarified