Hi,
>I did not see any discussion of "in use" proposal (including the Archives).
>
>There was just Holmberg's "commit by Offer/Answer"(Mutli-O/A was not discussed further).
>
>3GPP is waiting. But I think we should collect every meaningful proposal.
>There was just Holmberg's "commit by Offer/Answer"(Mutli-O/A was not discussed further).
>
>3GPP is waiting. But I think we should collect every meaningful proposal.
3GPP is not
waiting, because we already informed them about the current
agreement.
>And I think, it should be public as draft.
>And I think, it should be public as draft.
The agreement is
that there will be an "essential correction" draft which, corrects whatever
text/RFC that needs to be fixed, based on the agreed
outcome.
Regards,
Christer
Gonzalo Camarillo
<Gonzalo.Camarillo@xxxxxxxxxxxx>
2009-02-27 19:01 |
|
Hi,
> *And I really want to know why solution in my draft without considering.
we have had a huge thread considering and discussing those issues. If by
considering you mean accepting whatever you propose discarding WG
consensus, then that is impossible.
Thanks,
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.
_______________________________________________ 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