Re: [core] Tr : New Version Notification for draft-vial-core-mirror-proxy-00.txt

[[e-mail]]

>Now I think you might be referring to the links that an RD returns as a 
result of a lookup. I agree, it would be inefficient to repeat that for 
each resource link. 

Exactly.

>I think there should be a way to return a link to the end-point itself, 
where such end-point specific information can be returned (e.g. id=). This 
could be done by providing an additional REST interface for looking up 
end-points rather than resources.

When a sleeping endpoint registers with 2 mirror proxies, we've got 2 
endpoints in the RD database for the same id attribute. Also the proxy 
shares its endpoint with the registered sleeping nodes.
If I'm following your idea the right way, the new interface might return 
something like below (don't pay too much attention to the attribute 
format, could be something else)

GET /rd/new_interface
</rd/1>;ep="coap://[aaaa::ff:fe00:0001]/";h="proxy1";id="urn:dev:mac:0024befffe804f01",
</rd/2>;ep="coap://[aaaa::ff:fe00:0001]/";h="proxy1";ins="sleepy";id="urn:dev:mac:0024befffe804f03",
</rd/3>;ep="coap://[aaaa::ff:fe00:0002]/";h="proxy2";id="urn:dev:mac:0024befffe804f02",
</rd/4>;ep="coap://[aaaa::ff:fe00:0002]/";h="proxy2";ins="sleepy";id="urn:dev:mac:0024befffe804f03",

I still don't know how to relate the previous result with a resource 
lookup like:

GET /rd/rt=Temperature
<coap://[aaaa::ff:fe00:0001]/temp>;rt="Temperature";if="sensor"
<coap://[aaaa::ff:fe00:0001]/mp/0/temp>;rt="Temperature";if="sensor"
<coap://[aaaa::ff:fe00:0002]/temp>;rt="Temperature";if="sensor"
<coap://[aaaa::ff:fe00:0002]/mp/0/temp>;rt="Temperature";if="sensor"

Lines 2 and 4 are actually the same sensor mirrored on 2 proxies.

We might extend the Context parameter in the registration interface to 
accept a root path. We would have then:

GET /rd/new_interface
</rd/1>;ep="coap://[aaaa::ff:fe00:0001]/";h="proxy1";id="urn:dev:mac:0024befffe804f01",
</rd/2>;ep="coap://[aaaa::ff:fe00:0001]/mp/0";h="proxy1";ins="sleepy";id="urn:dev:mac:0024befffe804f03",
</rd/3>;ep="coap://[aaaa::ff:fe00:0002]/";h="proxy2";id="urn:dev:mac:0024befffe804f02",
</rd/4>;ep="coap://[aaaa::ff:fe00:0002]/mp/0";h="proxy2";ins="sleepy";id="urn:dev:mac:0024befffe804f03",

But it's still quite complex for a client to deduplicate the links.

Adding the identifier to each link is not efficient but should work with 
both RD and /.w-k/core.

Matthieu