Inline ... >-----Original Message----- >From: Paul Kyzivat (pkyzivat) >Sent: Saturday, December 01, 2007 2:31 PM >To: DRAGE, Keith (Keith) >Cc: [email protected] >Subject: Re: [Sip] Comments on draft-kaplan-sip-info-events-00 > >Keith, > >A comment about one of your points: > >DRAGE, Keith (Keith) wrote: > >> In particular, one area which needs to be covered is how the >embedded >> information tranfer caters for out of sequence delivery, given that >> the carriage mechanism does not guarantee order of delivery in all >> circumstances of SIP usage. > >I'm wondering what you have in mind here. > >It is possible to send request R1 then send R2 before getting >a response to R1. And then it is possible for R2 to arrive >before R1, and in that case it will be accepted. But then, >when R1 arrives there will be a CSeq error so it will be rejected.
But if the INFO is used for dtmf, the rejected request will be a problem as it will result in loss of digit information. So I think package type should define whether it is ok to send overlapping requests or not. Sanjay > >The end result is that you can get *nondelivery* of a message, >but not *out of order delivery*. > > Thanks, > Paul > > >_______________________________________________ >Sip mailing list https://www1.ietf.org/mailman/listinfo/sip >This list is for NEW development of the core SIP Protocol Use >[EMAIL PROTECTED] for questions on current sip >Use [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
