Re: M2PA: resynchronization of sequence numbers after PO
sdjugum <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Hi Brian, Since the question remained open I would just like to repeat it so that it is not left unanswered. The example metioned below clearly indicates that side B uses BSN received in LS Processor Recovered message to synchronize it's sequence numbers and that it begins sending messages after it has sent LSR (stream 1). So, the question is - what should it do at reception of LSR (stream 1) from peer? Example clearly shows that LSR is ignored and that BSN received in it is not used. So, which message should be used for synchronization and sending resume at side leaving RPO - LS PR or LSR (stream 1)? Best regards, Sasa Dario wrote: > > Hi Brian, > > Perhaps this was not clear from the description in section 4.1.4 of RFC, > however section > 5.4 brings more doubts: > In figure 16, the "B"-side (the side that receives Link Status Processor > Recovered message), > after receiving LS PR and after sending LS Ready (stream 1) message "has > completed synchronization > of sequence numbers and has sent LS Ready, so it is able to resume sending > data at this point with > the new sequence numbers". > > A side (the side that recovered from PO) sends the second LS Ready (stream > 1) but it seems noone > does anything with that message: if the purpose of synchronization was to > send the last received BSN > to synchronize FSNs at remote peer, then two messages seem to be > sufficient? > > Best regards, Dario > > > > > Brian F. G. Bidulock wrote: >> >> Dario, >> >> Dario wrote: (Thu, 15 Nov 2007 06:22:27) >>> >> -X--snip--X- >>> >>> Could you please explain why the second Link Status Ready (stream 1) is >>> needed? >>> thanks! >>> Kind regards, Dario >>> >> >> To acknowledge the LSR sent from the other end and permit the peer to >> again send MSUs. >> >> --brian >> >> >> -- >> Brian F. G. Bidulock >> [email protected] >> http://www.openss7.org/ >> >> >> _______________________________________________ >> Sigtran mailing list >> [email protected] >> https://www1.ietf.org/mailman/listinfo/sigtran >> >> > > -- View this message in context: http://www.nabble.com/M2PA%3A-resynchronization-of-sequence-numbers-after-PO-tf4812071.html#a13797998 Sent from the IETF - Sigtran mailing list archive at Nabble.com.