Re: Query Regarding M2PA Rfc 4165
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Amit, Amit Ray wrote: (Fri, 21 Oct 2005 20:46:10) > > Hi Brian, > I'd like some clarification on the Processor Outage mechanism > defined in RFC 4165. > > What should be the behavior in the following scenario: > > 1. Let us suppose there are two sides A and B. A and B both are in LPO > condition. Hence both the sides are in LPO and RPO simultaneously. > 2. Now LPO ends at side A. It will send a LPO Ended message to peer. > 3. Now what should be the behavior at side B? As it is still in LPO, should > not send a LS Ready message because it has some buffered data which is > still not notified to the application(as per the buffering mechanism in > LPO) . Hence correct re synchronization of FSN and BSN is not possible at > this moment. Why not? B can send LS Ready. Then I suppose there is no problem. --brian > 4. RFC 4165 says that if one end is in RPO, it should continue sending user > data messages and other end should buffer it. It also says that "M2PA > SHALL NOT resume transmitting User Data messages until it has sent the > Link Status Ready message". > 5. Hence in this case neither A nor B can send a packet as neither end > sends a LS Ready message. But as A is in RPO, it can continues sending > and receiving user data messages and B should buffer it. > -- Brian F. G. Bidulock [email protected] http://www.openss7.org/