The notion of "early dialog" in 3261 is a bit of a misnomer. It would be
better described as an "early invite-dialog-usage". (See
draft-ietf-sipping-dialogusage-06.)
The dialog itself isn't early or late, it just exists or not. When an
early invite-dialog-usage is established, a dialog is established. At
that point it *should* be ok to send OPTIONS or MESSAGE, since they
depend only on the dialog and have nothing to do with the
invite-dialog-usage. INFO is only valid as part of an
invite-dialog-usage, but I can see no reason why it shouldn't be ok in
an early one.
But the important word above is *should*. This is largely unexplored
territory, so I wouldn't be surprised to find these things don't always
work.
Paul
Nina Garaca wrote:
> Hi,
>
> According to RFC 3261, RFC 3428 and RFC 2976, INFO, OPTIONS, MESSAGE
> requests are mid-dialog requests. Does it mean that these can be sent or
> received during the early dialog also?
> Example:
>
> INVITE
> |-------------------------------->|
> | 180 |
> |<--------------------------------|
> | MESSAGE |
> |-------------------------------->|
> | 200 (MSG ) |
> |<--------------------------------|
> | 200 |
> |<--------------------------------|
>
> Thanks in advance.
>
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
