interworking(1/2) of INVITE and UPDATE

OKUMURA Shinji <[email protected]> Thu, 22 Apr 2010 17:23:12 +0900
Newsgroups gmane.ietf.sipping
Message-ID <[email protected]>
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 [email protected] for questions on current sip
Use [email protected] for new developments of core SIP