Hi,
> This is one of the figures in my proposals.
>
> A B
> | |
> | re-INV (offer0)|
> |<------------------------------|
> |1xx-rel (answer0) |
> |------------------------------>| --+
> |offer1(UPD) offer2(PRA)| M2| Acknowledge
> M1 |============\ /===============| <-+
> | \/ |
> | /\ |
> |<===========/ \==============>|
> | 491 (UPD)|
> |<------------------------------|
> | |
>
> If the INVITE is an intial INVITE, UA A can not send this UPDATE.
Yes. There's no such consistency for Ini-INVITE and Re-INVITE.
>
> >>
> >> 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?
> >
> >I think timing of "PRACK transaction is completed" is better.
> >
> >But it seams that there's no problem for UAS sending UPDATE just after
> >receiving PRACK(with out SDP).
> >If PRACK has SDP, then UAS should not send the UPDATE by O/A rules.
>
> This is another one of the figures in my proposals.
>
> A B
> | |
> | re-INV (no offer)|
> 1st reliable+-- |<------------------------------|
> response | M1|1xx-rel (offer1) |
> +-> |==============================>| --+
> | answer1(PRA)| M3| Acknowledge
> |<===========\ /===============| <-+
> | \/ |
> | /\ offer2(UPD)|
> |<===========/ \===============| M2
> |500 (UPD) |
> |------------------------------>|
> |2xx-PRA |
> |------------------------------>|
> | |
>
> This is a message crossing case.
The 500 is always with retry. So, B could re-send the UPDATE later.
But, I am not oppose to the clarification or fixing you suggested.
Thanks,
Gao
-------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________ 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
