RFC3265bis
Adam Roach <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
After 6 years of testing at SIPits and other experience in the field, it feels like time to fix some of the known bugs in RFC 3265. I've put together a 3265bis that addresses most of the bugs that have been reported to date (although some are called out as known issues): http://www.ietf.org/internet-drafts/draft-roach-sipcore-rfc3265bis-00.txt If you're already familiar with RFC 3265, I would suggest using Appendix C as your roadmap to navigating the changes. The areas I know I need feedback on are the open issues listed in Appendix B. Of course, it's always possible that the new document will prompt people to share implementation experience that hasn't yet been captured -- I'm happy to hear about that too. /a _______________________________________________ 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