Re: [rtcweb] Reg retransmissions using JSEP approach.

An implementation of ROAP on top of JSEP (-00) is available here:

http://code.google.com/p/webrtc-samples/source/browse/#svn%2Ftrunk%2Froap-jsep

One of the areas in which it is incomplete is retransmissions....

On 06/10/2012 04:21 PM, Cullen Jennings wrote:
> On Jun 9, 2012, at 7:26 , kiran kumar wrote:
>
>> Hi all,
>>
>> I am new to this list, so please don't mind if I am repeating the same question, if it has already discussed in this list.
>>
>> My doubt is regarding how JSEP style of implementation will differentiate the retransmission of messges with out ROAP.
>>
>> According to few mails and discussion lists, It is specified that ROAP is going to be replaced by JSEP.
>> But in updated JSEP draft an example with ROAP is also provided.
>>
>> If ROAP is going to be replaced by JSEP, which part of JSEP will differentiate the retransmitted offers.
>> ROAP is having "seq" field to differentiate it.
>> Is that part going to be completely left to the application protocol ?
>>
> Yes, I think the idea i the application would have to deal with that. It probably needs to keep track of the keeping between the offer / answers to the seq number too so that if an offer is rejected and it rolls back to reg previous offer, it has that offer so it can roll back. At the same time browser implementation  also need to keep track of the various offers so they can roll back. More text is needed in the drafts on all this.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb