??: Re: ??: Re: ??: Re: ??: Re: ??: Re: ??: Re: Closing the offer/answer rollback issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




I am not sure media synchronization you mentioned is the same as I talked.

I said two:

1. some precondition case, UAC and UAS can have inconsistent session state.

2. we let the session state user rejected alone, and can be illegal used.


And I really want to know why solution in my draft without considering. It is on January 8, 2009





Gonzalo Camarillo <Gonzalo.Camarillo@xxxxxxxxxxxx>

2009-02-27 18:38

收件人
gao.yang2@xxxxxxxxxx
抄送
christer.holmberg@xxxxxxxxxxxx, Eric.wangxr@xxxxxxxxx, sipping@xxxxxxxx, sipping-bounces@xxxxxxxx, wang.libo@xxxxxxxxxx
主题
Re: 答复: Re: 答复: Re: 答复: Re: ??: Re: [Sipping] ??: Re:  ??: Re: ??: Re: ??: Re: ??: Re: ??: Re:  Closing the offer/answer rollback issue





Hi,

at this point, the discussions are going in circles and are not
productive any longer. No new ideas are being introduced.

I think I now understand your main points (media synchronization and
session continuity) so that I can put together a more formal description
of the straw-man proposal in my original email that meets all the
requirements brought up here.

The proposal will be what the WG had agreed on before with slight
modifications (e.g., a clarification of the "in use" concept) in order
to better address your concerns.

Thanks for your input,

Gonzalo

gao.yang2@xxxxxxxxxx wrote:
>
> Yes. I think it is can, not MUST.
>
> And with precondition, the user can be hinted the new modification just
> after Offer/Answer pairs.
>
>
>
>
> *Gonzalo Camarillo <Gonzalo.Camarillo@xxxxxxxxxxxx>*
>
> 2009-02-27 18:22
>
>                  
> 收件人
>                  wang.libo@xxxxxxxxxx
> 抄送
>                  christer.holmberg@xxxxxxxxxxxx, gao.yang2@xxxxxxxxxx, sipping@xxxxxxxx,
> sipping-bounces@xxxxxxxx, Eric.wangxr@xxxxxxxxx
> 主题
>                  Re: 答复: Re: 答复: Re: ??: Re: [Sipping] ??: Re:  ??: Re: ??: Re: ??:
> Re: ??: Re: ??: Re:  Closing the offer/answer rollback issue
>
>
>                  
>
>
>
>
>
> Hi,
>
> UEB would have rejected the video stream in the 183 response.
>
> Gonzalo
>
> wang.libo@xxxxxxxxxx wrote:
>  >
>  > HI,
>  >
>  >    I think the video will be established.The figure below shows the case.
>  >
>  >
>  >       1. REINVITE(audio,vedio)
>  > ----------------------------->
>  >         2. 183
>  > <-----------------------------
>  >       3. PRACK/200  
>  > <------------------------------>
>  >       4. UPDATE(audio,vedio)
>  > ----------------------------->
>  >         5. 200(audio,vedio)
>  > <-----------------------------
>  >
>  >         6. 4XX
>  > <-----------------------------
>  >
>  > After step 5, UEs' precondition are met ,and the video stream is
>  > established too.
>  > But UE-B send 4xx to reject 4XX (step 6).
>  >
>  > Regards.
>  >
>  >
>  >
>  >
>  > *Gonzalo Camarillo <Gonzalo.Camarillo@xxxxxxxxxxxx>*
>  >
>  > 2009-02-27 17:30
>  >
>  >                  
>  > 收件人
>  >                  wang.libo@xxxxxxxxxx
>  > 抄送
>  >                  christer.holmberg@xxxxxxxxxxxx,
> gao.yang2@xxxxxxxxxx, sipping@xxxxxxxx,
>  > sipping-bounces@xxxxxxxx
>  > 主题
>  >                  Re: 答复: Re: ??: Re: [Sipping] ??: Re:  ??: Re: ??:
> Re: ??: Re: ??:
>  > Re: ??: Re:  Closing the offer/answer rollback issue
>  >
>  >
>  >                  
>  >
>  >
>  >
>  >
>  >
>  > Hi,
>  >
>  >  >   If UE-A wants to communicate with UE-B by video, but UE-B only
> want to
>  >  > communicate by audio.
>  >
>  > then UE-B rejects the video stream and the video stream is never
>  > established.
>  >
>  > Cheers,
>  >
>  > Gonzalo
>  >
>  >
>  > --------------------------------------------------------
>  > 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.
>
>
>
> --------------------------------------------------------
> 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.



--------------------------------------------------------
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

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux