Yeah my bad for not re-writing that whole thing. It started out as a "rfc3265 Event Packages for INFO" type thing, but after your emails on the subject we were convinced that was a bad way to go. I apologize for not cleaning it up better before submission. Do you want me to re-submit using better terminology? (unfortunately due to the submission deadlines I don't think I can do so officially?)
I was thinking this was really just a discussion point doc for the Vancouver meeting, and if the concept in general was adopted we'd fix all the terminology. Sorry 'bout that. :( -hadriel > -----Original Message----- > From: Adam Roach [mailto:[EMAIL PROTECTED] > Sent: Monday, November 19, 2007 3:57 PM > To: Hadriel Kaplan > Cc: [email protected]; Christer Holmberg > Subject: Re: [Sip] FW: I-D Action:draft-kaplan-sip-info-events-00.txt > > In general, I think the mechanism outlined in > draft-kaplan-sip-info-events-00 is a good starting place for > disambiguating multiple usages of INFO, and I'd like to thank Hadriel > and Christer for putting forth the effort to submit a concrete proposal. > I have a number of specific suggestions for improving the mechanism that > I'd like to offer up at some point in the future. > > However, I can't support the document in its current form. > > The current document conflates INFO packages with Event packages in a > way that is quite dangerous -- even going so far as to call INFO > packages "Event packages" in a few places (c.f. section 4: "The general > concept is that the UAC generating an INVITE request includes the Event > packages it supports sending and receiving, in two new headers: > Send-Event and Recv-Event."). It confusingly re-uses the "Event" header > field from RFC 3265, and even suggests that common packages can be > defined for RFC 3265 and for INFO. > > This harmful conflation between RFC 3265 event packages and INFO > packages pervades the document. Until this issue becomes less confused > in the text, I strongly believe that the document will do far, far more > damage than good. > > /a > > Hadriel Kaplan wrote: > > Howdy, > > Just an FYI that Christer and I submitted a draft for SIP INFO events, > based on the email discussion. This is on the agenda for Vancouver. > > Cheers, > > -hadriel > > > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >> Sent: Thursday, November 08, 2007 11:00 PM > >> To: [EMAIL PROTECTED] > >> Subject: I-D Action:draft-kaplan-sip-info-events-00.txt > >> > >> A New Internet-Draft is available from the on-line Internet-Drafts > >> directories. > >> > >> Title : SIP INFO Event Framework > >> Author(s) : H. Kaplan, et al. > >> Filename : draft-kaplan-sip-info-events-00.txt > >> Pages : 12 > >> Date : 2007-11-08 > >> > >> This document defines a proposed solution for defining, negotiating > >> and exchanging info-event notifications in INFO messages, within SIP > >> invite-created dialogs, for applications which need to exchange > >> session-related information inside the invite-created dialog. This > >> draft addresses issues and open items from RFC 2976, and updates it. > >> > >> > >> A URL for this Internet-Draft is: > >> http://www.ietf.org/internet-drafts/draft-kaplan-sip-info-events-00.txt > >> > >> To remove yourself from the I-D Announcement list, send a message to > >> [EMAIL PROTECTED] with the word unsubscribe in the body of > >> the message. > >> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > >> to change your subscription settings. > >> > >> Internet-Drafts are also available by anonymous FTP. Login with the > >> username "anonymous" and a password of your e-mail address. After > >> logging in, type "cd internet-drafts" and then > >> "get draft-kaplan-sip-info-events-00.txt". > >> > >> A list of Internet-Drafts directories can be found in > >> http://www.ietf.org/shadow.html > >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >> > >> Internet-Drafts can also be obtained by e-mail. > >> > >> Send a message to: > >> [EMAIL PROTECTED] > >> In the body type: > >> "FILE /internet-drafts/draft-kaplan-sip-info-events-00.txt". > >> > >> NOTE: The mail server at ietf.org can return the document in > >> MIME-encoded form by using the "mpack" utility. To use this > >> feature, insert the command "ENCODING mime" before the "FILE" > >> command. To decode the response(s), you will need "munpack" or > >> a MIME-compliant mail reader. Different MIME-compliant mail > >> readers > >> exhibit different behavior, especially when dealing with > >> "multipart" MIME messages (i.e. documents which have been split > >> up into multiple messages), so check your local documentation > on > >> how to manipulate these messages. > >> > >> Below is the data which will enable a MIME compliant mail reader > >> implementation to automatically retrieve the ASCII version of the > >> Internet-Draft. > >> > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 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
