On Dec 3, 2007, at 2:36 PM, [EMAIL PROTECTED] wrote:
From: Adam Roach <[EMAIL PROTECTED]>
I had it in my head many years ago that overlapping NITs were
illegal
also, but I couldn't ever find any supporting text in RFCs. I
think it
was in some pre-publication versions of 2543-bis, but got pulled
out
before finalization.
I think that overlapped transactions is a basic feature of SIP. (The
UAC has to be able to deal with the occasional 500 Out Of Order
situation, of course.)
Yes, but just because the protocol can handle overlapped NITs doesn't
mean the application should send them that way. If you have
sequential data that needs to be delivered in order (for example,
MESSAGE requests) you have to sequence the requests at the
application level.
--
Dean
_______________________________________________
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
