Re: PRACK update: other changes than allowing SDP offer inPRACK to be rejected?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: PRACK update: other changes than allowing SDP offer in PRACK to be rejected?
Hi,
 
Now, when everybody is in offer/answer mode, please let me remind me of the other issue we need to solve: rejecting SDP offers in PRACKs.
 
 
The status at the moment is that we agreed that one should be able to reject an SDP offer in a PRACK with a 4xx response.
 
 
Q1. One of the questions were whether that 4xx response should also terminate the re-transmission of the reliable 18x response the PRACK is supposed to acknowledge.
 
- One problem with saying that the re-transmission of the 18x shall stop is that if an intermediate rejects the PRACK, the UAS will still re-transmit the 18x - eventhough the UAC will think the re-transmission has ceased.
 
- One problem with saying that the re-transmission of the 18x shall not stop (basically meaning that the UAC would have to send a new PRACK) is that the current PRACK RFC more or less says that the re-transmission stops when the PRACK is received - no matter what the response code is going to be (maybe it was written in that way because it was assumed that the response code would always be 200).
 
So, we really need some input and thoughts on that.
 
 
 
 
Q2. Another issue was whether we were going to loose up some other PRACK restrictings, e.g. that the first reliable 18x must contain an SDP offer if the INVITE didn't. We agreed that we are NOT going to do that, unless someone can show that the current rules causes problems.
 
So, if you have use-cases or scenarios where the first-reliable-18x-must-contain-SDP-offer rule causes problems, please post them on the list.
 
 
Regards,
 
Christer
 
 
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux