I believe we can take that as a given condition. Please validate the results of your comments so far in any new version, and of course, it is open for all to make comments on this issue.
Note that there are some things that are not well defined in RFC 2796, so primarily the WG will be looking for compatibility with what RFC 2976 actually says, rather than what one implementation may have interpreted. So please back up any comments on compatibility issues with existing RFC 2976 text. Regards Keith > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Paul Kyzivat > Sent: Friday, October 24, 2008 2:58 PM > To: Eric Burger > Cc: SIP IETF > Subject: Re: [Sip] INFO Events Replacing or Updating INFO? > > > > Eric Burger wrote: > > > [X] INFO Events should Obsolete RFC 2976 [ ] INFO Events > should Update > > RFC 2796, because ____________ [ ] I do not care what you do > > But of course the new document must carefully define backward > compatible behavior. Its made a stab at that, and I expect it > to be complete before approval. > > Thanks, > Paul > _______________________________________________ > Sip mailing list https://www.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://www.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
