Hi, As you noted, that I-D is expired. In addition, work is being done to define a general mechanism for conveying user indications to support user interaction with applications. The current I-Ds are:
http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-markup-00.txt http://www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact-reqs-01.txt http://www.ietf.org/internet-drafts/draft-fairlie-sipping-netapp-session-00.txt http://www.ietf.org/internet-drafts/draft-culpepper-sip-key-events-01.txt You can expect an update to the requirements I-D shortly I believe. And a general framework, to follow. Himanshoo Ks wrote: > Hi, > > I have a question on draft-culpepper-sip-info-event-00.txt: > > 1. It says that MGCP subtype can be used to indicate the protocol between > MGC and MG and then some MGCP message can be encapsulated to request and > report the events as per MGCP packages. Does this mean that I can send the > complete command line ( I mean whole of RQNT) as message body for the INFO > request. It is needed since I also need to identify the end point where I > want event to be detected. The idea was that the the call identifying info in the SIP request would be used by the MGC to identify MGCP/Megaco connection. Just as it would for any other interworking function. The only proposed INFO message content was the actual event request/notification. > > 2. And more importantly, as per the date mentioned ni draft, this draft has > expired on October 2000. Is there some other draft / RFC which is taing care > of there issues ? Should I refer to some other document for finding solution > to this problem. Yes, the forthcoming I-Ds mentioned above. Best Regards, Bert Culpepper > > regards > Himanshoo > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use [EMAIL PROTECTED] for questions on current sip > Use [EMAIL PROTECTED] for new developments on the application of sip > > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
