Hi, > 1. define "in use" may make violation of current RFCs. the issue we are talking about is not addressed by current RFCs. As I indicated in my original email, we will have to make compromises. After many discussions within the WG, the current understanding is that we are willing to lose the atomicity of re-INVITEs. The idea is not to avoid violations by all means but to choose the best solution. > 2. the two side can have different view of "in use". if two endpoints are involved in a media session, they need to have the same view. Otherwise, if an endpoint uses a codec the other endpoint is not ready to receive, nothing would work. Could you provide an example of a situation where two endpoints are not in synch. > 3. And as there is a clear session state by current RFCs, why not choose > it :). Section 6 of RFC 3312 introduces the concept of the session parameters the endpoints are using and the session parameters the endpoints will use once their preconditions are met. However, that RFC did not define the concept formally or clearly. We can define it properly if we think it is a useful concept to have. Cheers, Gonzalo _______________________________________________ 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
