Hi Gao, I have two concerns. 1. Section 5.1 seems to describe different rules for each of initial INVITE and reINVITE. But I think there is no reason why the rules is separated. 2. Section 5.1 seems to say that the timing UA may send UPDATE is "after sending or receiving PRACK request". But I think it should be "PRACK transaction is completed". Because "after-PRACK-request" cause a glare case. Do you agree? My proposals regarding section 4 of the draft is based on these. Thanks, Shinji gao.yang2@xxxxxxxxxx Thu, 22 Apr 2010 17:04:43 +0800 >Hi Shinji, > >I feel your charts seems the same as RFC3311 and O/A draft. > >Could you tell us more about your problem? > >Thanks, > >Gao > >=================================== > Zip : 210012 > Tel : 87211 > Tel2 :(+86)-025-52877211 > e_mail : gao.yang2@xxxxxxxxxx >=================================== > >sipping-bounces@xxxxxxxx 写于 2010-04-22 16:23:12: > >> Hi all, >> >> At this chance, I want to hear your opinion about the >> interworking of INVITE and UPDATE. >> >> This is related to chapter 4 in a offeranswer draft, >> >> Regarding "5.1 Sending an UPDATE" of RFC3311, Paul said that >> "this language itself is non-normative and is justified as >> a corollary of 3261." >> >> I think so, but these descriptions are also very messy. >> About the timing when UA can send an UPDATE request, >> at last I think as the following, >> >> A B >> *| |* >> *|ini/re-INVITE(offer) |* >> |------------------------------>| >> | 1xx-rel(answer)| >> |<------------------------------| >> |PRACK | >> |------------------------------>| >> | 200(PRACK)| >> |<------------------------------| >> *| |*<-- after this pont, UA may >> *| |* send UPDATE with offer >> *| |* >> >> A B >> *| |* >> *|ini/re-INVITE(no offer) |* >> |------------------------------>| >> | 1xx-rel(offer)| >> |<------------------------------| >> |PRACK(answer) | >> |------------------------------>| >> | 200(PRACK)| >> |<------------------------------| >> *| |*<-- after this pont, UA may >> *| |* send UPDATE with offer >> *| |* >> >> Do you have any questions or comments? >> >> Regards, >> Shinji _______________________________________________ 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
