Yes, the REST API could describe the resource and map the protocol for establishing a connection, for example the SIP/SDP interface, then the client would open another socket and use RTP/RTCP natively to control and consume the stream.
Best regards, Michael > On Jun 14, 2016, at 7:20 AM, Macieira, Thiago <thiago.macieira at intel.com> > wrote: > > The description is so vague that the use-case would be "all of them". > > Just one example: if I searched for oic.d.camera and found one, I might want > to RETRIEVE its streaming details (probably a URL from which to get the RTP > stream). This is where UPnP knowledge would be useful: is a URL enough? > > If not, then what more information would we need? Or is it too much > information there, stuff that wouldn't make sense in a REST model? If it's > the latter case, then the RETRIEVE would only include a property saying "for > streaming, query via UPnP / DLNA" (with port number and IP address, so no > discovery is necessary). > > From: Wouter van der Beek (wovander) [wovander at cisco.com] > Sent: Tuesday, June 14, 2016 00:28 > To: Manoj Verma > Cc: Lofgren, Scott O; Macieira, Thiago; cftg at openconnectivity.org; uzchoi > at samsung.com; ??; iotivity-dev at lists.iotivity.org > Subject: RE: [cftg] RE: Re: [dev] AV streaming on Iotivity. > > Use case please? > > Kind Regards, > Wouter > > From: Manoj Verma [mailto:manoj.kumar.mbm at gmail.com] > Sent: 13 June 2016 15:18 > To: Wouter van der Beek (wovander) <wovander at cisco.com> > Cc: Lofgren, Scott O <scott.o.lofgren at intel.com>; Macieira, Thiago > <thiago.macieira at intel.com>; cftg at openconnectivity.org; uzchoi at > samsung.com; ?? <ashok.channa at samsung.com>; iotivity-dev at > lists.iotivity.org > Subject: Re: [cftg] RE: Re: [dev] AV streaming on Iotivity. > > May be we can use iotivity to control or discover resource which generate > binary data over gateway ------> control commands > And for data transfer we may use RTP or something else as separate service > ------> data transfer > > Manoj Kumar > (NEC technologies) > > On Mon, Jun 13, 2016 at 4:37 PM, Wouter van der Beek (wovander) <wovander at > cisco.com <mailto:wovander at cisco.com>> wrote: > Well the only video streaming is defined is for cameras.. .this is in the SH > specs and uses RTP... > > Anything else: UPnP is part of OCF.. so use UPnP for anything else.. > > Kind Regards, > Wouter > > -----Original Message----- > From: cftg at openconnectivity.org <mailto:cftg at openconnectivity.org> > [mailto:cftg at openconnectivity.org <mailto:cftg at openconnectivity.org>] > On Behalf Of Lofgren, Scott O > Sent: 11 June 2016 01:17 > To: Macieira, Thiago <thiago.macieira at intel.com <mailto:thiago.macieira at > intel.com>>; cftg at openconnectivity.org <mailto:cftg at > openconnectivity.org>; uzchoi at samsung.com <mailto:uzchoi at samsung.com> > Cc: ?? <ashok.channa at samsung.com <mailto:ashok.channa at samsung.com>>; > Manoj Verma <manoj.kumar.mbm at gmail.com <mailto:manoj.kumar.mbm at > gmail.com>>; iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at > lists.iotivity.org> > Subject: RE: [cftg] RE: Re: [dev] AV streaming on Iotivity. > > There are many ways of standardized streaming -- OCF should pick what they > believe is optimal and refer to it - last I heard this was UPnP AV4 (which is > part of OCF) and DLNA -- Scott > > -----Original Message----- > From: cftg at openconnectivity.org <mailto:cftg at openconnectivity.org> > [mailto:cftg at openconnectivity.org <mailto:cftg at openconnectivity.org>] > On Behalf Of Thiago Macieira > Sent: Friday, June 10, 2016 4:58 PM > To: cftg at openconnectivity.org <mailto:cftg at openconnectivity.org>; > uzchoi at samsung.com <mailto:uzchoi at samsung.com> > Cc: ?? <ashok.channa at samsung.com <mailto:ashok.channa at samsung.com>>; > Manoj Verma <manoj.kumar.mbm at gmail.com <mailto:manoj.kumar.mbm at > gmail.com>>; iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at > lists.iotivity.org> > Subject: Re: [cftg] RE: Re: [dev] AV streaming on Iotivity. > > AV streaming should be implemented using other protocols. Please use RTP/RTSP > or whatever is most suitable for your device. > > OCF should be used to discover the device that supports streaming and to > obtain the parameters of the stream. > > On sexta-feira, 10 de junho de 2016 23:51:07 PDT ??? wrote: > > Prior to implementation, data type should be defined for this streaming. > > According to OCF spec, the most similar one is the string data type > > with 16 bytes length which does not map with streaming use case. Let > > me include cfg mailing list. > > BR, Uze Choi > > > > > > --------- Original Message --------- > > Sender : ?? <ashok.channa at samsung.com <mailto:ashok.channa at > > samsung.com>> Senior Technical > > Manager/SRI-Bangalore-IoTivity/???? Date : 2016-06-11 00:19 (GMT+9) > > Title : Re: [dev] AV streaming on Iotivity. > > > > Hello, > > > > Is there any default support for AV Streaming in current iotivity > > stack or we need to think in that prospective? --> Currently we don't > > have any AV Streaming support except block wise transfer which can be > > used for comparatively bigger blocks but not for video streaming. > > Proposal and contributions always welcome. > > > > Regards, > > Ashok > > ------- Original Message ------- > > Sender : Manoj Verma<manoj.kumar.mbm at gmail.com <mailto:manoj.kumar.mbm > > at gmail.com>> Date : Jun 10, 2016 > > 19:16 (GMT+05:30) Title : [dev] AV streaming on Iotivity. > > > > Hello all, > > > > [AV Streaming] > > > > Video Streaming over COAP. > > > > Is there any default support for AV Streaming in current iotivity > > stack or we need to think in that prospective? > > > > > > Thanks and regard > > > > Manoj Kumar (NEC Technmologies) > > > > > > ---------------------------------------------------------------------- > > ------ > > ------ Sr. Technical Manager, Software Architect. > > SRI-B, IoT Division/ IoTivity, Samsung Electronics Co., Ltd. > > +91-9880709710 > > ---------------------------------------------------------------------- > > ------ > > ------ > > _______________________________________________ > > iotivity-dev mailing list > > iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at > > lists.iotivity.org> > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> > > > -- > Thiago Macieira - thiago.macieira (AT) intel.com <http://intel.com/> > Software Architect - Intel Open Source Technology Center > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160614/b5af362d/attachment.html>
