Open bsilverajan opened 8 years ago
Investigate a mechanism for reporting lifetimes per transport URI
eg:
REQ: GET /.well-known/core?tt=*
RES: 2.05 Content ;tt="sms udp" coap+sms://001234567/;rel="altloc" coap://server.example.com/;lt=200,rel="altloc"
Alternative:
Consider a new entry point for protocol negotiation using URI templates, similar to resource directory
eg GET /pn/tt?lt="100"
the "lt" link attribute would be introduced in version -03 of the draft
Name of lifetime link extension is changed to "al", active lifetime in version -03.
Investigate a mechanism for reporting lifetimes per transport URI
eg:
REQ: GET /.well-known/core?tt=*
RES: 2.05 Content ;tt="sms udp" coap+sms://001234567/;rel="altloc" coap://server.example.com/;lt=200,rel="altloc"
Alternative:
Consider a new entry point for protocol negotiation using URI templates, similar to resource directory
eg GET /pn/tt?lt="100"